yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] titanic_fanatic:
That means that you don't have the paths listed in your environment variables. First get the full path to your java and also for the android sdk. You need to add 3 paths in order for the cmd to be able to run the commands. Path to java jdk directory most likely c:\Program Files\Java\jdkx.xx_x where x represents your java version which should be no older than 1.6. The path to the android sdk tools and platform-tools I've installed the android sdk to program files\android do my paths look like this:

C:\Program Files\android\platform-tools

C:\Program Files\android\tools

These 3 paths will be added to your systems path. Right click on my computer then, click on properties in the context menu. Next, depending on your version of Windows, if your on Windows >= 7 I think it's advanced in the left menu. If your on Windows < 7 it opens the same pop-up window that advanced will open on the other Windows. In this pop-up window, click on the tabs until you find environment variables and click on that button. In the environment variables pop-up, you should see two panes placed one on top of the other. In the bottom pane find the variable path, I think you can double click on it to edit it. Go to the very end of the value, where all the paths are and add your three entries, separating them with a ; remember also to separate the last path that was in the values and the first path in your list with a ;.

Press ok until all the popups are gone and then close your command prompt and open it again for the changes to take effect. Type "java -version" into the command prompt. This should give you your java version, if it doesn't, something isn't right. Once java is confirmed, type adb and you should get a description of the usage of adb. If you ran both of those commands successfully, then you should use my other instructions to use adb to pull your build.prop.

Sorry for the vague information on where to find all the options, I'm not at my comp right now and doing this from memory ;)
[Galaxy S II General] chillycrow:
Almost there! Hopefully my last question, I've got adb working but it can't find the device when I run the command. When I list the devices in adb it doesn't list it there either, even though it is plugged in. I tried it while running cwm too, but that didn't work either. Any tips? Other than that it looks like it's working just fine!
[Galaxy S II General] titanic_fanatic:
Sounds like we're down to a driver issue and that's not uncommon. The easiest thing to do is to install kies. If you already have it installed, that's ok too, you can either uninstall and reinstall kies (long process) or you can open your device manager in Windows by right clicking on my computer (this is all with the phone plugged in) locate the driver for your phone, right it then uninstall. You would then unplug your phone and plug it back in and let Windows install the driver. Once the driver is reinstalled, you should see your device in the list. If android is running, you will have to have adb debugging enabled in developer options. If in cwm you should be good to go.
[Galaxy S II General] chillycrow:
Drivers are up and running, and the program works. Now how do I get it to move the file onto my computer? Because when I run a cd to move it, it doesn't transfer. I could just be putting the command in the wrong order for all I know though.
[Galaxy S II General] titanic_fanatic:
After you CD to the directory where you want to save the file, issue the following command:

I should also mention that if you're in cwm mount your system partition (an option in cwm). The adb command above will save the build.prop to the directory where you issued the command in your command prompt ;)
[Galaxy S II General] chillycrow:
Sorry to sound like a moron, but I can't seem to get it to actually save anywhere. I can run the adp pull just fine, looks like this

C:\Program Files\android\sdk\platform-tools>adp pull /system/build.prop build.prop

However, as soon as I add a cd to save somewhere else it either doesn't work or runs the adp list all over again. I don't consider myself a programmer/developer or the like, but there must be something missing somewhere.
[Galaxy S II General] titanic_fanatic:
The cd is only to change to the directory where you want to save the file. That is done first, and in your example above your in the platform-tools dir of the android sdk which is fine. Running the command from that directory should save the file to that directory. So your command will look something like the following:

Notice how the cd command is performed on its own and is also the first command to issue ;) in my example above, the build.prop file would be here:

EDIT:

Also just want to make sure that when you wrote adp that was a typo right? It's adb ;)
[Galaxy S II General] chillycrow:
What type of file does it save as? Because I can run the file but it doesn't show up where I send it to.
[Galaxy S II General] titanic_fanatic:
The filename will be build.prop and it's just a text file you can open with any text editor.

Once you run the adb pull command you should see the transfer speed and also the filesize of the file transferred. On my device this looks like the following:

