Develop Bugs

Having trouble rooting my device.........

For some strange reason (yes I know its very simple and obvious), I can't root my Nexus 20013. Its running Android 5.1.1, Build number LMY48G.
I followed the instructions here http://www.wugfresh.com/nrt/ to the letter, was able to unlock the boot loader, however when I attempt to root it, it installs TWRP, but then for whatever reason it never actually roots the device.
I've been through the troubleshooting section of the program to un-install the ADB and USB drivers, re-installed them etc, but I can't get it rooted. It goes to TWRP, and when I try to install SUPERSU (after the device has booted back up), it just stops and says the device is not rooted.
When I try to flash a specific kernel (the Timur kernel as this tablet will be permanently installed in my car), using TWRP, it can't find the ZIP file even though I copied the file to the root folder.
Any suggestions on what to do next?

Based on some quick reading Android 5.1.1 (LMY48G) is an updated version of Android 5.1.1 (LMY47V)
I have the former and can't root my device with the Nexus Root Toolkit v2.0.5. Is there any other way to root my device? I've searched online and used a manual method using the command line with the ADB drivers, but still can't root it. What are my options here?

Questions regarding rooting.

I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 

Tranquility. said:
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Click to expand...
Click to collapse
I'm not a dev, but I have some experience rooting the N7 (2012 and 2013).
1) Well, it looks like 6.0 isn't coming to the N7 2012, so there is a good chance support for major versions will be dropped soon (within the next year?). They might continue to release patches and security fixes for 6.x a year or two after that, like they appear to be doing with the N7 2012, but this is all speculation. There are probably number crunchers looking at the sales figures and survey results to gauge interest, and there were some rumors recently of a new N7 possibly in the works. Those will both factor into whether support will continue.
2) You will get a notification, but everything I've seen has indicated that the install will fail (won't brick the tablet, but will just show an error and reboot to its previous state). What I think most people do, including me, is just flash the stock image in 'no wipe' mode and re-root after the update. You can also sideload the OTA update, depending on rooting method (I think, but haven't done this myself). Lastly, if you don't mind reconfiguring all your apps or if you have a good backup scheme, you can just do a fresh install then root. I have never had trouble flashing stock in no-wipe and re-rooting, but I've heard some people have had problems. (It's worth noting that if your bootloader hasn't been unlocked, you will have to wipe the device anyways. The unlocking survives flashing, so it's a 'one and done' thing. You only really need to lock it again if you're sending it in for warranty service.)
3) Wug's toolkit is currently borked for most people (version 2.0.6), so avoid it until the thread in the N7 development subforum has some success stories. Also, rooting in Marshmallow is possible, but seek out instructions specifically for M and use the latest versions of any linked utilities (like SuperSU and TWRP). I used Wug's toolkit 90% of the time for updating and rooting, and when it works, it's a breeze. It might be worth waiting for it to be updated to address the current issues. You can use the previous version to do some basic things and as a launchpad for manual tweaking, but the main, one click and done options will not work - I tried and was greeted with a bootloop due to an out of date SuperSU. But, in version 2.0.5 you can unlock the bootloader and flash the latest stock (haven't tried the U or V versions, but MRA58K worked fine). From there you have to root mostly manually, but there are shortcuts for some of the steps in the Advanced Utilities section.
4) It's always possible to brick a device, but it's very rare. There are 2 kinds of 'bricks'. 'Hard' brick is what most people worry about - something happens that prevents access to even the lowest level of the device. It's as if there was a hardware failure. 'Soft' bricking is what less tech literate people equate to hard bricking because to them the device is useless. In reality, it's a software issue that prevents some early stage of the boot up process. It is almost always recoverable with enough time and research. In basic computer terms, hard bricking is failing to post and soft bricking is failure of the OS to load (basically, though there are nuances). With root, you have access to everything and you're trusting whatever you install that takes advantage of that power to use it wisely. An ad blocker shouldn't need to adjust the CPU voltages. This is rare if you don't intend to overclock or mess with low level hardware tweaks. It is much more likely, but still pretty rare, to soft brick the device, which means you just have to reflash the system image. Worst case is you have to wipe the device and start over, or spend a few hours researching exactly what caused it.
Hope that helps. I'm not an obsessive ROM flasher and my experience has been only with Nexus devices, but these are my impressions.

Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.

