Database Users

Rooting Kindle Fire HDX 7 32 GB 3rd Gen Fire OS 13.3.2.1 Wrapup

Rooting Kindle Fire HDX 7 32gb 3rd Gen Fire OS 13.3.2.1
Airplane Mode ON WIFI Off
Kindle Fire ADB Composite Drivers must be installed to working PC
In KFHDX Settings
Set Enable ADB - ON
Set Apps from unknown sources - ON
Faznx's KF-HDX Toolkit v0.95
https://www.androidfilehost.com/?fid=95832962473395302
KFHDX ToolKit v0.95.zip
MD5: 3C1D7DB855E54A39BF2FD59BE6ABA9DC
SHA-256: 614A0D077BEC8B85F6D6B377D2D18EB719AB9ED15B08B41CD5 8968BEED653C0C
Rooted KFHDX using Towelroot in above toolkit. - No Issues
Then applied:
1> SuperSU v2.14 installer in Faznx's KF-HDX Toolkit v0.95 - No Issues
2> Over the air update blocker and re-enabler for all current rootable versions in Faznx's KF-HDX Toolkit v0.95 - No Issues
Airplane Mode ON WIFI Off
Use adb to install ES File Explorer
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
ADB install (installs application) -- adb install c:\com.estrongs.android.pop.apk - No Issues
Checked in ES File Manager to make sure I had root.
Next rename the /system/etc/security/otacerts.zip file - one issue - resolved
Even though I ran the disable OTA updates, I am concerned that some post I have read said their system was update even though they renamed.
I think now it's possible they get around us by running an MD5 hash on files in that folder and compare to the hash they store for that version.
The better idea may be to move that file out of that folder. I did just that.
Here are the directions to rename:
see the contents of that folder with adb shell ls -Ral /system/etc/security
Example:
C:\Users\davcam\AppData\Local\Android\sdk\platform-tools>adb shell ls -Ral /system/etc/security
/system/etc/security:
drwxr-xr-x root root 2014-02-07 04:23 cacerts
-rw-r--r-- root root 1337 2014-02-07 04:23 otacerts.zip
Before you can rename this file you must set the \ and \system file systems to r/w - then you can rename or mv the file.
When completed, change \ and \system file systems back to ro
Next : Safestrap
https://goo.im/devs/Hashcode/thor/safestrap/
I tried Safestrap-Thor-3.72.apk and it did not seem to work. I unistalled recovery and Safestrap-Thor-3.72.apk.
I was able to successfully install Safestrap-Thor-3.75-os3.2.4-B02.apk, install recovery, boot into recovery, backup up stock, create a new rom slot,
change to that Rom slot and restore stock backup into that slot.
Now on startup i get the Safestrap screen.
One thing I noticed was that the stock values for the rom slots are a little small, so keep that in mind.
Thanks to everyone on XDA Forums, especial to EncryptedCurse for the terse, meaningful tips., Faznx's KF-HDX Toolkit v0.95, Geohot's Towelroot,
hashcode0f's Safestrap, OTA disable, and Supersu.
Current Status:
Using a copy of stock on a somewhat larger partition, no otacerts.zip file
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!

reggie9 said:
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!
Click to expand...
Click to collapse
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!

Edit: Looks like jeryll already said it.

jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Thanks! I appreciate the heads up. Any idea where I can locate TWRP 2.8.4.0 for this device?
Sorry - Found it here: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
Reggie9

jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.

reggie9 said:
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.
Click to expand...
Click to collapse
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup

jeryll said:
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup
Click to expand...
Click to collapse
jeryll - Thanks for the the thoughtful response - will study this. - reggie9

[SM-P905] Upgrade to Rooted Official Lollipop 5.0.2 - can be downgraded

** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
This has been tested with the Italian firmware released on 4/30/2015, PDA: P905XXUABOD7, CSC: P905ITVABOD7 (of course the language can be set to English after installation). This method should however work for other Lollipop releases as they become available in your region. This method does not trip the knox flag.
Requirements
1- Rooted KitKat (the easiest way to get root is to flash a ROM dated before June 2014 and root it with Towelroot).
2- FlashFire app v 0.17 or higher: The only way to get it is by following the instructions at: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Procedure
1- Make a back up of all your files.
2- Download your Lollipop ROM from Sammobile and unzip the .zip file to get the tar.md5 file. Copy the tar.md5 file to your sdcard.
3- Run FlashFire. Tap the +, Flash Firmware Package, and select the tar.md5 file. It will scan the file and opens a menu of option to choose.
4- Choose: Boot, Recovery, System, Cache, Preloaded/Hidden.
Also choose Highly recommended but optional: Modem Firmware (modem.bin) and Firmware (NON-HLOS). If you select these you should answer NO when it asks you "You are flashing both normal and ..."
The rest should be unchecked. Now tap the check mark at the top right corner of the dialog box.
5- When that is done, FlashFire adds two items to the list of actions: Process Cache and EverRoot. Open process cache and uncheck all the items. Open EverRoot and select Inject SuperSU and unckeck the other options.
6- Tap the + again and choose Wipe. Select System, Dalvik, and Cache. I highly recommend that you check 3rd party apps too, which will erase your existing apps and settings but it will give you a clean install. Do not select Internal storage.
7- Tap and hold to move the boxes containing the actions to get them in this order: Wipe, Flash Firmware Package, followed by the rest.
8- Tap the Reboot box and select Reboot to Recovery.
9- Hit the FLASH sign at the bottom of the page and hit OK. THE SCREEN WILL GO COMPLETELY BLANK DURING THE FLASHING OPERATION. Do not freak out. This is a bug in the tool and will hopefully be fixed in a future version. After 5-10 minutes your tablet reboots. If it takes longer than 20 minutes something is wrong.
10- During the first reboot it may take 5-10 minutes before you get the initial setup dialog. (If it takes longer than 20 minutes something is wrong.) Complete it and you will be on rooted Lollipop.
TiP: Settings -> General -> Security -> Security Policy Updates -> Uncheck Automatic Updates, and also Settings -> General -> About Device -> Software Updates -> Uncheck Auto Updates
Troubleshooting
If after the upgrade you suspect something does not work, install Flashfire on your rooted lollipop and start from step 4 again.
If you experience random reboots freeze or otherwise disable knox and update programs.
Downgrade
If you are not happy with the results, or something goes wrong, download a KitKat firmware from Sammobile and flash it in ODIN. Make sure to clean cache and data in recovery.

najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
This has been tested with the Italian firmware released on 4/30/2015, PDA: P905XXUABOD7, CSC: P905ITVABOD7. This method should however work for other Lollipop releases as they become available in your region. This method does not trip the knox flag.
Requirements
1- Rooted KitKat (the easiest way to get root is to flash a ROM dated before July 2014 and root it with Towelroot).
2- FlashFire app v 0.16 or higher: The only way to get it is by following the instructions at: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
3- SuperSU update zip version 2.46 or higher.
Procedure
1- Make a back up of all your files
2- Download your Lollipop ROM from Sammobile, unzip it and copy the tar.md5 file to your sdcard
3- Download SuperSU update zip and copy it to the sdcard.
4- Run FlashFire.
5- Tap the +, Flash Firmware Package, and select the tar.md5 file. It will scan the file and opens a menu of option to choose.
6- Choose: Boot, Recovery, System, Cache, Preloaded/Hidden.
Optional: Modem Firmware (modem.bin) and Firmware (NON-HLOS). If you select these you should answer NO when it asks you "You are flashing both normal and ..."
The rest should be unchecked. Now tap the check mark at the top right corner of the dialog box.
7- When that is done, FlashFire adds two items to the list of actions: Process Cache and EverRoot. Open each one and uncheck all the items under both
8- Tap the + again and choose Wipe. Select System, Dalvik, and Cache. I highly recommend that you check 3rd party apps too, which will erase your existing apps and settings but it will give you a clean install. Do not select Internal storage unless you want your internal SD card erased too.
9- Tap the + again, Flash Zip or OTA, and select the SuperSU update Zip. Leave Automount unchecked
10- Tap and hold to move the boxes containing the actions to get them in this order: Wipe, Flash Firmware Package, Flash Zip or OTA, followed by the rest.
11- Hit the FLASH sign at the bottom of the page and hit OK. THE SCREEN WILL GO COMPLETELY BLANK DURING THE FLASHING OPERATION. Do not freak out. This is a bug in the tool and will hopefully be fixed in a future version. After 5-10 minutes your tablet reboots. If it takes longer than 20 minutes something is wrong.
12- During the first reboot it may take 5-10 minutes before you get the initial setup dialog. (If it takes longer than 20 minutes something is wrong.) Complete it and you will be on rooted Lollipop.
TiP: Settings -> General -> Security -> Security Policy Updates -> Uncheck Automatic Updates, and also Settings -> General -> About Device -> Software Updates -> Uncheck Auto Updates
Downgrade
If you are not happy with the results, or something goes wrong, download a KitKat firmware from Sammobile and flash it in ODIN. Make sure to clean cache and data in recovery.
Click to expand...
Click to collapse
Thank you very much for this!
I wonder if could you please attach the odin files as you did with 4.4.2 thread.
Thanks in advance.

