yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] faceyourfaces:
I know I'm a little late, but there is CWM for the AOKP rom. The FC07 BootImg on the e4gtuato.zip file worked fine for me on the older version which was based off of FC15.
[Samsung Epic 4G Touch] krook250:
I would try that, but these folks have me scurred about using cwm within aokp. I have flashed between caulks ics/venum ice, anakonda/mijjz goodness,xplod mini and a couple other ICS roms all from cwm with absolutely no issues so far.

I am thoroughly confused right now. I am on aokp build 28 with a few significant issues and not sure what what direction to go next. I know how to get out of aokp safely now, but not sure which rom i want to go to, little issues with each that I dont know how to fix yet.
[Samsung Epic 4G Touch] Epix4G:
Read this thread it happens when using ics kernel with cwm .and then tell us u want to use cwm with a ics kernel.....it bricks phones please read it and understand

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

That's why people are using Odin to get el26 GB on their phones to flash with
[Samsung Epic 4G Touch] playya:
If you have been having luck thats fine but I can not see how you have not noticed int eh OP of the ICS roms and the OP of the recoveries it gives you instructions on what to do and what not to do. Also there are quite a few threads in here about the horror stories of the now infamous blue light of death. Once again if you have escaped this then maybe you should tell us your secret to success. Honestly the few extra steps it takes to ensure your phone stays your phone is well worth it.

Like Epix has posted please read up a little just incase something happens to you or anyone else who claims no problems so you know how to help yourself. Hopefully we wont have to see a I Think I just bricked my Phone thread from you.

Odin EL26 CWM and basically everything else stays the same after that... except you would need to either reflash the ICS rom you are using or have a copy of the kernel readily available
[Samsung Epic 4G Touch] krook250:
I've read that, hence the reason for my posts. I am not going to load cwm and start flashing away. From aokp, I will odin back to GB before I flash any new ICS roms. I also won't be flashing between other ICS roms, even ones I have done before with no problems. I odin every time now, but it is putting a serious damper on my flashing addiction.

I could flash 3 roms in the time it takes me to odin back to GB, lol!
[Samsung Epic 4G Touch] Epix4G:
I don't Odin to stock all the time I mobile Odin the el26 cwm kernel and then boot strait into recovery as the GB kernel won't boot the ics ROM and then I flash from there but I also u caulks format all too ....
[Samsung Epic 4G Touch] playya:
Thus is what I used to do at first myself I would flash the CWM kernel then just nandroid back my old rom and keep it moving. It just basically seems that as long as you do everything in a GB kernel based recovery as long as it is not the Touch recovery you should be OK
[Samsung Epic 4G Touch] krook250:
I am gonna look into mobile Odin so i don't have to be sitting at a PC to do work. So if I go back to gb and get my modem biz straightened out then flash an ics rom, my modem changes will stick?

It seems like this issue is isolated to sprint only, right? Much buddy on att is flashing ics over ics like crazy. And he said he hasn't seen anything like this over there.
[Samsung Epic 4G Touch] faceyourfaces:
I've only used the ICS recovery on AOKP to change modems and flash GB roms because it probably wouldn't work too well with other ICS roms.

UPDATE: It seems that using recovery on Touchwiz-based ICS roms (like Blend ICS) is safe but it is much more dangerous on roms built from stock (like CM9). Your buddy must be using roms based off of leaked builds and not stock AOSP.

------------------

If you flashed back to Gingerbread to change your modems and installed an Ice Cream Sandwich rom over it the modem should stay.
[Samsung Epic 4G Touch] Epix4G:
It has nothing to do with that it's the ics kernel and aosp and tw is using the same kernel but with minor changed , because there is no source released there can't be a built from source aosp kernel ....there is no safe ics kernel with cwm when source is released they will fix it, but the note has the same problem
[Samsung Epic 4G Touch] faceyourfaces:
The recovery that came with Blend ICS worked fine for me though. Trying to flash using recoveries on other ICS roms gave me soft bricks. Would you have any idea how Blend worked for me?
[Samsung Epic 4G Touch] Epix4G:
It is the same recovery and soft bricks ate usually from not wiping right....but use that kernel with cwm and wipe data and your risking a b.l.o.d. It doesn't take much ....the thing is Samsung changed a couple things with how the data partition is handled and they also changed a couple other partitions and sfhub said he thinks it writes over two of the partitions at the same time when wiping and makes both unusable creating a brick

