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.

Rooting?

I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.

What version are you running? B20/B27/B29

If you are not tech savvy, do not attempt the root method. It's for advance user and too many people have bricked their phone already. Just read the threads and you will know what I mean.

S8ntsHaz3 said:
What version are you running? B20/B27/B29
Click to expand...
Click to collapse
I'm running B29.
And yes I can probably guess the amount of people who bricked their phones. But what if everything were to be laid out simple and I follow the directions in every respect? I'm not going to start rooting until I know what I'm doing. So don't worry. I'm stupid but I'm not THAT stupid.

No your fine lmao I started with this phone so we're pretty much same level. As to my understanding it is possible but I would wait just a bit for the b29 stuff to come out.

Don't worry, you're not the only one. I've been reading these tutorials and it's all gibberish, lol.... Every phone I have has been rooted within the first day, this phone I've had over 2 months, and I still can't get it. So you're not alone, lol...

There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice

Bolandk said:
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Click to expand...
Click to collapse
I'm looking closely at this phone now myself...
I've seen the bootloader thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
I'm only interest in this if I can successfully unlock the bootloader and stock root is possible...from what I've read, BOTH can be done. According to the root thread, the model I need (A2017G) is listed as unlockable, correct? What's the difference between a2017g B02 and B03??
RoOSTA

totalFX said:
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
Click to expand...
Click to collapse
OK I have read far too many of these questions here about root on B29 - so here goes.
1. Go to the ZTE website, download the stock B20, and install it.
2. http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 use this to get TWRP installed on your phone - don't worry about root.
3. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 UNLOCK the bootloader
4. http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2 flash boot file, system file, and SuperSU 2.65
Now please relax - anyone here with any dev skills whatsoever are neck deep in other projects (like CM13). B29 hasn't been out long and the only stock image we have from ZTE is B20, which doesn't give us a ton to work with

I also very new to android smartphone and I also feel so so out of place too.
I wish someone make a video how to root this axon 7 phone.
search around youtube jailbrake iPhone is so easy root samsung phone is so easy.... but root axon 7 nothing
I love axon 7 so much now but if I know it's so hard to root i'm just gonna buy samsung phone .
so F..... tired of this youtube ads
ads block is the only reason why I want to root
and that is the only reason why I jailbrake all my ideviese

For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?

tasar said:
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
Click to expand...
Click to collapse
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.

So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Sent from my ZTE A2017U using Tapatalk

polar2792 said:
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Click to expand...
Click to collapse
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.

rczrider said:
[*] *Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
Click to expand...
Click to collapse
Thanks, reboot disemmcwp fixed my write access to /system

rczrider said:
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
Click to expand...
Click to collapse
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk

polar2792 said:
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I think ZTE will eventually put out a bootloader unlock without killing the warranty. But, yeah, either way it's easy enough to do it on your own now.

rczrider said:
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
Click to expand...
Click to collapse
Thank you; thank you, THANK YOU!!!!! I tried for an hour or two, using both ADB and Terminal Emulator to apply this "reboot disemmcwp" fix, and I just couldn't get it to work (I'm on B29). Then, I saw your instructions to use TWRP and followed them, and it worked first time, like a charm!
Thanks again - I'm a very happy camper. You da' man, LOL!
Dennis

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.

G6 Play: Pie Soak Test

Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.

Could anyone verify?

Figures it's for Aljeter. Makes me wonder if Jeter will get it at all.

yes it is for aljeter and is working fine

Spaceminer said:
Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
These installation steps need confirmation. I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Click to expand...
Click to collapse
Tested and working on G6 Play do Brasil!

Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.

Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)

Spaceminer said:
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Click to expand...
Click to collapse
Thanks @Spaceminer !!!! I'll give it a go. I thought at first that I might need to make some sort of patched boot image and faff about quite a bit but your instructions are clear and straightforward.
I must say I'm impressed with the G6 Play. I had a Nexus 6P and a Pixel both of which died on me from physical and customisation fatigue. I could afford a flagship so got this to see be through and I haven't had one complaint yet.
The handful of Pie features and esthetics have been implemented well by Motorola and battery life is still epic on this device.
Edit: rooted and fully set up how I usually have my daily driver handset. Pie is so tasty!

Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...

picopi said:
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
Click to expand...
Click to collapse
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.

madbat99 said:
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
Click to expand...
Click to collapse
Well yeah, I know that much. I meant the extra stuff like unlocking bootloader and downgrading the firmware etc lol. Ta for the extra info, mind.
Extra questions though because despite being having novice experience of doing phone flashing stuff, I've never touched a soak test for official firmware before...but I'm guessing I'll have to move back to Oreo temporarily to get the official Pie update...? Or will it just shift up from this soak test version?

Anyone get this working with the xt1922-7?

Donavonn said:
Anyone get this working with the xt1922-7?
Click to expand...
Click to collapse
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.

Spaceminer said:
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Click to expand...
Click to collapse
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?

Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working

Donavonn said:
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Click to expand...
Click to collapse
Yes, it should be possible on the first setup. I think if it works, LTE probably won't without an APN edit. That's what happens when I flash xt1922-5 RETUS firmware anyways.

picopi said:
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Click to expand...
Click to collapse
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.

Spaceminer said:
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Click to expand...
Click to collapse
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?

picopi said:
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
Click to expand...
Click to collapse
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.

Spaceminer said:
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Click to expand...
Click to collapse
Righto. In that case I'll report back with my findings, but yeah I'd imagine it should work fine as well. We'll see, fingers crossed.