If you see something similar to the above after you run the adb command, the transfer was successful. The path visible in your command prompt when you run the command is your save location and the file should be named build.prop.
[Galaxy S II General] chillycrow:
GOT IT! I could get it when I saved to my desktop, it didn't show up anywhere else I tried. Here you go! I had to convert it to a word file to attach it, hope that doesn't mess things up.
[Galaxy S II General] titanic_fanatic:
Perfect... I see that it's definitely not a problem with the model in your build.prop, so I've re-read all our messages, and think I might have a solution. Go into CWM and select "Install zip from sdcard" you should then see an option for "Toggle signature verification" select it and at the bottom of the screen it should say "Signature Check: Disabled". If it says "Signature Check: Enabled", it was already disabled so select it again to disable it again and try flashing the rom again. I'm pretty sure that it's currently enabled though and that's why you get a signature verification failed ;)

Essentially, we don't want cwm to check the package signature as we want to flash custom firmware which will not have this required signature.
[Galaxy S II General] chillycrow:
I don't have that toggle, it's probably a part of the cwm I couldn't flash for the same reason.
[Galaxy S II General] titanic_fanatic:
So you must not be running the cwm from dadoes page. Go to dadoes page download the cwm tar file and flash that from Odin. This cwm had the correct options.
[Galaxy S II General] chillycrow:
Everything works! Thanks a ton!
[Galaxy S II General] titanic_fanatic:
So glad you got it working ;)
[Galaxy S II General] chilli1327:
Unroot not working

I am trying to unroot my phone. Of course it is the Bell SGH-I757M and the unroot is not working. I got all the right files, but when I boot into the setup, it keeps saying that the system files have stop working and I cannot proceed with initial setup and I have to use Odin to re install CWM and re flash 4.1 Jelly Bean and that works. I want to go back to factory fresh but I am unable to. Odin says everything passes, but no luck. This is the file I am flashing to go bact to factory: I757MUGLCA_I757MOYCLCA_I757MUGLCA_HOME.tar.md5.

HELP!!!!!
[Galaxy S II General] Michaeljwjr:
Nothing works

My phone won't start. It loads directly into the CWM-based Recovery v5.5.0.4 (ported by dsixda) screen. It will not boot into Android.
[Galaxy S II General] titanic_fanatic:
This is a cwm bootloop. You just need to re-flash cwm to fix it. It usually happens if your using the touch cwm by dsixda and use the boot to recovery option from android.
[Galaxy S II General] Michaeljwjr:
So re run ODIN? I did that and got a fail from Odin. (oh and thanks for the quick response)
[Galaxy S II General] titanic_fanatic:
Is kies running on the computer where you use Odin? If so, turn off kies as it's been known to mess with Odin. If that's not the case, are you able to use adb (java and android sdk must be installed) if so, you could try downloading a cwm flashable zip of cwm and push it to your phone using adb to re-flash cwm.

It's concerning though that Odin failed for you. That is your ultimate last resort for restoring your device.

Did you try using a different usb port with Odin? Maybe the port you used isn't providing a consistent connection.
[Galaxy S II General] Michaeljwjr:
Ok so the issue was me not putting my phone in the right state. Odin fixed me up well thank you.

The reason I in the first place had the issue was I downloaded Root Checker, and it keeps giving me the following message:

Please wait for Root Check to complete. System appears to be running very slow.

So after doing everything perfectly, I still don't have a rooted device.
[Galaxy S II General] titanic_fanatic:
Which Rom did you flash? Your recovery is rooted, you also need to flash a rooted Rom. There are now a bunch for this device including cm10.2
[Galaxy S II General] Michaeljwjr:
Oh I didn't actually have a ROM was just using Stock on the phone. Do you have a link to CM10.2? Very much appreciated.

I am a novice at most of this.
[Galaxy S II General] titanic_fanatic:
Here is the link for cm10.2:

[ROM][RECOVERY][DEV][CM10.2][SGH-I757M]UNOFFICIAL CM10.2 For Bell SGH-I757M

You could also have a rooted stock Rom, here is a link for the stock Samsung 4.1.2:

[ROM][STOCK][FLASHABLE ZIP][JB.1.2][BELL SGH-I757M ONLY] Samsung Stock Rom
[Galaxy S II General] universumetal:
I am at a standstill and can't make heads or tails of what to do, here.

There is plenty of documentation on how to use Odin but I do not have a windows machine.

I see that my issue was addressed once before, a year or more ago but the source had not been released yet so no one knew the answer.

I have heimdall and have even come across a tut on rooting S2s with it but I cannot find the appropriate image/files to use on the I757M, I can only find the image for Odin.