... writers thing is it damages the emmc somehow and makes it even impossible to jtag it .... Which should really never happen
[Samsung Epic 4G Touch] faceyourfaces:
So the best thing I guess would be to just to avoid ICS recoveries all around.
[Samsung Epic 4G Touch] Epix4G:
For right now yes I avoid ics recoveries if you want to back up flash the el26 boot into it and flash the ics kernel from your ROM your ie .. cm9 aokp ,codename and stay in that el26 & create your backup then reboot or flash new ROM

It's a little more work but safe
[Samsung Epic 4G Touch] radrian92:
I'm in the same dilemma. I wanted to give CM9 a try and I got it running and what not. Then decided that it wasn't really stable and proceeded with Odin el29 and that flashed good. Then I did the one click root and Cwm and that went good. I then wanted to flash a ROM and it went with out a hiccup but as soon as it rebooted it sent me to the stock Android recovery. am I doing anything wrong? Thuds is the first time this had happened.
[Samsung Epic 4G Touch] faceyourfaces:
What was the rom that you flashed? Sometimes wiping/factory reset could fix the problem. If it doesn't you'll want to Odin back to el29.
[Samsung Epic 4G Touch] radrian92:
Its phantoms fd02. I have wiped/factory reset but after flashing that particular ROM it takes me to "manual mode" and I lose cmw.
[Samsung Epic 4G Touch] VECTUS:
Go here: http://xdaforums.com/showthread.php?t=1587607 to see my tut on CWM and what it is.

First, I'll try to keep this simple. AOKP, and CM9 use CWM.

Unfortunately Samsung has not released the "Source" for their ICS kernel yet and full CWM cannot be added. Therefore the developers are using a "tweaked" form of an ICS kernel for AOKP, CM9 etc. This will get you booted and operate the rom, unfortunately, when you "flash" said rom it formats over your old gingerbread CWM recovery (remember we don't have it yet on ICS kernels) and adds back stock android recovery. NOTE: Gingerbread kernels DO NOT work on ICS Roms, DO NOT flash one over your ICS rom.

Second, Rogue recovery is a tweaked ICS (Steady Hawkin the maker also has them for Gingerbread) kernal with a basic recovery that WILL flash Touchwiz Based Roms (BUT NOT AOKP, CM9 etc). I develop on these roms and I've done it a hundred times (they will also flash between different versions of touchwiz Based Roms and themes). In Rogue Recovery a new user should ONLY use the Wipe Data, Wipe Cache, Wipe Dalvik and Format/Sys commands. Often times new users get key happy and format their emms, internal etc etc which WILL brick your phone. So BE CAREFUL of what you hit in recovery. If you are safe and follow the instructions of the developer you should be ok.

Third, ALWAYS make a backup. Remember, you are playing with an exspensive toy. If you can afford it, be careless, if not BE CAREFUL.

Fourth, until further notice stay away from and don't even bother looking for Touch Recovery (I'm sure its great, just for ICS on our phones...)

