Database Users

[Q] Milestone 2 on CM9 unknoweird issues!

Hi everybody, this is my first post, though I've been a reader from a long time ago.
Long story short: I received this milestone 2 from my brother, my other phone is a defy (cm7), I use both of them, updated to cm9 on milestone, milestone kaput, need help, has anybody got a clue on what is going on with my phone?
Last night or so I grabbed a copy of the latest CM9 rom from the forum, installed it and really loved it. Except for two messy TINY things. except for that I cannot believe I got almost 2 days of battery out of it!!!
First issue: Google apps, I mean anything google related, won't work and FC. even if I am am on the browser, and try to type an address, the second google search kicks in to show suggestion dara! dead google crap.
Second Issue: Home button won't do anything. I mean the phone does vibrate when it is pressed, by the way I already chcked for key assignments, not even long-pressing it will show any response except for the vibration.
Third issue: Say Im reading something, lock my phone... when unlocking it, it won't show me the lockscreen, even though it is activated.
at first I said "ok let's swap launchers maybe I can make it go away" and so Ive tried ADW ex, trbuchet and a couple more, with no success, going back to ADW regular, a very nice thing here, is that video recording has worked well since the first time I flashed the rom.
Thanks for your eventual responses!!
I almost forgot: this is what I have done until now: flashed and reflashed at least 6 times, flashed gapps, flashed gapps fix, in many combinations, wiping the hell out of the phone every time... I'm really stuck in here!
Ive also searched not only the forums but the internet aswell, and I find my googling skills pretty decent to be fair

New developments!
So, I got a little curious.. I had installed on my milestone the ics alike cm7... or so I remember, (if it was a theme my bad, anyway...) I was going through phone information, and I noticed something strange:
Android version: 2.3.7
mod version: CyanogenMod-72-111215..........NIGHTLY Milestone 2 gb
Build number: Gingerbread GWK74 CyanogenMilestone 2
so one does not have to be a genius to just see that I *may* have not applied the update, or that the updating process was somehow incomplete.. question has anybody who has ever applied CM9 on their phones came to this issue?? have you applied the update via cwmod or stock recovery or wtf am I doing wrong here uh?
I am really, really puzzled!!

cm7 has a theme that make it looks like ICS but its still a gingerbread (2.3.x android version).
CM9 is the real ICS.
You installed CM7 with a ICS theme, as we can see in your mod version: CyanogenMod-72-111215..........NIGHTLY Milestone 2 gb

