Database Users

Rooting a Z2 with locked bootloader and recent lollipop system

Hi all,
I am kinda new here and would like to put a question, hoping it's not a repetition (I have been browsing though this forum thoroughly, but apparently couldn't find a proper answer). This is the situation:
- bought a used Z2
- Z2 was from UK O2 operator and it had operator lock and unlockable bootloader
- network operator lock has been cleared with unlock code
- O2 customized firmware has been wiped away by flashing a recent 5.0.2 stock lollipop
- unlockable bootloader still exists so cannot upload any customized/rooted .zip system
Clearly, the only thing I can do to modify this phone is to upload .FTF firmares to it, due to unlockable bootloader. Right now, I see available online only unmodified stock .FTF firmwares.
THE QUESTION: is there ANY way to create a pre-rooted .FTF file (modding not strictly necessay but rooting essential) so that I can upload it to the phone?
Thanks for all your precious advice!!!

You can't modify .ftf files as they are signed by sony. easiest solution is to root your phone with kingroot , install nut's dual recovery and then flash any stock prerooted zip (or a custom rom if you want) you can find on this forum. kingroot will be gone when you finish the .zip install too

ptmaniac said:
You can't modify .ftf files as they are signed by sony. easiest solution is to root your phone with kingroot , install nut's dual recovery and then flash any stock prerooted zip (or a custom rom if you want) you can find on this forum. kingroot will be gone when you finish the .zip install too
Click to expand...
Click to collapse
Thanks for answering!
Wouldn't just installing kingroot be enough for a simple rooting of the stock fw?
All I need is the ability to run some apps which need root (e.g. ad-away, set dns, etc.) and nothing more. Is the latest version tested on Z2 running 5.0.2?
Thanks again!

derjaeger said:
Thanks for answering!
Wouldn't just installing kingroot be enough for a simple rooting of the stock fw?
All I need is the ability to run some apps which need root (e.g. ad-away, set dns, etc.) and nothing more. Is the latest version tested on Z2 running 5.0.2?
Thanks again!
Click to expand...
Click to collapse
Kingroot works fine on 5.0.2 but by itself will not disable sony RIC and you won't get a writable system. Nut's dual recovery will disable RIC on boot, just install it after rooting and you should be good to go.
I suggested flashing a preroot zip just because i don't like kingroot app to manage root permissions and it's hard to replace it with supersu. flash a preroot zip and you'll end with a clean stock rom+supersu+nut's dual recovery and fully writable system

Thanks a lot buddy!
I will try kingroot+nut recovery and see how I find myself.
I will always be one step away from uploading a custom .zip in case I need supersu.
You really made my day!!! )))

Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.

gazza35 said:
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
Click to expand...
Click to collapse
Thanks for your answer!
But isn't this procedure including downgrade somewhat longer than the previous suggested one?

gazza35 said:
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
Click to expand...
Click to collapse
Go back to kk? why? it's a waste of time nowadays... the solution i mentioned won't even need to touch flashtool it's easier and quicker...

Just one last question: reading thrads about 5.1.1 it looks that it's due in a few days.
Would it be better to root now (as kingroot is still untested on 5.1.1 ) and then flash 5.1.1.ftf or just wait for it and then root?
Thanks

ptmaniac said:
Go back to kk? why? it's a waste of time nowadays... the solution i mentioned won't even need to touch flashtool it's easier and quicker...
Click to expand...
Click to collapse
Very true and if all are happy then it's all good, just don't forget to check ya phone afterwards for all the intrusive crap that kingroot throws on ya phone, tried it and it definitely didn't root my Z2 or a load of others.

derjaeger said:
Just one last question: reading thrads about 5.1.1 it looks that it's due in a few days.
Would it be better to root now (as kingroot is still untested on 5.1.1 ) and then flash 5.1.1.ftf or just wait for it and then root?
Thanks
Click to expand...
Click to collapse
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
gazza35 said:
Very true and if all are happy then it's all good, just don't forget to check ya phone afterwards for all the intrusive crap that kingroot throws on ya phone, tried it and it definitely didn't root my Z2 or a load of others.
Click to expand...
Click to collapse
Sure, i also don't like kingroot. Like i said before it does root fine but doesn't disable ric, flashing nut's recovery after solves this.
And if you flash a preroot zip after there will be no traces of kingroot on the phone. Downgrade to kk and flashtool is still not necessary...

