Develop Bugs

Idiot's guide to flashing the Xoom (for fun and profit)

This guide is for you that have a new Xoom (WiFi only, US model) with Android 3.1 and want to
- get root access
- enable the external SD card unit
Please note that Android 3.2, which now is available for the US Wifi models, make this guide more or less obsolete. If your aim is to have root access, then there are probably simpler methods.
What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and dont try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned!
I strongly recommend you to read the entire guide before trying this. In fact, read it twice to ensure that you have understood everything. If there is wierd stuff that you dont understand, dont hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but noone (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
If someone else adapts this guide for the EU model or the 3G model, feel free to drop me an IM and I will update the guide for these devices too. Until then, this has only been tested on a WiFi only, 32 GB device bought in the US. If you brick your 3G or EU bought model, dont call me ...
0. Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity)
2. Install Java SDK and Android SDK tools (for adb and fastboot commands)
3. Unlock the device for flashing (allowing replacement of recovery and boot images)
4. Install a modified recovery image (ClockWorkMod recovery for Android)
5. Root the device (Allow r/w access to the device filesystem)
6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)​
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows XP x86 SP3. Windows 7, Mac and Linux users will probably have to do some steps differently.
Update July 7: I have tested the procedure on Windows 7 x86 now and the procedure is identical to Windows XP.
1. Install the latest Motorola USB drivers
The installation file can be found here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2. Installation of development software
Java SDK 6 and Android SDK (for Honeycomb at least) need to be installed. You can find the installation kits here.
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
http://developer.android.com/sdk/index.html
2.1 Install them as any other software.
2.2 What I had to do was to manually modify the PATH environment variable. I use Windows XP so I did that by right clicking on My Computer, choose Properties and select Advanced. Here I added the path to platform-tools and Tools
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\QuickTime\QTSystem\;D:\Java\Android-sdk\platform-tools;D:\Java\Android-sdk\tools
Note: If the Android SDK complains that the Java Dev Kit cant be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
2.3 Test that ADB and FASTBOOT works. You should open a command window and go to your Android installation directory. Plug in your Xoom to your computer and write 'adb devices'. Your Xoom should now be listed like this
C:\Documents and Settings\Anders>adb devices
List of devices attached
0288414343813157 device​
Did your device not show up? Make sure that you have USB debugging enabled in Settings / Applications / Development
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to rescure important data before you start.
3.1 Power up and start the Xoom
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'My Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal, but now ready for step 4
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
4.1 Boot into flash mode with 'adb reboot bootloader'
4.2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img​
4.3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.4 Enter CWM with the following procedure
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. There are ways to prevent this (see posts below), but I recommend you to redo step 4 instead of messing with removal of system files. But both methods would probably work. Experiment!
5. Rooting the Xoom
The root zip file is located here
5.1 You need to transfer the ROOT zip file to a working micro SD card. You can do this on a computer or cell phone, but the ROOT zip must be located in the root directory of the SD card.
5.2 Insert the now prepared SD card in the Xoom
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option
5.4 Select 'Install ZIP from sd card'
5.5 Select 'Choose ZIP'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install the ROM Manager app and start it. If the rooting was successful, then ROM Manager should start without any complaints.
6. Flashing a new kernel that supports SD cards (and maybe more ...)
The kernel that I used is described here http://forum.xda-developers.com/showthread.php?t=978013
The kernel zip file is located here
6.1 This step is identical to 5, but swap the ROOT zip towards the KERNEL zip. For simplicity, you may want to prepare the SD card with both zip files at the same time in step 5.1 ...

Looks great. You just might want to give credit to LandMaster and cam30era, too.

Also is this for just USA or all, cos many people brick there xoom if its just for USA only

okantomi said:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Click to expand...
Click to collapse
Of course, done

juDGEY2k10 said:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
Click to expand...
Click to collapse
This is only tested on a US device. OP updated.

Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".

I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.

BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
When you unlock your Xoom, it will wipe all user data.

bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.

BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
Yes it will. Read 3.4 again, it will do factory reset.
The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.

bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
This is true, and I will update the OP to reflect that.

So has anyone followed this guide successfully yet? I don't really want to be the first...

yordikins said:
So has anyone followed this guide successfully yet? I don't really want to be the first...
Click to expand...
Click to collapse
Hi
I did!. And you know that someone gotta be first (actually second). Why not take the credit?

pingvinen said:
This is true, and I will update the OP to reflect that.
Click to expand...
Click to collapse
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App

Abracastabya said:
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.

cam30era said:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
Click to expand...
Click to collapse
Sounds good and thanks B-)
Sent from my Xoom using XDA Premium App

Tnx . Very help full .

I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).

rmcsc said:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
Click to expand...
Click to collapse
Try again, and remember that timing (3 seconds) are key to success ...

I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.
I'll update in a few. Thanks!
Sent from my T-Mobile G2 using Tapatalk

[Root]ATT SGS3 Tested working! Reset flash counter! Simple

First off, let me say that I did not develop this stuff and all thanks should go to those that did. Special thanks to noobnl, mskip and TeamEpic for all their work.
So here we go.
General Disclaimer:
Use these tools and this guide at your own risk. Doing these things wrong/improperly/etc. has the ability to completely ruin your device and YOU assume all risk and responsibility if that happens.
Also note that Rooting WILL violate the manufacturers warranty on the device making it ineligible for warranty repair. If you have insurance on the device however they MAY still replace it for the cost of your deductible.
Root Method Starts Here.
1. Download and install the Samsung USB drivers from Samsung's website
2. Turn on Debugging on your Phone
* Open Settings
* Select "Developer options" in the System section
* Check the box for "USB Debugging"
3. Plug you phone up to your computer using the USB cable and allow the drivers to install.
4. Download CMW_SuperUser_v3.07.zip from the bottom of this post
* I recommend making yourself a nice little GS3 folder in your downloads folder for all this stuff so it's easy to find
* DO NOT UNZIP!!
5. Copy CMW_SuperUser_v3.07.zip on to the Root of your GS3s INTERNAL storage (if you put it into a folder, you may have a hard time finding it later, but that's on you).
* DO NOT UNZIP!!
6. Unplug you phone
7. Power off your phone
^^ once u have now odin time......
1. Download Odin3-v3.04 from the bottom of this post
2. Extract Odin3-v3.04 into it's own folder somewhere where you can easily find it.
3. Download fixboot.tar from the bottom of this post to somewhere you can easily find it.
4. Reboot your phone into download mode
* Hold down Volume Down, Home and then power until Warning!! message is displayed
* Press Volume Up to continue.
5. Your phone should now be in download mode and displaying a green Android and say Downloading. If it is not, power off your phone by holding down the power button and then try to get into Download mode again. Do NOT progress until you have done so.
6. Go into the folder you extracted Odin3 into and run Odin3 v3.04.exe
7. Connect your phone to your computer via USB
8. In Odin, the COM box all the way to the left should turn blue and it should say Added!! in the Message area.
** Click on PDA and in the Open window that pops up navigate to and open the Tar With CWM from below file you downloaded earlier
** Verify that Auto Reboot and F. Reset Time are checked
** Click Start. Once the process is completed you device should automatically reboot and there will be a green PASS! box in the upper left of the window. You can then close Odin.
** Power off your device and boot into Recovery mode
* To boot into Recovery mode: Hold down Volume Up, Home and then the Power button until you are in Recovery (it should say CWM-based Recovery at the top of the screen)
**. Install CMW_SuperUser_v3.07.zip that you copied onto your internal memory
* Navigating ClockWorkMod Recovery: Use the Volume Up and Down arrow keys to change the highlighted option and the home key to select an option. The Back softkey works, but will not be lit and will take you back one screen.
Installing a zip:
* Select "Install zip from sdcard" (Yes, I know it's on the internal storage.)
* Select "Choose zip from sdcard"
* Select the zip you want to install; in this case CWM_SuperUser_v3.0.7.zip
* Select "Yes" to begin installing
**. Once the process has completed use the Back arrow to get back to the main recovery screen (remember, it works, but it's not lit) and select "reboot system now." Once your device boots up you should now be 'Rooted,' but there's still a few more things to be done
Reset counter: triangle away from playstore and reset the counter.
15. Install BusyBox. There are actually several ways to do this, but the BusyBox app in the Google Play Market is quick and easy. Install it, grant it SuperUser permissions and it'll walk you through the rest and advise you when to update.
16. Update your Binaries.
* Open the Superuser app
* Get into settings (the wrench icon in the upper right of the screen)
* Select Su binary under the General section towards the bottom of the list
* Select Update
**.Your device is now rooted and all set.
** optional: update cwm using rom manager or use img from clockworkmods website. Flash through adb.
Links:
First make sure you read all of the above:
Triangle away:
http://forum.xda-developers.com/showthread.php?t=1494114
New Odin Tar with Stock Kernel: http://www.mediafire.com/?d1t0av7u1e6d3xx
Odin Tar with CWM: http://forum.xda-developers.com/attachment.php?attachmentid=1148060&d=1340384923\
CWM Su fix (flash this in CWM after): http://www.mediafire.com/?0e86q6rexr7g8g4
after that
Hit thanks on Everyone mentioned in this post including myself
Special thanks:
noobnl, mskip and TeamEpic For root CWM
FennyFatal for stock Kernel
Me for Tar and Method testing
IRC for testers
TheSoberRussian for letting me pull his boot.img
^^ hit thanks on everyone here or ill eat u.

Now time to wait for ROMS!
This needs to be sticky

TheSoberRussian said:
Now time to wait for ROMS!
Click to expand...
Click to collapse
mine will go up as soon as i get the device xD
no more blind deving

Here's Odin again....

Yay. I'll give this a go (via Heimdall in Linux) as soon as I get my phone. In the meantime... I'll let you other guinea pigs below this post test it out.
Ohhh how I love root. Let me count theee ways: ClockWorkMod recovery (and nandroid backups), ROMs, TitaniumBackup, AdAway (/system/etc/hosts), adb over wireless, free wifi tethering, permanent debloating, kernel overclocking, CIFS (windoze) network shares, poking around /data/data in a root adb shell, yadda yadda...

Nice. I got my gs3 today
I'm going to wait a week before I do any rooting. Just to feel the phone out
sent from my GALAXY SIII

Process not working for me! I finished the ODIN flashing OK as usual but when going to recovery I end up in stock 3e recovery and not CWM!
Even tried adb reboot recovery and ended in stock 3e recovery too!
Can you check if you uploaded the correct boot.img?

Sweet ty
Sent from my Xoom using xda premium

Great job, can't want to see more from the dev's. Now to add to my reference thread. b:

From the TMO forum:
qbking77 said:
Here's a how to video for everyone!
http://www.youtube.com/watch?v=7Soapch0c5U
Click to expand...
Click to collapse
Original thread:
http://forum.xda-developers.com/showthread.php?t=1726725

mp2ning said:
Process not working for me! I finished the ODIN flashing OK as usual but when going to recovery I end up in stock 3e recovery and not CWM!
Even tried adb reboot recovery and ended in stock 3e recovery too!
Can you check if you uploaded the correct boot.img?
Click to expand...
Click to collapse
Same cant get into CWM recovery

ghost77 said:
Same cant get into CWM recovery
Click to expand...
Click to collapse
The T-Mobile and Sprint root guides root by installing a new recovery.img and this one installs a boot.img.....
No worries here as phone works correctly although the flash counter changed to custom and indicates the 3 times I flashed with ODIN!

Remember, this time its UP VOLUME home and power

duckfart said:
Remember, this time its UP VOLUME home and power
Click to expand...
Click to collapse
I am used to flashing my Samsung phones almost weekly! In fact I also own an International GS3 and I know how to enter recovery; problem is I reach the stock recovery and not CWM recovery!

+1 not working, 3e instead of CWM.

mp2ning said:
Process not working for me! I finished the ODIN flashing OK as usual but when going to recovery I end up in stock 3e recovery and not CWM!
Even tried adb reboot recovery and ended in stock 3e recovery too!
Can you check if you uploaded the correct boot.img?
Click to expand...
Click to collapse
Same here, still booting me into 3e recovery.

Got inpatient and did Sprint root method , and now have root

ghost77 said:
Got inpatient and did Sprint root method , and now have root
Click to expand...
Click to collapse
I figured all variants of US GS3 could have the same recovery but I am not about to try and soft brick it!

I just went to the spring thread and downloaded the clockworkmod.tar file and followed the instructions in THIS thread but instead of flashing the fixboot.tar i did the clockworkmod.tar from the other thread. Now have working root.

my bad man i thought it would have CWM ill fix now

pit files for i317 and i317m

As a general FYI, if you think you need to repartition your phone it is also possible that your phone has experienced:
a) A hardware issue, possibly partial or total emmc failure.
b) A mismatch between bootloader (sboot.bin) and trustzone (tz.img) versions. See this post or my MK6 stock thread for some possible options to fix this.
As a step of last resort to recreate the partition table on your phone, a pit file may be what you need. This can be done in either Odin or Heimdall.
Warning - repartitioning your phone may erase all data and might cause other unintended consequences. You assume all risk.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
To use a pit file in Odin, this is typically done as part of a flashing a stock rom package, like the LJ2 or MA4 package for the i317 (or similar package for the i317m). You specify the pit file in the PIT section, make sure the repartition box is checked, and then add the rom package in the PDA section like usual.
If you are running an official 4.3 or later bootloader you will not be able to successfully flash a stock firmware package that contains earlier bootloaders - Odin will hang and you will need to find a different stock package to flash that does not contain a bootloader. (i.e. If you took the the i317 4.3 OTA and are running the MK6 bootloader or a later bootloader, you'll want to avoid UCAMA4)
The attached zip includes pit files for both the i317 and the i317m. The partition mapping is the same for both (see the included analysis files), but the pit files have unique security signatures which are accepted only by the bootloader of the specific model phone for which they are intended. I've tested the file for the i317 and can confirm that it works as intended. The file for the i317m was pulled the same way by an XDA member (thanks @plemen !) with an i317m and I've confirmed it is formatted correctly. It has now been confirmed as working.

If you want to learn a bit more about pit files, check out this thread by Adam Outler:
http://forum.xda-developers.com/showthread.php?t=2540480

Very interested in this, as I need the pit file for my I317. Question about the bootloader, though.... I've never taken an OTA, just flashing CM and OmniROM nightlies (was on 4.4.2 when my phone committed suicide). Should I be safe to use this pit file? And what factory firmware would you recommend to go with it?

pit files should be back in a day or two (I'll be testing over the weekend).
Depending on what happened to your phone it's still highly probable that your pit (partition) data is fine. There's a way to confirm this using Heimdall - when time permits I'll add instructions to post #2. That's a safer first step than attempting a repartition.
As for bootloader and firmware - if you've never taken an OTA, and you're not on a 4.3 bootloader your best bet for stock firmware is UCAMA4. It's a more complete and somewhat newer package than the other option (UCALJ2). You can get this from sammobile, or a mirror copy I have linked in post #2 here:
http://forum.xda-developers.com/showthread.php?t=2589891
that post also has information on a couple apps you can load that will allow you to check which bootloader you have loaded once your phone is operational.

Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.

anine said:
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
Click to expand...
Click to collapse
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?

Zen Arcade said:
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Click to expand...
Click to collapse
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.

Help
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...

anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
The symptoms you describe are similar to those I've seen on the Q&A forum recently. I don't want to be the bearer of bad tidings, but I suspect you have a partial emmc (hardware) failure.
My time during the week is limited so I expect to have testing done this weekend.

terpencar said:
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
Click to expand...
Click to collapse
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
http://www.androidfilehost.com/?fid=23060877490003986
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.

rob_z11 said:
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
Click to expand...
Click to collapse
Thanks.. It just hangs at system.img in odin

Nice job Zen
Sent from my SGH-I317 using XDA Premium 4 mobile app

Pit files are back up and attached to the OP. The i317 pit file is tested and confirmed working.
The i317m file is identical, except for the security signature. I'm currently looking for someone with a healthy i317m willing to test flash the i317m pit file to confirm it works. (I would do this myself, but I don't have an i317m).

Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!

My phone was not booting and stopped at Samsung logo. After the pit file and stock rom, my phone is live again. I am still having issue with storage but at least I have good starting point.
thanks

Works fine on i317m

anine said:
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2626593

qkster said:
http://forum.xda-developers.com/showthread.php?t=2626593
Click to expand...
Click to collapse
See posts #9 and #13 on the thread above for the specific potential solution to try.

Corrupt pit file it says. for note 2 att help
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE

kumar_420 said:
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
Click to expand...
Click to collapse
Err mj9 is verizon haha
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged

Maybe an Idiots guide to Flashing (smt210/smt210R)

IDIOT GUIDE (I am the idiot)
This guide is aimed at the Samsung Tab 3 7.0 (SMT210/SMT210R)
I am I suppose still a newbie to the android world and a starter with rooting etc (but I do have a linux background) All the terms that appear technical are explained below.(see below)
The aim was to root (see below), my Samsung SMT210 (Ie TAB 3 7.0) and install a new Kernel (see below) and a new ROM (see below). Why you may ask, The standard SMT210 is slow, it has many programs that I don't want (Bloatware) and it runs down the battery so fast.
The first consideration when making any changes to phones or tablets is your BACKUP. There are loads of backup apps available for android, however if your device is not rooted you can only backup your data, contacts etc. The main system is not backed up. So the first priority is a too make a backup of everything, this will involve flashing (see below) your device.
I must add that I rooted my tablet before I did backups, since I had made no changes to the tablet before I rooted it, Ie it was out of the box. I rooted my phone by flashing a prerooted firmware from (Jaimison904) http://d-h.st/leL]prerooted.tar.md5 the instructions for flashing are the same as the flashing procedure for the recovery app.
Before doing anything make sure the tablet has at least 80% battery capacity left, if not charge it.
Additionally stop your display turning off, I normally set the display to a 30 min wait point.
Backing up / creating a recovery
This can be done in 1 of 2 ways with a computer, 1. using Odin (See below) for windows, 2. using Heimdall (see below) for Linux. I will concentrate on Odin as with Linux I feel that it's a bit complicated for newbies (or geriatrics like myself).
A useful tip before you start is to install Kies (see below) and make sure you get your computer to connect to your tablet (when this works the USB drivers will already be installed on your computer)
Another tip which might help is that you should create a directory for all your android & system files on you computer.
First you will need to download a copy of Odin (I have used 3.07) unzip it to your special directory.
Install Samsung USB drivers (see above)
Download a recovery app (see below) I used Philz_touch, download the xxxxxxxxxx.tar.md5 file put it in the directory you created. http://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi
Download the new RocketTab 3.1 (developed by Tempdroid) http://forum.xda-developers.com/showthread.php?t=2507772 Read the first section of the thread and the see the various options etc.
Download Blackhawk kernel
http://forum.xda-developers.com/showthread.php?t=2439564&highlight=root
Having downloaded all the above files please check the MD5 sums (this a file check that makes sure the files are not corrupted during the download process, it should be done for all downloaded files whatever they are)
We are now ready to start:
Please watch this video and thanks to Rootjunky.com http://www.youtube.com/watch?v=XolmtyvS3Yk
1.Power off your tablet
2.Close all programs on your PC
3.Start Odin 3.07 by clicking on the .exe file in the directory you setup (it appears after you unzipped)
4.Start your tablet in download mode (Hold Home, volume down and power, release with warning, then vol up)
5.Connect you tablet to the PC via the usb cable
6.Wait until Odin says device connected
7.Click on the PDA button and browse your computer until you find the Phil_touchxxxxxxxxxx.tar.md5 file and click on it.
8.Make sure that the only box that is ticked in Odin is F. Reset Time DOUBLE CHECK......
Then click start.
9.Wait until you see the green/blue PASS / RECOVERY box. The recover software will have been loaded.
10.Do not shutdown yet, remove the usb cable
11.Boot into Recovery mode, by holding home button, volume up, and power button, until the Samsung Galaxy tab3 logo appears and release the power button while still holding the home and volume up buttons until you see the software load.
At this point it is a good idea to create a backup either on the internal memory(called an sd card) or the external sd card (2 sd cards Confusing or what)
Just follow the instructions on the screen, be patient these things take time sometimes a few minutes.
Now I recommend that you reboot your device just select the menu option on the first screen and allow the device to restart, you shouldn't notice any difference from before you started.
Go to google play and download and install SUSuper user. (it won't work at the moment)
You are now ready to start rooting your device, there are a number of ways of doing this but I recommend that you flash prerooted.tar.md5 with Odin. The reason for this is that it allows you to explore your device and learn where files are stored and use apps with root access, freeze stock applications and generally test how things work without having changed the orginal system significantly.
So start the device in download mode and flash prerooted.tar.md5 with Odin in just the same way as you flashed Philz_touchxxx.tar.md5.
MAKE A BACKUP to recover from if something goes wrong.
When you are ready to change to RocketTab 3.1 and or the Blackhawk kernel follow the following:
Transfer the 2 zip files you downloaded (RocketTab3.1.zip and blackhawk-kernel-2.1-t210.zip) to the internal sd card, it is much safer than trying to load from the external card.
Restart your tablet in recovery mode (Home, Volume up and power buttons)
Choose full wipe (formatting system, data, cache and etc) which removes old system files and other things to allow a clean base on which to install your new files.
choose install from zip.
Scroll down and there is "don't allow old update-binary", it is checked by default and you just uncheck it. You will get an error if this is not done (Many thanks Ripshock)
Install zip from sdcard Rockettab3.1.
I then do another backup / recovery
Then Install zip from sdcard Blackhawk
Wait until done then reboot and start adjusting your settings as normal and enjoy the speed and reduced use of the battery.
I hope this proves useful to somebody, any comments would be appreciated and will include what updates are reasonable. I might add that I am not liable in any way shape or form for any damage that you may do, the above worked on a number of devices without problems.
Enjoy a new faster android device.
TERMS
Bloatware
Most of the rubbish that your provider preloaded on your tablet, eg games, Themes, help center etc
Download mode
Download mode, is the mode with which you can flash you system with Odin, Heimdall etc. To enter this mode hold the home button down and press the volume down and the power buttons together until you get the warning message, then release all buttons and press the up volume button. You will then see a screen saying Downloading with the green Android figure.
Flashing
Flashing is the method of uploading system software to your phone or tablet.
Heimdall
A phone or tablet flashing software that works on multiple pc platforms, ie Linux, windows and Mac
Keis
The Samsung connection software for windows. (only works on windows as Samsung doesn't support Linux)
Kernel
The kernel is the effectivly a translating module which converts instructions from the software to instructions that the hardware understands. So it controls the way that the hardware functions with the software that is installed.
Odin
Odin is a flashing software that was developed by Samsung which has been leaked to the internet. I used version 3.07. When you download this zip file you will need to unzip it to a convenient directory. Odin works with xxx.tar.md5 files NOT .zip files or .img files
Recovery app
There are two main recovery apps available CWM (Clockwordmod) and TWRP, I used a variation of CWM called Philz_Touch (Credit to Phil3759) which is an extremely good recovery system, easy to use and very powerful, but the basic CWM and TWRP versions can be used as well.
The Philz_touch download link for the SMT210 is http://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi
Recovery mode
The mode accessed by holding Home, Volume up and power button, which enables you to create recovery files and to flash your device using .zip files etc with CWM or similar without a PC.
Root / Rooting
Term to enable access to the system files on your phone or tablet. Read further on the Internet. Basically it allows you to at one extreme to totally destroy your device or at the other extreme to totally customize and speed up your device to make the whole experience much better.
So rooting allows access to the system files which control the device at a level which allows customization. Root is the term used to describe the user who has access to the system files.

Not bad. I do not have that device but I have done a few Roots/Roms/Recoveries so I understand the work flow. I would just make one minor change. On step 4 you tell the reader to do something, then you say "(see below)". At that point the reader has now stopped everything to try and find "below". I would recommend to keep the reader's attention directly on the task at hand and place steps on how to perform a function.
3. ...
4.Start your tablet in download mode.
a. Press the Home, Vol Down, and Power keys together.
b. Remain until the device logo appears then release.
5. ...
Also, I do not believe one has to be rooted to load TWRP or CWM (not sure if these are compatible with your device). Backups and restores can be performed with these tools. But again, I do not think one needs to be rooted at this point.
Just my thoughts.

Correction
Brian D said:
Not bad. I do not have that device but I have done a few Roots/Roms/Recoveries so I understand the work flow. I would just make one minor change. On step 4 you tell the reader to do something, then you say "(see below)". At that point the reader has now stopped everything to try and find "below". I would recommend to keep the reader's attention directly on the task at hand and place steps on how to perform a function.
3. ...
4.Start your tablet in download mode.
a. Press the Home, Vol Down, and Power keys together.
b. Remain until the device logo appears then release.
5. ...
Also, I do not believe one has to be rooted to load TWRP or CWM (not sure if these are compatible with your device). Backups and restores can be performed with these tools. But again, I do not think one needs to be rooted at this point.
Just my thoughts.
Click to expand...
Click to collapse
Thanks, I have edited the various lines, as to CWM and TWRP you are quite right you don't need to be rooted, but I wasn't, the tab was only rooted after the recovery flash was done.
For info the tab 3 7.0 is compatible with CWM and TWRP but the Philz_touch advanced edition is a major improvement on the normal CWR version which is why I chose it, the interface and functionality is greatly improved.

Unrooted note 4 change from 5.0 to 4.4

Is there a way to switch from 5.0 to 4.4 while the phone is unrooted or would I have to root it in order for that to happen? Also if I have to root what would be the best way to do so and put back 4.4?

I am totally interested in this as well any step-by-step information would be highly appreciated

I would have to say no... you can flash back to 4.4... but need root to flash
Sent from my SM-N910P using Tapatalk

kaz007 said:
Is there a way to switch from 5.0 to 4.4 while the phone is unrooted or would I have to root it in order for that to happen? Also if I have to root what would be the best way to do so and put back 4.4?
Click to expand...
Click to collapse
Here's a step by step procedure to downgrade, make sure you backup your internal sd card contents because it requires a data/reset on 4.4. since lollipop encrypts internal storage.
Download these 3 files.
USB (Driver) ver.1.5.45.0 ( Latest as of this post ) from samsung.com/support, search for your device SM-N910P and choose your color, and select manuals and downloads
Odin v3.10.6, from rwilco12's website, HERE
N910PVPU1ANK2 .TAR file, from ViperBoy's thread in generals forum HERE
Save these files to your desktop within a folder called Note4Downgrade makes it easier to find.
Uninstall your previous drivers like old Samsung, Kies of any versions.
open the Odin zip file, drag and drop its contents into the Note4Downgrade folder.
Open the N910PVPU1ANK2 zip file, drag and drop the .tar file into the Note4Downgrade folder.
Install the latest Samsung drivers, no need to reboot your computer.
Open the Odin3.10.6 executable file, select PDA or AP slot and load in the NK2.tar file, it'll take awhile and the Odin program will freeze as the file that its loading is ~1.8 GB's.
In the mean time while this is being loaded, shutdown your Note 4 Device and go into download mode by pressing Volume Down, Home Button, and Power Button Simultaneously.
Hold it down until it starts up into an Android Logo Firmware screen, Next Press Volume Up to continue into the next dialogue.
Once the file is loaded into the Odin program, use the original Samsung USB cable and plug it into a USB 2.0 port ( No, Not 3.0, Sometimes it can cause issues and errors, its do-able, but not recommended. )
Have the Odin Program detect your device and Windows will install the device drivers. Once this is done, a word within a blue box will state this message up top.
[COM:##]
It does not matter on what the "##" is as long as that is reading a number, meaning Odin has recognized and detected your device.
Stop here and recheck your progress.
- Latest Samsung Drivers installed ( SM-N910P )
- Odin 3.10.6 with loaded N910PVPU1ANK2.tar inside the PDA or AP slot
- Device in download mode, plugged into a USB 2.0
- Odin with [COM:##] in a box.
Proceed to clicking the "START" button if you have all of your above progresses done.
This will take around 15-30 minutes of flashing the stock 4.4 firmware, this will not tick the KNOX switch if you haven't rooted your device already as this is stock firmware.
It'll auto reboot once it is done, First time boot up will take longer as it is loading the device for the "First Time".
Once you're done, and you're on the welcome screen of the device, power it off.
Now we need to do 2 sets of resets, data factory within recovery, and an internal SD card wipe through Backup and Reset menu within settings of the device.
Now go into the devices recovery by pressing these 3 buttons. Power UP, Home Button, and Power Button.
Hold it until you see blue text at the top left corner of your devices screen stating "REBOOTING RECOVERY. . . ."
Then you can let go.
LEGEND
- Volume buttons = up or down
- Power Button = Proceed into next dialogue
From here go into the wipe data/factory and reset the device.
Once done, do a cache wipe.
and lastly, reboot the device.
Once your device has been rebooted, skip all the welcome steps and go to home, pull down the notifications bar and select the setting button up top.
scroll down to storage and unmount your Ext SD Card and take it out ( If you have one! ), now back out and go within Back up and Reset under personalizations. checkbox wipe internal Card and factory data reset again.
Once its all done it'll reboot, now you're on the latest firmware of kitkat on the note 4.
I hope this will help you as well as others wanting to stay on kitkat for any reasons they have or if they run into issues on lollipop.
Your guide, simplified!
- Spark91

Awesommmme! Thanks for taking the time Spark!

Glad I've helped out!

Very thorough guide.

bought a note 4 (sm-n910p) from eBay thinking that i can use ssu.apk to sim unlock the device. It was on lollipop.
so i thought i can downgrade to 4.4 . unfortunately while flashing kitkat using odin i got a fail message .After that phone is showing ("firmware upgrade encountered an issue ")
i tried to flash stock lollipop firmware using odin sadly now it show { THERE IS NO PIT PARTITION } error .
the device is on oe1 build

I'm on N910PVPU3BOF5 will that work with my phone ?

zjor2000 said:
I'm on N910PVPU3BOF5 will that work with my phone ?
Click to expand...
Click to collapse
I think of5 has an updated bootloader and cannot be downgraded.