Develop Bugs

So don't update to 4.4.2?

Plugged in my Z1c to my Mac and now I have an update ready for me. Im assuming its for KitKat. But I have read a lot of threads saying there are a lot of problems. So should I just stay on Jellybean then? Will these problems be fixable by another update if Sony does respond to these problems? If not i'll be staying on 4.3 for a while then. ha

I dont have any issue with 4.4.2
Sent from my D5503 using Tapatalk

choboii said:
Plugged in my Z1c to my Mac and now I have an update ready for me. Im assuming its for KitKat. But I have read a lot of threads saying there are a lot of problems. So should I just stay on Jellybean then? Will these problems be fixable by another update if Sony does respond to these problems? If not i'll be staying on 4.3 for a while then. ha
Click to expand...
Click to collapse
Everything is fixable by Sony, should they wish to do so
That said, I've been running KitKat (UK unbranded) for a week now without the kinds of issues reported by others - only the crackling notifications, but I can live with those and it's pretty certain Sony will fix that sooner rather than later. So YMMV.
I'm new to Sony phones, but tbh this kind of rigmarole over updates has been the same with *every* Android OEM I've been with so far. HTC even pulled their KK update for the One Mini within days because of its bugs, and over a month later they still haven't put out a fixed version ... hopeless.

I am since sunday with the KK and no issues at all, my battery runs ok, ram memory got better and phone calls and camera no problem.
i made by OTA with no wipe. for me looks prety safe, i think most people who run in some problem are those who unlock bootloader or mod the phone.
I am not rooted or so, waiting a good reason to do it(4K video recording could be one)

Imaeda said:
I am since sunday with the KK and no issues at all, my battery runs ok, ram memory got better and phone calls and camera no problem.
i made by OTA with no wipe. for me looks prety safe, i think most people who run in some problem are those who unlock bootloader or mod the phone.
I am not rooted or so, waiting a good reason to do it(4K video recording could be one)
Click to expand...
Click to collapse
I see. Then I might update since I am not rooted or have an unlocked bootloader either.

choboii said:
I see. Then I might update since I am not rooted or have an unlocked bootloader either.
Click to expand...
Click to collapse
I just think this maybe is cause the problem of most people here, my opnion, the only one i ocasianly have is that when I answer a phone call auto go to loudspeaker, but i had that so often with 4.3 that had with 4.4 looks the same(some people say to disable chrome thats dont happen anymore)
auto mode was a catastrophe already on 4.3. my batery is runing good and i play dead trigger 2 and GTA with no lag.
for me, personaly, the update is ok

Until now i didn't find any bugs, what i did was... updating to 4.4 and after install it i did a factory reset. It runs smoothly with no problems until now.

All of those have "NO" problem with KK bug, short survey below.
Are you: -
1. Rooted?
2. Unlocked Bootloader?
3. OTA update?
4. PCC update?
5. Factory Reset after update?
6. Flash using flashtool?

thermalboyz said:
All of those have "NO" problem with KK bug, short survey below.
Click to expand...
Click to collapse
Are you: -
1. Rooted? NO
2. Unlocked Bootloader? NO
3. OTA update? NO
4. PCC update? NO
5. Factory Reset after update YES
I flashed the UK unbranded with Flashtool. This option should be added to your list.
I do have crackling notifications though - although strangely only with the Sony supplied ones, the Hangouts sounds are always fine. The ways of Sony are mysterious

So I upgraded to KitKat. Seems fine right now except my camera freezes. Any fix around this?

choboii said:
So I upgraded to KitKat. Seems fine right now except my camera freezes. Any fix around this?
Click to expand...
Click to collapse
How did you update?

zxz0O0 said:
How did you update?
Click to expand...
Click to collapse
I used the Sony Bridge for Mac.

[Q] Update Kernel only from newer oficial firmwares

Hi,
as my D855 is on V10h-EUR (just released yesterday...), while I can see there are newer one (eg. V10j) I'm thinking (due to the eg. hissing sound issue, buzzing sound during calls while on GSM mode, lags.. I'm really tired of waiting, phone returned from warranty repair with confirmed repair while the issue is still present etc.) to take out only Kernel and flash it on current ROM. While our bootloaders are still locked out, is there some way how to take out Kernel only from newer versions and "update" it ? Or it's not possible at all due to the locked bootloader. Eg. even with tethered TWRP or using ? Normally LG Suite should debrick potential Kernel issue, or ?
I do not want to flash completely another ROM due to the potential impact on warranty (eg. not sure if the region "code" will come back after FW reflash) and re-installing everything from scratch.
Thanks for your ideas.

