Database Users

buying a new razr m to root?

I'm entirely new to anything phone/development related so I apologize for my ignorance (I also apologize if this is in the wrong section). I've had a razr M for about 2 years now and I'm entirely content with it except after the last update I can no longer use my foxfi for wifi access. From what I understand I can't root my phone and downgrade from this operating system so my question is this: Can I buy a new one off ebay for ~$100, root it and use foxfi (or some other free wifi tether) while keeping my unlimited data and not "bricking" it? The battery on my current phone has gone to crap anyways and I was considering buying a replacement phone considering they're only ~$100 anyways.
It's a pain in the but trying to figure all of this out with only limited time to browse the internet at work and trying to sort the 100's of pages of info from my phone.
Is this feasible? Are there certain things I need to verify about a phone before I buy it to make sure I can complete this process?
Thanks in advance,
Rory

If you're on the latest firmware, you CAN root with Towel Root and unlock with Motopocalypse. Then you can downgrade back to JB. There's a method posted by @bweN diorD somewhere in this forum.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
If you're on the latest firmware, you CAN root with Towel Root and unlock with Motopocalypse. Then you can downgrade back to JB. There's a method posted by @bweN diorD somewhere in this forum.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks RikRong! How do I know if I'm on the latest firmware (does that just mean the latest operating system? My phone says 4.4.2 so I'm assuming that's a yes)? Sorry, there's a thousand new terms and I'm struggling to take in what this all means.
When it comes to trying to root my phone, since I have no more foxfi I also don't have a way to have internet access on my computer/tablet to walk me through the rooting process/assist me if something goes wrong with the... would you think it's intuitive enough/fullproof that if I print out the thread I can just follow it through and shouldn't have issues? Also, I looked through the first 4 or 5 pages in this forum and didn't find any threads started by "bweN dior" but I'm probably just overlooking what I'm looking for. Do you know what the thread was titled?
Thanks,
Rory

http://forum.xda-developers.com/showthread.php?t=2783157
Install .apk and run
Profit
Don't forget to thank geohot

rypkr937 said:
Thanks RikRong! How do I know if I'm on the latest firmware (does that just mean the latest operating system? My phone says 4.4.2 so I'm assuming that's a yes)? Sorry, there's a thousand new terms and I'm struggling to take in what this all means.
When it comes to trying to root my phone, since I have no more foxfi I also don't have a way to have internet access on my computer/tablet to walk me through the rooting process/assist me if something goes wrong with the... would you think it's intuitive enough/fullproof that if I print out the thread I can just follow it through and shouldn't have issues? Also, I looked through the first 4 or 5 pages in this forum and didn't find any threads started by "bweN dior" but I'm probably just overlooking what I'm looking for. Do you know what the thread was titled?
Thanks,
Rory
Click to expand...
Click to collapse
actually, i didnt make a guide for this model. i made it for the hd/maxx hd. the root and bootloader unlock is the same and you can use those files, but you can NOT use any of the phone specific software in the guide or you will likely brick your phone.
http://forum.xda-developers.com/showthread.php?t=2789743

bweN diorD said:
actually, i didnt make a guide for this model. i made it for the hd/maxx hd. the root and bootloader unlock is the same and you can use those files, but you can NOT use any of the phone specific software in the guide or you will likely brick your phone.
http://forum.xda-developers.com/showthread.php?t=2789743
Click to expand...
Click to collapse
Yeah, I saw that it was someone else that made the guide for the M, but I like how yours is set-up. I was going to point him to your thread in the HD forum for rooting and unlocking, then refer him to guide in the M forum for downgrading. Use Bwen's guide to use Towel Root and Motopocalypse. Get TWRP from here: http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img and flash a SU zip to gain permanent root. Then use this guide to downgrade: http://forum.xda-developers.com/showthread.php?t=2786016 .