Tranquility. said:
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Click to expand...
Click to collapse
Android M is the last official update for N7 2013, the first gen N7 is done with updates. Once rooted you will not get any OTA updates anyway.
Flashing usually takes about 3-4 minutes. Booting up can take up to 10-15 min.
Just don't root on M until a stable method has been discovered.

Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.

You can check the marshmallow and the beta thread for updates. http://forum.xda-developers.com/apps/supersu

Tranquility. said:
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
Click to expand...
Click to collapse
You can root 6.0 pretty easy if you have fastboot installed. I've done it and can confirm it works. You just need to download the ElementalX-N7 kernel and SuperSU to your device then flash TWRP in fastboot then flash the kernel and SuperSU in TWRP. There are threads on here I believe with instructions to help you. If you need any help you can message me.

The beta SuperSU and elementalx method worked great for me and seems totally stable. I'd recommend learning fastboot/adb as mentioned. That has saved me a few times from the dumb things I've done messing around with root access.
Sent from my Nexus 7 using XDA Free mobile app

Rooting
As I mentioned in a previous post rooting using TWRP, SU I don't think fully roots
the device. When I loaded Multi-Rom, it installed in the usual fashion but only boots to the TWRP recovery utility.
In the past, one could globally root the device but the problem appears new.
Kurt

Fire TV 1st gen with Software Version 51.1.4.0 - what to do? (Update or not?)

Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
This thing was never actually used because I didnt want to risk it beeing updated and loosing the ability to root and/or bootloader unlock... (this Software is the one with which it was shipped..)
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!

zroice said:
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
Click to expand...
Click to collapse
I'm going to release recovery for both locked and unlocked Fire TV 1. The big difference being if you brick an unlocked unit, you can boot straight to recovery and fix it. If you brick a locked one, you're pretty much hosed.

rbox said:
I'm going to release recovery for both locked and unlocked Fire TV 1. The big difference being if you brick an unlocked unit, you can boot straight to recovery and fix it. If you brick a locked one, you're pretty much hosed.
Click to expand...
Click to collapse
thx for the reply.
Can unlocked bootloader be kept unlocked even with update to 5.0.5? Or does the new version require the new not unlockable bootloader?
Only way to unlock would be to hardware root the one I have or is there any other way? (with the 51.1.4.0 software)

zroice said:
thx for the reply.
Can unlocked bootloader be kept unlocked even with update to 5.0.5? Or does the new version require the new not unlockable bootloader?
Only way to unlock would be to hardware root the one I have or is there any other way? (with the 51.1.4.0 software)
Click to expand...
Click to collapse
Yes. If it's unlocked it will stay unlocked.
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.

rbox said:
Yes. If it's unlocked it will stay unlocked.
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
Click to expand...
Click to collapse
but amazon is not giving those out isnt it? =)

zroice said:
but amazon is not giving those out isnt it? =)
Click to expand...
Click to collapse
The tablet that uses that for their unlock has a program to generate the unlock codes. It's similar to my unlock, but it runs on your computer to generate the code versus my unlock that runs on the device.

but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)

zroice said:
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
Click to expand...
Click to collapse
Yes, mine requires root.

@rbox, has anything been learned about a custom recovery for the fire sticks now that we have root access?

zroice said:
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
Click to expand...
Click to collapse
No. Not a hardware root. Just wait on the @rbox prerooted software rom for the Fire TV/Stick. And shortly after that AFTVnews will provide an extensive how to root guide. Just be patient and you will eventually have a rooted/unlocked Fire TV/Stick.

BreakingDroid said:
@rbox, has anything been learned about a custom recovery for the fire sticks now that we have root access?
Click to expand...
Click to collapse
I'm trying to get recovery for FireTV1 working, before I work on the stick. The problem is if I brick the stick, it's game over. I'm trying to find all the ways that I can brick it while working on the FireTV1, so I don't do it with the stick.

mjbxx said:
No. Not a hardware root. Just wait on the @rbox prerooted software rom for the Fire TV/Stick. And shortly after that AFTVnews will provide an extensive how to root guide. Just be patient and you will eventually have a rooted/unlocked Fire TV/Stick.
Click to expand...
Click to collapse
hmmm but didnt I read that once you update the bootloader unlock is no longer possible?
I got the FireTV with old software still which accoding to atfnews is not rootable but bootloader unlockable.
I read that once you update that the eFuse thing will become active and prevent unlock attempts.
All in all I just need to know if I should update the 1st Gen from the current " 51.1.4.0" build to the latest one to get root, disable OTA etc and still be able to unlock bootloader and boot directly to a recovery or if it would needed to be hardware rooted in order to do that. (to prevent the bootloader update.. which activates the efuse)