knew that already!
yup dude, you are totally right, I may have confused you people along my post...
I have had installed CM7 with the ICS theme, the one with the 2.3.6 android
However, I grabbed a copy of CM9 from this forum (the one based on tezet's work, that first one on the dev thread...)
I flashed that file via cwm..
and I've had, as I state on mi first post here, flashed, reflashed, recontraflashed the thing, and resseted my phone to factory so much that it has got to be newer than brand new now... just kidding..
anyway, thanks for your interest man, my bad!
I've just re-read my post.. I never mentioned that I already had installed CM7 on my milestone!

LOL.
Try this:
In the bootmenu you can choose between "stock" "custom or "latest" recovery, try with a different one i think it worked for me when i used custom recovery.

LOL :S
Dude lol I think I've just messed up BIG TIME.....
well seeing how it didnt seem to work out any way, thanks for pointing out the other recovery methods btw.
I may have not told you the whooole story
the freaking usb connection wont work.. it hasn´t worked since I got the phone nor it has worked now.. the charge led will never turn on, or will the pc or mac or whatever I plug it into react somehow to it.
anyway, I may have flashed the rom again in stock recovery and this is where things got nasty... It doesnt get past the boot logo, which by the way, was the red M logo, the last time I remember it to boot (even after re re re re re re flashing the CM9 rom!!!!!) it had another one.... weird uh????
now it gets even weirder just read this thing!!!
The phone will get past the red M logo, then the screen goes black, but I can see it is lit...
I waited for a really long time (more than 30 minutes) to see no response..
took out the battery... did not power it on again as i had stuff to do..
I dont know why, but I plugged it into the usb cable.. (I was working on the computer) And the phone turned on!!!!!!! so I guess It is not a busted usb port???
I went on ahead to go to bootloader, and when I plug the cable it is shown as such!!!
sadly, rsd does not recognize the phone as plugged, even though the phone says it is indeed plugged in...
what the hell is wrong????
is there any way I can flash anything if Im stuck after the red M?
this sucks

Oh man...
There are 2 versions of gingerbread kernels, the chinese and the European. As i understand you've flashed the wrong version (CH rom over EU GB kernel or otherwise).
You can try flashing the fixed_sbf which is the CH kernel. Or you can try the below, which is my suggestion:
Download the 2.3.4 EU (UK) SBF flash it through RSDlite and then root, installl bootstrap, bootmenu and then the CM9 EU GB rom.
TWO IMPORTANT THINGS: NEVER INSTALL 2.3.6 VIVO OR PERSONAL ARGENTINA SINCE THEY ARE UNROOTABLE!! And also never use RSDlite when you are running low on battery.
And the MS2 is safe for flashing since it has a locked bootloader so its VERY hard to brick it. Your screen is black because it is in the bootloader mode.

Do not Vivo and Claro 2.3.6 roms
Be careful, VIVO and CLARO roms should not be used.

dafuq!
Nite! my man, I´ve been careful enough to avoid flashing wrong kernels so no, the answer is not there..... sadly...
I cannot interact in NO way with the device via USB, so flashing through RSD is a no-go.........
I do have another phone though.........
so the main prob here is now I do know what to do.. I think I´ve always knew rsd is the way to go.. as for the locked BL, yeah! Ive been into motomodding since the c350.. I really think I do know my way in the motorola mess if you know what I mean, OS may have changed but the system's structure's still the same **** from the old days!...
Basically now my question is this:
what the **** can I do given what I have??? (a non working usb connection, and a phone stuck at Bootloader OR stock Recovery....)

donlloreda said:
Nite! my man, I´ve been careful enough to avoid flashing wrong kernels so no, the answer is not there..... sadly...
I cannot interact in NO way with the device via USB, so flashing through RSD is a no-go.........
Click to expand...
Click to collapse
if power+up arrow and then flashing via rsd don't work for you
you only have two options - first is power+x and then @ which gets you to build in recovery (try to wipe or find an update.zip that can be flashed [if there is any - never did that myslef])
or flashing from your custom recovery if you have one installed
that is all i know (but i only have milestone since tuesday )
good luck anyway

Geez man!!!
So have you tried using another usb cable? Cause i've exhausted my theories about your problem... sorry

every freaking cable
As I got it as a gift, I thought my defy´s charger was "not powerful enought" even though that was absolutely ridiculous...
I went and try to buy the charger but nobody in here seems to know the pnhone so I would be kind of afraid to take it to service

Une petit question
so I think I found a really good site with *loads* of firmwares, branded debranded, official etc...
just to be sure, I tried to flash the update again in stock recovery (pwer + x) but at some point the installer promted some error about signature verification in the whole file.
so my question(s) are:
can I make a file *signed* in any way? if so can you point me out where and how to start?
and just to be on the safe side: If only if only I can grab something that I would be able to flash via stock recovery... I should flash a 2.3.7 based one right? If I do try and flash something lower I would make my problems worst right???
btw, If the phone freezes or sometimes goes through the red M, but there is no led lighting up, can I still go into custom recovery eg. CWM???

About the signing the zip file, yes you can, but i don't know how search in the "Android Development" section. But sbf files cannot be signed... if you discover how you will be the MS2 savior!
In the CWM you can flash just about anything as it can be reversed by flashing sbf's, on the otherside, YOU SHALL NOT FLASH!! Any VIVO or PERSONAL ARGENTINA 2.3.6 rom (sbf) cause they are unrootable. You should do just fine flashing the 2.3.4 UK.
And i don't think you will be capable of entering the CWM if the led doesn't flash cause it's an error that happens before CWM is started. In this cases you will have to flash sbf's, root.... all over again.

thaks man, but......
then the only way give I cannot flash under RSD, is making a "completeupdatewhateverCMorMIUUdafuq.zip" signed so I can load it through stock recovery rite???
remember CWM not availible.. nor USB interface...
will search though on "signing" an update file, yes that 2.3.4 UK you said.. from there I'll just try to make it match my defy

a little discovery!
Source: http://www.londatiga.net/it/how-to-sign-apk-zip-files/
When publishing an application or a custom rom you need to sign the .apk or .zip files with a certificate using a private key. The Android system uses the certificate to identify the author of an application and establish trust relationship between applications.
The classic way of doing this was to use keytool then sign it with jarsigner. In this tutorial i’ll explain an alternative method which is relatively easy to use for most people using a tool called SignApk.jar.
SignApk.jar is a tool included with the Android platform source bundle, you can download it from here.
To use SignApk.jar you have to create a private key with it’s corresponding certificate/public key. To create private/public key pair, you can use Openssl. Openssl is relatively easy to use under unix/linux system. For Windows user, you can download Windows version of Openssl here.
How to create private/public key pair using openssl (windows version)
Download openssl package from google code link.
Extract it anywhere...
Within openssl directory type (using cmd admin mode: ctrl+shift+r then cmd):
- openssl genrsa -out key.pem 1024
- openssl req -new -key key.pem -out request.pem
- openssl x509 -req -days 9999 -in request.pem -signkey key.pem -out certificate.pem
- openssl pkcs8 -topk8 -outform DER -in key.pem -inform PEM -out key.pk8 -nocrypt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(dload SignApk.rar)
Extract it anywhere
If you don’t have java installed, download and install it.
Copy certificate.pem and key.pk8 into your extracted SignApk directory
Within SignApk directory type (again using cmd admin mode: ctrl+shift+r then cmd):
java -jar signapk.jar certificate.pem key.pk8 your-app.apk your-signed-app.apk
OR
java -jar signapk.jar certificate.pem key.pk8 your-update.zip your-signed-update.zip
Note:
If you don’t want to create your own public/private key pair, you can use test key included in SignApk.rar.
Sooooo now what the hell do I have to sign???
LOL I'll go for the update I was trying to install at first... if anything goes wrong I'll just take it to service I guess have the USB repaired and RSD the hell out of it.. after all this is a reaaaaly great great phone uh?
maybe I should go first with the UK you suggested man?

About my last post
Hello everyone, so... the signing didnt went well LOL -.-
I guess I have to make the "signature" to match moto's right?
how can I get hold of that signature information? I mean can I download a signed (official) update, which is flashable via stock recovery (is there any???) extract the signature information, and then apply it to my package??????
Ok, now just to put things on the clear side: the instructions in the last post were not written well, but you may already knew that if you read the post.
anyway, as for the problems I ran into:
1: ctrl shift r does not do ****... just typoe cmd on the start menu, right-click it and run as admin.
2: It is EASIER if you copy everything to the root of your drive, and give files and folders short names!
3:
openssl genrsa -out key.pem 1024 <here you may run into an error regarding openss.conf.... just copy openss.conf from openss directory to openss/bin/ directory....
openssl req -new -key key.pem -out request.pem
openssl x509 -req -days 9999 -in request.pem -signkey key.pem -out certificate.pem
openssl pkcs8 -topk8 -outform DER -in key.pem -inform PEM -out key.pk8 -nocrypt
ok from now on it is pretty straightforward, I haven't got time to play around but, There is a step in which the program asks for your Company's name, adress, etc.. maybe if you knew what info is in motorola's signature you can make this fields match??
well I don't know.. but ill try and discover it!

donlloreda said:
I mean can I download a signed (official) update, which is flashable via stock recovery (is there any???) extract the signature information, and then apply it to my package??????
Click to expand...
Click to collapse
Nope and nope. Please learn something about signatures, how they work etc. You can't (obviously) "extract" the private key from the signed file... The signing would be useless then - don't you think?
donlloreda said:
anyway, as for the problems I ran into:
Click to expand...
Click to collapse
Seriously? I think you are not from IT industry, right?
donlloreda said:
ok from now on it is pretty straightforward, I haven't got time to play around but, There is a step in which the program asks for your Company's name, adress, etc.. maybe if you knew what info is in motorola's signature you can make this fields match??
well I don't know.. but ill try and discover it!
Click to expand...
Click to collapse
Stop it. You just wasting your time.
Your real options:
1) Get signed update.zip from Moto (I don't think there is any and I did not saw any)
2) get your USB port fixed and flash it via RSDLite. (if it is HW problem - just fix or get it fixed, otherwise, you are doing something wrong)
RSDLite and SBF flash is your only realistic option.
RSDLite works everytime. You can not break (except for HW issue) your M2 the way, it will not work with RSDLite.