I guess Xposed will not work on our lovely Touchwizzed-Lolipop device?
Please let me know if anyone tried it.

perce_ption said:
I guess Xposed will not work on our lovely Touchwizzed-Lolipop device?
Please let me know if anyone tried it.
Click to expand...
Click to collapse
Don't need to try.... Straight from the developer...
https://github.com/rovo89/XposedTools/issues/3#issuecomment-96386801

Screenshots
Please can u post screenshots for the updated apps or launcher!!
I have sm-p901

Thanks. Follow the instructions exactly and everything works.
PS: Set from Singapore.

works great, thanks
(sm-p905) italy.

Impossible
can't even register at the website to download the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!!website to d
ownload the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!! HELP!

AdjoX said:
can't even register at the website to download the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!!website to d
ownload the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!! HELP!
Click to expand...
Click to collapse
did you try to register from a mobile device? If so try to register from a PC or a laptop and download the files there.

Thanks for the instructions.
Does anyone have a flashable bootloader package? From experience Lollipop is unstable with the old bootloader....at least it was on the N9005.
EDIT: Have successfully upgraded. Initially left the Apps and data but the tablet got stock on "checking connection" during the initial setup. A fectory reset did dix that but also cleared the internal Sd card

Well, I did two simple steps: upgraded up to 5.0.2 and flashed http://forum.xda-developers.com/showpost.php?p=50498424&postcount=235 CF-Root via Odin. Works fine.

sudo.sh said:
Well, I did two simple steps: upgraded up to 5.0.2 and flashed http://forum.xda-developers.com/showpost.php?p=50498424&postcount=235 CF-Root via Odin. Works fine.
Click to expand...
Click to collapse
Pleasee note that flashing CF autoroot trips your knox flag irreversibly, if that is important for you.

najoor said:
Pleasee note that flashing CF autoroot trips your knox flag irreversibly, if that is important for you.
Click to expand...
Click to collapse
at the loading?

sudo.sh said:
at the loading?
Click to expand...
Click to collapse
The knox is knocked at the first reboot after the Odin flash. For you it shouldn't matter because you have already done it. Not a big deal. People have differing opinions about the consequences of tripping knox. I normally try to keep it unchanged on my devices but I don't have a personal opinion on that.

Yes, the Knox is knocked, and it doesn't matter for me.

sudo.sh said:
Yes, the Knox is knocked, and it doesn't matter for me.
Click to expand...
Click to collapse
Will this work for the 905V, Verizon with locked bootloader?
Sent from my SM-P905V using Tapatalk

Works fine, but I had a huge battery consumption until I flashed with Odin the Bootloader, the Kernel and the modem.

aviator1 said:
Works fine, but I had a huge battery consumption until I flashed with Odin the Bootloader, the Kernel and the modem.
Click to expand...
Click to collapse
You don't need to flash bootloader, just make sure you flash the modem when you use flashfire.

I did flash the modem in flashfire, then observed huge battery consumption. After that I reflashed the modem plus flashed the kernel the kernel, but the battery went from 80 to 50% in less than two hours using it not more than 1/2 hour, then I flashed the bootloader and consumption was back to normal (approximately 1% consumption per hour in idle mode). I know that the bootloader shouldn't affect the battery consumption, but that's what happened to me.

I seem to be having an issue with the security. After following instructions, upon boot I get an error "System software not authorized by Verizon Wireless has been found on your phone."
Anyone have any ideas? I'm gonna try getting on a Windows computer and using Odin (I'm on linux)
Edit: I'm back on stock, seems this is blocked by the Verizon bootloader. It's a shame they feel the need to cripple such a good piece of hardware.
Thanks

Root lollipop on AT&T Note 3 without Safestrap!

