yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Android Rocks:
How it works in Nexus 4?
[ONE Original Android Development] Heisenberg:
This ROM? It doesn't. You're in the wrong section.

Transmitted via Bacon
[ONE Original Android Development] Prodigalza:
Why not just root?

Sent from my Google Edition S4 GT-I9505G
[ONE Original Android Development] Vonnegut:
Not many know that the cyano gallery is freely available on the store https://play.google.com/store/apps/details?id=com.cyngn.gallerynext&hl=en
[ONE Original Android Development] Zephyr!:
Please someone post the latest version of official Cyanogenmod of OnePlusOne. Just received the global variant yesterday.
[ONE Original Android Development] K Rich:
https://cyngn.com/products/oneplusone/
[ONE Original Android Development] TheShoxter:
Try looking around the forum ;) In the One Android Development subforum you can find Calkulin's stock ROM zips. The latest is 44S.
[ONE Original Android Development] dasti555:
I don't know guys if this is right place on ask. But if I make clean install of this rom that mean I will have 44S if I flash AK Kernel. Will I still have OTA?

Because I was on 38 and I dont receive ota on 44 .. But maybe i was just too fast.

I read somewhere about OTA lose .. So this happen when? When I make what? Because I have backup of 44S and I read about new update in january with audio improvement so if I will on 44S will I receive official update? Or I will need flash it as 44S when I was on 38?

I hope do you understand my complicate english :) THx
[ONE Original Android Development] knuspertante:
Yes you will receive the next OTA Update.
[ONE Original Android Development] Benz83:
Hello guys, i have a little problem.

With the OTA, the phone download the firmware, reboot on recovery mode but not install the firmware and give me error. Phone try to install the upgrade to XNPH38R incremental , now the versione is 11.0-XNPH33R

I get this error : http://www.mediafire.com/view/6grk0lxti6bsflg/IMG_20141216_170158.jpg

Well, i installed TWRP recovery and Supersu (oem unlock etc) , everything fine.

I installed different ROM , when i going to the recovery mode, and try to install, i get again a error.

Why? i cant understand. I check if the bootloader is unlock, and is fine.

Some one can help me?
[ONE Original Android Development] Heisenberg:
It gave you that error when trying to apply the OTA because you have a modified/missing system file (velvet.apk, which I believe is the Google Search app). Modified or missing system files cause the OTA to fail, so if you want to remedy that situation you need to revert whatever you did to the Google Search app.

As for installing the other ROM, exactly what error did you get that time? Did you check the md5 after downloading the ROM zip? Exactly which ROM zip is it?
[ONE Original Android Development] Benz83:
Thanks for reply! but i not toch nothinkg, how can fix that apk (i dont know how revert, i did also a hard reset) however i try several , and someone tell me the zip signature or md5 arent ok, but usually the velvet.apk problem

cm-bacon-3628510d76-to-ac1ccf7921-signed.zip

cm-11.0-XNPH44S-bacon-signed-fastboot.zip

no i try again with TWRP with cm-11.0-XNPH44S-bacon-signed-fastboot.zip and give me only the error : NO MD5 FILE FOUND ,
[ONE Original Android Development] Heisenberg:
Ok. Your best option is probably to flash the 44S fastboot images, I have detailed instructions in my guide thread (link in my signature).

