Database Info

[A] [SM-P900] HOWTO: Full Backup without Root and Easiest way to get Root

Disclaimer: Not responsible for what you do with this information.
Important Note: So far (April 2015), no one has been able to root or flash non-stock recovery on SM-P900 without tripping KNOX. For all we know, KNOX is useless to us, but nonetheless use the SuperSU app to disable KNOX after you are able to get root. No need to disable KNOX if you don't root.
I tried to get root on my SM-P900 but for some reason I couldn't get TWRP recovery to stick (always reverted to stock recovery) and also had corrupted display after flashing Chainfire autoroot using ODIN (Odin was stuck on flashing cache.img). My summary here should help anyone else to quickly what they need without digging through different threads. FYI-- these steps work on latest Samsung OTA with Kitkat 4.4.2
Tools required (for full backup or to get root):
Windows 7 PC (or Virtual Box VM https://www.modern.ie/en-us/virtualization-tools#downloads -- did not test using a VM)
Samsung USB Drivers for Note Pro 12.2
Odin3 (v3.09, not 3.07 or 3.10.x)-- Only get this from xda-developers forums, not from any third party website http://forum.xda-developers.com/attachment.php?attachmentid=2409624&d=1385179473 -
P900XXUANB3-RecoveryImg.tar -- http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
twrp-2.8.6.0-v1awifi.img.tar (or just latest twrp for P900 .img.tar image)
Two things to be aware of:
To Boot Tablet in Odin mode press and hold: (Vol Down + Menu + Power)
To Boot Tablet to Recovery press and hold: (Vol Up + Menu + Power) release after seeing Samsung logo for the second time
1. Compleletly remove Samsung Kies from your PC
2. Install latest Samsung USB drivers for Galaxy Note Pro 12.2 (just google and get it from the official Samsung Website)
3. Keep USB cable disconnected from PC, Boot into Odin Download Mode on the tablet
- Make sure to accept the warning by pushing Vol up
- Odin Mode should say:
Current Binary: Samsung (or Official)
System Status: Samsung (or Official)
Knox Warranty Void: 0
4. Start Odin on the Windows PC as Administrator (not sure if Admin rights are necessary but just do it)
5. Load the P900XXUANB3-RecoveryImg.tar image into "AP" (or "PDA" if you are using an earlier Odin3 version!!!). Also remove "Auto Reboot" option and keep "F. Reset Time" enabled
6. Connect the Tablet. Odin should say ""<ID:0/00#> Added!! -- this means USB connection established
7. Flash the Recovery Image by hitting "Start". Should take maybe 5-10 seconds.
8. Next load the twrp .img.tar file in to "AP". Flash that by hitting "Start". Should take maybe 10 seconds.
9. Power tablet off. Disconnect USB.
10. Plug in an external microSD card (if you want to backup). Boot in to recovery (Vol up + Menu + Power).
If you do a full boot, you will lose recovery. If you flash CF Auto Root .tar.md5 image you will get corrupted display then you wont be able to boot unless you flash the P900XXUANB3-RecoveryImg.tar image.
11. Once in TWRP recovery, you should do a backup and select the destination the external microSD card.
12. Then go to reboot, select system, and then swipe right if you want to root.
13. Boot up normally, then download SuperSU app from Google Play Store
14. Run SuperSU, it will say binary needs to be updated. Hit OK, then hit TWRP/CWM Recovery. Device will reboot in to TWRP, run a script then will say "FAILED" and reboot automatically.
15. Boot up normally, you now have root. Open SuperSU app, it will say seems that you have KNOX, do you want to disable it? Say yes.
People on this forum said that if Root is acquired and KNOX is not disabled, they suffered from random soft-reboots.
Download Adaway APK and install it. Once installed run the app an it will ask for root privileges. Now you're golden.
Troubleshooting:
If you tried to flash and TWRP doesn't stick check your status by going in to Odin Mode if the tablet still says:
Current Binary: Samsung (or Official)
System Status: Samsung (or Official)
Knox Warranty Void: 0
Then nothing changed from stock settings.
If it says:
Current Binary: Samsung (or Official)
System Status: Custom
Knox Warranty Void: 1
Then you probably have TWRP installed but didn't try booting in to it.
If it says:
Current Binary: Custom
System Status: Custom
Knox Warranty Void: 1
Then you probably have TWRP installed and also root (if you swiped right).
Where to go from here?
You can stay rooted, or you can now use TWRP to flash another rom (CM12+ for example).

reserved.

Good Guide, thank you!, was about to write one anyways.
5 more things:
1.) On the Note Pro you don't need the home button! You can reach recovery by pressing Vol up + Power, let got of the Power and keep pressing Vol when you see the screen turn on (easier when device is unplugged from both PC and power)
2.) For those interested in using a VM to use with Odin: VirtualBox DOES NOT WORK! (tested with Win XP and Win7). The problem seems to be the virtual USB Controller to connect to Host USB devices. Odin won't detect connected devices.
Use VmWare instead! I used VMWare Fusion with Win 7 Enterprise and it worked like a charm. Seems to have better USB Host integration.
3.) Odin 3.10.6 worked fine for me (Odin 3.9 also works!)
4.)Suggestion:
If you want root, instead of downloading SuperSU from the Play store, place the TWRP SuperSU (at the moment SuperSU 2.46) on your SD card. When you boot into recovery, you can flash the SuperSU directly after making you initial backup.
No Errors, so installing Supersu twice, no problems
5. SUPERSU link is missing in the "things needed" list.
Feel free to add this information to the first post.

