Develop Bugs

CWM Recovery using old version?

The hacked kernel with CWM recovery posted here:
http://forum.xda-developers.com/showthread.php?t=1268037
Seems to be from build EB30, but my phone came with build EG30. Why the difference, and is EB30 safe to use?

psusi said:
The hacked kernel with CWM recovery posted here:
http://forum.xda-developers.com/showthread.php?t=1268037
Seems to be from build EB30, but my phone came with build EG30. Why the difference, and is EB30 safe to use?
Click to expand...
Click to collapse
All current versions of CWM are a little iffy. We won't have total stability until we get an official build that's flashable via ROManager.

Ahh, so it is a known bug that the one from rom manager doesn't work? It seems to reboot into the stock samsung recovery to install itself, and that obviously refuses to install the image because it isn't signed. Isn't the ROM manager supposed to replace the stock recovery with CWM recovery and reboot into that instead?

psusi said:
Ahh, so it is a known bug that the one from rom manager doesn't work? It seems to reboot into the stock samsung recovery to install itself, and that obviously refuses to install the image because it isn't signed. Isn't the ROM manager supposed to replace the stock recovery with CWM recovery and reboot into that instead?
Click to expand...
Click to collapse
Yeah, ROM Manager doesn't support the E4GT yet. Some of the devs have managed to compile custom versions of CWM for us to use but with no integration with ROM Manager.
To answer your first question I think EB30 was just a typo. it is supposed to be EG30.

How I flash newest ICS (FC15) from previous build

