Related
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.
Dear valued Android and Samsung experts,
it is my first post in this forum. I waited until the flashable ROM etc. was released, so today I tried humbertOS' CM9 (RC0) from 02.02.2012. It is only my second time doing this, after initially upgrading von Android 2.0 or so to 2.3.3.
My Device Info (after wiping, while stuck now)
European SAMSUNG GALAXY TAB (GT-P1000)
Android 2.3.3
Current baseband version: P1000XXJPZ
Current kernel version: [email protected]#2
Build No : GINGERBREAD.XXJQ1
Rooted with Super One Click (Maybe. Can't remember anymore, but it is rooted.)
Installed ROM Manager Pro.
Backed up with TitaniumBackup (Premium I think) to my Dropbox (via Wifi). I hope that is correct this way.
I get the following error:
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
Installation aborted.
Click to expand...
Click to collapse
What did I try to solve the issue?
I redownloaded the ROM.zip, but it didn't help. As there are no md5 hashes available (why?) for the online files, I couldn't compare if there is a problem on my download side. But I used Google Chrome, Internet Explorer 9 and jDownloader now, they can't all be faulty. Of course I re-wiped the cache every time after I had to start the phone or transfer the files!
I read 3+ threads that I found via search, but there was no solution. By the way I was unable to find this forum (Samsung Galaxy Tab) in the forum scroll-down list? Am I blind? I triple-checked! ... In one of the threads I read there I should go go back to the stock version (2.1 or so), is that true? How do I force my Tab to do so?
Now what I think could be the problem source is that I'm wondering why the path /sdcard is showing all the other folders and stuff and why before I put the files on the flash partition of the Galaxy Tab it didn't initially show up! What I try to say is: It seems to me the bootloader accesses NOT the SD-card, but the Tab's flash (all while calling it /sdcard), how can that be!
My SD card is basically empty asides of the ROM, kernel and GApps, but (how) can it even happen that the bootloader choses the internal flash over the SD card?
The last time (2.1 to 2.33) I upgraded I used Odin. This time this is not an option? I only follow the procedure you outlined and ask no questions. I mean in the other thread I read "you will need to flash via odin first because stock rom of gtp1000 have limited options in the recovery mode." (source) - well why is this then not mentioned in this thread or on humberos website? As said, I just followed the directions, thus avoided Odin this time!
And here I read a lot about "Clockwork Recovery", do I really need it? *confused* I mean I already own and payed for ROM Manager and Titanium Backup, should be fine right? I mean it is almost absurd how much I read about it...I can assure you I bought the above tools because back then those were the ones in the talk!
I also heard about "disabling of signature verification", but as it involves a lot of steps, is it really necessary?
I also read about "3e Recovery" but what is that? I would be happy if everyone could stop throwing around with abbreviations that yield no helpful Google results and instead write out and describe what tool or method they use exactly. For the above example my open question is obviously if this recovery method also applies to me with a different brand (Samsung) and model (Galaxy Tab "classic") compared to where I found this method....
Finally do I need to / should I replace my bootloader / recovery menu with another one maybe? ... In conclusion I hope you see I did my research, but there are so many ways to get a solution, so right now I simply need a hint from more experienced pro's about in which direction I have to go!
Thank you for your help in advance!
ClockworkMod Recovery
Ok, I noticed now my mistake probably is that I was missing an installed "ClockworkMod Recovery".
But: When I try to install CWM from within the ROM Manager (v.5.0.0.6, Premium) it only displays a choice of two models - "Samsung Epic4G" and "Samsung GalaxyS i9000" - in the list and not my model (Galaxy Tab EU) or any other model! What is going on there, why does ROM Manager Premium not display an array of other devices?
And is there any alternative way to download and install CWM on my Tab?
PS: The "Euro bootstrap recovery" app mentioned in other threads is not available anymore in the market either.
PPS: I also found this directory full of clockwork builds: http*//download.clockworkmod*com/recoveries/, which one of those would be right for the GT-P1000? The "recovery-clockwork-tab.img" & "*.zip" from 04-Jun-2011 17:37?
The commonly known method is to restock according to Overcome 4.1 rom thread
Then install overcome kernel.
That gives you cwm recovery and it also converts your filesystem to ext4.
Then flash the cm9.
Sent from my GT-P1000 using XDA App
Thanks priyana
Thanks priyana, that hint really made it for me!
Successfully made it through!
Now only the GApps don't show up even though I installed them.
Will browse the forum here and Google for solutions...
reset to factory default and re-install gapps once more?
seems to happen now and then to some flashes
Hey priyana, I didn't update the thread, yes I'm done with that already!
A question though: Is it normal that the internal + external storage show "as one" drive or is the SD card actually not mounting on my Windows laptop? (I assume.)
The problem is, even though I activated UMS with the toggle, I can only put the data on the "12,8 GB" drive, from which I also installed GApps.
But it seems I can't install *.apk files from this location and I also have difficulties restoring my Titanium backup files from there (I put them in the TB subfolder).
So far my progress. I only want my backup back and mount my SD card, then I'm done.
can't help you there yet. I am not yet on ICS
But in slimdizzy's latest built he confirms that both cards visible from windows.
remember one is on /sdcard (internal) and the other is /mnt/emmc (external) because that is CM standard.
One of these days I will follow you guys into ICS.
Tried once earlier before the wifi speed was fixed and didn't like it.
I mean looking from the Windows / PC perspective.
There, I have neither of those paths. I hope that is not unusual.
Another point maybe: As I can't use Kies now, how to manage music? I succeeded in putting videos into the "video" folder, but the same doesn't work for music files (in "Music" as *.mp3 files). Probably I'm lacking the basics (I self-teach them to myself ), so a link to a tutorial about all this is more than welcome. But as said, asides from restoring my backup (I'm still looking for a solution...) and the music issue, all is fine. I even managed to install the apps from within the internal storage with the pre-installed file-manager.
Dont know much about the kies and music.
For TB, there is a setting in there for backup folder.
Have you explore the options?
I can put my my backups anywhere and point TB to it and restore.
Sent from my GT-P1000 using XDA App
Actually, now after another restart it did recognize both the music and the missing TB backup files! I'm really a bit sloppy. Now I'm actually restoring successfully.
Now I will only try to find how to remove a few apps (not selected for restore!) from the backup (job). Apps that I actually don't ever want to see on my tablet again.
I'm sure I'll be able to find out myself...
same problem
priyana said:
The commonly known method is to restock according to Overcome 4.1 rom thread
Then install overcome kernel.
That gives you cwm recovery and it also converts your filesystem to ext4.
Then flash the cm9.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
please help .... im new to this but having the same problem .n i didnt understand what is overcome n how will it solve this issue..please reply
I have replied the same way many times in this forum too
Here goes again:
Overcome ROM is a GB 2.3.6 custom ROM based on Samsung ROM.
We use it a lot because:
1) it has very clear step by step fool proof way to "re-stock" your TAB in a good clean stock condition, upon which you can then install most ROM
2) its kernel, Overcome Kernel 4.0 comes in ODIN flashable and gives you a CWM Recovery 5.x, which is needed to flash other ROMs
3) When flashed, the kernel performs conversion(and support) of RFS filesystem to EXT4 which is better and faster filesystem. This is sometimes desirable.
Go to overcome site
http://www.teamovercome.net/p1000/
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
But please read it many times until you get what it is saying.
Basically to restock:
Download GB-stock-safe-v5.zip, unzip it and and flash with ODIN according to the guide.
Stop there and you will have Gingerbread JQ1
Next step if you want, just continue following the guide.
Basically flash Overcome Kernel tar using ODIN, and it will reboot and converts your filesystem (you hear female robotic voice).
At the end of it, you get CWM recovery (access it while off : press volume-up and power button)
From CWM recovery you can flash any custom ROM you want.
You will find most of them ask you to flash from CWM.
[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?
please fix dead links
dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.
please fix dead links
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.
[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient
[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone
server stilll unreachable.
As the title says, I have a problem rooting my friends Samsumg Galaxy Tab 8.9.
The model number is GT-P7310.
The Android version is 4.04 Stock (I don't know if stock means the original version, or just untampered with; I say stock because it hasn't been tampered/flashed/root/etc. We just updated it into 4.04 version).
The compilation number is IMM76D.XXLPV.
Total space is ~13GB.
The problem:
I've been browsing this subforum for the last hour, checking the "Root guides" (the main one has been discontinued -> http://forum.xda-developers.com/showthread.php?t=1287205), searching for the problem, with no solid help or hint on what is the solution. I have an idea what needs to be done, I'll get to it:
I've downloaded the root_original.zip file and put it on the root folder, and even created a folder SDCARD and copied it into there.
When I get into recovery mode, it gives these options:
*reboot system now
*apply update from external storage
this gives an error (red) message "E:unknown volume for path [/sdcard] and the recovery mode only allows me to go back to the menu
*wipe data/factory reset
*wipe cache partition
*apply update from cache
I think the problem is either
* The Tablet simply doesnt have an sdcard (which makes sence, we looked for a hole for the SDCard and it doesn't have one, unless we need to take off the whole back of the tablet)
* We have to flash it using ODIN/etc, which the main thread doesnt really mentions anything about it.
I have flashed and rooted my Samsung GIO about a year ago so I can simply check for tips on that thread if I need, but I am wishing that we don't need to flash it.
Thanks for the help.
Flame86 said:
As the title says, I have a problem rooting my friends Samsumg Galaxy Tab 8.9.
The model number is GT-P7310.
The Android version is 4.04 Stock (I don't know if stock means the original version, or just untampered with; I say stock because it hasn't been tampered/flashed/root/etc. We just updated it into 4.04 version).
The compilation number is IMM76D.XXLPV.
Total space is ~13GB.
The problem:
I've been browsing this subforum for the last hour, checking the "Root guides" (the main one has been discontinued -> http://forum.xda-developers.com/showthread.php?t=1287205), searching for the problem, with no solid help or hint on what is the solution. I have an idea what needs to be done, I'll get to it:
I've downloaded the root_original.zip file and put it on the root folder, and even created a folder SDCARD and copied it into there.
When I get into recovery mode, it gives these options:
*reboot system now
*apply update from external storage
this gives an error (red) message "E:unknown volume for path [/sdcard] and the recovery mode only allows me to go back to the menu
*wipe data/factory reset
*wipe cache partition
*apply update from cache
I think the problem is either
* The Tablet simply doesnt have an sdcard (which makes sence, we looked for a hole for the SDCard and it doesn't have one, unless we need to take off the whole back of the tablet)
* We have to flash it using ODIN/etc, which the main thread doesnt really mentions anything about it.
I have flashed and rooted my Samsung GIO about a year ago so I can simply check for tips on that thread if I need, but I am wishing that we don't need to flash it.
Thanks for the help.
Click to expand...
Click to collapse
Stock recovery won't allow you to install the zip. First you need to use odin to flash a custom recovery...both twrp and cwm are available for you device.
For cwm:
http://forum.xda-developers.com/showthread.php?t=1312218
For TWRP:
http://forum.xda-developers.com/showthread.php?t=2602188
The links are the threads with the said recovery images. Download the one for the p7310 and flash via odin. Then reboot to recovery and flash the root.zip that you have on the sdcard.
Note that odin requires you to be in download mode. Hope this helps.
---------- Post added at 09:01 AM ---------- Previous post was at 08:58 AM ----------
And this tablet does not have an external sdcard....you're stuck with whatever internal memory thats included with the device, in your case 16gb but only 13gb or so is available to the user.
Hi all, first time posting here.
Recently i updated my Z3C from kitkat 4.4.4 to 5.1.1 build number 23.4.A.1.200
After a week updated to 5.1.1, i noticed that i couldn't receive any text message / SMS nor send out text message/ SMS.
It always show error message 'couldn't send' whenever i tapped on the send button.
Hence, i disabled the messaging apps can install google messenger app as alternative. Still, the result are same. I am still unable to use the sms function.
I tried with google hangout apps next. I am able to send sms and receive the sms notification. However, when i opened up the hangout apps, i can't see any new sms arrival.
Lastly, as alternative, my fren introduce me to the apps called textra. Fortunately, it worked like a charmed and i am now able to send, receive and view them.
I would like to ask, what is the root cause of the failure of the stock messaging apps and is there anyway to fix it?
Hope to get answer here. If there is any need to provide more info for the case, please let me know.
Thanks in advance.
walafungka said:
Hi all, first time posting here.
Recently i updated my Z3C from kitkat 4.4.4 to 5.1.1 build number 23.4.A.1.200
After a week updated to 5.1.1, i noticed that i couldn't receive any text message / SMS nor send out text message/ SMS.
It always show error message 'couldn't send' whenever i tapped on the send button.
Hence, i disabled the messaging apps can install google messenger app as alternative. Still, the result are same. I am still unable to use the sms function.
I tried with google hangout apps next. I am able to send sms and receive the sms notification. However, when i opened up the hangout apps, i can't see any new sms arrival.
Lastly, as alternative, my fren introduce me to the apps called textra. Fortunately, it worked like a charmed and i am now able to send, receive and view them.
I would like to ask, what is the root cause of the failure of the stock messaging apps and is there anyway to fix it?
Hope to get answer here. If there is any need to provide more info for the case, please let me know.
Thanks in advance.
Click to expand...
Click to collapse
Hi , I encountered this kind of issiue too, and I solved this way.....
just:
Use Flashtool 0.9.19.8 (download the 0.9.19.7 , install it and do not open. Download x10flasher.jar too and put into the installation folder.)
Download and Create new ".FTF" the last update firmware available clicking on XL icon. - HOW TO - make a .ftf and downgrade link.
Using flashtool to downgrade click the two wipes checkboxes on the top-right and say yes when it ask to you for using the FSC Script !
Install new version of PRFcreator 1.1. Put inside files : Your updated .FTF , SuperSu 2.46 flashable and Z3C-lockeddualrecovery2.8.21 flashable. Flag on Kernel, FotaKernel and Modem. So click on Create.
Now ... Root and BackupTA. Close Flashtool (PC-Companion etc .. etc..) during this steps remeber always :
-Enable USB debugging on the phone , Allow mock locations , Work in airplane mode , Allow Applications into Security menu.
Ok, Move flashable-prerooted.zip on SD Card External.
Just to Install Z3C-lockeddualrecovery2.8.21 follow this steps please :
so first go in the "files" of directory Z3C-lockeddualrecovery2.8.21 then press SHIFT + MOUSE RIGHT CLICK and select "open command prompt..."
In the command prompt type "adb shell" then "su" (allow root on the phone if needed) then "mount -o remount,rw /system". That's it, close the prompt window.
start install.bat and follow instructions you should be in TWRP RECOVERY automatically now)
PERFORM A FACTORY RESET & FORMAT DATA , I ADVISE THAT YOU WILL LOOSE ALL YOUR SD INTERNAL DATA !!!
Now Install flashable-prerooted.zip from SD CARD EXTERNAL and reboot.....
This is how I solved .... Now I'm on rooted and fully functional 23.4.A.1.232 Z3 Compact Device.
I'm here... so stay calm , Drink a Coke and start again
carminedev said:
Hi , I encountered this kind of issiue too, and I solved this way.....
just:
Use Flashtool 0.9.19.8 (download the 0.9.19.7 , install it and do not open. Download x10flasher.jar too and put into the installation folder.)
Download and Create new ".FTF" the last update firmware available clicking on XL icon. - HOW TO - make a .ftf and downgrade link.
Using flashtool to downgrade click the two wipes checkboxes on the top-right and say yes when it ask to you for using the FSC Script !
Install new version of PRFcreator 1.1. Put inside files : Your updated .FTF , SuperSu 2.46 flashable and Z3C-lockeddualrecovery2.8.21 flashable. Flag on Kernel, FotaKernel and Modem. So click on Create.
Now ... Root and BackupTA. Close Flashtool (PC-Companion etc .. etc..) during this steps remeber always :
-Enable USB debugging on the phone , Allow mock locations , Work in airplane mode , Allow Applications into Security menu.
Ok, Move flashable-prerooted.zip on SD Card External.
Just to Install Z3C-lockeddualrecovery2.8.21 follow this steps please :
so first go in the "files" of directory Z3C-lockeddualrecovery2.8.21 then press SHIFT + MOUSE RIGHT CLICK and select "open command prompt..."
In the command prompt type "adb shell" then "su" (allow root on the phone if needed) then "mount -o remount,rw /system". That's it, close the prompt window.
start install.bat and follow instructions you should be in TWRP RECOVERY automatically now)
PERFORM A FACTORY RESET & FORMAT DATA , I ADVISE THAT YOU WILL LOOSE ALL YOUR SD INTERNAL DATA !!!
Now Install flashable-prerooted.zip from SD CARD EXTERNAL and reboot.....
This is how I solved .... Now I'm on rooted and fully functional 23.4.A.1.232 Z3 Compact Device.
I'm here... so stay calm , Drink a Coke and start again
Click to expand...
Click to collapse
thanks for your detailed post! i will apply this method next month as i need to send my phone for warranty next week to replace my spoiled heaphone jack
if i can't root my phone due to warranty issue (till i finish claim my warranty), is there any other alternative without root?
Thanks.
walafungka said:
thanks for your detailed post! i will apply this method next month as i need to send my phone for warranty next week to replace my spoiled heaphone jack
if i can't root my phone due to warranty issue (till i finish claim my warranty), is there any other alternative without root?
Thanks.
Click to expand...
Click to collapse
You can root your Z3 Compact without loose warranty.... anyhow sorry for confusion just tought you was on rooted phone.
So install Sony PC-Companion there's a new firmware update 23.4.A.1.232 click on Support Zone and choose Update or Repair and follow the "User Friendly" steps
I suggest to you just to change build updating your device.
carminedev said:
Hi , I encountered this kind of issiue too, and I solved this way.....
just:
Use Flashtool 0.9.19.8 (download the 0.9.19.7 , install it and do not open. Download x10flasher.jar too and put into the installation folder.)
Download and Create new ".FTF" the last update firmware available clicking on XL icon. - HOW TO - make a .ftf and downgrade link.
Using flashtool to downgrade click the two wipes checkboxes on the top-right and say yes when it ask to you for using the FSC Script !
Install new version of PRFcreator 1.1. Put inside files : Your updated .FTF , SuperSu 2.46 flashable and Z3C-lockeddualrecovery2.8.21 flashable. Flag on Kernel, FotaKernel and Modem. So click on Create.
Now ... Root and BackupTA. Close Flashtool (PC-Companion etc .. etc..) during this steps remeber always :
-Enable USB debugging on the phone , Allow mock locations , Work in airplane mode , Allow Applications into Security menu.
Ok, Move flashable-prerooted.zip on SD Card External.
Just to Install Z3C-lockeddualrecovery2.8.21 follow this steps please :
so first go in the "files" of directory Z3C-lockeddualrecovery2.8.21 then press SHIFT + MOUSE RIGHT CLICK and select "open command prompt..."
In the command prompt type "adb shell" then "su" (allow root on the phone if needed) then "mount -o remount,rw /system". That's it, close the prompt window.
start install.bat and follow instructions you should be in TWRP RECOVERY automatically now)
PERFORM A FACTORY RESET & FORMAT DATA , I ADVISE THAT YOU WILL LOOSE ALL YOUR SD INTERNAL DATA !!!
Now Install flashable-prerooted.zip from SD CARD EXTERNAL and reboot.....
This is how I solved .... Now I'm on rooted and fully functional 23.4.A.1.232 Z3 Compact Device.
I'm here... so stay calm , Drink a Coke and start again
Click to expand...
Click to collapse
please use TWRP for install...!!! don't used CWM Philz
Never used...
- Tapatalk -
walafungka said:
Hi all, first time posting here.
Recently i updated my Z3C from kitkat 4.4.4 to 5.1.1 build number 23.4.A.1.200
After a week updated to 5.1.1, i noticed that i couldn't receive any text message / SMS nor send out text message/ SMS.
It always show error message 'couldn't send' whenever i tapped on the send button.
Hence, i disabled the messaging apps can install google messenger app as alternative. Still, the result are same. I am still unable to use the sms function.
I tried with google hangout apps next. I am able to send sms and receive the sms notification. However, when i opened up the hangout apps, i can't see any new sms arrival.
Lastly, as alternative, my fren introduce me to the apps called textra. Fortunately, it worked like a charmed and i am now able to send, receive and view them.
I would like to ask, what is the root cause of the failure of the stock messaging apps and is there anyway to fix it?
Hope to get answer here. If there is any need to provide more info for the case, please let me know.
Thanks in advance.
Click to expand...
Click to collapse
Did you find a solution to this?
I answered the same question at least 4 times. Just use the search feature..
WieserZ1C said:
Flash back to 4.4.4 ( i used .93 fw ) , root and install xzdr , create a new flashable rom with prf creator 1.1 ( None Below! ) including fotakernel kernel and modem. Wipe data, do a factory reset via TWRP And flash the newly created clean rom.
Seems prf creator 1.0 wasnt able to handle the modem files... :/
Click to expand...
Click to collapse
WieserZ1C said:
Hangouts figures to work, but in fact it doesn't. You can recognise it by switching back to stock messaging app, then the "send" SMS are gone. The solution I gave already. That's the simplest way to fix it with Bootloader locked, otherwise root will be lost. UB devices should fix it by flashing the actually used fw by flashtool with a full wipe, flashing a kernel with including recovery. Now just flash the latest SuperSU via recovery
Click to expand...
Click to collapse
Thank you, carminedev. I had the same problem and these steps solved it