Transmitted via Bacon
[ONE Original Android Development] Benz83:
Sorry, mi mistake. I did it :(

But only this step not work fastboot update -w cm-11.0-XNPH44S-bacon-signed-fastboot.zip

the others step go well

after reboot : fastboot reboot

Nothing change! and is very strange!
[ONE Original Android Development] Heisenberg:
You need to provide more information, what happened on that step?

Transmitted via Bacon
[ONE Original Android Development] Benz83:
C:\adb-tools>fastboot update -w cm-11.0-XNPH44S-bacon-signed-fastboot.zip

error: failed to load '-w'
[ONE Original Android Development] Heisenberg:
There's something fishy going on with the "fastboot update" command so you'll need to flash each part individually. See the following post for detailed instructions:

http://xdaforums.com/showpost.php?p=57367830&postcount=404

Transmitted via Bacon
[ONE Original Android Development] Benz83:
Hello!

infact as i tell you i make the same step, i can try to did again

However i found on another site the firmware cant work because i need the chinese version for A0001, its possible?

C:\adb-tools>fastboot flash modem NON-HLOS.bin

sending 'modem' (56369 KB)... OKAY [ 2.072s]

writing 'modem'... OKAY [ 0.740s]

finished. total time: 2.813s

C:\adb-tools>fastboot flash sbl1 sbl1.mbn

sending 'sbl1' (295 KB)... OKAY [ 0.013s]

writing 'sbl1'... OKAY [ 0.021s]

finished. total time: 0.035s

C:\adb-tools>fastboot flash dbi sdi.mbn

sending 'dbi' (11 KB)... OKAY [ 0.004s]

writing 'dbi'... OKAY [ 0.006s]

finished. total time: 0.010s

C:\adb-tools>fastboot flash aboot emmc_appsboot.mbn

sending 'aboot' (376 KB)... OKAY [ 0.017s]

writing 'aboot'... OKAY [ 0.011s]

finished. total time: 0.029s

C:\adb-tools>fastboot flash rpm rpm.mbn

sending 'rpm' (185 KB)... OKAY [ 0.011s]

writing 'rpm'... OKAY [ 0.008s]

finished. total time: 0.020s

C:\adb-tools>fastboot flash tz tz.mbn

sending 'tz' (283 KB)... OKAY [ 0.027s]

writing 'tz'... OKAY [ 0.009s]

finished. total time: 0.037s

C:\adb-tools>fastboot flash LOGO logo.bin

sending 'LOGO' (9591 KB)... OKAY [ 0.379s]

writing 'LOGO'... OKAY [ 0.128s]

finished. total time: 0.507s

C:\adb-tools>fastboot update -w cm-11.0-XNPH44S-bacon-signed

error: failed to load '-w'
[ONE Original Android Development] Heisenberg:
You don't need the Chinese version, the international version should be fine, many other people have used it.

Transmitted via Bacon
[ONE Original Android Development] Benz83:
But i cant explain, why i cant flash
[ONE Original Android Development] Heisenberg:
Did you take my previous advice and flash the images one by one instead of using the fastboot update command?

Transmitted via Bacon
[ONE Original Android Development] Benz83:
I cant try again because isnt my phone :) . Maybe i can do in future. Thanks for all guys!!
[ONE Original Android Development] DooshPastesh:
Try to change fastboot driver. I had the same problem but on flashing some partitions. Now I'm using Samsung universal usb drivers and fastboot work well.
[ONE Original Android Development] Darkside14:
Maybe put the "-w" at the end of the command?
[ONE Original Android Development] pablo.va87:
Hi!

Does anyone know where can I find the 11S 44S ROM rooted to be flashed with a custom recovery?

Thanks!
[ONE Original Android Development] cryogeno:
Here:

[ ROM ][ Nov 7 ] Stock Rooted XNPH44S

And take a look also here: [INDEX] OnePlus One Resources Compilation Roll-Up, a very usefull thread.
[ONE Original Android Development] kvikram:
I have the Indian version of the OnePlus One which does not get OTA updates. How do I go about upgrading to the latest build, without wiping everything?
[ONE Original Android Development] pandasa123:
Adb sideloading the update zips
[ONE Original Android Development] Heisenberg:
Just download the correct OTA file from one of these threads:

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

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

Install it with your recovery.

Transmitted via Bacon
[ONE Original Android Development] didicola:
when i come from cm11 generally do i have to do all the above from the first post or i just flash normally?
[ONE Original Android Development] Heisenberg:
The instructions in the first post are outdated. Go to my guide thread (link in my signature) and see section 8.

Transmitted via Bacon
[ONE Original Android Development] ek69:
I would download the entire 44s ROM and flash everything after a clean wipe off everything. If you want get 15 second adb installer if you don't have drivers and that will install all the correct drivers for everything system wide so you don't have to move files into a specific folder etc, press and hold ALT then right click and "open command prompt here" in the folder with all the files and you're good to go.

[MENTION=4153349]timmaaa[/MENTION] maybe you could please add these steps into your posts in the threads in your sig? That way noobs don't get confused with the driver installation part to begin with lol and it's a resource provided by a fellow XDA member :)

Link for 15 second adb installer

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

Cheers

Sent From Lollipopified Bacon Goodness!
[ONE Original Android Development] Heisenberg:
I already direct members to get adb/fastboot the proper way, via the Android SDK. And I have a link to the drivers too.

Transmitted via Bacon
[ONE Original Android Development] ek69:
Yeah I know, that's cool too. I was just thinking it could be an alternative for noobs that need to start from square one, since that link I provided just streamlines the entire process and installs it system wide so you can flash from any folder instead. Just a suggestion :) either way it's all good

Cheers

Sent From Lollipopified Bacon Goodness!
[ONE Original Android Development] Heisenberg:
In my opinion, when you start taking shortcuts problems can occur, and when problems do occur adb/fastboot isn't always given the attention it deserves as a possible cause. If you install things the way they were intended to be installed you can virtually discount it as the cause of a potential problem.