RikRong said:
Yeah, I saw that it was someone else that made the guide for the M, but I like how yours is set-up. I was going to point him to your thread in the HD forum for rooting and unlocking, then refer him to guide in the M forum for downgrading. Use Bwen's guide to use Towel Root and Motopocalypse. Get TWRP from here: http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img and flash a SU zip to gain permanent root. Then use this guide to downgrade: http://forum.xda-developers.com/showthread.php?t=2786016 .
Click to expand...
Click to collapse
Okay, I'm trying to start this process. From my droid, I downloaded http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img but immediately I'm encountering problems. My phone says it cannot open this file. I'm already dreading this is going to be difficult/dangerous...
Why can't I open this file? Also, what is flashing a SU zip?

There is far too much about this I don't understand.
I am willing to pay someone to root a razr m for me. Do I have any takers?

Towel Root and Motopocalypse are both apps that you can download to the phone and then run. They're just apps, so they are as easy as opening the app then running. You need to use Towel Root, then Motopocalypse to unlock, and then you can install TWRP. If you don't want to use fastboot to install recovery, then you can flash it with Rashr or Flashify. Just download TWRP and place on your external SD, no need to open or extract it. Flash it with one of those apps. Once you're rooted and unlocked, you should be able to use that guide to downgrade.
Sent from my HTC6525LVW using Tapatalk

rypkr937 said:
Okay, I'm trying to start this process. From my droid, I downloaded http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img but immediately I'm encountering problems. My phone says it cannot open this file. I'm already dreading this is going to be difficult/dangerous...
Why can't I open this file? Also, what is flashing a SU zip?
Click to expand...
Click to collapse
just use the tutorial i posted before as a guide, substituting the files @RikRong gave you for the recoveries.
i just updated the guide to include a complete step by step for flashing the recoveries and su zip.
the only thing you will need is fastboot and adb in the same folder with your recovery file.
the guide instructs to use adb and fastboot from my script, but you wont have my script. thats why you need to grab adb and fastboot from google.
its not difficult, you just dont understand what needs to be done. you dont open the recovery with the phone booted up. just read the guide and subsequent link to the step by step and you will quickly see where you are going wrong.
http://forum.xda-developers.com/showthread.php?t=2789743
just a quick disclaimer for those not following along, ^^^^^ the firmware and recoveries in this guide are for the 926 only!!! use it for reference only!! any other files in the guide and the guide itself, is universal.

rypkr937 said:
There is far too much about this I don't understand.
I am willing to pay someone to root a razr m for me. Do I have any takers?
Click to expand...
Click to collapse
Please refer to this thread > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

Now I think I got problems. I thought I had it all figured out with all of the walkthroughs. I have the phone in fastboot mode and I was flashing it with RSD for the previous firmware. It was going through the steps and on 7/20 it said failed flash. I tried again and now it says failed flash after 1/20. I'm afraid to try and boot the phone. What should I do?

rypkr937 said:
Now I think I got problems. I thought I had it all figured out with all of the walkthroughs. I have the phone in fastboot mode and I was flashing it with RSD for the previous firmware. It was going through the steps and on 7/20 it said failed flash. I tried again and now it says failed flash after 1/20. I'm afraid to try and boot the phone. What should I do?
Click to expand...
Click to collapse
If your boot loader isn't unlocked, you can't flash older FW. Did you unlock already?
Sent from my HTC6525LVW using Tapatalk

rypkr937 said:
Now I think I got problems. I thought I had it all figured out with all of the walkthroughs. I have the phone in fastboot mode and I was flashing it with RSD for the previous firmware. It was going through the steps and on 7/20 it said failed flash. I tried again and now it says failed flash after 1/20. I'm afraid to try and boot the phone. What should I do?
Click to expand...
Click to collapse
It says USB error. I unplugged it from the computer and tried it again. It's step 7/20 "flash modem "non-hlos.bin" where it is getting screwed up.