[TUTORIAL] How to change the MODEL ID of the HTC One including video link

MOD EDIT
Seems this guide, if not properly followed will cause a (soft)brick. Also there are more up to date guides.
[how to]change your MID without the eng bootloader
[TOOL] MID change without ENG HBOOT | Aroma GUI
In the interests of all users the guide is hidden, below.
If you wish to follow it go ahead. If you brick your handset, you were warned.
FIRST OF ALL THANKS AND CREDITS GOES TO THE FOLLOWING XDA MEMBERS
@fnoji111​ for working on the ENG HBOOT in the Droid DNA forum
@Argumentation​ for creating the flashable zip that I used for this tuttorial
@daddioj​ for doing the leap of faith and used the ENG HBOOT on his device which lead me to writing this tutorial
NOTE: I created this tutorial because HTC One has different variants. After reading mike1986. article on HTC One variants I realized why I can't install OTA updates with my model ID (MID). Now since we have S-OFF I wanted to get updates from the UK. But since I have a different MID to the UK version, I can't install OTA updates. And this is the only solution I found to work at this time. So I hope it will help people who wants to change their MID​
VIDEO LINK AT THE BOTTOM OF THIS POST​
REQUIREMENTS:
1: S-OFF
2: KNOWLEDGE OF ADB COMMANDS
3: PATIENCE
PLEASE MAKE SURE YOU PAY ATTENTION TO EVERY STEP ON THIS TUTORIAL
***** I WILL NOT BE HELD RESPONSIBLE IF YOU BRICK YOUR PHONE*****​
STEP 1:
Make sure you don't have HTC Sync Manager installed, if you do uninstall it!! Also make sure you have HTC drivers installed!
Step 2:
Go here http://forum.xda-developers.com/showpost.php?p=38180376&postcount=6 and download the Argumentation's zip file
Step 3:
After downloading the PL83IMG.zip you will need to edit the android-info-txt inside. Please see sample picture below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 4:
Now you have to place the zip file in C:\Android SDK\sdk\platform-tools folder. I know some people don't have the same directory as I have so this is just an example. Just make sure you place in the platform-tools folder.
Step 5:
Now connect your HTC One (MAKE SURE YOUR DEVICE HAS PLENTY OF CHARGE) to your PC and start a command prompt in the "platform-tools" folder. The quickest way to do this is (see picture below):
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone.
NOTE: When you run the RUU and it says "waiting for bootloader" you will need to restart your phone manually by holding down the power button for a few seconds until it reboots. EACH TIME (does it twice) the RUU says "WAITING FOR BOOTLOADER" you will need to restart the phone manually​
You will not lose S-OFF and still have unlocked bootloader. I suggest that backup all important stuff before doing this I hope it helps.
If the mods feels that this doesn't belong here, please feel free to remove it. Thanks.
Here's a short video that shows how I changed my MID (model ID) on my HTC One

Just a side note: better to edit all kind of text with notepad++.
1) It formats text better (not just one single line)
2) It keeps Unix coding if needed
EDIT 05.12.2013 by the request of user @alray
THIS METHOD WILL NOT WORK USING WINDOWS 8.1
After flashing ENG hboot, Windows 8.1 won't detect the device and fastboot won't work, so you can't change MID and execute the RUU. (win 8.1 drivers issue).

I'll give this a go shortly

The warning on step six makes no sense
Does it automatically reboot after flashing the zip or what
Sent from my HTC One using xda app-developers app

tyler1234567 said:
The warning on step six makes no sense
Does it automatically reboot after flashing the zip or what
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Which warning? Like it states in the last picture when you flash the ENG HBOOT it will get stuck at 3/4 of a way in the status bar. You will need to restart the phone yourself. Then you will get a gray screen and won't be able to see anything. You might think it's bricked but it's not. You just have to proceed with adb command to write the MID and then another adb command to write the CID.
Once you have changed the MID and CID. You may have to reboot your phone and then run the RUU even when it's only a gray screen you see. The RUU will flash back the proper HBOOT and you will see the RUU screen (black screen with HTC logo). Just be patient and wait until the RUU is finished its operation. And that is it.
I will make a video when I get home to assure people that this mod works.

Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.

shadowboy23 said:
Which warning? Like it states in the last picture when you flash the ENG HBOOT it will get stuck at 3/4 of a way in the status bar. You will need to restart the phone yourself. Then you will get a gray screen and won't be able to see anything. You might think it's bricked but it's not. You just have to proceed with adb command to write the MID and then another adb command to write the CID.
Once you have changed the MID and CID. You may have to reboot your phone and then run the RUU even when it's only a gray screen you see. The RUU will flash back the proper HBOOT and you will see the RUU screen (black screen with HTC logo). Just be patient and wait until the RUU is finished its operation. And that is it.
I will make a video when I get home to assure people that this mod works.
Click to expand...
Click to collapse
Oh ok I got ya. Didn't see that before.

Xstop said:
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
Click to expand...
Click to collapse
If it doesn't belong here then the mods can delete that is fine by me.
EDIT:
Just sent a message to one mod so he can delete this thread if it doesn't belong here.

thank you very much it worked like a charm just changed a tmous mid so far so good waiting to install ota

Xstop said:
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
Click to expand...
Click to collapse
False. How is this not developement. And if this isn't developement then neither is the cid thread, or all the stock rom threads.

