5.1 speakerphone bug - fixed by bootloader?

Since 5.1 lollipop, I've had the 'speakerphone bug' (cannot switch to/from speakerphone once call has been established) using stock Motorola roms. I have, however, read that the speakerphone works perfectly for some people using stock roms. I am guessing that my bootloader version is the problem (doesn't seem intuitive), and I would like to confirm that it works before I update my (old) bootloader. Can anyone conclusively confirm that the following environment works and does not have the 'speakerphone bug'?

• unlocked


• flash full ATT xt1058 5.1 rom from SBF except recovery.img


• rooted with supersu

For what it is worth, I tried the following combinations:
- ATT xt1058 5.1 from SBF with ATT 5.1 NON-HLOS.BIN + FSG.mbn = speakerphone bug (flashed everything except motoboot.img, gpt.bin and recovery.img)

- Brazilian xt1058 5.1 retail from proxuser's TWRP backup (/system and boot.img, thanks proxuser):

• with ATT 4.4.4 modem = speakerphone bug


• with ATT 5.1 modem (NON-HLOS.bin) from SBF = bootloop


• with ATT 5.1 modem (NON-HLOS.bin + FSG.mbn) from SBF = bootloop


• with Brazilian 5.1 modem (NON-HLOS.bin) from SBF = bootloop


• with Brazilian 5.1 modem (NON-HLOS.bin + FSG.mbn) from SBF = bootloop

- Brazilian xt1058 5.1 retail from update.zip made from SBF (/system and boot..img flashed with TWRP):

• with ATT 4.4.4 modem = speakerphone bug


• with ATT 5.1 modem (NON-HLOS.bin) from SBF = bootloop


• with ATT 5.1 modem (NON-HLOS.bin + FSG.mbn) from SBF = bootloop


• with Brazilian 5.1 modem (NON-HLOS.bin) from SBF = bootloop


• with Brazilian 5.1 modem (NON-HLOS.bin + FSG.mbn) from SBF = bootloop

- Brazilian xt1058 5.1 retail from SBF using fastboot = error when flashing system.img (sp space is not enough)

I always 'fastboot erase modemst1 and modemst2.
I always cleared cache and wiped dalvic.
I tried erasing all useradata at least once.


thanks!

Bootloop not fixed by flashing TWRP backup

I flashed a CM12.1 nightly on top of one that was a couple days old, and it wasn't playing nice. This was through CM's internal update function, which sets a recovery script and reboots into recovery to install it (which BTW failed).

So I went into TWRP and flashed it back to the backup I made not a couple hours earlier. But now I have kind of a bootloop. Most of the time, just the LG logo shows up, then it reboots back into recovery. One time it got stuck on the logo, and I was able to see it with ADB but it told me init.sh was missing if I tried to adb shell into it.

I have a few backups I've tried restoring, including /boot, /recovery, /system and /data, and wiping the Dalvik cache and /cache, but nothing is kicking this thing loose. I'm really at a loss to explain what's going on, and out of ideas right now.

Intermittent display, no touch screen, FIXED

My nexus 5 screen wasn't turning on. I could push on the back and it might turn on, or show a distorted display. It eventually booted and the touchscreen wouldn't work. It was a mess.

Oh, and before this the mic wouldn't work without pushing on the back. It was bad.

I followed this video for unseating the main display cable and battery. https://www.youtube.com/watch?v=OPuCmfhzgbg

I reconnected only the display cable, not the battery, and plugged it into the pc. I was hoping it would boot so I could remove its photos before sending it in for repairs.
It showed a no battery symbol, BUT the display was on, and properly working!

I reconnected the battery, and it booted normally. Touchscreen worked and all.

Now, there are no issues, no mic problem, no touchscreen problem, like new! Just thought, if anyone else is dealing with this same dilemma, they might find this post helpful.

Note: This is my second nexus 5, the last one had major battery issues and needed to be replaced. Don't know if I'd buy another LG (nexus) phone after this.

broken touch screen fixed itself

A couple weeks into using my new nexus 5, half the touch screen stopped working (if you really had to, you could still press buttons by pressing the thing really hard). It seemed like it was a hardware issue so I unrooted and wiped the device with this guide
http://forum.xda-developers.com/goog...image-t2513701
with the intent of returning it. Part of this process involved TWRP (where there are touch controls), and the problem occurred even there. (to me, that seemed to confirm it must be a hardware issue).

Now after everything is factory-reset, the touch screen has magically started working again. I'm extremely confused how this could have happened. My best guess is that the issue was intermittent and i accidentally jiggled the phone in a certain way to make it start working again.

Does anyone have an idea what could have happened, or how I could stress-test things to find out? If it is indeed an intermittent issue and the phone needs to be replaced I'd like to do that ASAP because I'm leaving the country and dealing with warranty will be difficult from overseas.

Fixed screen, at first green light on charge, now not booting and overheating charge

Hi today i got my nexus 6 back, after a smashed screen, i put it on charge and at first i had the green light in the speaker grill, then after a few minutes that light went out and nothing much happened when i tried to turn it on, i left it to charge for a while and when i went to check on the phone, it was getting quite hot (probably as hot as it would on heavy gaming).

Basically i don't know the issue here, im hoping it is a minor thing as at first something did happen, then the overheating with nothing happening. Do you reckon this is done for, or it is saveable?

Thanks

[Fixed] Note 4 Alpha S6 Revolution Rom Setting Force close

Here Is the solution of n4 alpha s6 revolution rom settings force close flash it over cwm or any recovery and done..

HIT thanks Plz If It Fixed

PHP Code:

---


https://drive.google.com/file/d/0B0bibHRtIJb7OG91bm1rVE95TUE/view?usp=docslist_api 





---

Screen is not cracked but has a block of black on it, what needs to be fixed?

My galaxy s5 fell, the screen itself is perfect but like there is a patch of black on it . what may be the problem?

Is OPO vulnerable to Stagefright? Which ROM has this fixed?

There's been massive publicity in the news last couple of days about this huge vulnerability in android devices. I take it OnePlus using unpatched ROMs is also vulnerable to this stagefright bug. If so, are there any ROMs out there that has this critical vulnerability patched up?

Did I brick my phone and can it be fixed?

Hard reset my phone and now I can't get past the set up screen. It may be because I used titanium backup to free a few apps and did not disable this before the hard reset. I get as far as the wifi setup screen and it won't get any farther. It either gets stuck at "Just a sec" or "checking for updates". I can get into stock recovery and it appears my computer recognizes the ability to adb sideload. Can someone please help me? Thanks either way. Oh, I have the Sprint LS991 G4.