ptmaniac said:
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
Good afternoon!
I have been though your procedure and, I must say, kingroot and nut's recovery installed well. Now the phone is rooted. Also added Purify app. There is just one problem left.
At the moment I have a stock 23.1.A.1.28 FW installed, just wanted to make a try with a 23.2.A.1.62 to see how the whole process goes. Instead of preparing the full .zip file, I already had a ready one, so I uploaded it into the phone, plus another .zip for gapps. Then, trying to start recovery, the phone does not enter recovery, but boots normally.
I know that nut's recovery is installed well, as, after installation process, it showed up a recovery (philz's?) with grey keys, and I also went though its menus to check it up. Right now these are the ways I tried, failing, to start recovery:
- immediately after switching on the phone (after vibration), pressing volume up
- immediately after switching on the phone (after vibration), pressing volume down
- starting manually (any of the 3 proposed recoveries) from NDR UTILS app
- starting manually from XZRecovery app
None of these methods work, the phone sometimes makes a double reboot (i.e. stays at "sony" first screen goes black and then goes back to sony screen again) but always ends up with loading android system. Is this maybe due to my locked bootloader? In this case would the only option be every time doing FTF upgrade+kingroot+nut's? Or is there some sure method to boot the recovery and install whatever I want?
After all, if it started once, I believe it can start again....
Thanks!
Click to expand...
Click to collapse

derjaeger said:
ptmaniac said:
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
Good afternoon!
I have been though your procedure and, I must say, kingroot and nut's recovery installed well. Now the phone is rooted. Also added Purify app. There is just one problem left.
At the moment I have a stock 23.1.A.1.28 FW installed, just wanted to make a try with a 23.2.A.1.62 to see how the whole process goes. Instead of preparing the full .zip file, I already had a ready one, so I uploaded it into the phone, plus another .zip for gapps. Then, trying to start recovery, the phone does not enter recovery, but boots normally.
I know that nut's recovery is installed well, as, after installation process, it showed up a recovery (philz's?) with grey keys, and I also went though its menus to check it up. Right now these are the ways I tried, failing, to start recovery:
- immediately after switching on the phone (after vibration), pressing volume up
- immediately after switching on the phone (after vibration), pressing volume down
- starting manually (any of the 3 proposed recoveries) from NDR UTILS app
- starting manually from XZRecovery app
None of these methods work, the phone sometimes makes a double reboot (i.e. stays at "sony" first screen goes black and then goes back to sony screen again) but always ends up with loading android system. Is this maybe due to my locked bootloader? In this case would the only option be every time doing FTF upgrade+kingroot+nut's? Or is there some sure method to boot the recovery and install whatever I want?
After all, if it started once, I believe it can start again....
Thanks!
Click to expand...
Click to collapse
Nut's dual recovery works fine on LB (i have unlockable bootloader too) probably something you installed messed up the recoveries, did you install/update busybox from the play store? Nut's dual recovery includes it's own busybox which can't be replaced / updated.
Reinstalling the recoveries with the installer on your pc should fix the problem and make them work again.
Click to expand...
Click to collapse

ptmaniac said:
derjaeger said:
Nut's dual recovery works fine on LB (i have unlockable bootloader too) probably something you installed messed up the recoveries, did you install/update busybox from the play store? Nut's dual recovery includes it's own busybox which can't be replaced / updated.
Reinstalling the recoveries with the installer on your pc should fix the problem and make them work again.
Click to expand...
Click to collapse
Hi,
it looks like the device was somewhat messed up. U were right that i had installed another busybox from gplay, nevertheless uninstalling it did not sort out any effect. Also nut's reinstall failed. Maybe there was some chaos still inside due to experiments done before using kingroot, like, for instance, trying towelroot.
This is how I acted to solve the issue:
- downloaded most recent fw with xperifirm (Telekom.de one, full of useless apps)
- completely flashed phone with .ftf
- reinstalled kingroot
- reinstalled nut's recovery
Now the phone is back again rooted and I deleted some stupid apps with root app delete.
I am now eagerly waiting for 5.1.1 release, hope there will be a vanilla firmware somewhere this week ))
Best would be to already download a patched .zip image.
Right now thanks for the ideas!
Click to expand...
Click to collapse

