Database Info

A: Having Problems Rooting the Note Pro 12.2 SM-P900/905? TRY THIS!

**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!

Need a link to the files you mentioned.

Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?

sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.

Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks

sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin

I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!

sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok

I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.

pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...

Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.

Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:

Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!

your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:

Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !

soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you

Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?

VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.

Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.

sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk

[Q] Nexus has been unusable since 5.0 OTA

As a preface, I keep my Nexus (16GB) stock/unrooted because having it down while flashing ROMs is not an option anymore. I need to the phone to work all the time, period. The irony is ridiculous.
Received the OTA from Sprint a couple of weeks ago, immediately noticed the (often-mentioned) dismal battery life and GPS hasn't been able to connect since that day. As I use GPS daily and need my phone to last for longer than 6 hours--these present full stop problems. This is in addition to the (often mentioned) stuttering/lag/freezing issues which are beyond frustrating as a heavy user. Really Google?!
Over the last week I've:
-Cleared caches multiple times
-Wiped/Factory Data Reset (3 times as it would not allow me to sign into my Google Account or sync apps)
-Spoke with Nexus Support for three hours today, which ended with 'Sorry, you'll have to call Sprint or LG'
-Tried GPS location 'fix' on XDA (didn't work)
-Been unable to send/receive SMS messages for two days
I'm beyond frustrated with this process and with Google for their lack of response in fixing widely-known 5.0 issues...on their own device. This phone is useless at the moment. What are my options? Root and roll back to KitKat? Throw this phone out of the window and go get a G3? I don't want to use a custom ROM/Recovery unless there are no other options.
Thanks for any advice-

993 said:
Over the last week I've:
-Cleared caches multiple times
-Wiped/Factory Data Reset (3 times as it would not allow me to sign into my Google Account or sync apps)
-Spoke with Nexus Support for three hours today, which ended with 'Sorry, you'll have to call Sprint or LG'
-Tried GPS location 'fix' on XDA (didn't work)
Click to expand...
Click to collapse
For the problems you're describing, you really haven't done much to solve it.
Unlock the bootloader, flash a factory image, relock the bootloader.

Why would you speak to Nexus support for 3 hours for? Waste of time

Frankly, I wanted to see if they would even acknowledge any of the issues that appear to be quite common recently with 5.0. They clearly did not, and it was relatively little effort wasted as it was through Hangouts (on a desktop though, phone forgot how to Hangout).
I have not tried to flash the bootloader, as I said I want to keep this phone as OEM as possible. Since that doesn't appear to be an option I will update when it's complete.

993 said:
I have not tried to flash the bootloader, as I said I want to keep this phone as OEM as possible. Since that doesn't appear to be an option I will update when it's complete.
Click to expand...
Click to collapse
Please read the stickies and take advantage of the knowledge base. My suggestion keeps the phone absolutely stock. It's telling that you couldn't recognize that.

I agree, just flash the stock image from fastboot.
Sent from my Nexus 5 using Tapatalk

Wakamatsu said:
Please read the stickies and take advantage of the knowledge base. My suggestion keeps the phone absolutely stock. It's telling that you couldn't recognize that.
Click to expand...
Click to collapse
That isn't what the Nexus rep said (reps have been known to be misinformed). I have read the relevant stickies and am aware of how to use this site. You didn't read my question. As I said, I would rather not flash if there are other viable options. IF this is the only workable solution thus far for people experiencing the above listed issues then OK. Thanks for your suggestion.

993 said:
That isn't what the Nexus rep said (reps have been known to be misinformed). I have read the relevant stickies and am aware of how to use this site. It is telling you didn't read my question. As I said, I would rather not flash if there are other viable options. IF this is the only workable solution thus far for people experiencing the above listed issues then OK. Thanks for your suggestion.
Click to expand...
Click to collapse
Flash the factory image. OTAs sometimes fail to implement properly. What you are describing is almost certainly that. You've already tried everything you can to fix the issues short of flashing. So flash.

You either have bad hardware, or the upgrade didn't install correctly. As others have mentioned, flashing the factory image should work.

993 said:
You didn't read my question. As I said, I would rather not flash if there are other viable options.
Click to expand...
Click to collapse
You said that you don't want to flash a custom rom. A factory image is what is installed on the Nexus by Google. Again, you're betraying a lack of knowledge on this subject.

If you wanted stablity you should of stayed on kitkat, hence why i never updated, you a os i can rely on and thats currently 4.4, as usual android builds at the start have minor issues and we wait for google to fix them.
I usually dont update till the devs can get a functioning build thats suitable for the community.
as above,
Fastboot oem unlock, flash 4.4 or 5.0 google image, relock bootloader
If he doesnt want to flash a custom rom then he should know how to flash a stock rom.
https://developers.google.com/android/nexus/images

I don't even speak to my own family for 3 hours, let alone a complete stranger lol wow

Wakamatsu said:
You said that you don't want to flash a custom rom. A factory image is what is installed on the Nexus by Google. Again, you're betraying a lack of knowledge on this subject.
Click to expand...
Click to collapse
Here's what's been done so far several times over:
Unlocked Bootloader
Installed SDK kit from Google using their walk though
Attempted ADB sideload of Google Factory images (5.0 then 4.4) from appropriate modes on CWM and TW
Attempted Fastboot (works only with CWM, no push/pull)
Multiple Full Wipes in both recoveries
Attempted ADB commands through terminal (W7 Pro - Admin)
Uninstalled, Reinstalled all recommended device driver packages, only recognizes in device manager as 'Google Nexus ADB Device' not Explorer Shell (read relevant FAQs) regardless of driver.
Used multiple USB ports/cables, rebooted PC each change in configuration
Root Toolkit 1.9.9 does not recognize through ADB
As of current, only Bootloader (unlocked) and Recovery mode work. I cannot access the SD card of the device through any means I've tried. The last that the OS booted I ensured that USB debugging was on in Settings. ADB mode in either recovery does not change device recognition on PC, nor does file system appear. System will not boot to ensure debugging setting has remained. Same issues with a laptop with no known prior driver issues.

993 said:
Attempted ADB sideload of Google Factory images (5.0 then 4.4) from appropriate modes on CWM and TW
Attempted Fastboot (works only with CWM, no push/pull)
Click to expand...
Click to collapse
You can't sideload a factory image. Fastboot commands are executed in bootloader, not recovery.

That should read that 'fastboot only responds to commands while CWM is the recovery'.
I can flash recoveries by this method from CMD but anything else (ROMS, etc) show progress but end before completion.

993 said:
That should read that 'fastboot only responds to commands while CWM is the recovery'.
I can flash recoveries by this method from CMD but anything else (ROMS, etc) show progress but end before completion.
Click to expand...
Click to collapse
Dude, you really need to read and understand the stickies before you do something bad to your phone. You are just flailing right now.
And really, all you needed to read was the install instructions on the Google factory image page.
1) Unlock bootloader
2) Unzip the factory image zip
3) Reboot in to bootloader
4) Run the flash-all script in the factory image folder.