I feel like one of my daily job is flashing new ROMs these days.....
Any way, we are getting lots of ROMS that we can flash with different methods.
Because I'm flashing the ROMs almost every day in these days, I just wanted to share some information how I do my daily job. (Lot's of Devs are flashing the Roms with their own ways but I believe the general concept is same and we are always trying to avoid the 'bricks' caused by wrong direction.
In here, what I'm doing is my safest way and I never failed with this method but please do this with your own risk if you want to follow this guide. There are tons of other guide and directions that you may also want to consider.
[Most important thing is, you must follow ROM publisher's instruction first. The information in here is the way what I'm doing day to day basis. So, it may not work based on your situation. Don't blame be if you phone bricked]
* Flashing Calk rooted Stock Rom
1. if you don't have the Modified CWMRecovery kernel something like Rogue Recovery Kernel, before following this guide, you need to download 'it' first.
For me, I use Rogue's FB27 recovery Kernel until another newest stable version comes out. You can download it from
http://forum.xda-developers.com/showthread.php?t=1390393
If you use the .tar file, then I assume that you already have a odin executable in your pc (.tar file in you pc) or mobile odin in your phone (.tar file in your sdcard).
Or if you use the zip file, you need to be sure that you are able to install the zip file through the recovery (zip file in your sdcard).
2. download Calk's rooted stock Rom and place into your sdcard (or external SD).
Most recent Calk's rooted stock Rom can be found at
http://forum.xda-developers.com/showthread.php?t=1552117
Modem file also needs to be required if you want to install the modem at the same time when you flash his rom. If the modem tar file available from other Dev's post, you can flash the modem later or before the flashing his rom thru odin or mobile odin.
3. Be sure that you already have nandroid backup of your current rom or make the nandroid backup before flashing his rom.
4. Check if there's any stock kernel available. If there's no separate kernel available, you need to extract zImage file from Calk's zip file and save to sdcard (for mobile odin) or to PC (for odin). If you want to keep the current Recovery Kernel, you don't need this step.
5. Now I assume that you have all the files ready and placed those to the right places. If your current kernel is not Rogue's, then install his recovery kernel. For me, I use mobile odin and pick it up from sdcard.
After installation, phone automatically reboot. Before the first screen comes out, press vol up + power keys at the same time. It will bring you to the Rogue CWM recovery screen.
6. From recovery screen, select install from zip and point the Calk's zip file you saved. Select and install it.
7. If you want to install the modem at the same time, do the same thing as step 6 but choose the modem zip file. There's no special sequence between step 6 & 7. Anything can be installed first. If you don't have modem zip file but have modem tar file, modem can be installed later. Or you can install the modem first before starting all these steps.
8. reboot
9. The kernel went back to stock kernel. So, if you need to do some recovery task, you need to start from step 5. One example is, if you want to run Calk's Bare Rom converter tool but you missed doing it after installing the ROM, then you need to install the Rogue recovery Kernel again. Usually Rogue Kernel is behind of current Kernel. But don't worry about coming back after the recovery task. This is the reason why I added step 4 above.
Additional steps coming back to current Kernel after the Recovery Task -
1. Install Rogue Recovry Kernel (usually previous kernel version)
2. Reboot and do the recovery task (backup, running Bare Rom converter zip file, cleaning data/dalvik cache, format battery stat, etc).
3. Reboot
4. if you use mobile odin, then install the zImage file or any kernel that you want.
If you use odin, go to the download mode by pressing vol down + power button together and install the kernel.
- if the kernel zip file is also available, then you can skip the steps 3 and 4. Just after the step 2, install the kernel zip file and reboot.
* Flashing ODIN/TAR rooted stock Rom
The basic idea is same to flashing Calk's ROM.
The most recent Stock rooted odin/tar file can be found in http://forum.xda-developers.com/showthread.php?t=1551901
1. if you don't have the Modified CWMRecovery kernel something like Rogue Recovery Kernel, before following this guide, you need to download 'it' first.
For me, I use Rogue's FB27 recovery Kernel until another newest stable version comes out. You can download it from
http://forum.xda-developers.com/showthread.php?t=1390393
If you use the .tar file, then I assume that you already have a odin executable in your pc (.tar file in you pc) or mobile odin in your phone (.tar file in your sdcard).
Or if you use the zip file, you need to be sure that you are able to install the zip file through the recovery (zip file in your sdcard).
2. download odin/tar file. For me, I use sfhub's one-click self-extractor package.
To install this ROM into your phone, please read his instruction carefully. In his package, you can install everything with just one odin or you can install modem/kernel/rom separately. Also, there are two packages available, one is for whom don't want the old data, and another one is for whom want to keep the old data.
3. after the odin finished, phone restarts automatically. Now you have the new ROM installed on your phone but there's no modified recovery Kernel. To do the recovery task, you need to follow the steps in 'Additional steps coming back to current Kernel after the Recovery Task'.
Important - if you don't know what you are doing, please be sure that you know what you are doing before doing anything by asking your questions to someone! There would be someone who can help you about your questions but there's no one who is responsible for your bricked phone!

[SGH-I747/M] CF-Auto-Root

Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) !
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 8 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery
Installation and usage
Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home).
Using this root increases your flash counter. You should run Triangle Away (see below) after rooting to reset the counter. Note that if you want to run custom kernels or custom recoveries, your flash counter will be set to 1 at every boot. Either configure Triangle Away to reset the counter at every boot (Play version only) or only reset the counter when you need to go into warranty.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
No CWM and such ?
I have personally moved away from permanent custom recoveries, and I am no longer supporting them. On newer devices they cause flash counter and OTA flashing issues. If you really want one, others do provide versions of CWM and TWRP for most devices. Personally I just use Mobile ODIN to install ZIPs and Titanium Backup for my backup/restore needs. I do always want root though, and as such I'm still supporting CF-Auto-Root as quick way to root.

ODIN Installation (detailed)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
You may now optionally want to install and run Triangle Away to reset the flash counter.

Download
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download:
SGH-I747: CF-Auto-Root-d2att-d2uc-samsungsghi747.zip
SGH-I747M: CF-Auto-Root-d2can-d2vl-sghi747m.zip
--- History ---
2013.05.20: SuperSU v1.30
2013.02.20: SuperSU v1.05
2012.12.02: SuperSU v0.98
2012.10.30: SuperSU v0.96

Stupid noob question time....will this also work for the SGH I-747M also? Pretty much the same phone but just to be sure. I only ask because there will be alot of Canadian users in this forum seeing this and wondering.

Added I747M version, should work for Rogers, Bell and Telus.

Looks great for people who want to keep on stock but have more control.

Thanks nothing else would root friends phone and this worked first try
Sent from my SGH-I747 using xda premium