zroice said:
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
This thing was never actually used because I didnt want to risk it beeing updated and loosing the ability to root and/or bootloader unlock... (this Software is the one with which it was shipped..)
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
Click to expand...
Click to collapse
rbox said:
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
Click to expand...
Click to collapse
rbox is right. You can unlock the bootloader of a 1st-gen Fire TV using only an A-to-A usb cable. Although I'm not sure if it works on 51.1.4.0. I think it requires 51.1.0.2 or older.
I was going to write a guide, but the python script to generate the unlock code/file has been taken down, and it was really only useful for those who bricked with a locked bootloader, so I didn't try to find the script. Pretty sure the script was called cublock.py from here.
Assuming you can get ahold of the script, and it works on your software version, you would connect an A-to-A usb cable and reboot into fastboot by connecting via ADB and running
Code:
adb reboot fastboot
then run
Code:
fastboot devices
to ensure you're in fastboot and connected, then run
Code:
fastboot oem emmc-info
to get a code that you need for the python script. The code is in the form
Code:
(bootloader) 0x12345678
and you use the python script to generate the unlock code like this
Code:
./cublock.py 56 12345678
That will generate an unlock file which you then use as follows:
Code:
fastboot flash unlock /path/to/file.unlock
After that, you can use fastboot to flash custom recovery if you'd like. Instructions are at the bottom of this guide under the "Repair Recovery with Fastboot Mode" section. I've attached a screenshot of the process from my notes for the unwritten guide, back when I tried it.

ill try that - thanks very much

what driver to use for fastboot mode?

zroice said:
what driver to use for fastboot mode?
Click to expand...
Click to collapse
I'm not sure which Windows drivers to use. My Mac didn't need any.

This should help concerning Windows ADB/Fastboot drivers:
http://forum.xda-developers.com/showthread.php?t=2317790

http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
Tools.zip package from this post includes the cublock.py file

ARGH that sob Fire TV.. Cannot root the damn thing in current stage with Kingroot and cant get my PC(s) to connect to fastboot.
My flashing PC which has all sorts of drivers installed only detects it as ADB device - "fastboot devices" doesnt work. And my Laptop does recognize it as "Fire TV" with no drivers installed in fastboot mode.
I need help to get that damn fastboot goin please. On the PC I forced driver install of some "universal" fastboot drivers but it still wont show up in fastboot devices (to get the info needed for the python script..). No idea why the pc thinks its an adb device when connected in fastboot mode.. (adb doesnt work in that stage either...)
Downgrading & Bootloader unlocking after updating to 5.0.5 probably wont work, right? Because the bootloader cannot be downgraded I guess..

zroice said:
ARGH that sob Fire TV.. Cannot root the damn thing in current stage with Kingroot and cant get my PC(s) to connect to fastboot.
My flashing PC which has all sorts of drivers installed only detects it as ADB device - "fastboot devices" doesnt work. And my Laptop does recognize it as "Fire TV" with no drivers installed in fastboot mode.
I need help to get that damn fastboot goin please. On the PC I forced driver install of some "universal" fastboot drivers but it still wont show up in fastboot devices (to get the info needed for the python script..). No idea why the pc thinks its an adb device when connected in fastboot mode.. (adb doesnt work in that stage either...)
Downgrading & Bootloader unlocking after updating to 5.0.5 probably wont work, right? Because the bootloader cannot be downgraded I guess..
Click to expand...
Click to collapse
P.S: I could try to boot linux from USB if that helps - but that probably also needs some sort of drivers doesnt it?

Zenfone 2 issues in 2017

