It's that time again!

I spent 0 to get the screen fixed on my LG Optimus G and it hasn't work properly since. Unfortunately U Break It won't continue to tweak the screen issues because I have since dropped the phone again (a couple of times actually) but the problems existed before that.

The drops are caused by it's Gorilla Glass back, it's slipped out of my hands if I don't have a firm grip on it.

Anyway, I was waiting for the Moto G to drop and have had my eye on the 2GB/16GB model since my LG has has similar specs. The LG does take great video and pictures (on a tripod) so I will continue to use it in some capacity.

But I need a new daily driver and I want to save money. I don't mind paying 0 for the Moto G, but I have started to look at some other devices.

So should I just get the Moto G or -

Blu Studio 5 C Super Camera
Blu Studio X Plus
Asus ZenPhone 2 (16 GB version)

I don't want any former flagships (G3, etc) I want a fresh device, not a dethroned flagship...

Thanks

No Android Pay with root and why it's BS.

Yes, this is a new thread because the existing ones are focused on the technical debates around why it should or shouldn't work.

I've been following this discussion to some degree and I just couldn't help but jump in. IMO the focus on the technical aspects of this issue are misguided. This is a purely, for lack of a better word, "political" decision.
Here's the thing. You can blather on for days about the supposed technical reasons that Android Pay cannot or should not work in a rooted/ROM'd environment, but the truth is, the state of the host device is nearly irrelevant. Consider this. You can take any Windows, Linux, or Mac PC and login with any level of user privilege you wish and use nearly any browser to access your bank's "secure" account website. There you can do MUCH more financial damage than you could ever do from a mobile payment app given the transaction limits placed on the latter. You can even do this from a pirated, hacked copy of Windows or MacOS with no issue. In fact you can login from a PC with known malware or trojan infections! Given this, anyone trying to make a technical security argument for not supporting mobile payment on rooted devices is either ignorant or lying. This was strictly an arbitrary decision on someone's part. Likely on the banking system's side.
The fact is, an Android phone with a rooted, custom ROM, is at best still a more secure environment than most PC's, at worst it's no less secure. Given the mechanism's in place on Android, it's even easier to verify an apps integrity than on a desktop OS.
So let's throw out all the pointless discussions about the technical issues that make mobile payment on rooted devices impossible. We already know that the banks have accepted much less than a perfectly pristine and secure environment for accessing their systems. Raising the bar for mobile devices was simply a bureaucratic decision, not a technical one.
If you want mobile payment on rooted devices, you'll have to lobby for it. Hard, and hope you can force anther bureaucratic decision in your favour. Even then I wouldn't hold my breath.

Okay, it's time to ask for help. I can't flash anything!

Well....Almost, I have CM11 "working"

I have a (bestbuy) refurb HTC One M7spr ... I'm wondering if the CID may be incorrect o.O but I haven't messed with that on any of my previos phones.

give me a sec, I'll get back to my chromebook and edit this with a few more details (I'm in an office on a win pc at the moment)

I gave up and grabbed "rom.zip" from the %temp% folder, I'll detail my struggles in a few.

Here is my fastboot session (for my info and anyone willing to help figure this one out)

Quote:

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock ... (bootloader) Lock successfully... (bootloader) mipi display off (bootloader) mipi_dsi_cmds_tx_ext (bootloader) pm8921_vreg_disable function, vreg_id = 38 (bootloader) pm8921_vreg_disable function, vreg_id = 1 (bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C) (bootloader) Use PSHOLD to reset device. FAILED (status read failed (No such file or directory)) finished. total time: 1.170s C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock ... (bootloader) Device was already locked! OKAY [ 0.000s] finished. total time: 0.000s C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU ... (bootloader) Start Verify: 3 OKAY [ 0.040s] finished. total time: 0.040s C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip Rom.zip target reported max download size of 1514139648 bytes Invalid sparse file format at header magi error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th e block size 4096 sending sparse 'zip' (1478648 KB)... error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th e block size 4096 error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th e block size 4096 OKAY [112.640s] writing 'zip'... (bootloader) signature checking... FAILED (remote: 12 signature verify fail) finished. total time: 226.710s C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip target reported max download size of 1514139648 bytes Invalid sparse file format at header magi error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th e block size 4096 sending sparse 'zip' (1478648 KB)... error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th e block size 4096 error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th e block size 4096 OKAY [ 82.260s] writing 'zip'... (bootloader) signature checking... FAILED (remote: 12 signature verify fail) finished. total time: 196.330s C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip Rom.zip target reported max download size of 1514139648 bytes Invalid sparse file format at header magi error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th e block size 4096 sending sparse 'zip' (1478648 KB)... error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th e block size 4096 error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th e block size 4096 OKAY [ 80.333s] writing 'zip'... (bootloader) signature checking... FAILED (remote: 12 signature verify fail) finished. total time: 194.897s C:\Program Files (x86)\Minimal ADB and Fastboot>

Samsung Galaxy A5 detects S-View cover when it's not even attached.

Hi XDA Fellows ;)
My Samsung Galaxy A5 detects the S-view cover even when it's not attached.
The s-view windows always appears and I couldn't navigate outside it. The screen portion under it and the home button are totally disabled.
Anybody has an idea to solve this?

Xiaomi Piston 3,why it's so hot?

I found Xiaomi Piston 3 is very hot ,ant it's on a hot sale on those online shopping website,such as amazon,tinydeal,banggood.Why is't so hot?Because its brand or the product'quality or something else like piston 2?

In case you guys haven't noticed already, Lollipop is here. What else? IT'S ROOTABLE!

Major credits again to @zachariahpope for the Lollipop build earlier tonight. Unfortunately getting it rooted from stock won't work. Which is why I proceeded to try the same method from my rooting guide to attempt root. And I am proud to say...I HAVE THE ROOTED LOLLIPOP SONY XPERIA Z3V!!!

And also, I have recovery as well.
If you're going to follow in the same footsteps, please PLEASE remember when you get the supersu file, grab the v2.49 as that is for LOLLIPOP.

Attached Thumbnails