RikRong said:
If your boot loader isn't unlocked, you can't flash older FW. Did you unlock already?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yes. I think? I did these steps successfully
-----------------------------------------
2. BOOTLOADER UNLOCKING
-----------------------------------------•Download Towel Root [XDA] [WEBSITE] - Disregard if you have previously rooted using Towel Root
•Download Motopocalypse [WEBSITE] [DOWNLOAD]
•Place both on external SDcard
•Install and run Towel Root
•Follow any in-app prompts
•Reboot
•Install and run Motopocalypse
•Follow any in-app prompts
•Reboot
•PROFIT!
My error specifically says this:
Failed flashing process. 7/20 flash modem "non-hlos.bin" -> USB error occurred while reading/writing.

I unplugged it and tried another USB port and it went through all the steps 20/20. Then it rebooted my phone and the phone says "please wait, this may take a few minutes". After several minutes RSD told me to "manually power on the phone". Since the phone was never shut off I couldn't do this so I unplugged the USB and replugged it in thinking maybe there was another USB error. RSD has now finished and says result is "PASS". However my phone still says "please wait, this may take a few minutes". Should I let me phone be or should I restart it?

rypkr937 said:
I unplugged it and tried another USB port and it went through all the steps 20/20. Then it rebooted my phone and the phone says "please wait, this may take a few minutes". After several minutes RSD told me to "manually power on the phone". Since the phone was never shut off I couldn't do this so I unplugged the USB and replugged it in thinking maybe there was another USB error. RSD has now finished and says result is "PASS". However my phone still says "please wait, this may take a few minutes". Should I let me phone be or should I restart it?
Click to expand...
Click to collapse
do the 3 button trick to get into flash mode and tell us what the status code is please.

bweN diorD said:
do the 3 button trick to get into flash mode and tell us what the status code is please.
Click to expand...
Click to collapse
power + volume up + down rebooted me to a screen that asked me to select my language (just as before). After selecting English it goes back to the "please wait this make take a few minutes" screen.

It's working!!!! I just ran RSD again (and this from the start on a usb 2.0 port as I read 3.0 can screw it up). This time it worked like a charm! I'm back on jellybean and posting from my laptop through a foxfi connection from my phone! SO thankful for this and those who did the write ups/walk throughs and posted in here! I got a lot of apps and setting to update ahead of me ugh. I'm going to do some donating here for the help! Thanks to those who posted in this thread and the ones who made those write ups and the app developers!

How do I keep my phone from automatically updating back to KK?? I didn't let it update when KK originally came out (I just kept clicking postpone) until about a month or two later it just updated on it's own. Well my phone just started automatically downloading a system update again. I put it in airplane mode but how do I keep this update from happening again and getting screwed by KK again?

Xposed installed

Ok guys, bear with me.
I haven't done much "developing" or anything but I was able to get Xposed to install and now have Gravity Box running on my stock and locked Maxx. I used the KingRoot described and provided in the thread http://forum.xda-developers.com/droid-ultra/general/root-kingroot-4-4-4-su-6-7-t3117552 by @aviwdoowks. I had installed SuperSU Pro, KingRoot from the aforementioned thread, and the Xposed framework. After getting root with KingRoot, I went into SuperSU and checked survival mode (don't know if this does anything or not). Then, I went into Xposed and had it set to classical installation.
Now, this is where some persistence and effort went into effect. Through multiple attempts, of rebooting , KingRoot rooting, and trying to install Xposed, it finally took. Where aviwdooks, says to wait after booting to run KingRoot, I ran it immediately. As soon as root was obtained I would go into Xposed and run the Classical install. When it finally took, and asks to reboot, HIT CANCEL. Then from the Xposed menu, hit soft-reboot. So far I have survived multiple soft-reboots with Xposed running.
hope this helps someone.

@teerout
Kudos
Does it all go to data? Or rather once installed is system not utilized?
Btw the synchronization to gdrive is all sorted out now. My entire sd excluding 0/TiBU AND including legacy/TiBU!! Using Drive AutoSync.
Ti does tower above He in both convenience and allowing all user apps. I thought I would say it here as my thread is rather a mess