shadowboy23 said:
If it doesn't belong here then the mods can delete that is fine by me.
Click to expand...
Click to collapse
No harm, just easier to follow one thread since I am interested in this.
I converted my ATT One to the Dev Edition (hoping that nothing ATT is on m phone now except service), easy since both have the same MID but will be doing this for the PN0710000 soon.
Thank you for the tutorial. :good:

so to make sure i just put the same info from the YOUR text file picture in the one i downloaded ?

CheesyNutz said:
so to make sure i just put the same info from the YOUR text file picture in the one i downloaded ?
Click to expand...
Click to collapse
Which one? Do you mean the "android-info-txt"? If that's what you meant then you have to put in your current model ID, CID and ROM version..If it's the same as mine then you just copy what is written in the first picture. Just remember that Argumentation's zip file is intended for Droi DNA but all you have to edit id the "android-info-txt" and you don't have to touch the HBOOT.nb0.

A video lesson would be perfect

Tried to do something, but adb is not for me, I guess...
It would be perfect to change from carrier to free uk version..

darenas said:
A video lesson would be perfect
Click to expand...
Click to collapse
Uploading now, will post it in the OP when finished. The video is not a tutorial of some sort but more of a guide. It just shows you the process of actually flashing the ENG HBOOT and what I typed using adb/fastboot commands.

shadowboy23 said:
Uploading now, will post it in the OP when finished. The video is not a tutorial of some sort but more of a guide. It just shows you the process of actually flashing the ENG HBOOT and what I typed using adb/fastboot commands.
Click to expand...
Click to collapse
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly...
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
darenas said:
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly...
Click to expand...
Click to collapse
I see already.

darenas said:
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly..
Click to expand...
Click to collapse
Well my phone has S-OFF and have a unlocked bootloader. S-OFF is a MUST! You will see in the video very clearly what I type in adb/fastboot so I'm pretty sure people can work it out.

Video link is up! It is at the bottom of the OP. I hope it helps people.

Done with OTA :thumbup:
Sent from my HTC One using Tapatalk 2

[12/29] Restore for MJ5 --Doesn't trip Knox and optionally provides root--

Update:
After repeatedly, and unsuccessfully, attempting to take total ownership of my phone, I've switched to T-Mobile and will no longer maintain this thread. Thanks to those great many donors who've contributed to support this device and my effort, and best of luck to those who still have the drive to support this device.
A Special Thanks to the Following Donors:
@acdcflame
@lilhacker
@JAKISTER
@royal1262
Click to expand...
Click to collapse
---UPDATE---
If this is your first time recovering to MJ5, please follow all steps.
If you've already ran through this method successfully once, you can start at step 5
**Thanks to:
147aaron - OTA update
Designgears - RDLV
A.S._id - MJ5 Firmware
drakeymcmb - kn0x0ut support / mirror
1) Download and install Heimdall from here for windows. You'll need this and this to avoid missing .dll file errors
2) Download the following files;MI9_fix.img.ext4
https://mega.co.nz/#F!icMTnSQY!bMBNFmUnn2_K8olSTYpwIA (mirror provided by drakeymcmb)
sec_csc.zip
rldv.zip
2400258.zip​Put everything except for the system.img on your external SD card
3) Download and install the MJ5 partions. Use Odin to flash these files (match the file names with the different upload slots)AP_N900AUCUBMJ5.zip​BL_N900AUCUBMJ5.zip​CP_N900AUCUBMJ5.zip​HLTE_USA_ATT_32G.pit​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4) Now is the time to use Heimdall.
Reboot into Download Mode once Odin finishes.
Install the vcredist packages downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message
5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.
IMPORTANT -- Go to the Utilities tab and click the "Detect" button
Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.
click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.
6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery
7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.
8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you remember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place
9) IMPORTANT--After flashing the sec_csc, the Note will reboot.
Try to catch it in time to reboot BACK into recovery
Once in recovery, select "Choose update from external" in the recovery, and select the 2400258.zip you downloaded earlier.
This will give you a stock MJ5 system. You can choose to stop here if you don't want to root.
10) Extract rldv.zip to the root of your internal sdcard (NOTE **my script removes Knox apps). Reboot, then once SuperSu installs, Reboot again.
This leaves you with a rooted MJ5 device.
If this helped, please hit thanks or donate
I'm finishing up a custom rom image for us. We'll be able to flash it without the inventive, but dirty, kn0x0ut script.

Thanks alot. Now people shouldnt be scared to try out my rom flashing thread. I have good news for you, if you go to my thread, i think i found a fix for all the problems people were having with the international roms. Its the last post in my thread.
Keep up the good work,this is useful
If your already on mj5 and you softbrick, does this still work?

drakeymcmb said:
If your already on mj5 and you softbrick, does this still work?
Click to expand...
Click to collapse
It does indeed. I was softbricked but recovered using this method.

So the only thing that an unlocked bootloader allows at this point is custom kernel and peace of mine right.
Sent from my SAMSUNG-SM-N900A using Tapatalk

Yes. And not having to use a computer when you want to change roms.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

gordec said:
So the only thing that an unlocked bootloader allows at this point is custom kernel and peace of mine right.
Click to expand...
Click to collapse
Unlocking the bootloader would also allow us to use custom recovery, and the custom kernels would also allow us to run AOSP based roms
---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
Now on another note, I'm on MJ5 and I see where you say we can stop after flashing non-rooted MI9. Theoretically, wouldn't I be able to continue to root and then be able to use the kn0x0ut script to flash a custom rom?

KingRedHot said:
Unlocking the bootloader would also allow us to use custom recovery, and the custom kernels would also allow us to run AOSP based roms
---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
Now on another note, I'm on MJ5 and I see where you say we can stop after flashing non-rooted MI9. Theoretically, wouldn't I be able to continue to root and then be able to use the kn0x0ut script to flash a custom rom?
Click to expand...
Click to collapse
You are correct. At that point you can either upgrade to mj5 or run kn0x0ut.