Hello,
I bought a Zenfone 2 in 2015 and have loved it ever since. Back then it was simple to root, unlock the bootloader, and neither required the other.
To root, just enable ADB and run this.
To unlock the bootloader, just download this from azus.
Now, buying a phone fresh, to remove all the bloat is becoming a challenge.
To root, you need an unlock the bootloader. To unlock the bootloader, you need to downgrade to an early 5.0 image.
So I downgrade, unlock the bootloader, and root. To get back on 6, I need to upgrade to a newer version of 5.0, so I do. Root gone, bootloader still unlocked, splash screen is normal. Fine, I root again.
Finally, after upgrading to 6.0 (using adb sideload) both root and the bootloader unlock are gone. So I have to start again, and either live with unbloated 5.0, or unrooted, bloated 6.0.
As far as I can tell the only way around this is downgrade to 5.0, unlock my bootloader, then flash a pre rooted unsigned system.img.
Sadly I cannot find a recent pre rooted unsigned system.img, and have no way of knowing how to create one. If someone could help me make one I would greatly appreciate it.
Am I doing this all wrong? Is there a better way?
Because now I have a phone that I'm either stuck with a buggy 5.0 or a bloated 6.0; and the original, two year old zenfone is stuck in the bootloader because I was experimenting with various tools from around here.
I am well aware that I could just nuke the old phone with xFSTK to get out, but I refuse to. I have no such problems nuking the new one though.
Any and all help would be greatly appreciated, the Zenfone 2 is still a great device and is fantastic value for money, so if I can sort out all this I will happily make a full, comprehensive guide with my new knowledge to replace the errors in the outdated one here, and to add far more comprehensive knowledge about unbricking:
https://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Thank you all for your time