Used this when I had the international S3, worked great for easy root.
Sent from my SAMSUNG-SGH-I747 using xda premium

I'm so glad to see CF-Root for our devices. :laugh: I'm already rooted and using a AOSP rom but still nice to see.

Hey man....Nice seen you here!!! Love your work on my International SG 2.....Thanks for your work here!!! Simple question....does it matter if i use the Odin 3.07 that is been ad for GS3 on the forums or the one that you attached, 3. 1.85??? My guess is no but to be sure!!!
Nevermind...Same thing!!!

Out of curiosity, is Mobile ODIN essentially the same as ROM Manager but for stock recovery? Can you flash AOSP builds, modems, kernels, or anything while just using Mobile ODIN?

Sir_Brizz said:
Out of curiosity, is Mobile ODIN essentially the same as ROM Manager but for stock recovery? Can you flash AOSP builds, modems, kernels, or anything while just using Mobile ODIN?
Click to expand...
Click to collapse
Mobile ODIN is like a mobile version of desktop Odin. Meaning that you can flash tars in the PDA slots. Unsure...someone could give a more thorough explanation... I don't use it.
Sent from my SGH-I747 using xda premium

Sir_Brizz said:
Out of curiosity, is Mobile ODIN essentially the same as ROM Manager but for stock recovery? Can you flash AOSP builds, modems, kernels, or anything while just using Mobile ODIN?
Click to expand...
Click to collapse
Mobile ODIN can flash Samsung's stock files (entire stock firmwares, modems, kernels, recoveries, etc etc in img/bin formats) as well as ZIP files (modems/kernels/customfirmwares in "CWM" format), yes.

Chainfire said:
Mobile ODIN can flash Samsung's stock files (entire stock firmwares, modems, kernels, recoveries, etc etc in img/bin formats) as well as ZIP files (modems/kernels/customfirmwares in "CWM" format), yes.
Click to expand...
Click to collapse
Really? So how would you go about installing a custom ROM through mobile odin.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Erazo1986 said:
Really? So how would you go about installing a custom ROM through mobile odin.
Click to expand...
Click to collapse
Well, it does require Mobile ODIN Pro, but you can just "Open file ..." or "OTA / Update ZIP" on a CWM ZIP file and it'll install it...

Thanks a lot Chainfire ! Worked on my GS3 Rogers without a problem

sorry if i missed it somewhere, but is this going to wipe my apps and data?

ShadowVlican said:
sorry if i missed it somewhere, but is this going to wipe my apps and data?
Click to expand...
Click to collapse
I don't believe it does.
Sent from my SGH-I747M using xda app-developers app

Any future plans to support At&t 747?

dlbjmb35 said:
Any future plans to support At&t 747?
Click to expand...
Click to collapse
maybe try reading the OP and you'll have your answer.
Sent from my SGH-I747M using xda premium

[Q] Flashing a new kernel