Wow this is awesome. You are a genius
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

I seem to be stuck on step 9.
I'm not sure how to get to the root filesystem with my phone not yet rooted. Much less have the permissions to write files there i.e. copy and/or extract the rdlv to /system/
I can initiate an adb shell session in userland as "shell" but not as root. Can you clarify this step please? I seem to recall when I first rooted my phone with MI9 that I had full access to the filesystem (even just using explorer.exe) after using the designgears oneclick utility.
update:
well my impatience got the better of me and i went to the darkside and rooted with kingo. installing wanam now and everything appears to be ok. If there's an obvious assumption i'm missing that didn't allow me to complete step 9 i would like to know though since the more elegant solution is the preferred one

Download and install the MJ5 partions, using Odin, from here.
Im stuck on this step what files am i downloading? theres 5 files on the link.
---------- Post added at 01:36 AM ---------- Previous post was at 01:35 AM ----------
Download and install the MJ5 partions, using Odin, from here.
Im stuck on this step what files am i downloading? theres 5 files on the link.

[email protected] said:
I seem to be stuck on step 9.
I'm not sure how to get to the root filesystem with my phone not yet rooted. Much less have the permissions to write files there i.e. copy and/or extract the rdlv to /system/
I can initiate an adb shell session in userland as "shell" but not as root. Can you clarify this step please? I seem to recall when I first rooted my phone with MI9 that I had full access to the filesystem (even just using explorer.exe) after using the designgears oneclick utility.
update:
well my impatience got the better of me and i went to the darkside and rooted with kingo. installing wanam now and everything appears to be ok. If there's an obvious assumption i'm missing that didn't allow me to complete step 9 i would like to know though since the more elegant solution is the preferred one
Click to expand...
Click to collapse
No problems. Kingo works fine. But, to answer your question-you should always have write access to your internal sdcard -- hook your phone up to your comp and it's the folder called "phone" that pops up. I apologize if that wasn't clear.

Can someone make a video of this? I would need help with Step 2 and Step 9 specifically.

Fidelio_o said:
Download and install the MJ5 partions, using Odin, from here.
Im stuck on this step what files am i downloading? theres 5 files on the link.
---------- Post added at 01:36 AM ---------- Previous post was at 01:35 AM ----------
Download and install the MJ5 partions, using Odin, from here.
Im stuck on this step what files am i downloading? theres 5 files on the link.
Click to expand...
Click to collapse
All of them you may want to review the context of that post as well as reading through the OP of that thread. Using Odin, it should be clear as to where each of those files are intended to be flashed.
I would like to remind everyone that flashing anything on a phone as (expensive) locked down as our phone is, is dangerous. It may be why we are all here reading this post, but, if one of the steps includes something you've never heard of, please take the time to read more about it. You may learn about other things that will help the community achieve full control of our device! We need everyone at this point. I'm drafting an army of the willing

evilpotatoman said:
No problems. Kingo works fine. But, to answer your question-you should always have write access to your internal sdcard -- hook your phone up to your comp and it's the folder called "phone" that pops up. I apologize if that wasn't clear.
Click to expand...
Click to collapse
Aha, i guess for some reason i was under the impression that the shell script and the rdlv directory needed to be written to the /system/ (owned by root with 755) directory. Not sure why when i was looking at the "phone" mount point it didn't look to me like the root directory of a nix filesystem. Regardless, i really appreciate you putting this together / figuring it out. My phone has been FCing for about 3 weeks now . Hopefully other folks have similar success stories.

I haven't tried any of this as of yet, but plan to later today when I have some time. This might just be the best early Christmas present I've ever received. I was on the verge of buying a TMO Note 3 later today just to be able to load a custom ROM... this appears to make that unnecessary. If so, maybe I'll take some of the price difference between my subsidized ATT Note 3 and the TMO Note 3 and add it to the bootloader unlocking bounty.

rooted_1 said:
I haven't tried any of this as of yet, but plan to later today when I have some time. This might just be the best early Christmas present I've ever received. I was on the verge of buying a TMO Note 3 later today just to be able to load a custom ROM... this appears to make that unnecessary. If so, maybe I'll take some of the price difference between my subsidized ATT Note 3 and the TMO Note 3 and add it to the bootloader unlocking bounty.
Click to expand...
Click to collapse
the links are down

Could you be more specific in your instructions? You are missing so many things, there you change the name of many options, its so confusing that way

drakeymcmb said:
the links are down
Click to expand...
Click to collapse
If we need space and bandwidth for hosting the files, someone please PM me. I'll be glad to get something set up between later this evening and tomorrow (it will probably be tomorrow). I'm happy to help the effort if I can.

Can someone make a video?

Can somebody who downloaded this make a mirror. The links for dropbox are down.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

[uncontinued]HOWTO stock|Lenovo Yoga Tablet 8"/10"[4.2.2] + Easy KITKAT[4.4.2] ROOT!