Plus, noobs will continue to be noobs unless they're prompted to undertake slightly more challenging ways to get things done, you can only improve your knowledge and ability with experience, so that's why I go about things the way I do.

Don't get me wrong, I very much appreciate the feedback, I'm just explaining why I'm choosing to maintain the status quo.

Transmitted via Bacon
[ONE Original Android Development] ek69:
No worries, no offense taken on either end of the conversation by us :) I do see your point. One shortcut leads to another, etc, then that's where ppl get into using point and click tool kits which almost always lead to problems lol.

Just a random question, what ROM & kernel setup are you running? I've only seen you help ppl, never post any problems you're having lol

Sent From Lollipopified Bacon Goodness!
[ONE Original Android Development] Heisenberg:
My current setup is in my signature, but I'm running the official Nameless KitKat ROM (with their stock kernel) which can only be found on their G+ community. I generally don't have problems, because I know what I'm doing, and I'm very careful about what I'm doing. Research is key, I do a lot of reading.

Transmitted via Bacon
[ONE Original Android Development] Griffrez:
I've been getting hard reboots (kernel panics). They are random at best (I can have none in a day but 3 in the next). I've reflashed many times, and I have no root applications and no dodgy apps. I'll attach my most recent last_kmsg.

I noticed how the file text is cut, but I just extracted from the phone and came like this. If you need another say it and I'll post another after the next crash I get.
[ONE Original Android Development] Tzfardaya:
Lovely mess in that log... Usually when I see that I suggest a full clean flash, after redownloading the source image files... Use fastboot rather than some toolkit, and don't flash one of the repacked zips via recovery.... Grab the latest image files from cyngn.com and try again?
[ONE Original Android Development] Griffrez:
I've done exactly that several times! I've download the zip file directly from Cyanogen, this one:

http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH44S-bacon-signed-fastboot.zip

I extracted it and ran, through fastboot the following commands:

fastboot flash modem NON-HLOS.bin

fastboot flash sbl1 sbl1.mbn

fastboot flash dbi sdi.mbn

fastboot flash aboot emmc_appsboot.mbn

fastboot flash rpm rpm.mbn

fastboot flash tz tz.mbn

fastboot flash LOGO logo.bin

fastboot update -w cm-11.0-XNPH44S-bacon-signed-fastboot.zip

And I get these issues anyways. And I've done this several times. And I don't use backups or anything. It's completely clean.
[ONE Original Android Development] Tzfardaya:
Good good, just checking... I've dealt with a lot of people who use bad backups, bad download and the like and keep having the same issues..

So, you have all your apps installed after the clean install when the reboots occur?

Try using the phone for a couple days with minimal/no apps installed and see if the issue persists while pure stock.

If the problem persists with no apps installed (or updated) after a clean flash then it sounds like a hardware issue....
[ONE Original Android Development] Griffrez:
Yeah, I thought of that, but I have yet to try it out. Since I am on vacations, I don't really require my phone, so I guess I'll try it out. I'll update later. Thanks anyway. I'll even redownload the ROM. BTW, is the "debuggable" image any helpful for this situation?
[ONE Original Android Development] erdal67:
Is there a flashable zip of cm11s 44s? I really need to dirty flash it on my phone

Sent from my OnePlusOne
[ONE Original Android Development] Heisenberg:
Look in the dev section for Calkulin's stock rooted 44S ROM.

Transmitted via Bacon
[ONE Original Android Development] erdal67:
Thanks bro, really needed it[emoji4]
[ONE Original Android Development] Tzfardaya:
Yes and no... It would have better Debugging support, but unless you know how to use it, and translate it... Not that useful for us laymen....
[ONE Original Android Development] szaf:
I am on 44S rooted.I have a strange problem.Sometimes keyboard doesn't show up.It is there where it should be but i cannot see it.I know it is there because when i touch the screen in the area where the keyboard should be i can write.I use stock keyboard.I usually solve the problem by rebooting the phone.But today rebooting didn't help.So i had to clear data/cache of keyboard in apps.Does anyone know something about his?
[ONE Original Android Development] UltraBoykj:
So if Ive only done updates from the about phone section, how do I know what version 11s I'm using ? My Cyanogenmod Version says: 20141008-SNAPSHOT-M11-bacon.
[ONE Original Android Development] Tzfardaya:
Well, that's a cm11 snapshot version...

Not a cm11s version...

Cm11s version would look more like "11.0-XNPH44S"