derjaeger said:
ptmaniac said:
Hi,
it looks like the device was somewhat messed up. U were right that i had installed another busybox from gplay, nevertheless uninstalling it did not sort out any effect. Also nut's reinstall failed. Maybe there was some chaos still inside due to experiments done before using kingroot, like, for instance, trying towelroot.
This is how I acted to solve the issue:
- downloaded most recent fw with xperifirm (Telekom.de one, full of useless apps)
- completely flashed phone with .ftf
- reinstalled kingroot
- reinstalled nut's recovery
Now the phone is back again rooted and I deleted some stupid apps with root app delete.
I am now eagerly waiting for 5.1.1 release, hope there will be a vanilla firmware somewhere this week ))
Best would be to already download a patched .zip image.
Right now thanks for the ideas!
Click to expand...
Click to collapse
It's all part of the experience of learning what's best, I always only use dual recovery because windows can install it directly and root at same time, there used to be plenty of rooting apps like kingroot but you don't see so many anymore, but I'm glad you're sorted, when ya get 5.1.1 just use prfcreater to make it into flashable zip then you don't lose root and have to go through the process all over again.
All the best
---------- Post added at 01:26 AM ---------- Previous post was at 01:21 AM ----------
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Click to expand...
Click to collapse

Thanks a lot!
Yes, it really goes this way, now waiting for an unbranded fw, as this night the first branded ones have started to roll out...
I am really happy: for a couple of months I thought I was buried behind that nasty unlockable bootloader, and now i discovered it's even better, as rooting it without touching bootloader allows the software to work at 100% of it specs
Coming from Samsung to Sony is kinda rough at first for nibbling but when the right instruments are present and clear it's worth dealing with superior hardware.
Also, must say that Sony is lately improving its behaviour, after so many years of mafia attitudes towards buyers
Inviato dal mio X500U utilizzando Tapatalk

I've had Samsung, HTC, Apple, blackberry and finally stuck with Sony, I guess they all have pros and cons, Samsung phones are the easiest to mod and flash, Sony is quite daunting for newcomers very much like HTC. Can be tricky to learn.
Horses for courses and all that, I much prefer a rooted phone with locked boot, no particular reason except the drm keys etc, I do think camera is better on lb, than the quality on ul, although there is a drm restore mod on cross Dev, for ul, it does make xreality work, but it doesn't remove the missing key error in security tests.
I read on a page that once drm keys are gone, Sony won't honour the warranty, very much like Samsung and the knox counter, I'm not sure tho, but I do know I'll always remain Lb and stock based rom.
Only problem I have is getting wifi tethering working properly, it's doing my head in, 4 weeks of decompiling and editing and still can't get my phone to broadcast on any other channel except 1.
GGGRRRRRR @ SONY.
#whattheheckhaveyoudonesony

All so true!
Btw1, when I reflashed last evening the phone was also complaining when I went to hotspot section in order to configure it.... I think they messed up something, but maybe 5.1.1 will have fix so let's see...
I have a couple of Mediacom X500U, which I discovered, besides being fairly nice phones after more than a year of use, that are basically rebranded HTC phones (this comes out of their factory hex code detected by Linux). Do you think they could be modded like for generic HTC or never heard about them?

derjaeger said:
All so true!
Btw1, when I reflashed last evening the phone was also complaining when I went to hotspot section in order to configure it.... I think they messed up something, but maybe 5.1.1 will have fix so let's see...
I have a couple of Mediacom X500U, which I discovered, besides being fairly nice phones after more than a year of use, that are basically rebranded HTC phones (this comes out of their factory hex code detected by Linux). Do you think they could be modded like for generic HTC or never heard about them?
Click to expand...
Click to collapse
Looks like a cheap option of unb
randed HTC, but no, I don't think a HTC section would help.
I think it's an Italian release, dual simply phone, simply Google pointed to an Italian forum androidiani androidiani, run the link through a webpage translator and you may be in luck for root and rom, I think towelroot may root it.

Actually framaroot already offered rooting at the price of a horrible hack (3-4 reboots before device is ready when turning on or rebooting, plus device instability on heavy loads), never tried towelroot on it.
But problem is not about rooting rather than getting rid of horrible stock firmware. The latest fw edition by Mediacom was a total disaster (forums cry loud) and I thought it would be great to try to put some mod on the phones: this is why I had in mind to ask you if there is a general toolkit for HTC phones (like flashtool for Sony) which I could use to try to take care of it and experiment....
Inviato dal mio X500U utilizzando Tapatalk

1050F: OTA Update #S100256_160119