This was the first method I tried. I have downloaded the factory image from Google several times and I get an 'unexpected end of data' message in 7zip when extracting my copies. Downloading from Google has been hit or miss with 'unknown network error' that halts the download, not sure what that could be.
I am trying to pinpoint the cause of these issues, as flashing back to factory without good images won't be possible. I understand how straightforward a factory flash should be especially with OEM tools but in my case I keep running into roadblocks.

Disable your antivirus and firewall during the download, that may help.

gee2012 said:
Disable your antivirus and firewall during the download, that may help.
Click to expand...
Click to collapse
Thanks for your suggestion. I disabled MSE + Firewall on the W7 machine and attempted to download [hammerhead-lrx21o-factory-01315e08.tgz] again from Google with the same error result, halting the download before completion.
My main machine, a Chromebook, will download the file completely however the zip cannot be moved without losing file size (downloads the entire 556.3MB, however once moved it magically becomes 417.2MB).
Further, I went to the Sprint Store today (I know) to see what the techs could do about pushing the factory image on the device. After about 30 minutes, they came back with "You should call Google". Brilliant. Now all I need is someone to suggest I call LG and the trifecta will be complete.

993 said:
Thanks for your suggestion. I disabled MSE + Firewall on the W7 machine and attempted to download [hammerhead-lrx21o-factory-01315e08.tgz] again from Google with the same error result, halting the download before completion.
My main machine, a Chromebook, will download the file completely however the zip cannot be moved without losing file size (downloads the entire 556.3MB, however once moved it magically becomes 417.2MB).
Further, I went to the Sprint Store today (I know) to see what the techs could do about pushing the factory image on the device. After about 30 minutes, they came back with "You should call Google". Brilliant. Now all I need is someone to suggest I call LG and the trifecta will be complete.
Click to expand...
Click to collapse
Try LG to see if they will help. Haha had to.
Can you not download on your phone? I'm not familiar with sending MMS but does it work forcing your phone to 1x? I'm trying to think of ideas. What all apps do you have installed?
Sent from my Nexus 5 using XDA Free mobile app

