Database Users

motorola razr M prototype?

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.

[XT1053] [5.0.2] Lollipop Soak Test Download

Here is a download for the 5.0.2 soak test from Motorola for XT1053 devices. I have not tried this yet, I received this from a friend who reported it successfully working on his device.
I do not take responsibility if this file bricks, destroys, or sets fire to your phone. Use this at your own risk. I have not tested this file, therefore I cannot confirm that it works.
If you do venture to try this, please report back.
[Someone has already posted this on the other thread, removed]

[MOD EDIT:]SHAME SHAME SHAME. Signing an NDA means you're agreeing to not share details of the special program you are in.
This has been removed at the request of Motorola due to your negligence in violating the terms of your agreement.
[DARKTERMIT EDIT:]I'm not signed NDA
Screenshots
Click to expand...
Click to collapse
i smell this

habusho said:
i smell this
Click to expand...
Click to collapse
It's likely coming. But at least I'm not breaking the NDA, my friend is. Probably won't matter. I'm getting it out while I can.

Bigluc said:
It's likely coming. But at least I'm not breaking the NDA, my friend is. Probably won't matter. I'm getting it out while I can.
Click to expand...
Click to collapse
Nothing good will come out of this, please remove it. The ones installing this will likely have issues further updating.
Just wait a few more days (after 4 months a few days seem like nothing).

alexferdean said:
Nothing good will come out of this, please remove it. The ones installing this will likely have issues further updating.
Just wait a few more days (after 4 months a few days seem like nothing).
Click to expand...
Click to collapse
how exactly is patching a factory zip update complicating future updates?

DrDecoy said:
how exactly is patching a factory zip update complicating future updates?
Click to expand...
Click to collapse
The OTA updates, including soak/beta or whatever you want to call pre-release received via the Moto Feedback Network, and those pushed by the carriers, have pre-flash validation checks in them.
They check for certain things in build.prop, particular files (and checks their hash/check sum), etc. IF your phone doesn't match, the OTA wont install. In addition, with the OTA's and these leaked ZIPs including updates to GPT.BIN and the bootloader, and history showing how easy it is to brick trying to downgrade when those are involved, that could complicate trying to get back on track should Moto or the Carriers push something else out.
A while back, I think it was the Droid X, there were leaked updates, people were flashing them, they were not meant to be released and the people who installed them got STUCK unable to update for a while. It was a while ago, so my memory is fuzzy, but a process was finally found, but it took a while, and a few updates, to bring those people back in line. And it was a little more difficult due to locked bootloaders.
So practicing a little caution is a good thing.

Bigluc said:
It's likely coming. But at least I'm not breaking the NDA, my friend is. Probably won't matter. I'm getting it out while I can.
Click to expand...
Click to collapse
Nice way to justify leaking stolen software. Always amusing to see wanna-be devs pirating someone else's work and somehow justifying it to themselves.

KidJoe,
One person can update his bootloader, others supplied with system partition backups don't have to. Deployed Android doesn't require updated motoboot, or secure things. You know what I mean...
But hey, it's illegal, firstly. And secondly, let's not spoil Motorola good intentions to bring us the latest Android, and quickly. Sooon )

Can you post a link to the new post with the file?

s5610 said:
KidJoe,
One person can update his bootloader, others supplied with system partition backups don't have to. Deployed Android doesn't require updated motoboot, or secure things. You know what I mean...
But hey, it's illegal, firstly. And secondly, let's not spoil Motorola good intentions to bring us the latest Android, and quickly. Sooon )
Click to expand...
Click to collapse
Quickly is not the right word when it has being months of LP being out.

sorullo_xgrx said:
Quickly is not the right word when it has being months of LP being out.
Click to expand...
Click to collapse
I'm with Motorola on this one.
You should see s4 after lollipop update.
The battery gives Hardly 1 hour of screen time.
It has rendered the phone unusable.
At least we are getting a reasonably stable update.
Also getting features from new flagship.
Who does that

DrDecoy said:
how exactly is patching a factory zip update complicating future updates?
Click to expand...
Click to collapse
Besides other things the bootloader gets updated. It's not so easy to go back to 4.4.4.