Received this yesterday evening and am wondering if anyone has a good idea of what this update entails. It states is security patch and stability fix, if I'm not mistaken. Probably just a regular non-major update, then?

I am in the middle of returning my tab back to stock to then update to this update... Will report back in a while. @all
If you have unlocked your bootloader to use a custom recovery DO NOT UPDATE. It will soft brick!!! I tried in vain and am having to resort to 'back to stock' as, like a pleb, I don't backup before I tinkered
Sent from my SM-G901F using Tapatalk

I happens to the best of us, man. Sorry to hear. I'm currently not rooted, but at some point will, so that possibility of messing up will ALWAYS be there.

i have just updated my yoga 830LC. But i forgot my bootloader is unlocked. It's soft brick. Can you help me how to back to stock Lollipop ROM. please help me! thanks

Do you have a backup? When I first tried to update I think it did update part of the rom. I reflashed the patched esp (which you should still have if you have unlocked you boot-loader)
It then let me in to recovery and to restore.
Try that and report back
Sent from my SM-G901F using Tapatalk

Hi. I have this update from lenovo too, my 1050F is rooted, how I do a backup ? and you flash which stock rom, before upgrading ?
If possible, I want to keep my data.
Thank you.

I think the only way to keep you data is with something like Titanium backup saved to an external source and then whenever the update is finished re-root and restore selected backed up data

If you have unlocked you boot-loader you must have flashed a customers recovery. I did a twrp back up and selected what I want to restore.
Edit - get the files you need from this post
corasman said:
Hi Rob
These files I copied from various threads on here.
They are on my g/drive,if they are any good to you or anyone else.
http://tinyurl.com/zdr92pf
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo
http://tinyurl.com/hjy4kks
http://tinyurl.com/jhrjscj
Click to expand...
Click to collapse
Sent from my SM-G901F using Tapatalk

I have the 8 inch version of this tablet (830F) and received a similar update notification.
I just used the temp recovery trick to root and disable some bloat but left it otherwise stock. The tablet is currently in the process of backing up with temp TWRP and I was thinking of unrooting and giving this update a shot.
But it's not worth losing root over it...
Did anyone apply the patch in the meantime? Were you able to root again?
Thanks.

Yeah I have rooted, unlocked the boot-loader and flash twrp... All is good.
Have you flashed the patched boot-loader? If so you will need to flash the stock 830F ROM

Soft Brick
I'm just leaving my experience in case anyone does the same mistake as I.
I tried to use de "Hide root" option of SuperSu before upgrading, I have a locked bootloader, so I thought that it would be enough but I well... it didn't even boot after de lenovo screen
So I had to returno to stock, after reading what other peole did I manage to finally flash it back to stock lollipop.
I download this stock rom from lenovo-forums.ru
1050f_s100196_151123_row_lос-50
Click to expand...
Click to collapse
[As rookie, cannot post links :silly:]
Before flashing, the flash.xml has to be edited. Find
<string>fastboot flash system $system_file</string>
Click to expand...
Click to collapse
and add -s 1G to the command
<string>fastboot -S 1G flash system $system_file</string>
Click to expand...
Click to collapse
Then, enter on bootloader mode. I did it from de Recovery Mode (PWR on, and after de "lenovo" press both volume keys)
And just flash it with Phone Flash Tool
Everything it's probably pretty obvious for many of you but I leave this here for noobies like me! :victory:

Thank you 69PerTTu69.
Did you have keep your data partition?
I have understood you have only install system partition. Right ?
If so, I Will try to use your method.

Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.

-beluga- said:
Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.
Click to expand...
Click to collapse
I have a new 1050F which has finished churning through all the updates to get it from KitKat.
It is now at the level of this update (..S100256_160119..)
I was about to root following the "[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]" 1st post instructions by AndroMAN (which uses a temporary pushed recovery) but I'm now a little concerned since that will put me in exactly the position of you -beluga-.
I'd be grateful if you could let me know how you get on (or if anyone else can comment on whether attempting to root this way is now a bad idea)