[uncontinued]HOWTO stock|Lenovo Yoga Tablet 8"/10"[4.2.2] + Easy KITKAT[4.4.2] ROOT!
EDIT:Since my device died in my bathroom, I cannot continue the support for this thread!!!
This is a guide for restoring the stock Lenovo Yoga Tablet 8 (B6000) and Lenovo Yoga Tablet 10 (B8000) ROMs [Android 4.2.2] (not for Lenovo Yoga Tablet 10hd+)​
To root your KitKat Yoga go to the second post.[*]​
This guide is just a translation from russian Lenovo forum.
All credits belongs to them. All image - rights belongs to them too.​
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research before flashing it! YOU are choosing to make these
* modifications.
* This should be the last option, you'll do, if your device is soft-briked
* or the software
* is too damaged (from rooting etc)
*/
Russian was my native language once (now I'm living in germany and my russian "skills" are little bit lower ) And my english isn't very good too. So if yo don't understand what i mean, just ask in PM.
Versions: 4.2.2 Android for 8" and 10" Yoga Tablets (WIFI, 3G and WW_CALL)
ROM: Official Lenovo
OS: Android 4.2
Languages: Multilanguage (chinese, english, german, spanish, italian, etc
This guide works only with Windows (XP, Vista, 7, 8)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At first let's begin with the ROM - download itself. There are different versions of those tablets, so choose wisely
I'll post only the Android 4.2.2 versions of the rooms, if you want, you can update them by yourself with the OTA. It is because at the moment you can root the JB - version more easily. (FRAMAROOT for 4.2.2 Jelly Bean versions only!!)
You have to register on this forum for download - permissions!!
Lenovo Yoga Tablet 8":
[ROM] Yoga 8 B6000_A422_000_059_131219_WW_WIFI
[ROM] B6000_A422_000_084_140310_WW_CALL
[ROM] Yoga8_B6000_A422_000_084_140310_WW_3GDATA
Lenovo Yoga Tablet 10":
[ROM] Yoga 10 B8000_A422_000_085_140402_WW_WIFI
[ROM] Yoga 10 B8000_A422_000_084_140310_WW_3GDATA
for download click on the green button on the top right side:
1. Drivers
Click to expand...
Click to collapse
Now, whyle you are downloading the ROM, lets look at the drivers you'll need.
At first you need Lenovo USB Driver [from this site] version 1.00.11. 9,28mb
Next step youl need some other drivers and tools:
Driver for USB "download mode" [download it, unzip and place it on your desktop.
SP Flash Tool Driver Auto Installer [9,49mb] - works only with Windows ХР SP2, Windows Vista, Windows 7.
for installing unsigned drives on Windows 8, follow the guide below:
Get access to Startup Options: HOWTO - Method 2 is the easiest way for me
Once you are there (After a restart) you have to choose number 7 (Disable driver signature enforcement)
When you install unsigned driver after it, windows is allways asking you this:
- install this driver anyway
2. Install the ROM
Click to expand...
Click to collapse
What do you need:
At least 30% of battery
All Driver from above and unzipped driwer for "Download mode"
time
Now let's begin.
Install the USB driver.
Unzip The ROM and put it on your desktop.
Turn off your device and unplug it from USB (if its pluged in).
for Windows 7/Windows Vista/Windows XP: Install the SP Flash Tool Driver Auto Installer from above and jump to step 7.
go to "Device Manager (link for short guide)
now when you are in your device manager it'll be a little bit tricky. When you NOW plug in your device (it have to be turned off), a new "unknown" device will appear. It will be there only for a few seconds, so you habe to be quick. RIGHT-Click on this unknown device and then go to "Update driver" in preferences. Then choose the driver you had downloaded and unzippt on your desktop. Thats it!
Now start the FlashTool.exe, (I think which you'll find in your unzipped ROM in the "Upgrade tool" folder. And plug in your device (micro USB)).
Click on "Scatter loading" (like on the image above). Then go to your ROM (you know, on your desktop) and in folder "target_bin" choose this file: "MT6577_Android_scatter_emmc.txt" (I am nbot shure if its the same name on all ROMs, but it has to be something with "scatter" in its name.
Click on "DA DL ALL WITH Cheksum" (without it, the device wont start after flashing and you have to flash all again) you'll see it on the pictures below:
The "FAC" - file will be propably not checked.
Just choose it in your ROM folder by yourself in target_bin folder:
Click on "Firmware -> Upgrade"
Then you'll see some pink lines loading. When the lines bekame yellow, you can skip the next step.
It can be, that after the pink lines the Flash Tool will stop and nothing will happen then. If it keeps for one minute you have to unplug your device for 30 seconds and than just plug in again. NOTHING ELSE!!!
When the green lines appears, just wait till its finished. You'll see it, when the green circle appears:
Unplug your device and restart. Don't panik, its multilingual and your language will be there (for shure), just click on the rigt chinese words in the first window which appears and scroll up.
After that you can easiely update your tablet to 4.4.2 with the OTA
Happy flashing =)

Easy Root your 4.4.2 KitKat ROM
HOWTO Root your 4.4.2 ROM:​
At first you have to know, whats behind all the followigng steps.
It is not that easy to root this device with KitKat (at least at the moment).
At first you have to install an app, which uses a hack and pushs a file in /system.
next you start the installed app (which is in /system now) and with this app (Kinguser) you'll have Root rights
most users dont believe in chinese root apps. So you have to install an another Rootapp, the best is SuperSU (link ist below)
After you allow SuperSU the root rights, you can just uninstall the other two apps and enjoy the happiness of beeing rooted
Click to expand...
Click to collapse
Now let's beginn:
1. Just download and install this file: Root_genious_General.apk
2. It will install a small tool, which can root your tablet. And it installs "Kinguser"
. It will ask you, to update your ROOT(1.0.23) to ROOT (1.1.33). It will be in chinese, just chose the right button and allow to update this tool.
3. A circle will appear with "ROOT" in it. "Push" the button and magic will happen (a progress bar) An yellow window will appear, in chinese, but you'll see, if it was a success then you'll see Kinguser installed on your device. (if it don't works for the first time, just try it again)
4. After that you need to reboot your device and download and install "SuperSU" from PlayStore.
5. Install SuperSU and then Kinguser will aks you, if you will allow SuperSU root rights. Chose "Yes" and now you have the rootrights. IF IT DOESN'T you have to reboot your device several times (don't know why, I needed several reboots and then it worked)
NOTE: I don't really know why, but it seems, like Kinguser do not recognize, that it has root permissions at the first time. I had to turn off the permission in Kinguser options, restart and give Kinguser the root permissions again, than restart again. Just play a little arround with whis option of Kinguser. Somehow it will work than. I had to do the game twice, and it worked both times. But really don't know why.
6. After that you need to update your binaries in SuperSU and reboot your device.
7. Then you can uninstall both chinese APPs (Kanguser can just be uninstalled with Titanium Backup) and you are rooted then

Hi, thanks for your post !
I can't go after the number 14 :/
At the bottom of the windows there is : Searching or USB but nothing happen.
I have installed LenovoUSBDriver and SP_Flash_Tool_Driver_Auto_Installer ...
I put the inf file in C:/windows/inf ...
I have tried in FastMode Boot on the tablet but nothing.
Where is my mistake ?
PS : I'm on Windows 7 x64
Thanks in advance and sorry for my bad English !

mpatate said:
Hi, thanks for your post !
I can't go after the number 14 :/
......
I put the inf file in C:/windows/inf ...
.....
Click to expand...
Click to collapse
I am not really shure, but I think its the step 6, what caused the problem. The drivers have to be installed manually, when you are plug in your device. it's not enough to "put" them somewhere. try to do this step by step, like i tried to translate
You open your device manager, turn your device OFF, plug it then on USB and than watch, when they appears a new device. very quick (you have 1-3 seconds I think), rightclick on it and than go to "Propperties", or "options" (dont really know what there is in your language ). then "Update your drivers" and then choose the drivers manually. I hope it will help.

aluk4rd said:
I am not really shure, but I think its the step 6, what caused the problem. The drivers have to be installed manually, when you are plug in your device. it's not enough to "put" them somewhere. try to do this step by step, like i tried to translate
You open your device manager, turn your device OFF, plug it then on USB and than watch, when they appears a new device. very quick (you have 1-3 seconds I think), rightclick on it and than go to "Propperties", or "options" (dont really know what there is in your language ). then "Update your drivers" and then choose the drivers manually. I hope it will help.
Click to expand...
Click to collapse
Waou, fast reply !
This is OK now, I don't know why, I restart the tablet and the software begin the work !
Now it's reboot and I have to choose my langage, thanks for all !

mpatate said:
Waou, fast reply !
This is OK now, I don't know why, I restart the tablet and the software begin the work !
Now it's reboot and I have to choose my langage, thanks for all !
Click to expand...
Click to collapse
have a night shift right now
you are welcome!

OTA?
what is OTA? u say it for upgrade 4.2.2 to 4.4.2

VelaJuel said:
what is OTA? u say it for upgrade 4.2.2 to 4.4.2
Click to expand...
Click to collapse
OTA means Over The Air it is the way how most devices are updating via wifi.

Question
Good evening I would like to ask you to do the tempering the rom that you put should be the same as the build number of the device that I have or that does not matter does not play a role build number ???

VelaJuel said:
Good evening I would like to ask you to do the tempering the rom that you put should be the same as the build number of the device that I have or that does not matter does not play a role build number ???
Click to expand...
Click to collapse
Good evening.
as far as i know it is always a good idea to take the same build number,as you have. it can brick your device,because it could always be, that there are differences in the hardwre and also the drivers,between the builds.

aluk4rd said:
Good evening.
as far as i know it is always a good idea to take the same build number,as you have. it can brick your device,because it could always be, that there are differences in the hardwre and also the drivers,between the builds.
Click to expand...
Click to collapse
well my build number is B6000_A442_001_023_140811_ww_wifi but i can't find the same any help about were can i find it ?

VelaJuel said:
well my build number is B6000_A442_001_023_140811_ww_wifi but i can't find the same any help about were can i find it ?
Click to expand...
Click to collapse
The buildnumer is B6000, and the only other important thing is the "wifi" at the end. So take just this one:
[ROM] Yoga 8 B6000_A422_000_059_131219_WW_WIFI
All the numbers between, are just patch-versions of your b6000 wifi Tablet

aluk4rd said:
The buildnumer is B6000, and the only other important thing is the "wifi" at the end. So take just this one:
[ROM] Yoga 8 B6000_A422_000_059_131219_WW_WIFI
All the numbers between, are just patch-versions of your b6000 wifi Tablet
Click to expand...
Click to collapse
so the only metters is the b600 and the wifi at the last? the other number's don't metter?
thank you very much i will do you guide and i will tell how it goes...

VelaJuel said:
so the only metters is the b600 and the wifi at the last? the other number's don't metter?
thank you very much i will do you guide and i will tell how it goes...
Click to expand...
Click to collapse
not really important for restore your stock 4.2.2 rom
good luck

Very good work
Thank you for ur post stock work's perfect for me just dont miss any step and will work thank u again...

Somebody can help me and upoad the original product tour video from 4.4.2.are deleted after restore

hi,
i'm stuck when the green circle appeared...
i stuck for more than 20 minutes...
what should i do?
redo whole process or wait for it?

hardia said:
hi,
i'm stuck when the green circle appeared...
i stuck for more than 20 minutes...
what should i do?
redo whole process or wait for it?
Click to expand...
Click to collapse
NOOOOOOO!
green circle is good it means you are ready. close the circle, close the software, unplug your device and start it

Please Help OP
http://forum.xda-developers.com/len...3300gv-rom-t2868596/post55266101#post55266101

-Aatif- said:
Please Help OP
http://forum.xda-developers.com/len...3300gv-rom-t2868596/post55266101#post55266101
Click to expand...
Click to collapse
Hello,
I am really sorry but I jujst can answer questions for my own device but i looked arround. as far as i can see, there is no stock rom to flash. I dont know if thats you, who postet this request in russian forum, but have a look there. The site admin will look, if he can find something [LINK]. Maybe he can find some help in chinese forums. Don't know, how he handle such requests.
You have a very special device number, build just without 3g for Ukraine, as I can see there. Hope, you'll find help there.

[DISCUSSION]All things Oxygen OS: Features, download, install, root, troubleshooting

READ THIS FIRST:​After downloading "oxygenos_1.0.0.zip" you will notice that it contains a folder with two files:
oxygenos_1.0.0_flashable.md5
oxygenos_1.0.0_flashable.zip
Extract oxygenos_1.0.0_flashable.zip first, then copy it to the SD card, wipe, flash, etc.
MultiROM works!
Check here and click thanks for MMWolverine.
New touchscreen driver to fix ghost touches:
Click here.​
__________________________________________
Just a weeeee bit late.
https://oneplus.net/de/oxygenos
__________________________________________
Download it here:​
Official:
https://forums.oneplus.net/threads/oxygen-1-0-2-release-with-stagefright-security-patches.340711/
There is a pre-rooted and de-bloated version by @CraZY_BoY^ right here:
[ROM][MOD] OxygenOS - Rooted | Cleaned | Some apps from CM
Features​
Screen-off gestures like double-tap to wake, music controls, and shortcuts for the camera and flashlight
Hardware and software navigation keys
Quick settings feature, tiles can be added, removed, and re-organized
Their own file manager, though it's pretty buggy ATM (see below).
Missing features:
Privacy guard
Double tap to sleep
Display color settings
Theming support
Custom camera app (uses Google camera app)
MaxxAudio and Swiftkey (coming in a future update)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation steps:​
Please make sure all your data and files are backed up before commencing. Flashing OxygenOS onto CM does require a system wipe, so you will lose all of your data. We are actively working on an easier, more automated solution soon to be available, but for now the build must be flashed manually.
Please proceed only if you are confident in your abilities to flash a custom ROM. This guide exists to help you flash OxygenOS, but things can still go wrong if not followed correctly. While rooting and flashing will not void your OnePlus warranty, any damage caused by improper flashing is not covered under warranty.
The following instructions assume you have Fastboot and ADB installed.
Step 1
You first need to flash a recovery onto your device. We recommend using TWRP. Please download the recovery image to your computer. You can follow their instructions to flash recovery, or you can reference these steps:
Boot into fastboot mode. You can do this on your OnePlus One by holding down the power button and the volume up button. When you see the fastboot logo, connect your device to your computer.
In your terminal window, find the folder where you put the recovery image and run the following commands:
fastboot oem unlock (You can skip this step if your phone’s bootloader is already unlocked).
fastboot flash recovery <recovery.img>. Image file should be the TWRP recovery image.
fastboot reboot
You should now have the recovery installed.
Step 2
Copy oxygenos_1.0.0.flashable.zip to your phone. On a Mac, you can use Android File Transfer.
Step 3
Boot into recovery. You can do this on your OnePlus One by holding down both the volume down key and the power button.
Step 4
Once you are in the recovery interface, the first thing you want to do is a factory reset. Again, you will lose all your data so please make sure you have backed up everything before doing this.
Step 5
After the wipe, go to install and find oxygenos_1.0.0.flashable.zip. Confirm flash. This will flash OxygenOS onto your device.
Step 6
After the flash succeeds, you can reboot the device, which will take you to the new OxygenOS. Enjoy!
If you find yourself wanting to rollback to CM, Make sure you have TWRP or CM recovery on the device. Another factory reset will be needed before flashing unfortunately so make sure you backup all of you data.
Click to expand...
Click to collapse
Source
To revert back to CM11/CM11s:​
Flash the latest CM11/CM11s modem from here.
Restore CM11/CM11s from a backup or flash new.
There is no need to reboot between steps 1 & 2.
Rooting Instructions:​
Just like CM11s, download SuperSU-v2.xx.zip to your SD card and flash from recovery.
Known issues:​
Reported by OnePlus:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
Reported here & elsewhere:
4k video is non-functional with Google camera.
Google Play Services wakelocks. Check here for a fix.
Other Stuff​
Wallpapers
Boot animation
Modem
Please click thanks for the guys that posted these for you.

CafeKampuchia said:
Just a weeeee bit late.
https://oneplus.net/de/oxygenos
Click to expand...
Click to collapse
Downloadning now! Lets see

very slow..hope for a mirror soon!

CoreGaming said:
very slow..hope for a mirror soon!
Click to expand...
Click to collapse
Its 700 MB

Nice to know, but I'll wait CM12s and then I choose what to do

I'm getting an average 100-150kbs using Firefox and DownloadThemAll. 1 hr 22 minutes left :/
Edit
Mine's shot up to >300kbs - 20 minutes left

Nothing like flashing a new ROM at 1:30AM!
Downloading now - Cant wait to get this thing running!

I am downloading on both my pc and my opo. on my the opo, it's taking 1 hour or so to download. on my pc it took 10 minutes. both on wireless on the same network.

Uploading to mega now, nearly half way, will post a link when finished.

gsmyth said:
Uploading to mega now, nearly half way, will post a link when finished.
Click to expand...
Click to collapse
Send me the link and I'll update the OP ASAP.

3rd feature according to this video is FILE MANAGER ARE YOU KIDDING ME
MEANWHILE STOCK BUG LIST:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
HOPING TO ROOT IT AGAIN VIA RECOVERY AND provide my feedback with xposed, viper sound mod etc

I'm really happy with cm12 nightlies, I'll wait for the reviews whats the battery like?

aravindhramachandran said:
3rd feature according to this video is FILE MANAGER ARE YOU KIDDING ME
MEANWHILE STOCK BUG LIST:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
HOPING TO ROOT IT AGAIN VIA RECOVERY AND provide my feedback with xposed, viper sound mod etc
Click to expand...
Click to collapse
Bug list in OP already, friend. Good point on the file manager. I'll add that to the OP as well. :good:

vacenzo said:
I'm really happy with cm12 nightlies, I'll wait for the reviews whats the battery like?
Click to expand...
Click to collapse
Dude, nobody even has it installed yet. And even if they do, it's been <1 hr. We'll know something tomorrow. :highfive:

mirror please. cant flash beacuse my download was corrupted and now the download is super slow. :crying::crying:

saar120 said:
mirror please. cant flash beacuse my download was corrupted and now the download is super slow. :crying::crying:
Click to expand...
Click to collapse
Read the comments.
Transmitted via Bacon

Guys, it keeps giving me error when trying to flash. Im on cm nightlies the latest one but for some reason it wont flash... i can flash other roms just fine

this is what happend to me as well. in the middle of the download i switched from wifi to 3g . i thought it was beacuse of that.

zee24 said:
Guys, it keeps giving me error when trying to flash. Im on cm nightlies the latest one but for some reason it wont flash... i can flash other roms just fine
Click to expand...
Click to collapse
Did you extract the zip? There is a flashable zip in the zip you downloaded.

There is a zip inside downloaded zip! Flash that.