s5610 said:
KidJoe,
One person can update his bootloader, others supplied with system partition backups don't have to. Deployed Android doesn't require updated motoboot, or secure things. You know what I mean...
But hey, it's illegal, firstly. And secondly, let's not spoil Motorola good intentions to bring us the latest Android, and quickly. Sooon )
Click to expand...
Click to collapse
Actaully, based on history with the 2013 X...
That doesn't always work right. i.e. When it was found that 4.4.2 broke MotoWpNoMo and SlapMyMoto, some tried upgrading by flashing only PARTS of the 4.4.2 rom (so they could roll back).. They ran into features not working, like App Drawer -> Settings -> Security.
We've seen other issues arise when partially flashing too, but they were a while back so my memory is a little fuzzy on the specific details.

I flashed it days ago.... My phone is fine

needleyepoke said:
I flashed it days ago.... My phone is fine
Click to expand...
Click to collapse
Quick question are you on T-Mobile. Do you have the 4g LTE or just 4g on the status bar?

sorullo_xgrx said:
Quick question are you on T-Mobile. Do you have the 4g LTE or just 4g on the status bar?
Click to expand...
Click to collapse
I'm on T-Mobile with the xt1053 and no I do not have the LTE signal BUT I do have LTE when looking in phone settings... I've heard everyone saying the same thing

needleyepoke said:
I'm on T-Mobile with the xt1053 and no I do not have the LTE signal BUT I do have LTE when looking in phone settings... I've heard everyone saying the same thing
Click to expand...
Click to collapse
Yeah same here, I wonder if moto remove the LTE on lollipop but since is just a soak test it not yet implemented , thanks

So are you thinking that after the soak test we will get another update?
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
My nexus 5 has it don't know why they wouldn't have it in the moto..I guess it really doesn't bother me as much as not having 5.0

sorullo_xgrx said:
Quick question are you on T-Mobile. Do you have the 4g LTE or just 4g on the status bar?
Click to expand...
Click to collapse
I have TMo and the XT1053 and I'm only showing 4G but with LTE speeds. I saw a screenshot on here of someone with what appears to be a special T-Mobile build of the Lollipop soak test with LTE in the signal bars though.

Razgriz said:
I have TMo and the XT1053 and I'm only showing 4G but with LTE speeds. I saw a screenshot on here of someone with what appears to be a special T-Mobile build of the Lollipop soak test with LTE in the signal bars though.
Click to expand...
Click to collapse
Probably the actual update and not the first soak test that went live a week ago...
---------- Post added at 03:34 PM ---------- Previous post was at 03:32 PM ----------
Man I hate the day lenovo bought motorola, it just felt updates were not gonna be the same.

[Q] LG G2 Android 5.1 Update

Hi guys! I just found this new and I want you to say me what do you think about it, if you think it's true or not, and such...
This is the page: http://en.yibada.com/articles/37437/20150609/android-5-1-lollipop-release-news-lg-g2-mini-g.htm

JoeBro19 said:
Hi guys! I just found this new and I want you to say me what do you think about it, if you think it's true or not, and such...
This is the page: http://en.yibada.com/articles/37437/20150609/android-5-1-lollipop-release-news-lg-g2-mini-g.htm
Click to expand...
Click to collapse
While I honestly don't care for official updates, I would be gladly surprised if LG did give this device a 5.1 (hopefully 5.1.1) update.
On the other hand, the website seems like a clickbait site, so see if you can find a more reliable source.

Why shouldn't lg give 5.1? 5.1 falls in 2 year support cycle

Choristav said:
While I honestly don't care for official updates, I would be gladly surprised if LG did give this device a 5.1 (hopefully 5.1.1) update.
On the other hand, the website seems like a clickbait site, so see if you can find a more reliable source.
Click to expand...
Click to collapse
This phone was born with JB, we got KK and now LP
I think we wont get nothing else from official stock lg.
But Cyanogen,Paranoid,Aosp,Resurretion remix,Aicp,Slim,blisspop... And all stock modded and ports still under develop for years

In my opinion, the Lollipop 5.0.2 update brings some issues (like memory leaks, call problems) that can't be solved until the 5.1.1 update, so LG will probably be forced to push the 5.1.1 at some point in time. They can't leave their smartphones in a bad state for a last update.

Cst79 said:
In my opinion, the Lollipop 5.0.2 update brings some issues (like memory leaks, call problems) that can't be solved until the 5.1.1 update, so LG will probably be forced to push the 5.1.1 at some point in time. They can't leave their smartphones in a bad state for a last update.
Click to expand...
Click to collapse
And that's the reason I think LG will be update... Probably and hopefully.

Choristav said:
While I honestly don't care for official updates, I would be gladly surprised if LG did give this device a 5.1 (hopefully 5.1.1) update.
On the other hand, the website seems like a clickbait site, so see if you can find a more reliable source.
Click to expand...
Click to collapse
Ok I'll search more about...