IT CAN BE DONE​
Here's how I did it. (And don't blame me if you brick the phone, etc., etc....)
PLEASE DO NOT ATTEMPT IF YOU DO NOT UNDERSTAND THESE NOTES! Read them thoroughly!
1. Install stock NC2 (Instructions are all over)
2. Root with towelroot.
3. Install latest SU from the play store and update binary (you know the drill, right?)
4. See Chainfire's site here. http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 Get FlashFire
5. Place the AT&T stock lollipop .tar file on your SD card. It is available in the note 3 forum.
6. Run FlashFire. Once it has done its thing, click on the + sign.
7. Click on flash firmware package and navigate to the stock .tar file.
8. FlashFire will analyze the file and you will see a screen with partitions checked. These are the partitions that FlashFire can write (AND ROOT)
9. Click the download sign at the top on the red bar.
10. Click on the check mark to Create New Archive (FlashFire will create a .tar.md5 file take note of where it is saved and COPY TO YOUR PC BEFORE you run FlashFire! You will need it!
11. Next you will see the screen with ACTIONS on a red bar. Scroll to the bottom and touch FLASH
12. FlashFire will now write the partitions that are checked. When it reboots the phone, IMMEDIATELY hold the volume down, home, and power button to enter download.
13. Go to your PC where you copied the archive (that .tar.md5 fike). Right click on the file and choose rename. Remove the .md5 from the file name or odin will likely give you an error.
14. Open odin and connect your phone. Place the .tar archive FlashFire created in the AP section and flash. It will write the partitions that FlashFire could not.
15. Reboot and enjoy rooted lollipop on your phone.

Hate that I still have to wipe data to get it to boot at all, but a minor gripe I suppose. Just hate having to reinstall my apps and set them back up. Thanks for sharing this, been waiting for something like this for a while!

Yeah but if you're already on rooted nc2, why not just flash the stock rooted lollipop rom?

Doesn't that process require using SafeStrap, where this process does not?

netracerx said:
Doesn't that process require using SafeStrap, where this process does not?
Click to expand...
Click to collapse
You can use flashfire...
Plus why go through all this hassle to reach the same result?

That's absolutely true. but think it is a matter of preference. I had some issues with Safestrap, but were it still supported for lollipop, I would probably still be there. I also had a soft brick when I attempted to do a backup, which supposedly still works by booting from the power screen. SO for those who would prefer a cleaner option, this might suit them better. Flashfire also has the potential to install other custom roms. I am still looking at that option.

swapavi said:
You can use flashfire...
Plus why go through all this hassle to reach the same result?
Click to expand...
Click to collapse
this is the first post i've seen for the N900A that advised using Flashfire, all other posts required using Safestrap (which i personally did not like the idea of using just because it wasn't actually updating the OS on the phone, but essentially tricking the phone into loading a different set of files much like multi-booting). if it were possible to use Flashfire with the rooted lollipop roms, i'm surprised none of the thread OPs updated their posts to reflect that.

FlashFire has only been out since April. It is Chainfire's successor for Mobile Odin. It takes a while for all of the phones to be tested. There are a couple of other users that have tested it. Just search the FlashFire forum for Note 3 and you can read the comments. At least one other has used it on the AT&T variant.

reboot into download mode
I just finished your method successfully. Thank you. I would like to add that there was an option to reboot into download mode after flashing with FlashFire. I didn't have to worry
about immediately holding vol. down . I think the version of FlashFire I used is a little newer. Anyway thanks again!

I will keep trying
Hi all,
I was able to go through all the steps but keep getting stuck on step 14. Odin fails at the very very end and never finishes. I have done the whole process 3 times over.
Questions:
1. When picking the .tar in step 7, I am selecting the largest file of lollipop. I believe it is an AP file about 2.2 Gigabytes. This is the right one to select in step 7??
2. On step 10 when it ask you to Create New Archive, do i check ALL the boxes?? Nothing is checked by default when i press the download sign in step 9.
Other than these two things, everything else seems to work nicely. I did also notice that when Flash Fire runs and writes the system, wipe is set to OFF. I figured it was like that on purpose but just saying.
Thanks in advance,
John :good:

Sorry for the delay. I have moved on to the S6, so been busy with it.
For step 7, choose whichever ROM you wish to use. The one you have should be fine.
With regards to the second question, Flashfire should check the files in step 8 that are needed for the archive. Are you using a stock rom for step 7? If not, it might be able to flash without a separate tar file.