-beluga- said:
Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.
Click to expand...
Click to collapse
Ok, this was a success -
1. Unroot through the SU app (just to be safe)
2. Restart
3. Apply the update through the regular system/settings UI and wait for it to finish
4. Re-root as before (using IntelAndroid-FBRL-07-24-2015 and BETA-SuperSU-v2.67-20160121175247)
Keep in mind that I was on stock bootloader and didn't alter much besides disabling crapware. Deeper modifications may cramp your style.
Cheers
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
dingers01 said:
I have a new 1050F which has finished churning through all the updates to get it from KitKat.
It is now at the level of this update (..S100256_160119..)
I was about to root following the "[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]" 1st post instructions by AndroMAN (which uses a temporary pushed recovery) but I'm now a little concerned since that will put me in exactly the position of you -beluga-.
I'd be grateful if you could let me know how you get on (or if anyone else can comment on whether attempting to root this way is now a bad idea)
Click to expand...
Click to collapse
Yes, this worked fine. See my other follow up post. Good luck.

saupiquet said:
Thank you 69PerTTu69.
Did you have keep your data partition?
I have understood you have only install system partition. Right ?
If so, I Will try to use your method.
Click to expand...
Click to collapse
Sorry for the delay, but no. Everything within the internal storage will be lost.

Safe System Updates_6.0.1 MM_FlashFire, dm-verity work around, SM-N910V

This is too complicated for me to explain everything but here is my Cheat Sheet !
If you have been flashing you probably already have these files.
1. Odin SamMobile N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar
reboot and factory reset a few times if needed to remove custom icon, Block SDM
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar
( ! System and Cache only ! ) Unblock SDM
8. Now with FlashFire installed and Granted SU Access, Check for new system updates in Phone Setting.
It could start downloading automatically or it may not download for hours. I have tested both scenarios
9. When Updates finishes downloading open FlashFire to install the update.
I got the Build update MMB29M.N910VVRU2CPF3 over the air.
Your mileage may vary.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting of 5.1.1
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on[Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1]then you can use FlashFire.
EDIT: You have to do step 7 manually with N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar manually download to your phone. Automatic updates start after step 8 with SDM unblocked.
Credit AstonsAndroid I found it HERE

Reserved
FlashFire
Many of the problems we have been having with the Safe Upgrade to Marshmallow are not present with the FlashFire System Flash.

Interesting, may have to give this a spin at some point. This fixes the issue of DM-Verity, produces a clean EFS folder to go along with Root/unlocked bootloader when the steps are finished?

It's true, I tried this awhile back when doctor-cool posted this in one of the theads in the development forums. I was experiencing an inability to send MMS messages, the "Roam Indicator" message and missing the Applications option in the Setting menu. After reflashing CPD1 through FlashFire, it fixed everything. Flashed the CPF3 update through FlashFire as well and am currently up to date.

doctor-cool said:
This is too complicated for me to explain everything but here is my Cheat Sheet !
If you have been flashing you probably already have these files.
1. Odin SamMobile N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with adb , samsung_unlock_n4-fix
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP then boot System
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar
( ! System and Cache only ! )
8. With FlashFire installed and Granted SU Access, Check for new system updates in Phone Setting.
It could download automatically.
9. When Updates finishes downloading open FlashFire to install the update.
I got the Build update MMB29M.N910VVRU2CPF3 over the air.
Your mileage may vary.
Credit AstonsAndroid I found it HERE
Click to expand...
Click to collapse
So reading your instructions we don't worry about rooting (unlocking the bootloader) till step 3? I need to try this if I can because I suspect Kingroot and Kingoroot has screwed up my EFS folder. It's to the point that when I try to root again thru those 2 apps it locks up and throws me into a bootloop everytime. I'm really hoping to get my Note 4 back to normal operating but I'm to the point I think an XDA expert who had their hands on it would be my only hope. Any suggestions or help would be greatly appreciated :fingers-crossed:

lorilucille9 said:
So reading your instructions we don't worry about rooting (unlocking the bootloader) till step 3? I need to try this if I can because I suspect Kingroot and Kingoroot has screwed up my EFS folder. It's to the point that when I try to root again thru those 2 apps it locks up and throws me into a bootloop everytime. I'm really hoping to get my Note 4 back to normal operating but I'm to the point I think an XDA expert who had their hands on it would be my only hope. Any suggestions or help would be greatly appreciated :fingers-crossed:
Click to expand...
Click to collapse
that's the way I did it