Is there some way I can use that image with heimdall? Or is there a known method for heimdall and the SII HD LTE that I'm seemingly too inept to locate?

I'm also having issues with heimdall detecting the phone, even with debugging on and the device in the stock recovery screen.

Any help or guidance would be greatly appreciated. I should note, in case it helps, that I don't need to retain phone functionality, I hope to run a linux distro and run a few servers off of my local network.

To that note, if there's a way I can put on a direct install of some linux distro, that would be amazing, since I've only done so with a chroot environment on previous devices.
[Galaxy S II General] titanic_fanatic:
There is a project called ubuntu touch that is intended for mobile devices but is touch enabled. I looked at it briefly and think it would take some time to port it. If it's something you want to try to port, your welcome to use my github repos for building. I'm a little busy with kk right now, but if you have any questions about building, I might be able to answer them ;)
[Galaxy S II General] silverbret12:
Help, i use galaxy s2 hd lte sgh-i757m from bell canada, android version 4.0.4, kernel version 3.0.8-perf-i757muglh2-cl869289, i can't install clockworkmod, i have done every step you show on #1 but when i enter to Recovery, that show it's not CWM recovery, it's original recovery. Help me, plz!
[Galaxy S II General] titanic_fanatic:
After you flash cwm with Odin, are you letting the phone boot into android? If so, that's why, if you let it boot into android it will rewrite the recovery. To overcome, as soon as Odin displays a green pass message, hold both the volume up and volume down button at the same time. This should boot you into recovery before it gets overwritten. Once into cwm, you need to install a rooted Rom :)
[Galaxy S II General] silverbret12:
Thanks so much, I'll try it again.
[Galaxy S II General] windrose:
Hello,

I can' t seem to get this to work. I hope people still frequent this thread even though it is somewhat an outdated phone.

I've tried doing what you wrote here but I can't get CWM to load, I am holding down volume up and volume down but it just boots up like normal, I don't even get the stock recovery. However it does say "safe mode" when it boots up. Has this problem ever occurred for anyone else?

EDIT:

I figured it out. The original quote above was confusing but I found your newer post which was much clearer in instructions.
[Galaxy S II General] KilluaGaming:
can you give me a download link for cwm recovery, and custom rom? all of the download links seems like they don't work anymore
[Galaxy S II General] markdexter:
Oh..... Sorry didn't even see it!!
[Galaxy S II General] dsixda:
Ok, I've updated CWM to a new version, 5.5.0.4a. Please see change log for details.

The good news is that I was able to compile an ICS kernel that actually boots. This means CM9 is possible in the future.
[Galaxy S II General] markdexter:
So we just flash this with Odin, does this mean we will be using an ics kernel with a gingerbread rom?
[Galaxy S II General] dsixda:
Flash as you would before, with Odin. It's an ICS kernel in a *recovery image*, not in a ROM's boot partition. Your ROM still has GB kernel.

This is mainly a proof-of-concept, to see that an ICS kernel can actually boot.
[Galaxy S II General] B.Moreira:
I can just flash this over the original CWM that you made right?
[Galaxy S II General] dsixda:
Yes
[Galaxy S II General] stickus:
Thanks for all your hard work on this! I've been trying to flash it with Heimdall, but I can't seem to get Heimdall to recognize my device. I don't run Windows on any of my machines at home (2 Linux boxes and a MacBook), so Odin isn't really an option for me. Any suggestions to making the sgh-i757m get recognized in Heimdall? If not, I guess I'll have to co-opt a friends Windows machine to get this done. Thankfully, once I get CWM on there, the rest is easy peasy.
[Galaxy S II General] dsixda:
No luck here either with Heimdall. Try to flash the rooted stock image and use adb to flash the recovery.img file inside recovery.tar. You'll find the adb instructions at the Galaxy Note SGH-I717 CWM thread.
[Galaxy S II General] B.Moreira:
Do you know if it's possible to flash roms from other GSII variants to this phone? Such as the i727m. Or is it just not possible due to the lack of software for this phone.
[Galaxy S II General] dsixda:
No, because they're not 720p resolution and more than likely have a different touchscreen technology and/or screen panel (hence incompatible kernel).
[Galaxy S II General] B.Moreira:
Ok, i was just wondering about it because i saw a post about how to to flash i9100 roms on to the korean version of the GSII
[Galaxy S II General] stickus:
So I managed to co-opt my friends Windows computer and downloaded the files needed to do this. Took longer to download the files I needed than to actually flash everything. Smooth like a babies bottom I tell ya. Can't wait to see what you guys accomplish with CM9. :D
[Galaxy S II General] lgsshedden:
Thanks for all these efforts: my daughter's I9000 was fatally damaged and it was smarter to replace than repair -- Bell has the 757 in stock as of today and she has one now.