My Google-fu is lacking tonight. Having built myself a new kernel, how do I flash it onto the phone? (either straight from the root commandline or in CWM - I don't really want to have to find a Windows machine for Odin). All the "how to flash a custom kernel" guides out there seem to assume you want to install a kernel that someone else has already packaged for you...
Secondly, if it all goes wrong and the kernel won't boot, am I right in thinking that CWM will still work and I can just recover my old image using nandroid?

Go here
http://forum.xda-developers.com/showthread.php?t=2067896
Download the kernel, open in 7zip or winrar, delete boot.img and replace with yours and flash away.
Sent from my SGH-I927 using xda premium

Excellent, thank you! I now have a kernel with CONFIG_USB_SEC_WHITELIST turned off so I can use any USB device with the phone.

[ND8] 4.4.2 knox removal and root

Hi all I have found a way to root and remove Knox from stock samsung galaxy s3 ND8 4.4.2 kitkat
** neither me or xda is responsible for any **** ups you cause so read and follow directions to a T lol
*Requirements
Samsung drivers
Download from samsung site
CF auto root
http://download.chainfire.eu/233/CF-Root/CF-Auto-Root/CF-Auto-Root-d2spr-d2spr-sphl710.zip
Choose the right one depending on your device
Windows computer
Know how to follow directions
Time and patience
Instructions
Once all the files are downloaded extract Chainfire's CF auto root
Move the desamsungnizer and the superuser app to your SD card
Next open Odin
Reboot your phone to download mode for people who don't know how to power off the phone and press volume down home and power then press volume up to confirm
Make sure auto reboot and repartition is not checked
Click PDA and select the recovery image When your phone is connected press start and let it flash
Once complete remove your USB cord and battery put battery back in after a few seconds and reboot to recovery (volume up+home+power)
Choose install zip from sd card and choose the supersu Zip file
Confirm flash and then flash the desamsungnizer file
After complete reboot phone it may day android is upgrading when the phone fully powers on go to manage appliations and go to all and scroll down and see if you see super su if so then all went well if not retry from odin step
OK next go to the play store and download root checker superuser update fixer
superuser
Root checker
terminal emulatoremulator
Nobloat free
Ok open up superuser update fixer and force fix the binary and you should get a root request popup agree and close the app open terminal emulator and type the following lines
su[enter]
pm disable com.sec.knox.seandroid
*NOTE - the above to lines require you to go to a new line after typing "su", the [enter] is only a reminder, DO NOT type [enter] after su
This disabled KNOX for me - but that wasnt good enough for me - I was out for blood at this point.
I then used NoBloat free to remove any of the left overs of knox
Also for a custom recovery just download team win recovery project
Now you're good to go to flash ROMs and whatever else you would like to do
Also I apologize for the thread look this is my first time creating one
Special thanks to
Chainfire
Teamwin

Can you link to the desamsungnizer and SU files you used? I have TWRP on my S3 w/ ND8 but flashing the desamsungnizer and su ZIP files that I have that worked with MK3 do not work with ND8.

scottlindner said:
Can you link to the desamsungnizer and SU files you used? I have TWRP on my S3 w/ ND8 but flashing the desamsungnizer and su ZIP files that I have that worked with MK3 do not work with ND8.
Click to expand...
Click to collapse
All recoveries except the very latest Philz Touch Recovery are known to have problems under ND8 / NDC.
You can find the ND8 deknoxifier (only for apps, not Bootloader) and debloater either in Development (non original), General or Themes and Apps - can't look right now.
For SuperSU.zip, just Google it and you'll find Chainfire's site or just use Philz Touch Recovery's option to reroot your phone.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

http://forum.xda-developers.com/showthread.php?t=2507931

Will this take away the flash count?
Sent from my SPH-L710 using Tapatalk

No it does not take away flash count and use philz touch recovery when you first flash desamsungnizer and supersu sorry forgot to mention
Sent from my d2lte using XDA Free mobile app

I must be missing a step somewhere. When I odin the chainfire tar.md5 file, I see RESET instead of PASS. Also when I reboot into recovery, it reboots after 10 seconds, while reinstalling the stock recovery. I get no chance to flash anything else. Can I flash these other files from Odin? If so, in which area (e.g. PDA) of Odin do I place the files
(Sprint SPH-L710 with stock ND8)

Moritzio said:
I must be missing a step somewhere. When I odin the chainfire tar.md5 file, I see RESET instead of PASS. Also when I reboot into recovery, it reboots after 10 seconds, while reinstalling the stock recovery. I get no chance to flash anything else. Can I flash these other files from Odin? If so, in which area (e.g. PDA) of Odin do I place the files
(Sprint SPH-L710 with stock ND8)
Click to expand...
Click to collapse
Flash Philz Touch Recovery in tar.md5 format from Odin. Reboot into recovery and in one of its menus is an option to reroot.
Then flash everything else from Philz.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

roirraW "edor" ehT said:
Flash Philz Touch Recovery in tar.md5 format from Odin. Reboot into recovery and in one of its menus is an option to reroot.
Then flash everything else from Philz.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Thanks, that worked. Should this information be part of the first post?

Moritzio said:
Thanks, that worked. Should this information be part of the first post?
Click to expand...
Click to collapse
Glad it worked! There was already a more complete (no offense, OP) thread for this here http://forum.xda-developers.com/showthread.php?t=2750846, but yes IMHO it should be in the OP.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.