Avi,
I don't know how to answer that about data or system being utilized. Good work with getting the backups to work. I should do something similar.

teerout said:
Avi,
I don't know how to answer that about data or system being utilized. Good work with getting the backups to work. I should do something similar.
Click to expand...
Click to collapse
Still working?
How long now?

yes, still working. I had it running the other day, but wanted to make sure I could recreate it before posting on here. So from installing it this morning around 830, its past noon now, still working and surviving the soft-reboots. it looses functionality on a hard reboot, but can always be re-activated. hope to hear others can get it too.

@teerout
Hi,
You on su6-7.2?
We are all waiting to hear from you at 9:41am sharp.

Yes this is a known effect of a soft boot. You can change anything you want in /system (with root) as long as you only do soft boot. Only the user apps get initialized from terminating zygote.
You are better flashing in root per CrashXXL's thread. It would be nice to bake xposed in so it survives a KK OTA like root does but I suspect the only way is to image and flash the entire 6-72 /system partition.

aviwdoowks said:
@teerout
Hi,
You on su6-7.2?
We are all waiting to hear from you at 9:41am sharp.
Click to expand...
Click to collapse
No, SU6-7.
Yea, Ive been debating if I want to take the steps to work through the method crash put together. Got essentially the same results. Im tempted to try the "crash" method with an older fxz from Moto, but don't want to destroy my device.

teerout said:
No, SU6-7.
Yea, Ive been debating if I want to take the steps to work through the method crash put together. Got essentially the same results. Im tempted to try the "crash" method with an older fxz from Moto, but don't want to destroy my device.
Click to expand...
Click to collapse
Have many bricked that way? I just thought it was damn arduous.
Soooo how long?

aviwdoowks said:
Have many bricked that way? I just thought it was damn arduous.
Soooo how long?
Click to expand...
Click to collapse
don't think anyone has reported they bricked, im just hesitant to force my phone to brick through the process. im also trying to determine from this other thread by littletoslo in the QA section, if they used an older fxz file and got it to work.
xposed is still running with the gravity box mods, no hiccups.

On 6-7, the crashxxl method survives a hard reboot for both su and xposed. Using an older or newer fxz with the crash method will brick your device. Furthermore, just flashing an older version may result in serious gpt version issues.
Sent from my XT1080 using XDA Free mobile app

larsdennert said:
On 6-7, the crashxxl method survives a hard reboot for both su and xposed. Using an older or newer fxz with the crash method will brick your device. Furthermore, just flashing an older version may result in serious gpt version issues.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
To verify: I took the OTA this morning after a quick skim of xda, much to my chagrin, as I learned xposed didn't survive. To fix this, I can just reflash the 6-7 back using rsdlite and I'm back in business? Is anyone working on a fix for surviving hard reboot with baked in xposed on the 6-7.2? Thanks!

Yes the keys didn't update. You can do a full rsd flash of 6-7 and go back through the root/xposed process. If I find some time I will tackle making a system image of 6-7.2 with root and xposed. It may come down to root on the G4 though. If it doesn't have a R/O system image, I'm jumping ship from many years of Motorola.

larsdennert said:
Yes the keys didn't update. You can do a full rsd flash of 6-7 and go back through the root/xposed process. If I find some time I will tackle making a system image of 6-7.2 with root and xposed. It may come down to root on the G4 though. If it doesn't have a R/O system image, I'm jumping ship from many years of Motorola.
Click to expand...
Click to collapse
How this pertains to the op?

aviwdoowks said:
How this pertains to the op?
Click to expand...
Click to collapse
Basically just reaffirming that you can temp install xposed if you have some sort of root as long as you only soft reboot. Problem is you can only soft reboot so many times before it locks up and then you have to cold boot (Vol up + Vol Dn + Power). A better way is to bake it in to the r/o system image like CrashXXL and the Moto X. An even better way is to be done with Motorola LOL.