[Completed] Currently panicking: root gone wrong

First of all, sorry if I am posting this in the wrong thread or wrong area.
I'm seriously depressed and deprived of sleep because I finally rooted my phone and everything went wrong.
Yeah, I fell in with that crowd. Shame on me, i know ,_,
Samsung Galaxy Note 3 SM-N900W8 is the victim. I downloaded CF AUTO ROOT HLTECAN HLTEUB SMN900W8 which, apparently, should have had no problem. Used Odin 3.07 on my laptop and the process was smooth and quick. Buuuut of course my phone got mostly wiped (no surprise here, totally worth the root). Along with that wipe came the rage of Google and Samsung.. don't know why but most apps just force close when I try to open them.
Long-story short I need to regain access to my Google account, my messages (so I can, you know, message my grandmother so she can pick me up at the university) and the ability to have a functional good phone.
I've learned my lesson, I'm leaving this rooting stuff to the more apt. However I need guidance on how to what I believe is called "flash" the system back into having all the permissions it used to have. Not sure what I'm talking about any more.
If it is possible to keep the root and somehow fix the problem (regain access to basic services such as messages and play store) that'd be nice. But really, I just wanna travel back in time and forget this ever happened so late at night that it's almost morning and my feelings are extra hurt.

Hello Dear ,
Its ok just re install the official rom for ur device n900w8 after that just do a full for ur device through stock recovery then install twrp through odin in AP tap from this link
https://twrp.me/devices/samsunggalaxynote3canada.html
After that boot ur phone to custom recovery then install supersu from this link
https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
That's all for rooting ur device mate
Thank You ,

Thanks for the help! But I'm still a bit lost. I did as you suggested and found the 5.0 stock firmware, which I am currently downloading. I will open Odin, plug in my phone, put the firmware file in the AP slot and install it from the download screen on my phone. Same process as the rooting that failed earlier.
However, I don't get the TWRP part.
"after that just do a full for ur device through stock recovery then install twrp through odin in AP tap from this link"
Is that step necessary, or is it just in case I want to try rooting my device again? Also, in the list you provided doesn't seem to be 5.0/lollipop for the phone. But then again, I'm not entirely sure how all that works.
Thanks again!

Installing the Stock firmware did not work. Once the phone boots, everything stops working unexpectedly.
Oh well, I guess it's time to take it to a store ,_,
Thanks anyways!

I am in utter shock. For some strange reason, factory reset worked and my phonne is ok. Not sure how... but it actually worked!

Nice to hear that mate congrats then

Downgrade from 7.0 nogat and get Root to 5.1.1