thanks for the tips.
using the method described above, SuperSU script is downloaded with the play store SuperSU app. So it guarantees you're using the latest version. plus you should use the SuperSU app to monitor which apps have been granted root privileges.
although i haven't tried Odin with Virtual Box, I've used fastboot and adb a few thousand times and it always worked for me. maybe its something specific happening here.

Need help with my non-booting SM-N915A

So I wanted to downgrade to 4.4.4 from 5.0.1 with the downloaded ROM from this forum. I used odin 3.04 and loaded up the BL, AP, CP, and CSC. it always failed. Well in my finite wisdom tried adding a PIT file that I found for the device and also reformat. My phone starting giving me the yellow triangle of doom. After that i read that just installing the PIT file fixes that so I did and it succeeded but now it loads up the Samsung Galaxy Note Pro powered by Android screen for a few seconds then reboots back to the same screen. I can now get to recovery mode and download mode but recovery mode says disabled on all options when selected. HALP!
Edit: In recovery mode, the bottom says, dm-verity verification failed...
At the top it says the following
Android system recovery <3e>
KTU84P.N915AUCU1ANK2

Myself if you can access Download Mode ,
Then reflash stock 5.0 because there's no way possible to backroll to 4.4.4 once yer on Lollipop
(Read the Forum it's all over)

tried to install a 6.0.1 rom and ****ed up my phone so bad.

downloaded twrp 3, was running 5.1.1 on my phone and rooted it. tried to flash a rom and got stuck in a bootloop, now I cant boot into twrp, or anything for that matter. All i can do is hold volume down and power and home and try to ODIN a new bootloader or such and it just fails. what do i do? but when I try to boot into TWRP it goes into a blueish screen with a White exclamation mark saying "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software. I tried to do that but it didnt even recognize the device. At this point i dont care about the data, I just need a working device

Okay, so I attempted to unroot and flash the stock 5.0.2 software and I got a error on the download screen. It says SW REV. CHECK FAIL. DEVICE: 3. BINARY: 1.

If you have no knox install MM official then flash this kernel tar file (AP) https://drive.google.com/folderview?id=0B40ItdHKfkyQcTA5bnRPWDg0X28&usp=drive_web#list it will boot to mm 5min :good:
Btw you cann downgrade from 5.1.1 to 5.0.1 you just go up not down

zach616 said:
downloaded twrp 3, was running 5.1.1 on my phone and rooted it. tried to flash a rom and got stuck in a bootloop, now I cant boot into twrp, or anything for that matter. All i can do is hold volume down and power and home and try to ODIN a new bootloader or such and it just fails. what do i do? but when I try to boot into TWRP it goes into a blueish screen with a White exclamation mark saying "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software. I tried to do that but it didnt even recognize the device. At this point i dont care about the data, I just need a working device
Click to expand...
Click to collapse
Happened to me a lot of times in the past few days trying to get MM, for some weird reason flashing Unikernel always works for me (takes me to recovery screen after, then i select 'reboot now'), and all my data, apps etc are still there

emcardle660 said:
Happened to me a lot of times in the past few days trying to get MM, for some weird reason flashing Unikernel always works for me (takes me to recovery screen after, then i select 'reboot now'), and all my data, apps etc are still there
Click to expand...
Click to collapse
will try and update. thank you. didnt work.

Okay guys so now I need a ROM to flash using ODIN. I tried to download from sammobile but the speeds are too damn slow. What I tried to flash was this file " G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar.md5 " and i got the error 3 to 1.

Download Samfirm from here, XDA itself.
Run samfirm, enter model as G920F and your region code.
It will download from Samsung servers, so high speed.
Now flash using Odin the downloaded file by putting the phone in download mode, (vol down+home+power on).
How did it happen?
Did you try to flash the VOD 6.0.1 and got stuck towards the end at hidden.IMG failing the process?
If yes, then its a two minute job. Just open the 6.0.1 tar archive and look for hidden.IMG extract it anywhere and rename it from "hidden.img" to "hidden.img.tar".
Note flash this hidden.img.tar as AP in download mode, your phone should boot.

Failed adb update caused bootloop, dm-verity failure!

Update: The only version of Odin that would work for my phone is 3.11.1 which finally got my phone booting again!
Yes, I know I am an idiot. I realize now that clicking on things that I dont know what they do is a very stupid thing. So anyways, long story short; I was playing around with my new Note 5 phone and rebooted into recovery mode and selected Apply update from adb to see if I could extract and modify an apk file. I did not know I could do an adb sideload with the phone on and I should not be in this screen (I am new to such a thing because I am used to direct access with root but there is no root for this particular phone). So I exit out of the screen with a power button combo to reset it but it kept booting over and over. So I booted into recovery mode and see "dm-verity verification failed..." so I did a wipe data/factory reset then a wipe cache partition and reset the phone but now instead of booting over and over it just boots once to show the android screen then shuts off. I tried using every possible version of Odin to flash the phone but most Odin versions say Failed and the others hang on NAND Write Start!! I have also downloaded the stock firmware from multiple sources because maybe the file I was trying to use was corrupted.
Could anyone help me unbrick my device? I just bought this phone and was absolutely in love with it until this problem. How could such a simple mistake as selecting the wrong option brick my phone?!
5.1.1 oj3 firmware
frp lock: off
RP SWREV: B:2 K:0 S:0

synterror said:
Update: The only version of Odin that would work for my phone is 3.11.1 which finally got my phone booting again!
Yes, I know I am an idiot. I realize now that clicking on things that I dont know what they do is a very stupid thing. So anyways, long story short; I was playing around with my new Note 5 phone and rebooted into recovery mode and selected Apply update from adb to see if I could extract and modify an apk file. I did not know I could do an adb sideload with the phone on and I should not be in this screen (I am new to such a thing because I am used to direct access with root but there is no root for this particular phone). So I exit out of the screen with a power button combo to reset it but it kept booting over and over. So I booted into recovery mode and see "dm-verity verification failed..." so I did a wipe data/factory reset then a wipe cache partition and reset the phone but now instead of booting over and over it just boots once to show the android screen then shuts off. I tried using every possible version of Odin to flash the phone but most Odin versions say Failed and the others hang on NAND Write Start!! I have also downloaded the stock firmware from multiple sources because maybe the file I was trying to use was corrupted.
Could anyone help me unbrick my device? I just bought this phone and was absolutely in love with it until this problem. How could such a simple mistake as selecting the wrong option brick my phone?!
5.1.1 oj3 firmware
frp lock: off
RP SWREV: B:2 K:0 S:0
Click to expand...
Click to collapse
Follow this guide and follow it to a T (link below).. skip down and start at number 6 since you can't get into the phone anyway.. Make sure you use the correct firmware for your phone.
http://forum.xda-developers.com/ver.../downgrade-to-lollipop-5-1-1-verizon-t3368250

FRP lock bricked my device? please help

I made a huge mistake, unticked OEM unlock in developer settings when I was on DEVBASE rom (G930FXXS6ESGD_DevBase_v6.0_encrypt.zip), and now what I'm able to do is:
- flash combination file: COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship.tar.md5, this way I am able to enter recovery and download mode.
- flash stock rom via Odin: G930FXXS3ERLF_G930FORX3ERKF_ORX. After flashing, phone reboots blue screen "sotware update", then "Erasing" , unexpectedly restarts before finishing erasing, and then yellow triangle, " no command". Unable to enter recovery(black screen: #fail to open recovery_cause....), device is stuck in bootloop or I can get to Download mode, but can't turn off the phone.
what can I do? any help appreciated:angel:

lulzor said:
I made a huge mistake, unticked OEM unlock in developer settings when I was on DEVBASE rom (G930FXXS6ESGD_DevBase_v6.0_encrypt.zip), and now what I'm able to do is:
- flash combination file: COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship.tar.md5, this way I am able to enter recovery and download mode.
- flash stock rom via Odin: G930FXXS3ERLF_G930FORX3ERKF_ORX. After flashing, phone reboots blue screen "sotware update", then "Erasing" , unexpectedly restarts before finishing erasing, and then yellow triangle, " no command". Unable to enter recovery(black screen: #fail to open recovery_cause....), device is stuck in bootloop or I can get to Download mode, but can't turn off the phone.
what can I do? any help appreciated:angel:
Click to expand...
Click to collapse
when it goes to the "no command" screen, what happens if you let it sit on that screen for about 3 min or so? also, have you tries keis? i hate keis, but it helped me recover a phone a time or 2 in the past

youdoofus said:
when it goes to the "no command" screen, what happens if you let it sit on that screen for about 3 min or so? also, have you tries keis? i hate keis, but it helped me recover a phone a time or 2 in the past
Click to expand...
Click to collapse
1. it keeps rebooting and heats up
2. Kies doesn't want to connect, but even if it could....I think there is only 1 way: "Firmware upgrade and initialization" menu.... entering model number SM-G930F, and Serial Number ??????
(I was able to look my serial number up in this Factory Binary rom/Combination rom, but Kies states it's not correct which I believe - it looks kinda weird though. I am unable to find my box, since I got this phone used. I don't want to disassemble the back cover to check it on the battery because I would loose water resistance :/ )

Update: I have the box, also I spot the S/N on the back cover

I'm able to flash via Odin U3/S3 roms only(which are designed to my region), but it doesn't remove FRP LOCK...It was be good if any rom could start the google auth process, cause I have access to my google account, it's a silly thing that I got locked out from my system... :crying:

lulzor said:
I'm able to flash via Odin U3/S3 roms only(which are designed to my region), but it doesn't remove FRP LOCK...It was be good if any rom could start the google auth process, cause I have access to my google account, it's a silly thing that I got locked out from my system... :crying:
Click to expand...
Click to collapse
have you tried entering your own gmail account info in the fields where its asking for the previous users info?

the problem is that I can't even get into this menu, none of the stock roms I'm able to flash are booting up, except the Factory Binary (Combination rom). Even the lowest security rom is S3...? That one is actually not bootlooping, able to turn off device, but not booting up, recovery is working here and download mode.
I'm afraid that only a Z3X box software, with the physical box and cable could save this phone....

After ~20h work finally got into the phone!!!
https://www.youtube.com/watch?v=NplMF8O2aTk
this tutorial helped!
So the steps:
1. flash your device compatible Combination file with Odin
2. boot up, enable developer options, check usb debugging to be enabled
3. reboot into recovery, do a factory reset
4. enter Download mode
5. repack your device compatible stock rom's "AP.... .tar.md5" file into a new .tar file so it only contains: boot.img, sboot.bin, system.img
6. flash with odin, enjoy!
7. thank to this guy from the video

lulzor said:
the problem is that I can't even get into this menu, none of the stock roms I'm able to flash are booting up, except the Factory Binary (Combination rom). Even the lowest security rom is S3...? That one is actually not bootlooping, able to turn off device, but not booting up, recovery is working here and download mode.
I'm afraid that only a Z3X box software, with the physical box and cable could save this phone....
Click to expand...
Click to collapse
lulzor said:
After ~20h work finally got into the phone!!!
https://www.youtube.com/watch?v=NplMF8O2aTk
this tutorial helped!
So the steps:
1. flash your device compatible Combination file with Odin
2. boot up, enable developer options, check usb debugging to be enabled
3. reboot into recovery, do a factory reset
4. enter Download mode
5. repack your device compatible stock rom's "AP.... .tar.md5" file into a new .tar file so it only contains: boot.img, sboot.bin, system.img
6. flash with odin, enjoy!
7. thank to this guy from the video
Click to expand...
Click to collapse
awesome to hear that you got past the FRP lock!