If you never flashed cm11 to your phone, someone else did before you got it...
[ONE Original Android Development] UltraBoykj:
Ugh. Ok.

So if I want 11s, I need to follow this document.

It's running so nicely and has a beautiful dark & colorful theme on it. Don't want to have to do all that again :)

What are some examples of things I am missing ( I will go read the OP now as well )

Thank you for the information.
[ONE Original Android Development] Heisenberg:
You're only missing out on the fancy lockscreen and camera, which you can install manually anyway.

Transmitted via Bacon
[ONE Original Android Development] Kamekazegoldi:
I am trying to flash 44S coming from Temasek (Android 5.0.2).

Keep getting errors (it just says "failed" the whole time).

When I try to flash via fastboot it says that boot.sig etc are missing.... :/

Want to get back to the original ROM. Any idea what is wrong?
[ONE Original Android Development] danielferratti:
same thing here bro..... BUT you can Download the 44S with the Toolbox from INTHIAANO and ALL your problems will be solved..... just install the Drivers on your PC, reboot to fastboot mod and you will be 2 clicks away from the flash.

http://inthiaano.com/oneplus-one-toolbox/
[ONE Original Android Development] DobbyDook:
Power button not work during calls

I currently have the 44S restored by working nandroid backup after doing system, cache, dalvik and data wipes.

The problem I have is that the screen will not wake up by pressing the power button during calls

I tried to restore only system and boot partition and it work so i think the problem is in data partition.

Can someone help me understand what the problem is?

Thank you
[ONE Original Android Development] Svid:
Try to flash clean (no nandroid) and test it again.
[ONE Original Android Development] knuspertante:
He know how they can fix his issue but they don't unterstand why they have this issue. [MENTION=3092332]DobbyDook[/MENTION] sorry I can't help you

Gesendet von meinem A0001
[ONE Original Android Development] Tzfardaya:
Bit rot, cross rom contamination, broken system mod links, bad nandroid restore, incomplete wipes, etc etc etc.... Lots of possible causes if it wasn't a full, clean install...
[ONE Original Android Development] paarthdesai:
modified ota from 38r to 44s?
[ONE Original Android Development] gianton:
Here buddy,

http://xdaforums.com/showpost.php?p=56577751&postcount=84
[ONE Original Android Development] pandasa123:
Not 12S exactly, but here's a link to the new (ALPHA) AOSP based OnePlus ROM: https://forums.oneplus.net/threads/rom-official-5-0-android-lollipop-alpha.223252/
[ONE Original Android Development] n30wav3:
Certainly need a dedicated thread I guess. Good start of 2015 for OnePlus after all that CM/OnePlus negative talk

The odd part is that's its AOSP. No official CM12S???

---------- Post added at 09:36 PM ---------- Previous post was at 09:33 PM ----------

My bad. The thread is already on the other section. Shouldn't it be in this section though? AOSP original development...
[ONE Original Android Development] Heisenberg:
It isn't in the dev section because:

1. The person that posted the thread isn't the owner of the project.

2. The person that posted the thread is just linking to the ROM page on the OnePlus forum. It isn't actually a dev thread and therefore it doesn't belong in the dev section.

Transmitted via Bacon
[ONE Original Android Development] LenAsh:
What he said...
[ONE Original Android Development] bastard79:
check this https://forums.oneplus.net/threads/official-cm11s-download-links.141825/
[ONE Original Android Development] Heisenberg:
That's the ROM that OnePlus developed themselves. I wouldn't go anywhere near it, I've seen a whole bunch of people having major issues after flashing it and even after restoring a backup they have no signal.

Transmitted via Bacon
[ONE Original Android Development] n30wav3:
.... Discard
[ONE Original Android Development] Tzfardaya:
Well.. It is labelled alpha....
[ONE Original Android Development] Heisenberg:
Yes it is. But it's causing users to completely lose cell service end after wiping and going to another ROM. Hence my advice to steer well clear of it. Go ahead and flash it if you want though, it's your phone and your potential paperweight.

Transmitted via Bacon
[ONE Original Android Development] Tzfardaya:
I tend to avoid software labelled alpha for that reason... I usually wait until betas..
[ONE Original Android Development] Heisenberg:
Yeah, I agree. Although all these "alpha" builds that are being released are being labelled incorrectly anyway, I don't think the devs quite understand the definition of an alpha. An alpha is a build that is only tested in-house, and therefore not released to the public, they're actually beta releases if they're being released.

Transmitted via Bacon
[ONE Original Android Development] Sh0X31:
hello,