First of all, don't get your hopes high, i rooted as traditional method like many others. I'm flashaholic and i started new thread for those who upgraded intentionally or accidentally and now think download would brick their sets. it won't. things are pretty obvious here but i repeat I'm sharing this to people who've upgraded for any reasons and have no clue how to downgrade or achieve root.
So i bought a cell (sm g920V) with preinstalled PI2 (MM6.0.1) . found out pingpong root is avail only for 5.02 . i was afraid to downgrade so i searched more. found out nogat 7.0 DQD1 has root. and can be rooted via cf autoroot. i upgraded and i tried. but it didn't worked. on nougat i did everything. tried every root app (both pc and apk ver) but failed. i decided to go back.
here i found This thread by @toutanje which said even i upgraded to nougat, i can safely downgrade to PK2 (6.0.1) , PH1 (6.0.1) and BOG7 (5.1.1) . i flashed BOG7 (5.1.1) directly because during search i've foundout that there is temporary root available for BOK7, and they both are 5.1.1. i did this because BOG7 is earlier version than BOK7, for this i won't have to downgrade but to upgrade that i did. i flashed BOK7 and headed Here, a thread by @klip1 . there wasn't any clear instructions not links no attachments. but thanks to @MrMike2182 who shared main file Here. BEWARE that you'll lose root each time you reboot, but you can gain it back easily by running root apk simply from your mobile. this is better then not having one.
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrage to BOK7), then flash BOK7, odin Sboot file (attached). you'll see some yellow codes above when restart. i was stuck there with bootloop on VZ logo. all you need to do is to factory reset. (by pressing and hold vol + & vol down + power button until you see black screen with options. press vol down and highlight second option factory data and reset. now press home button. )
phone will start normally, goto devloper options, enable usb debug, allow unknown sources and than root it with kingroot apk. done.
Those who prefer SuperSu can get lead from Here thanks to @EvilRubberDuck. but i am not sure about point 3. there is nothing attached at first post. tough little search may lead you to success.
Thanks to whoever took even little interst to make this beast rooted. please try to get permanent root for this device too. if anyone know how to get it, or any more info regarding rooting this device. please share. let me aware. i'll really appreciate that.
NOTE : i take no responsibility of what you do to your mobile. you're doing it with your own consent. if you're unsure what you're doing, don't do it. I, developers/members mentioned and xda are not responsible for ANYTHING or what you do to your phone.

Sharjeel.Khan said:
First of all, don't get your hopes high, i rooted as traditional method like many others. I'm flashaholic and i started new thread for those who upgraded intentionally or accidentally and now think download would brick their sets. it won't. things are pretty obvious here but i repeat I'm sharing this to people who've upgraded for any reasons and have no clue how to downgrade or achieve root.
So i bought a cell (sm g920V) with preinstalled PI2 (MM6.0.1) . found out pingpong root is avail only for 5.02 . i was afraid to downgrade so i searched more. found out nogat 7.0 DQD1 has root. and can be rooted via cf autoroot. i upgraded and i tried. but it didn't worked. on nougat i did everything. tried every root app (both pc and apk ver) but failed. i decided to go back.
here i found This thread by @toutanje which said even i upgraded to nougat, i can safely downgrade to PK2 (6.0.1) , PH1 (6.0.1) and BOG7 (5.1.1) . i flashed BOG7 (5.1.1) directly because during search i've foundout that there is temporary root available for BOK7, and they both are 5.1.1. i did this because BOG7 is earlier version than BOK7, for this i won't have to downgrade but to upgrade that i did. i flashed BOK7 and headed Here, a thread by @klip1 . there wasn't any clear instructions not links no attachments. but thanks to @MrMike2182 who shared main file Here. BEWARE that you'll lose root each time you reboot, but you can gain it back easily by running root apk simply from your mobile. this is better then not having one.
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrage to BOK7), then flash BOK7, odin Sboot file (attached). you'll see some yellow codes above when restart. i was stuck there with bootloop on VZ logo. all you need to do is to factory reset. (by pressing and hold vol + & vol down + power button until you see black screen with options. press vol down and highlight second option factory data and reset. now press home button. )
phone will start normally, goto devloper options, enable usb debug, allow unknown sources and than root it with kingroot apk. done.
Those who prefer SuperSu can get lead from Here thanks to @EvilRubberDuck. but i am not sure about point 3. there is nothing attached at first post. tough little search may lead you to success.
Thanks to whoever took even little interst to make this beast rooted. please try to get permanent root for this device too. if anyone know how to get it, or any more info regarding rooting this device. please share. let me aware. i'll really appreciate that.
NOTE : i take no responsibility of what you do to your mobile. you're doing it with your own consent. if you're unsure what you're doing, don't do it. I, developers/members mentioned and xda are not responsible for ANYTHING or what you do to your phone.
Click to expand...
Click to collapse
If you use the SuperSU instead of KingRoot then you can use my installroot script and then the rootatboot if you need to reboot for some reason however if you are not near a PC at the time and you really need to reboot then use terminal emulator from the play store and open it and type su then enter and on the next line type pkill zygote and voila reboots without PC.

