Related
Hello all,
I recently bought a Captivate (batch 1106) that comes with Froyo 2.2 and UCKB2. Since it has a 3e recovery menu, I've followed with great interest all the threads about changing this recovery menu into something "flashable". Finally, I followed the method in this thread and installed a modded version of the 3e recovery that allows me to flash kernels, roms, install CWM recovery with ROM manager, etc. The funny thing is that since I've done this, I can access two different recovery menus at will: if I use the three button click, I get the modified 3e Samsung recovery menu; however, if I reboot into recovery menu using ROM manager, I get the CWM recovery menu installed by ROM manager. This also happens even when I flash a custom kernel with cwm recovery (such as Speedmod): in that case, the 3 button click gets me into the CWM menu installed by the kernel, whereas the ROM manager one gets me into the recovery installed by ROM manager.
The truth is that I'm quite happy with this, since it lets me choose between different recoveries. However, as I haven't seen anyone mentioning this behavior anywhere in the threads I'd like to really understand what's going on. Therefore, any help or ideas would be really appreciated. Thanks in advance.
Best,
Angel
ajgausa said:
Hello all,
I recently bought a Captivate (batch 1106) that comes with Froyo 2.2 and UCKB2. Since it has a 3e recovery menu, I've followed with great interest all the threads about changing this recovery menu into something "flashable". Finally, I followed the method in this thread and installed a modded version of the 3e recovery that allows me to flash kernels, roms, install CWM recovery with ROM manager, etc. The funny thing is that since I've done this, I can access two different recovery menus at will: if I use the three button click, I get the modified 3e Samsung recovery menu; however, if I reboot into recovery menu using ROM manager, I get the CWM recovery menu installed by ROM manager. This also happens even when I flash a custom kernel with cwm recovery (such as Speedmod): in that case, the 3 button click gets me into the CWM menu installed by the kernel, whereas the ROM manager one gets me into the recovery installed by ROM manager.
The truth is that I'm quite happy with this, since it lets me choose between different recoveries. However, as I haven't seen anyone mentioning this behavior anywhere in the threads I'd like to really understand what's going on. Therefore, any help or ideas would be really appreciated. Thanks in advance.
Best,
Angel
Click to expand...
Click to collapse
Most custom kernels use the kernel itself to provide recovery. It's possible that ROM Manager is actually booting your phone into the recovery partition. I noticed that flashing the recovery partition with random stuff has no impact on the standard recovery mode.
Right, the cwm recovery from rom manager is contained in an update.zip that does not stick once the recovery session is over. It's in.the root directory of your sdcard, you don't need rom manager anymore just 3 button into stock recovery and reinstall packages twice and it will boot into cwm. If you're on a stock kernel. Otherwise cwm will be baked into any custom kernel.
AdamOutler said:
Most custom kernels use the kernel itself to provide recovery. It's possible that ROM Manager is actually booting your phone into the recovery partition. I noticed that flashing the recovery partition with random stuff has no impact on the standard recovery mode.
Click to expand...
Click to collapse
studacris said:
Right, the cwm recovery from rom manager is contained in an update.zip that does not stick once the recovery session is over. It's in.the root directory of your sdcard, you don't need rom manager anymore just 3 button into stock recovery and reinstall packages twice and it will boot into cwm. If you're on a stock kernel. Otherwise cwm will be baked into any custom kernel.
Click to expand...
Click to collapse
Thanks very much for your replies. OK, so I think I understand: I still have my modded recovery file in the recovery partition after going back to stock kernel. The recovery menu I see when using rom manager is the temporary one contained in the update.zip.
Actually, I think I won't flash/reinstall the update.zip package just yet, since I'm quite happy with being able to choose the recovery menu I want (in case I need to return/exchange the phone under warranty).
Thanks again for your help.
Angel
When you flash the update.zip by reinstalling packages twice, it's still temporary. That's exactly what rom manager does, just in the background so all you see is cwm.
Once you have the update.zip on your sdcard you can ditch rom manager and just choose reinstall packages every time you want cwm.
Maybe it has something to do with this...
Code:
Uncompressing Linux...................................................................................................................................................................................
[ 0.000000] copy: bad source 0
[ 0.000000] mout_audss: bad source 0
[ 0.090142] KERNEL:kernel_sec_get_debug_level_from_boot=0x574f4c44
[ 0.094877] KERNEL:magic_number=0x0 DEBUG LEVEL low!!
[ 0.099895] (kernel_sec_set_upload_cause) : upload_cause set 0
[ 5.833835] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
sh: can't access tty; job control turned off
$ [ 11.433364] init: no such service 'bootanim'
[ 24.851663] init: sys_prop: permission denied uid:1000 name:wifi.interface
[ 35.227503] init: no such service 'bootanim'
[ 38.484304] init: sys_prop: permission denied uid:1000 name:dpm.allowcamera
su
sh: can't access tty; job control turned off
# dmesg|tail
<4>[ 47.443068] [email protected]
<4>[ 51.363390] mook - wm8994 TTY Off
<4>[ 51.666438] eth0: SIOCSIWSCAN : ISCAN
<4>[ 51.667822] +++: Set Broadcast ISCAN
<4>[ 53.013468] [email protected]
<4>[ 54.447852] Send Event ISCAN complete
<4>[ 54.448053] eth0 wl_iw_iscan_get_scan buflen_from_user 8192:
<4>[ 54.448067] eth0: SIOCGIWSCAN GET broadcast results
<4>[ 54.448111] wl_iw_iscan_get_scan return to WE 803 bytes APs=3
<4>[ 84.445803] wl_iw_set_ss_cache_timer_flag called
#
This is from a Samsung Infuse. You can see that at one point it makes a reference to '/system/etc/install-recovery.sh' whichi is obviously a linux shell script called early in the booting sequence (5 seconds). Possibly CWM is writing a script to call recovery to that file and as the last command, deleteing itself.
Thank you all for you help with this issue.
Angel
This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and ClockWorkMod recovery
THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THE ENTIRE FIRST FEW POSTS!
Donate
There have now been nearly 1.000.000 downloads of CF-Root for various devices (see for example Galaxy S1, Galaxy Tab 7", and Galaxy S2), and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user had donated me $1...
Main features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Root
- Busybox v1.19.2-cm71
- ClockWorkMod Recovery 5
- CWM Manager (see below for more detail)
- Custom boot / init scripts
- Custom boot animations
v5.3 and newer
- SuperSU (replaces Superuser)
- "Fake-secure" (ro.secure=1, but ADB is patched to run as ro.secure=0)
v5.5 and newer
- CWM updated to v5.5
v5.6 and newer
- Possible brickbug fix
Installation instructions
Please see the next post !
Other kernels
Replacing CF-Root with other kernels and vice-versa sometimes works, sometimes it doesn't. I don't have a list.
When going from CF-Root to another kernel, root will usually stay, while CWM will be lost (unless the other kernel also includes it), but there should not be issues. The CWM Manager app may remain, but probably won't do anything useful.
ClockworkMod
CF-Root includes a custom version of CWM5. I always make custom versions, as the originals often do not take some Samsung specific things into account.
CF-Root/CWM5 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly or using the CWM Manager application included with CF-Root
- Booting into recovery will immediately give you CWM. The standard recovery will only be started if a Samsung package is detected.
- ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery.
CWM Manager
Because of incompatibilities with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011). You can find it under Applications -> CWM. It is much faster to use than manually booting into CWM and selecting these options.
Features:
- Boot to ClockWorkMod Recovery
- Boot to Download mode
- Reboot normally
- Backup firmware
- Restore backups (including partition selection)
- Delete backups
- Install APKs
- Flash CWM3/4/5 update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP)
--- without changing warning triangle status or increasing flash counter
- Flash complete firmwares (seperate files as well as .tar and .tar.md5 archives, dump files in /sdcard/external_sd/firmware folder)
--- without changing warning triangle status or increasing flash counter
--- can pre-root new firmwares during flash
Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility !
Custom boot / init scripts
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use #!)
- /system/bin/customboot.sh (busybox sh)
- /system/xbin/customboot.sh (busybox sh)
- /data/local/customboot.sh (busybox sh)
Please make sure you chown / chmod the scripts correctly so they can be executed. Pretty much root:root / 755.
Custom boot animations and binaries
CF-Root also supports custom boot animations:
- /system/media/bootanimation.zip
- /data/local/bootanimation.zip
And custom boot binaries:
- /data/local/bootanimation.bin
Installing busybox over the included version
It is possible to install a custom busybox over CF-Root v3.0 and newer. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. It is now used to make CF-Root for many devices!
Help! Which file do I use ?
Listen closely, for I will say zis only once!
Go to Settings -> About phone -> Kernel Version. Note the string present there:
2.6.35.7-N7000XXKJ4-CL641703
What matters most (KJ4) in this case, is in bold. Try to find the matching file under downloads:
CF-Root-SGN_XX_XEN_KJ4-v5.0-CWM4.zip
The XX and XEN identifiers are not that important. Usually a "KJ4" kernel is a "KJ4" kernel, and that is that. Sometimes (pretty rare) it happens there will be multiple different kernels with the same name in different firmwares, that are actually different. If this happens, they are usually only very minor changes and you should expect them to still be fully compatible. I include the "XX" and "XEN" identifiers so the very advanced users can deduce from which full firmware I have taken the kernel file.
Don't worry too much, just find the matching download and use it. What if there is no matching download ? You can ask me to make one, but I can tell you right now, I very very rarely make CF-Root's for kernels on request, unless it is the very latest kernel that has been released by Samsung. In the latter case, be sure to let me know. If there's no match and I'm not making one, try finding the closest match. You should treat "KJ4" as a number, but instead of 1-9, we have 1-9, A-Z (where A would be 10, and Z would be 35). "KJ3" is really close to "KJ4", "KF1" is not close to "KG4" at all. I hope that makes sense.
@Developers: I have noticed that doing a NANDROID RESTORE while connected to your computer AND Eclipse is running may cause the restore to fail. Eclipse automatically starts logcatting in the background, which will prevent /system from being properly restored.
Download
These are general-purpose downloads. See the posts following this one for the kernels.
Installation intructions
The Samsung Galaxy Note keeps track of the kind of kernel you are running (stock or custom) and how often you have flashed kernels. This is probably for warranty purposes. There is currently no known way to reset this counter on the SGN.
So, what we want to do is get root, busybox, and CWM, all without getting that ugly yellow triangle or updating the flash counter on our device. Luckily, CF-Root allows for all these things. The new CWM Manager even allows you to flash new firmwares and apply root to them while flashing.
We need to get rid of ODIN pretty much completely, and we can! The difficult part is getting root the first time, after that, it should be happy camping forever.
--- Chapter 1: Initial application of root ---
DO NOT USE ODIN TO FLASH THE KERNEL !
This is the annoying part. There are three different methods:
1.1. If you are already rooted
- Download the attached "InitialRootFlasher.zip" and extract it somewhere
- Download one of the CF-Root kernels, and extract it (repeat) until you end up with a zImage file
- Place the zImage file from the CF-Root kernel in the zImage folder from InitialRootFlasher
- Start "already-rooted.bat" and follow the instructions
For those needing to do this manually (Linux boxes and such), this is the important command. Place the zImage file on your phone (example: /data/local/zImage) and execute this command in a rooted shell:
dd if=/data/local/zImage of=/dev/block/mmcblk0p5 bs=4096
1.2. If you are not rooted yet: Using the zergRush exploit This method no longer works on KL* and newer firmwares!
(while it still works on our firmwares, this exploit will probably be fixed soon! Known to work on KJ1 and KJ4 firmwares)
- Download the attached "InitialRootFlasher.zip" and extract it somewhere
- Download one of the CF-Root kernels, and extract it (repeat) until you end up with a zImage file
- Place the zImage file from the CF-Root kernel in the zImage folder from InitialRootFlasher
- Start "not-rooted-yet.bat" and follow the instructions
1.3. If you are not rooted yet: Flash a modified FACTORYFS
I am providing this method just this once, for the KJ1 firmware. This is the /system part of the KJ1 firmware, modified so at first boot it will flash the KJ1 CF-Root and reboot, without getting you the yellow triangle or increasing the flash counter.
Using a newer firmware? Do this operation first, then flash the newer firmware back using CWM Manager. This is explained in Chapter 3 below.
Download: http://www.multiupload.com/YB9EL8D8O3
- Optional: flash the full KJ1 firmware first
- Unzip the file, you should get "SGN_XX_OXA_KJ1_FACTORYFS.tar"
- Make sure your SGN is NOT connected to your computer
- Reboot your SGN into "download mode" (see below)
- Start ODIN
- Click the PDA button, and select the "SGN_XX_OXA_KJ1_FACTORYFS.tar" file
- Connect the SGN to your computer
- Make sure "repartition" is NOT checked
- Click the START button
- Wait for the phone to reboot TWICE
- Done
If you do not know how to get into download mode:
- Turn off the device
- Count to 10
- Hold the "home" (the big physical button in the middle) and "volume down" buttons
- Press and release the power button (keep holding "home" and "volume down" !) to turn the device on
- You should get a download mode screen
- If it tells you to press a button to continue, do so
--- Chapter 2: Getting rid of ODIN ---
This is easy. Find ODIN, and delete it. In the future you should only need it to flash bootloaders, which probably will only really be needed one time: when upgrading from Gingerbread to Ice Cream Sandwich.
--- Chapter 3: Upgrading your firmware ---
My CWM Manager application has a full-fledged firmware flasher built in. Using the flasher from CWM Manager does NOT give you the yellow triangle or increase the flash counter.
3.1. Flashing a new kernel
This is easy. CWM Manager can flash zImage files (on any rooted kernel), zImage files inside a .tar file (only on a CF-Root kernel), and zImage files inside a .tar.zip (only on a CF-Root kernel). Note that zImage must be the ONLY file in an archive, if is is inside a tar or zipped tar.
- Put the zImage (or tar, or zip) file on your SD card
- Open the CWM Manager app
- Select "Flash kernel"
- Select the file you just put on your device
- CWM Manager will flash the kernel and reboot
If you flash a non-CF-Root kernel, you will lose a lot of functionality from CWM Manager. However, the app will (likely) still allow you to flash kernels.
3.2. Flashing a new firmware
Important: This works ONLY on a CF-Root kernel !
CWM Manager has the ability to flash firmware parts either from separate files (zImage, factoryfs.img, etc) or from .tar / .tar.md5 files that they usually come packaged in.
- Download the firmware you want to flash
- If you have a ZIP or RAR file, extract it until you have seperate files, or .tar / .tar.md5 files
- Create a folder named 'firmware' on your external SD card
- Copy the files you want to flash to this folder ( /sdcard/external_sd/firmware ). factoryfs ("system") is mandatory part at the moment.
- TIP: If you are flashing a new firmware that already has a CF-Root kernel available, put it in the 'firmware' folder as well in zImage or .tar form (NOT .zip). Select it when asked which kernel to use, then use the "Flash normally" option later on.
- Open the CWM Manager app
- Select "Flash stock firmware"
- At this point, CWM Manager will tell you about the firmware parts it has found, and which ones it will flash. It will also give you warnings about bootloaders and PIT files if those were found. If some firmware parts are present multiple times, it will ask you which file to use as source.
- If what you are flashing includes both kernel and system parts, CWM Manager will warn you about this as you are about to lose root. It will provide you with three options:
1: Keep CF-Root kernel
Keeps the current CF-Root kernel, only flash the other parts. You will not lose root or CWM Recovery. You can flash a newer CF-Root kernel later (or maybe you have already done so), see 3.1 above.
2: Pre-root system
Flashes both kernel and system parts, but roots system during the flash. You will lose CWM Recovery, but you will keep root (if all goes well). The CWM Manager application will also remain, and allow you to flash the correct CF-Root kernel at a different time (if you have not done so before), see 3.1 above.
3: Flash normally
Doesn't do anything specific. If the kernel you are flashing is not a CF-Root (or similar) kernel, you will lose root, and CWM Recovery.
- CWM Manager will reboot into CWM Recovery, and will flash the firmware, rebooting afterwards.
--- reserving another post ---
Downloads
See the second post of the thread for flashing instructions. If you're thinking about using ODIN to do it, you should probably read that post.
CF-Root-SGN_XX_OXA_KJ1-v5.0-CWM5.zip
CF-Root-SGN_XX_XEN_KJ4-v5.0-CWM5.zip
CF-Root-SGN_ZS_MUL_KJ6-v5.0-CWM5.zip
CF-Root-SGN_ZS_MUL_KK1-v5.0-CWM5.zip
CF-Root-SGN_XX_DBT_KK9-v5.0-CWM5.zip
CF-Root-SGN_XX_AUT_KKA-v5.0-CWM5.zip
CF-Root-SGN_XX_ODD_KL3-v5.0-CWM5.zip
Downloads
See the second post of the thread for flashing instructions. If you're thinking about using ODIN to do it, you should probably read that post.
CF-Root-SGN_DX_XSP_KL1-v5.0-CWM5.zip
CF-Root-SGN_XX_DBT_KL7-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_KL8-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_LA1-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_LA3-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5.zip
CF-Root-SGN_XX_SER_LA6-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_LB1-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5.zip
ALL THE KERNELS IN THIS POST ARE OUTDATED AND/OR DANGEROUS, GO TO THE NEXT POST !
CF-Root-I9220_ZC_OZH_LP1-v5.2-CWM5.zip
CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5.zip *read before flashing LPY: http://forum.xda-developers.com/showpost.php?p=25966147&postcount=1322* *old*
CF-Root-SGN_ZS_OZS_LPF-v5.3-CWM5.zip *old*
CF-Root v5.5:
CF-Root-SGN_XX_OXA_LPY-v5.5-CWM5.zip
CF-Root-SGN_ZS_OZS_LPF-v5.5-CWM5.zip
CF-Root-SGN_DD_ODD_LP8-v5.5-CWM5.zip
CF-Root-SGN_DX_OLB_LP9-v5.5-CWM5.zip
Be warned that *all* of the above kernels may be suffering from the superbrick bug ( http://forum.xda-developers.com/showpost.php?p=25966147&postcount=1322 ) !
PLEASE READ THIS POST BEFORE FLASHING !
CF-Root-SGN_XX_OXA_LPY-v5.6-CWM5.zip
CF-Root-SGN_ZS_OZS_LPF-v5.6-CWM5.zip
CF-Root-SGN_DD_ODD_LP8-v5.6-CWM5.zip
CF-Root-SGN_DX_OLB_LP9-v5.6-CWM5.zip
CF-Root-SGN_XX_XEU_LQ2-v5.6-CWM5.zip
CF-Root-SGN_XX_SEB_LQ3-v5.6-CWM5.zip
CF-Root-SGN_XX_DBT_LRG-v5.6-CWM5.zip
CF-Root-SGN_XX_OXX_LRI-v5.6-CWM5.zip
CF-Root-SGN_XX_DBT_LRK-v5.6-CWM5.zip
CF-Root-SGN_XX_DBT_LRQ-v5.6-CWM5.zip
Love u man.....
My note is so dull without ur magic sprinkle....
Cant say how much I can thank you.
A little donation your way.
xxxxxxxxxx894473X
Will buy a note! Thz Chainfire
Sent from my GT-I9100 using xda premium
I'm also glad to see you on this device too. Thanks man!
sent from my Galaxy Note via T*patalk
zomg yay! can't wait
nice to see you here.. short question regardin binary counter, usb jig didnt work, is there a way to flash your kernel whitout affect the binary counter?
Chainfire said:
Should be ready later tonight or early tomorrow. I need the thread URL
(could have posted it days ago, but I'm still fixing minor issues with CWM5)
Usual CF-Root features apply. Root, busybox, CWM, custom bootanimations, custom boot scripts, CWM Manager(tm), etc.
Click to expand...
Click to collapse
fantastic chain
m_adnan said:
nice to see you here.. short question regardin binary counter, usb jig didnt work, is there a way to flash your kernel whitout affect the binary counter?
Click to expand...
Click to collapse
Yes, stay tuned for more info!
Great news! !!!
Sent from my GT-N7000 using XDA App
amazing man!! thanks!!
small donation to you: 81Y69202241504401
Chainfire said:
Yes, stay tuned for more info!
Click to expand...
Click to collapse
I always know when I've bought the right device when I see you pop up the same forum
Sent from my GT-N7000 using Tapatalk
Great news, .
magic Chain !!!
Can't wait for this. Any idea what file system the Note uses?
Sent from my GT-I9000 using xda premium
T-Mobile/Samsung have rebranded the Exhibit II 4G, giving us a new kernel, a bump to Android v2.3.6 and performance improvements (they claim) in the process. The phone we all love is now the Samsung Galaxy Exhibit 4G.
This stock ROM (UVLG3) is NOT vulnerable to USSD Dialer Attacks!
Rooting
Currently, zergrush will not root this phone's Android 2.3.6. Three known methods:
Root Stock 2.3.6 w/o a new kernel or ROM
root-stock.zip
Mirror
This zip will install Superuser, su and busybox, leaving you rooted, but otherwise no changes to your phone. ClockworkMod must be installed to flash this. So:
1. Flash ClockworkMod
2. Boot into ClockworkMod and flash root-stock.zip.
Rooted Community ROM (forkable)
t679.uvlg3.odex.01.zip
Mirror
(also see custom ROMs)
Linked above is Samsung's newest release for the Galaxy Exhibit, a stock rooted UVLG3 Gingerbread ROM. Busybox is also included. You must flash it via clockworkmod. Clockworkmod can be flashed with Samsung's stock recovery.
Custom rooted kernel
t679-root-v1.8.zip
Mirror
Kernel sources
The kernel is based on Samsung's kernel source. This kernel is rooted; if you flash it via stock recovery or cwm your ROM will be rooted with Superuser.apk, Busybox and the Galaxy Exhibit cwm-recovery installed. This kernel works with all Samsung Gingerbread releases.
Rooted ROM Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. The installation will format your data partition. I suggest Titanium Backup, available in the Market.
2. Download & copy the current t679.uv???.deodex.0x.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
3. Install Galaxy Exhibit Custom Recovery . If you're already rooted, you may install from the command line, otherwise you may install from Samsung's Recovery. Samsung's recovery only sees the internal SD, so copy the cwm zip there if you just have stock recovery. Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Select ROMwipe. This step is required!
6. Highlight install zip from sdcard, then press Home.
7. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
8. Highlight the rooted rom zip file, then press Home.
After you confirm your choice, installation should take less than three minutes.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied. Your first post-installation boot may be several minutes long.
Rooted Kernel Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. I suggest Titanium Backup, available in the Market.
2. Download & copy t679-root-v1.8.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
It's recommended to install Clockwork Mod, but you can also flash the kernel from Samsung's stock recovery. Samsung's recovery only sees the internal sd, so copy files there if you don't have cwm.
Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Highlight install zip from sdcard, then press Home.
6. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
7. Highlight the kernel zip file, then press Home.
After you confirm your choice, installation should take less than a minute.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied.
Please DO NOT PM me with support questions! They will be ignored! Post them in this thread!
Links and useful info
Galaxy Exhibit XDA Wiki
Galaxy Exhibit IRC channel
Galaxy Exhibit Themes
Custom ROMs
All ROMs listed require cwm for installation.
Peach Sunrise
RebelROM
XquiziT
CyanogenMod 9 Beta
Galaxy ExHibition
CM10 Port
AOKP (WIP)
CM7 (WIP)
CM9 Pure Nexus
Stalled, partially working
AOKP
KEMIUI
Help! I keep getting FCs!
Custom kernel for Rebel Rom
This is custom kernel 1.8 packaged specifically for RebelRom, tested on
version 3.0.8. This package includes kernel & modules only.
rrkernel.zip
Mirror 2
Stock 2.3.6 via Odin
uvlg3.odin.zip
Mirror
Adb for Windows
winadb.zip unzip and copy to your c:\Windows directory
Mirror
Flash2Stock
Flash2Stock (flash via cwm) will install stock UVLG3 and Samsung's stock recovery, un-rooting
your phone, removing ClockworkMod and returning your phone to factory condition.
uvlg3.flash2stock.zip
Mirror
SwapSD
SwapSD This simple app allows you to swap internal "usb storage" (aka /sdcard) and your removable sdcard (aka external_sd) so your larger "external sd" is mounted as "/mnt/sdcard/" and the smaller sd internal memory is mounted as "/mnt/sdcard/external_sd". This is done by changing a file called vold.fstab in your phone's /etc folder. The original device vold.fstab file is backed up to /etc/vold.fstab.backup when this app first runs. Your data on /mnt/sdcard and /mnt/sdcard/external_sd is not touched in any way whatsoever.
Dropbear (flash via cwm)
is a software package that provides a Secure Shell-compatible (ssh) server and client. It is designed as a replacement for standard OpenSSH for environments with low memory and processor resources, such as embedded systems. This archive also includes the scp and rsync utilities.
dropbear.zip
Mirror
Bloatware
These apps are safe to delete. You may also freeze them using Titanium backup.
AnalogClock.apk
Browser.apk (Only if you use an alternative browser)
Dlna.apk
DownloadProviderUI.apk
DualClock.apk
DualClock.apk
IQ-tmobile-release-signed-zipaligned-v1.1....
JobManager.apk
KiesAir.apk
MobileBackup-unsigned_v3.3.02.apk
MyFiles.apk(Only if you have an alternative File Browser i.e. Astro File Manager)
SamsungWidget_Program...
Swype.apk
TetheringManager2.apk(Only if you don't use T-Mo's tethering service)
TouchWizCalendar.apk
TouchWizCalculator.apk
TwCalendarAppWidget.apk
VideoPlayer.apk(Only if you have an alternative video player)
VoiceRecorder.apk
WiFi-Calling.apk(If you don't use it)
ZinioSettingsProvider.v2.03.3331.TMobile....
sihome-signed-tmo-android-8.apk
talkback.apk
tmobile_m4m_3_0_15.signed...
vvm-signed.apk
Partition Table
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20 all 0's
/dev/block/mmcblk0p21 all 0's
/dev/block/mmcblk0p22 all 0's
/dev/block/mmcblk0p23 all 0's
/dev/block/mmcblk0p24 all 0's
/dev/block/mmcblk0p25 all 0's
/dev/block/mmcblk0p26 all 0's
/dev/block/mmcblk0p27 efs (encrypted fs)
/dev/block/mmcblk0p28 /mnt/sdcard
Credits:VanillaTbone,s0unds,KemikalElite, jocala, Wildchild, bpear96, camcory, Intercepter and others. If your name belongs here or you have info that needs to be added please speak up!
Zergrush
Rooting the original Exhibit II via zergrush: Please read DooMLoRD's Easy Rooting Thread
Please note that this method does not work with Android 2.3.6 on the Galaxy Exhibit.
ClockworkMod
Galaxy Exhibit cwm-based recovery v6.0.1.2
6.0.1.2 has new features, including better support for both external and internal SD cards, faster backups and restores with a new backup format that de-duplicates data in between backups. Exclusive features for Galaxy Exhibit include:
wipe menu with rom wipe
All system wipes under one menu: rom (system/cache/data),cache,dalvik,cache/dalvik,data.
Stack zip files for installation:
Flash cm9 & gapps, etc. Select as many zip files for installation as you choose. Flash them all with one command.
Install system images:
Drop any recognized system image into a folder on your phone and recovery can flash it. You can even drop the entire contents of an odin tar/md5 file in a folder and cwm recovery will flash it all automatically.
All images must conform to Odin naming standards:
adsp.mbn
amss.mbn
boot.img
cache.img.ext4
preload.img.ext4
recovery.img
system.img.ext4
Click to expand...
Click to collapse
This is regular interface, not touch.
cwm.6012.t679.zip
Mirror
To initially install Galaxy Exhibit Custom Recovery you need to:
1. Copy cwm.galaxy.exhibit.zip to your internal SD storage.
2. Boot into stock recovery:
Starting recovery: Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons.
Or a different method some find easier:
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Recovery should start after the Galaxy Exhibit/T-Mobile logo.
3. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm.galaxy.exhibit.zip file.
If you already have cwm installed, to update follow the steps above, booting into your current cwm instead of stock recovery.
Should you need to install ClockworkMod via Odin:
cwm.6012.tar
Mirror
We have needed a new thread for our phone, thanks for making this!
kingdavidd said:
We have needed a new thread for our phone, thanks for making this!
Click to expand...
Click to collapse
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links and information.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any general discussion of our Galaxy Exhibits (concerning development as well). I also hope folks will evangelize and point people here rather than carry on in the older abandoned OP threads.
Nice job jocala! Thanks.
Sent from my Calculator with Android.
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct? Much rather flash that then go back to stock then update. Thank you for that.
Sent from my SGH-T679 using xda premium
jocala said:
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any discussion of our Galaxy Exhibits.
Click to expand...
Click to collapse
Yea all the old threads OP's abandoned them and the original post had all old info, I am glad you're dedicated to this phone!
SurgeRush said:
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct?
Click to expand...
Click to collapse
Yep, that's it. Purely stock except for root, busybox & recovery.
Cant wait to see what roms come out of this
Sent from my SGH-T679 using XDA
The rebranding works out nicely, if for no other reason than providing a point of demarcation.
Many props to Jocala who is awesome, as we all know. It can't be said too often but we'll try not to overdo it. :thumbup:
Sent via frazzled carrier pigeon -->
Ditto here man. We'd all be screwed & tattooed without his know-how. BTW worth mentioning I had to refreeze all the bloatware again after the update. Noticed how the phone lagged and then checked Titanium Backup. Sure enough all the crap was back. Also re-check settings in programs like Juice Defender and Rom Toolbox. I had to re-enter some of them again as well.
Has anyone managed to update successfully while already being rooted? (Specifically by Zerg Rush method)
I've yet to received the OTA notification and still holding off If i should update using the software. Stock ROM but just rooted. Holding off on "flashing" anything as I've never done it before.
ArtfulDodger said:
Ditto here man. We'd all be screwed & tattooed without his know-how.
Click to expand...
Click to collapse
That's not true at all, but thanks for saying it. Anyone handy with *nix can do what I do, and 95% (or more) of the techniques I use were pioneered by others here on xda.
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder(not in stock) T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though. It also looks like you might have taken a different approach to rooting the rom, maybe you could look at mine see if its just complete fail or not lol and or maybe pming me, to avoid clutter, on how you did urs.
ive made sooo many edits lol but just wanted to add too, thanx for all the work you have done for us.
cars1189 said:
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though.
Click to expand...
Click to collapse
The phones I use have always come odexed. I know of no other root methods. I don't have time to beta your rom, but feel free to post a link. I'm sure you'll have volunteers
cool, and no problem, and basically all i did was use the dsixd kitchen and added root(from in the kitchen menu), does that not really root it? does that just change the file permissions? cause when i did that it added the su binary so i assumed it did, but doesn't look like thats what you did, urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
cars1189 said:
urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
Click to expand...
Click to collapse
You are correct
Flashed the ROM, all went smooth, but I can't install anything from the Market. Every time I try I get "ERROR "Blah" Could not be downloaded due to an error." Any ideas? Did a full romwipe and dalvik before flashing. The markets not even updating to Play store either.
Hi,
Ive just bought a used Galaxy Note running Stock 2.3.6 (N7000XXLC1 Kernel an N7000XXLB2 baseband) and want to put the latest jellybean rom on.
Ive read through lots of threads about the brick warning and so on, i just want to know how to go from 2.3.6 and have it rooted and cwm on and the latest 4.1 leak or a modified 4.1
Could somebody please tell me the steps to do it as dont want to brick it and this 2.3.6 is rubbish
Matt
Hello!
I've rooted my Note like this:
#1
Get the original software (like N7000XXLRU - the file is 914Mb and it is a *.md5 file. ) and odin (Odin3 v1.87), install it in odin...how?
Open odin and put the file in PDA.
Option in odin leave alone (Auto Reboot & F. Reset Time; are selected)
Put Note in download mode: Volume Down Key + Home Key + Power Key; then Volume up key to continue
Connect the phone to computer
Odin recognize the phone and you will see it on COM port
Click Start
After several minutes the phone will turn on.
Now you have a original sw on your phone, and believe me this sw is GREAT...but if you want more...
#2
Root you phone
Described in this link (http://forum.xda-developers.com/showthread.php?t=1329360)
I used ''1A.Root + safe kernel + advance recovery''
Just read carefully (will write it down)
Visit this thread
http://forum.xda-developers.com/showthread.php?t=1901191
And download kernel in zip format according ROM you are having on device (just look for XXLRU-VDI; PhilZ-cwm6 v3.5 with CWM 6.0.1.8)
Copy downloaded file to Ext SD card to root directory (or any folder you make; I have ''A_ROOT'' for this things)
Reboot into recovery (Volume Up Key + Home Button + Power Key)
Select install(update) zip from ext SD card (Install zip >> Choose zip from sdcard; and click on the *.zip file)
select '[your downloaded kerenel].zip' which you have copied to Ext card above
Reboot device
Now you will have Root + safe kernel
And your phone is rooted now. You can have all the programs that work only when your phone is rooted (Titanium Backup, Root Uninstaller, Root Browser Lite, ...)
#3
Your phone is now ready to install all Android Development ROMs
Read each post ''How to flash'' it is easy
For instance I like stock rom and love 4.1.2, so i have sw from http://forum.xda-developers.com/showthread.php?t=1970626
Example:
Save *.zip on your SD/EXT Card (Ultimate N7000 XXLSA JellyBean 4.1.2 v5)
Restart in CWMR (Volume Up Key + Home Button + Power Key)
Be sure you're on SAFE KERNEL, then you can wipe (jes you are - on PhilZ-cwm6)
Full wipe /data/factory reset /cache and dalvik (dalvik is in advanced option)
Flash the ROM (Install zip >> Choose zip from sdcard; and click on the *.zip file)
Wait some minute until your phone boot!
You are done. That's all.
I've never had any problems with any of the ROMs. You can do the #3 1000 times and nothing will go wrong. Just remember to do a back up in CWM, when you have a rom that works great for you and you like. So if anything happens and you phone is stuck in ''samsung'' sing, you can go in CMW and restore it.
I hope it helps and I didn't forget anything.
Thanks so much for posting. I followed all the instructions and it worked fine. I have however gone and installed a 4.0.4 rom after using 4.1 for a bit and finding it too juddery.
Thanks again
Matt
No problem.
You can wait for the official firmware release and then everything will work 100%.
Since he didnt i hit thanks
Sent from my Amazon Kindle Fire using Tapatalk 2
Have hit thanks now , forgot!
Hi guys! I believe most of you obtained root via this method by Jiangyi: [TUTORIAL] Root access for ICS on I9100G which requires a temporary CWM. Quite a few users face problems because in temporary CWM, internal storage is swapped with external storage, i.e. sdcard=internal storage, internal sdcard=external storage. It may be confusing for newbies, especially on their first attempt on rooting. Therefore, I decided to release an easier method, where you can flash the zip files directly via stock 3e recovery!
Requirements:
- Running a stock ICS/JB ROM
- External sdcard
Features:
- SuperSU v0.99 by Chainfire
- Busybox v1.20.2 by Stericson
- No yellow traingle
- No increase in binary counter
Instructions (Root):
1. Download SU-BB-Installer.zip from here: http://www.androidfilehost.com/?fid=9390233485161005747
2. Place it in your external sdcard.
3. Power off your device COMPLETELY.
4. Boot into recovery mode by pressing Volume up + Home + Power buttons simultaneously.
5. Navigate to "apply update from external storage" using the volume buttons.
6. Select it by pressing the Power button.
7. Select SU-BB-Installer.zip.
8. Wait for it to finish and navigate up (select "../").
9. Select "reboot system now".
10. Congratulations, you now have root and busybox!
Optional: (For ICS only)
To obtain CWM recovery in order to start flashing ROMs or mods, read on:
1. Download kTool from Play Store: https://play.google.com/store/apps/details?id=net.hellcat.droiddev.ktool
2. For ICS: Download the CWM recovery kernel by codeworkx from here: [KERNEL][GT-I9100G] ClockworkMod Recovery 6.0.1.2
3. Extract the .tar file and you will get a file named zImage.
4. Place the zImage in the root of your internal storage.
5. Launch kTool and select "Flash kernel from /sdcard/zImage".
6. Reboot and profit! If you boot into recovery by Volume Up + Home + Power buttons, you will now see CWM recovery.
Optional: (For JB only)
To obtain CWM recovery in order to start flashing ROMs or mods, read on:
1. Download one of the stock recovery flashable zips of Blazing Safe Kernel from here: http://forum.xda-developers.com/showthread.php?t=2293576
2. Place it in your external sdcard.
3. Power off your device COMPLETELY.
4. Boot into recovery mode by pressing Volume up + Home + Power buttons simultaneously.
5. Navigate to "apply update from external storage" using the volume buttons.
6. Select it by pressing the Power button.
7. Select the zip.
8. Wait for it to finish and navigate up (select "../").
9. Select "reboot system now".
6. Reboot and profit! If you boot into recovery by Volume Up + Home + Power buttons, you will now see CWM recovery.
Instructions (Unroot):
1. Download SU-BB-Unstaller.zip from here: http://www.androidfilehost.com/?fid=9390233485161005748
2. Place it in your external sdcard.
3. Power off your device COMPLETELY.
4. Boot into recovery mode by pressing Volume up + Home + Power buttons simultaneously.
5. Navigate to "apply update from external storage" using the volume buttons.
6. Select it by pressing the Power button.
7. Select SU-BB-Unstaller.zip.
8. Wait for it to finish and navigate up (select "../").
9. Select "reboot system now".
10. You are now unrooted.
**NOTE: In order to use this method to unroot, you MUST use my method to root before this.
Optional (remove CWM recovery)(For ICS only):
This is the tricky part, the easiest way is to reflash a whole firmware via ODIN. But if you like new methods, try this:
1. DO NOT uninstall kTool or unroot your phone first!
2. Obtain a stock zImage (either you download it or extract it from a firmware package), make sure that it is meant for the firmware you are using.
3. Place the zImage in the root of your internal storage.
4. Launch kTool and select "Flash kernel from /sdcard/zImage".
5. Reboot and if you boot into recovery by Volume Up + Home + Power buttons, you will now see the default stock 3e recovery.
6. Now you can unroot your device.
Optional (remove CWM recovery)(For JB only):
1. Download stock_XXLSR_kernel.zip from here: http://bit.ly/XCEejd and place it into your external sdcard/internal sdcard.
3. Power off your device COMPLETELY.
4. Boot into recovery mode by pressing Volume up + Home + Power buttons simultaneously.
5. Navigate to "Install zip from sdcard" using the volume buttons.
6. Select it by pressing the Power button.
7. Select "Install zip from sdcard" if you placed it in the external sdcard, or select "Install zip from internal storage" if you placed it in the internal sdcard.
8. Navigate and select stock_XXLSR_kernel.zip.
9. Wait for it to finish.
10. Select "reboot system now".
11. CWM recovery is now replaced by stock 3e recovery, and back to stock kernel too.
That's all from me. Happy rooting!
You are too free at 3.30 in the morning hahahaa
Nice guide btw. will help a lot of people.
Nice guide mate =)
New rooting method !
Great effort
---------- Post added at 06:40 AM ---------- Previous post was at 06:36 AM ----------
iXanza said:
You are too free at 3.30 in the morning hahahaa
Nice guide btw. will help a lot of people.
Click to expand...
Click to collapse
Lol..You too Not bad at 4AM XD
Great Guide @OP..
for the verifirst time i follow this and it working great without using my pc,,and i just do it on my friend S2 today,,
FOR NOOB*
Read and follow the instructions in the thread as what @OP wrote...
YOU MAY SUCCESSFULLY ROOT.FLASH CWM ON YOU S2
I think this this thread should be STICKY THREAD
Great Mate
will be back to our 'G' Family soon
with blast
Sent from my Xperia T using tapatalk 2
Very good guide! Great Job.
Sent from my GT-I9100G using xda premium
i cant root it say..E: failed to mount /SDcard...how to fix this...?
roshan2989 said:
i cant root it say..E: failed to mount /SDcard...how to fix this...?
Click to expand...
Click to collapse
Mount and remount your SD Card =)
Really great guide man. Super simple. Will use this to root my gf's 9100G and get her on CM once I get back to India. Especially helpful because she just burned out her USB port by dropping the phone in a toilet so she can't use odin. =_=
Sent from my 9100G, running CM10.1 / Codebox / Slim Bean, depending on the day
301stSpartan said:
Really great guide man. Super simple. Will use this to root my gf's 9100G and get her on CM once I get back to India. Especially helpful because she just burned out her USB port by dropping the phone in a toilet so she can't use odin. =_=
Sent from my 9100G, running CM10.1 / Codebox / Slim Bean, depending on the day
Click to expand...
Click to collapse
This is much better than odin hehe
Really nice. I wondered how to remove the cwm in case i have to send my device to Samsung. Now i know. Thank you
Sent from my GT-I9100G using xda app-developers app
roshan2989 said:
i cant root it say..E: failed to mount /SDcard...how to fix this...?
Click to expand...
Click to collapse
Keep in mind that you need an EXTERNAL SDCARD for this...Or you are already using one, you will have to wait a while in recovery if that happens...it takes some time...if not, reinsert your sdcard...
This is going to be a bit of a noob question, but I'm new to samsungs, I swear that rooting is very different on everything else.
Is this the best way to flash a new aosp rom? The phone is not ICS at the moment, so I was going to flash stock ICS, follow this tutorial to root, and then install some jb rom like rootbox. Or can I just do temporary CWM and flash the root box on there and keep cwm?
Re: [NEW][GUIDE][ICS] How to Root/Unroot Your I9100G Via Stock Recovery
Pinktank said:
This is going to be a bit of a noob question, but I'm new to samsungs, I swear that rooting is very different on everything else.
Is this the best way to flash a new aosp rom? The phone is not ICS at the moment, so I was going to flash stock ICS, follow this tutorial to root, and then install some jb rom like rootbox. Or can I just do temporary CWM and flash the root box on there and keep cwm?
Click to expand...
Click to collapse
No, JB ROMs require ICS bootloader...so the best way is to flash a stock ICS ROM, root it and get a kernel with CWM, then only flash the new ROM...
Re: [NEW][GUIDE][ICS] How to Root/Unroot Your I9100G Via Stock Recovery
Pinktank said:
This is going to be a bit of a noob question, but I'm new to samsungs, I swear that rooting is very different on everything else.
Is this the best way to flash a new aosp rom? The phone is not ICS at the moment, so I was going to flash stock ICS, follow this tutorial to root, and then install some jb rom like rootbox. Or can I just do temporary CWM and flash the root box on there and keep cwm?
Click to expand...
Click to collapse
U must flash ics stock firmware 1st in order to get the ics bootloader..then u can do temporary cwm and can flash any roms based on ics/jb..
Sent from my GT-I9100G using Tapatalk 2
Hi guy need ur help..im follow the step but when enter su-bb-installer
Finding update package...
Opening updated package..
Verifying updated package..
E:signature verification failed
Re: [NEW][GUIDE][ICS] How to Root/Unroot Your I9100G Via Stock Recovery
What are you on? Are you sure you are on ICS? That only happens for GB...
Thanks mate 4 quick reply..
But I'm sure my phone is ICS..already updated with Samsung kies 4.0.3
Re: [NEW][GUIDE][ICS] How to Root/Unroot Your I9100G Via Stock Recovery
Hmm...weird then...it works for most of us...then you'd have to try the method by Jiangyi on another thread...maybe Sammy changed some stuff...:\
Did the su bb installer link dead? I cant open it.