assuming you are already on MM version ww4.21.10.233... if no update to this version and download the following tool..
https://drive.google.com/open?id=0B72QQTXqZSRwTDNtU1N6OEdMdmM
reboot phone in fastboot mode. now extract the downloaded zip and double click unlock.bat phone will reboot 2 times. then you will get white screen and stuck there. when you see white screen. simply turn off mobile. reboot in fastboot mode with volume plus and power button. and run restore.bat from extracted zip.
now download twrp from official twrp website version 3.1.1.0. and flash it in fastboot mode. hope you know how to ( place twrp image in adb fastboot tool and open command windows in same folder reboot phone in fastboot mode and connect to pc. run the following command
fastboot flash recovery twrp-3.1.1-0-Z00A.img
then use volume button to find recovery mode and click power button to boot into twrp.
now download super su from following link use this version only as i have just tested it few minutes ago.
https://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
place superuser zip on internal memory or sd card and click install in twrp and install super userzip. alternatively you can sideload supersu zip as well. then wipe cache and dalvik cache and reboot system. note phone may bootloop or restart 2,3 times. don't interrupt it. it will boot itself into system.
this is 100 percent safe way.
---------- Post added at 11:12 PM ---------- Previous post was at 11:05 PM ----------
x86fanboy said:
Hello,
I bought a Zenfone 2 in 2015 and have loved it ever since. Back then it was simple to root, unlock the bootloader, and neither required the other.
To root, just enable ADB and run this.
To unlock the bootloader, just download this from azus.
Now, buying a phone fresh, to remove all the bloat is becoming a challenge.
To root, you need an unlock the bootloader. To unlock the bootloader, you need to downgrade to an early 5.0 image.
So I downgrade, unlock the bootloader, and root. To get back on 6, I need to upgrade to a newer version of 5.0, so I do. Root gone, bootloader still unlocked, splash screen is normal. Fine, I root again.
Finally, after upgrading to 6.0 (using adb sideload) both root and the bootloader unlock are gone. So I have to start again, and either live with unbloated 5.0, or unrooted, bloated 6.0.
As far as I can tell the only way around this is downgrade to 5.0, unlock my bootloader, then flash a pre rooted unsigned system.img.
Sadly I cannot find a recent pre rooted unsigned system.img, and have no way of knowing how to create one. If someone could help me make one I would greatly appreciate it.
Am I doing this all wrong? Is there a better way?
Because now I have a phone that I'm either stuck with a buggy 5.0 or a bloated 6.0; and the original, two year old zenfone is stuck in the bootloader because I was experimenting with various tools from around here.
I am well aware that I could just nuke the old phone with xFSTK to get out, but I refuse to. I have no such problems nuking the new one though.
Any and all help would be greatly appreciated, the Zenfone 2 is still a great device and is fantastic value for money, so if I can sort out all this I will happily make a full, comprehensive guide with my new knowledge to replace the errors in the outdated one here, and to add far more comprehensive knowledge about unbricking:
https://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Thank you all for your time
Click to expand...
Click to collapse
do you state that you have an old device which you are unable to revive with xFSTK. what error do you get? put device on charge for 5,6 hours with original charger and use the following guide. use correct gp flag value use 4 zeros not 5
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

wow, no need to do all this... just use one of the available tool, my prefered one is this one:
https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293
very easy to use, to unlock, it will temporaly downgrade your boot to 5.0, unlock bootloader, then reflash boot 6.0.
Once there, just flash TWRP recovery and Magisk, from the tools.
I also had a locked ZF2 in MM 6.0 and using this tool it took less than 5 minutes to have an unlocked rooted phone, and I haven't wiped or lost anything.

Help! Bootloop Nightmare!

I was trying to root/custom rom/etc in a hurry and I was interrupted a million times, so I screwed up. SM-N910v. I started out on kitkat, 4.4.1. I tried this guide: https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
I odin N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5. That upgraded me lollipop 5.5.1. I then follow a guide similiar to this: https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Its not the exact one, but there is several guides that are the same. I temporary rooted with kingoroot, installed TWRP. One of the guides said not to let it boot normally, so I freaked out and made sure I didn't do that. I booted back into twrp. Using this guide: https://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I can't remember or find the exact guide I was on... But I flashed these files in the following order:
BETA-SuperSU-v2.71-20160331103524.zip
Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip (this was really dumb)
cm-13.0-20160919-UNOFFICIAL-trltevzw.zip
I tried to boot, I left it on for atleast 30 mins, and the clockworkmod logo kept animating abnormally fast.
I then installed N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 again (... doh ...).
Now it bootloops.... so I said.. 'ok, maybe I just need my TWRP recovery back'. Tried to install TWRP and fail....
I can boot into safe mode fine, but not normal mode. The problem with safe mode is you can't install apps.
I've tried factory reset, wipe cache, dalvik, etc etc. Nothing. I've also tried a different firmware I believe as well.. I am lost...
Current Android Info:
5.1.1
security patch level: 2015-12-01
baseband version: N910VVRU2CPD1
Kernel version: 3.10.40 Jan 20 2016
Build Number: LMY47X.N910VVRU2BPA1
The information above indicates that I am still in this version: N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Ok so.. I just odin this file N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5
Same story, I can boot into normal mode, but not safe mode.
I check my info:
5.1.1
security patch level: 2015-12-01
baseband version: N910VVRU2BPA1
Kernel version: 3.10.40 Jan 20 2016
Build Number: LMY47X.N910VVRU2BPA1
Factory reseting now... and seeing if that fixes my problem... nope... same bootloop problem...
my thinking is... if I undo "samsung_unlock_n4-fix" and that would fix my bootloop. If thats true..... I guess my biggest question is: if the boot loader is unlocked, then why can't I flash TWRP like I was able to the first time??
I appologize, I will be unaviable for the next 5 or 6 days..... any help would be much appreciated!

I followed Max Lee's guide on youtube for rooting/unlocking the bootloader I recommend downloading the files he has linked, just ensure that your phone is the SM-N910V the hardest part or more time consuming part is getting kingo root to get you that temporary root needed to unlock your bootloader/root phone. Kingo root is very unstable and your phone will freeze/restart many times, You definitely need a spare sd card, at least a 2GB from my experience and patience, set aside a few hours because your follow through is crucial. If all goes well you will be able to install TWRP. I hope this helps. Tip, if you decide to follow his method, the file titled 'samsung_unlock_n4-2' you need to rename it to say 'samsung_unlock_n4-fix' good luck!

UmbrellaTakedown said:
I followed Max Lee's guide on youtube for rooting/unlocking the bootloader I recommend downloading the files he has linked, just ensure that your phone is the SM-N910V the hardest part or more time consuming part is getting kingo root to get you that temporary root needed to unlock your bootloader/root phone. Kingo root is very unstable and your phone will freeze/restart many times, You definitely need a spare sd card, at least a 2GB from my experience and patience, set aside a few hours because your follow through is crucial. If all goes well you will be able to install TWRP. I hope this helps. Tip, if you decide to follow his method, the file titled 'samsung_unlock_n4-2' you need to rename it to say 'samsung_unlock_n4-fix' good luck!
Click to expand...
Click to collapse
I appreciate your post. However I don't think you quite understand whats going on.
https://galaxynote4root.com/cwmtwrp-recovery/
His site specifically states: "Verizon SM-N910V unless you have a developer’s edition phone as retail version come with locked bootloaders meaning you cannot install regular CWM or TWRP!!!"
It also shows that comment in the video. I definitely DO NOT have the developers edition.
In summary: I flashed the firmware that has the bootloader unlock vulnerability->Installed twrp->Installed CWM->Installed Firmware with bootloader vulnerability, which replaced everything I did. Now it seems like the bootloader is re-locked, and I can't boot into normal mode, which means I can't run kingo again. I can't flash TWRP, the only things I can do are: adb sideload, odin, boot any 5.1.1 in safe mode.

TouchOdeath said:
I appreciate your post. However I don't think you quite understand whats going on.
https://galaxynote4root.com/cwmtwrp-recovery/
His site specifically states: "Verizon SM-N910V unless you have a developer’s edition phone as retail version come with locked bootloaders meaning you cannot install regular CWM or TWRP!!!"
It also shows that comment in the video. I definitely DO NOT have the developers edition.
In summary: I flashed the firmware that has the bootloader unlock vulnerability->Installed twrp->Installed CWM->Installed Firmware with bootloader vulnerability, which replaced everything I did. Now it seems like the bootloader is re-locked, and I can't boot into normal mode, which means I can't run kingo again. I can't flash TWRP, the only things I can do are: adb sideload, odin, boot any 5.1.1 in safe mode.
Click to expand...
Click to collapse
I did not have a developers edition either, I have retail, this method makes your phone into the developer edition. This method is designed for verizons note 4. So what i'm saying is, I followed his method using a retail note 4 branded verizon and this exploit makes it into a developers edition so you may install twrp and roms. You are able to odin flash stock firmware for marshmallow and then downgrade to 5.1 to run max's method.

Ok so.. I managed to get everything working... so I'm happy. Thank you UmbrellaTakedown for invoking thought and thank you for replying, your the only person who replied, so much appreciated!
1. Boot into safe mode
2. Install app by: adb install c:\kingoroot.apk
3. At this point, its installed but the launcher needs to be refreshed for the icon to show up. I don't know how to refresh the launcher without a reboot.. so...
4. Find the kingoroot package name: adb shell 'pm list packages -f'
5. In my case it said: package:/data/app/com.kingo.root-1/base.apk=com.kingo.root So your answer is: com.kingo.root
6. Now in order to launch kingo, you need to find the activity of the package: adb shell pm dump PACKAGE_NAME | grep -A 1 MAIN
7. Start the activity: adb shell am start -n com.kingo.root/com.kingoapp.root.MainActivity
From here I was able to temp root through kingo, and run samsung_unlock_n4-fix. This time I had to only run samsung_unlock_n4-fix once. After that, TWRP installed no problem (where before it would not).
Update:
I am now officially on Jasmine ROM marshmallow. I had to copy the jasmine folder to /data/media/0/TWRP/BACKUPS/xxxx/jasmine
xxxx= you get that from adb devices
Then simply do a restore, after restore, restore the partial firmware file (it has to be done in that order or else it won't work)

TouchOdeath said:
Ok so.. I managed to get everything working... so I'm happy. Thank you UmbrellaTakedown for invoking thought and thank you for replying, your the only person who replied, so much appreciated!
1. Boot into safe mode
2. Install app by: adb install c:\kingoroot.apk
3. At this point, its installed but the launcher needs to be refreshed for the icon to show up. I don't know how to refresh the launcher without a reboot.. so...
4. Find the kingoroot package name: adb shell 'pm list packages -f'
5. In my case it said: package:/data/app/com.kingo.root-1/base.apk=com.kingo.root So your answer is: com.kingo.root
6. Now in order to launch kingo, you need to find the activity of the package: adb shell pm dump PACKAGE_NAME | grep -A 1 MAIN
7. Start the activity: adb shell am start -n com.kingo.root/com.kingoapp.root.MainActivity
From here I was able to temp root through kingo, and run samsung_unlock_n4-fix. This time I had to only run samsung_unlock_n4-fix once. After that, TWRP installed no problem (where before it would not).
Update:
I am now officially on Jasmine ROM marshmallow. I had to copy the jasmine folder to /data/media/0/TWRP/BACKUPS/xxxx/jasmine
xxxx= you get that from adb devices
Then simply do a restore, after restore, restore the partial firmware file (it has to be done in that order or else it won't work)
Click to expand...
Click to collapse
Just an FYI, you need to run the sasmung_unlock_n4 application twice. The first time, it will write your eMMC CID to the correct one, and the second time you execute, it will write the CID signature/blob to the bootloader - completing the unlock process. Glad to see you got it working.