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
Hi Friends,
Hope you're all having a great new year. So last time I was lurking the S7E forums, we had a leaked Engineering Bootloader that was used to acquire root on all US Snapdragon models, albeit, with a lot performance issues and etc.
I came here to glance as well as all other variant forums for the SD model and now we have Root for every model, with even ROMs being baked like the Echo ROM for Verizon, Sprint, AT&T models, usually the toughest to achieve these things on. I'm trying to read through the forums, but I fear I'm missing the details, that will help me pull the trigger for getting the device or not.
Can one of you very experienced, knowledgeable, and kind members educate me on the latest?
1. Do we have unlocked Bootloader and Root for all US carrier S7Es? How is it done? I use people using Flashfire. So no TWRP?
2. Does this process still trip Knox and render Samsung Pay to never be used again on the device?
3. If I bought the Verizon variant, for example, can I root, unlock Bootloader, and etc, and then return to stock, to return to the store in case I don't like the phone?
4. Xposed Framework working for all models?
Much appreciate your responses, any and all of them in advance! Thanks!
ProFragger said:
Hi Friends,
Hope you're all having a great new year. So last time I was lurking the S7E forums, we had a leaked Engineering Bootloader that was used to acquire root on all US Snapdragon models, albeit, with a lot performance issues and etc.
I came here to glance as well as all other variant forums for the SD model and now we have Root for every model, with even ROMs being baked like the Echo ROM for Verizon, Sprint, AT&T models, usually the toughest to achieve these things on. I'm trying to read through the forums, but I fear I'm missing the details, that will help me pull the trigger for getting the device or not.
Can one of you very experienced, knowledgeable, and kind members educate me on the latest?
1. Do we have unlocked Bootloader and Root for all US carrier S7Es? How is it done? I use people using Flashfire. So no TWRP?
2. Does this process still trip Knox and render Samsung Pay to never be used again on the device?
3. If I bought the Verizon variant, for example, can I root, unlock Bootloader, and etc, and then return to stock, to return to the store in case I don't like the phone?
4. Xposed Framework working for all models?
Much appreciate your responses, any and all of them in advance! Thanks!
Click to expand...
Click to collapse
Absolutely nothing has changed on root (only possible due to ENG kernel) and bootloader unlock (which is not yet possible).
1. No
2. No
3. No
4. No idea about all models. For the t-mobile one, please check: https://forum.xda-developers.com/tmobile-s7-edge/how-to/guide-installing-xposed-framework-t3414718
You can use the search feature in xda for finding out
CravingMender9 said:
Absolutely nothing has changed on root (only possible due to ENG kernel) and bootloader unlock (which is not yet possible).
1. No
2. No
3. No
4. No idea about all models. For the t-mobile one, please check: https://forum.xda-developers.com/tmobile-s7-edge/how-to/guide-installing-xposed-framework-t3414718
You can use the search feature in xda for finding out
Click to expand...
Click to collapse
Hey bud, thanks for getting the ball rolling on these questions. If you could add some more information, I'd appreciate it :
If we still don't have a way to Root or Unlock bootloader, how are these ROMs (Echo, Tek, and other stock ROMs) available with root? And how are these flashed? Are we somehow bypassing the BL by using FlashFire?
Can you also educate me on the U Firmware and why people install it and is it reverseable?
Lastly, if I got a T-Mobile variant for example, installed these ROMs Tek, Echo, etc, can I return to Stock completely and return to T-Mobile, by any chance for them to take it back? Thank you again!
for the t mobile variant, I was able to flash the U firmware and flash back to stock t mobile. NOTE: I did not flash the U bootloader. I kept the T mobile bootloader just be sure I could flash back to stock t mobile(APK1). I'm sure this method would work with other carriers as well. so what ever variant you have, make sure you stay on that BL and only flash the U firmware CSC and AP. As for the CP(modem) I would flash your carriers latest CP file. That's what worked best for me with the U firmware. Currently I'm using the latest nougat BETA
Thank you very much for your response, bud. One last follow up question: Since all the US variants are rooting based on the ENG Kernel, is there really a benefit of getting one variant over another, for rooting or etc purposes?
P. S. May I ask why you flashed the U Firmware? What are the advantages of it? ?
ProFragger said:
Thank you very much for your response, bud. One last follow up question: Since all the US variants are rooting based on the ENG Kernel, is there really a benefit of getting one variant over another, for rooting or etc purposes?
P. S. May I ask why you flashed the U Firmware? What are the advantages of it?
Click to expand...
Click to collapse
The u firmware basically does not include all of the software that is usually included with the phone. For example.. Tmobile with their software on it, Verizon att etc... Makes the phone a bit snappier especially if you were to root. Even tho I hope for a more stable root still. I am rooted at the moment. Wish they didn't recall the note 7 because the root on that was better
ProFragger said:
Hi Friends,
Hope you're all having a great new year. So last time I was lurking the S7E forums, we had a leaked Engineering Bootloader that was used to acquire root on all US Snapdragon models, albeit, with a lot performance issues and etc.
I came here to glance as well as all other variant forums for the SD model and now we have Root for every model, with even ROMs being baked like the Echo ROM for Verizon, Sprint, AT&T models, usually the toughest to achieve these things on. I'm trying to read through the forums, but I fear I'm missing the details, that will help me pull the trigger for getting the device or not.
Can one of you very experienced, knowledgeable, and kind members educate me on the latest?
1. Do we have unlocked Bootloader and Root for all US carrier S7Es? How is it done? I use people using Flashfire. So no TWRP?
2. Does this process still trip Knox and render Samsung Pay to never be used again on the device?
3. If I bought the Verizon variant, for example, can I root, unlock Bootloader, and etc, and then return to stock, to return to the store in case I don't like the phone?
4. Xposed Framework working for all models?
Much appreciate your responses, any and all of them in advance! Thanks!
Click to expand...
Click to collapse
You're confused. At least, you were.
We do not have an "unlocked Bootloader" and we never did. We had an engineering kernel. That engineering kernel allows certain commands that enabled us to acquire root access. But without that kernel, the system (with the original kernel or boot partition) checks for any changes in the /system partition. If any are found it triggers a bootloop. So basically, if you want root we MUST have the engineering kernel. Unless someone else finds another way that's just the way that it is.
Personally, I unrooted and went back to stock. Root was okay at first but with the lack of development, Samsung Pay and the fact that Android 7+ will probably not be seeing root... well... time to accept the fact that Samsung owns the phone even though we bought it. What else can we do?
nitroevo said:
The u firmware basically does not include all of the software that is usually included with the phone. For example.. Tmobile with their software on it, Verizon att etc... Makes the phone a bit snappier especially if you were to root. Even tho I hope for a more stable root still. I am rooted at the moment. Wish they didn't recall the note 7 because the root on that was better
Click to expand...
Click to collapse
Binary100100 said:
You're confused. At least, you were.
We do not have an "unlocked Bootloader" and we never did. We had an engineering kernel. That engineering kernel allows certain commands that enabled us to acquire root access. But without that kernel, the system (with the original kernel or boot partition) checks for any changes in the /system partition. If any are found it triggers a bootloop. So basically, if you want root we MUST have the engineering kernel. Unless someone else finds another way that's just the way that it is.
Personally, I unrooted and went back to stock. Root was okay at first but with the lack of development, Samsung Pay and the fact that Android 7+ will probably not be seeing root... well... time to accept the fact that Samsung owns the phone even though we bought it. What else can we do?
Click to expand...
Click to collapse
Thanks for your helpful responses fellas. I understand root is not perfect, but for some folks like me, Xposed seems to be worth the trouble. For Samsung Pay, I intend to use the Gear S3 one day ?.
Final question, since all US Snapdragon models are using the engineering kernel to root and etc... Is there a benefit of getting one carrier variant, over another? For example, Verizon is usually the cheapest. Is it wise to get that, with the U Firmware, to use on AT&T? Thanks!
ProFragger said:
For Samsung Pay, I intend to use the Gear S3 one day .
Final question, since all US Snapdragon models are using the engineering kernel to root and etc... Is there a benefit of getting one carrier variant, over another? For example, Verizon is usually the cheapest. Is it wise to get that, with the U Firmware, to use on AT&T? Thanks!
Click to expand...
Click to collapse
Let me know if that works out for you then.
I just purchased the S2 Classic (on T-Mobile) and use Samsung Pay quite a bit. But I can tell you that it does open Samsung Pay on the phone and if you are rooted, Samsung Pay will not work at all. So I'm not sure if it will work at all for you even with the S3.
In regards to your other inquiry, I haven't tried the U firmware. I read something about data issues, no wifi calling (which is pretty important to me), no hotspot (which is also really important to me) but I heard that it is really fast. Not sure how much of that is still a problem but you should probably read up on it before doing anything first. But the rooting method is all the same between carriers I believe. All require the engineering kernel and breaks Samsung Pay along with a couple of other apps.
Just make back ups, have a stock firmware available to flash with ODIN just in case and remember that it's almost impossible to brick this device (because we don't have an unlocked bootloader.)
Binary100100 said:
Let me know if that works out for you then.
I just purchased the S2 Classic (on T-Mobile) and use Samsung Pay quite a bit. But I can tell you that it does open Samsung Pay on the phone and if you are rooted, Samsung Pay will not work at all. So I'm not sure if it will work at all for you even with the S3.
In regards to your other inquiry, I haven't tried the U firmware. I read something about data issues, no wifi calling (which is pretty important to me), no hotspot (which is also really important to me) but I heard that it is really fast. Not sure how much of that is still a problem but you should probably read up on it before doing anything first. But the rooting method is all the same between carriers I believe. All require the engineering kernel and breaks Samsung Pay along with a couple of other apps.
Just make back ups, have a stock firmware available to flash with ODIN just in case and remember that it's almost impossible to brick this device (because we don't have an unlocked bootloader.)
Click to expand...
Click to collapse
Thank you again for a helpful post. So the S3 has a dedicated MST/NFC chip in it, that allows for Samsung Pay to work from the watch, it's done through the Gear app. That's what I have read.
About the rest of it, again, curious to see if there is one US variant, superior to another in terms of Root capabilities or bands and radios available and etc? Can anyone confirm this for me?
Thanks!
ProFragger said:
Thank you again for a helpful post. So the S3 has a dedicated MST/NFC chip in it, that allows for Samsung Pay to work from the watch, it's done through the Gear app. That's what I have read.
Click to expand...
Click to collapse
So does the S2.
When I was setting up the Samsung Pay on my watch it said that it had to download an update.
Then I went through the setup process through my phone which was from the Samsung Pay app.
You go to "Add card" on your watch and it opens Samsung Pay on your phone.
You click "Next" and it displays your Samsung account information.
Then it takes you to a screen that says "Setup complete" telling you that you're ready to use it and at the bottom says "Add card"
You do that all from the Samsung Pay app on your phone which leads me to suspect that if you root your phone, you won't be able to use Samsung Pay on your watch.
People on this thread that you have to set it all up first, remove the Samsung Pay app on the phone but leave it on the watch. If it's all done correctly then it should work. Just make sure you get it all set up first.
Next thing that I'm going to try is using my watch in "Standalone" with my phone out of bluetooth or wifi range. See if that still works.
ProFragger said:
About the rest of it, again, curious to see if there is one US variant, superior to another in terms of Root capabilities or bands and radios available and etc? Can anyone confirm this for me?
Thanks!
Click to expand...
Click to collapse
As far as I know, the U firmware permits use of some other bands that aren't normally used. Not sure which ones though.
Binary100100 said:
So does the S2.
When I was setting up the Samsung Pay on my watch it said that it had to download an update.
Then I went through the setup process through my phone which was from the Samsung Pay app.
You go to "Add card" on your watch and it opens Samsung Pay on your phone.
You click "Next" and it displays your Samsung account information.
Then it takes you to a screen that says "Setup complete" telling you that you're ready to use it and at the bottom says "Add card"
You do that all from the Samsung Pay app on your phone which leads me to suspect that if you root your phone, you won't be able to use Samsung Pay on your watch.
People on this thread that you have to set it all up first, remove the Samsung Pay app on the phone but leave it on the watch. If it's all done correctly then it should work. Just make sure you get it all set up first.
Next thing that I'm going to try is using my watch in "Standalone" with my phone out of bluetooth or wifi range. See if that still works.
As far as I know, the U firmware permits use of some other bands that aren't normally used. Not sure which ones though.
Click to expand...
Click to collapse
Thanks for the correction/education on the S2, bud, much appreciated. I wonder if the rooted phone works with the S3, because Samsung has allowed many other non Samsung phones to know work with the S3? But I could be wrong, I thought it was open like that with the S2 as well, no? Looking forward to your testing, hope there is a breakthrough in there! ?
if you want root and customizability and roms, just don't get this phone. you will be very disappointed with the performance once you root and it gets so much worse with Xposed. not worth it at all, you will have better performance and speed from a 4 year old phone that has an unlocked bootloader and strong development. I mean my Nexus 5 (from 2012) had better performance than my rooted S7. it sounds like you do want roms, and if you want roms then AOSP/Cyanogenmod is the way to go. there will probably never be any AOSP or CM ROM on the QC S7/E so you're better off getting an older galaxy model that does have a great development community and unlocked bootloader. or just get a OnePlus or Nexus or something.
xVermicide said:
if you want root and customizability and roms, just don't get this phone. you will be very disappointed with the performance once you root and it gets so much worse with Xposed. not worth it at all, you will have better performance and speed from a 4 year old phone that has an unlocked bootloader and strong development. I mean my Nexus 5 (from 2012) had better performance than my rooted S7. it sounds like you do want roms, and if you want roms then AOSP/Cyanogenmod is the way to go. there will probably never be any AOSP or CM ROM on the QC S7/E so you're better off getting an older galaxy model that does have a great development community and unlocked bootloader. or just get a OnePlus or Nexus or something.
Click to expand...
Click to collapse
Or a Exynos S7.
Binary100100 said:
Or a Exynos S7.
Click to expand...
Click to collapse
exactly this. except for some reason I thought exynos variants are lacking certain bands/features on American networks. could be wrong.
xVermicide said:
if you want root and customizability and roms, just don't get this phone. you will be very disappointed with the performance once you root and it gets so much worse with Xposed. not worth it at all, you will have better performance and speed from a 4 year old phone that has an unlocked bootloader and strong development. I mean my Nexus 5 (from 2012) had better performance than my rooted S7. it sounds like you do want roms, and if you want roms then AOSP/Cyanogenmod is the way to go. there will probably never be any AOSP or CM ROM on the QC S7/E so you're better off getting an older galaxy model that does have a great development community and unlocked bootloader. or just get a OnePlus or Nexus or something.
Click to expand...
Click to collapse
Binary100100 said:
Or a Exynos S7.
Click to expand...
Click to collapse
xVermicide said:
exactly this. except for some reason I thought exynos variants are lacking certain bands/features on American networks. could be wrong.
Click to expand...
Click to collapse
Very helpful inputs guys, thank you! If I were to be honest with myself, I don't want AOSP/CM/Lineage, especially on a Samsung phone, so unlocked bootloader is not a deal breaker for me. However, I think root is cool for me for doing some SystemUI tweaks, Xposed and etc. Exynos was an option I was exploring, but lack of warranty, no Samsung Pay, and the price are enough to keep me at bay. I think I just need to put my big boy pants on and try to use a phone without rooting it. Something I have yet to do in EVER using an Android phone since about 10 years ago, and I have never ever used or bought an iCrap... I mean... an iPhone !
ProFragger said:
Very helpful inputs guys, thank you! If I were to be honest with myself, I don't want AOSP/CM/Lineage, especially on a Samsung phone, so unlocked bootloader is not a deal breaker for me. However, I think root is cool for me for doing some SystemUI tweaks, Xposed and etc. Exynos was an option I was exploring, but lack of warranty, no Samsung Pay, and the price are enough to keep me at bay. I think I just need to put my big boy pants on and try to use a phone without rooting it. Something I have yet to do in EVER using an Android phone since about 10 years ago, and I have never ever used or bought an iCrap... I mean... an iPhone !
Click to expand...
Click to collapse
Get a One+ 3T good development and really nice phone if you want root. Root is dead on Samsung phones and so are ROMs.
So by reading thru this thread, I assume having a T-mobile S7E (G935T) rooting is pointless and really not available the way I'm used to it coming from a Note 4. That's kind of a bummer... I've been using Android and have always had ROOT and all the goodies that come with it. And I recently starting really enjoying my Note 4 with all the cool development in Note 7 ported roms oh well... I wonder if the S7E is enough of an upgrade to keep my interest as stock?
I see there is a G935U firmware, but that seems a bit hit and miss? But I'm just starting to read up on all this... :good:
ShrekOpher said:
Get a One+ 3T good development and really nice phone if you want root. Root is dead on Samsung phones and so are ROMs.
Click to expand...
Click to collapse
Believe me bud, if Oneplus 5 or even 3T had an SD Card, I'd already have that phone, but thanks for your wisdom !
Araltd said:
So by reading thru this thread, I assume having a T-mobile S7E (G935T) rooting is pointless and really not available the way I'm used to it coming from a Note 4. That's kind of a bummer... I've been using Android and have always had ROOT and all the goodies that come with it. And I recently starting really enjoying my Note 4 with all the cool development in Note 7 ported roms oh well... I wonder if the S7E is enough of an upgrade to keep my interest as stock?
I see there is a G935U firmware, but that seems a bit hit and miss? But I'm just starting to read up on all this... :good:
Click to expand...
Click to collapse
You and I both man... The last few years, I have lived off the mercy of T-Mobile and their BLs being unlocked. But Samsung sure done them all in ! Even the International unlocked ones disable Samsung Pay (forever, mind you!) if Knox is tripped, which I believe it is, when rooted and TWRP'd.
As I understand it,
Android pay / Samsung pay is why they frown on rooting now. I can understand it, though I don't agree with it.
The first time someone's financial information is compromised, and they've ever used one of the "pay" methods, on a rooted device the pr nightmare that would ensue would make the note 7 fiasco look like child's play.
"Samsung unsecured device compromises persons credit card information today, while Apple is still secure" I can see the headline.
Sent from my Samsung Galaxy S7E
I will be creating a repository of root methods and guides, recoveries, roms and stock files. This will be a one stop shop for all your developer needs.
So far the only development. Is by Janjan, providing root, and a twrp recovery
https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
idontwanttobeanoob said:
I will be creating a repository of root methods and guides, recoveries, roms and stock files. This will be a one stop shop for all your developer needs.
So far the only development. Is by Janjan, providing root, and a twrp recovery
https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
Click to expand...
Click to collapse
considering all development for this device, from the only dev that ever worked on it, has stopped. I regret buying this device. I thought for sure Sony would have better action than this. I had a note 2 before this, and they were still developing for that phone when I stopped using it 2 months Ago. I think im going to try to sell it. it's really pathetic. but it is what it is
Sent from my Xperia XA1 Ultra using XDA Labs
I am in the process of moving but once that is done I will be working on porting a few roms so that we have some choices. Don't give up yet. I have faith in the community
idontwanttobeanoob said:
I am in the process of moving but once that is done I will be working on porting a few roms so that we have some choices. Don't give up yet. I have faith in the community
Click to expand...
Click to collapse
I just bought this coming from a Nexus 6P and was surprised that nothing had really been done with it it seems to be a good phone, just some of the stock options suck lol. I saw your thread for root and custom recovery and am going to try it I'm the next couple days.
You said you are going to be porting some Roms over, any ideas which you will be attempting? If you are taking requests I wouldn't mind Pure Nexus.. It's pretty kickass from a well known dev.. Or maybe even crdroid (lineage based)? Thanks for your work so far and keep at it.. Like I said, pretty good phone, just no development much yet.
mikeandjaimie said:
I just bought this coming from a Nexus 6P and was surprised that nothing had really been done with it it seems to be a good phone, just some of the stock options suck lol. I saw your thread for root and custom recovery and am going to try it I'm the next couple days.
You said you are going to be porting some Roms over, any ideas which you will be attempting? If you are taking requests I wouldn't mind Pure Nexus.. It's pretty kickass from a well known dev.. Or maybe even crdroid (lineage based)? Thanks for your work so far and keep at it.. Like I said, pretty good phone, just no development much yet.
Click to expand...
Click to collapse
The option for root and recovery is done by JanJan who has stopped working on this device. Please give him a thanks and your credit. Mid level phones have a habit of taking a few months to really get development going. But this phone should have plenty in the coming months!
I'd like to jump in for kernel and recovery development, but the problem is I don't have experience and I have to setup a dedicated Linux machine from one of unused laptop. Also, I have to work like everybody. I have four Xperia (Z Ultra, XA Ultra, XA1 Ultra, and L1). I just need other developers to help me get started.
Note: I only have US version except Z Ultra (C6833).
Hii
Just to give my opinion too on this topic
I did the mistake.. Usually I do my own research by google-ing all the reviews
Then I read some opinions, then i look also on you tube and then the most important
I do look at xda forum to see the support of the device
And i saw all that...but than I saw the forum is not like I am used to..its like dead .. not
just there are no one posting things..but the custom rom support is not there...
Well, I said to me also... ok its a 6 inch.. not everybody likes phablets..
Like, 5 inch is more popular.. maybe that is the reson there are no development..
And then I said..ok announced in Feb/March but just got to the market about May..
So..new device..should be some development..
Unfortunally I got one with bootloader unlock NO status..
And now I can not even get root..
But still... It was weird to have such an phone on XDA with dead forum all at all
Did a bit more research last few day after I got the device
As It looks like all the X series from the Sony Xperia... has no support..
Like there are 7 or 8 devices from the X series and the only one is the X Performance Model wich has like 4 to 5 custom roms
and a few stock modified kernels..
All the other phones do not have anything..
Or let me say the best example the XA Ultra also 6 inch from last year 2016 Model
Has not evan 1 thread or commend under xda forum for custom roms or kernels or what ever..like
more then one year and what?? Nothing..
So I do not hope we will have anything...not to get fooled its a new devices it will be in time and
we will need to wait ... bla bla bla.. nothing will happen
The best thing is to fool yourself with different launchers so that after some of use of the phone
You get sort of a feeling you did flash something..and get the feeling you changed the phone
Thats all...
Would point to NOVA laungher..and some others wich have much settings to modify the looks and
the way it works...
I really to not think anything will happen.. ever
i bought the regular xa1 thinking that there'd be insane development going on for it. looking back, i shouldn't have unlocked bootloader, and looked at getting different phone. if i try to take it back to the store now even though it's under 1 year warranty, they'll just say, "oh we can't replace it, we got to send it off to sony" in which case they won't do anything as sony will see that the bootloader is unlocked
Not to say custom ROMs aren't great and all, I too was here for the good stuff, but people complaining and taking phones back is a bit dramatic.
The stock ROM is great. It doesn't really need a custom ROM. It's a perfectly reasonable phone by itself.
A custom ROM makes sense in phones such as Samsung, Huawei and Xiaomi, where they botch everything to make it "unique", but Sony phones tread the line carefully to keep it pure as possible whilst adding actual useful features.
If you're picking up phones just to hack them, maybe you should try to start your own development on them. Get the toolchains, bring up a Linux system and get creative. Then you can be the hero of your own story.
What is the best way to return to fully stock? Relock the bootloader and flash the latest firmware? Might sell mine too and get an Essential PH-1.
So since this is my first Sony device and may be my last for a few reasons question I want to return everything to stock, and I use the method that was provided it won't relock bootloader right? I have to manually relock it like any other device? I just wanna return to stock so I can try and see what it take to get a Oreo rom once the update comes through.
Actually maybe do some research when this phone first came out with had start of support. We have twrp and custom kernel. There's a search button. Try it out.
I know that this thread seems to be dead but I was wondering if someone could share the sound file for plugging in the charging cord
Anybody know if/when this update is coming? Verizon updated their version of the G6 last week. Also, is anyone else frustrated that it is taking LG so long to update Android? Oreo was released August 2017 and it is May 2018. I like LG hardware a lot on the G6 and G7 models. But I am having a lot of second thoughts about buying their phones in the future due to the lack of software support. Maybe I should just get a Pixel next time.
LG says they have created a new division in the company focused on improving the speed of Android updates. I am not sure they will focus on older devices though.
https://techcrunch.com/2018/04/12/l...-bringing-android-updates-to-its-smartphones/
Would it help at all to contact LG and tell them I am switching to Pixel due to their poor software support?
htcnext said:
Also, is anyone else frustrated that it is taking LG so long to update Android?
Click to expand...
Click to collapse
No, no one else is frustrated with it. Nobody else has even thought about it. It's literally only you. That's why when you searched, you didn't find any other threads about this.
htcnext said:
Would it help at all to contact LG and tell them I am switching to Pixel due to their poor software support?
Click to expand...
Click to collapse
It could help you feel better. LG won't give a shit, though. You wouldn't be telling them anything they don't already know. They won't even reply to your email. I'd take that to mean, "Okay. Enjoy your Pixel, then."
I mean no disrespect to the initiator of this thread, but I really wish there would be some moderation and conglomeration of the threads, I requested this elsewhere.
Basically the whole Q and A forum has become useless-- just a bunch of unrelated and random threads about Oreo with unanswered questions and random observations, often without any relation to the title.
Everytime I visit the forum, there is yet another pointless "oreo" thread started, which divides people's time, attention and effort to answer.
There should be one thread on Oreo updates and that's it!!!
People, please stop posting of new oreo threads!
The thing is that the other Oreo threads did not have details on unlocked model us997. In any case, for a person with medium tech skills, how hard is it to load a custom Oreo rom to this model LG G6?
htcnext said:
The thing is that the other Oreo threads did not have details on unlocked model us997. In any case, for a person with medium tech skills, how hard is it to load a custom Oreo rom to this model LG G6?
Click to expand...
Click to collapse
You have to unlock your bootloader first
https://forum.xda-developers.com/lg-g6/how-to/official-lg-g6-bootloader-unlock-t3614719
I received us99720a last night
Anyone know how long it takes after they roll out a software update for us to get a kdz to flash I still don't have the update yet.
shaneg79 said:
Anyone know how long it takes after they roll out a software update for us to get a kdz to flash I still don't have the update yet.
Click to expand...
Click to collapse
No one knows
LG continues to be indifferent to software updates especially for non-carrier unlocked phone. I am also not going to buy LG cell phone once I switch to G5 in 6 months.
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.