larsdennert said:
Basically just reaffirming that you can temp install xposed if you have some sort of root as long as you only soft reboot. Problem is you can only soft reboot so many times before it locks up and then you have to cold boot (Vol up + Vol Dn + Power). A better way is to bake it in to the r/o system image like CrashXXL and the Moto X. An even better way is to be done with Motorola LOL.
Click to expand...
Click to collapse
.... Reboot is hold power on X, Ultra & newer
Ok. :good:

I think I've just successfully extracted a modified 6-7.2 system image for flashing back. This should be interesting.

larsdennert said:
I think I've just successfully extracted a modified 6-7.2 system image for flashing back. This should be interesting.
Click to expand...
Click to collapse
you had my curiosity, now you have my attention.

See next post

Save for pics
used here

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

One Click Root For Moto G5 Plus?

Hello,
Recently, I purchased the G5 Plus & am looking to just 1 click root it for the time being. I've seen a lot on Towelroot but can't find any working downloads or further information regarding it.
Does anyone use it & if so, how is it?
Thank you!

Dyke67ny said:
Hello,
Recently, I purchased the G5 Plus & am looking to just 1 click root it for the time being. I've seen a lot on Towelroot but can't find any working downloads or further information regarding it.
Does anyone use it & if so, how is it?
Thank you!
Click to expand...
Click to collapse
I wouldent go anywhere near it do u not have a PC ?

joeeboogz said:
I wouldent go anywhere near it do u not have a PC ?
Click to expand...
Click to collapse
Yes, I have a computer but like I had mentioned previously, I had read of numerous complaints of wifi not working after rooting via the computer connection.

Dyke67ny said:
Yes, I have a computer but like I had mentioned previously, I had read of numerous complaints of wifi not working after rooting via the computer connection.
Click to expand...
Click to collapse
U don't root with computer only flash twrp then flash root with twrp

Dyke67ny said:
Yes, I have a computer but like I had mentioned previously, I had read of numerous complaints of wifi not working after rooting via the computer connection.
Click to expand...
Click to collapse
Back in the beginning of this device, rooting required flashing a patched kernel... if you had a slightly different radio version than the kernel was intended for, this could occur.
This has not been an issue for some time, at least not since Magisk and SuperSU officially support this device now. I would recommend Magisk though.
If you were going to have issues, it would more than likely be with a One-click root method rather than the documented and proven methods of doing it manually.

acejavelin said:
Back in the beginning of this device, rooting required flashing a patched kernel... if you had a slightly different radio version than the kernel was intended for, this could occur.
This has not been an issue for some time, at least not since Magisk and SuperSU officially support this device now. I would recommend Magisk though.
If you were going to have issues, it would more than likely be with a One-click root method rather than the documented and proven methods of doing it manually.
Click to expand...
Click to collapse
I have successfully flashed & rooted the Moto G5 plus via the computer & all is working except I now have a few issues.
1. I receive the following message upon restarting the phone "Your device has been unlocked & cant be trusted message"
2. The camera no longer works as I receive the message "Camera keeps stopping."
3. "ADB Unauthorized" message when trying to connect back to the program.
Are you familiar with any of these issues?
Thank you!
P.S. I rooted using the "Moto G5 Toolkit"

acejavelin said:
Back in the beginning of this device, rooting required flashing a patched kernel... if you had a slightly different radio version than the kernel was intended for, this could occur.
This has not been an issue for some time, at least not since Magisk and SuperSU officially support this device now. I would recommend Magisk though.
If you were going to have issues, it would more than likely be with a One-click root method rather than the documented and proven methods of doing it manually.
Click to expand...
Click to collapse
As I've already rooted the phone using Motorola software, I did read that installing Magisk would fix the camera not working issue. I'm not familiar with this as I had mentioned in the first writing, it's been awhile since I've rooted an android device (last 3 devices I did, 2 required a computer & the other 1 used Z4root <- awhile ago!)
Am grateful for your help!

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.