doctor-cool said:
that's the way I did it
Click to expand...
Click to collapse
Well my problem is I'm stuck btw being rooted and not rooted. The phone says I am (phone state = custom) but any other app says I'm not. I try to root again thru Kingroot/Kingoroot and it fails both by APK and Desktop version. Reinstalling official LP still holds remnants over and it's not a clean install like everone thinks. I'm on my last nerve with this and all I want is to get my phone back to root so I can clean up the crap in efs folder or truly do a clean back to stock flash. Can accessing the phone to do this be done any other way?
Sent from my SM-G935V using XDA-Developers mobile app

lorilucille9 said:
Well my problem is I'm stuck btw being rooted and not rooted. The phone says I am (phone state = custom) but any other app says I'm not. I try to root again thru Kingroot/Kingoroot and it fails both by APK and Desktop version. Reinstalling official LP still holds remnants over and it's not a clean install like everone thinks. I'm on my last nerve with this and all I want is to get my phone back to root so I can clean up the crap in efs folder or truly do a clean back to stock flash. Can accessing the phone to do this be done any other way?
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
Try from within Phone Setting a Factory Reset after the first step

doctor-cool said:
Try from within Phone Setting a Factory Reset after the first step
Click to expand...
Click to collapse
Several times I have... nothing wipes it completely clean. Does EFS folder get touched when flashing or Odining official firmware? I think that folder is my problem to it all.
Sent from my SM-G935V using XDA-Developers mobile app

lorilucille9 said:
Several times I have... nothing wipes it completely clean. Does EFS folder get touched when flashing or Odining official firmware? I think that folder is my problem to it all.
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
You absolutely could have corruption of the efs folder. The only way I personally know of to clean the efs folder is HERE.
But you need Root to do it.

doctor-cool said:
You absolutely could have corruption of the efs folder. The only way I personally know of to clean the efs folder is HERE.
But you need Root to do it.
Click to expand...
Click to collapse
Everything worked though before I switched phones. I have a backup of my EFS folder via TWRP... is there any way to edit the backup so just the files that should be there are there then reinstall? Do you know anyone that would be willing and trusting to fix my phone if I sent it to them? I'd pay to get it fixed too!
Sent from my SM-G935V using XDA-Developers mobile app

lorilucille9 said:
Everything worked though before I switched phones. I have a backup of my EFS folder via TWRP... is there any way to edit the backup so just the files that should be there are there then reinstall? Do you know anyone that would be willing and trusting to fix my phone if I sent it to them? I'd pay to get it fixed too!
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
No Way, I would not try to edit that backup partition. It may end up unable to mount.
You're on the wrong thread. You need to establish a simple unlocked 5.1.1 bootloader.

doctor-cool said:
No Way, I would not try to edit that backup partition. It may end up unable to mount.
You're on the wrong thread. You need to establish a simple unlocked 5.1.1 bootloader.
Click to expand...
Click to collapse
The backup is what I meant on editing and I'm on this thread because in the beginning you made it sound like I don't have to start from LP... I asked that... and was hoping this may be a different way to get my root back. Sorry!
Sent from my SM-G935V using XDA-Developers mobile app

lorilucille9 said:
The backup is what I meant on editing and I'm on this thread because in the beginning you made it sound like I don't have to start from LP... I asked that... and was hoping this may be a different way to get my root back. Sorry!
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
It's Okay good luck but I was able to skip the recommended rooting of 5.1.1
In this example, I did not unlock until step 3 and I did not permanent root until step 6.
The process I used to unlock is
HERE I just re-tested and the OP is valid.

Thanks for the detailed listing of downloads and links for instructions. To be clear, in both of the links you provided for instructions on unlocking your bootloader, the instructions say you need root (su) in order to run the samsung_unlock_n4-fix. However, you are saying that you were able to run it successfully without root (or at least without Kingroot)? Also, could you clarify what you mean by "use SIM card for data" in step 3 of the OP?

azumandias said:
Thanks for the detailed listing of downloads and links for instructions. To be clear, in both of the links you provided for instructions on unlocking your bootloader, the instructions say you need root (su) in order to run the samsung_unlock_n4-fix. However, you are saying that you were able to run it successfully without root (or at least without Kingroot)? Also, could you clarify what you mean by "use SIM card for data" in step 3 of the OP?
Click to expand...
Click to collapse
Thanks, I should have said permanent root. You do have to use Kingroot to use the samsung_unlock_n4-fix but you don't have to install Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.

I tryed to do flash fire only problem was I wasn't able to do anything. I hit the plus icon to search for it with no luck and it was there because I got the box asking to install now or later
Sent from my SM-N910V using XDA-Developers mobile app