JoeBro19 said:
Ok I'll search more about...
Click to expand...
Click to collapse
We need somebody here to report they in fact received this update.
LG needs to push a new set of code for us to look at.
This probably isn't true, otherwise the forums would be buzzing right now.

berryman13 said:
We need somebody here to report they in fact received this update.
LG needs to push a new set of code for us to look at.
This probably isn't true, otherwise the forums would be buzzing right now.
Click to expand...
Click to collapse
I didn't thought on that, you are right, the forum should have talked about that... But, let's think they didn't realize...

Screen gets black sometimes

Hi guys, my smartphone's screen gets black sometimes, and, after a quarter of second, it gets back. It's a Moto G Play (4th gen.). I want to unlock BL, root and change ROM too. But I'm scared about if it isn't a h/w issue.
If you can give me a hand, it'd be really appreciated.
Here's a logcat taken from the boot until 1 hour of activity reached: https://gist.github.com/FacuM/1bf3d99bf1c6c7dc4178051ab197074d
And here you can get a .zip packed version: https://gist.github.com/FacuM/1bf3d.../d2c32dcd9a3a30e28ae25e43d0c79f6427cda676.zip
Here, a logcat from when I wiped logcat until I opened a lot of apps with at least one black flashing: https://gist.github.com/FacuM/b72ae8c12bb50c5aebfec3c0eb3cf497
And here a .zip packed version: https://gist.github.com/FacuM/b72ae.../2e47f0cd8418ebda2c8522cac8b85b2bde826cdc.zip

If it gives us both any relief, I can confirm the issue - it's like the blink of an eye, so fast, quite rare and absolutely random. A quick Google search only hinted towards the Moto display function which might be the issue but I didn't disable it because it's one of the phone's killer features
So, I 've decided to wait for an app update or the Nougat update that's on the way (?) and see if it gets fixed - otherwise I will pay a visit to the local Moto service center in terms of guarantee

dbal said:
If it gives us both any relief, I can confirm the issue - it's like the blink of an eye, so fast, quite rare and absolutely random. A quick Google search only hinted towards the Moto display function which might be the issue but I didn't disable it because it's one of the phone's killer features
So, I 've decided to wait for an app update or the Nougat update that's on the way (?) and see if it gets fixed - otherwise I will pay a visit to the local Moto service center in terms of guarantee
Click to expand...
Click to collapse
Thanks for your answer. Basically, the problem as I see might be related to GBoard or Moto Display, as you say.
Also, I don't know if you've checked the logs I uploaded, but there are a lot of OMX decoding errors, I'm almost sure that there's no hardware failure there.
I'm now going to unlock Bl and see what's up with a custom ROM.
Sent from my Moto G Play (4th gen.) using Tapatalk
------
EDIT: Before proceeding, disabled Moto Display. Will give more feedback later.
Anyways, flashing again got the issue completely gone. Maybe your theory is the most appropriate.

Well, I wouldn't suspect Gboard because I 've noticed the thing days before I got it installed
I also don't vote towards hardware issue that's why I am not extremely eager to visit the service plus the fact that the issue happens 1-2 times a week and I almost forget it in the meantime
If you go for a custom ROM, this might shed some light whether it's firmware or app related and what we have to expect as a solution - don't forget to post some feedback after a few days testing
Let's see btw if anyone else posts here for having the issue as well

dbal said:
Well, I wouldn't suspect Gboard because I 've noticed the thing days before I got it installed
I also don't vote towards hardware issue that's why I am not extremely eager to visit the service plus the fact that the issue happens 1-2 times a week and I almost forget it in the meantime
If you go for a custom ROM, this might shed some light whether it's firmware or app related and what we have to expect as a solution - don't forget to post some feedback after a few days testing
Let's see btw if anyone else posts here for having the issue as well
Click to expand...
Click to collapse
BTW, I've already disabled Moto Display. I haven't fell asleep yet and it's 7 am here. Tomorrow I'll keep testing and hope it doesn't fail anymore. If not, I'll go for Bl unlocking and get rid of this Motorola's buggy attempt of softly modded AOSP.
Sent from my Moto G Play (4th gen.) using Tapatalk

Here I've uploaded a screencast of what appears to be related to the bug and shows clearly it's a software bug related to the video render in Marshmallow.
https://youtu.be/qhmUN43y0Pk
Sent from my Moto G Play (4th gen.) using Tapatalk