In conclusion, what did we learn? You went to EL26 with full CWM. You then flashed AOKP which has a stock ICS kernel (No CWM). And thats why you had android recovery and not CWM. Until source is out you won't have CWM on AOKP, CM9 roms. You CAN flash Touchwiz Based ICS roms in rogue recovery AFTER going back to EL26 first I might add even for a first time flash of a Touchwiz Based ICS roms, because ICS requires Full CWM to boot first time (if you brick your phone though, who do you blame if you get careless? YOU). Simple really.:D
[Samsung Epic 4G Touch] faceyourfaces:
I installed Phantom's FD02 earlier this week. When I needed to use recovery I went back to EL29 (using Odin) and installed recovery over that.
[Samsung Epic 4G Touch] -EViL-KoNCEPTz-:
When i use mobile Odin(haven't used it yet) to flash ICS roms can I just flash the el26 kernel+cwm boot to recovery and flash the rom, and the. Going back to GB use mobile Odin to flash just el26 kernel+cwm again boot to recovery flash the rouge gunslinger kernel and boot back to recovery and restore my nandroid made in rogue? Or do I need to Odin the entire GB rom tar from mobile Odin first? Trying to make heads and tails of all the different stuff I've read and be safe so i don't brick :)
[LG Revolution] revo_65:
I was just curious of others performance... So on the free adw that comes installed on Broken Out, if I click an app it is very quick at opening it. With ADW Ex this is not the case, also sometimes in Ex the dock icons are unresponsive when you click them, it takes a couple clicks. Anyone else experience this? I love Ex but these issues drive me nuts lol

Also these issues were there before Broken Out so it's not the problem.
[LG Revolution] pendragon11:
Funny, I was thinking the same thing. Really like ex so I'm trying to pretend it isn't there though
[LG Revolution] wheelern:
Ya I have the same thing with Ex, gotta hit the dock icons a few times sometimes.
[LG Revolution] elreydotcom:
Mt has the loopy smoothness tweak for the adw built in to broken out ROM, which probably has something to do with it. I think you can change the tweak to attach to adw ex, I'll play around with it and see what I can find.
[LG Revolution] revo_65:
Kk. I looked into the tweak and idk if this will work, haven't used it long enough to tell, but I just edited the init.d script and deleted the input for the stock LG launcher and replaced it with ADW Ex process name.
[LG Revolution] elreydotcom:
That's exactly what I did.. Also added a line for widgetlocker. Seems to have made a difference as far as speed is concerned
[LG Revolution] revo_65:
Yea after using it a bit it has seemed to help. Thanks for pointing out loopy smoothness as the thing to mess with!
[LG Revolution] JetBlue:
Wait so you're saying if you add more lines for certains apps they speed up?
[LG Revolution] gumnaam.sur:
So what exactly did you change ?

So what exactly did you change in init.d file ?
[LG Revolution] revo_65:
Um i think it is hit or miss. On the loopy smoothness thread he said it might work. But i dont think you want to add to many because it might put too much load on the CPU.

In init.d there is the loopy smoothness file, in there there should be a section towards the top titled launchers. you will see adw and the stock LG launcher process names. So I just deleted the process name for the lg launcher and replaced it with adwex (org.adwfreak.launcher). Then I rebooted and seems to be working much smoother
[LG Revolution] elreydotcom:
Very true, I was just curious if adding the widget locker process to the would stop the occasional slow unlock, and so far it's been rock solid. No lag
[LG Revolution] JetBlue:
Well if that's the case I'll try adding go launcher and seeing if it seems to work better.
[LG Revolution] pendragon11:
What did you add for widget locker? Under what list? Thanks guys
[LG Revolution] elreydotcom:
The list doesn't matter, those are just for reference. The hash marks in front of those scripts cause the script to skip those lines. However, I added it under the launcher processes as

renice -3 `pidof com.teslacoilsw.widgetlocker`
[LG Revolution] drt054:
I was on adw then tried ex on phone and my tablet but went back to regular adw on both. Speed and overall responsiveness were main reasons..
[LG Revolution] Spectre1206:
Noob here. I am having the same issues with the widgetlocker being slow and adwEx being slow. I have no idea how you guys are fixing the scripts but would love to fix the same issues. :confused: Can someone either show me how or maybe if it's one file upload the fixed file so the lag isn't there. It would be great for us Noobs who have no idea how to fix it. I am trying to learn how to create themes so in time I will maybe know how to do this.
[LG Revolution] Spectre1206:
I found the file thanks to root explorer. I changed the settings. When it saved it said it backed up the original and then exited. I rebooted the phone and went back to see if it actually changed it still states the same as if I didn't do anything. Did I do something wrong? Any help?

On the other hand it does seem that the phone is running much smoother.
[LG Revolution] revo_65:
are you sure you werent looking at the backed up file? Also i dont use root explorer but make sure in the settings it is set to "write" so you can make changes to the system folders.

Otherwise try a different file explorer, i use ES and have had a similar problem where i changed things but after a boot it wasnt changed...root browser by jrummy never fails
[LG Revolution] Haxcid:
For those reading this thread and wonder where init.d is

/system/etc/init.d

And it does seem to make ex more responsive to the touch. Good find.
[T-Mobile Samsung Galaxy S II SGH-T989] jahrule:
Can some one tell me why we can't compile AOSP for the t989 and just use Samsung kernel so everything works? Basically why can't we kang together a t989 ROM that is how much ever is needed of Samsung device modules etc and the rest AOSP?
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
You should do it so that we get AOSP rom
[T-Mobile Samsung Galaxy S II SGH-T989] Towle:
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
[T-Mobile Samsung Galaxy S II SGH-T989] jahrule:
It is cool. And yes i would love to do it. With my experience with linux this would be no biggie, but android i have no idea. I think that if it was possible surely someone would have made a flawless 98% AOSP rom with 2% samsung parts....... right?
[T-Mobile Samsung Galaxy S II SGH-T989] lilz4life:
Csb are u done tryna be a mod? Cause reading back to your comment you didn't really contribute anything useful to his question either.

Now as for the question also apks cannot simply be installed on a touchwiz room the framework for both of these is pretty different you have to actually change code and port it over can't simply uninstall =(
[T-Mobile Samsung Galaxy S II SGH-T989] jahrule:
You did not answer my question at all.
[T-Mobile Samsung Galaxy S II SGH-T989] lilz4life:
Then I don't u derstand ur question.
[T-Mobile Samsung Galaxy S II SGH-T989] alphadog32:
Okay, it is very difficult to make an AOSP ROM with no device tree. That's why we have barely any 100% working. Remember, if you take kernel apart, you will find yourself with many, many files. You need to look through them all and link all the files. If those linked files don't work, then maybe you have to add some. If it still doesn't work, you will need to rework the drivers/firmwares. It is a difficult process. You also need to link all kernel/ROM together. *APK's HAS NOTHING TO DO WITH THIS PORTING PROCESS*
[T-Mobile Samsung Galaxy S II SGH-T989] thederekjay:
Apparently you have never worked with source and/or compiled from... there are plenty of reasons why that can't happen. Main reason there is no device tree with proper source.

:: DARKSIDE ::
[T-Mobile Samsung Galaxy S II SGH-T989] jahrule:
I only use linux for the past 5 years i sure the hell have compiled and worked with source. I just never had to compile for anything other than x86(_64) cpu before aka no toolchaining.
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
This is among the useful response for the original question. I was just encouraging him to go try it that is the best way form him to figure out why its not that simple.

This question has been asked before and I have seen how people have responded with different answers of this question. Whenever this question has been responded with technical reasons then it just ends up being followed by a question of why cant you do "A" even though "A" is based on not knowing another technical reason. The problem is the real satisfactory answer involves knowing alot of the basics which would have precluded you from asking the question in the first place.

Asking this question is like ends up like the following

"A: Why cant you fish with potato bits as bait?"

"B: well fishes dont like to eat potatoes"

"A: potato is food though,Why dont they like food"

It has been suggested before so clearly if someone knew how to do it they would have done it. The best thing at this stage is to try it.
[T-Mobile Samsung Galaxy S II SGH-T989] jahrule:
Yea.. I was not implying that we grab APKs from some random AOSP build and copy on top of some working stock ROM. My question more is that I see on samsungs opensource site they give us kernel source for the t989 (have not looked at it yet) and then they gave us some build files to copy over and overwrite the build environment for AOSP which I did and built (currently trying to figure out how to use the *.img files), but shouldn't that give us a ~90% AOSP build? That or I am completely not understanding the README file from samsung.
[T-Mobile Samsung Galaxy S II SGH-T989] jahrule:
I think he was trying to say if you don't want to spend the time explaining the details because you make some asumptions about people and their posts whom you have never met... then it is best you remain silent rather than giving some smart remark as an answer.
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
I wasnt giving you a smart remarks just pointing out that at this point it is best to just try it because nobody knows all the exact steps because nobody has done it for this device.

You are left seeking genera android kernel advice which ->

If you run into trouble with technical details go here http://xdaforums.com/forumdisplay.php?f=565 since it is a better place to ask questions about using img files than in the same forum where people ask "how do I install custom rom" even the themer section is a better place.
[T-Mobile Samsung Galaxy S II SGH-T989] jahrule:
I was not saying you were being a smart %^& just saying what I think dude was saying. In fact because of your comment I went got the source from samsung and repo synced AOSP and compiled it and have been playing around since :) just a little stuck now. My question was for more a technical reason. I understand now that we don't have a device tree for the t989 that works flawlessly... at least thats what i get from alpha and darkside. Now my question more is what the heck is the use of the source from samsung then?
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
You can actually modify the Kernel it just takes work. For example if for some reason either the t989 or skyrockets ICS kernel was open sourced there would be a rotation fix so quick for the one with broken rotation.