rmc198501 said:
I tryed to do flash fire only problem was I wasn't able to do anything. I hit the plus icon to search for it with no luck and it was there because I got the box asking to install now or later
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
You have to do step 7 manually with N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar manually download to your phone. Automatic updates start after step 8

I have been trying to root for days and I can not get anywhere. I'm doing something wrong but I don't know what it is. And trying to get help is like asking for a million bucks just ant gonna happen.
Sent from my VS990 using Tapatalk

mwebb34 said:
I have been trying to root for days and I can not get anywhere. I'm doing something wrong but I don't know what it is. And trying to get help is like asking for a million bucks just ant gonna happen.
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
You could have a hardware problem even a bad usb cable

Samsung Galaxy J3 SM-S320VL need this rooted

Hi,
i need to get this phone rooted please, no root apps works, @Chainfire maybe can help?

Any one be able to help if this can be rooted?

xxmcvapourxx said:
Any one be able to help if this can be rooted?
Click to expand...
Click to collapse
Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.
KNOX should remain 0x0
Instructions
1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.
2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3
3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.
4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.
5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
6. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl
Good luck I hope it works for you.
.

ashyx said:
Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.
Instructions
1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.
2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3
3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.
4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.
5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
6. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl
Good luck I hope it works for you.
.
Click to expand...
Click to collapse
Hi quick question ,
i've done steps 1-3 worked fine - http://pastebin.com/raw/PbA49d0q
my next question cant i get a custom twrp to root it or custom rom cause kingaroot not working properly.

xxmcvapourxx said:
Hi quick question ,
i've done steps 1-3 worked fine - http://pastebin.com/raw/PbA49d0q
my next question cant i get a custom twrp to root it or custom rom cause kingaroot not working properly.
Click to expand...
Click to collapse
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?

ashyx said:
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
Click to expand...
Click to collapse
when trying to root
By Kin9Root Won Chu chu in a few ROot failure 'not yet suitable ˉ a - condolence ˉ ˉ a ˉ a "` ` One by one - one 'one one '- one - the
i get i've tried the pc version and the apk a few tries i keep getting notifications in the settings it is set to permissive

ashyx said:
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
Click to expand...
Click to collapse
i keep getting stuck on this : https://s4.postimg.org/mxi70k1vx/Image3.png
figured it out -- it was the pin we just trying super me

xxmcvapourxx said:
i keep getting stuck on this : https://s4.postimg.org/mxi70k1vx/Image3.png
ok I tried 3 different cords, various lengths, and now no matter what I get this screen only
Click to expand...
Click to collapse
You're using the desktop version, please download and use the android English apk:
http://www.apkmirror.com/apk/kingro...-release/kingroot-5-0-5-android-apk-download/
.

Is there an update on this, did anyone achieve root?
.

ashyx said:
Is there an update on this, did anyone achieve root?
.
Click to expand...
Click to collapse
Hi,
Just update :
used the bootimge via odin works fine.
Installed kingaroot via app root takes a few times.
Superme (legit) brought removes kingaroot and installs super su and binaries then reboots <---- here i lose root again i have to use kingaroot sometimes it auto reboots it self.
My friend also has the same phone do you have skype or telegram so we can chat private

xxmcvapourxx said:
Hi,
Just update :
used the bootimge via odin works fine.
Installed kingaroot via app root takes a few times.
Superme (legit) brought removes kingaroot and installs super su and binaries then reboots <---- here i lose root again i have to use kingaroot sometimes it auto reboots it self.
My friend also has the same phone do you have skype or telegram so we can chat private
Click to expand...
Click to collapse
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.

ashyx said:
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
Click to expand...
Click to collapse
Yes as soon as super su me installs ask to install binaries ans ask to reboot it will lose root.
I will try the script without flashing firmware
Thank you ill let you know how i get on

ashyx said:
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
Click to expand...
Click to collapse
My friend done a tutorial what he did on the process when losing root he followed your first guide http://pastebin.com/raw/ZSZExWt6

xxmcvapourxx said:
My friend done a tutorial what he did on the process when losing root he followed your first guide http://pastebin.com/raw/ZSZExWt6
Click to expand...
Click to collapse
It's not related to the bootloader, the bootloader is still locked, it's simply an incomplete installation of SuperSU. Probably due to permissions.
Follow the guide posted above and you should be good. I'd also suggest using root package disabler to disable knox.
Hit search in the app and type knox. Disable all knox related files.
https://play.google.com/store/apps/details?id=com.kunkunsoft.rootpackagedisablerfree
.