Ok,
Yes it was stock and thanks for the tip i will give this a shot as soon as i can and see how it goes.

So this will work to Root the Note III on Lollipop?

What exactly does Flashfire do in this case? Is it unlocking the bootlader, allowing for flashing a custom rom? Or is it only rooting Lollipop? I was looking at safestrap for running a custom rom on the AT&T Note 3, and someone mentioned in another thread that Flashfire was a better option for doing so, with no need for the multi-boot workaround. Thanks to anyone who can straighten me out on this, and if Flashfire doesn't allow for flashing a custom rom on the AT&T note 3, is there anything else out there that does?
I'm under the impression that the AT&T note 3 has a locked bootloader, which is my point of confusion.

fitzly said:
What exactly does Flashfire do in this case? Is it unlocking the bootlader, allowing for flashing a custom rom? Or is it only rooting Lollipop? I was looking at safestrap for running a custom rom on the AT&T Note 3, and someone mentioned in another thread that Flashfire was a better option for doing so, with no need for the multi-boot workaround. Thanks to anyone who can straighten me out on this, and if Flashfire doesn't allow for flashing a custom rom on the AT&T note 3, is there anything else out there that does?
I'm under the impression that the AT&T note 3 has a locked bootloader, which is my point of confusion.
Click to expand...
Click to collapse
Great Guide and find.
Flashfire has the power to bypass the security that would provent Odin from installing , for example a custom kernel, so be carefull with Flashfire, it installed a custom kernel on my phone and flagged Knox to a 1

Followed the steps in the 1st post...worked flawless! May I add its good to clear cache & delvic cache as well
Sent from my SAMSUNG-SM-N900A using Tapatalk

Excellent. I don't like Safestrap, so this was perfect... I didn't have to wipe my phone, and everything went perfectly the first time. One note, I did have to put my phone in Download Mode (as stated in the OP) after the reboot from Flashfire. Thanks so much to all who worked on this!
Update: The OC2 update happened pretty much immediately after I booted. The OTA update actually managed to complete, and I still have root.

I am currently on 4.3 MI9 version..
i rooted it with chainfire method root de la vega.
Now can i flash NC2 with odin and continue the thing ?

Can someone point me to the stock lollipop tar? I cannot for the life of me find it in any of these forums. Please & thank you.

Chocu1a said:
Can someone point me to the stock lollipop tar? I cannot for the life of me find it in any of these forums. Please & thank you.
Click to expand...
Click to collapse
look here, if you still have issues let me know
http://forum.xda-developers.com/showthread.php?t=2703006

[GUIDE] How to Root Note 5 I EFS Backup I Xposed I Deep sleep Fix I Updated