Just downloaded your files and will check Dex's custom rom thread directly.

Will post the ICS update if and when Bell follows through on the promised update.
[Galaxy S II General] sorg:
Hi, dsixda

Can u give me function to reset recovery flag? I wanna make CWM for Asian S2 HD.
[Galaxy S II General] dsixda:
I don't know how to do that, I just made an ICS kernel and it automatically fixed the reset problem.
[Galaxy S II General] sorg:
ok, i see.

Thanks for info.
[Galaxy S II General] jonnyjb:
I have gotten several times "back button has been disabled" and when i try to select something with the power button it turns off the screen, have you seen this before?
[Galaxy S II General] dsixda:
This is normal CWM behaviour, just google the problem and you will see if you press the Down Volume button a few times the functionality gets disabled.
[Galaxy S II General] markdexter:
Hey there Dsixda, wondering if you may now how to modify this update script to allow our devices to have a superwipe script?

To nervous to try this, since you have the Rom Kitchen you may have a much easier time than me!!

I took it from the HTC sensation site, Recognised developer mike1986
[Galaxy S II General] dsixda:
Na, I'm busy enough with CM9 already, I don't feel like doing anything else. Feel free to search the Root I757 thread for the mount points necessary to fix whatever is in that ZIP.
[Galaxy S II General] markdexter:
Oh ok. If the mount points are posted it will defibately help, didnt realise it was posted. Thanks
[Galaxy S II General] dsixda:
It's in Page 5 or so of that thread.
[Galaxy S II General] dsixda:
Hi guys, I've updated CWM just now. Hopefully that helps with the SD card flashing issues experienced by some people.
[Galaxy S II General] jonnyjb:
OH I'm so excited i hope this works I Miss ICS SO MUCH....

THANK YOU for all your hard work!!!

i hope you had a wonderful long weekend.

cheers
[Galaxy S II General] dsixda:
Don't get your hopes up too high :-D It's just a shot in the dark. I was looking at the SD driver config and noticed one value was overlooked, even though it was enabled in 2.3 and also in the ICS ROMs for other S2 devices.
[Galaxy S II General] jonnyjb:
Ya it was working but then i plugged it in to power and all was lost.
[Galaxy S II General] dsixda:
Unplug power, hold down the power button for a few seconds to restart.
[Galaxy S II General] spaztiq:
Could someone post a mirror of "root_sgs2hdbell.zip"? Dev-Host has been transferring this tiny file to a new server for a while now, and I am unable to download it because of that. Figures the moment I want to root, something goes funky.
[Galaxy S II General] dsixda:
Check my response in the cm9 thread.
[Galaxy S II General] hhcat:
Hi dsixda, this is great work!

I am trying to port to Korean Galaxy SII HD LTE phone.

Could you share the tool you used to pack and unpack recovery.img?

I search on internet and got the tool bootimg-tools.

Following the instruction, I failed at the step:

gzip -dc ../recovery.img-ramdisk.gz | cpio -i

Error messages like:

cpio: xxx not created: newer or same age version exists

And there are no files extracted.

Could you please help?
[Galaxy S II General] dsixda:
I'm just using the msm8660 sources for kernel, as well as CM9 sources for recovery image. See my GitHub for instructions (kernel and device folders).

EDIT: You can also use my Android Kitchen, under Advanced Options, option #20 (to extract and re-pack a boot.img/recovery.img).
[Galaxy S II General] hhcat:
Thanks for the answer.

I am reading your instructions. It require to get CM9 code and compile from the scratch.

I am thinking of whether I could do in alternative easy way that just unpack your CMW recovery for i757, replace .ko module, replace fstab and then repack. :)

One more question, what is the base address?

I looked at hex content of recovery.img, it looks like 0x40400000, is this correct?
[Galaxy S II General] dsixda:
That's the address for my device, but I'm not sure if your device has the same address.. you'll need to look at a stock boot.img or recovery.img to be sure.