Btw, can someone provide me from latest "i" firmware all files :
/system/etc/mixer_paths*.xml (all 3 files)
/system/etc/media_profiles.xml
/system/etc/media_codecs.xml
...just wondering if this could fix hissing sound, or if LG has updated there something. I guess there was a temporary fix for LG G2 using mixer_paths.xml, but it's a guess only....

Just do a normal flash with latest v10j global version, it's almost the same as an ota update! No root needed, no warranty issues!

You probably mean flashing D85510I_00.kdz using LG Flash? Settings will be lost completely, right ? Thank you.

Doesn't matter, installed latest version as stated above using LG Flash 2014 (full wipe) and still getting the same issues....so either it's not SW issue or phone is broken and will not get fixed.

V10i kill the Batt. in my opinion if Yu will install a kdz u shoyld take the 10j it's So Good ..
Sent from my LG-D855 using XDA Free mobile app

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.

HELP! T-Mobile G3 - Can't Upgrade to Lollipop Via OTA or LGMobile Support Tool

Hi everyone! I need some help or guidance here. I think I may know why this is happening but not sure . I'll explain in detail below:
Anyway, so the long awaited Lollipop was apparently released on April 7th for the T-Mobile LG G3. I've been waiting for it for a while just as many other probably have been. Well, none of the updates ever showed up on my phone via OTA or the LGMobile Support Tool.
The only thing I can think of as to why this MIGHT be happening to me (unless nobody else has been able to update yet because T-Mobile delayed the update) is because my IMEI has been reflashed to a Galaxy Note 2. However, I'm not sure that a different IMEI on my phone would prevent it from being updated since the firmware is obviously still a D851 LG firmware...
My phone is NOT rooted. It's all stock by the way.
Anyway, I guess what I need to know is:
1) Has everyone else with the T-Mobile Lg G3 been able to successfully update to Lollipop yet?
2) Will the different IMEI on my phone affect whether or not my phone is detectable as a D851 G3?
Thanks everyone in advance!

Bump. Anybody?

I'm really not sure that IMEI have any effect on the update center , have you tried to do a factory reset ?
another thing I can think of is just root your device and install a stable fast stock rom that uses LP on it ( like cloudy ).

MrFishiz said:
I'm really not sure that IMEI have any effect on the update center , have you tried to do a factory reset ?
another thing I can think of is just root your device and install a stable fast stock rom that uses LP on it ( like cloudy ).
Click to expand...
Click to collapse
Yeah I'm not sure it does either. I talked to a friend of mine that works at T-Mobile and he said a mismatched IMEI shouldn't make a difference. However, worst case scenario I'll have to manually flash it to Lollipo once the official ROM has been uploaded somewhere on the internet. I haven't tried to do a factory reset. Not positive on this but I think the IMEI is stored in memory that won't change whether it's factory reset or not especially since the original one was wiped and replaced.
I'll try to stick to the stock ROMs on this phone to avoid any issues with the custom stuff. Although, I was never able to successfully tether via WiFi on this phone. It works via USB cable. Still annoying hehe.

SaMirakle said:
Yeah I'm not sure it does either. I talked to a friend of mine that works at T-Mobile and he said a mismatched IMEI shouldn't make a difference. However, worst case scenario I'll have to manually flash it to Lollipo once the official ROM has been uploaded somewhere on the internet. I haven't tried to do a factory reset. Not positive on this but I think the IMEI is stored in memory that won't change whether it's factory reset or not especially since the original one was wiped and replaced.
I'll try to stick to the stock ROMs on this phone to avoid any issues with the custom stuff. Although, I was never able to successfully tether via WiFi on this phone. It works via USB cable. Still annoying hehe.
Click to expand...
Click to collapse
There is already a firmware on the forum: http://forum.xda-developers.com/showthread.php?t=2785089
I don't know if you can do this guide though since you never rooted your phone, better if you ask there.

MrFishiz said:
There is already a firmware on the forum: http://forum.xda-developers.com/showthread.php?t=2785089
I don't know if you can do this guide though since you never rooted your phone, better if you ask there.
Click to expand...
Click to collapse
Thanks for the link. I don't think the OP has the D851 Lollipo version uploaded. I only saw it for D855. I guess I'll just wait until everyone else gets the official update and flash it manually. From what it sounds like people have been having issues minor issues with Lollipop anyway. Maybe that's why T-Mobile is delaying the OTA updates. Who knows

Latest Android 10 update Error PCB / Battery

