Related
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
I want to root my SGN but i am confused which metod i should to use?
TNx?
1.2. If you are not rooted yet: Using the zergRush exploit
(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.
Go here and just read after 16Nov edit
http://forum.xda-developers.com/showthread.php?t=1329360
Final Update 1.21.2014 » Changelog.
For support beyond this guide, please look in another thread. I no longer have this product.
Thanks for all your support in this thread!
Bulletin Board
If your ROM has issues with root, see Fixing Root How-To for the solution.
-----------------------------
Common ICS issues FAQ by fred_be9300 here
------------------------------
NOTE: If you ever experience screen issues with the included CWM Recovery in the Toolkit, please flash the alternate version here or even better, flash TWRP (but be warned this guide's based on CWM).
Click to expand...
Click to collapse
This guide covers the following for models GT-P7300 and GT-P7310 in FAQ and How-TO sections:
Root/Unroot, Bootloader Mode, Odin, Recoveries & NANDROID Backup.
--------------------------------------------------
Greetings people. The main focus of this guide is centralizing information and files about the title contents to help bolster this community. I'll be as clear as possible in this little guide and excuse me if my English isn't perfect (it isn't my native language) and this is my first XDA guide. Oh and a little disclaimer: I AM NOT RESPONSIBLE IF YOU IN ANY WAY DAMAGE YOUR TABLET. BY FOLLOWING THIS GUIDE YOU ACCEPT FULL RESPONSIBILITY FOR YOUR ACTIONS. ALSO PLEASE NOTE THIS GUIDE HAS BEEN WRITTEN WITH A WINDOWS PC IN MIND. IF YOU DON'T HAVE A WINDOWS PC AVAILABLE, GET ONE, BORROW ONE, I DUNNO, but you need one. That said, let's begin.
--------------------------------------------------
FAQ Section
About Root
What exactly is root and what does it do in my Galaxy Tab 8.9?
XDA user phonic covered the technical details in this post, but basically root allows you to access and control (through applications) the device's internal system files, therefore making you a "superuser". Some apps require root. Advantages such as ad-blocking and more are only available if your device is rooted.
About Bootloader, Recovery & Download Modes
What is Bootloader Mode and how can I access it?
Bootloader Mode is a menu where you manage core functions in your device. In order to access Download Mode (needed for ODIN) and/or Recovery Mode (needed to flash ROMs and more), you will need to enter Bootloader Mode by holding VOL- when turning ON your Gtab, selecting the mode using VOL-, and entering by using VOL+. The box icon represents the Recovery Mode and the other one the Download Mode. While inside Recovery Mode, the Power button will act as an "Enter" button while the volume buttons will move the cursor.
I read something about Stock Recovery and CWM Recovery. What are those?
There are two types of recoveries. The default one that comes with your GTab (Stock Recovery which looks like this) and the CWM (Clockwork Mod) one which has cyan-colored letters for our GTabs. To flash ROMs and manage your device a bit more, you need the CWM one.[/U][/COLOR][/B]
Can I flash the CWM Recovery using the ROM Manager app? Oh and which file format is compatible?
Refrain from that. As of this writing, the ROM Manager app does not have a CWM Recovery compatible with our specific GTabs. If you still proceed, you will softbrick your device and your device will have to do a trip to ODIN in order to work properly once more. CWM-flashable files are .zip files.
About NANDROID Backup
What's NANDROID and why is it recommended?
Simple, a NANDROID is a master backup tool which is available through the CWM Recovery's "backup and restore" menu. It stores everything in the ROM except the kernel and your SDcard contents such as pictures, music, documents, etc (so always backup those elsewhere). It's more like this analogy: a photograph which captured the exact state of your ROM, apps and all at the moment of backup. It is recommended in case of emergency and in case you need to go back to the latest working ROM. How-To section below.
About ODIN
What's ODIN?
ODIN's a troubleshooting/emergency tool in case your GTab bootloops (eternal restarting of a device, i.e. softbrick). Please note that if your device's screen doesn't even turn on (an example of a hardbrick) then you may be out of luck. This tool can save your GTab if you follow instructions, or can hardbrick your GTab if you don't follow instructions.
Where can I find ODIN? Do I need something like a driver to make it work? Also, which file format is compatible?
Yes you do need a driver first (provided at the end of this guide) and a Windows PC. The ODIN program is inside the zip inside the Toolkit provided at the end of this guide. As suggested by developer alterbridge86, use ODIN version 1.85. Regarding file compatibility, generally the .tar files are the ones for ODIN.
Does it remove Root and custom recoveries such as CWM in case of a warranty claim?
Yes. There are two ways:
[*]Flashing an ODIN image to go back to stock defaults (easier in my opinion). If you want to use ODIN then you have options in the Development forum, specifically this thread.
OR
[*]Flashing a CWM zip file (CWM, which is a Recovery, will be discussed in the Recovery FAQ below) after doing all wipes and restoring Stock Recovery (Restoring Stock Recovery How-To is below these FAQs)
Ok, so how do I use the tool?
The How-to section is below the FAQs.
How-To Section
Remember, all files mentioned in this section this way are included in the Toolkit at the end of this guide.
[ Rooting ]:::::::::::::::::::::::::::::::::::::::::::
Make sure to download the Toolkit from the link at the end of this post and put the "Root" .zip in your device's internal memory. You will enter Bootloader Mode, and then Recovery Mode as detailed in the About Bootloader FAQ above. You will now select "install zip from sdcard" then "choose zip from sdcard" and look for the Root.zip which you previously put in your SDcard. Select it with the Power button to flash it and then reboot your device. When your device finally boots, check if the SuperSU app is available, if it is then you're rooted now.
[ Fixing Root ]:::::::::::::::::::::::::::::::::::::::::::
In some cases a ROM can come with a broken root due to the superuser binary being located in the wrong system folder. Please flash the Root.zip package in CWM Recovery. The Root package will delete the offending binary from the wrong place and install it in the right place. For more instructions, see Rooting How-to.
[Unrooting]:::::::::::::::::::::::::::::::::::::::::::
For unrooting, proceed to Bootloader Mode and select the Recovery icon (detailed in the About Bootloader FAQ above) please flash the CWM Recovery flashable file provided in the Toolkit link at the end of this guide called "Unroot". Now reboot your device. If there is no app called SuperSU or Superuser in your apps list, then your device is now unrooted.
[Installing the CWM Recovery]:::::::::::::::::::::::::::::::::::::::::::
First, you need the file called either "7310_CWMR" or "7300_CWMR" depending on your model, inside your device's SDcard. The procedure is very similar to Rooting and either procedure can be done first. Go to Bootloader Mode (as detailed in the FAQ above), then Recovery (assuming you've Stock Recovery), select "apply update from /sdcard", then look for the file you put in the SDcard. Select it with the Power button to flash it. Now, reboot once more to Bootloader Mode, go to Recovery Mode and now you will see the CWM Recovery Mode. You are now ready to flash stuff. Please note you don't need root to flash a ROM, just this CWM Recovery. Be sure to follow the ROM thread's instructions precisely.
[Restoring Stock Recovery]:::::::::::::::::::::::::::::::::::::::::::
For this one you will need to use ODIN. Locate the file "Stock Recovery", which is a .tar file, perfect for ODIN's PDA section. Follow the ODIN 1.85's HOW-TO below.
[Doing a NANDROID Backup/Restore]:::::::::::::::::::::::::::::::::::::::::::
You need CWM Recovery for this one. Once you're in CWM Recovery, the process is straightforward. Look for the "backup and restore" menu, access it and you will see two options: "backup" and "restore". Select "backup" and wait until the system gathers all data and packs it as a backup located in your internal memory, inside a folder called "clockworkmod". Once more, remember this will not backup your SDcard contents such as your documents, music, pictures, etc (so always have a backup of those elsewhere).
For restoring the process is the same. You need to do the following to ensure a proper restore and prevent issues that might pop up: Wipe your system using CWM Recovery's "wipe data/factory reset" and after that go to "advanced" and now "wipe dalvik cache". Now go to the "mounts and storage" menu and select "format /system". That was a full wipe. Now proceed to the "backup and restore" menu, select "restore" to select your backup. Remember to reflash the kernel if you had one that didn't come with the ROM (like _motley's for example).
[Using ODIN 1.85]:::::::::::::::::::::::::::::::::::::::::::
Enter Bootloader Mode and then Download Mode as detailed in the FAQ above. Be sure to have installed the drivers (included in the zip at the end of this guide) in your Windows computer along with the ODIN program anywhere in your PC (also included in the Toolkit at the end of this guide). Open ODIN 1.85 in your PC, look for the "PDA" button, press it and look for the right file (which usually is the biggest-size file inside the downloaded and unzipped ROM .zip). THE FOLLOWING THREAD OFFERS MOST ODIN IMAGES. IF AVAILABLE, put the CSC, PIT and whatnot files in their corresponding places by pressing the corresponding buttons (IF these files aren't available, ignore this sentence). The PIT file is only necessary in case you want to have the Repartition option available and want to repartition the device (this is an alternative that can work in case of a really borked tablet full of bootloops even after a normal ODIN session without Repartition). Now, assuming you have the drivers installed in your PC, connect the device while in Download Mode, and you will see that ODIN will see it in a yellow rectangle in the upper section that says COM# (# being any number). BEFORE CLICKING "START" MAKE SURE "F. RESET TIME" IS CHECKED ON THE LEFT SIDE. Now, click the START button inside ODIN and it's flashing time. Wait until the blue meter fills. After ODIN says PASS in a green square, you can then reboot the device (long pressing the Power button is an alternative if it doesn't auto-reboot).
Toolkit Link: shorturl.at/pqCIY
SHA-1: 4DC13D60280ECA6352704AA72153E5E4EDF875E0
MD5: 59CC2548FC76D93075FDF8B392DAA1AE
Contains essentials such as: Drivers, Root, Unroot, Stock Recovery, CWM Recovery & ODIN files. Remember to unzip the package. Also, with drivers being included, you don't need to install KIES.
[CREDIT GOES TO]:::::::::::::::::::::::::::::::::::::::::::
alterbridge86 (For his ROMs and the first CWM Recovery for our tablets)
_motley & Team Galaxian Soup (For their excellent kernels and deodexed ROMs)
kallt_kaffe (Pioneer in bringing the newer CWM Recovery to our tablets along with CyanogenMod ROMs)
suwandiapr (For the flashable unroot file and ODIN image thread)
phonic (Great rooting explanation and manual unroot post)
lufc & sudec123 (For the past mirror links)
Chainfire (For making SuperSU)
SamHaLeKe (For the Samsung USB drivers)
...and to anyone I might have forgotten, do say in a PM .
Click to expand...
Click to collapse
Changelog
Code:
[B][COLOR="Red"][I]1/21/2014 - FINAL UPDATE[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated SuperSU to v1.91 for Root.zip - Important fix for Android 4.4.x
[B][COLOR="DarkOrange"][I]1/19/2014[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated SuperSU to v1.89 for Root.zip
[B]TOOLKIT[/B] - Updated Adobe Flash Player to last release v.11.1.115.81
[B]TOOLKIT[/B] - Updated Samsung USB drivers to v1.5.29.0
[B]BULLETIN BOARD[/B] - Suggested TWRP Recovery with a warning.
[B]GUIDE[/B] - Deleted Mirror Link for Toolkit due to HotFile's shutdown.
[B][COLOR="DarkOrange"][I]4/20/2013[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Replaced Superuser with SuperSU (v1.25) for Root.zip
[B]TOOLKIT[/B] - Updated Unroot.zip to remove either Superuser or SuperSU
[B]TOOLKIT[/B] - Updated Adobe Flash Player to version 11.1.115.54
[B]TOOLKIT[/B] - Updated Samsung USB drivers to version 1.5.18.0
[B]GUIDE[/B] - Modified Rooting, Fixing Root and Unrooting How-to to reflect Toolkit changes.
[B]BULLETIN BOARD[/B] - Redirected users having root issues to the right place, reflecting Toolkit changes.
[B][COLOR="DarkOrange"][I]1/13/2013[/I][/COLOR][/B]
[B]GUIDE[/B] - Unroot How-To - Added solution for ROMs that have the root binary
in the wrong place. See [B][COLOR="Red"]red[/COLOR][/B] note.
[B][COLOR="DarkOrange"][I]1/9/2013[/I][/COLOR][/B]
[B]GUIDE[/B] - Corrected error in the manual Unroot command (thanks trekker99!)
[B][COLOR="DarkOrange"][I]11/17/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated Root.zip and Unroot.zip
[B]TOOLKIT[/B] - Updated Adobe Flash Player to version 11.1.115.27
[B]TOOLKIT[/B] - Updated MD5 and SHA-1 checksums.
[B][COLOR="DarkOrange"][I]10/12/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Suggested Common ICS issues FAQ by fred_be9300
before the introduction.
[B][COLOR="DarkOrange"][I]10/07/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated & Fixed Root.zip. Independent file [URL="http://forum.xda-developers.com/showpost.php?p=32496433&postcount=257"]here[/URL].
[B]TOOLKIT[/B] - Updated USB drivers to v1.5.15.0.
No need to reinstall if you installed a previous version.
[B]TOOLKIT[/B] - For convenience. Added Adobe Flash Player 11.1.115.17
(latest version for ICS and Jelly Bean ROMs).
[B][COLOR="DarkOrange"][I]8/04/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Added MD5 and SHA-1 of the Toolkit in its section.
[B][COLOR="DarkOrange"][I]7/25/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - CWM Recovery v.6.0.0.8 included.
[B]GUIDE[/B] - Alternate version link also [URL="http://forum.xda-developers.com/showpost.php?p=21194554&postcount=2"]included[/URL] in case
of screen issues in some units.
[B][COLOR="DarkOrange"][I]7/22/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Major redesign. Users can now choose what to view.
[B][COLOR="DarkOrange"][I]7/21/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Minor, simpler redesign using the Roboto font.
[B]TOOLKIT[/B] - PIT file for ODIN now included
[B]TOOLKIT[/B] - Drivers updated to v.1.5.6.0
[B]TOOLKIT[/B] - CWM Recovery v.6.0.0.0 included
[B][COLOR="DarkOrange"][I]7/1/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - *Fixing Root* How-To section updated and further simplified.
[COLOR="DarkOrange"][I]6/17/2012[/I][/COLOR]
[B]GUIDE[/B] - Added one important detail in Nandroid FAQ/How-To and Toolkit sections.
[B]CHANGELOG[/B] - Format revised for consistency.
[COLOR="DarkOrange"][I]6/10/2012[/I][/COLOR]
[B]TOOLKIT[/B] - Updated Drivers to v.1.5.5.0.
[COLOR="DarkOrange"][I]5/19/2012[/I][/COLOR]
[B]GUIDE[/B] - Reorganized contents for ease of use.
[B]TOOLKIT[/B] - Changed the CWM Recovery to a fixed one by kallt_kaffe due
to several getprop status7 flash errors with the one provided by alterbridge86.
[COLOR="DarkOrange"][I]5/8/2012[/I][/COLOR]
[B]GUIDE[/B] - Minor redesign.
[COLOR="DarkOrange"][I]4/24/2012[/I][/COLOR]
[B]TOOLKIT[/B] - USB Driver version 1.5.4.0 now included.
[COLOR="DarkOrange"][I]4/8/2012[/I][/COLOR]
[B]GUIDE[/B] - Included suwandiapr's ODIN images thread link in both ODIN FAQ & How-To
as reference.
[COLOR="DarkOrange"][I]4/7/2012[/I][/COLOR]
[B]GUIDE[/B] - Minor revisions in "Fixing Root" and manual "Unroot" commands.
[B][COLOR="DarkOrange"][I]2/25/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Minor redesign.
Fixed manual Unroot commands.
[B][COLOR="DarkOrange"][I]2/23/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Discarded model specific CWM Recoveries and
replaced them with an universal flashable
for convenience. Credit goes to alterbridge86.
[B][COLOR="DarkOrange"][I]2/16/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Deleted ODIN image suggestions.
[B][COLOR="DarkOrange"][I]2/5/2012[/I][/COLOR][/B]
[B]GUIDE & TOOLKIT[/B] - Updated with the newer CWM Recovery along with instructions where needed.
[B]TOOLKIT[/B] - Unroot flashable included along with a newer driver (not necessary if you already installed the previous one).
[B]GUIDE[/B] - Suggested firmware KHA for the 7310 instead of the KL2 one at ODIN FAQ's third question due to better feedback.
[B][COLOR="DarkOrange"][I]1/30/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Added newer KL2 ODIN firmware link for the 7310 in the FAQ.
[B][COLOR="DarkOrange"][I]1/27/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Minor reorganization/cleanup.
[B][COLOR="DarkOrange"][I]1/25/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Improved ODIN How-To with one little but very important detail in red.
[B][COLOR="DarkOrange"][I]1/23/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Removed Filesonic mirror due to them shutting down their file sharing services.
[B][COLOR="DarkOrange"][I]1/20/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Improved 3rd question of ODIN FAQ and also replaced links with the right ODIN images (had mistakenly put CWM links instead of ODIN image links).
Added a little disclaimer in the Bootloader FAQ in red.
[B][COLOR="DarkOrange"][I]1/19/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Removed the non-working Megaupload mirror link because of [URL="http://gizmodo.com/5877612/feds-kill-megaupload"]this[/URL].
[B][COLOR="DarkOrange"][I]1/14/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Added 3 new mirror links (thanks sudec123!).
Replaced KK5 (7300) ODIN firmware link with KL4.
[B][COLOR="DarkOrange"][I]1/12/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Improved Unroot How-To.
[B][COLOR="DarkOrange"][I]12/28/2011[/I][/COLOR][/B]
[B]GUIDE[/B] - Added Fixing Root How-To and updated ODIN FAQ with a new question.
[B][COLOR="DarkOrange"][I]12/26/2011[/I][/COLOR][/B]
[B]GUIDE[/B] - Added NANDROID FAQ and How-To.
[B][COLOR="DarkOrange"][I]12/22/2011[/I][/COLOR][/B]
Initial guide.
Thank for create this thread.
Nice work mate
Thanks for all the info, Will give it a sticky
Did a Mirror on File Sonic if you want to use it
mynewuser said:
Thank for create this thread.
Click to expand...
Click to collapse
No worries!
lufc said:
Nice work mate
Thanks for all the info, Will give it a sticky
Did a Mirror on File Sonic if you want to use it
Click to expand...
Click to collapse
Thanks a lot, lufc. I've put your provided link at OP along with credit.
Hi, I've installed the clockwork Recovery, I wiped everything because I wanted to turn back to factory defalut and now the tab is bricked.
I can turn on it, I see the galaxy tab logo but nothing happens.
So I turned to the default system recovery, wiped again but it is the same: after 10 minutes the screen shows only the logo and nothing else.
Any advice?
Thanks
HarryCustom said:
Hi, I've installed the clockwork Recovery, I wiped everything because I wanted to turn back to factory defalut and now the tab is bricked.
I can turn on it, I see the galaxy tab logo but nothing happens.
So I turned to the default system recovery, wiped again but it is the same: after 10 minutes the screen shows only the logo and nothing else.
Any advice?
Thanks
Click to expand...
Click to collapse
Flash a rom and you will be fine.
Done! Now it works perfectly.
Now i'll retry to install clockwork recovery...
Overcome_CWM_Recovery_v5.1.2.6_P73xx,Can use with the other galaxy device such as galaxy S plus?
somboons said:
Overcome_CWM_Recovery_v5.1.2.6_P73xx,Can use with the other galaxy device such as galaxy S plus?
Click to expand...
Click to collapse
I don't know. This guide is focused on the 7300/7310 variants of the Tab 8.9 as specified in the OP.
Sent from my GT-P7310
thanx nirogu for the guide..
all the steps is correct rite?
im going to try soon.... ^^
install CWM, backup stock rom using nandroid,
and then root....its better this way rite?
about root, it will void the warranty rite?
how about CWM? did we need to instal stock recovery back before claim for warranty or no need?
Thanx..^^
slaughterer0206 said:
thanx nirogu for the guide..
all the steps is correct rite?
im going to try soon.... ^^
install CWM, backup stock rom using nandroid,
and then root....its better this way rite?
about root, it will void the warranty rite?
how about CWM? did we need to instal stock recovery back before claim for warranty or no need?
Thanx..^^
Click to expand...
Click to collapse
Yes, you are correct. You can root while being in Stock ROM (the system that comes with your device) or after flashing a custom ROM. Yes, root will void it, but you can always go back to the factory image (hint: ODIN) and that removes everything, including CWM Recovery and Root. If you're staying with Stock ROM, then yes, you need to flash the Stock Recovery and Unroot (both How-Tos in the guide).
nirogu325 said:
[Restoring Stock Recovery]:::::::::::::::::::::::::::::::::::::::::::
For this one you will need to use ODIN. Locate the file "Stock Recovery" (in the zip included at the Download Link at the end of this post), which is a .tar file, perfect for ODIN's PDA section. Follow the ODIN 1.85's HOW-TO above.
[Doing a NANDROID Backup/Restore]:::::::::::::::::::::::::::::::::::::::::::
You need CWM Recovery for this one. Once you're in CWM Recovery, the process is straightforward. Look for the "nandroid menu", access it and you will see two options: "backup" and "restore". Select "backup" and wait until the system gathers all data and packs it as a backup located in your internal memory, inside a folder called "clockworkmod".
For restoring the process is the same. You need to do the following to ensure a proper restore and prevent issues that might pop up: Wipe your system using CWM Recovery's "wipe menu", do a "wipe data/factory reset" and after that "wipe dalvik cache", now go to the "storage menu" and select "format /system". Then proceed to the "nandroid menu", select "restore" to select your backup. Remember to reflash the kernel if you had one that didn't come with the ROM (like _motley's for example).
.
Click to expand...
Click to collapse
Hello All,
Maybe a stupid question but, I did not find any clear answer to my question.
I have taken a backup with NANDROID and got the backup into the folder clockworkmod as told in the instruction. Now as I Understand this does not include the ROM or does it?
Also the Restoring stock recovery, how does that work, I put the "recovery.img.md5" file into Odin and flash, but from where does the stock firmware come? Most probably it's not in the 4MB "recovery.img.md5" Do I need to prepare something before using this or does it work without any preparation?
Does it also erase Overcome CWM Recovery that I installer earlier?, It did not say anywhere in the post if I need to have Root permissions to use this?
---------- Post added at 08:35 PM ---------- Previous post was at 08:30 PM ----------
taiger78 said:
Hello All,
Maybe a stupid question but, I did not find any clear answer to my question.
I have taken a backup with NANDROID and got the backup into the folder clockworkmod as told in the instruction. Now as I Understand this does not include the ROM or does it?
Also the Restoring stock recovery, how does that work, I put the "recovery.img.md5" file into Odin and flash, but from where does the stock firmware come? Most probably it's not in the 4MB "recovery.img.md5" Do I need to prepare something before using this or does it work without any preparation?
Does it also erase Overcome CWM Recovery that I installer earlier?, It did not say anywhere in the post if I need to have Root permissions to use this?
Click to expand...
Click to collapse
Hmm, for some reason I did not see page 2 before posting my questions, Got answers to most already, Only the Restoring stock recovery question left, how doest it really work?
taiger78 said:
Hello All,
Maybe a stupid question but, I did not find any clear answer to my question.
I have taken a backup with NANDROID and got the backup into the folder clockworkmod as told in the instruction. Now as I Understand this does not include the ROM or does it?
Also the Restoring stock recovery, how does that work, I put the "recovery.img.md5" file into Odin and flash, but from where does the stock firmware come? Most probably it's not in the 4MB "recovery.img.md5" Do I need to prepare something before using this or does it work without any preparation?
Does it also erase Overcome CWM Recovery that I installer earlier?, It did not say anywhere in the post if I need to have Root permissions to use this?
Hmm, for some reason I did not see page 2 before posting my questions, Got answers to most already, Only the Restoring stock recovery question left, how doest it really work?
Click to expand...
Click to collapse
A Nandroid, as stated in the guide (FAQ section), is an exact copy of the ROM you were using with all its settings and apps you had. For the Stock Recovery, you just need the file you mentioned, and as stated in the guide, use ODIN and put the file into the PDA section. Yes, it overwrites the CWM Recovery, and no, Root is a process inside the ROM (once your device boots into it), it doesn't have any effect in Bootloader Mode.
Okay, don't know if it's me that is just stupid or what the problem is. I have tried to root my device and it does not seam to work as I'm not able to install any new kernel. Picture attached of when I try to install root.zip
It complains about: "Can't access to '/system/csc/NEE/system/'.
I have successfully installed Android 3.2 (http://forum.xda-developers.com/showthread.php?t=1410887) At least in About it says that I'm running Android 3.2. From new it was running 3.1
taiger78 said:
It complains about: "Can't access to '/system/csc/NEE/system/'.
Click to expand...
Click to collapse
This error doesn't have anything to do with root or kernel. It is just trying to set your CSC and fails because the folder is not there. It happens if you flash firmware that is not intended for your region, it doesn't effect anything else, so don't worry about that.
poisike said:
This error doesn't have anything to do with root or kernel. It is just trying to set your CSC and fails because the folder is not there. It happens if you flash firmware that is not intended for your region, it doesn't effect anything else, so don't worry about that.
Click to expand...
Click to collapse
+1 Okay, thank you for your answer, the firmware I flashed, included all European languages that's why I used it.
Anyhow any ides to why I can't install a custom kernel after I have installed the Root.zip file? I get following screen when installing:
But after rebooting I still have the original kernel from flashing 3.2
taiger78 said:
Anyhow any ides to why I can't install a custom kernel after I have installed the Root.zip file? I get following screen when installing:
But after rebooting I still have the original kernel from flashing 3.2
Click to expand...
Click to collapse
Okay got it now, problem was that "Overcome_CWM_Recovery_v5.1.2.6_P73xx" had been removed when installing HC 3.2
taiger78 said:
+1 Okay, thank you for your answer, the firmware I flashed, included all European languages that's why I used it.
Anyhow any ides to why I can't install a custom kernel after I have installed the Root.zip file? I get following screen when installing:
But after rebooting I still have the original kernel from flashing 3.2
Click to expand...
Click to collapse
The picture you posted shows stock recovery and you can't flash a kernel with stock recovery.
You need to install CWM recovery and then you can flash the kernel from there. I'm using CWM recovery from there http://forum.xda-developers.com/showthread.php?t=1321142
I used the Overcome_CWM_Recovery_v5.1.2.6_P73xx.zip and flashed it using stock recovery.
If you know how to use Odin then you can download the Overcome_CWM_Recovery_v5.1.2.6_P73xx.tar and flash it using Odin.
It doesn't matter which you use, the end result is the same. Only flashing method is different.
When you have CWM recovery installed, then you can boot to CWM recovery and flash the kernel from there.
If you at any time flash stock rom back using Odin, then it will overwrite all, including the recovery. So you have to start all over.
I registered to say THANKS!!
I'm fairly new at this, and did something rather stupid this morning.
Thought my tab was hosed, but following the excellent instructions provided here I was able to recover it, what a relief...
It was actually a pretty good learning experience, although a bit traumatic.
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.
I have purchased my Samsung S10 Exynos and successfully rooted it using the only possible ways that have seems to be available so far. I have gained root, but I was wondering if anyone has solved the issue of having to turn the device on with all 3 keys held down at the same time. I understand that this is because the rooted version of the phone has be installed on the recovery of the phone, but I hope that there becomes a way to turn on the phone with root and use only the power button. I check from time to time, but it seems that this has not been solved yet. If anyone can find a solution for me so that I do not have to keep searching then I will reward them $100. An idea that I had is if there was a way to modify the power button to boot into recovery by itself? I believe this would be impossible but if anyone could think of a way to do that then that would solve the problem. I am okay with never being able to unroot the device if this would be the case.
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
DHGE said:
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
Click to expand...
Click to collapse
Hello, thank you for the suggestion. I thought about that idea already and I forgot to mention it in my post. I am looking for a way to do it via a cold boot. I know about the reboot into recovery method already, and I know of a way to map the power button to reboot into recovery if held down, but I am looking for a way to cold boot into recovery with just the power button.
I like your idea, but if there was a way to do it as a cold boot then that is ideally what I'm looking for. Your method would work if there was a way to just keep the phone shut down and wait until I hold the power button to turn it on and then it boot into recovery. If you can think of a way to do that then let me know.
The reason I am seeking this is because I root the S10 out to have a proprietary app on it and the app requires root to function properly. I need the power button to boot with root on the S10 so that it will always do so and my employees / customers will not access the non-rooted side of the phone by accident. The 3 button combination is too difficult, so I would need to resort so either a S8 or S9 if the S10 won't allow power button only to boot with root access. The app that I make uses a great amount of battery life so I need the ability to shut down the phone and cold boot it back into recovery. Thanks.
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
Awesome. Your solution sounds perfect for what I was looking for. Yes, I got my S10 back over a year ago and rooted it with patched AP file and magisk. I was only able to find that method even up until yesterday. I would like a step by step if you are able to quickly put one together. If it works then I am glad to grant you the reward for your help. I am willing to do this in the easiest way possible, even if it requires wiping data. I never used the phone so wiping is no problem at all. I am looking to do this to several devices so the easiest and fastest way would be the best. I will look into your comments and see if I can figure out doing this over this weekend. Will keep everyone updated.
pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
I just read some info on the links you provided and i think i can figure it out. if i have any trouble then ill let you know. Dont worry about a step by step for now unless I have any trouble. Thanks!
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
pjc21 said:
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
Click to expand...
Click to collapse
Hey There, Been busy lately and I haven't gotten around to trying any of these methods until today. Today I attempted the stockrom+CruelKernel. I am having a strange problem. I am acquiring root but as a read-only. I can not make any changes to system files, I can only view them. Can you tell me if you are able to modify or add to the system directory? Let me know. I know your phone is running custom rom + custom kernel, so I just might have to do that if that is the only fix. I have tried several things and read all of the threads but can not find anyone else that is experiencing this issue / I can not find a fix. I'm about to try the custom rom (stock based) + custom kernel to see if that works. If you can tell me if you have access to read/write system files then let me know so I know if this is even possible. Thanks.
I have found out that I can modify system files through twrp recovery, but when I boot into the main operating system then I have root but as read-only.
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
pjc21 said:
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
Click to expand...
Click to collapse
Cool, I'll give your suggestions a try. I'm a fan of ES File Explorer. They have a root explorer built in their app and previously I had a S8 Exynos and a S9 Exynos and that app worked for those phones but with this S10 the switch is grayed out and no other app is working for me either. On my older S8 Exynos and S9 Exynos I rooted with stock-rom + stock-kernel and just needed TWRP+Magisk and I always was able to modify or add/delete system files with ES file explorer. I guess Samsung is getting more and more strict on allowing this by making us hop through more hoops in order to do so. So far I only have ready only system files on the S10 Exynos which is new to me because the S8 and S9 always allowed modifying system files in the past but I will try your methods you suggested. Worst case I'll attempt the custom-rom + custom-kernel and see if that works. Right now I have stock-rom+custom-kernel. I was able to make changes in the system files in TWRP but hopefully your method will allow me to edit system files without having to switch to TWRP every time I want to change something. I will keep you updated.
On a side note I just rooted a Samsung S20 Exynos and turns out that the system files are read only everywhere whether in TWRP or not, so Samsung keeps making things more difficult on us all. I currently have no way of modifying system files on the S20 no matter what I try but that phone is still much newer so I will give the magicians more time before I look into the forums more for that phone. Right now if I can get the S10 Exynos then I'll be happy.
I'll let you know how things progress. If I get what I need done with this S10 then I am happy to give you a donation for your help in this matter. I would not have gotten this far without your help. Previously the S8 and S9 days were so much easier and people had youtube videos galore that described how to root. The process was easy and everything was unlocked as read write back in the S8 and S9 days.
Yeah I use to use ES on android 6-8 then moved of to solid explorer, very similar ui to ES and also has root explorer but unfortunately it does not work to change permissions on s10 android 10 (bloody samsung/google). So far the only free one I have found is x-plore to be able to do this now. Looks like google is locking down android even more now with android 11