Related
Hi guys... I have just returned to android after joining the other side. My last android device was an htc hero which was rooted and running a custom rom, but that was a very long time ago and android has moved on so much since then. I recently purchased a motorola atrix which was locked to t-mobile uk, I used an unlocking code to use on the o2 network. I then rooted the device. I have looked through the many many posts of how to unlock my bootloader and usually I wouldnt have any issues but many of the download links are down, so I read another method and the more I read the more I doubt myself.
please dont flame me, if somebody could spare a few moments i'd be very grateful...
my device details are as follows...
Model - MB860
Android Version - 2.3.4
system version - 45.31.2MB860.T-Mobile.en.GB
Baseband version - N_01.100.00R
Build number - 4.5.2A-74_OLE-31.2
Also, any good rom suggestions? I drive for a living so I use co-pilot sat nav alot, I also love taking pics and videos, so would like a rom that has working camera and video recording....
thanks again...
I am not certain with what your issues are with following the method in the sticky at the top of this thread. If some download is not working, seach around for the same file. It is all about getting the unlocked bootloader to flash.
AFAIK, the only way to unlock a moto phone is to flash a moto signed unlocked bootloader.
I do wonder if just burning the fuse would do the trick, but do not know either if it can be done or if it works. But I seriously doubt you want to go there.
Sorry guys.... The sticky somehow got linked to my question.... please ignore the sticky!!! I have no idea how that happened.
Ok, I managed to sort everything out... I'm running Nottach Trix4g custom rom.
But I did notice something whilst running rsd lite, I made sure that I followed the instructions exactly, my phone was detected and started to unlock my bootloader, all files extracted and for some reason on the last section my phone rebooted but the operation had not complete on rsd lite. So I tried again with the same thing happening, the device would reboot with no 'UNLOCKED' on the boot screen. After the second time I was alittle worried so checked the phone was working properly and noticed a decrease in performance. I then checked available memory and it was at 78mb free, even after rebooting with 200mb used!!!
Basically I ended up unlocking the bootloader via command prompt and it worked first time, I've made a back up of my stock rom and then went ahead and installed the nottach Trix4g custom rom, this rom has the ramfix as an option during install.
So right now after checking my running services I have 440mb free with 222mb used, does that seem right?
After I installed the new rom I let it settle for around 30mins before using the device.
It seems ok but what do the more experienced users think, have I messed something up?
yup sounds about right thats a good rom too
Sent from my MB860 using Tapatalk
Really happy with the rom too. If i was to change roms would I have to re-apply the ramfix?
thanks for your help.
hope this helped!!
depends if you have bell atrix AT&T atrix or international. all international users have to flsh the ramfix when needed. i have att atrix so i can flash either flaux123 clesmyns or cm9 kernels well depending on the rom. cm9 uses cm9 or flauxes123 kernel and gingerbread uses gb kernels.
oh ok, I see..... im from the uk so I had to flash ramfix. Does that mean that even if I was to flash a stock rom that I'd still have to flash ramfix, or would it be back to normal? I suppose what im trying to say is, using the method I used to unlock my bootloader have I damaged the ram in anyway?
Whats the best ics custom rom available at the moment?
Thanks again....
No by unlocking the boot loader you didn't mess up anything. You just voided your warranty. Now if you were to put stock rom u don't have to flash ram fix. If it boots up and passed the boot logo then you're good. But if it stays stuck on boot logo for more than 2 minutes then logically u need to apply ram fix. U can flash any ATRIX rom. If it gets stuck then u need ram fix. And best ics rom as from right now will be the one from jokerjax.com.
sent from "ATRIX-BEAST" using voice commands.
thanks guys, I really appreciate your help. All seems to be running surprisingly well with the new rom.
now to try cm9.....
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Leraeniesh said:
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Click to expand...
Click to collapse
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Eclipse00 said:
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Click to expand...
Click to collapse
is the CWM 100% operational ?
Last time I checked it was half baked still.
Give the Devs some time. =) atleast we got KK officially =) Loving it.
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
j27h said:
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
Click to expand...
Click to collapse
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Leraeniesh said:
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here is the forum he was using to post that update. I sent him a PM letting him know about the resolution issue(XHDPI).
http://forum.xda-developers.com/showthread.php?p=53245960
It's here
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
Just used it this morning to install root on 4.4.2. Worked fine.
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
I'm assuming you have an unlocked bootloader. I had that same issue after the initial upgrade to the new OTA and bootloader. I ran through a few steps like unlocking the bootloader again (may have not done anything), I used a pre-rooted RSD flash of stock and I used the ADB method of installing the recovery instead of using fastboot.
To use the adb method I downloaded the batman 1.2 recovery tool, just renamed the version of TWRP (in this case TWRP2710-RAZR_M-KITKAT.img) to TWRP.IMG and placed it in the root of the batman folder, then I ran the flash TWRP recovery option. Note that the batman tool was designed for older firmware and you should probably not run any other functions on it if you are on the new firmware.
Batman 1.2
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
You need to remove or rename,
Code:
/system/[COLOR="Red"][B][I]recovery-from-boot[/I][/B][/COLOR]
Thanks I will give this a try. I may hold off for now I read there was a possible update coming. I would guess you would need the stock recovery to get the update to work.
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
ezdi said:
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
Click to expand...
Click to collapse
Two weeks at best, considering it's the 4.4.3, which is probably the last update we'll get from Moto, unless a miracle occurs and we're given the 4.5 or 5.0, which shouldn't land until at least 5 months after it's release (if it does release next week).
I can't believe they're already planning another update. Sitting on jb we were all pretty sure that the kk update would be the last
Sent from my DROID RAZR M using Tapatalk
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
GnatGoSplat said:
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
Click to expand...
Click to collapse
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Sent from my DROID RAZR M using Tapatalk
thewraith420 said:
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Click to expand...
Click to collapse
Yeah, I'm hoping the update is because there were bugs that were too big to ignore, but Verizon forcing them to patch the exploit is probably more likely. Definitely a shame to close it on a 2yr old phone. IMO, we need some kind of consumer protection law that forces VZ and AT&T to allow BL unlocks once a device reaches EOL. It would even be better for the environment as it does keep devices relevant for much longer and less likely to end up in a toxic Chinese burn pile.
I feel like the reason we got the exploit back was a Moto dev saw the device is reaching EOL and decided it wouldn't hurt to help the community by putting the exploit back in, because it would almost have to have been deliberate.
Well it's actually lucky that 4.4.4 didn't patch towelroot, so root, I THINK, will stay, but for the bootloader unlock, it's better now than wait with Verizon.
Hi everyone, I have a nexus 6p still running 6.0.1 with an unlocked bootloader, I got the notification for the 7.0 update, but I don't know if I can install it with the bootloader unlocked. Is it possible or do I have to lock the bootloader first?
Yes, bootloader can be unlocked. If you have modified system in any way, it may not apply the update though. I.E. if you are using twrp or you changed any system files.
Radit26 said:
Hi everyone, I have a nexus 6p still running 6.0.1 with an unlocked bootloader, I got the notification for the 7.0 update, but I don't know if I can install it with the bootloader unlocked. Is it possible or do I have to lock the bootloader first?
Click to expand...
Click to collapse
My bootloader has been unlocked since the day I got my 6P. I restored back to stock MM today, flashed the newest TWRP and joined the android beta pgm to get the N OTA. Worked like a charm, no issues whatsoever.
jackpollard said:
My bootloader has been unlocked since the day I got my 6P. I restored back to stock MM today, flashed the newest TWRP and joined the android beta pgm to get the N OTA. Worked like a charm, no issues whatsoever.
Click to expand...
Click to collapse
Just so I can make sure I pass on correct info for the future, the OTA installed by itself with twrp installed? Or did you push it via fast boot?
I went a different route and installed Nougat via a ROM (tried both Stock+ and digital Hugh's versions), so for me it was hardly any different than installing any other ROM.
helioXverse said:
Just so I can make sure I pass on correct info for the future, the OTA installed by itself with twrp installed? Or did you push it via fast boot?
I went a different route and installed Nougat via a ROM (tried both Stock+ and digital Hugh's versions), so for me it was hardly any different than installing any other ROM.
Click to expand...
Click to collapse
Yes to the OTA installed with twrp installed, it rebooted into the twrp recovery and then did some patches, etc. rebooted updated apps and hello nougat! I did have to reflash twrp after I booted back up, it did wipe it out.
I was debating about flashing digital Hugh's rom, how do you like it so far?
Good to know, thanks.
I've used aosp based Roms for so long, stock took a little getting used to. But I don't know if I will be going back to aosp now.
Digitalhigh's ROM is very smooth, and it's setup "out of the box" to allow root and android pay (albeit you have to toggle root off when you want to use AP). That's one feature I've always missed out on W aosp.
That said, there are a couple small issues some people are experiencing, clock updating the time only every 3-5min, and some having issues with vipermod not working system wide. I haven't experienced any of those. Plus he's already working on an update to allow for centered status bar clock as well as some other features.
I personally recommend giving it a shot if you want Nougat, worst that happens is you have to nandroid restore a backup.
*Edit* and he already has the night mode built into it, as well as the new nexus launcher if I'm not mistake.
Wouldn't let me attach this in an edit for some reason. That's with 4 hours screen on time, only reason you see that little charging bump is i was backing up a few files to my PC.
Thanks for the answers, just tried to update and everything was installed :good:
helioXverse said:
Good to know, thanks.
I've used aosp based Roms for so long, stock took a little getting used to.....
Click to expand...
Click to collapse
Thanks for the detailed reply, you may have pushed me over the edge and I may give it a try. Ive been on Benzo rom across my last 3 phones and got used to all the goodies. But using 7 the last day I find it; very fast, been a fan of Pay when it worked with systemless, can't comment on battery yet but seems decent. I may give it a day or 2 and flash digitialhighs rom, it seems like it gives me Pay with minor hassle and is close to stock. Again thanks.
My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel
No! Suit yourself, but I would simply upgrade to N4F26I and enjoy your phone. There is nothing wrong with running stock and you have a good kernel. Viva! Saúde!
Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
rcoliveirajr said:
My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel
Click to expand...
Click to collapse
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..
rcoliveirajr said:
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..
Click to expand...
Click to collapse
CM will be replaced by Lineage OS.
Sent from my Nexus 6P using Tapatalk
Does anyone downgrade to Marshmallow?
Would you guys recommend me to do it?
jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.
Jammol said:
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.
Click to expand...
Click to collapse
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Sent from my Nexus 6 using XDA-Developers Legacy app
CyberpodS2 said:
I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Click to expand...
Click to collapse
Some people have said it has happened to them on MM. Not sure how true it is but who knows.
---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------
jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Lineage IS CM. It literally is only a name change. If you go to the GIT you'll see, or even go to the CM thread. It's just the company and name is dead. All the source files were moved by maintainers and it was all rebranded to be called LineageOS. They just no longer have the pockets to run things the way it used to be.
And as far as custom Roms go, they are all the same. They are all either based on AOSP, or the Stock(Google) firmware of the device. They all carry the same features that they renamed to whatever the name of the ROM is. That has always been the problem with stock Android devices.
I have a 6p that does not know Nougat yet, I'll stick to MM until further clarification.
No issues - latest MM, SuperSU 2.79, Xposed v87 and Franco v28.
jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Do some more research before releasing false information. Lineage OS isnt starting from scratch lol. Do you follow their threads or github? Cyanogen 7 was my first ROM on HTC Inspire...and it was BEASTMODE. They were pioneers on a digital frontier, and in my book OG. The name may be dead but Lineage is here to stay and they have all the OPENSOURCE code. Long live Cyanogen!!!!!
Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.
Uggg
Sent from my Nexus 6 using XDA-Developers Legacy app
Bad news, and there isnt official answer from Google
I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it
seand88 said:
I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it
Click to expand...
Click to collapse
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
dogmatism said:
Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.
Click to expand...
Click to collapse
Hopefully your phone was still under warranty. Sounds like you got a lemon.
jhs39 said:
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
Sorry for the late reply. I was not doing anything at all. It was sitting in a cup holder as I was driving and thats when I noticed it looping.
Click to expand...
Click to collapse
CyberpodS2 said:
Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
i do not understand what this thread is supposed to be about, are you people saying that a stock nexus 6p with no kernel mods or custom rom can just spontaneous go into a boot loop? and now people saying it can happen on MM and it is not just a N issue? or is this only for modded devices? or is it mainy something that ahppens on stock N?
my 6p has major battery issues and drains at about 1% per minute on stock MM, i need to RMA the phone now and it is on MM
i want to root it and install xposed so i do not want N , i found this thread looking to find out if a downgrade from N to MM is possible
so if my phone gets returned to me on N or if they send a new phone to me and it is on N, then am i stuck with N or can i downgrade in back to stock MM?
phone is not modded to root no TWRP no backup will i be able to get on MM if they return my phone on N or send a new one on N?
Hey guys, so I plan on getting this phone within the next month and I want to be prepared to unlock the bootloader and install magisk as soon as I get it. The guides I've looked at just jump right into it without explaining anything. What are the best up-to-date guides for bootloader unlocking and custom recovery installing? Thanks for any help!
EarthboundHero said:
Hey guys, so I plan on getting this phone within the next month and I want to be prepared to unlock the bootloader and install magisk as soon as I get it. The guides I've looked at just jump right into it without explaining anything. What are the best up-to-date guides for bootloader unlocking and custom recovery installing? Thanks for any help!
Click to expand...
Click to collapse
you need to know that there are 3 versions of the phone. A2017 (chinese), A2017G (intl) and A2017U (USA). I don't really know the exact differences, but keep in mind that the A2017U has probably the best support and has the most ROMs and kernels and stuff available. The A2017 comes, from what I've heard, with a recovery in Chinese. And the A2017G has development and stuff but you definitely want to avoid bricking it (DFU mode might need you to disassemble the phone). Besides from that the guides are well written, for example the one I used for my A2017G was okay (from Controllerboy). Everything's explained. If you find something that's not evident send the guide link here and ask.
I just got this phone today too. Man I don't see why anyone's even rooting this... It's working great for me. I spent a couple hours in settings, setting up Nova, and all that, and I'm really amazed by this phone. Stock Antutu and it's scoring 155k! Very fluid phone too. I got scared during delivery, because I started reading horror stories about this phone, and development it seems like there's always something broken or not working correctly. I really really don't see the need to mess with the software one bit! I would recommend sticking with stock just to see how you enjoy it, before taking any risks. I used to be a flashaholic, but after marshmallow, the need isn't really there anymore. Android has become so smooth, rooting has lost most of its novelty. At least that's my opinion.
Reasons to root
JoRocker said:
I just got this phone today too. Man I don't see why anyone's even rooting this... It's working great for me. I spent a couple hours in settings, setting up Nova, and all that, and I'm really amazed by this phone. Stock Antutu and it's scoring 155k! Very fluid phone too. I got scared during delivery, because I started reading horror stories about this phone, and development it seems like there's always something broken or not working correctly. I really really don't see the need to mess with the software one bit! I would recommend sticking with stock just to see how you enjoy it, before taking any risks. I used to be a flashaholic, but after marshmallow, the need isn't really there anymore. Android has become so smooth, rooting has lost most of its novelty. At least that's my opinion.
Click to expand...
Click to collapse
There are a lot of reasons to root it. Maybe you are just used to the Cyanogenmod ROMs ans don't want to use any of the proprietary ROMs and Launchers. XPosed Framework, adblock, VPN, custom CA Certificates and Linux arm with VNC in the background are only some of hundreds of reasons to root your phone.
EarthboundHero said:
Hey guys, so I plan on getting this phone within the next month and I want to be prepared to unlock the bootloader and install magisk as soon as I get it. The guides I've looked at just jump right into it without explaining anything. What are the best up-to-date guides for bootloader unlocking and custom recovery installing? Thanks for any help!
Click to expand...
Click to collapse
No need for any guides just use my toolkit: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
JoRocker said:
I just got this phone today too. Man I don't see why anyone's even rooting this... It's working great for me. I spent a couple hours in settings, setting up Nova, and all that, and I'm really amazed by this phone. Stock Antutu and it's scoring 155k! Very fluid phone too. I got scared during delivery, because I started reading horror stories about this phone, and development it seems like there's always something broken or not working correctly. I really really don't see the need to mess with the software one bit! I would recommend sticking with stock just to see how you enjoy it, before taking any risks. I used to be a flashaholic, but after marshmallow, the need isn't really there anymore. Android has become so smooth, rooting has lost most of its novelty. At least that's my opinion.
Click to expand...
Click to collapse
There are obviously reasons for root, BUT i am with you on this one. I have personally not found a reason to root yet. And that means a lot coming from me, as i am a real ROM-whore and update-slut. The firmware suits my needs perfectly, i have a 2017U with firmware B029 installed. Oh and do check @bkores tookit! It rocks!
bkores said:
No need for any guides just use my toolkit: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Click to expand...
Click to collapse
Hey does your rootkit work with a phone that can't access adb? Like I was looking at the EDL method of returning my Axon 7 to stock for an RMA exchange. I am exchanging it because mtp/quick charge/adb does not work anymore. Fastboot still works.
runderekrun said:
Hey does your rootkit work with a phone that can't access adb? Like I was looking at the EDL method of returning my Axon 7 to stock for an RMA exchange. I am exchanging it because mtp/quick charge/adb does not work anymore. Fastboot still works.
Click to expand...
Click to collapse
The bootloader unlock and restore stock options both use EDL.
runderekrun said:
Hey does your rootkit work with a phone that can't access adb? Like I was looking at the EDL method of returning my Axon 7 to stock for an RMA exchange. I am exchanging it because mtp/quick charge/adb does not work anymore. Fastboot still works.
Click to expand...
Click to collapse
I've had this problem before. It's because I updated an "N" version of Windows without installing the latest media feature pack. If you have an "N" version of Windows, make sure to install the media feature pack.
EarthboundHero said:
I've had this problem before. It's because I updated an "N" version of Windows without installing the latest media feature pack. If you have an "N" version of Windows, make sure to install the media feature pack.
Click to expand...
Click to collapse
I am aware of that issue but this is something else. Quick charge doesn't work at all and adb doesn't either. In fact a buddy of mine plugged his Axon into my computer and it worked just fine so..
I just got this phone today and it came with 6.0.1 MM B29. I am pretty impressed by the features that ZTE has added in to their stock UI. I hear that has gotten better with the N updates.
If I OTA update bone stock to N B25 and decide I miss root, I can go back and downgrade to N B19 via various methods and unlock the bootloader, install TWRP, root, and custom ROM etc?