MrMike2182 said:
If you use the SuperSU instead of KingRoot then you can use my installroot script and then the rootatboot if you need to reboot for some reason however if you are not near a PC at the time and you really need to reboot then use terminal emulator from the play store and open it and type su then enter and on the next line type pkill zygote and voila reboots without PC.
Click to expand...
Click to collapse
yes i've read this post of yours, i should've added this. Glad you came here and i really appreciate your efforts for s6 users. you've done great job for us.
it'll be great if you attach your script and write or quote your method here too. so users don't have to go through earlier threads and finding things. like me who bought this phone pretty late.
right now i'm using quickreboot apk to get hot reboot which keeps the root. but sometimes when you really need to restart. i see your solution as best.

Sharjeel.Khan said:
yes i've read this post of yours, i should've added this. Glad you came here and i really appreciate your efforts for s6 users. you've done great job for us.
it'll be great if you attach your script and write or quote your method here too. so users don't have to go through earlier threads and finding things. like me who bought this phone pretty late.
right now i'm using quickreboot apk to get hot reboot which keeps the root. but sometimes when you really need to restart. i see your solution as best.
Click to expand...
Click to collapse
OK so my phone is on 5.1.1, it was originally on 7.0 so you can downgrade back to the 5.1.1 firmware.. I've included in the file the eng kernel and eng sboot but there's different versions so this one in my file called boot.tar is from the eng kernel to the S6 G925V so if you're using G920V you need to get the eng kernel for that one.. Now first you put the phone into download mode and flash the eng kernel using odin and after the phone boots then using Windows command prompt navigate using the cd command to where the file is you downloaded called S6rootbyMrMike2182 once you're in there type installroot and the script should run and flash everything needed including busybox and then the phone will reboot (it will also boot just this one time without using the rootatboot because the same codes in this file too) now when you click on the SuperSU app it's going to say it needs to update su ignore it and go right to the play store and install/update the SuperSU from there and then the phone should be rooted and ready to go.. If you ever need to reboot for some reason connect the phone to your PC and open a command prompt in the same folder again and run rootatboot and it will set the phone as permissive again so it boots.. You can unplug it after you see the Verizon logo.. If for some reason you aren't near a computer and you really need to reboot then use terminal emulator from the play store and open it and type su and grant root access and then on the next line type pkill zygote and voila reboots without a computer
If you have KingRoot on your phone and you want to get rid of it to use SuperSU thanks to @Chainfire then use this script that I'm listing below.. Also keep terminal emulator open while you are doing this because you might(not all devices just some) get a continuous annoying popup that prevents you from doing anything (thanks to KingRoots junk) so you'll have to use terminal emulator to kill/end that process in order to continue and after you kill/end that process then go delete it immediately! Links to root with SuperSU and KingRoot removal are below!
S6EdgeRootByMrMike2182
KingRoot removal script
G920V ENG Sboot
By the way I nor XDA-DEVELOPERS is responsible for anything you choose to do to your phone! If something goes wrong, just reflash your original firmware but don't go blaming me nor XDA because I don't have to put this up so please do your research before messing with your phone and as always, make a backup of everything you wish to keep! And no this will not delete or wipe your phone unless you choose to! Links are above. You can change it or whatever just give props where it's due!!
SERIOUSLY MAKE A BACKUP OF ALL YOUR PICTURES ETC ETC BEFORE DOWNGRADING AND I'M NOT KIDDING!!!