facuarmo said:
and shows clearly it's a software bug related to the video render in Marshmallow.
Click to expand...
Click to collapse
That's great news to know :victory: (since it's not hardware related and could be fixed in an updated firmware) but can you please elaborate a bit, how you prove this claim and this short video shows it?

dbal said:
That's great news to know :victory: (since it's not hardware related and could be fixed in an updated firmware) but can you please elaborate a bit, how you prove this claim and this short video shows it?
Click to expand...
Click to collapse
Sometimes, life's about taking the risk.
I've unlocked BL, flashed recovery and installed AOKP.
Now, no flickers found.
Prove:
https://youtu.be/T3e8-6dnyl0
Hope you like guys, and you take the risk too. Flashing a ROM solved everything.

Getting back to the thread after 2 weeks just to confirm your long testing now...is the bug still away or has reappeared somehow?
I am asking before I make the switch to LineageOS which seems a pretty good implementation of nougat

dbal said:
Getting back to the thread after 2 weeks just to confirm your long testing now...is the bug still away or has reappeared somehow?
I am asking before I make the switch to LineageOS which seems a pretty good implementation of nougat
Click to expand...
Click to collapse
I've compiled a kernel based on Squid2's sources with the fixed SELinux setup, then you should see no flickers so far in any ROMs.
Mine's working without any flicker, but I've only tested in Custom ROMs. Maybe you can try on stock?
https://forum.xda-developers.com/g4-play/development/kernel-somefeak-moto-g4-play-t3544556
Good luck and sweet flashes! :fingers-crossed:

Maybe an updated version of software by Google will fix the BLOD

Hello guys.
I live in South Korea and just had contact with customer service.
They said once my warranty is now passed, they might not be able to provide me a free repair, but google will soon release an update that is supposed to fix the BLOD(Boot Loop Of Death), so I'd better wait for it.
I don't know if it will work, but for me, and people having a phone which can't even get to recovery but only bootloader, who seem to have nothing to lose, this update will worth the wait.
Let's hope that's true and we can get our 6P back to life.

Didnt Google mentioned BLOD is a hardware issue earlier?

Aswin08 said:
Didnt Google mentioned BLOD is a hardware issue earlier?
Click to expand...
Click to collapse
Yeah. There's a news that Google said it's hardware problem, but Huawei did say the upcoming update will fix it.
IDK which one is truth.. just hoping simply updating software will fix it.

frostydawn said:
Yeah. There's a news that Google said it's hardware problem, but Huawei did say the upcoming update will fix it.
IDK which one is truth.. just hoping simply updating software will fix it.
Click to expand...
Click to collapse
If it's a software issue why does it happen with Marshmallow, Nougat and custom ROMs? I don't think Huawei is being honest.

jhs39 said:
If it's a software issue why does it happen with Marshmallow, Nougat and custom ROMs? I don't think Huawei is being honest.
Click to expand...
Click to collapse
Oh it didn't occured to me..
I also have some doubt that it's a software-related problem, because downgrading to MM doesn't even work.
Well, maybe they are fixing bugs that they haven't found before, or also maybe, the defective OS has triggered something..
I'm not sure that update will fix my phone, but for now, this is my last hope.

frostydawn said:
Oh it didn't occured to me..
I also have some doubt that it's a software-related problem, because downgrading to MM doesn't even work.
Well, maybe they are fixing bugs that they haven't found before, or also maybe, the defective OS has triggered something..
I'm not sure that update will fix my phone, but for now, this is my last hope.
Click to expand...
Click to collapse
Good luck but I honestly wouldn't get my hopes up too high. But you aren't the first person Huawei told this to. Hopefully there is something to it besides them trying to brush people off. I personally think people should file a class action suit against Huawai since the phone appears to be defective and it should last for more than a year given its premium price. I've never had a phone from HTC, LG or Samsung break, no matter how long I kept using them. I've never even heard of another phone that has all the issues the 6P does.

jhs39 said:
Good luck but I honestly wouldn't get my hopes up too high. But you aren't the first person Huawei told this to. Hopefully there is something to it besides them trying to brush people off. I personally think people should file a class action suit against Huawai since the phone appears to be defective and it should last for more than a year given its premium price. I've never had a phone from HTC, LG or Samsung break, no matter how long I kept using them. I've never even heard of another phone that has all the issues the 6P does.
Click to expand...
Click to collapse
Yeah I'm suspecting if there's an inherent hardware defects, and if that's the case, I think they should provide us a proper support like LG providing refund of Nexus 5x in US.
But, I'm not an expert and don't know what caused boot loop.
As I saw another person who may live in another country of mine, heard from Huawei that update will fix the problem, there may be something google is preparing for.
For now, there best thing I can do, is wait android 7.1.2 beta image.
If it won't work, that's a problem of then.
p.s. luckily I have unlocked bootloader, but considering boot looping devices can update their software only through unlocked bootloader, what should normal people having locked bootloader should do?