i flashed the lastest CM11S like in the first thread. Everything is stock but if I shutt the 1+1 down, it start itself and its reboot always hisself.
[ONE Original Android Development] Tzfardaya:
Normally I'd agree, and when software to s developed by a (largish) company that's true... But when it's just a single/small group developers, they will occasionally (frequently) do public alphas to bug hunt serious issues faster than they can on their own. Another reason for releasing public alphas is to show people that progress is being made on the project.
[ONE Original Android Development] tollboy:
Hello,

Can somebody tell me what is the default fonts used in CM11S.
[ONE Original Android Development] Heisenberg:
I get what you're saying, but an alpha by definition is not what they're releasing.

Transmitted via Bacon
[ONE Original Android Development] blahquader:
Same here, when AC Adapter or USB is connected. Have you tried to shut it down without a cable connected?
[ONE Original Android Development] Svid:
Hexo (Included in stock fastboot image)
[ONE Original Android Development] manishgkasera:
Is the source released for CM11s? Or kernel source?
[ONE Original Android Development] ghul21:
I think we will still get a support from cm. But next update it will not be a 12 version. ;)
[ONE Original Android Development] androik:
Hello,

Possible create one quick raccourci for this advanced option ?

Thx
[ONE Original Android Development] compman25:
Same here, waited 40 minutes and it never finishes booting.

---------- Post added at 04:46 PM ---------- Previous post was at 04:45 PM ----------

Yep

40 minute

md5 matched
[ONE Original Android Development] redukt:
´bout 10 minutes - never had any problems with my devices so far....

MD5 seems fine too - that´s my first check for all dl´s...

deleting xposed fw give same results - stuck in bootloop again :rolleyes:

however mark, thx for your work :)
[ONE Original Android Development] five40:
Stuck at boot animation. Had to flash back to 25R

Waited 15 minutes and it never booted for me either.
[ONE Original Android Development] VeNuMuS:
Working great bro. Didn't loose my mods
[ONE Original Android Development] LiquidSolstice:
God, the boot time is killing me, and adb isn't even active so I have no idea if it's working or not.

I flashed the 25R zip from cyngn directly first, and then I flashed your OTA on top. Would that be problematic?
[ONE Original Android Development] turilo:
Flashed and working perfectly! Not one issue. Thanks Markbencze !
[ONE Original Android Development] Shaquiel Harris:
I've been waiting for about 15 minutes myself but mine's hasn't fully booted up yet. Gonna wipe, flash stock then flash the ota on top to see if i have better results.
[ONE Original Android Development] Negan:
It could be but doubtful.

I'm sad to see that some are still having issues.

What I did was put the zip on my SD, made sure I didn't update cm recovery, then rebooted to twrp ( my recommended recovery) and just flashed. No wiping of any sort.

And waited for it to boot.
[ONE Original Android Development] Shaquiel Harris:
I wiped, reinstalled stock then ota, used the su install option just now. Will let you know if it works. Ill check on it in about 15 minutes. Thank you again for the flashable update!
[ONE Original Android Development] LiquidSolstice:
Yeah, I'm at 12 minutes now after clean flashing 25R, rebooting, and then flashing OTA.

Something isn't quite right here.
[ONE Original Android Development] bose301s:
I had 0 problems just downloading the file from AFH and installing it as a zip in TWRP just like you would any other zip or ROM, didn't lose any data, only lost root which I got back by letting TWRP restore it and installing SuperSU.
[ONE Original Android Development] Negan:
Plug in your power cord to something like your PC and give it 2 min. If still nothing then hard reboot and see.

Just a hunch
[ONE Original Android Development] LiquidSolstice:
Bummer, didn't seem to work.

I appreciate you putting the zip up though, it seems to be definitely working for some people. Wish I was one of them.

I guess I'll try again.
[ONE Original Android Development] Negan:
Yeah keep trying. I can't see why I won't work
[ONE Original Android Development] Kerjifire:
I'm having an issue, I locked a folder with 2 apps in it, I clicked to remove on it from that folder and now I can't find the app in the drawer? Bug? Its the People app I lost, I can't even open it anymore

EDIT found a way to show the app again, long hold on homescreen, press the 3 dots arranged in an upward arrow, scroll down to protected apps, re enable the app :D hope this helps anyone
[ONE Original Android Development] tpcrackpipe:
Worked perfectly for me and I had xposed and other system mods activated. I just wiped cache and dalvik before and after Flashing. Flash took about a minute. Saw splash screen for about 1 minute then "android is upgrading" where the apps are counted for a couple minutes. Everything worked perfectly. Thank you.