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.
I update to N7000DDLA5, but after that when I type any key from keyboard showing “NULL NULL”.
I found some fix from XDA, by flashing “CSC” file by mobile odin. But from where I will get that CSC file, I have only single N7000DDLA5…..TAR.MD5 file only.
Advise please…
i extract TAR.MD5 with WINRAR. then flash with Mobile odin > Cache > Internal SD-Card > Cache.img
but after restart i am getting below message and issue still persist. please help me....
# MANUAL MODE #
--Updating application..
Successfully updated application.
--Appling Multi-CSC…
Installing Multi-CSC
Can’t access to ‘/system/csc/XSG/system/’.
Successfully applied multi-CSC.
I faced the same problem. Use the latest version of Mobile Odin to flash the whole thing again, you'll be fine. You can also use the CWM app to flash this.
1. If you have an extra memory card, use it. Make a folder named 'firmware' (without quotes) and put your tar.md5 file in it.
2. In the CWM app, select 'flash stock firmware'.
3. Select continue>keep CF Root kernel.
If you don't happen to have an extra memory card,create a folder named 'external_sd' at the root of your internal storage (/sdcard/external_sd/firmware/blahblah.tar.md5).
I must tell you, this has never worked for me though, and I've always managed to miss the error message thrown up by the recovery, so I can't tell you why
I got this error when updating to la4, not sure what the issue is but I don't use the samsung keybaord anyway I use smart keyboard and the issue doesn't happen with this keyboard, so I'm not t bothered about it
Flash stock firmware method stated above
bloodyhippo said:
I faced the same problem. Use the latest version of Mobile Odin to flash the whole thing again, you'll be fine. You can also use the CWM app to flash this.
1. If you have an extra memory card, use it. Make a folder named 'firmware' (without quotes) and put your tar.md5 file in it.
2. In the CWM app, select 'flash stock firmware'.
3. Select continue>keep CF Root kernel.
If you don't happen to have an extra memory card,create a folder named 'external_sd' at the root of your internal storage (/sdcard/external_sd/firmware/blahblah.tar.md5).
I must tell you, this has never worked for me though, and I've always managed to miss the error message thrown up by the recovery, so I can't tell you why
Click to expand...
Click to collapse
Bloodyhippo, issue resolved, I follow your steps.
1. Update Mobile ODIN pro (v2.15)
2. re-flash same firmware (N7000DDLA5) whole again.
3. after restart, Samsung keyboard issue resolved. Done!
Many thanks guys.
musheercmr said:
Bloodyhippo, issue resolved, I follow your steps.
1. Update Mobile ODIN pro (v2.15)
2. re-flash same firmware (N7000DDLA5) whole again.
3. after restart, Samsung keyboard issue resolved. Done!
Many thanks guys.
Click to expand...
Click to collapse
Thats what I was going to say. Glad you got it
thnxxxxxxxxxxxx 4 this useful tip
null keyboard characters after rooting my Samsung Galaxy Note
I just got my samsung galaxy note (SGN) and rooted it following the instructions on this page (very good - worked great)
http://forum.xda-developers.com/showthread.php?t=1331784
When the SGN booted it was rooted but the built in samsung keyboard would display null no matter what key i hit.
I did not have mobil odin installed nor could i install it without using my keyboard and i did not want to re-flash a kernel or any other drastic measures... so to fix this easily i went into the android market now (google play store) and then tapped CATEGORIES then TOOLS then TOP FREE and scrolled down to GO Keyboard (i am sure any free keyboard will work - this is just the first one i found) and installed it.
This resolved the Samsung keyboard problem and i can now type normally so i can upgrade to new ROM's etc...
-Mitch SGN / CF-ROOT / CWM / android 2.3.5 / baseband LA4 / kernel KJ1
hi guys
i m new to this site
this small tutorial is when ur restoring ur rooted or normal stock firmware with any other firmwares or unrooting and restoring to stock firmware.
btw its very simple when u update firmware over odin use the latest version and don't forget to check USB debuggin start update process.......
it takes some time.
when ur device is working it will be null null null .........
go to recovery mode wipe factory reset first then wipe partition...
when ur finished with above steps
go to downloading mode and repeat the update of firmware procedure from ODIN again ...
ur phone will be without any errors (for ex: no null in keyboard wen u type
and will be able to update from ur current firmware if updates are available ...
any doubts please feel free to ask thank you.
flash it via pc odin
i flashed it via mobile odin and got the null error too
bloodyhippo said:
If you don't happen to have an extra memory card,create a folder named 'external_sd' at the root of your internal storage (/sdcard/external_sd/firmware/blahblah.tar.md5).
Click to expand...
Click to collapse
I dont have the firmware in "md5" format, but in "TAR", will that work?
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
I had same problem tried almost everything and in the last had to flash stock GB to start over again.
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Flash back to GB and root and then come to CM9 or CM10.
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Had you tried the rooting method of dr ketan. http://forum.xda-developers.com/showthread.php?t=1329360
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Last few months ago im also having the same problem. No matter which method i had try..dr.ketan...start from gb...no luck at all. The partial root problem still remain.
Luckily i met someone to gv me help. And his method 100% works.
Please report back if u able obtain full root. Other wise i will gv u the proper step to obtain full root.
Good luck
Sent from my GT-N7000 using xda premium
Maybe the problem lies with busybox. Try getting busybox binary updated. I've read some people can do it by installing busybox from Google Play. For my case usually I inject busybox directly via CWM, but it is potentially dangerous so I won't share it here.
When I had this prob, I tried everything bo no luck, so flashed gb again.
Sent from my GT-N7000
lee yun khong said:
Last few months ago im also having the same problem. No matter which method i had try..dr.ketan...start from gb...no luck at all. The partial root problem still remain.
Luckily i met someone to gv me help. And his method 100% works.
Please report back if u able obtain full root. Other wise i will gv u the proper step to obtain full root.
Good luck
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I am having exactly this problem.
I have tried everything over and over and still partial root.
I would REALLY appreciate your help with getting full root on my note.
u need to give more details. what rom are u on?