Related
Hey guys,
I a long time IOS user and just moved over to the Android family. I just purchased my S3 from ATT yesterday. Came home, did the OTA update and went to root it.
I just found out that the new OTA prevents you from installing CWM and rooting the traditional ways. So my question is, what is my option to get my phone rooted? I wanna remain on the stock ROM but, just clean it out a little from all the bloatware, use google wallet and be able to tweak some things around.
Any help would be greatly appreciated. Thanks
I THINK the ota can be rooted through the toolkit...pretty sure I read that before. Maybe someone can confirm that.
Sent from my SGH-I747 using xda premium
I'm pretty sure the toolkit can do it. Option 4 (I think ... the last option at least) will walk you through using Odin to flash a custom recovery and then flashing a zip file in recovery to root your device.
You may find that when you reboot your custom recovery will be replaced with stock recovery. The OTA includes a script that's run on boot to reset recovery to stock. If that happens to you, then make sure that when you use Odin to flash the custom recovery you don't let Odin reboot your phone. When the flash is done, pull the battery or press and hold power and Vol Up until the phone turns off, then press Vol Up, Power, and Home to get into recovery. Then flash the zip to root your device.
Once you reboot your phone, you can remove /system/recovery-from-boot.p and /etc/install-recovery.sh. You may need to install a custom recovery one more time, but it should stick.
I've had my phone for a year now. I've hit the internal memory limit thanks to the app updates and I'm getting really sick of the performance issues.
I've been wanting to root for a while but thanks to .62 being nigh unrootable by normal methods (including unlockroot.com), I'm stuck trying to figure out the instructions for flashing which for some reason are incomprehensible to me. I appreciate FMA965's efforts to explain things as much as possible, but I'm still lost on a few things and hope you guys can help.
My first attempt at using Flashtool nearly ended in disaster. There wasn't anywhere mentioning specifically what flashing is and that flashing the firmware wipes the phone. I did back up so the losses were minimal (just my notes and some progress on a game in FPSe either because I forgot to backup or the backup function was screwy). I tried flashing a second time and that seemed to have bricked the phone somewhat, but I managed to restore it back to stock.
It seems the stock firmwares I downloaded weren't properly recognized by Flashtool. I thought I was flashing into .42 or .58 but only the .62 I got for recovery was being recognized.
Also, how do I know if I have the correct USB drivers installed? Currently all the softwares I tried (Flashtool, unlockroot, SuperOneClick and the SE PC Companion) recognize my phone. Am I done with that part or am I missing something? Also, how do I know which stock roms are compatible with my phone? I'm not very knowledgeable about custom roms, so I'd rather just stick with a rooted stock so I can at least get rid of the bloatware and free up precious memory.
After tons of google searching in and out of the board I've seen several methods but there's always one or several steps that I have no idea how to do (for the record, I checked and it seems I can unlock the bootloader or my R800i):
1- Clockwork Recover Mod before FMA965's guides a lot of people were pointing to this as the way to root the Play 0.62. I can't find any instructions on how to apply this thing.
2- The ADB/SDK force SD card install method. Does this method make anything get installed on the SD card regardless of root? Or does it just put the stuff that can already be moved so you don't have to do it manually?
3- How to root 2011 Xperia range. "For this guide i will be using official firmware xx.xx.xx.62 which will be flashed via wotan."<-- I do not understand this step. Why does .62 need to be flashed and why by wotan? What is fastboot and why do I need to do that?
4- Doomlord's Advanced Stock Kernel. When everyone is talking about Doomlord's ASK, is that what they are referring to?
5- Root and Install CyanogenMod7 after Unlock Your Bootloader. Does this method still work?
So right now that's about 3 methods to root but I unsuccessfully tried one and can't figure out the other two.
Appreciate any help in sorting out this confusion.
If you can unlock your bootloader, I think the easiest way is probably to go ahead and do that first, then you can follow the instructions to install the Gin2JB Rom here which I find is the fastest one around and the process is very simple. You will need to install the Lupus kernel here.
Thanks, but that step requires flashing, which is still a process I'm having trouble with due to incompatible stock firmware roms.
AceWhatever said:
Thanks, but that step requires flashing, which is still a process I'm having trouble with due to incompatible stock firmware roms.
Click to expand...
Click to collapse
you mean you are having troubling flashing kernel or flashing the stock image using flashtools ?
The easiest way to root ANY Android device, running ANY verison / firmware, is to boot into recovery and flash a superuser.zip
In the case for the Xperia Play, you can easily have your bootloader unlocked, and use fastboot to flash a custom kernel and boot recovery or use fastboot to boot a recovery.img , either method , then just flash the superuser .zip like normal and BAM your rooted
216Monster said:
The easiest way to root ANY Android device, running ANY verison / firmware, is to boot into recovery and flash a superuser.zip
In the case for the Xperia Play, you can easily have your bootloader unlocked, and use fastboot to flash a custom kernel and boot recovery or use fastboot to boot a recovery.img , either method , then just flash the superuser .zip like normal and BAM your rooted
Click to expand...
Click to collapse
Yeah that's what I would do.
Sent from my R800i using Tapatalk 2
See, this is why it's so confusing.
You guys just mixed steps from like 3 different tutorials. Will this wipe my phone like flashing a rom? And can I use a custom kernel with a stock rom?
Lemme try to piece this together:
I unlock the bootloader. Then I grab the fastboot package from this thread and extract it to the PC. Shift + Right Click the folder and press "Open Command Window Here", then I run the run_me.bat file then I turn off my phone, plug the USB and hold the search button to go into fastboot. Did I get that right so far?
Where do I get recovery.img and superuser.zip and where do I put them? The SD card?
Here are some instructions for if you want stock firmware, kernel and all. If you want to change the kernel and/or rom, I'll add such instructions upon request.
Turn your phone off with the battery intact.
Go download an older firmware from here (you'll have to scroll down quite a bit).
Place the .ftf file in "C:\Flashtool\firmwares" or wherever your flashtool installation is.
Open Flashtool (as administrator if option is available).
Click on the lightning icon and click 'OK' on the following pop-up.
On the left of this new menu, highlight your downloaded .ftf (it should read somewhere along the lines of "|R800i |4.0.2.A.0.XX | -Name of vendor or region goes here- ). On the right, leave all settings as they are except "Wipe data" which you must uncheck. Now click 'OK'.
Wait for the menu instructing you to plug the phone in. Do so: insert the usb of the turned off phone while holding down the back (leftmost) key. Please note that if the menu does not vanish upon doing this then you do not have the required drivers.
Wait while Flashtool does its job. You will know that it's done when the text "Device disconnected" appears in the program window.
Disconnect the phone and turn it on.
If you followed the instructions properly, the phone should boot into the older version with all downloaded apps, data and settings intact.
Insert USB.
Follow instructions here.
There you are. It's rooted. There may be certain apps missing; these are usually preinstalled apps that were on your system partition which was formatted during the flashing process.
AceWhatever said:
See, this is why it's so confusing.
You guys just mixed steps from like 3 different tutorials. Will this wipe my phone like flashing a rom? And can I use a custom kernel with a stock rom?
Lemme try to piece this together:
I unlock the bootloader. Then I grab the fastboot package from this thread and extract it to the PC. Shift + Right Click the folder and press "Open Command Window Here", then I run the run_me.bat file then I turn off my phone, plug the USB and hold the search button to go into fastboot. Did I get that right so far?
Where do I get recovery.img and superuser.zip and where do I put them? The SD card?
Click to expand...
Click to collapse
You have it right indeed. First thing i would flash the 4.0.2.A.0.62 FTF file using FlashTool (flashtool can be found in the development section, first or second thread) after it is done and If your boot loader is unlocked, go to the LuPus v7 for Gingerbread thread (also in the development section) download his kernel, then to make it easier, rename the file "boot.img" now plug your phone in USB for fast boot mode, and in the command window type " fastboot flash boot boot.img" When it is done unplug and power it on, when the notification lite turns blue press up or down (up or down will indicate which "recovery" version you want to enter) once in recovery choose "instal from SD card" and select the superuser.zip and instal it. You can find the superuser.zip in a few places, but Wedgess made it easy, its also in the LuPus v7 for Gingerbread thread so you can download it from there. Then reboot and your rooted with running 2.3.4!
It seems like a lot I suppose but once you a familiar with it, it becomes second nature, once you get that down, your ready to give some custom roms a try, the developers in the xperia play forums have done some nice work!
Sent from my R800at
Thanks, but like I explained before I don't understand why the .62 needs to be flashed and I'm having trouble finding stocks that are recognized by Flashtool on my R800i. Is there a region independent .62 or .58 I can use?
Flashing the stock ROM (.62) will wipe everything, it's more like a factory reset and will make it the pure original Xperia Play ROM, meaning that there will be nothing that could cause problems when installing custom ROMs on top of it. There's a link of stock .ftf files in the "official firmware" section here, see if you can flash R800i_4.0.2.A.0.62_phoenixvendor.ftf onto your Play with flashtool, as when you also flash a custom kernal later, this will unlock some hidden internal space.
On the other hand, have you managed to unlock the bootloader using Sony's official method (that you linked in #7)?
Yes. That was luckily the easiest step.
After much fidgeting around and cross comparing instructions, I finally managed to root the damn thing. I would have preferred not install a custom kernel without fully understanding what it does but I was getting impatient and everything seems to be working fine so far so no problems there. Feels good to finally be able to use Titanium Backup to toss all that stupid bloatware out.
Thanks to everyone who helped! :good:
So I'm assuming that in the future any updates or replacements to the kernel or the need to install a custom ROM will require wiping everything all over again? It's not a huge hindrance to me since I don't have a lot of apps and data restoration is simple, but I figure that since this is an almost weekly/monthly thing for some people here is there some kind of method to batch restore all your data and settings in a few steps?
Ok. I have seen several people asking about rooting their T-Mobile Note 3. I am sure there have been posts on how to accomplish this feat. I am going to put out the steps that I took and mention a few other options and my thoughts on those. I hope to make this an all inclusive post for newbies. This method works whether you are on 4.3 or 4.4 BUT you will need to make sure the recovery and ROM you download is for the correct version of android you are using. To make this easier I am going to assume you are already on 4.4 Not everything will be clear but should be able to be easily understood. If there is something you don't understand ask and I am sure people will try to help. That or you can do a google search and probably find the answer a whole lot faster. If you did have a problem and found the solution please post it so others can use your information. I don't have the time at the moment to provide all the links but I will try to update this thread as much as I can.
I am NOT responsible for bricked devices, voided warranties or downloaded virus to your computer.
That being said rooting should be a relatively simple and easy process.
1. Download Odin 3.07 or 3.09 .zip file and install on your computer. (I have found no real difference in between the two when attempting root.) (No link provided just google it.)
2. Download the custom recovery of you choice. (I use and prefer twrp, but some people have had problems flashing ROMs and have had better luck with philz recovery) Below is the link for TWRP. If using 4.4 make sure to download the img.tar file for 2.7. There are other files but you want the one ending in img.tar! http://teamw.in/project/twrp2
3. Open Odin and connect your phone. You need to put your phone into download mode before connecting. Shut your phone off and then turn back on while holding volume down, power and home key. You will see a special screen pop up and a warning. Acknowledge the warning and the connect to the computer. If you don't get a blue bar on the left side of Odin after connecting your phone then you need to update your driver's (google search).
4. Place the .tar file that you downloaded into the PDA(3.07) or AP(3.09) section. Make sure the ONLY boxes on the left are Auto Reboot and F. Reset Time are checked (that should be the default settings)!!
5. Hit the start button. Be advised that Flashing a custom recovery WILL trip Knox.
6. You should the blue bar turn green and say "pass." You know have a custom recovery on your phone and you can disconnect your phone.
At this point you do not have root access, you just have a custom recovery. You now have a choice to make. Do you want your phone rooted or do you want to flash a custom ROM. If you want to flash a custom ROM jump to #8. If you just want root and plan on staying on stock go to #7.
7. Download the latest version of SuperSU file from http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash from your custom recovery. when you restart your phone make sure you can open the SuperSU app. If you cannot go to the play store and reinstall it from there. Congrats!!
8. If you want a custom ROM you need to download the .zip file of that ROM. I would recommend placing it on your EXTERNAL sd card.
9. Go to your custom recovery. There are some things you are going to need to back up prior to Flashing the ROM.
a. Backup your stock ROM, This could save you from some major problems. Back up-system, data and boot-to your EXTERNAL sd card.
b. Backup you EFS files (this can be done via twrp, other wise you will need to do it another way-Google search)
10. Wipe the phone. You want to wipe Data, Cache and Dalvik
11. Flash you custom ROM. Almost every custom ROM comes rooted. You just need to read the info on that ROM
12. Your phone should reboot and you are done!!
Below is some Q&A and helpful tips.
If I upgrade to 4.4 from 4.3 to get a diffent ROM can I switch back? NO
What is "Bricked"? It is a phone that will not boot and only stays on a black screen. Soft Brick is where your phone constantly reboots without opening your ROM.
What is Knox? Google it
Will tripping Knox void my warranty? Probably
How do I get into the recovery? Shut your phone off and then restart while holding the volume up, power and home key. You have to let go as soon as you see the blue letters "Recovery Booting"
There are not that many ROMS for T-mobile can I use an international ROM? Yes! I currently run an international ROM but on most of them you do loose your wifi calling feature. You also need to download a custom T-Mobile Kernel and the Wifi/BT fix.
Should I use CF Auto root or Klingo? I personally don't like the idea of Klingo. Some of the things I have seen they appear to be a little fishy and with them rooting your phone they initially have access to EVERYTHING. CF auto root does not place a custom recovery. You CANNOT flash a custom ROM without a custom recovery. I did it my way because I wanted a custom ROM and just not root.
What about the De La Vega Method? I have no idea and it seemed more work that it was worth. I did not care about tripping Knox
Tips:
Some ROMS will delete your internal memory when flashing as will wiping your phone. That is why I strongly suggest placing the backups and ROMS on your external sd card.
Some ROMS come with an Auroma set up. You will automatically be directed into it when you flash from recovery.
If you are flashing an international ROM make sure that you flash the ROM, T-mobile Kernel and Wifi Fix before choosing the reboot option. If you don't have the t-mobile kernel prior to reboot you will go into a bootloop.
I hope this helps and I will add more and clarify this post in the next few days. I just hope this can help some of you new guys out a little bit and if you found it useful especially if you obtained root please hit the thanks meter.
OK, I deleted all the information here about all the errors I made so that this won't confuse anyone. To summarize my error, I thought I had purchased Android 4.4.2 and flashed the wrong versions. After flashing the correct version, 4.3, everything worked.
The SD-card is not visible in stock recovery and the ADB method won't work without first having root, so that leaves the Odin method.
The Odin method flashes TWRP recovery successfully and when I exited it asked me if I wanted to root the device. I chose 'yes' and it worked for a while then booted into the Android OS. In Android it booted normally, then after I did something which I did not think about and don't recall, a dialog advised me that the GUI portion of the root process still needed to be applied. I allowed it to proceed and now I am rooted with TWRP. I verified the root through ADB by creating a file in the root directory.
Frank
I will try to break this down for you.
1. You need to reflash twrp via Odin to make sure it works correctly since doing auto root.
2. That screen you saw is exactly what you wanted to see. As stated in the OP when you see that screen let go of the buttons and wait, twrp will open shortly. I get the same screen so don't worry. Once you get into twrp and if you need a tutorial on twrp I would suggest looking it up on YouTube.
3. If you reflash the stock ROM via Odin it should fix everything. I am not sure about the partition problem. I will get back if I get some more info.
I would not worry about trying to reflash stock. I would just reflash twrp, boot into recovery and then proceed as listed in the OP.
Frank Westlake said:
**************************************************************************
I found my problem. I think the box, or something, was mislabeled because "About" tells me I have Android 4.3, not 4.4.2. So I flashed the 4.3 version of TWRP and booted right into it. After another reboot to make sure it's stable I'll try rooting again.
Frank
Click to expand...
Click to collapse
Great. Yes, it did not work because 2.7 is written for the new bootloader in 4.4. Are you planning on staying stock jb or planning on flashing a ROM?
sm-n900t: Powered by X-Note V13
FFTony said:
Are you planning on staying stock jb or planning on flashing a ROM?
Click to expand...
Click to collapse
Stock. With root I'm able to customize everything right on the device about as much as the ROM builders. But there are things I cannot do on the device so I'll be keeping an eye on the ROMs to see if anything is attractive.
After I finished this update I refreshed this page and saw that you had been commenting. The screen you saw should be there was also there when I flashed the correct TWRP, and it did move on to TWRP as you said. I'm adding the following paragraph separately so that it's easier for people to find if they need it:
After I had flashed the wrong version of TWRP (4.4 instead of 4.3) it boot-looped to the "SEANDROID NOT ENFORCING" display. To get out of that boot-loop I held the Download Mode keys (HOME-POWER-VOLDOWN) until it rebooted into the first download mode screen, the warning which says you can press VOL-DOWN to boot normally. At that point press VOL-DOWN and it will boot normally. If you press VOL-UP and continue into Download Mode then you will still be in the boot-loop when you reset the device and you will need to reboot again into the Download Mode warning screen and press VOL-DOWN to boot normally.
Thank you very much for your help with this.
Frank
FFTony said:
What about the De La Vega Method? I have no idea and it seemed more work that it was worth.
Click to expand...
Click to collapse
Samsung explains about Root De La Vega here: Samsungknox.com/en/blog/about-root-de-la-vega
So I flashed cm 10.2 on my Galaxy S3 AT&T, and forgot to flash the right gapps, so I did that, except I forgot to do a factory reset when I flashed them. When I went to reboot, my phone would not turn on, nor get into recovery mode. It keeps showing the Samsung logo with the little CyanogenMod figure underneath it, and keeps vibrating repeatedly while trying to turn on. This is not a boot loop (I think) because my phone doesnt even get as far as the arrow animation that keeps going in circles. All I can do is access download mode. Can anyone help me? I have tried taking the battery out multple times and waiting for the battery to charge and then trying to turn it on, to no success.
rohanr014 said:
So I flashed cm 10.2 on my Galaxy S3 AT&T, and forgot to flash the right gapps, so I did that, except I forgot to do a factory reset when I flashed them. When I went to reboot, my phone would not turn on, nor get into recovery mode. It keeps showing the Samsung logo with the little CyanogenMod figure underneath it, and keeps vibrating repeatedly while trying to turn on. This is not a boot loop (I think) because my phone doesnt even get as far as the arrow animation that keeps going in circles. All I can do is access download mode. Can anyone help me? I have tried taking the battery out multple times and waiting for the battery to charge and then trying to turn it on, to no success.
Click to expand...
Click to collapse
If you can get to download mode, try flashing a stock file via Odin to reset your phone to working conditions. Thereafter, you can go back to a custom ROM. Would you recall what firmware version you were on prior to flashing CM? If it was anything older than 4.3 (e.g. 4.1.2, 4.1.1), you can Odin back to 4.1.1. If you already had 4.3, you would need to Odin back to 4.3 following the instructions posted in the thread below ..
http://forum.xda-developers.com/showthread.php?t=2722660&page=3. Scroll through carefully for the file you need for 4.3. Otherwise, you can find the Odin flash-able 4.1.1 stock file on sammobile.com
Larry2999 said:
If you can get to download mode, try flashing a stock file via Odin to reset your phone to working conditions. Thereafter, you can go back to a custom ROM. Would you recall what firmware version you were on prior to flashing CM? If it was anything older than 4.3 (e.g. 4.1.2, 4.1.1), you can Odin back to 4.1.1. If you already had 4.3, you would need to Odin back to 4.3 following the instructions posted in the thread below ..
http://forum.xda-developers.com/showthread.php?t=2722660&page=3. Scroll through carefully for the file you need for 4.3. Otherwise, you can find the Odin flash-able 4.1.1 stock file on sammobile.com
Click to expand...
Click to collapse
I have looked at the thread but I am new to all this stuff, how do I flash using Odin?
rohanr014 said:
I have looked at the thread but I am new to all this stuff, how do I flash using Odin?
Click to expand...
Click to collapse
First you will need to download and extract the Odin tool. Odin is Samsung's tool for flashing (installing) firmware. You can download Odin v3.07 via the link below ...
http://www.mediafire.com/download/772dlmuaxfgm0x2/Odin307.zip
Once you have downloaded it, extract the files and look for the executable file (*.exe). That's the one you will need to run to open Odin.
We also need to identify the appropriate firmware to flash. You did not answer the earlier question on what Android version your device was on prior to flashing the custom firmware. This is important to let us know which official version you can safely revert to (4.1.1 or 4.3). If you were an older version than 4.3, you should flash 4.1.1 but if you were already on 4.3, then you should stick to this. Either way, you can download the 4.1.1 file via this link .. http://rapidgator.net/file/681a28a5...ATT_I747UCDLK3_I747ATTDLK3_Original.zip.html?
Download the files to your PC and extract.
To flash via Odin, open Odin.exe on your PC
Click on the PDA tab and navigate to the file you just extracted. Select the file ending in *.tar.md5 (For 4.1.1, this would be I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5). Make sure this file is showing in the PDA tab.
Boot your phone into download mode and connect to your computer with a good quality micro-USB cable. Make sure your phone is recognized by Odin. You should see the message Added in the left pane.
Do not check or uncheck any boxes other than the defaults.
Click on start and waiting for firmware flashing to end and you see Pass. Your phone will reboot at this stage. You can disconnect from your PC
However, for 4.3, it looks like the Odin flash-able file has been taken offline so you would need to this via custom recovery. That's a different process so please revert on your Android version first so we'll know whether this is required or not
I was running JB 4.3, and I am planning to flash 4.1.1 as you've said. I am downloading that rom from the SamMobile site, however it is taking quite a while...
I understand that it shouldnt be a two minute download, however its been 2 hours and only 210 MB has been downloaded.
Also, I have Odin v3.09, which in the place of a PDA tab, there is an AP tab... should I place the file in the AP tab?
rohanr014 said:
I was running JB 4.3, and I am planning to flash 4.1.1 as you've said. I am downloading that rom from the SamMobile site, however it is taking quite a while...
I understand that it shouldnt be a two minute download, however its been 2 hours and only 210 MB has been downloaded.
Also, I have Odin v3.09, which in the place of a PDA tab, there is an AP tab... should I place the file in the AP tab?
Click to expand...
Click to collapse
Please do not try to flash 4.1.1 if you were on JB 4.3 otherwise you could hard brick your phone due to the secure bootloader in 4.3. You need to revert to stock 4.3 via custom recovery. You may go to the thread below for instructions...
http://forum.xda-developers.com/showthread.php?t=2658486
1) Flash custom recovery (I would suggest TWRP because of the GUI). In Odin v3.09 use the AP tab in place of PDA. You can download TWRP for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore zip file in the thread above and copy to your (micro) SD card. The (TWRP) stock restore zip is also available via the following link .... http://www.mediafire.com/download/30idxwhg2hidxx2/ATT_I747_UCUEMJB_StockRestore_2282014.zip
3) Flash the custom recovery file via Odin. Remove battery immediately the flashing is complete to stop reboot.
4) Place the SD card with the recovery file in your phone
5) Reboot into recovery mode by simultaneously holding down the Volume Up, Home and Power buttons. Hold all buttons until you see the blue flash across your screen, then release power button but keep holding the volume up and home buttons until the Android image appears.
6) Select install and navigate to the stock restore file. Swipe across screen to flash and wait for installation to be complete.
7) Clear cache/dalvik and reboot to system
If you are unable to boot to recovery, then you may still try flashing using Odin v3.09. You may follow the instructions in the thread below and load all the respective partitions. You would need to use the version that has separate flashable files as the single *.tar file has been taken down.
Larry2999 said:
Please do not try to flash 4.1.1 if you were on JB 4.3 otherwise you could hard brick your phone due to the secure bootloader in 4.3. You need to revert to stock 4.3 via custom recovery. You may go to the thread below for instructions...
http://forum.xda-developers.com/showthread.php?t=2658486
1) Flash custom recovery (I would suggest TWRP because of the GUI). In Odin v3.09 use the AP tab in place of PDA. You can download TWRP for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore zip file in the thread above and copy to your (micro) SD card. The (TWRP) stock restore zip is also available via the following link .... http://www.mediafire.com/download/30idxwhg2hidxx2/ATT_I747_UCUEMJB_StockRestore_2282014.zip
3) Flash the custom recovery file via Odin. Remove battery immediately the flashing is complete to stop reboot.
4) Place the SD card with the recovery file in your phone
5) Reboot into recovery mode by simultaneously holding down the Volume Up, Home and Power buttons. Hold all buttons until you see the blue flash across your screen, then release power button but keep holding the volume up and home buttons until the Android image appears.
6) Select install and navigate to the stock restore file. Swipe across screen to flash and wait for installation to be complete.
7) Clear cache/dalvik and reboot to system
If you are unable to boot to recovery, then you may still try flashing using Odin v3.09. You may follow the instructions in the thread below and load all the respective partitions. You would need to use the version that has separate flashable files as the single *.tar file has been taken down.
Click to expand...
Click to collapse
Just to reaffirm since I am not very experienced and do not wish to break my phone:
1) Download the twrp 2.6.3.1 d2att.tar file and flash it to my phone in download mode via Odin.
2)Download zip file on my computer, and take out the microSD from my phone, and copy the file to my microSD.
3) I am confused here because you stated to flash the custom recovery in step 1... anyways when flash is complete I immediately take my battery out to stop the reboot.
4) I insert the microSD with the zip file containing the stock rom
5) Now I should be able to reboot into recovery mode on my phone, though I could not beforehand.
6) Once in Recovery, go to Install and flash the custom stock.
7)Wipe dalvik cache and cache, and reboot to system.
Please clear up any confusion, I am very cautious and inexperienced. Sorry.
rohanr014 said:
Just to reaffirm since I am not very experienced and do not wish to break my phone:
1) Download the twrp 2.6.3.1 d2att.tar file and flash it to my phone in download mode via Odin.
2)Download zip file on my computer, and take out the microSD from my phone, and copy the file to my microSD.
3) I am confused here because you stated to flash the custom recovery in step 1... anyways when flash is complete I immediately take my battery out to stop the reboot.
4) I insert the microSD with the zip file containing the stock rom
5) Now I should be able to reboot into recovery mode on my phone, though I could not beforehand.
6) Once in Recovery, go to Install and flash the custom stock.
7)Wipe dalvik cache and cache, and reboot to system.
Please clear up any confusion, I am very cautious and inexperienced. Sorry.
Click to expand...
Click to collapse
Yes, you are correct. What you are doing in step 1) is flashing custom recovery to your phone. Custom recovery allows you install zip files to your phone and is more functional and versatile than stock recovery.
The zip file referred to in 2) is the stock restore zip. This is the file you will be flashing from (custom) recovery and is the one from the following link (http://www.mediafire.com/download/30...re_2282014.zip). Once you have downloaded it to your computer, save to an SD card so you can insert it into your phone to flash.
The battery pull is after flashing the TWRP file. You then have to boot into (custom) recovery mode to flash the stock restore zip from the SD card.
You are OK on the other steps. Trust this clarifies. Let me know if you encounter any issues.
I have done everything you said, I flashed the TWRP file via Odin, and then i copied the stock zip file to my microSD and put it back into my phone.
I am able to boot into recovery, and everytime I go to flash the stock rom, midway through the flash my phone starts rebooting. Even if I try to clear dalvik cache and cache first, once they are cleared my phone automatically starts rebooting. What do I do now? The zip file is there and I can reach TWRP recovery, but the flash wont complete because my phone starts rebooting. I am at a 100% battery right now so I do not know what the cause of this could be. Please help, I cannot tell what I did wrong if I did do anything wrong.
Try installing the latest version of Philz Touch for the d2lte. Some people have good results with TWRP. I found Philz Touch, which is based on CWM, better for my purposes. Philz can be installed via Odin as long as you down the tar version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Larry2999 said:
Yes, you are correct. What you are doing in step 1) is flashing custom recovery to your phone. Custom recovery allows you install zip files to your phone and is more functional and versatile than stock recovery.
The zip file referred to in 2) is the stock restore zip. This is the file you will be flashing from (custom) recovery and is the one from the following link (http://www.mediafire.com/download/30...re_2282014.zip). Once you have downloaded it to your computer, save to an SD card so you can insert it into your phone to flash.
The battery pull is after flashing the TWRP file. You then have to boot into (custom) recovery mode to flash the stock restore zip from the SD card.
You are OK on the other steps. Trust this clarifies. Let me know if you encounter any issues.
Click to expand...
Click to collapse
Ok, something very strange has occured.
Since my phone would not flash the original stock rom, I decided to go ahead and flash CM10.2 and its gapps to see if it the problem was with my phone or with the file. Everything worked fine and my phone booted and ran CM10.2, but then I had absolutely no signal anywhere. I could confirm something was wrong because there were multiple AT&T users near me that had good signal. So then I went to flash the stock rom, and it worked. I cleared dalvik and cache like normal after all these flashes and performed factory resets, however when I flashed this stock rom, it worked but 1) I could not connect to Wifi 2) I could not use apps with root requirements, and Root Checker said I did not have root access, even though I had definitely rooted my phone earlier when I first ran CM11 and CM10.2
Should I root again? Please help, my phone is working and I can go into download, stock recovery, and normal mode.
audit13 said:
Try installing the latest version of Philz Touch for the d2lte. Some people have good results with TWRP. I found Philz Touch, which is based on CWM, better for my purposes. Philz can be installed via Odin as long as you down the tar version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Click to expand...
Click to collapse
The whole idea was to get your phone back to working state. Thereafter, you can build up on the food chain. The stock file you flashed restores the phone to near factory settings including a complete stock (official) firmware, stock recovery, resetting the flash counter. Unfortunately, it also removes root as well. You can, however, re-root in a number of ways. You may also do as Audit advised and reflash Philz Touch custom recovery which would allow you flash any custom ROM of your choice. You do not necessarily need to root to flash custom ROMs if you have custom recovery. However, if you need to use apps which require root, I would recommend you try SafeRoot (http://forum.xda-developers.com/showthread.php?t=2565758). Very easy to use and worked quite well for me.
Finally, you should be able to restore your Wi-Fi from settings. Wi-Fi setup should have happened during the set-up process upon reboot after the firmware installation but sometimes this step is skipped. If you go to Settings, you should be able to enable and set up Wi-Fi.
Recently tried to root my Samsung Galaxy Tab S (I am not allowed to post links yet so I'll just say the site is techbeasts)
I believe I went through these instructions and followed them all precisely.
This method also installs SuperSU on my device..
However, I tried checking the root status with Root Checker, and it says "verification failed"
I then checked SuperSU, and it said something along the lines of "binary needs updating". I tried the "normal" method for doing this twice, but it didn't seem to work. There is an option presented in SuperSU to do this through TWRM or CWM, so I tried that option. ( NOTE I do NOT have TWRM or CWM installed)
**Then when I started the tablet, a whole bunch of messages came up saying "unfortunately, ____ stopped" [/B]and a whole bunch of these are there. I'm sure this is a crash.... **
I managed to get the tablet back to semi-working state by using the factory reset from the recovery partition (it's the stock recovery partition). However, the crash-on-reboot problem still persists.
Any help on getting back to working state? I can use the tablet but I cannot restart it as it will crash again (have had to do the factory reset from recovery twice now...)
I should mention that i am trying to:
1) have a rooted tablet
2) Not have these crash-on-reboot issues...
Bharat
Best would be to flash your firmware again with Odin. You can download your firmware on sammobile (see link below).
You will need Odin for this, the correct drivers on your pc and to have USB Debugging on (under Developer options in Settings).
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
Download supersu.zip as well (see link below, you can download 2.46 or 2.49 beta) and put it on the tablet or external sd card.
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
http://www.sammobile.com/firmwares/database/SM-T800/
http://forum.xda-developers.com/showthread.php?t=1538053
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Good luck!
Wow, how to massively over complicate something.
Just install the stock firmware, then look for my build of cf_autoroot in the dev section, flash in ODIN. Done.
If you want to upgrade twrp to the latest version you will find it in the dev section too. This version fixes some of the issues with the official version and has more options.
Hi guys,
TThanks so much for your replies! Complicated or not, anything helps...
I had previously used Odin to flash the rooted firmware to the tablet, so I amn faniline with the software.
Alta1r: looked at the links and it looks like sprue stock firmware. A couple of questions about this procedure:
1) Is it normal that the stock firmware file (as downloaded) is larger than firmware images used to root the tablet?
2) Would using TWRP to flash Supersu onto the tablet root the tablet, even if the stock firmware is installed?
Thanks again guys!!
Not sure what you mean with firmware images to root the tablet. Do you mean a custom rom? Those should be smaller in size yes, as the are usually de bloated.
Maybe you flashed a wrong version if a custom rom for your tablet before, that would give you problems when flashed.
Both my or ashyx's method can be applied on a stock rom. I'm running just stock with root.
@Asynx: I flashed the latest firmware on my T800 this week and twrp didn't stick after the first boot. Tried many versions, also the one you mention in the dev section, but to no avail. Even replaced the recovery in the samsung's tar file and flashed it like that: twrp screen showed up right after the flash, but on next boit it was stock again. Only way to make it stick was to reboot into recovery right after flashing it.
Never had that problem before though on the Tab S (did have it already once on Galaxy S6).
Edit: forgot to mention I hadn't seen there was cf-auto root available for our current firmware. If I knew it would have saved me some time. Could have flashed the recovery with Flashify afterwards.
Apologies I am still getting used to the lingo with this stuff
Have done some stuff with Linux and some tweaking in Windows as well, so figured this shouldn't be too bad...
@Alta1r: so the process you describe is what you said, flashing the stock ROM and then root it afterwards...
Will try this process and report results here
(aside: I think the tablet was working fine after flashing with CF autoroot ROM -- is that the right word? -- what I think ruined it was when I told Supersu to try updating its binary through TWRP or CWM....which isn't yet on my tablet)
Alta1r said:
Only way to make it stick was to reboot into recovery right after flashing it.
Click to expand...
Click to collapse
It seems since lollipop this has to be done if flashing over stock recovery or it will be replaced at boot with stock.
Twrp will patch the recovery install script at first boot.
Sooooo...
First off, thanks for the "luck wishing"
I decided to try the method of @Alta1r.
@ashyx - I tried the CF-autoroot thing before (this was first attempt at getting a rooted tablet), and this didn't work for me. So I wanted something a bit more "hands on".
This is procedure I followed and worked for me (as of this post):
1) Before I began, I accidentally went into recovery mode instead of download mode. So I had to restart the tablet *gulp*
....yet I was able to restart just fine (no crashed as mentioned in my first post). I think this ~might~ have something to do with the fact that I downgraded the version of supersu that was "updated" through Google Play, but I'm not really sure...
2) Downloaded all relevant files.
3) Flashed firmware for tablet as instructed:
Alta1r said:
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Click to expand...
Click to collapse
Result was that tablet booted just fine!
Made sure that a few apps worked OK, and also rebooted the tablet a few times to make sure it was stable
(this is a linux based system, not Windows, but I still like reboot tests for stability checking...)
4) Next I did the TWRP flash through Odin:
Alta1r said:
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Click to expand...
Click to collapse
TWRP flashed fine. But then....
5) Tried to boot into TWRP recovery:
Alta1r said:
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Click to expand...
Click to collapse
As predicted, Alta1r, the TWRP didn't flash properly. I got an error on the stock recovery saying:
"Error message is "E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)"
So I tried your odin + reboot trick as above, and this booted into TWRP recovery.
6) Then I flashed supersu.zip (had kept on microSD card that is in tablet).
Andddddd.....
Root checkers says all good
Thanks so much for the help guys. I wrote the procedure above for anyone else who attempt this method!
bsquared938 said:
Root checkers says all good
Thanks so much for the help guys. I wrote the procedure above for anyone else who attempt this method!
Click to expand...
Click to collapse
Glad to hear all went well, and by the looks of it had fun doing it.
Although computer/device problems can get me agitated, I still have fun in the end
Not sure if I can ask this here, but two other slight issues after the rooting:
1) Upon rebooting the tablet, I always get the message "android is upgrading", even if I didn't touch any apps through Titanium Backup or other root-only apps that are meant to remove pre-installed applications.
Is this an issue? And if so, is there a way to get rid of this?
2) I am able to uninstall/remove apps with Titanium Backup (freezing them isn't possible without the paid version of the app), but I am not able to restore them. I made a full backup before I started to uninstall stuff. I put on USB debugging mode in developer options, but still I cannot put apps back. Any thoughts on this?
Thanks again!
Bharat
I wouldn't worry about the upgrading message, most get that.
AFAIK TB requires a kernel that can be set permissive to fully function.
If you want the ability to remove and restore apps use system app remover (root)
ashyx said:
I wouldn't worry about the upgrading message, most get that.
Click to expand...
Click to collapse
Okay thanks, I will not worry about that upgrading message for now...
ashyx said:
AFAIK TB requires a kernel that can be set permissive to fully function.
If you want the ability to remove and restore apps use system app remover (root)
Click to expand...
Click to collapse
Is there a way to set this up? Even System App Remover does not let me reinstall stuff...
(I don't plan to ever use any of the apps I am removing, but I would like this feature for "sanity" purposes...)
bsquared938 said:
Okay thanks, I will not worry about that upgrading message for now...
Is there a way to set this up? Even System App Remover does not let me reinstall stuff...
(I don't plan to ever use any of the apps I am removing, but I would like this feature for "sanity" purposes...)
Click to expand...
Click to collapse
Are you sure you have full root?
ashyx said:
Are you sure you have full root?
Click to expand...
Click to collapse
Yes I am sure I have full root.
I used root checker to check if I have full root access and it comes back green (to say root access is good).
(Just checked again now before posting this...)
Using either Titanium Backup and Root App Deleter, I am unable to restore deleted apps...
I have enabled USB debugging in the developer tools, as instructed to by Titanium Backup....
I read something about the "mount namespace separation" in supersu, I might try to toggle that option to see if it helps this situation.
Root app deleter? Is that system app remover?
Also what is the error when you try to restore with it?
ashyx said:
Root app deleter? Is that system app remover?
Also what is the error when you try to restore with it?
Click to expand...
Click to collapse
App is called System App Remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
It tries to restore the app, and after about half a second it just says "try again if it fails" with a "yes" button to be selected...
bsquared938 said:
App is called System App Remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
It tries to restore the app, and after about half a second it just says "try again if it fails" with a "yes" button to be selected...
Click to expand...
Click to collapse
That doesn't mean it doesnt restore. It says that every time iirc. Check in system apps to see if it restores.
ashyx said:
That doesn't mean it doesnt restore. It says that every time iirc. Check in system apps to see if it restores.
Click to expand...
Click to collapse
Okay I'm just going to say exact issue...
I deleted calendar storage, thinking that it's part of Samsung's calendar app (when in fact it is used by all calendar apps).
So now Google Calendar doesn't show me my calendar....and I'm trying to restore calendar storage, but it's not restoring
(had previously deleted through System App Remover, but now can't get it back)
Edit: I uninstalled and reinstalled Google Calendar, and that seemed to bring back my calendar.....
Sorry to cause you this trouble, I guess I panicked too early...
But will still be careful of what I remove...
Alta1r said:
Best would be to flash your firmware again with Odin. You can download your firmware on sammobile (see link below).
You will need Odin for this, the correct drivers on your pc and to have USB Debugging on (under Developer options in Settings).
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
Download supersu.zip as well (see link below, you can download 2.46 or 2.49 beta) and put it on the tablet or external sd card.
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
http://www.sammobile.com/firmwares/database/SM-T800/
http://forum.xda-developers.com/showthread.php?t=1538053
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Good luck!
Click to expand...
Click to collapse
worked for me thx :good: