yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario Software Upgrading] epimazzo:
Hi Buddy,

I faced similar problem when I got a friend´s wizard to upgrade its OS, etc...

Have you read my thread regarding that? It can works for ya!;)

Check it out here:

http://xdaforums.com/showthread.php?t=294107

Good luck!:)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mfrazzz:
D'OH! Yes I've seen that and completely forgot about the reason for this thread! Thanks. We'll give this a go tomorrow to see if that lets him flash the Button ROM.
[G3 General] gangaskan:
i'm going to try a diff rom, but i'm running the nightly 21'st CM12 rom this started happening after i upgraded.

its a pain to get on to some items on the screen this way. here is what the touch debug show's i have a whole LINE down the screen that is dead. -- see attached.
[G3 General] ItsJacobee:
I flashed Cyanogenmod 12 to my LG G3 D851 and had no problems. I would try reflashing it. Sorry I can't help anymore.
[Windows Phone 8 Q&A, Help & Troubleshooting] QA Bot:
Q&A for [TUT]Flash Windows Phone 8.x with FFUTool[Unlock BL]

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [TUT]Flash Windows Phone 8.x with FFUTool[Unlock BL]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Windows Phone 8 Q&A, Help & Troubleshooting] wuiyang:
where to find .ffu ROM? or is anyone has OEM account and able to download phone image designer and upload it?
[Windows Phone 8 Q&A, Help & Troubleshooting] G.moe:
I assume microsoft links an OEM's ID to the OEM-exclusive downloads when they are sent, and therefore nobody will publically be posting such tools. OEM access is so inexpensive ($99 per year) that this must be the only reason certain tools have not been made public here.
[Windows Phone 8 Q&A, Help & Troubleshooting] axter:
I have this error when I want to flash it. My Lumia is a 930 Proto. Can anybody helpme?

"C:\Users\herna\Downloads\bsflash_ffuretail>ffutool -uefiflash flash.ffu

Logging to ETL file: C:\Users\herna\AppData\Local\Temp\ffutool4116.etl

Found device:

Name: Nokia.MSM8974.P6180.2.2

ID: 00000015-5a2d-73c6-0000-000000000000

Flashing: flash.ffu"

An FFU error occurred: Failed to flash with device error { 0x18, 0x0, 0x0, 0x2,

0xa, 0x5 } : Status: 0x8000001a.
[Windows Phone 8 Q&A, Help & Troubleshooting] GeorgeLeonte:
NPS?

Have you tried finding RM pack of your phone then flashing with Nokia Product Support?
[Windows Phone 8 Q&A, Help & Troubleshooting] axter:
what's the RM pack? I'va downloaded a lot of product codes firmwares, but all of this tell me the same thing. I don't know what else to do...:confused:
[Windows Phone 8 Q&A, Help & Troubleshooting] axter:
I have this error when I want to flash it. My Lumia is a 930 Proto. Can anybody helpme?

"C:\Users\herna\Downloads\bsflash_ffuretail>ffutoo l -uefiflash flash.ffu

Logging to ETL file: C:\Users\herna\AppData\Local\Temp\ffutool4116.etl

Found device:

Name: Nokia.MSM8974.P6180.2.2

ID: 00000015-5a2d-73c6-0000-000000000000

Flashing: flash.ffu"

An FFU error occurred: Failed to flash with device error { 0x18, 0x0, 0x0, 0x2,

0xa, 0x5 } : Status: 0x8000001a.
[Windows Phone 8 Q&A, Help & Troubleshooting] sabity:
Device ID error (0x16)

Just tried to flash a Lumia 521 with a 520 ffu but recived a 0x16 error stating that the image ID and the device ID do not match. Could you help me out (point me to a source) on how to address this issue, if possible. I suppose it would involve changing the product type.

Thanks
[Windows Phone 8 Q&A, Help & Troubleshooting] augustinionut:
Lumia 640 xl dual sim

Hi, can i flash this variant rm -1065 if my phone is rm-1067? I want to activate LTE suport.
[Windows Phone 8 Q&A, Help & Troubleshooting] dmc_xda:
ATIV S

Does this work on the ATIV I8750?
[Windows Phone 8 Q&A, Help & Troubleshooting] DilanChd:
Hi,

No, you can not flash a different product type that your device. Not currently.
[Windows Phone 8 Q&A, Help & Troubleshooting] augustinionut:
Not currently sound great :)
[XDA Assist] GaneshXDA:
Hey ,

I flashed my moto e to CM 12 , its working perfect . but i have only one issue , unable to listen received calls .

pls help me!!!
[XDA Assist] Heisenberg:
Hi :)

Thanks for writing to us at XDA Assist. A quick search allowed me to find the q&a thread for the ROM you're talking about here:

[Q&A] [ROM][5.0.2] CyanogenMod 12.0 CAF [CONDOR][NIGHTLY]

I'd suggest you perform a search of the thread because your question is most likely already being discussed there. If it isn't already being discussed taken go ahead and ask in that thread, that way it'll reach the people who are using the ROM and get you a helpful answer.

Good luck!

Thread closed.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] tluley51:
Well I was hoping someone had some ideas with my battery issues. It's hard to pinpoint exactly what it is without root, but here is what I can provide. Any help would be awesome!
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] wadamean:
That surely is bad battery life there. Try an FDR (factory data reset) and that should fix your problem most likely or disable as much bloat ware including Motorola stuff and see if that helps. Most likely though you will need a factory data reset
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] xbxjunkie:
......or try wiping cache in recovery, that worked for me
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] tluley51:
I'll give the cache wipe a shot and report back. As for disabling bloat, I went through and gave it a real good scrub over the weekend and I'm still seeing these terrible numbers. I'm hoping to hold off on the factory reset until lollipop comes out, since it's recommend you factory reset when going to lollipop, but who knows when that will be.
[Windows Phone 8 Q&A, Help & Troubleshooting] wuiyang:
how do i trick Lumia softare recovery tool that my phone is Lumia x30? and flash that Lumia ROM into my phone?
[Windows Phone 8 Q&A, Help & Troubleshooting] edwardmax2010:
why are you making the app trick your phone type in the first place? I don't think you can.
[Windows Phone 8 Q&A, Help & Troubleshooting] mstrvd:
I'd try with Nokia care suite that let you really flash roms, but it will obviously refuse to do that, even if you managed to flash another rom you'd brick the phone
[Transformer TF300T Q&A, Help & Troubleshooting] lordofazeroth:
This question is not about the TF300T but about the ME301T, quite similar but cheaper and without dock.

I had my tablet in RMA. This was changed to new hardware:

* Touchscreen

* Display

* Battery

* Mainboard

Question:

What is left of my original tablet? What was not repaired (changed) in RMA?

The back plate, there are some scratches like before RMA.
[LG Optimus L90] darkmx-6:
Dropped my phone in water.

thought everything was ok till I made a phone call and now the microphone doesn't work.

Any Ideas?
[LG Optimus L90] darkmx-6:
for anyone interested I opened it up to see how hard it may be. (i followed part of a youtube how to remove screen) found the board with the microphone on it, disconnected the ribbon cables and tried to pry it off lightly. It didn't want to let go. Figured I needed to use a heat-gun or blow-dryer with a plastic pry to get it off. As I didn't have the board I needed yet I decided to scratch a little on the microphone (probably did nothing). Popped the connecters back on and put it back together. turned it on and It started working.

May be it needed some air? May be the connectors were not engaging right? IDK but I'm confident I can replace the charging port and microphone on one of these because they are on the same board. The screen isn't that much harder either.
[LG Optimus L90] pduke7:
!

hi!

unfortunately i had the exact same experience but in my case the mic never fanctioned again.

Since you did it, can you please tell me which one is the mic...? is it the round thing on the oposite side of the speaker with the 2 spiral connections on it or am i ...scratching the wrong thing :P ??

thank you in advance man
[ONE General] cssacropolis:
Release delayed to mid/late march.

Source

Mods:If this is duplicate, I apologize in advance and you can lock/delete!
[ONE General] .psd:
I've given up waiting. At this point I can't imagine their month-old build is less buggy than the up to date CM12 nightlies anyways. So I'm just sticking with the nightlies getting pretty shameful battery live compared to 05Q. All I want is for them to release the new camera on the Play Store so we don't have to wait :'(
[ONE General] lsl640:
I didn't put much hope for oxygen os, waiting for 12S
[ONE General] DesignGrits:
Everyone knew this already, i'm not sure why its such a big surprise.
[ONE General] Stories:
Oh well. CM12 nightlies is good enough for me that I don't mind putting up with some of the silly bugs.
[ONE General] served24:
They need to clean up their act and speed things up. I'm sticking with nightlies but would appreciate an official stable release.
[ONE General] vazovskiiii:
It's very bad when company not doing there promise about 3 month i bought this phone because of good support and in time promise but for sorry they couldn't. I understand about small company etc but they should say 6 month or something else to be sure that they could. It's very bad. Almost everyone got lollipop except us i think i will sell my opo and will go back to Samsung
[ONE General] kolyan:
Well its better then nothing. Good to see mid-late March dead line. 1 month is not alot if final release is nice and stable
[ONE General] bozzykid:
How has OxygenOS been delayed? There has never even been an announcement about a release date.
[ONE General] PlayingPoise:
Honestly surprised people still care about OxygenOS. Why buy a phone that has the unlimited capibilities of being rooted and unlocking the bootloader if you won't do anything with it? Just install Slim and move on, it's not like Oxygen looks all that groundbreaking and spectacular.
[ONE General] vanessaem:
Thread cleaned.

Wow, there were only 16 posts and already arguing and massive uses of profanity. Please try to express yourselves without cursing and using foul language. None of that is allowed here. Holding a difference of a opinion doesn't mean being nasty and disrespectful to someone because of that fact. See below:

Please try and be civilized. Remember at the end of the day, these are only handheld devices and not vital organs. :)

Regards
[ONE General] kripz:
What are the differences between Opensource Cyanogen and Closed? Just the features/apps? Are the blobs/kernel taken from closed source?
[ONE General] dmarden:
I'm not surprised by the delay. Plenty of serious CM12 issues that I would imagine are currently present in internal CM12S builds too.
[ONE General] Logic717:
The sad part of all this is that OnePlus / CM actually has a great track record of releases from 4.4.2 to 4.4.3 to 4.4.4 all happened super fast. Clearly 5.0 is a much bigger release but I'd rather them spend the time to squash bugs than release a crappy ROM. If they did that I'm certain there would be a complaint thread about that as well...
[ONE General] the Doctor:
Android Police is reporting mid-late March for the release of CM12s and OxygenOS, and that

Source
[ONE General] bombadier:
Yes its offiical OP are a complete laughing stock, they have left kitkat with a broken camera and at present CM12 nightlies still have the issue, and without access to proprietary drivers that will continue

https://jira.cyanogenmod.org/browse/BACON-1309

https://forums.oneplus.net/threads/oneplus-cam-problem-pictures-in-2-halves.114953/

And as for this Never Settle milarky easy to talk the talk
[ONE General] mharis05:
How is your battery coming along on the nightly?

Mine is like half of what I used to get on 4.4.4.
[ONE General] vinylakos:
Clearly you have never tried other phone companies and you have no clue how things work. They delay cause they want the Os to be as stable as possible with all the features working. So they could release a beta or an alpha now but it would be buggy and not working correctly, then people start complaining again about it etc etc. Just wait or flash any other custom rom that is already lollipoped. There are a ton of options all stable enough for daily use and so many great developers that make great kernels roms for the Opo. Just saying you can freely go back to Samsung or any other company you used to and pay the overpriced same spec phones with even less official support.
[ONE General] gsmyth:
Keep seeing these articles in my twitter feed and think it's a OPO lollipop release. [emoji12]

https://twitter.com/EngadgetUK/status/570527165017513984
[ONE General] rraquib:
The resemblance is uncanny.
[ONE General] gsmyth:
Yea never really noticed it before, but at a quick glance and with that reddish wallpaper.
[ONE General] rraquib:
Look at the speaker size and camera position along with top and bottom trip. Hope it is not a photoshopped OnePlus.
[ONE General] pingling:
Well, looks like it might be. The phone looks different to the one shown in the product video...
[ONE General] :
I just don't get people whining about getting a delay for a stable ROM. The fact of the matter is that cm11s is rock solid if you want a stable daily driver. If you want to diddle and fiddle, they manufacturer has made this one of the easiest devices to unlock and install custom recovery on, and there is a plethora of custom ROMs of all shapes and sizes available.

Be glad they care enough to try to release a stable ROM, and be equally glad you have the freedom to install an unlimited amount of custom ROMs.
[ONE General] Heisenberg:
Couldn't agree more. There's a really saddening, unfounded sense of entitlement being displayed here.

Transmitted via Bacon
[ONE General] Giocarro:
The reason of this winning might be that some of us purchased the One exactly because of official Cyanogenmod commitment to provide updates.

Otherwise, if ROM development was not a priority, we could have well chosen a Xiaomi Mi4, a Meizu Mx4, an Oppo Find 7a, a Huawei, etc. etc.
[ONE General] sendhiloo7:
I totally agree with you
[ONE General] the Doctor:
None of which have official Lollipop yet :rolleyes:

This delay could likewise prove that CyanogenMod is more committed to putting out a quality ROM than keeping an artificial deadline set before they knew the full scope of the project. Carl Pei at OnePlus has cited "proprietary drivers, code, QA, [and] certifications," not CyanogenMod's priorities as the reason for the delay. It's also the cause of the delay of OxygenOS, a ROM CyanogenMod isn't even involved in. So any speculation beyond what Pie has said is biased heresy unless there is solid evidence.
[ONE General] Giocarro:
And that's my point, too: the One should have had an official Lollipop by now.

I'm not a developer and hence don't care about the reasons behind the delay.

I purchased the One because I wanted official updates delivered at the same time or before other brands, namely Samsung, Motorola and LG.
[ONE General] Heisenberg:
This says a lot. For the wrong reasons. It doesn't matter whether you're a developer or not, there are reasons behind the delay, and they're for

your own benefit

. If they rushed a release out you'd probably be one of the first people to complain about the bugs. And CM have not once stated or promised that they'd be releasing updates at the same time as (or sooner than) the big players, so I have no idea where you got that ridiculous notion.

The fact is, building a ROM from scratch is a huge task in itself, and then taking on a new Android version is an even bigger task, and then taking on a new Android version that's so vastly different is an even bigger task, and then there's the change from the dalvik runtime to the ART runtime. The fact that you don't have the slightest idea of what's actually involved doesn't mean you can just ignorantly complain about the delay, and then claim that because you don't have the slightest idea of what's involved that somehow the valid reasons behind the delay don't matter. This is exactly what I meant earlier when I mentioned an unfounded sense of entitlement. Be patient. It isn't the end of the damn world.

Transmitted via Bacon
[ONE General] Coll_1:
Guys i've bought the One last summer, i've been using it for 5 months... it's just a peace of Chinese crap!

I am selling it and i'll buy the MOTO X
[ONE General] Heisenberg:
Cool story. Off you go then.

Transmitted via Bacon
[ONE General] Giocarro:
I got that ridiculous idea from the CM logo stamped on the back of my One.

Your reasoning makes sense BUT somehow a few other companies managed to accomplish this huge task anyways.

I agree: nobody has to make a drama about official ROM updates and I can assure I sleep well at night even running CM nightlies, but the patience doesn't remove the disapointment for not getting earlier updates.
[ONE General] bombadier:
What I fail to understand is the rush of people to defend the company, they are big enough to fight their own battles, shame they choose silence over engaging with the community and I'm sorry but 5 words in a tweet is NOT an official statement, the only reason I care about CM12S is that the camera bug driver is meant to be fixed as it is not in CM12, nor will it be unless CM12 has access to closed source propriety drivers, its no wonder the community rage as OP is silent on a great many things that they should be vocal about
[ONE General] Heisenberg:
Dude, that logo doesn't indicate anything other than CM being the OS for the phone. The point is that CM never claimed to be releasing updates at the same you're as the big players. You're drawing an irrational conclusion based on nothing at all there.

And those companies had a massive head start over CM because they received Lollipop in advance months before the release, which is when CM got their hands on it.

If you're running the nightlies there really shouldn't be all that much to complain about, the differences between the stable release and nightlies for this phone are so minimal. We're talking lockscreen, camera, and MaxxAudio, all of which can be installed on the nightlies.

Transmitted via Bacon
[ONE General] bombadier:
Source ? as there were developer previews out in the wild for a couple of months, why was CM excluded ?
[ONE General] Heisenberg:
I'm not attempting to defend CM, I don't even really like CM. What I'm doing is attempting to breathe some logic into this thread, and dispel some of the garbage that's being posted. You're right, CM probably should be more public about what's going on, but they're not. It doesn't mean everyone should whine like children about it.

Transmitted via Bacon

---------- Post added at 08:57 PM ---------- Previous post was at 08:55 PM ----------

It was revealed at the Google I/O conference last year I believe. It's part of an initiative to have updates released faster. There are only a handful of participants, and only those participants have access to it. And Google hate CM, of course they'd exclude them.

Transmitted via Bacon
[ONE General] bombadier:
According to Wiki AOSP source code was made available in July 2014 so not sure how CM were "denied access" ?

There is a difference in wanting answers to whining like children, my issue is with the way OP are handling this whole mess, the silence causes the moaning, if OP man up and make an official statement so "non developer plebs" like me understand then that would go along way to silence the critics,

Take my point about this driver issue, It has been active since September, look at what has been going on to address this recognised and accepted bug ? thats right nothing, we have been told a fix is being developed,but have seen absolutely no development being made, then a OTA shows up on kikkat which does not address this issue? are you telling me thats ok ?
[ONE General] Heisenberg:
I'm not saying it's ok, but I'm not saying it's not ok either. My point is that the way people are carrying on it's like they think the delay is occurring purely to spite them. Or just because a bug hasn't been squashed yet that it isn't being worked on at all. It's ridiculous. And it shows a complete lack of understanding of just how complex these things are, and just how difficult certain problems can be to fix. Everyone's a freaking armchair coach without having the slightest idea of what they're talking about.

Transmitted via Bacon
[ONE General] bombadier:
Yeah thats the problem with stone wall silence, as you say everyone is an armchair coach,the fact NOBODY from OP or CM makes any effort to explain the complexities encourages that mentality, we both agree though that the vast majority of complaints are from whiners, Never ceases to amaze me the number of people that think CM12S is just a "stable" version of CM12, point is nobody does anything to clear up these misconceptions and encourage the whining.

As far as I am concerned if there was more engagement then people might have a better understanding of the challanges,silence just breeds frustration,after the "offiical" tweet what did the OP forum mods/admins do to address any of the rage ? thats right nothing and that just encourages folks to rage.

How do I know what work is being done when the official bug tracker shows nothing? that is the definition of frustration mate,especially when the developer of Camera FV-5 has managed to implement a work around
[ONE General] Heisenberg:
People see it how they choose to see it. It isn't frustrating for me at all. We have a plethora of great development happening for this device, that, lets face it, is probably better than anything CM will release. And really, if you're on XDA you're probably into flashing custom ROMs. So why not just have some fun with some custom ROMs while CM and OnePlus do their thing?

Maybe they should be more vocal, maybe they should release an update every seven hours, maybe we should all be generously compensated for the severe heartache and awful stress that waiting for a stable release is causing (because it's such an ordeal to have to wait for an update, forget about whatever other awful things are taking place around the world, it's right up there isn't it).

Moaning about it doesn't change a thing. Moaning about it here on XDA doesn't even come close to reaching the people that could have an effect on the situation. It just like spoiled brats throwing their toys around because they didn't get their way right now.

Transmitted via Bacon
[ONE General] bombadier:
Now you are just trying to be a smart arse, not asking for an update every 7 hours, how will flashing a custom ROM help ? the bug is in the closed source drivers, every rom is affected, but you are right this is pointless and in the scheme of things unimportant, I take the bait everytime I see someone defend this shambles of a company.
[ONE General] Heisenberg:
Yes I'm exaggerating the situation for comedic effect. But I have seen people complain that they're not getting nightly updates to CM11S.

Like I said before, I'm not trying to defend either of those companies. I'm not a crusader for CM or OnePlus, I'm just sick of seeing all the whining from people who think they have some kind of special and unique insight into what's going on at either of those offices. Nobody does. Nobody ever will.

Transmitted via Bacon
[ONE General] jmtjr278:
I am not in any sort of rush for official lollipop as unofficial is running great for me.

But... One of your previous posts mentioned one plus never promised an update within a time frame. In fact, they did. 90 days after lollipop source officially released.

Second paragraph of my link is the first result when googling oneplus one lollipop.

http://m.androidcentral.com/oneplus-one-lollipop-update-delayed-march

Have a nice day all.

Sent from my A0001
[ONE General] :
And once again, i will repost my post from yesterday.