So can anybody confirm where we're up to with this. Has root been achieved? Are we good to post this as a viable root solution?

ashyx said:
So can anybody confirm where we're up to with this. Has root been achieved? Are we good to post this as a viable root solution?
Click to expand...
Click to collapse
Hi,
still not rooting perm -- Followed the exact tutorial you have gave us , me and my friend and we both lost root.
stock > odin > kingroot apk > supersu me > flashfire > supersu-sytemmode.2.79 rebooted lost root.
the only way we can do this is not to ever reboot....to keep root

xxmcvapourxx said:
Hi,
still not rooting perm -- Followed the exact tutorial you have gave us , me and my friend and we both lost root.
stock > odin > kingroot apk > supersu me > flashfire > supersu-sytemmode.2.79 rebooted lost root.
the only way we can do this is not to ever reboot....to keep root
Click to expand...
Click to collapse
So even when flashing root with Flashfire still losing root? Did you try using the script posted above?
Also could you post a screenshot of Root validator after losing root?
I would also suggest flashing the stock firmware with FLASHFIRE.
Ensure to Uncheck the boot partition and disable EverRoot.
Add the system supersu zip to the install.
It may be remnants of Kingroot causing the issue. Flashing this way will ensure a clean system with just supersu.

Having the same problem
I can't even do the OEM unlock and wondering if Knox is stopping me from doing it. Kingroot gets to about 77% before giving up. Also tried "one click root" and "odin" and a couple of others. Tried to uninstall Knox with many different aps but noway will it let me. I bought this J3 in HongKong and it is full of crap and adds that pop up and cover the whole screen. I have had some negative affects on the phone with all the playing around I've done to the point where when I hold down the buttons (power volume etc) the phone just goes into its first normal boot screen and stays there. Hope I haven't hijacked the thread but thought I may have the same problem as the original thread poster

stanfox said:
I can't even do the OEM unlock and wondering if Knox is stopping me from doing it. Kingroot gets to about 77% before giving up. Also tried "one click root" and "odin" and a couple of others. Tried to uninstall Knox with many different aps but noway will it let me. I bought this J3 in HongKong and it is full of crap and adds that pop up and cover the whole screen. I have had some negative affects on the phone with all the playing around I've done to the point where when I hold down the buttons (power volume etc) the phone just goes into its first normal boot screen and stays there. Hope I haven't hijacked the thread but thought I may have the same problem as the original thread poster
Click to expand...
Click to collapse
Why can't you enable OEM unlock? Remove any pin/password from the device first.

ashyx said:
Why can't you enable OEM unlock? Remove any pin/password from the device first.
Click to expand...
Click to collapse
I was surprised at first when you directed me to this thread ashyx, the first word I saw was Kingroot and I was sure a dev such as yourself wouldn't use that.
I write against Kingroot all the time. It is information stealing malware that doesn't even give true root, packs PUPs, and sends IMEI and other info to China upon install (check the logcat).
And it's nortoriously hard to get rid of and replace with a different SU. From what I read above, true root hasnt' been achieved yet. Ive used KR a few times in the past, but never again. It used to be easier to replace KingUser w SuperSU. Not so much anymore.
Please folks, Kingroot IS NOT actual root ; please quit posting about it in a true professional developer site.
Ahyx, PM me if you wish. I'd like to work on any methods other than this. I can get the bootloader unlocked from Net 10. But not until having it hooked up w/ lthem for a year. I've already chosen to disconnect this device anyhow because I can't stand using a non-rooted phone. Too bad, it's a good machine. I got a great buy on it. $50US brand new. Same store today $99. WalMart = $120
I just bought an LG G3 for $45. Verizon model, interesting root. I had to downgrade firmware to achieve root. It's TWRPd, and running Dirty Unicorns 10.6, a nice rom, better once I mod it.
Tried the latest RR rom for it. Nougat was cool, but too early, too many bugs.

Shortcut to being rooted on N910VVRU2CQI2

Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE

I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks

My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839

RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.

Thanks doc. Is that a folder that gets overwritten when you flash a new room?

This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?

lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works

RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.

does this require the developer version? btw how do i backup

I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.

RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.

kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.

Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.

In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.

Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.

Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.

Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?

lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.

kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.

Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.