Please,Don't upgrade you device firmware
Similar problem arose like before with initial global releases of Samsung ..
After suspending the update roll out but still some devices are receiving the update with a small code error and unable to communicate properly with PCB results in
Bootloop unable to fix this issue
Though this issue is resulting to a small niche of users
Developer recommend those few users can wait till some official notification is released
Or Users can try manually downgrading SYSTEM
(Keep nand backup since HOME CSC won't work due to encryption except you can restore data later after device is successfully reset)
Direct Link to Stock SM-705G (official only for units manufactured in India)
https://dl2018.sammobile.com/NV9ZRi...ERdVg../A705GMDDU5ATA1_A705GMODM5ATA1_INS.zip
Instruction to Odin Flash (in case)
https://www.sammobile.com/samsung/galaxy-a70/firmware/SM-A705GM/INS/download/A705GMDDU5ATA1/312540/

We already know this

Bugz1 said:
We already know this
Click to expand...
Click to collapse
I knew about this since previous update and this April security patch really f**ked bad
Fair Warning ...
P.S data lost

Abish4i said:
Please,Don't upgrade you device firmware
Similar problem arose like before with initial global releases of Samsung ..
After suspending the update roll out but still some devices are receiving the update with a small code error and unable to communicate properly with PCB results in
Bootloop unable to fix this issue
Though this issue is resulting to a small niche of users
Developer recommend those few users can wait till some official notification is released
Or Users can try manually downgrading SYSTEM
(Keep nand backup since HOME CSC won't work due to encryption except you can restore data later after device is successfully reset)
Direct Link to Stock SM-705G (official only for units manufactured in India)
https://dl2018.sammobile.com/NV9ZRi...ERdVg../A705GMDDU5ATA1_A705GMODM5ATA1_INS.zip
Instruction to Odin Flash (in case)
https://www.sammobile.com/samsung/galaxy-a70/firmware/SM-A705GM/INS/download/A705GMDDU5ATA1/312540/
Click to expand...
Click to collapse
This has already been fixed, updating to stock Android 10. The first release had the battery issue and was hard bricking the a70, samsung suspended the update and rolled out a new fixed android 10 update. Alls good now.

MarvinMod said:
This has already been fixed, updating to stock Android 10, samsung suspended.
Click to expand...
Click to collapse
I am talking abt the update one somewhere around 26-04
it was supposed to be the one with patch but that update corrupted itself ...:good:

[/COLOR]
Abish4i said:
I am talking abt the update one somewhere around 26-04
it was supposed to be the one with patch but that update corrupted itself ...:good:
Click to expand...
Click to collapse
Im saying, the issue with pcb is fixed. Try downloading the update now and flash. Fyi, you cant downgrade from 10 to 9 once you have updated to 10. Samsungs efuse will be triggered. It's been said that a device affected with the PCB bug is hardbricked, however, that is not entirely true.

MarvinMod said:
[/COLOR]
Im saying, the issue with pcb is fixed. however, that is not entirely true.
Click to expand...
Click to collapse
This was for people who might have bricked their devices and are looking for a workaround to successfully fix bootloop boot (same happened to me)
Since due to lookdown a lot of us can't visit customer support for same.
FYI officially you can downgrade without breaking efuse

Abish4i said:
This was for people who might have bricked their devices and are looking for a workaround to successfully fix bootloop boot (same happened to me)
Since due to lookdown a lot of us can't visit customer support for same.
FYI officially you can downloadgrade without breaking efuse
Click to expand...
Click to collapse
Efuse is popped during an update not a downgrade. Idk if ota pops it but i know updating with odin sure does and no, once the efuse is provisioned, there is no going back. If you or anyone else has found a way besides opening the device and making jumpers, please explain or provide links.

Device never went to 10 since the update with 10 has this error to ppl can still switch back to 9 hassle-free.

Thx for heads up!
Overall, Android 10 upgrade was a big disappointment for me, and pushed towards rooting it first, and then to installing LineageOS 17.1.
So, after rooting I disabled auto updates as I knew things can go bad.
But now I'm lucky LOS user!

I flashed my A705MN using Odin to get around the bootloop and it worked but now my wifi and bluetooth doesn't turn on. -_- I'm kinda new at this flashing business. How can I activate them both again?

MarvinMod said:
This has already been fixed, updating to stock Android 10. Alls good now.
Click to expand...
Click to collapse
Not good yet ;
I did some research with certified service centres this problem can't be fixed with software though it can be fixed with as a manual upgradation of PCB board is required

Ultrachamo said:
I flashed my A705MN using Odin to get around kinda new at this flashing business. How can I activate them both again?
Click to expand...
Click to collapse
If still error do following
Are you sure abt manufacturing unit place of origin is India it's fine ... Still if you used HOMECSC and it worked
you need to format it first thing in​
If not manufactured in India Search for country origin specific file ... for odin flash

Why does this count as "development"?

DroidGTV said:
Why does this count as "development"?
Click to expand...
Click to collapse
Idk maybe it cuz the bug is related to PCB bridge code error in software which might be fixed with either downgrading FW ver or Hardware upgradation...