MrMike2182 said:
OK so my phone is on 5.1.1, it was originally on 7.0 so you can downgrade back to the 5.1.1 firmware.....
Click to expand...
Click to collapse
great. you completed the thread :highfive:
Didn't know about script removing kr.. wil give it a try for sure. :good:

ok i'm getting confuse here. can you please provide exact files that needed to flash on g920V please ? i mean eng kernel and sboot ? and the file with odin says "G920A_Kernel_Root_5.1.1_S****.tar", A ? isn't A refers to at & t ?
i'm afraid if i may flash wrong file. can you please help me here with exact files needed for us (G920v) ?
and when i'm running installroot via cmd, it execute it goes like it created by you until daemon started successfully for like for five to 8 sec and then disappear. phone doesn't reboot. nothing happens. ,

can anyone confirm if i can directly downgrade to BOK7 ? im currently on DQD1 also can anyone guide me how to actually flash my phone like step wise im new here.. I upgraded to 7.0 but I desperately want root now I've odin installed i just need some1 to teach me how to do it like where to select sboot file and other files
Thanks

Sharjeel.Khan said:
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrade to BOK7), then flash BOK7.
Click to expand...
Click to collapse
Muhammad Aliyan said:
can anyone confirm if i can directly downgrade to BOK7 ? im currently on DQD1 also can anyone guide me how to actually flash my phone like step wise im new here.. I upgraded to 7.0 but I desperately want root now I've odin installed i just need some1 to teach me how to do it like where to select sboot file and other files
Thanks
Click to expand...
Click to collapse
welcome here. first things first, i don't mean to discourage you but if you don't know about where to "put sboot and other files", you really shouldn't be doing this. additionally downgrading is a risky process where things get messy due to single mistake .
To answer your question directly, NO. i've read a post somewhere here that we can only downgrade to mentioned (in 1st post) firmware. OP there tried to downgrade to other fw but failed.
and that is exactly why i did long and safe procedure and downgraded to BOG7 and then BOK7. . both are 5.1.
2nd question : you need to put sboot file in "AP" section of odin. (be careful with using it)
i assume you have G920V, which have locked bootloader, my suggestion would be... its not worth it. trust me. even if you downgrade, and rooted too, you'll loose root if you restart your device. and you cannot install recovery and so on. there is no permanent root for this device.
Exchange your device for international version or so, either wait for it and enjoy being on nougat. devs are working on it may be. some claim to root nougat too. better don't downgrade and much better if you stop right there when you don't have basic knowledge about this. you'll end up having paper weight instead of device.

Sharjeel.Khan said:
welcome here. first things first, i don't mean to discourage you but if you don't know about where to "put sboot and other files", you really shouldn't be doing this. additionally downgrading is a risky process where things get messy due to single mistake .
To answer your question directly, NO. i've read a post somewhere here that we can only downgrade to mentioned (in 1st post) firmware. OP there tried to downgrade to other fw but failed.
and that is exactly why i did long and safe procedure and downgraded to BOG7 and then BOK7. . both are 5.1.
2nd question : you need to put sboot file in "AP" section of odin. (be careful with using it)
i assume you have G920V, which have locked bootloader, my suggestion would be... its not worth it. trust me. even if you downgrade, and rooted too, you'll loose root if you restart your device. and you cannot install recovery and so on. there is no permanent root for this device.
Exchange your device for international version or so, either wait for it and enjoy being on nougat. devs are working on it may be. some claim to root nougat too. better don't downgrade and much better if you stop right there when you don't have basic knowledge about this. you'll end up having paper weight instead of device.
Click to expand...
Click to collapse
But on 5.1.1 my battery life was so good now it just keeps draining even on power saving just drain and drain I previously also upgraded using Odin from 5.1.1 to 7.0 (biggest mistake) and i'm regretting it although its much better it terms of improvements and performance i just cant live with this battery life also i need root for WifiKill and to hack in-app purchases .. and i don't reboot my device often..
so if im downgrading to both of these BOK7 or BOG7 i need to use the sboot file u provided right ?

