Develop Bugs

[Q] LG G3. First steps. Shutdown bug.

Model
LGD855
ADEUTN (32GB)
Build number
KVT49L.A1401987978
Software version
V10a-EUR-XX
--
Hi all,
it has been a pair of weeks with this phone and i'm experiencing the shutdown bug described at:
LG G3 D855 shutsdown on its own
http://forum.xda-developers.com/lg-g3/help/lg-g3-d855-shutsdown-t2803292
about 4 times during this time. Also, when unlocking the device, the display doesn't light up when it's knocked but it does when power button is pressed, (roughly 30 percent of tries).
It's not rooted and I haven't flashed any mods/scripts/themes: it's full stock.
I decided to buy it when I knew the bootloader was finally unlocked. I plan to root it and possibly flash other roms sometime but my main worries now are:
- be sure the hardware is working properly before it's too late to return it.
- keep the bootloader stack unlockable.
- don't void the warranty.
Is this a software only problem? Can I fix it with an update?
After reading quite a few posts on the referred thread, there's no a clear answer to that question in my opinion. It's said that it's a hw problem (no sources by the way):
http://forum.xda-developers.com/showpost.php?p=57346459&postcount=1343
but it's also said that it's fixed with an update:
http://forum.xda-developers.com/showpost.php?p=54530196&postcount=679
(google translate: http://translate.google.com/transla...ehebt-plotzliche-abschaltung-des-smartphones/)
Is there any hardware revision of this device? Is there any way to get the manufacture date (or week)?
Is there any new-device-test procedure? Possibly by using the LG hidden menu? Or by testing each device capability? (is it that simple?)
Thanks for your help,

Yoyonovich said:
Model
LGD855
ADEUTN (32GB)
Build number
KVT49L.A1401987978
Software version
V10a-EUR-XX
--
Hi all,
it has been a pair of weeks with this phone and i'm experiencing the shutdown bug described at:
LG G3 D855 shutsdown on its own
http://forum.xda-developers.com/lg-g3/help/lg-g3-d855-shutsdown-t2803292
about 4 times during this time. Also, when unlocking the device, the display doesn't light up when it's knocked but it does when power button is pressed, (roughly 30 percent of tries).
It's not rooted and I haven't flashed any mods/scripts/themes: it's full stock.
I decided to buy it when I knew the bootloader was finally unlocked. I plan to root it and possibly flash other roms sometime but my main worries now are:
- be sure the hardware is working properly before it's too late to return it.
- keep the bootloader stack unlockable.
- don't void the warranty.
Is this a software only problem? Can I fix it with an update?
After reading quite a few posts on the referred thread, there's no a clear answer to that question in my opinion. It's said that it's a hw problem (no sources by the way):
http://forum.xda-developers.com/showpost.php?p=57346459&postcount=1343
but it's also said that it's fixed with an update:
http://forum.xda-developers.com/showpost.php?p=54530196&postcount=679
(google translate: http://translate.google.com/transla...ehebt-plotzliche-abschaltung-des-smartphones/)
Is there any hardware revision of this device? Is there any way to get the manufacture date (or week)?
Is there any new-device-test procedure? Possibly by using the LG hidden menu? Or by testing each device capability? (is it that simple?)
Thanks for your help,
Click to expand...
Click to collapse
I would suggest going ahead and rooting and Bump'ng your device and installing a pre-rooted, updated custom rom afterwards. You are on software revision 10a, the first oke released and it was full of bugs like this. As far as I know, the shutdown bug has long since been fixed as there has been multiple updates since 10a.

acparker18 said:
I would suggest going ahead and rooting and Bump'ng your device and installing a pre-rooted, updated custom rom afterwards. You are on software revision 10a, the first oke released and it was full of bugs like this. As far as I know, the shutdown bug has long since been fixed as there has been multiple updates since 10a.
Click to expand...
Click to collapse
Thanks for your fast response.
Am I voiding the warranty by doing this?
What if I do it and the shutdown problem persists (is hardware related)?
Thanks again,

acparker18 said:
I would suggest going ahead and rooting and Bump'ng your device and installing a pre-rooted, updated custom rom afterwards. You are on software revision 10a, the first oke released and it was full of bugs like this. As far as I know, the shutdown bug has long since been fixed as there has been multiple updates since 10a.
Click to expand...
Click to collapse
I have a 16gb white 20e version, and the shutdown problem is still here when taking pictures with flash o using gps, so I think only possible solution is LG support or selling the phone.

Yoyonovich said:
Thanks for your fast response.
Am I voiding the warranty by doing this?
What if I do it and the shutdown problem persists (is hardware related)?
Thanks again,
Click to expand...
Click to collapse
Yes you are. But using the LG flashtool to return to,stock leaves no trace of root and they will take it back under warranty no problem.

Has Anyone Bricked the Device on 5.0.2 that manually flashed a factory image?

As the title states, has anyone's 2013 n7 bricked after the 5.0.2 update when flashing a factory image instead of the OTA? Mine bricked after taking the 5.0.1 OTA, but i now have it back from Asus after repair and am wanting to flash the factory image to 5.0.2. However, if anyone has experienced bricking as a result of this (or 5.0.1 or 5.0) being flashed and not just the OTA, which we know is bricking devices, then I will stick with 4.4.4 for now.
Thanks

You can not brick a Nexus 7 unless you somehow screw up the bootloader and can no longer enter the bootloader.

khaytsus said:
You can not brick a Nexus 7 unless you somehow screw up the bootloader and can no longer enter the bootloader.
Click to expand...
Click to collapse
Well then some form of that must be happening due to or in very strange coincidence with the 5.0, 5.0.1, and 5.0.2 updates - just ask those of us whose tablets turned off only to turn on and be stuck at the google logo with so far zero solution for fixing it other than a hardware replacement. My tablet was at ASUS's repair factory for almost a month and had the motherboard replaced. This was after a "successful" OTA update to 5.0.1 that worked for a few days and then died. This has happened more than just infrequently to many members on here recently.
So what I would like to know is is anyone experienced the same "successful update" and then a few days later a dead tablet via factory image flashingof 5.0+. We already know that taking the OTA to 5.0+ might be a problem, and before I flash up to 5.0.2 I'd like to hear if anyone did a manual factory image flash and still had the die a few days later issue, despite not going via OTA.

Norcalz71 said:
Well then some form of that must be happening due to or in very strange coincidence with the 5.0, 5.0.1, and 5.0.2 updates - just ask those of us whose tablets turned off only to turn on and be stuck at the google logo with so far zero solution for fixing it other than a hardware replacement. My tablet was at ASUS's repair factory for almost a month and had the motherboard replaced. This was after a "successful" OTA update to 5.0.1 that worked for a few days and then died. This has happened more than just infrequently to many members on here recently.
So what I would like to know is is anyone experienced the same "successful update" and then a few days later a dead tablet via factory image flashingof 5.0+. We already know that taking the OTA to 5.0+ might be a problem, and before I flash up to 5.0.2 I'd like to hear if anyone did a manual factory image flash and still had the die a few days later issue, despite not going via OTA.
Click to expand...
Click to collapse
I don't understand the obstinance regarding official LP flashing. OTA has been pulled from the shelf, lots have killed their devices with it, so it's obvious something seriously wrong is going on. I've been flashing CM and other custom roms derived from LP without problems. Why insist on incantations? This is not the first time Asus screws up with its firmwares! LP ain't nothing special that's worth it.

graphdarnell said:
I don't understand the obstinance regarding official LP flashing. OTA has been pulled from the shelf, lots have killed their devices with it, so it's obvious something seriously wrong is going on. I've been flashing CM and other custom roms derived from LP without problems. Why insist on incantations? This is not the first time Asus screws up with its firmwares! LP ain't nothing special that's worth it.
Click to expand...
Click to collapse
So you are saying LP Roms/factory images should be just fine, provided they don't go OTA? I'm sure most are, my concern is if anyone has experienced a failure hours/days after flashing to LP

Norcalz71 said:
So you are saying LP Roms/factory images should be just fine, provided they don't go OTA? I'm sure most are, my concern is if anyone has experienced a failure hours/days after flashing to LP
Click to expand...
Click to collapse
Given previous experiences with Asus JB on another model, I'd avoid anything "official" like the plague, and wait till major bugs are swatted. Clearly, I'm not saying "LP Roms/factory images should be just fine." But I've been flashing custom roms based off LP, and nothing out of the ordinary has happened. They work fine. What I don't get is people would insist on flashing the crappy OTAs Asus has been putting out in the face of so much bricking.

Asus doesn't put out updates for the N7; Google does.

Telyx said:
Asus doesn't put out updates for the N7; Google does.
Click to expand...
Click to collapse
I don't see the difference. Just because Google funded and marketed the device doesn't make it less Asus. An Asus is an Asus is an Asus, whether you buy it at Staples or in China. I seriously doubt the firmwares are 100% (or 10% for that matter) Google unless one can prove to the world otherwise.

I haven't bricked mine, and I manually updated using the 5.0.1 (and then 5.0.2) image on Google's site. However, I also have an unlocked boot loader (It was unlocked about an hour after we got it home, and hasn't been locked since) and modified /system partition. I have always manually updated the software images from fastboot.

You're saying Asus makes aosp? No. Google makes the software for nexus devices.
Asus assembled the hardware. Google makes the software (aside from proprietary drivers, of which Asus made only audio and "sensors").
Asus has very little to do with the n7 aside from the fact that they put it together.

jshamlet said:
I haven't bricked mine, and I manually updated using the 5.0.1 (and then 5.0.2) image on Google's site. However, I also have an unlocked boot loader (It was unlocked about an hour after we got it home, and hasn't been locked since) and modified /system partition. I have always manually updated the software images from fastboot.
Click to expand...
Click to collapse
Mine will remain unlocked from now on. I took it from 4.4.2 back to 4.4.4 (since after repair it was back to original and wiped) via fastboot, and will probably wait awhile longer to update it via fastboot to 5.0.2. No more OTA for me though.

Problem with RETEU firmwares on chinese ADDISON_RETCN (XT1635-03)

I have tried to update my chinese XT1635-03 to 7.1.1 with OTA through ADB sideload and unfortunately it is not working.
I have sucessfully flashed the phone with reteu latest firmware with April security patch (ADDISON_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) through fastboot.
But once I try to sideload 7.1.1 OTA (Blur_Version.26.1.22.addison.retail.en.US) the process terminates at 47% with notification that the package expects product name "addison" but actual value is "addison_retcn"
Is it possible to either change the product name or disable such check of product name? It seems to me, that at the moment there is no way to flash OTA and I need to wait for full 7.1.1 image.

Reading similar questions around, I have to ask. Why you people cannot wait couple of weeks to get OTA? Instead of risking to brick your device?
New update is not bringing revolutionary/awesome/amazing/mind blowing... new features. I understand if it's update to completely new Android version or that your device/region will not get update at all.
Sent from my XT1635-02 using Tapatalk

You have XT1635-03 and the update is for XT1635-02. So if you have a reteu phone you can really update over sideload without issues. And yes, I need android 7.1.1 and I wouldn't wait one day longer. I need app-shortcuts, because I had this on my old phone, too. There was android 7.1 since the first day. But if you don't have it before you can't miss it. So you can wait much easier For me it was important for other issues, too. For example Wifi problems and stability fixes and over 100 security fixes. Many reasons for the update
Edit: And one more reason for the update: To help google to get more than 0.6% for android 7.1 We should update all, otherwise android 7.1 will never get 1%
Everybody should help to get this 1% maybe next month. So update, just do it for the 1%, yes xD
:silly::good:

The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.

freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
The point is, how can you change the channel...

freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
OK, makes sense for you but for many/most others is just matter of time.
I'm not blaming anyone. Do whatever you want with your phone, just be ready if something goes wrong

The surprise was a different phone name. Different channel is usually not a problem

freeman_g said:
The surprise was a different phone name. Different channel is usually not a problem
Click to expand...
Click to collapse
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED

flashallthetime said:
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED
Click to expand...
Click to collapse
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?

allrightlite said:
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?
Click to expand...
Click to collapse
I have no idea

flashallthetime said:
I have no idea
Click to expand...
Click to collapse
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.

allrightlite said:
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.
Click to expand...
Click to collapse
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.

dandrumheller said:
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.
Click to expand...
Click to collapse
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.

allrightlite said:
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.
Click to expand...
Click to collapse
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.

dandrumheller said:
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.
Click to expand...
Click to collapse
It feels not like a beta. It's more like a big bug fix with much patches. For example my Wifi is now stable as hell and never reconnections anymore. Hope it keeps stable, but looks very very good. I think this beta will be the final release in few months, or weeks? But it's much better than 7.0. And better than LOS14.1, which is not so stable (on my other phone). And I have no app crashes anymore. Gboard was crashing with 7.0 one time and few other apps like firewall. So, 7.1.1 is pure stable as hell and must have :laugh:

Afaik, it's not beta. It's​ soak. So, if test users reported as stable, it will be pushed to all as the final build. If not, Moto has to fixed and not all users around the world will be affected.
Regular and recommend way of releasing update.
Sent from my LG-V940n using Tapatalk

Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:

If you are on XT1635-03 with reteu frmware you will not receice any OTA. My experience told that you can't even sideload an update. So no worry about bricks.
Very often devices are hardbricked when you are downgrading bootloader but once I have hardbricked my Nexus 6 with OTA (sideloading it). Well, it was not full brick, but I can't load the system (only fastboot) and my bootloader was locked. Without system loaded you can't allow unlocking procedure so the first thing I do with new phone is unlocking.

allrightlite said:
Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:
Click to expand...
Click to collapse
I know the build is not a beta. I'm referring to the fact that once you leave the official upgrade path, taking any update is a scenario not tested by Moto. So you are testing for them. Maybe you win, maybe you brick.

It seems that the problem with "addison_retcn" may be fixed with editing build.prop but in this case systemless root is required (AFAIK there us no systemless root for Nougat)

Question related to "After updating, you will not be able to downgrade..." message

Question related to "After updating, you will not be able to downgrade..." message
Hope you guys are safe and well.
Currently my A50 on August update. I have no problems with this update but I like to update to Android 10 for additional features. I'm reluctant to update because of this message. I'm afraid that if I had problems or something wrong with the new update, I won't be able to go downgrade to August update.
So, Is it really impossible to downgrade using Odin with an official firmware?
I'm coming from iOS and hence the fear of updating. As you may know, iOS downgrade is impossible when Apple sign-out the old software.
Thanks in advance.

Most major OS updates (i.e. from Android 9 to 10) also update the 'bootloader', which is a little piece of software that initializes your device, and runs before the system can even start (when you turn your phone on).
Once the bootloader is updated, it's often impossible and certainly not recommended to downgrade the OS, since you may permanently brick your device.
If Android 10 is out for your device model (eg. A505G in my case), just go ahead and update. I don't have any issues with it whatsoever, in fact it has fixed quite a few bugs (wifi connection would frequently drop for me in Pie with February/March updates, and now it doesn't anymore).
Greetings.

pripyaat said:
Most major OS updates (i.e. from Android 9 to 10) also update the 'bootloader', which is a little piece of software that initializes your device, and runs before the system can even start (when you turn your phone on).
Once the bootloader is updated, it's often impossible and certainly not recommended to downgrade the OS, since you may permanently brick your device.
If Android 10 is out for your device model (eg. A505G in my case), just go ahead and update. I don't have any issues with it whatsoever, in fact it has fixed quite a few bugs (wifi connection would frequently drop for me in Pie with February/March updates, and now it doesn't anymore).
Greetings.
Click to expand...
Click to collapse
But can't I backup the boot loader too? Also, I heard that the official firmware includes the boot loader and therefore I won't have problems downgrading. I'm confused.

Screen not responding after update
Hi. I updated to the new Android 10 which my phone prompt me to install. But after updating, my screen is not responding anymore. I already tried to restart and factory reset. What can i do regarding this? Thank you very much!

sheidyly said:
Hi. I updated to the new Android 10 which my phone prompt me to install. But after updating, my screen is not responding anymore. I already tried to restart and factory reset. What can i do regarding this? Thank you very much!
Click to expand...
Click to collapse
Try to flash the ROM manually using ODIN

redymedan said:
Try to flash the ROM manually using ODIN
Click to expand...
Click to collapse
I'm sorry but I'm new to all of this and I seem to read some comments saying the phone was bricked after flashing.
And if I will try flashing, do I use the old firmware or the new one?
Thank you so much!

mistpsn said:
But can't I backup the boot loader too? Also, I heard that the official firmware includes the boot loader and therefore I won't have problems downgrading. I'm confused.
Click to expand...
Click to collapse
I think... and I could be completely wrong, but it keeps track of the highest version of bootloader you installed. So it will not allow you to boot if you flash the older one. However, I am not sure how it behaves if the bootloader is unlocked.

If anyone have the same concerns I had. I found out that only security updates seems to have this message and risk bricking your phone in case you downgrade to lower version. Some people confirms that they were able to downgrade without any problems from android 10 to android 9 on their A50.
It also made sense that there are no problems since the warning message only included with security updates. The android 10 Update change list have no warnings related to downgrading to older versions.
March security update had the warning message. And I had to do the security upgrade before the android 10 update was available OTA.

Question Fold 3 Issues after Android 12 update

Hi everyone,
My Fold 3 started showing wierd sympotoms after Abdroid 12 update however I thought they might get fixed with the next upgrade. Last night I received Android 13 upgrade but to my surprise the issues with my phone stayed same.
My phone is official, no rooting or bootloader unlocking. Knox tripping is 0x0. The same result is shown by the Diagonostics in Members app.
My employer needs me to install work profile that this phone is not allowing and throwing an error saying I have a custom OS. I cannot boot into the bootloader from the recovery menu and getting a smart select error. Moreover I cannot login to Samsung Pay (stuck at fingerprint authrized) and Samsung Pass (Currently not available error: 162)
I have added all the possible screen shots for ready reference.
Can you please advise as what can I do to fix this annoyance! Many thanks in advance

try reflash latest official rom with full data erase

AndrOmega said:
try reflash latest official rom with full data erase
Click to expand...
Click to collapse
Thx for ur reply. I tried doing this already. Situation remains same.

It isn't Maas360 that you are trying to install by chance?

imapfsr said:
It isn't Maas360 that you are trying to install by chance?
Click to expand...
Click to collapse
I am not aware of Maas360!

Can anyone with knowledge help as I need to setup my office profile urgently. My second phone is acting up...

If your phone is not modified in any way, then I would go straight to Samsung. Someone here might be able to help, but in cases like this, Sammy might be your best bet.

Its not modified however Samsung wants to change the mother board and charge big as its out if warranty.
Thats the reason I turned to the community as I have got many issues fixed from the wonderful people that Sammy wanted to charge otherwise.

Update your Google services. Says July, last is October!