Related
hi everyone, so i recently saw motorola razr m. the thing is, it had motorola markings on it like it is some kind of prototype or test device. it was running jellybean. just the markings were a bit curious, if someone can shed some light on what it was. thanks !
mikeverne said:
hi everyone, so i recently bought a second hand motorola razr m. the thing is, it has motorola markings on it like it is some kind of prototype or test device. it works totally fine, gsm unlocked and its running jellybean. everything runs as it should, just the markings are a bit curious. ive attached a pic to see if someone can shed some light on what it is. thanks !
Click to expand...
Click to collapse
Seems kinda fishy lol
https://forums.motorola.com/posts/0dc68e3f0d?commentId=716757#716757
Somber73 said:
Seems kinda fishy lol
https://forums.motorola.com/posts/0dc68e3f0d?commentId=716757#716757
Click to expand...
Click to collapse
yea i saw that too. but that doesn't really tell me anything apart from the fact that other phones like mine were also sold(which i already knew).
It would be best to just drop the subject. You have something rare, and if you want to keep it, I would keep it quiet. The guys on the Motorola forum are launching a pretty big investigation into this. I would delete your pic and edit your OP. Don't get me wrong, I DO NOT condone illegal activity, but there is a reason these are out in the open...
Regardless of the circumstances surrounding where or how he got the phone, there ought to be someplace where this guy can get answers as to its origin or what it is exactly without everybody overreacting.
Sent from my XT907 using xda app-developers app
It is an Engineering model device and it will have a fully unlocked bootloader Status 1 when you boot into AP Fastboot mode from the boot menu.
It will also have engineering firmware with userdebug testkeys builds unless it was flashed by prior owner to stock or a custom build.
These are very valuable devices to a developer because they can run any firmware, including the engineering bootloaders and radio images, which cannot be run even on devices with unlocked bootloaders via exploit or the official Development edition devices, all of which have a Status 3 bootloader.
The good news is you can run any firmware you like safely on them, but you must flash them manually and you can't run any OTA updates until you do so because they will fail signatures and checksums on engineering builds.
There is also usually a lot of debugging binaries and apps and monitoring components on these builds that you want to disable generally.
It's a great opportunity, but comes with some greater responsibility.
The official forum, as noted above, is an extremely poor place to get this kind of information and is basically useless, as you discovered.
More of these devices have been showing up lately and I have seen several posts by confused users like yourself regarding such phones.
Consider yourself lucky and start learning how to take advantage of your rare device!
It would seem, especially from the reaction by Motorola, that it is indeed an internal phone. I'm guessing they want the IMEI so they can take someone's head off.
I doubt Motorola would go after any end users, they didn't seem too mad at the guy who posted there. Someone inside will probably not be happy after that investigation though
Sent from my XT907 using Tapatalk 4 Beta
cellzealot said:
It is an Engineering model device and it will have a fully unlocked bootloader Status 1 when you boot into AP Fastboot mode from the boot menu.
It will also have engineering firmware with userdebug testkeys builds unless it was flashed by prior owner to stock or a custom build.
These are very valuable devices to a developer because they can run any firmware, including the engineering bootloaders and radio images, which cannot be run even on devices with unlocked bootloaders via exploit or the official Development edition devices, all of which have a Status 3 bootloader.
The good news is you can run any firmware you like safely on them, but you must flash them manually and you can't run any OTA updates until you do so because they will fail signatures and checksums on engineering builds.
There is also usually a lot of debugging binaries and apps and monitoring components on these builds that you want to disable generally.
It's a great opportunity, but comes with some greater responsibility.
The official forum, as noted above, is an extremely poor place to get this kind of information and is basically useless, as you discovered.
More of these devices have been showing up lately and I have seen several posts by confused users like yourself regarding such phones.
Consider yourself lucky and start learning how to take advantage of your rare device!
Click to expand...
Click to collapse
thank you! and btw, that wasn't me who posted in the official forums lol. thats the lase place i would think of posting if i had a prototype haha.
sloosecannon said:
It would seem, especially from the reaction by Motorola, that it is indeed an internal phone. I'm guessing they want the IMEI so they can take someone's head off.
I doubt Motorola would go after any end users, they didn't seem too mad at the guy who posted there. Someone inside will probably not be happy after that investigation though
Sent from my XT907 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thank you! and yea, i agree.
that convo on the motorola forum is hilarious!
buyer claimed he got it from someone he does not know that placed an ad on pakistani forum.
jco23 said:
that convo on the motorola forum is hilarious!
buyer claimed he got it from someone he does not know that placed an ad on pakistani forum.
Click to expand...
Click to collapse
uh, actually im pretty sure he is telling the truth. its sort of a Pakistani craigslist.
RSD is proprietary software, owned by Motorola. While I know it's very easy to find online, it's not intended for public use. The rules of this site forbid discussion of software installation or use unless that software is distributed by Motorola or one of its partners.
That pretty much sums it up. Had he come to xda, he'd have gotten help. He didn't seem too open to helping the Motorola guys out though, so they didn't help him. Don't see why he would lie about that, he's just a poor guy who wants his confidential Motorola property to work for him... By asking the people that someone stole it from... Yeah...
Sent from my XT907 using Tapatalk 4 Beta
guys, i am going to buy a similar "confidential" razr m phone. what do you suggest? is this going to cause software issues like installing new roms or gapps?
dasche said:
guys, i am going to buy a similar "confidential" razr m phone. what do you suggest? is this going to cause software issues like installing new roms or gapps?
Click to expand...
Click to collapse
Nope. Since it's factory unlocked, you should be able to install TWRP and go about flashing whatever you want. It might be a wiser choice to buy a regular handset, since you want have Motorola property all over the front.
DAN ROSENBERG HAS FOUND AN EXPLOIT TO UNLOCK THE MOTO X (AND OTHER DEVICES) BOOTLOADER!!!
Will he release it? Your guess is as good as mine...
Per jcase: Support to be added soon to "Sunshine" unlock app for Moto devices!
jcase said:
Motorola support is yet to be added to the version on the site, stay tuned (and dont update your phones)
Click to expand...
Click to collapse
DO NOT UPDATE YOUR DEVICE OR TAKE ANY OTAS IN THE MEANTIME!!!!!
EDIT 9/22/14: Unlock now available for Droid Maxx, Mini, Ultra, and THE MOTO X!!!
Find the tool at http://theroot.ninja
Cost is $25 per device. Works on 4.4.3 and BELOW, and *some* 4.4.4. You have to try the app to find out. You do NOT pay unless the tool confirms compatibility.
EcHoFiiVe said:
AN EXPLOIT HAS BEEN FOUND BY DAN ROSENBERG EVERYONE.
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
EcHoFiiVe said:
He officially unveiled it at the Black Hat conference
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
samwathegreat said:
AMAZING NEWS!!! Thanks!!!!! I'm researching this now, and will post here as soon as more info is found. THANK YOU FOR THE HEADS UP!!!!!
EDIT: Confirmation posted to REDDIT, HERE: http://www.reddit.com/r/Android/comments/2csyiq/
Click to expand...
Click to collapse
Lots of interest in the Moto X forums.........none here???
Well, when I entered this thread my opinion was "WTF, again, what chance this guy has against Motorola cryptography?" BUT, why not? There is nothing can be gathered from my unlock code, except my IMEI (reverse calculate from the unlock token or database match - both of which are unlikely) which could be used by Moto to re-lock my BL but if they wanted to, they would've done it with the latest update.
I'm going with it!
Good luck, @samwathegreat
CrazyRussianXDA said:
Well, when I entered this thread my opinion was "WTF, again, what chance this guy has against Motorola cryptography?" BUT, why not? There is nothing can be gathered from my unlock code, except my IMEI (reverse calculate from the unlock token or database match - both of which are unlikely) which could be used by Moto to re-lock my BL but if they wanted to, they would've done it with the latest update.
I'm going with it!
Good luck, @samwathegreat
Click to expand...
Click to collapse
Thanks. Keep in mind, we are NOT attempting to crack Moto's cryptography, as I well know that this isn't possible (in my lifetime, at least). Instead, we are trying to find if a single code has successfully unlocked more than one device. There isn't any proof, based on Dan Rosenburg's (author of the Razr M Bootloader Exploit) analysis of the "token validation" logic, that the code is based on the IMEI.....although it COULD be the case. This whole thing is quite the mystery - especially the "China Middleman" aspect of it.
Dan suggests it is based on the particular certificate / key / hash / q-fuses for said devices. And once again....this is ALL based on complete speculation (as I've stated many times (don't care to count how many). )
Thanks to anyone who contributes and thanks for creating this effort! I have a BL locked Mini and it's a 2013 version so not only can I not pay (he only unlocks 2014s right now), but I don't have PayPal and I don't have $45. Really, this might work and so please post your codes if you want to help people like me... we can never know if it works until we try.
Sent from my XT1030 (Droid Mini)
Is there a way to retrieve the code? I'm unlocked via the Tao bao site on the first go around. I used the IM feature on the site to communicate so I don't have the code in an email. I can't remember for the life of me how I signed on to look to see if it's still there. Is the code stored on the device anywhere once unlocked?
Sent From My Droid Ultra
Caseyk621 said:
Is there a way to retrieve the code? I'm unlocked via the Tao bao site on the first go around. I used the IM feature on the site to communicate so I don't have the code in an email. I can't remember for the life of me how I signed on to look to see if it's still there. Is the code stored on the device anywhere once unlocked?
Sent From My Droid Ultra
Click to expand...
Click to collapse
No way to retrieve it from the device itself....and I'm not familiar with Taobao (or how to look up a prior purchase from there). You can try searching your email (if you even received one) for your IMEI, as he usually included it along with the unlock token.
Aside from that, I don't have any suggestions. Thanks for trying to help though.
If moto x gets a way to unlock bl for free, it could help us a lot!
I just wanted to say "THANKS!" to all the ---jerks--- that are putting bogus info into the form.....like "12345", or the most recent "1".....yeah, thanks for the humor you're giving me. Including Mr. XDA username "a"...how original....
Nice to get a good laugh every now and then.....knowing I can simply erase your bogus data away with one simple keystroke... LMAO
Collecting just unlock code make no sense. I think that code AT LEAST a hash code of IMEI. Well it might be not a IMEI but serial number or what ever. They run hashing on security chip and verify the signature. The chance of two phones having the same code is veeeeery low. In another words you won't find equal codes, I know for sure. The only way is to get how they calcualte the code but that would be hard because you don't know what it comes from and you have nothing at all, not even IMEI or serial.
Dragon31337 said:
Collecting just unlock code make no sense. I think that code AT LEAST a hash code of IMEI. Well it might be not a IMEI but serial number or what ever. They run hashing on security chip and verify the signature. The chance of two phones having the same code is veeeeery low. In another words you won't find equal codes, I know for sure. The only way is to get how they calcualte the code but that would be hard because you don't know what it comes from and you have nothing at all, not even IMEI or serial.
Click to expand...
Click to collapse
You might want to re-read the first post...specifically here:
samwathegreat said:
Also, I'm not suggesting that I'm right about this, or even COULD be right about this -- I'm merely suggesting a POSSIBILITY. It is entirely possible (probable, even) that I'm completely wrong / off-track about this. I wouldn't be surprised in the least. In fact, I'm actually EXPECTING it.
Click to expand...
Click to collapse
and here:
samwathegreat said:
OK, sure, we understand that. Now examine the logic. Nowhere does Dan Rosenburg suggest that the TOKEN is unique to a particular IMEI, OR in any way validated or hashed against the IMEI. Only that it is based on certificates / keys / hashes STORED in the CID partition, and blown Q-fuses.
Click to expand...
Click to collapse
and here:
samwathegreat said:
And finally, I'll end this post by saying that curiosity is very important to achieve any new breakthroughs. Making "educated guesses" based on analysis of available data is the only way to make innovations and new discoveries. It's OK to be wrong, as long you use what you have learned to build upon your knowledge and use this information to improve future analytics.
This is a hypothesis based on the [small amount of] data currently available. Nothing more.
Click to expand...
Click to collapse
and in response to:
Dragon31337 said:
The only way is to get how they calcualte the code but that would be hard because you don't know what it comes from and you have nothing at all, not even IMEI or serial.
Click to expand...
Click to collapse
Please consider that we have no interest in what you are suggesting....which is actually breaking Moto's encryption / master key. Based off my knowledge of key / certificate - based cryptography, I am well aware that even IF we had 10,000 VALID unlock token / IMEI combinations, it would STILL likely take -longer than our combined lifetimes- to crack the master key. And that's assuming you are correct about there being a correlation between Token & Serial / IMEI. Have you considered "q-fuses"? Moto very well could have blown q-fuses (identically) in more than one device...
Personally, I have no interest in -that-. I'm not seeing what purpose collecting the IMEI combinations would have, other than deterring people from actually participating in this because they don't want to share their IMEI...
So my questions really is: What are you trying to say that I haven't already? Self-admittedly, this probably won't work....said it more times than I care to count in the first post alone...
And finally, EVERYONE is entitled to their opinion, and I welcome to you "speculate" however you wish! Lets just please not clog up this thread with any more of it. This thread has a specific purpose, and I'd like to keep it at that. Thanks
Many of the Motorola Users who have msm8960 devices unlocked their bootloaders using this method...
http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1
iAjayIND said:
Many of the Motorola Users who have msm8960 devices unlocked their bootloaders using this method...
http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1
Click to expand...
Click to collapse
Which doesn't apply at all to this device. That is for the RAZR HD.
iAjayIND said:
Many of the Motorola Users who have msm8960 devices unlocked their bootloaders using this method...
http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1
Click to expand...
Click to collapse
Topsnake said:
Which doesn't apply at all to this device. That is for the RAZR HD.
Click to expand...
Click to collapse
That is Dan Rosenberg's method. I've mentioned his name multiple times in the OP, as well as his "Token Validation Logic".
Since the Razr M/HD AND the Moto X have the exact same SoC (MSM8960), his token validation logic likely still applies. @Topsnake is correct in that it will not work on the Moto X, but its because that method exploited a vulnerability in TrustZone to write to (blow) q-fuses in the secure area, thereby unlocking the BL.
All of this is described in the OP, but thanks for trying to add some useful info
Hello everybody. This idea is getting alot more interest in the Moto X section, and one user asked if we would be willing to share some details on the data collected so far. Here it is:
samwathegreat said:
Sure! I think everyone deserves to know the current status....
As of RIGHT NOW, we have:
86 submissions
of which 5 are completely and purposely BOGUS
and 2 sets (4 submissions) are -complete duplicates- and were posted from the same IP, within seconds of each other (I wonder if they really thought I wouldn't look at the timestamps / IP addresses?)
zero correlations
What I can also tell you is that IF the build dates entered are correct, we do have 3 sets (6 submissions) that have the same build date and are completely unique codes. This would seem to rule out the previously suggested idea that perhaps all units from a particular build date might use the same unlock-token.
Still need much more data to make any further (useful) correlations.
Hope everyone appreciates the update.... :good:
Click to expand...
Click to collapse
Keep those submissions coming!
MAY I HAVE YOUR ATTENTION EVERYONE:
I've just received word that DAN ROSENBERG has found a bootloader-unlock exploit, and has just unveiled it at the BlackHat conference!!!!!!
I haven't verified it 100% yet, but if true, this is AMAZING!!!!
This means that until patched, we can all now unlock our bootloaders for FREE!!!!!!!!!!!!!!!
:highfive: :highfive: :highfive: :good: :good: :good: :laugh: :laugh: :laugh:
EDIT: Guys, it appears to be 100% True!!!!!!
See the Reddit article here: http://www.reddit.com/r/Android/comments/2csyiq/
He just demonstrated this LIVE @ the Blackhat Conference!!!!
Hopefully it will be released soon for all the guys that missed the China boat.
sent from "my kungfu is stronger than yours" XT1080
That's great news. Hope it pans out for everyone!!
Sent from My Droid Ultra
OMG!!! this is GREAT NEWS FOR EVERYONE WITH A DROID MAXX ULTRA MINI X!!!!!!!
and its only a 3 page document (lol)
i hope he releases it to the public for free!
a new wave of unlocked BL are coming!
thanks for the heads up!
Having missed the China Boat as someone said earlier... This 2013 Maxx owner is hoping anxiously for this to come true quickly.
This is just unacceptable.
Sent from my XT1032
MetalPhoenix45 said:
This is just unacceptable.
Sent from my XT1032
Click to expand...
Click to collapse
You're right to be frustrated. Like yourself, I'm still waiting on the lollipop update for my global US retail of the xt1032. From the moment Lenovo took over the company, the US version of the moto G has been the last to get update. Look at the time they took to update use to 4.4.4 from 4.4.3. A whole three or four months after it was released to every other region for the phone but we were the first to get the update to 4.4.3 while they skipped for 4.4.3 to 4.4.4 for the other regions. I have no hope of seeing the update coming before July or before android 5.2 comes out. Ridiculous.
And what did you expected to receive talking to Motorola Chat? Did you expected to talk to a developer? Mind yourself that the person who answers the questions are girls from 20 to 30 years old that own a Nokia Lumia phone and dont know anything about ETAs of OTAs...And even if they knew something about that, they wont release any info to an average Moto user..
Also, there is no need to be like that when chatting to customer service... No need to be rough.. Just flash CM12, works great already, or flash BR Lollipop, its rocky stable! When the day comes, go to US Lollipop.
So, no need to open a new thread for this man,,, take it easy.
Cheers!
MetalPhoenix45 said:
This is just unacceptable.
Sent from my XT1032
Click to expand...
Click to collapse
I totally agree. This is just unacceptable. The way you talk to another human being. You are extremely rude. If I was the moto representative, I'd just disconnect from you. Moto support is for people who need help with their phones. What did you expect will be the outcome, that they'll give you the update over moto support? I know they often don't help well with normal stuff, but that doesn't give you a right to be rude to them. Go and get a life
tzzeri said:
I totally agree. This is just unacceptable. The way you talk to another human being. You are extremely rude. If I was the moto representative, I'd just disconnect from you. Moto support is for people who need help with their phones. What did you expect will be the outcome, that they'll give you the update over moto support? I know they often don't help well with normal stuff, but that doesn't give you a right to be rude to them. Go and get a life
Click to expand...
Click to collapse
How was I rude?
Sent from my XT1032
You didn't worship the ground they walk on, that's how you were rude. Where were your manners?
MetalPhoenix45 said:
How was I rude?
Sent from my XT1032
Click to expand...
Click to collapse
Helo??
?
Heloooooo
Please can you respond faster?
tzzeri said:
Helo??
?
Heloooooo
Please can you respond faster?
Click to expand...
Click to collapse
Good point!
Also if one is so angry/furstrate/pissed or whatever. Switch phones, it is easy as that. If you are NOT satisfied with the product don't use it.
I have done that. And things didn't get better, so wait patiently like we do or do what was suggested.
MetalPhoenix45 said:
This is just unacceptable.
Sent from my XT1032
Click to expand...
Click to collapse
I am waiting too but if you are really that impatient then just flash UK or EU firmware and get the update, works just as well
People like you are the reason Motorola stopped Soak tests.
Guys you should not be worried about updates, you should enjoy the phone, previously I have a nexus 5 and believe me updates are not what we expected, lollipop make me need to reboot the phone everyday cause leak, camera, flash, and 5.1 was the same thing I was very disappointed with Google.
Now I have a moto g and I can use my phone everyday without having to worried about battery, flash, ram and so on.
MetalPhoenix45 said:
This is just unacceptable.
Sent from my XT1032
Click to expand...
Click to collapse
There is no need of a thread for this kind of ****
If you are a senior xda member you should not cry like a kid for official updates but you should flash a custom firmwares.
And there is no need to say bad things about the company or the representatives
Close this thread
Sent from my Moto G using XDA Free mobile app
tzzeri said:
Helo??
?
Heloooooo
Please can you respond faster?
Click to expand...
Click to collapse
Its because the responder took almost 10 minutes to reply.
Sent from my XT1032
sjandroiddeveloper said:
There is no need of a thread for this kind of ****
If you are a senior xda member you should not cry like a kid for official updates but you should flash a custom firmwares.
And there is no need to say bad things about the company or the representatives
Close this thread
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I guess.
Sent from my XT1032
We didn't by our phones expecting this update. It's not like you have a unusable device on 4.4.4
FFS it's only a operating system!
eemgee said:
We didn't by our phones expecting this update. It's not like you have a unusable device on 4.4.4
FFS it's only a operating system!
Click to expand...
Click to collapse
You know what, im just going to stick with cyanogenmod.
Sent from my XT1032
MetalPhoenix45 said:
Its because the responder took almost 10 minutes to reply.
Sent from my XT1032
Click to expand...
Click to collapse
That's because you're not the only one in the world they need to respond to. Either way, with the word almost, it seems you're exaggerating. And they're not your slave, they can answer when they want
tzzeri said:
That's because you're not the only one in the world they need to respond to. Either way, with the word almost, it seems you're exaggerating. And they're not your slave, they can answer when they want
Click to expand...
Click to collapse
Its one at a time, when I went to get support before it said you are #7 in line so this shows that its one at a time, and of course they are not my slave. It took 5-10 min.
Sent from my XT1032
MarckozZ said:
Also, there is no need to be like that when chatting to customer service... No need to be rough.. Just flash CM12, works great already, or flash BR Lollipop, its rocky stable! When the day comes, go to US Lollipop.
Click to expand...
Click to collapse
There's a problem here. You know what's great about Android most of the time? The ability to develop custom ROMs for it and tweak it to make it our own.
You know what's not acceptable? Locking bootloaders, not letting certain groups of us unlock it, and essentially preventing us from owning what's rightfully ours. I don't mean to sound entitled here, but the hardware is mine, I legally purchased it, and I should be able to break it all I want. I have no issue with Motorola taking their time to make sure Lollipop is the best it can be. My issue is the fact that just because I have a "branded" device, I'm not allowed to unlock my bootloader and install a different ROM. And I'm not even an ATT/Cricket customer, so why should I be subjected to their rules?
Sorry about the rant, it's just an issue that really bothers me here.
Chrono86 said:
There's a problem here. You know what's great about Android most of the time? The ability to develop custom ROMs for it and tweak it to make it our own.
You know what's not acceptable? Locking bootloaders, not letting certain groups of us unlock it, and essentially preventing us from owning what's rightfully ours. I don't mean to sound entitled here, but the hardware is mine, I legally purchased it, and I should be able to break it all I want. I have no issue with Motorola taking their time to make sure Lollipop is the best it can be. My issue is the fact that just because I have a "branded" device, I'm not allowed to unlock my bootloader and install a different ROM. And I'm not even an ATT/Cricket customer, so why should I be subjected to their rules?
Sorry about the rant, it's just an issue that really bothers me here.
Click to expand...
Click to collapse
They lock the device to prevent you from killing it and knocking on company's doors for warranty
Sent from my Moto G using XDA Free mobile app
checked devtester http://devtester.ro/projects/lg-firmwares/country.php?country=Taiwan
and sure enough there's a new firmware when I checked LG Bridge.
No OTA notification for me yet though
if only we could root
Absolutely no interest in Marshmallow unless we finally get a bootloader unlock for the TWN variant.
Absolutely love my G4, but I have no respect for their decision to simply ignore the wishes of developers/people who want to use their phone how THEY want.
Poor form LG, poor form indeed.
Weirdly it was there Last night on my netbook but it refused to Work as it didn't have enough ram available. Today on Work computer it said no update available! Looks like they pulled it again
And when I tried again just there now again it's gone! Update withdrawn: AGAIN!
is there any KDZ available that we could flash using LGUP?
Stevles said:
Absolutely no interest in Marshmallow unless we finally get a bootloader unlock for the TWN variant.
Absolutely love my G4, but I have no respect for their decision to simply ignore the wishes of developers/people who want to use their phone how THEY want.
Poor form LG, poor form indeed.
Click to expand...
Click to collapse
Same! I absolutely love my G4 but bcoz of this ridiculous decision of theirs I will never buy another one and will steer everyone I know away from them. The way they are carrying on you would think they were worried everyone in the world wants to unlock their bootloaders but it's only enthusiasts and devs, the very people they should be making happy as it's us that spreads word of mouth recommendations. Which is the best form of marketing. I updated to MM bcoz I've totally lost faith in LG and got sick of waiting for either them to have a change of heart or devs to come up with a solution (which LG will probably try and thwart). I'm joining the Nexus army!
i see the update available in mac versions of lg bridge but not the pc version. it goes through the whole download process and then the update fails on two separate macs. pretty frustrating.
oracleoftruth said:
Weirdly it was there Last night on my netbook but it refused to Work as it didn't have enough ram available. Today on Work computer it said no update available! Looks like they pulled it again
And when I tried again just there now again it's gone! Update withdrawn: AGAIN!
Click to expand...
Click to collapse
Yep, it was available for me last night, but now it says no update available. They pulled it.
I wanted to have a play before I sell my G4.
I have the kdz file, if you want I can upload it
shinanai said:
I have the kdz file, if you want I can upload it
Click to expand...
Click to collapse
Please upload it. I really need it.
okay uplodaing
Man don't even bother flashing marshmallow onto your phone. It's not what you think it is. I did flash using LGUP and what a mistake it was too flash the marshmallow kdz. You only get half the screen on time compared to lollipop. So hold of until they sort the issues out
Sent from my LG-H815 using Tapatalk
http://forum.xda-developers.com/g4/general/h815-twn-kdz-t3272976
kdz file here
dieselhazza said:
Man don't even bother flashing marshmallow onto your phone. It's not what you think it is. I did flash using LGUP and what a mistake it was too flash the marshmallow kdz. You only get half the screen on time compared to lollipop. So hold of until they sort the issues out
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Thank you for your advice.
It's much more smoother and no bugs that I encounter so far, a few days needed for doze mode to kick in. I highly recommend it, you won't regret.
I do think if they pulled it (or aren't ready to release and someone accidentally pushed it out prematurely) then it's for a reason. If they have it ready then why would they hold it back? I'll let them continue to bug test and i'll get it when ready. Lollipop is still fairly new and without better battery life I don't see the point of marshmallow at this point.
Sent from my LG-H815 using Tapatalk
shinanai said:
http://forum.xda-developers.com/g4/general/h815-twn-kdz-t3272976
kdz file here
Click to expand...
Click to collapse
Thread closed, please use the above thread
Can someone please confirm that you received this Nougat update from Motorola, for this model ( XT1607 )
kurdacrunch said:
Can someone please confirm that you received this update from Motorola, for this model ( XT1607 )
Click to expand...
Click to collapse
Err...what update?
Davey126 said:
Err...what update?
Click to expand...
Click to collapse
Sorry I didn't specify, thought it was obvious that I am taking about the update to nougat. My bad...
kurdacrunch said:
Sorry I didn't specify, thought it was obvious that I am taking about the update to nougat. My bad...
Click to expand...
Click to collapse
I never received an OTA update notification on two XT1607s (US). Not that it would have done any good as both are bootloader unlocked with a custom recovery (stock recovery and an untouched system partition are two of many prerequisites required to process OTAs). Eventually updated both via TWRP flashable build from this thread. Worked a treat. Encourage reading posts from March 1st forward before deciding your path. Good luck.
kurdacrunch said:
Can someone please confirm that you received this Nougat update from Motorola, for this model ( XT1607 )
Click to expand...
Click to collapse
Spouse's US retail xt1607 is factory stock, boot loader still locked, etc. I hasn't received Nougat yet.
n76 said:
Spouse's US retail xt1607 is factory stock, boot loader still locked, etc. I hasn't received Nougat yet.
Click to expand...
Click to collapse
Me neither and the bootloader is locked, stock firmware, and never rooted, damn...
Thank you.
kurdacrunch said:
Me neither and the bootloader is locked, stock firmware, and never rooted, damn...
Click to expand...
Click to collapse
Speculation: Moto isn't pushing updates to XT1607s (why would they) leaving the decision to carriers who could care less about unbranded G4P variants. At some point you will probably have to unlock the bootloader and apply updates manually.
Note this does NOT require replacing stock recovery as booting TWRP will get the job done. Or install directly from fastboot (harder with no benefit IMHO).
Davey126 said:
Speculation: Moto isn't pushing updates to XT1607s (why would they) leaving the decision to carriers who could care less about unbranded G4P variants. At some point you will probably have to unlock the bootloader and apply updates manually.
Note this does NOT require replacing stock recovery as booting TWRP will get the job done. Or install directly from fastboot (harder with no benefit IMHO).
Click to expand...
Click to collapse
My main concern is to use a rom that may be potentially dangerous. Still I guess I'll have to do it in the future. Also, I think Moto should have a desktop app so the people can update it painless, but anyway, I agree with you.
Thank you to all of you, you were great.
Thumbs up for the community!
kurdacrunch said:
My main concern is to use a rom that may be potentially dangerous. Still I guess I'll have to do it in the future. Also, I think Moto should have a desktop app so the people can update it painless, but anyway, I agree with you.
Thank you to all of you, you were great.
Thumbs up for the community!
Click to expand...
Click to collapse
Thanks for the kind words.
I wouldn't be too concerned with stock Marshmallow. Overall security profile will be slightly diminished but can be effectively offset through good hygiene: avoid extensive use of public WiFi, surf responsibly, careful with clicks, don't download 'crapware', only use trusted stores, etc. Google Play Services also offers a layer of protection that remains current regardless of ROM status.
Still, should you be worried given all the media drama about the latest exploit impacting tens of millions of devices? Depends on behaviors that are entirely within your control. I sleep well at night regardless of patch status on my varied devices. Update when it is convenient and for refinements in Nougat that may improve your overall productivity and enjoyment.
Davey126 said:
Thanks for the kind words.
I wouldn't be too concerned with stock Marshmallow. Overall security profile will be slightly diminished but can be effectively offset through good hygiene: avoid extensive use of public WiFi, surf responsibly, careful with clicks, don't download 'crapware', only use trusted stores, etc. Google Play Services also offers a layer of protection that remains current regardless of ROM status.
Still, should you be worried given all the media drama about the latest exploit impacting tens of millions of devices? Depends on behaviors that are entirely within your control. I sleep well at night regardless of patch status on my varied devices. Update when it is convenient and for refinements in Nougat that may improve your overall productivity and enjoyment.
Click to expand...
Click to collapse
Agree, but what I am afraid is how this rom is really untouched. Is there a safe download somewhere?
kurdacrunch said:
Agree, but what I am afraid is how this rom is really untouched. Is there a safe download somewhere?
Click to expand...
Click to collapse
Provided link in a previous post (few days back).
Davey126 said:
Provided link in a previous post (few days back).
Click to expand...
Click to collapse
Thank you!
Davey126 said:
Provided link in a previous post (few days back).
Click to expand...
Click to collapse
Sorry to bother you again, but I have some doubts, I did check out the link, the date of this have more than a year, are you sure this is not the soak test?
Also I would like to keep my phone as pristine as possible, and I have a while since I am not messing with roms, my question is what do I need to make this work?
PD: Using the console is not an issue
kurdacrunch said:
Sorry to bother you again, but I have some doubts, I did check out the link, the date of this have more than a year, are you sure this is not the soak test?
Also I would like to keep my phone as pristine as possible, and I have a while since I am not messing with roms, my question is what do I need to make this work?
PD: Using the console is not an issue
Click to expand...
Click to collapse
Lastest upload is from a few months back (NPI26.48.36) and yields the Nov 1st 2017 patch level. Unfortunately, OP does not exercise any form of formal change control; you'd have to read through the thread to know there were updates. On that note you can read through this thread again and the linked thread (especially from March 1st forward) to gain confidence the upload is legit.
Bigger issue is getting over the pristine hurdle. You will need to unlock the bootloader which immediately voids the warranty and yields an ugly boot screen (which can be remedied). You'll then need to learn TWRP which isn't difficult but not geared toward the average Facebook user. You probably will NOT have to root either the old or new ROM. If any of that feels significantly uncomfortable then the wiser path may status-quo. There are tens of millions of mobiles running Lollipop, KitKat and older ROMs that date back three or more years. The version of Android on you two G4Ps isn't nearly as outdated as you might think.
Davey126 said:
Lastest upload is from a few months back (NPI26.48.36) and yields the Nov 1st 2017 patch level. Unfortunately, OP does not exercise any form of formal change control; you'd have to read through the thread to know there were updates. On that note you can read through this thread again and the linked thread (especially from March 1st forward) to gain confidence the upload is legit.
Bigger issue is getting over the pristine hurdle. You will need to unlock the bootloader which immediately voids the warranty and yields an ugly boot screen (which can be remedied). You'll then need to learn TWRP which isn't difficult but not geared toward the average Facebook user. You probably will NOT have to root either the old or new ROM. If any of that feels significantly uncomfortable then the wiser path may status-quo. There are tens of millions of mobiles running Lollipop, KitKat and older ROMs that date back three or more years. The version of Android on you two G4Ps isn't nearly as outdated as you might think.
Click to expand...
Click to collapse
Thanks again, can't see any reason to rush myself into nougat, anyway is a matter of development and marketing; that we'll see more candies in the near future (not for this smartphone) it's kinda sad we are obliged to buy a new smartphone if you want the security patches, even if it's a very expensive one, but even worse is the incompetence of Lenovo sharing an update through OTA.