Muhammad Aliyan said:
But on 5.1.1 my battery life was so good now it just keeps draining even on power saving just drain and drain I previously also upgraded using Odin from 5.1.1 to 7.0 (biggest mistake) and i'm regretting it although its much better it terms of improvements and performance i just cant live with this battery life also i need root for WifiKill and to hack in-app purchases .. and i don't reboot my device often..
so if im downgrading to both of these BOK7 or BOG7 i need to use the sboot file u provided right ?
Click to expand...
Click to collapse
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:

Sharjeel.Khan said:
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Click to expand...
Click to collapse
Quick question if i can root my device with this method it possible to install xposed framework via Flashfire?, just a question.
If not possible install xposed not a problem, better root than nothing, and i am not reboot so much, to say nothing.
And like say Muhammad Aliyan, the battery in 7.0 is much more less than 5.1.1
(Sorry for my bad english.)

LuisElListo said:
Quick question if i can root my device with this method it possible to install xposed framework via Flashfire?, just a question.
If not possible install xposed not a problem, better root than nothing, and i am not reboot so much, to say nothing.
And like say Muhammad Aliyan, the battery in 7.0 is much more less than 5.1.1
(Sorry for my bad english.)
Click to expand...
Click to collapse
i have tried it earlier and failed but now when i saw youre asking this, i gave it another try and i'm stuck on bootloop. lol.
better don't do it.
i've read it that xposed is not compatible to our devices (64bit) yet ( just read it not confirming it) + in xposed official thread, it has been warned that bootloops occur in samsung stock roms. soi'd say do not try this.

Sharjeel.Khan said:
i have tried it earlier and failed but now when i saw youre asking this, i gave it another try and i'm stuck on bootloop. lol.
better don't do it.
i've read it that xposed is not compatible to our devices (64bit) yet ( just read it not confirming it) + in xposed official thread, it has been warned that bootloops occur in samsung stock roms. soi'd say do not try this.
Click to expand...
Click to collapse
So close, well better wait to safe method in stock room, or unlock bootloader. Thanks anyway.

Sharjeel.Khan said:
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Click to expand...
Click to collapse
everything was good I downgraded to BOG 7 first with odin all good then OK7 and again all good successfully booted up everything is fine fingerprint sensor etc right after i flash the sboot file my fingerprint sensor stopped working it says an error occurred can you please help me .. phone is rooted though but cmon fingerprint sensor i can't live without it..
Edit: tried factory reset and restarting, none worked.
edit2: reflashed OK7 again and its fingerprint is working but can't root. flashed sboot to root but fingerprint stopped working.
edit3: again flashed OK7 then sboot again green text in the corner again root succeed but again fingerprint not working guess something wrong with the sboot..

