I may be spoiled because all my previous phones were various versions of Nexus phones (and tablets), all rooted and with various stock and/or other ROMs installed. But Nexus phones were originally designed for developers, easy to root and mod.
Moto G7 is my first non Nexus phone. So what I write may not be unique and perhaps apply to other non-Nexus phones. I don't know.
Despite all my modding I never bricked a phone until I got the Moto G7. And I've read of many others who have hard bricked their Moto phones too. Moto certainly does not want you to root or modify their phones and punishes you if you do.
If you wish to root the G7:
—unlocking the bootloader requires you to first contact and get a code from Moto
—you then get an annoying persistent warning at every boot that tells you this is now an untrusted phone (as if you did not know)
—rooting this phone is fraught with many problems along the way (but it is a new phone with little development)
—if you make the error of later installing an ota update from Moto (even if officially announced on the phone as available and even after unrooting the phone) it can irretrievably brick your phone without warning (as I've done)
That said, the unrooted phone is excellent value despite some problems like occasionally dropping wifi. But in my experience it is not particularly suited for rooting and modding.
Fwiw
(Does anyone know what Moto charges to repair a phone out if warranty?)
maybeme2 said:
I may be spoiled because all my previous phones were various versions of Nexus phones (and tablets), all rooted and with various stock and/or other ROMs installed. But Nexus phones were originally designed for developers, easy to root and mod.
Moto G7 is my first non Nexus phone. So what I write may not be unique and perhaps apply to other non-Nexus phones. I don't know.
Despite all my modding I never bricked a phone until I got the Moto G7. And I've read of many others who have hard bricked their Moto phones too. Moto certainly does not want you to root or modify their phones and punishes you if you do.
If you wish to root the G7:
—unlocking the bootloader requires you to first contact and get a code from Moto
—you then get an annoying persistent warning at every boot that tells you this is now an untrusted phone (as if you did not know)
—rooting this phone is fraught with many problems along the way (but it is a new phone with little development)
—if you make the error of later installing an ota update from Moto (even if officially announced on the phone as available and even after unrooting the phone) it can irretrievably brick your phone without warning (as I've done)
That said, the unrooted phone is excellent value despite some problems like occasionally dropping wifi. But in my experience it is not particularly suited for rooting and modding.
Fwiw
(Does anyone know what Moto charges to repair a phone out if warranty?)
Click to expand...
Click to collapse
I bought mine used but mint xt1962-1 on eBay for $110. Prob $150 for repair by Moto. Blankflash is avail on Tele$ram for qld 9008 brick
maybeme2 said:
I may be spoiled because all my previous phones were various versions of Nexus phones (and tablets), all rooted and with various stock and/or other ROMs installed. But Nexus phones were originally designed for developers, easy to root and mod.
Moto G7 is my first non Nexus phone. So what I write may not be unique and perhaps apply to other non-Nexus phones. I don't know.
Despite all my modding I never bricked a phone until I got the Moto G7. And I've read of many others who have hard bricked their Moto phones too. Moto certainly does not want you to root or modify their phones and punishes you if you do.
If you wish to root the G7:
—unlocking the bootloader requires you to first contact and get a code from Moto
—you then get an annoying persistent warning at every boot that tells you this is now an untrusted phone (as if you did not know)
—rooting this phone is fraught with many problems along the way (but it is a new phone with little development)
—if you make the error of later installing an ota update from Moto (even if officially announced on the phone as available and even after unrooting the phone) it can irretrievably brick your phone without warning (as I've done)
That said, the unrooted phone is excellent value despite some problems like occasionally dropping wifi. But in my experience it is not particularly suited for rooting and modding.
Fwiw
(Does anyone know what Moto charges to repair a phone out if warranty?)
Click to expand...
Click to collapse
Agreed. The reasons you cite are probably why there is so little development activity on this device.
A big THANK YOU to the TWRP and LineageOS teams for the work they have done on the G7.
I cannot agree more! A huge thank you to the few developers who have helped us, including Alberto97 who gave us the unofficial TWRP early on, the twrp team who recently provided an official version, and the few brave helpers who helped us in XDA.
But, one problem non-expert users face when seeking advice by 'searching first' (as recommended) instead of asking 'again' in the threads is the *outdated advice* found. Take for example something as common as how to root the Moto G7. Advice found by searching for rooting advice include:
If your phone channel is "US Retail", download RETUS (retail US) on pc.
Copy the image to your phone and use Magisk to patch the image. After that, copy the output image to your host computer.
(This spawned numerous queries of 'how do you use Magisk to patch the.....)
Now turn your phone off, press and hold power + volume down to enter bootloader, connect your phone to host computer, and enter
fastboot flash boot
Press space once and drag and drop the output image file to command window.
If everything goes well, restart the phone and confirm it is rooted with Magisk
Click to expand...
Click to collapse
Rather complicated! Actually rooting the Moto G7 with an unlocked bootloader is as simple as:
—install Magisk Manager and use it to download Magisk zip.
—in TWRP, install Magisk zip
That will root the phone.
(besides, many versions of Magisk would patch boot.IMG in ways that don't work correctly for the G7)
I don't know that there is much that can be done about outdated or incorrect advice but it explains the frustration of non-expert users. ?
Tele$ram has much better support these days than XDA
HueyT said:
Tele$ram has much better support these days than XDA
Click to expand...
Click to collapse
You are correct. XDA is were I go first but Telegram solved several of my most stubborn problems.
I had zero problems following the directions in these forums, just my two cents.
HueyT said:
Tele$ram has much better support these days than XDA
Click to expand...
Click to collapse
It absolutely does. XDA is a fantastic library. I see it as a central hub where the best and the brightest Android people congregate. But if you have a question to ask or feel like helping someone who does, TG can fix you up right away.
Instant gratification - it's what's for dinner.
SmilingPerson said:
It absolutely does. XDA is a fantastic library. I see it as a central hub where the best and the brightest Android people congregate. But if you have a question to ask or feel like helping someone who does, TG can fix you up right away.
Instant gratification - it's what's for dinner.
Click to expand...
Click to collapse
You said it perfectly.
Rapid, knowledgeable answers on Telegram.
XDA is a fantastic library — but that means search finds old advice messages that are no longer valid and can create more problems for you.
Related
I was really surprised to learn that LG don't have a bootloader unlocking service like even HTC have done and given that the LG never managed to unlock the bootloader, I'm quite surprised that there wasn't more of a community outcry. What is up with that? Have LG ever spoken of supporting the development community? Is it unlikely that we'll see it happen within the flagship lifetime of our device?
NB: This is discussion topic, it's really not a question/answer topic.
sabret00the said:
I was really surprised to learn that LG don't have a bootloader unlocking service like even HTC have done and given that the LG never managed to unlock the bootloader, I'm quite surprised that there wasn't more of a community outcry. What is up with that? Have LG ever spoken of supporting the development community? Is it unlikely that we'll see it happen within the flagship lifetime of our device?
NB: This is discussion topic, it's really not a question/answer topic.
Click to expand...
Click to collapse
whoa is this 100% correct? if that's the case I will strongly reconsider getting the G3 and will probably go for either M8 or Z2...
Well, coming from an LG Nexus 5, I can tell you that the development community is booming over there. But that's to be expected with a Nexus device. I'm planning on switching from the Nexus 5 to the G3 (ordered yesterday) in an effort to no longer sacrifice hardware in order to get the vanilla Android experience. These days I'd rather give up some of the software advantages in AOSP ROMs in order to get significantly better hardware.
Unfortunately, it's a sacrifice one way or another. And if you buy a phone such as the G3 you must do so expecting that the development for it will take significantly longer and will likely have less options. However, in my opinion the interface/features offered in the latest stock LG interfaces are quite improved and look/feel much better than the interfaces provided by other manufacturers. I don't think I'll have any issue using the stock interface with the LG for many months after coming from the previous 4 generations of Nexus devices.
The vanilla Android experience has gotten quite boring in my opinion and I welcome the features that will be available on LG's stock ROM.
cez10 said:
whoa is this 100% correct? if that's the case I will strongly reconsider getting the G3 and will probably go for either M8 or Z2...
Click to expand...
Click to collapse
Sadly yes, it's something I should've looked into in the six months of waiting for this phone. But it's sadly the case. Even on the G2, they couldn't unlock the bootloader and instead had to bypass it.
sn0warmy said:
Well, coming from an LG Nexus 5, I can tell you that the development community is booming over there. But that's to be expected with a Nexus device. I'm planning on switching from the Nexus 5 to the G3 (ordered yesterday) in an effort to no longer sacrifice hardware in order to get the vanilla Android experience. These days I'd rather give up some of the software advantages in AOSP ROMs in order to get significantly better hardware.
Unfortunately, it's a sacrifice one way or another. And if you buy a phone such as the G3 you must do so expecting that the development for it will take significantly longer and will likely have less options. However, in my opinion the interface/features offered in the latest stock LG interfaces are quite improved and look/feel much better than the interfaces provided by other manufacturers. I don't think I'll have any issue using the stock interface with the LG for many months after coming from the previous 4 generations of Nexus devices.
The vanilla Android experience has gotten quite boring in my opinion and I welcome the features that will be available on LG's stock ROM.
Click to expand...
Click to collapse
If you have the patience, I'd recommend waiting a little while to see if they announce a GPe of the G3. That could provide you with the best of both worlds.
Development will improve for sure - the phone has only been out less than a week (D855) with most people still not having received their devices yet and is not even released in the US. It seems the Korean models have shipped with an unlocked bootloader (from what I have heard) and as for the D855 no one has yet confirmed it a) it is locked and b) if it can be unlocked.
I have certainly not looked into it yet myself, although if it is locked, unlocking via any "hacking" method, is beyond my knowledge, someone smarter than me will have to tell us how to do that.
Give it time, development is always slow in the first month of a new device (unless its a nexus), and tends ot only pick up after release in the USA.
sabret00the said:
If you have the patience, I'd recommend waiting a little while to see if they announce a GPe of the G3. That could provide you with the best of both worlds.
Click to expand...
Click to collapse
Eh, if they release a GP edition G3 it will still pay to have this one because any AOSP ROMs for the GP edition will be quickly ported over to the non-GP edition anyway. I plan on keeping this phone but will also still be happy if they come out with a GP edition as well so we can get some AOSP source code up and running for this device.
And I'm not worried about the bootloader being locked. Someone ALWAYS finds a way to unlock it rather quickly these days.
Personally, my goal with this phone is to root it to get my DPI settings where I want them and get rid of any bloat that may cause the phone to slow down. If I can manage to accomplish those two things, I'll be happy (and it's already doable). My days of rooting, flashing ROMs, bricking, unbricking, and flashing more ROMs are over. At this point I just want a solid phone that works flawlessly.
Lennyuk said:
Development will improve for sure - the phone has only been out less than a week (D855) with most people still not having received their devices yet and is not even released in the US. It seems the Korean models have shipped with an unlocked bootloader (from what I have heard) and as for the D855 no one has yet confirmed it a) it is locked and b) if it can be unlocked.
I have certainly not looked into it yet myself, although if it is locked, unlocking via any "hacking" method, is beyond my knowledge, someone smarter than me will have to tell us how to do that.
Give it time, development is always slow in the first month of a new device (unless its a nexus), and tends ot only pick up after release in the USA.
Click to expand...
Click to collapse
I'm not so much talking about from the community side, I have faith the community will find an unlock or bypass method. I'm more so talking about from LG's point of view. They don't seem to be supportive hence no official channel to unlock the G2 bootloader despite the G3 launching globally this week.
sabret00the said:
I'm not so much talking about from the community side, I have faith the community will find an unlock or bypass method. I'm more so talking about from LG's point of view. They don't seem to be supportive hence no official channel to unlock the G2 bootloader despite the G3 launching globally this week.
Click to expand...
Click to collapse
Remember it took years to get HTC to provide an unlock tool (and the company nearly going bankrupt!), Moto and Sony were the same - moto becoming better when Google acquired them and Sony nearly gave up making android devices completely before they decided to become more dev friendly.
Basically companies only provide unlock methods as a last resort, when they feel its the only way to improve their sales. LG haven't needed this yet.
There are still plenty of devices where you cannot officially unlock the bootloader, its not just an LG thing.
Lennyuk said:
Remember it took years to get HTC to provide an unlock tool (and the company nearly going bankrupt!), Moto and Sony were the same - moto becoming better when Google acquired them and Sony nearly gave up making android devices completely before they decided to become more dev friendly.
Basically companies only provide unlock methods as a last resort, when they feel its the only way to improve their sales. LG haven't needed this yet.
There are still plenty of devices where you cannot officially unlock the bootloader, its not just an LG thing.
Click to expand...
Click to collapse
I totally hear you, but with the success Sony have enjoyed, you'd hope manufacturers would get involved early on.
Lennyuk said:
and as for the D855 no one has yet confirmed it a) it is locked and b) if it can be unlocked.
I have certainly not looked into it yet myself, although if it is locked, unlocking via any "hacking" method, is beyond my knowledge, someone smarter than me will have to tell us how to do that.
Click to expand...
Click to collapse
Is this something that is easy to check?
Dubhar said:
Is this something that is easy to check?
Click to expand...
Click to collapse
I can't even access the bootloader. Despite turning USB debugging on, I can't get ADB to recognise the phone. I started a thread to check if others have a similar problem.
It's a flagship, I'm not worried about development support. Look at the g2, it got cm support. Plus the LG software looks decent, not too basic like HTC or too intrusive like Samsungs touchwiz
sabret00the said:
I can't even access the bootloader. Despite turning USB debugging on, I can't get ADB to recognise the phone. I started a thread to check if others have a similar problem.
Click to expand...
Click to collapse
I rooted D855 yesterday using ioroot and as a part of the process "adb devices" did show the phone with USB debugging on.
I had to install lg unified driver so windows 8 had a right driver for it.
Heisenberg420 said:
It's a flagship, I'm not worried about development support. Look at the g2, it got cm support. Plus the LG software looks decent, not too basic like HTC or too intrusive like Samsungs touchwiz
Click to expand...
Click to collapse
This thread is about development support from LG. Please read threads before commenting. The G2 you mentioned was given as an example of the lack of support previously provided by LG.
jodvova said:
I rooted D855 yesterday using ioroot and as a part of the process "adb devices" did show the phone with USB debugging on.
I had to install lg unified driver so windows 8 had a right driver for it.
Click to expand...
Click to collapse
Perhaps I need to update my drivers then. Though that's nearly unheard of as I'm on Linux.
If i can atleast root the phone to remove the bloatware, I'll be happy for a little while.
sabret00the said:
This thread is about development support from LG. Please read threads before commenting. The G2 you mentioned was given as an example of the lack of support previously provided by LG.
Perhaps I need to update my drivers then. Though that's nearly unheard of as I'm on Linux.
Click to expand...
Click to collapse
Hm, i've not check on Linux yet, but it is recognised on windows with the right USB drivers installed. Maybe its lacking some udev rule to properly recognise the device?
The LGD855 boots into recovery with adb reboot recovery, but not the bootloader using adb reboot-bootloader its just reboots. I goes into download mode with power+volume up, that about all ive tried.
Slash8915 said:
If i can atleast root the phone to remove the bloatware, I'll be happy for a little while.
Click to expand...
Click to collapse
towelroot worked.
on Win 7 by flashing sphinxrom for d855 and s,k,l :
when i was installing the lg driver, it installed the AndroidNet Sooner Single ADB Interface
i had to change it Android ADB Interface
what the hell the device just came out give it some time
daddioj said:
what the hell the device just came out give it some time
Click to expand...
Click to collapse
What the hell can't you read & understand what OP has said or trying to say? (sorry no offence intended). He isn't talking about the support of the development community to this device(G3), which by the way will certainly pick up from what it is now, but he is talking about LG's support to the development community(being more developer friendly as Sony & HTC).
And even if we talk about how much active Android development this device(& it's variants) will see, then let me tell you that the development activity of this device will(probably) never be as much as you see with other flagship devices like HTC One(M7 & m8), that is because a) HTC is more developer friendly by letting you to unlock the bootloader & thus making easy for developers to port(make) ROMs, recoveries & what not, where as with LG & G2 it is entirely different case(ask any developer involved in G2 development, how difficult it is or was to make a recovery or a ROM for G2 and for common flahers the risk factor of flashing those recoveries & ROMs that much more because all the solutions based on a bypassing solution with many permutations & combinations rather than a fully unlockable bootloader just as with HTC devices and b) they are more popular devices among people(as much successful the G2 was it wasn't sold as many as S4s & S5s or M7s & M8s).
We all hope that LG will follow HTC & Sony in being developer frienly. No doubt they are making beautiful devices like G2 & now G3. But sadly, as one of other member pointed out above, it is at the stage of extinction that a manufacturer tend to be more friendly with developer community.
st_7 said:
What the hell can't you read & understand what OP has said or trying to say? (sorry no offence intended). He isn't talking about the support of the development community to this device(G3), which by the way will certainly pick up from what it is now, but he is talking about LG's support to the development community(being more developer friendly as Sony & HTC).
And even if we talk about how much active Android development this device(& it's variants) will see, then let me tell you that the development activity of this device will(probably) never be as much as you see with other flagship devices like HTC One(M7 & m8), that is because a) HTC is more developer friendly by letting you to unlock the bootloader & thus making easy for developers to port(make) ROMs, recoveries & what not, where as with LG & G2 it is entirely different case(ask any developer involved in G2 development, how difficult it is or was to make a recovery or a ROM for G2 and for common flahers the risk factor of flashing those recoveries & ROMs that much more because all the solutions based on a bypassing solution with many permutations & combinations rather than a fully unlockable bootloader just as with HTC devices and b) they are more popular devices among people(as much successful the G2 was it wasn't sold as many as S4s & S5s or M7s & M8s).
We all hope that LG will follow HTC & Sony in being developer frienly. No doubt they are making beautiful devices like G2 & now G3. But sadly, as one of other member pointed out above, it is at the stage of extinction that a manufacturer tend to be more friendly with developer community.
Click to expand...
Click to collapse
i am Guilty of not reading the whole Thread
While I wait for the arrival of my MXP I have some questions for the community so that I can hit the ground running. First thing, I'd like to unlock my boot loader but I was just curious if there is a way to re-lock it afterwards just in case I need to send in for repairs or something along those lines? Also wondering about VOLTE support. I see some roms that state they have it working but is this a stock feature or do I need to use a custom ROM to get VOLTE to function? Also is there any known method of rooting without unlocking the boot loader just in case re-locking it is not possible? Thanks for the help everyone.
I am coming from a g920a. That phone is torture for someone like me who likes stock Android and rooted devices. Probably the worst phone I have ever had. Can't wait to get my hands on my MXP and leaves this piece of junk behind!
I'm on Verizon and I can confirm it supports advanced calling, which is VoLTE as far as I know but it might require turning it on at the provider level.
Sent from my XT1575 using Tapatalk
I haven't messed with VoLTE yet so I can't answer those questions, but as for your others: The bootloader can be relocked, but the unlock method involves submitting an unlock request code to motorola, and they immediately email you an unlock key, along with a warning about voiding your warranty, so even relocking it does not unvoid your warranty. HOWEVER, it only voids your warranty for software issues. If it's a hardware problem unrelated to the bootloader being unlocked, they'll still handle it, and accidental drops and things are still covered if you buy an accidental damage warrenty. Also, as far as I know there is still no way to root without unlocking the bootloader.
10 characters
squallz506 said:
Volte is only available on stock roms.
Click to expand...
Click to collapse
I thought this had been fixed on AICP based ROMS?
Sent from my XT1575 using Tapatalk
countryfolk07 said:
I thought this had been fixed on AICP based ROMS?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Whoops, yeah I guess they fixed it down the line. Sorry, I've been enjoying stock+xposed too much to follow custom development.
Edit: also root without bootloader unlock will likely never happen. We have a root method already, so there's no incentive to find another method.
The answer you seek was right in the first page of this forum....
http://forum.xda-developers.com/moto-x-style/general/moto-x-style-how-to-unlock-bootloader-t3192140
That being said, I would consider waiting until after Marshmallow drops before you unlock your bootloader so as not to interfere with any OTA's. Conventional wisdom is that it is coming within the next few weeks as the "test drive" has already started and a "soak test" should follow shortly.
yeah i know it can be unlocked I already read that post. I would not have gotten this phone if the boot loader was not un-lockable. That's the whole reason I am moving away from my AT&T Galaxy s6. I was just trying to clarify if re-locking made any difference as far as the warranty is concerned. I appreciate the answers guys. Just trying to determine if I should keep it stock or use a custom ROM out of the box. Sounds like I will go stock for the time being. Now as far as unlocked boot loaders interfering with OTA's? Is this really a thing? And wouldn't somebody just post the OTA image on the forums when its ready anyway?
timde9 said:
yeah i know it can be unlocked I already read that post. I would not have gotten this phone if the boot loader was not un-lockable. That's the whole reason I am moving away from my AT&T Galaxy s6. I was just trying to clarify if re-locking made any difference as far as the warranty is concerned. I appreciate the answers guys. Just trying to determine if I should keep it stock or use a custom ROM out of the box. Sounds like I will go stock for the time being. Now as far as unlocked boot loaders interfering with OTA's? Is this really a thing? And wouldn't somebody just post the OTA image on the forums when its ready anyway?
Click to expand...
Click to collapse
Well as to it being a thing, I certainly can't say for sure. But what reason is there to unlock the bootloader if you're not going to root? And once you do that, you almost certainly will not get OTA's. What am I missing? Is there another reason you are looking to unlock?
The one thing I don't know is if there a some type of a "tamper flag" that would require something like triangle away.
You don't think you could just do a fastboot oem lock?
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
timde9 said:
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
Click to expand...
Click to collapse
I'd still recommend waiting at least a couple of weeks to see if Marshmallow shows up!
I'm coming to the MXPE from a OnePlus One which I have to say was one of the funnest phones I've ever owned. I wasiunlocked, rooted and flashing CM12.1 nightlies about twice a week.
I thought I would miss it, but so far so good on the MXPE without rooting. We'll have to see what happens after MM drops. I'd like to get it rooted, but I haven't done nearly the amount of modding you've done.
Good luck with your phone. I can honestly tell you it's a really nice device!
While its tempting to wait for marshmallow to show I cannot live without root any longer. I have already been without it for months because of this damn s6. I'm sure someone will upload the OTA as soon as it's available so I'll just flash it when the time comes.
timde9 said:
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
Click to expand...
Click to collapse
Well if you're an xposed user you should root immediately with no concern about the 6.0 OTA, since xposed doesn't work on 6.0. I'm not moving to 6.0, myself, until xposed is released for it. I use xposed modules everyday and am not giving it up, not even for doze mode.
That's kinda how I am feeling as well. I can achieve similar results to doze with the xposed app amplify with enough tweaking so its not a big deal.
Hey Moto G users
I'm attempting to email Motorola asking them to release the blankflash files as I amongst many others are facing hard bricked phones.
To cut a long story short, one of my Moto G phones the Moto G 2014 (XT1072 aka Thea) worked fine and then suddenly it decided to not boot up (infinite boot animation screen). I sent it to Motorola and they sent it on to a repair company. I had an email from the repair company saying the phone had been rooted, which clearly it wasn't as the bootloader was still locked. Of course the method I have always rooted phones is via a custom recovery which means an unlocked bootloader is required.
Eventually the phone came back to me and they refused to touch the phone any longer. As the repair company didn't care from this point I thought about unlocking the bootloader. However, that didn't actually work as there was a message on the bootloader screen displaying 'Enable OEM Unlock in developer options'. This was impossible as I already knew the phone wouldn't boot and the only way to unlock the bootloader was to enable the option in the developer settings within the OS.
After playing around with some clear cache and formatting commands (which I obviously tried before I sent the phone off) via fastboot and an attempted bootloader unlock command (not done before until received back from the repair company), miraculously the phone did boot up and I was able to do an OTA update to Android 6 (Marshmallow). I did however keep the bootloader unlocked as everything seemed to run fine with the new update. After 4 days use of my phone the phone repeated apps crashing and eventually the infinite boot animation came back. From here I decided to unlock the bootloader and re-flash a stock ROM for this phone. The 5.0.2 ROM worked and I tried an OTA update to 6.0, the phone powered off and now the phone no longer boots and the bootloader is non-existent.
All I'm going to say is the Moto G series of phones are far one of the most popular, cheap, powerful, bargain phones on the market and it is a shame for them to die off never to be used again when bootloader corruptions occur. I'm going to email Motorola UK and share this thread with them showing a poll of users that also would like access to the blankflash files so we can start our phones on a clean slate. My phone may be a hardware issue but I want to at least give it another attempt by re-partitioning the phone and re-flashing it.
Thanks for reading
Will
This is the email I've sent to Motorola. I have also copied in the URL for this thread so they can see how many people vote on the poll. So if you are a Moto G user and have a phone sitting around you would like to bring back to life please vote.
Amongst other Moto G users, we all love our phones for the amazing low price yet still powerful performance. Problem is many of us like to improve the phone by removing bloatware apps and customising the GUI or even installing custom ROM's.
In my case my phone was claimed to have been rooted by your repair company which was lies, and now that nothing can be done with the phone I've attempted to fix the ROM myself. However, the bootloader has decided to break entirely and without the correct software tools I have a £150 phone sitting around doing nothing that could be used.
I have created a thread on the XDA Developers forum with a poll showing the amount of users also requesting you to release the blankflash files. http://forum.xda-developers.com/moto-g/general/requesting-blankflash-files-motorolla-t3350441
I hope you understand the frustration we have when you hold such as good phone back. The Moto G is really great phone, but for the Android enthusiasts such as myself who want to run Android to its full potential (the beauty of being an Open-source OS), sometimes problems will occur and we need the tools to start that clean slate. This is why we need these tools to return the phone back to a 'working' state so we can try again.
It is not just the Moto G that is popular. The entire Moto series have become a well-known icon of phones, and it's what has brought Motorola back as that great phone company. All of the Moto series phones are constantly being customised by Android enthusiasts so please release the software tools to the public so we can keep our phones going.
N.B Please allow the poll to populate as it has only just been created.
Many thanks
Will
Click to expand...
Click to collapse
Just for the record, hard-bricks have also occurred for a small number of users while applying an official OTA update on Bootloader locked phones. Down-graders are not the only people vulnerable.
I would be amazed if you received any response at all from them. No offense, but I'm sure they don't care in the slightest. ?
Sent from my XT1045 using Tapatalk
AtomicFizzle said:
I would be amazed if you received any response at all from them. No offense, but I'm sure they don't care in the slightest. ?
Sent from my XT1045 using Tapatalk
Click to expand...
Click to collapse
True. But I thought I'd try.
Sent from my Nexus 6P using Tapatalk
DUCK you LENOVO
i hope motorola give our devices a life one more
I've been reading the various rooting threads for a couple of days and overall the process seems pretty complicated with many different Nokia 6 versions, and different tools to use, etc.
Is there a way to get root with just the stock bootloader? I only want to do a few sudo operations once in a while, not flash any ROMs. Is this possible somehow? I'm using TA-1003 with 8.0.0 + April security update.
Thanks
leekohlbradley said:
I've been reading the various rooting threads for a couple of days and overall the process seems pretty complicated with many different Nokia 6 versions, and different tools to use, etc.
Is there a way to get root with just the stock bootloader? I only want to do a few sudo operations once in a while, not flash any ROMs. Is this possible somehow? I'm using TA-1003 with 8.0.0 + April security update.
Thanks
Click to expand...
Click to collapse
Your best bet is to return the phone. Nokia has made a really, really bad bet by locking the boot loader. I think that by getting burnt by windows, they decided to jump back into the frying pan again. They don't understand what "OPEN SOURCE SOFTWARE" is. If they had a clue, they would not lock the boot loader. I returned mine because there will not be any active development or roms. I wanted the phone so I could root it, like you, and then unlock the sound features from the sound chip. So, don't bother rooting the phone, just return it or keep it stock.
In a year or two, Nokia will flop or get the idea that they want active development so people will buy their phones. It is a bad way to enter the market.
In principle I agree but I've used the phone for almost a year lol and sadly the power user community is really very small and so there's not much motivation for Nokia to make open phones. This seems especially true to me, since they're offering the phone as an Amazon prime adware phone, for example, so there is in fact a motivation to not open the phone, since it might let users remove the adware from their subsidized hardware... My 2mBTC
If Verizon users are still intrested, just take a look here:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
This guy J4NN is a genius!
Maybe for a bounty he will do it for your device. ?
Inerent said:
If Verizon users are still intrested, just take a look here:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
This guy J4NN is a genius!
Maybe for a bounty he will do it for your device.
Click to expand...
Click to collapse
I got a PM about Temp root for Verizon Google Pixel 2 XL, I guess it was due to this post of you, @Inerent.
It seems that instead of exchanging PMs, it would be better to post it here, to clarify the situation.
Hopefully this is ok with @trabadura, who contacted me.
trabadura said:
j4nn said:
trabadura said:
Hi j4nn, i see your post in xda for temp root Sony XZ1c with Snapdragon 835 and I figured you could help us for temp root Verizon Google Pixel 2 Xl for Unlock Bootloader?
Click to expand...
Click to collapse
Hi, I am not sure about that - I do not have that phone and cannot get/borrow it for testing either.
Do you know if it is possible to downgrade it's firmware?
Can you point me to earliest fw for download that it can be downgraded to?
What exactly the problem is - bootloader is not possible to unlock because Verizon (is it a mobile network operator?) disabled bootloader unlock possibility while on general not Verizon variant google allows it?
Is it also sim locked to Verizon operator only?
And how do you know that getting temp root would help you?
Click to expand...
Click to collapse
Hi, аs far as I know, it can not downgrade firmware with locked bootloader. With unlocked bootloader no problem.
The problem is in mobile operator. They lock option "OEM Unlock" (stay grayed out) in developer option. In general not Verizon variant no problem option is active and no problem to unlock bootloader. No sim locked only bootloader. Тhere is a lot of writing about the topic I can give a few links in the forum.
Links:
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
Click to expand...
Click to collapse
I am sorry, but in my opinion, you are out of luck.
At least if google/verizon delivers FOTA updates and most users accept them instead of staying at the version they bought the phone with.
You could get temp root only with some completely new not fixed kernel vulnerability which would not get patched for longer period of time and that's not happening very often.
If someone starts working on an exploit while most users upgrade in short time closing the bug being worked on, it does not make sense to put an effort into it.
To consider porting my work for other targets, you need to make sure you can run kernel which is still vulnerable to CVE-2017-7533 (race between inotify and rename) and few other CVEs that are needed to overcome android oreo mitigations. Google has patched the mentioned CVE which is the primary one with 2017-12-05 security patch level.
How many users do you think stay on older patch level than that? And would continue staying on it?
I am afraid nobody would help you no matter how much you promise with the bounty.
And so you know, working on it, only because of the bounty mostly is not worth it - at least in my case if I compare the lost time and what is promised in xperia xz1 bounty thread I would be better working any low paid job. That means if I did not want to get it done for myself, I would not work on it!
And even though Google Pixel 2 XL bounty is lot higher, the difficulty (due to no downgrade possibility) is extremely high and gets higher with each update.
I am afraid you need to get used to the fact that there never be a root for it, I am sorry.
You all should have probably bought the open (not Verizon locked) variant instead or be satisfied with the product as bought (I guess it must have been a great deal, right?).
Or at least educate all users here not to allow any upgrade at all since beginning (if that's even possible to disable the updates).
j4nn said:
I got a PM about Temp root for Verizon Google Pixel 2 XL, I guess it was due to this post of you, @Inerent.
It seems that instead of exchanging PMs, it would be better to post it here, to clarify the situation.
Hopefully this is ok with @trabadura, who contacted me.
I am sorry, but in my opinion, you are out of luck.
At least if google/verizon delivers FOTA updates and most users accept them instead of staying at the version they bought the phone with.
You could get temp root only with some completely new not fixed kernel vulnerability which would not get patched for longer period of time and that's not happening very often.
If someone starts working on an exploit while most users upgrade in short time closing the bug being worked on, it does not make sense to put an effort into it.
To consider porting my work for other targets, you need to make sure you can run kernel which is still vulnerable to CVE-2017-7533 (race between inotify and rename) and few other CVEs that are needed to overcome android oreo mitigations. Google has patched the mentioned CVE which is the primary one with 2017-12-05 security patch level.
How many users do you think stay on older patch level than that? And would continue staying on it?
I am afraid nobody would help you no matter how much you promise with the bounty.
And so you know, working on it, only because of the bounty mostly is not worth it - at least in my case if I compare the lost time and what is promised in xperia xz1 bounty thread I would be better working any low paid job. That means if I did not want to get it done for myself, I would not work on it!
And even though Google Pixel 2 XL bounty is lot higher, the difficulty (due to no downgrade possibility) is extremely high and gets higher with each update.
I am afraid you need to get used to the fact that there never be a root for it, I am sorry.
You all should have probably bought the open (not Verizon locked) variant instead or be satisfied with the product as bought (I guess it must have been a great deal, right?).
Or at least educate all users here not to allow any upgrade at all since beginning (if that's even possible to disable the updates).
Click to expand...
Click to collapse
You are completely right. And that is the difference between Android and iPhone communities. Every Android user prefer to stay aside of this problem, naively thinking that they would not be affected. In Oreo Google has already put all the Root CAs into the System storage. So Nobody knows what kind of data the phone uploads every day to 3rd party servers. Verizon is just an example there are many companies who do the same. iPhone community is great because everybody know that some day under certain circumstances they can lost their JB. I hope one day some mid-range iOS developer will buy Android phone and start developing a great root tools. Sure it will be quite easy because all the source code is available.
I appreciate your work. Thank you and good luck.
First they came for the socialists, and I did not speak out—
Because I was not a socialist.
Then they came for the trade unionists, and I did not speak out—
Because I was not a trade unionist.
Then they came for the Jews, and I did not speak out—
Because I was not a Jew.
Then they came for me—and there was no one left to speak for me.