You don't need the .ko module.. it's a recovery image so its kernel doesn't rely on modules like a kernel in boot.img does (required for wi-fi, bluetooth, etc.).

For building the recovery image, just replace my BoardConfig.mk to match yours (in the device folder).

Also, for the kernel, replace "cyanogenmod_celoxhd_defconfig" with the defconfig that comes with your stock ICS:

- you can grab it from from the Samsung opensource site, OR:

- grab the file /proc/config.gz while your phone is on, extract the config file, and rename it so that it ends with "defconfig".. e.g. "SHV_120L_defconfig"

Then follow instructions in my device_celoxhd github to do the "makerecoveries.sh".
[Galaxy S II General] hhcat:
I enabled cwm recovery for e120s. :)

One monor issue, adb is not enabled in recovery.

Is this the expected issue or I might miss certian step?
[Galaxy S II General] dsixda:
Congratulations, how did you do it?

I don't know how to enable adb, it might be set in the rc files or default.prop?
[Galaxy S II General] hhcat:
I didn't find out how to enable adb in reocvery.

I have tired the following steps but did not succeed:

*set persist.service.adb.enable=1 in default.prop

* in init.rc:

service adbd /sbin/adbd recovery

enabled

The investigations are still on-going...
[Galaxy S II General] dsixda:
I don't think mine does adb either, I don't remember.

So did you build from source?
[Galaxy S II General] stronixs:
home button don't work

Very useful recovery, thanks:) But on my i757m don't work the Home -> Up button. In advanced menu key test show that menu = 139, home = 172, back = 158, search = 217. It's not deadly, but uncomfortably. What is the problem? Any advice?:confused:
[Galaxy S II General] dsixda:
Same here.. I don't know why.. maybe it was disabled on purpose. Just use the volume keys.

BTW the keys are defined under /system/use/keylayout/melfas_touchkey.kl. In the code it checks for KEY_HOME, but ours has it defined as just HOME. Not sure if that's the issue there
[Galaxy S II General] B.Moreira:
I managed to build a rom on 2.3.6 from stock using your kitchen :)

It booted the first try! Would you want it on your dev-host files?

It just has root, busybox, de-odexed, zip-aligned, and all bloatware/useless apps removed.
[Galaxy S II General] dsixda:
Well, if you used the kitchen with the usual canned options then yes it will always boot.. But glad to see you managed to install the kitchen successfully. No, I'm not interested in someone else's custom 2.3 ROM, but we already have a couple other ROMs with those options enabled.
[Galaxy S II General] B.Moreira:
Ok I wasn't sure if you wanted other people's roms or not.
[Galaxy S II General] dmeinder:
Thanks for the root help....but after performing the OP steps, when I load up Titanium BU, i get the message "rom is rooted but su binary has non-optimal access" (or something like that.

Is this method super su?

If not is that ok?

Did I even ask the right questions above? (haha)

Thank for you help!
[Galaxy S II General] dsixda:
Which ROM are you using?
[Galaxy S II General] dmeinder:
Using stock rom rooted as per directions. I got it sorted out.... Thx
[Galaxy S II General] dsixda:
How did you sort it out?
[Galaxy S II General] dmeinder:
I allowed TB to set the required value.... All is good now
[Galaxy S II General] jonnyjb:
was this hard to port? I think i remember you having some issues in the beginning, the reason i ask is because there is the new 6.0 touch or regular CWM and it is supposed to be really really good a lot faster and more stable, i was trying to Google how to do it but haven't had any luck (plus my source skills are rather lacking), would it be hard to port the new one over to this? Just a thought I would bring it to your attention if you haven't already seen it. anyways again you have done awesome things here thanks for all your hard work.

cheers.
[Galaxy S II General] dsixda:
I'm going on vacation in a couple of days for 2 weeks but when I come back I might look at it. I thought it was beta right now, however.
[Galaxy S II General] jonnyjb:
Awesome man. Have a Great vacation.. hope you enjoy it. i updated my wife's (my old phone) and it jumped to the 6.0.0.2 or what ever it is. it was a SGS i9000 and bam its there. so when ever what ever if it never happens, meh, you have done a tun for us with this phone. so thank you again and have an awesome vacation.
[Galaxy S II General] milococo:
Odin file analyze and CRUSH every time

you didn't specified what must tick on Odin and what not. In 1.85 are many choose like repartition phone efs clear, phone boot loader update, etc. And it's on bootloader or in PDA

thanks