Muhammad Aliyan said:
everything was good I downgraded to BOG 7 first with odin all good then OK7 and again all good successfully booted up everything is fine fingerprint sensor etc right after i flash the sboot file my fingerprint sensor stopped working it says an error occurred can you please help me .. phone is rooted though but cmon fingerprint sensor i can't live without it..
Edit: tried factory reset and restarting, none worked.
edit2: reflashed OK7 again and its fingerprint is working but can't root. flashed sboot to root but fingerprint stopped working.
edit3: again flashed OK7 then sboot again green text in the corner again root succeed but again fingerprint not working guess something wrong with the sboot..
Click to expand...
Click to collapse
thats strange because i had FP working while rooted from same sboot file that i attached.
try downloading from another source like in second post where mrmike2182 shared it. and try removing Samsung account (if its there, don't forget to turn off reactivation lock before that.)
see if it helps.

Sharjeel.Khan said:
thats strange because i had FP working while rooted from same sboot file that i attached.
try downloading from another source like in second post where mrmike2182 shared it. and try removing Samsung account (if its there, don't forget to turn off reactivation lock before that.)
see if it helps.
Click to expand...
Click to collapse
Same issue with this flash OK7 FP work ok, but install Sboot and FP not working.
edit1: cant root the device i open cmd with adm permission, installroot, daemon is stop, is starting, after close cmd and the phone not reboot.

LuisElListo said:
Same issue with this flash OK7 FP work ok, but install Sboot and FP not working.
edit1: cant root the device i open cmd with adm permission, installroot, daemon is stop, is starting, after close cmd and the phone not reboot.
Click to expand...
Click to collapse
hmm. i believe FP didn't came friendly with this sboot. any experienced dev might help us out here
make sure you have proper drivers installed and have working adb. read instructions, search fourm. by the way, for same kind of issues, i had to go with kingroot.

Sharjeel.Khan said:
hmm. i believe FP didn't came friendly with this sboot. any experienced dev might help us out here
make sure you have proper drivers installed and have working adb. read instructions, search fourm. by the way, for same kind of issues, i had to go with kingroot.
Click to expand...
Click to collapse
Well better than nothing, uninstall all bloatware for my phone (finally), FP sensor yes it to cool but, meee y si better pin or patron.
Just have to try install Xposed and all done.
Do you try to install official xposed? Or the unofficial for Samsung Stock https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960

LuisElListo said:
Well better than nothing, uninstall all bloatware for my phone (finally), FP sensor yes it to cool but, meee y si better pin or patron.
Just have to try install Xposed and all done.
Do you try to install official xposed? Or the unofficial for Samsung Stock https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
i'd love to try right now but i can't because i'm currently working on something else.
but for your assistance, Here is what you're looking for. its a success.

Sharjeel.Khan said:
i'd love to try right now but i can't because i'm currently working on something else.
but for your assistance, Here is what you're looking for. its a success.
Click to expand...
Click to collapse
I try a shoot.
Its working, its ****ing working, I sacrifices FP, and Supersu but I dont mind i have xposed and a root.
imgur(dot)com/a/zLvrD
Edit1: bad news activated module xposed requeried reboot, soo the root is lost and requiered to root again with kingroot the problem is my percent is not advance 01%. Also every time I rooted the phone is slowing arriving a point where it restarted alone and is only 01%.
If i a factoy reset i lost xposed and root or better reflash the Rom OK7?

HELP. Samsung SM-J327a root.

Hello Forum,
I am in desperate need of rooting my old Galaxy Express Prime 2 (SM-J327a), because I accidentally deleted all of my images. I cannot find a .tar file to recover the device. I checked TWRP's site, and they don't have a file to support this device yet. Does anyone know another way to root this device, or where I can find a .tar file to use with Odin? I have tried virtually all root apps and programs.
Thank you,
Mosaic Owl

I would like to second this request (though I am not near as desperate). Has anyone tried using the Samsung one click root method for this phone?

Link to modded Odin to skip SHA256
Hydran said:
I would like to second this request (though I am not near as desperate). Has anyone tried using the Samsung one click root method for this phone?
Click to expand...
Click to collapse
I tried loading up One Click Root on my laptop and it said it couldn't find its servers. I also tried flashing twrp for a similar Boost phone, (SM-J327p) knowing there was a risk of bricking it. My J327a was free and I plan to stick with my Moto, so I could afford to risk it, plus I've always been able to un brick anything from graphics cards to phones and game systems.
Anyway, Odin 3.12 gets a few steps into the twrp install, but before it actually begins to install, an error pops up that says "SHA256 is invalid". I searched for a couple of hours, and all I can come up with is that AT&T put an extra check in there to see where the files were coming from, and attempting to install custom recovery will cause this error. A modified Odin was released to skip this check on an older phone, but I could not find a working link to it.
That's what I came here for: a link to the modified Odin that will allow me to install TWRP without that check. If it's posted, DO NOT try flashing the wrong twrp recovery if you can't afford having it bricked for a while like I can.

I guess you would need to start with an eng bootloader that will let your phone boot then work on a tethered root... I'm still looking for binary 2 with rev 2 combination file without luck, all I need is to extract the boot and see if I can reset lock pattern. I tried google account but it does not have the option to lock-relock screen anymore. It's my nephew's phone and my daughter messed it up. I can login the google account and make it ring and locate it but can't disable the pattern. He has no backup of this phone...

Have any one make it done?