Samsung just throws the source they finished out there but doesnt really provide or I think care to provide any work towards AOSP builds.
[T-Mobile Samsung Galaxy S II SGH-T989] rynstphn:
Check out this thread.
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
Hes asking about compiling Kernel from source I think
[T-Mobile Samsung Galaxy S II SGH-T989] jahrule:
No i am talking about the userland
[T-Mobile Samsung Galaxy S II SGH-T989] jahrule:
Yea thats cool and all but i am more intetested in GB. There is sone source that samsung gives us which i thought is the device tree for this phone... So in essence what i am asking is: what is the source that samsung provides and what use is it? I am aware of the kernel source already i am refering to the other package.
[Motorola Droid RAZR] iAaronHD:
Hey you all I rooted my phone a while back when I first got it. Now I want to unroot but I have a problem....My phone shows up as not being rooted, but I can't get rid of SU, can anyone help with this?

I can't remember which root method I did, I think it was called the "Forever Root" or something of the sort.
[Motorola Droid RAZR] Ronin3178:
Look for mattgroffl's RAZR Batman utility

Edit: http://xdaforums.com/showthread.php?t=1486718

in the development section, there is an automated unroot option in there.
[Motorola Droid RAZR] iAaronHD:
I tried doing this method but when I did the command prompt said "'moto-fastboot.exe' is not recognized as an internal or external command,