frostydawn said:
Yeah I'm suspecting if there's an inherent hardware defects, and if that's the case, I think they should provide us a proper support like LG providing refund of Nexus 5x in US.
But, I'm not an expert and don't know what caused boot loop.
As I saw another person who may live in another country of mine, heard from Huawei that update will fix the problem, there may be something google is preparing for.
For now, there best thing I can do, is wait android 7.1.2 beta image.
If it won't work, that's a problem of then.
p.s. luckily I have unlocked bootloader, but considering looping devices can update their software only through unlocked bootloader, what should normal people having locked bootloader should do?
Click to expand...
Click to collapse
Exactly, with those people have warranty expired and locked bootloader as well will have to throw it away?

Blod, I assume thats bootloader something something. Wish everyone would just write ..... Nevermind.

dontbeweakvato said:
Blod, I assume thats bootloader something something. Wish everyone would just write ..... Nevermind.
Click to expand...
Click to collapse
Battery life of death...

dontbeweakvato said:
Blod, I assume thats bootloader something something. Wish everyone would just write ..... Nevermind.
Click to expand...
Click to collapse
Sorry for not writing post in a way everyone can understand easily and using only abbreviation.
BLOD means Boot Loop Of Death

tigsandmitch said:
Battery life of death...
Click to expand...
Click to collapse
*Boot Loop of death

Hardware Issue
frostydawn said:
I don't know if it will work, but for me, and people having a phone which can't even get to recovery but only bootloader, who seem to have nothing to lose, this update will worth the wait. Let's hope that's true and we can get our 6P back to life.
Click to expand...
Click to collapse
If you have exhausted your warranty options, it's time to put the phone down and move on.

v12xke said:
If you have exhausted your warranty options, it's time to put the phone down and move on.
Click to expand...
Click to collapse
Maybe you're right.
I'm not sure if the update will fix my phone, and whether they meant 7.1.2 beta or officially update.
I also have a bad feeling that my phone won't back, but if this phone doesn't return, I have no choice but keep using my old-fashioned Nexus 5.
If the beta update doesn't fix it, maybe I'll just give up or give it a second chance for official update.. but for now, I can see some hope because Huawei said it to me.

There's some news about what I tried, but there ain't good things.
First, I downloaded N4F26O update(https://developers.google.com/android/images), which was uploaded in 2 days ago(Yeah, I only thought about 7.1.2 beta, abd didn't think about this) and installed it.
It didn't work.
So I contacted with Huawei and Google's consumer care center.
Huawei said, to talk about softwares, I should contact with Google.
Google said, they didn't receive any plan of the update which is supposed to fix boot loop. I got confused, since a days ago, Huawei once did say there will be that update.
They also said, if I have a secondary phone, I'd better use that phone and see if the update will be released and fix my phone.
So... I didn't gain anything. Google and Huawei both said they can't assure the update will fix the bootloop, and the only clear solution is to change its motherboard.
Well, I won't give up, at least unti thel 7.1.2 beta's release, but I'm tired and for now, have nothing to do.
I'll just wait for the 7.1.2 beta.
I'll just keep waiting...

If you feel compelled to support, and bring attention to this issue.
https://www.change.org/p/google-inc...utm_source=share_petition&utm_medium=copylink

frostydawn said:
There's some news about what I tried, but there ain't good things... I'll just keep waiting...
Click to expand...
Click to collapse
Since you have nothing to lose, why not try this while you are waiting. I would direct any questions you have about this method to the dev.

v12xke said:
Since you have nothing to lose, why not try this while you are waiting. I would direct any questions you have about this method to the dev.
Click to expand...
Click to collapse
But that's seems to be for devices that's stuck in EDL mode.
I still can access bootloader, so thank you for your advice, but that seems to not work.

I'm afraid that you'll have to let this go.. Huawei is know for telling customers BS on the phone. Even the warranty repair center sucks. They downgrade people their phones and say that the battery issue is now resolved. It really is a shame, but they don't give a rat's *ss about you or any other customer who has already paid for the product.