FOR TEMPORARILY USE THIS METHOD TO ROOT NOTE 5 running on NOUGAT
PS : Running version of SuperSU will not work, once It will be updated use below said method
-------------------------------------------------------------------------------------------------------------- For Marshmallow and lower use below method-------------------------
I have seen many users still have no proper information about rooting SM-N920* (Galaxy Note 5)
Here Steps to root your Note 5. Since there are major changes in policy to root device here I am updating this guide in favor of newbies to make it simple as possible.
Before you proceed to root, you should know some facts like we need to have custom kernel as of now to root device (This is no more compulsory as Systemless root like Supersu 2.60+ can root device on stock kernel. Read below.). Also we have bootloader protection to flash anything but that can be unlock (read below). Also to note that rooting your device warranty voids (permanently) apart from warranty if you want to unroot device after rooting it once, you may have deep sleep bug. Read Deep Sleep issue on stock non rooted ROM at end of this post.
Need to know before rooting Note 5.
Here I am making two parts for two different method to root your Note5. Before proceeding you have to device which way you want to root as mixing both method may mess up your system and ultimately you may need to reflash stock ROM.
Before starting step just to explain what is difference between both the methods of root.
Method 1: Systemless root.
Systemless root is recently provided by @Chainfire for our device.
Major advantage is you can simply flash same zip (superSu 2.60 and up) to any Note5 variant without any dependencies on kernel for your device.
As Systemless root is still beta and may be we will get stable version very soon but most of root stuff working fine as it should with beta version too. Edit : It seems Systemless root is almost stable now.
Systemless root can be achieved by two methods
1A. - Flashing SuperSU from custom recovery.This is two step procedure. First flash custom recovery and second Flash SuperSu zip Advantage of this method over 1B (below) is you will have custom recovery and helpful to make nandroid backup OR flashing other recoveries.
1B - Flashing with Odin - Flashing root package with Odin. Single step root. Easiest method.
Method 2 : Using prerooted kernel. With prerooted kernel you can root your device in single step even without having custom recovery. This is true in case of your kernel is having prerooted script and available in tar version. I will provide example below in guide which kernel have this.
There is no any issue using this method but you must have to find correct kernel for your device.
Click to expand...
Click to collapse
How to root Note 5
Method 1 (systemless root) Again there are two method for Systemless root and you can go with either of it.
Method 1A - Systemless root by flashing SuperSU zip
You will require custom recovery to use this method. Here are steps for how to install custom recovery as well how to root.
1.Unlock Flashing
Go to settings-about device-Software info - You will see "build number" - Tap repeatedly on build number to unlock development option
Now you will see Development option in setting (just above about device)
Open Development option - OEM Unlock - Enable it.
2.get custom Recovery.
Download TWRP by @bigbiff according your variant. Here select tar version of file NOT zip
OR
Philz CWM. Philz recovery is ported for Note 5 by @arter97 and you can download from his web page. - Here look to latest build and select your device model. for example your variant is N920I you have to open n920ci (this indicate n920c and n920i) and download Philz recovery with file name ending tar.md5 (not zip)
3A.Flash custom recovery.
Use Odin V3_10.7 to flash downloaded recovery
Switch off device
Reboot to download mode (Vol down+power+home)
Select downloaded above said custom recovery with AP tab of Odin and flash.
when TWRP prompts asking to "keep read only" or to "allow modifications", select the option to "Keep Read-Only." (Phil's CWM doesn't give the option to keep it read-only.) As well, _if_ TWRP/Philz offers to install root - DO NOT LET IT (as it's not compatible with systemless root.)
Reboot to recovery and now you should have custom recovery.
In case still you have stock recovery then follow this
Again reboot to download mode
Select recovery file with AP tab of Odin
Now uncheck Auto reboot option
Flash selected file
Once flashing complete, disconnect device and long press Vol down+Power
Once screen turns off, immediately press vol up+power+home to reboot to recovery manually.
3B : This step is only for those who want to use Android Pay otherwise you can jump to Step 4 directly.
A completely stock system with the systemless root installed will NOT, by default, work with Android Pay. To make it work with android pay, the following command should be run from a shell prompt on the device (while the device is in TWRP, but before installing superSU.) This is easier to do via 'adb shell', but could, I guess, be done from within TWRP itself (advanced->terminal command)
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
4.Root with Systemless root.
Once you have custom recovery on your device then simply download Systemless superSu zip and flash from recovery that's it.
Here is link for Systemless root Big Thanks to @Chainfire
You have to download latest version of it.
Click to expand...
Click to collapse
Once it is done, you will see SuperSU app on your drawer and your device is rooted now.
Method 1B - Systemless root by Odin (CF Auto Root)
Click to expand...
Click to collapse
This is easiest way to root Note 5
Download required files from CF Auto root download page. Simple search your device ID e.g. N920I. If you see your device model is listed then you can see download option beside of your device ID in table.
Download according your device ID and extract it. You will get Odin and one *.tar.md file.
Before starting unlock bootloader
1.Go to settings-about device-Software info - You will see "build number" - Tap repeatedly on build number to unlock development option
Now you will see Development option in setting (just above about device)
Open Development option - OEM Unlock - Enable it.
2.Reboot device to download mode (switch off device then Vol down+power+home)
3.Open Odin on PC
4.Select that *tar.md5 file for AP (PDA) tab of odin
5.Connect device to PC and wait till color change for com port (successfully connected device) and select 'Start' to flash
Once flash finish, disconnect device and reboot. You will have rooted device now.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Method 2: Flashing Prerooted Custom kernel.
Basically you can install any prerooted kernel with odin or with custom recovery but here i will show a example which can be done in single step
1.Download prerooted odin flashable (in .tar.md5 format)
Example : Get Skyhigh kernel by @UpInTheAir
here is Original thread by him
Look to post #2 of that thread and under Download section you will find many version of kernel. You have to download one which is for your variant as well available as odin flashable.
As of today available versions are
[Odin3 v3.10.6] SM-N920-C / CD / G / I [ v3.4 ] - which same for following devices like N920C N920G N920I N920CD
[Odin3 v3.10.6] SM-N9200 [ v3.4 ] - For N9200
[Odin3 v3.10.6] SM-N9208_SEA [ v3.4 ] - For N9208
2.Flash Downloaded file with Odin
Use Odin V3_10.7 to flash downloaded kernel
Switch off device
Reboot to download mode (Vol down+power+home)
Select downloaded kernel file with AP tab of Odin and flash.
Device will auto reboot and you can see kernel info in Setting-Device info. Also on successfull flashing you will see SuperSU app on your drawer.
If you don't find any version available for your variant, you can simply make request to OP on kernel thread OR Use Systemless root meanwhile.
PS : As said above you can use any custom kernel by any developer but keep in mind that if kernel is not Odin flashable then you need to flash custom recovery first and if not prerooted then flash Supersu recommended by kernel developer. I have make example is based on just easiest way to flash i found.
Click to expand...
Click to collapse
IMPORTANT
Here is end of how to root note 5. Read below some miscellaneous discussion.
- There may be issue with DRM protected videos (like Netflix). You can fix with this.
- Now DON'T FORGET TO MAKE EFS (IMEI) BACKUP
- Xposed on Note 5
Deep sleep issue. - THIS IS FIXED AFTER SuperSu 2.67
If your device doesn't go to deep sleep after root. commonly reported after rooting with stock kernel (systemless root)
How to know deep sleep issue : Main symptom of deep sleep bug is fast draining battery. You can confirm if your device has this issue or not by using batterbattery stat or any similar app.
After installing BBS keep device idle for sometime and see other profile and check your device record deep sleep? If you don't have deep sleep recorded then you need fix. Here is screenshot of deepsleep record.
Deep Sleep Issue on stock non rooted device:
This is classically happens when you root device/flash custom kernel/recovery/ROM and later revert to stock ROM. Now even you have non rooted device with pure stock ROM, your device won't enter to deep sleep. Basically this is not a bug but poor policy and samsung don't care to address this issue as if you use device as per samsung suggests (without tripping knox) there will be no issue. Again solution is root your device and apply deep sleep fix / any kernel/ROM which have bio;t in deep sleep fix.
How to Fix :
You can try this to fix Deep sleep issue.
Click to expand...
Click to collapse
Big Thanks and credit goes to @Chainfire
Thanks and credit to @garyd9 for all the helps to users and providing lots good information.
.

Reserved

Reserved 3

Rsereved 4

Last
I will add some more important information later

Last
I will add some more important information later

Mod Edit
Thread stuck
:good:
malybru
Forum Moderator

Perfect guide
Sent from my SM-N920C using XDA Free mobile app

Great info.
Maybe add a warning that it's not for 920A (ATT) or 920V (Verizon).

I've read that currently there is reboot issues with that kernels. Which one from the 3 versions is the most stable?
Sent from my SM-N920C using XDA Free mobile app

juliano76 said:
I've read that currently there is reboot issues with that kernels. Which one from the 3 versions is the most stable?
Sent from my SM-N920C using XDA Free mobile app
Click to expand...
Click to collapse
Let's keep this thread on the track only and don't make kernel discussing thread. All developers are working hard and it's insulting to say this one is better. For A - may be kernel X is better and for B - may be kernel Y is better, moreover it's subjective and you have to find yourself which one is best for you. Purpose of guide is how to root and I am pretty sure using any of mention kernel will do job. If you are not happy with your kernel you can change anytime OR may you can seek assistance from kernel thread.
Hope this make clear.

What about this root method? It seems so easy!
https://www.androidroot.us.com/how-to-root-samsung-note-5/
Sent from my SM-N920C using XDA Free mobile app

Dr. Ketan what is the version of Note 5 we will be getting from tomorrow in India ? Is it 920i or 920c ? whats the difference ?

N920G for India nothing great just the difference of the awesome naming trend of Samsung

Thanks you DR. KETAN!
This is really a huge help and put my mind at ease! Again, many THANKS.
Quick question... Once I root and install custom recovery can I install any note 5 rom? I have the n920i. Reason I ask is I would like to try a few n920T roms and was wondering if there would be any issues or negatives?

how to root indian SM-N920G .?
none of the kernels seem to support ..
---------- Post added at 03:05 PM ---------- Previous post was at 03:05 PM ----------
how to root indian SM-N920G .?
none of the kernels seem to support ..

stu5797 said:
Thanks you DR. KETAN!
This is really a huge help and put my mind at ease! Again, many THANKS.
Quick question... Once I root and install custom recovery can I install any note 5 rom? I have the n920i. Reason I ask is I would like to try a few n920T roms and was wondering if there would be any issues or negatives?
Click to expand...
Click to collapse
Not all but some variant can share same ROM like n920i and n920c
For tmobile, they need to flash call audio fix to use international rom so same way if you flash n920t rom may you get some bug. Yet I haven't read if anyone reported his/her experience regarding this, you can try yourself.
daviefl86 said:
how to root indian SM-N920G .?
none of the kernels seem to support ..
---------- Post added at 03:05 PM ---------- Previous post was at 03:05 PM ----------
how to root indian SM-N920G .?
none of the kernels seem to support ..
Click to expand...
Click to collapse
Either you can try n920c/i or can make request to kernel developer to add support to your device
Sent from my SM-N920I using xda premium

I currently have the SM-N9208 (Duos) version of the Note5. Would I be able to use this method to root it too?

Hi Dr. Ketan...
Just want to know what are the future possiblities of Rom Development for model no. SM-N920G which is being distributed in India rite now... are the roms/kernels going to be model specific or universal for models other than Sprint/verizon etc...!!
With so many models coming up , its going to be quite confusing for both developers and users i guess.... !!!!

There are possibilities there n920i/c model rom kernel may work on n910g. If not then you have to request developer for kernel. I may consider to add support for rom if there is no support for n910g and sufficient users available.
Sent from my SM-N920I using xda premium

[GUIDE] {no root required} STOCK TW WITH MODS SUPER SMOOTH S7 FLAT G930F

After flashing a number of different custom roms, I always seem to find myself back to stock.
Here is my set-up which is safe, stable and fast, all without root, however you WILL trip KNOX by installing a custom recovery.
All the files I have supplied are not my work, please thank the developers.
1: Make sure you are on the latest MM stock ROM.
2. Flash TWRP via ODIN - (if you don't know how to do that maybe this is not for you)
3. Factory reset via TWRP (use the 'format data' option - this will allow you to transfer files to phone via TWRP - reboot to recovery)
4. Transfer and flash the following:
a. Debloat Zip (not my work just passing information) https://mega.nz/#!4soHlQzb!m0l216lifA1iQafiPfJWwL8LtGcB0C1GEsKTxXGuyQQ
b. Ad-block provided by MOAAB
https://mega.nz/#!toAUXbAT!VoeNDxSAEDOiNYJwKmGSMW2x0lio-zIMfKchuzQfSDo
c. Dolby Sound Mod
https://mega.nz/#!I4g1DTJC!Q1QeoGkPKEJwLka4Odpq7hU9AKfPZ9FkB7B5nHkid5E
d. No-Verity - this is required or you will have bootloop.
https://mega.nz/#!4oxlXaIR!qdwGgx_MPVgFM7rPHI_7J3rsVmsTw_AmVwRQTOMhgB8
(optional)
Pixel Launcher: https://mega.nz/#!Y1oUUDpK!YuDw62kpyAiiZLqqFCU7YwppMA-q9KrQMKzlrW6wZSc
Reboot phone and you will have a debloated, fast, stable ad-free sound upgrade experience and you don't have to even root the phone.
Geekbench 4 Results:
https://mega.nz/#!p4gx3RLb!hG2we4C2N-4Mf4iMSk0sdaUF0mPVPqqwhKCG7lDVzsU https://mega.nz/#!d5RDWBQY!d7idJtMMSIixQz3zCXXwDlc84-X_w7v_oXGibWH8EkA https://mega.nz/#!pkQgFK4B!28nbZ_QRjhkMoOg_muOOXwlAV63N0p1FY3WQ_3Gm8wU
Any questions, feel free to ask!

Yes it does... saw it reading second time... (knox) my bad

vuolia said:
Yes it does... saw it reading second time... (knox) my bad
Click to expand...
Click to collapse
Yes, as stated in the post.

vuolia said:
Yes it does... saw it reading second time... (knox) my bad
Click to expand...
Click to collapse
Ha ha no problem!

After debloat not work ok google when screen off
Taptalked