operable program or batch file." The Batman utility is saying the same thing.

EDIT: I got it man thanks! I used it to do a Fastboot Restore to 173. Worked like a charm.
[Motorola Droid RAZR] iolinux333:
just a thought: what if you did voodoo temp unroot then hard reset the phone?
[Motorola Droid RAZR] stephendowney:
How to get rid of su

you can re-root the phone and then install root manager, in root manager go to uninstall apps and it will show all installed apps even the system apps, find the su .apk select and reboot, you phone will still be rooted but the su app will be gone. from there you just need to unroot.
[Motorola Droid RAZR] iAaronHD:
I got it guys thanks for the advice!
[General Questions and Answers] austrooper:
Hi,

If anyone could point me in the right direction would be much appreciated. I flashed the early version of 4.0.3 from sammobile on my SG2 and since it has been really buggy, I have searched the net wide for a solution to restore to a stock ROM although they are all hosted on Megaupload which has been taken down. I would be happy to install a less buggy version, but for some reason none of my PC's will recognise the phone via USB. Any suggestions would be appreciated.

edit... after many more hours.....I have still been trying, no matter what I try the pc wont recognise the device, when it tries to install the usb driver its coming up as a Marvell 91x at config device!!!

baseband version: l9100XXlP6

kernal version: 3.0.1.15-l9100XXlP6-CL72050 se.infra@SEP-53 #3

Build no: IML74K

Im lost

Cheers
[Samsung Galaxy Nexus] Mrcojocaru:
Any thoughts? It's really weird to me (gives weird predictions, splitting words in half)

I'll just chalk it up to it being in beta.

It's really good looking though.
[Samsung Galaxy Nexus] zeke1988:
after 2 days of testing, i love it. it still in beta, cant expect much from it. also, smart spacing is amazing and larger spacebar too.
[Samsung Galaxy Nexus] Mrcojocaru:
Yeah the smart spacing is pretty cool. Don't know why they even have a space bar lol. Easiest way to type ever lol.
[Samsung Galaxy Nexus] Zengster6474:
To me it's either Swype or Swiftkey 3, I'll give Swiftkey 3 a try when I can.
[Samsung Galaxy Nexus] Stephen289:
I gave up on swype after finding it hard to adopt to one hand swyping, loving swiftkey beta 3
[Samsung Galaxy Nexus] Aerolith514:
Where can I find the beta? Wasn't on the play store
[Samsung Galaxy Nexus] xzillerationer:
I tried the beta, and while I loved it, giving me nostalgia back to my days of my old droid 2, its just too buggy(rom and keyboard) for me. And the vibrations just feel weird to me.
[Samsung Galaxy Nexus] Aerolith514:
For those of you who want to get the beta, look up SwiftKey vip on Google and sign up on their website's forums and install the beta directly on your phone after you get the confirmation email.

I'm loving it a lot of my only vendetta against SwiftKey X was that the space bar was too small. Although if I had the opportunity I'd replace the voice recognition button with a comma.
[Samsung Galaxy Nexus] zephiK:
http://xdaforums.com/showthread.php?t=1581770 apk is posted in that thread

as for me... im loving swiftkey 3, huge improvement in prediction and makes me like typing on the galaxy nexus (or even in general) a new experience.