Database Info

[Q] T300 install CM 10.1 and up to TWRP 2.7

I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.

RBraverman said:
I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.
Click to expand...
Click to collapse
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.

cmendonc2 said:
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.
Click to expand...
Click to collapse
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?

RBraverman said:
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?
Click to expand...
Click to collapse
Hope you get getter
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093

cmendonc2 said:
Hope you get getter
Click to expand...
Click to collapse
Thank you, slowly on the mend.
cmendonc2 said:
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093
Click to expand...
Click to collapse
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
So I need 3 things: newest F/W (have), Latest TWRP(don't have - yet but looking, 2.7 I believe), latest way to root(don't know) - Correct?
Again where is that thanks button!!!!!

RBraverman said:
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
Again where is that thanks button!!!!!
Click to expand...
Click to collapse
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.

cmendonc2 said:
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.
Click to expand...
Click to collapse
NOW it's there!
Okay upping to stock F/W, looking for TWRP (openrecovery-twrp-2.6.3.0-tf300tg-JB.img) then how do I root this

RBraverman said:
NOW it's there!
Okay upping to stock F/W, looking for TWRP - how do I root this
Click to expand...
Click to collapse
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.

cmendonc2 said:
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.
Click to expand...
Click to collapse
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?

RBraverman said:
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?
Click to expand...
Click to collapse
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much mroe optimized for older devices, and you should see a performance upgrade.

cmendonc2 said:
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Click to expand...
Click to collapse
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
cmendonc2 said:
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much more optimized for older devices, and you should see a performance upgrade.
Click to expand...
Click to collapse
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.

RBraverman said:
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.
Click to expand...
Click to collapse
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob

cmendonc2 said:
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob
Click to expand...
Click to collapse
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Just rebooted, and it's 4.2.1, but everything I had - most of what I had, is still there!?! And the run?

RBraverman said:
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Click to expand...
Click to collapse
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.

cmendonc2 said:
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.
Click to expand...
Click to collapse
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!

RBraverman said:
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!
Click to expand...
Click to collapse
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.

cmendonc2 said:
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.
Click to expand...
Click to collapse
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.

RBraverman said:
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.
Click to expand...
Click to collapse
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.

cmendonc2 said:
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.
Click to expand...
Click to collapse
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.

RBraverman said:
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.
Click to expand...
Click to collapse
I'm not sure what you are talking about with "fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img". As long as TWRP is working you shouldn't have to use fastboot anymore.
The new bootloader that you upgraded to only has 3 icons when you press vol-down and power. Fastboot now connects automatically if you turn on your tablet with the USB plugged in and pressing the key combo. To access TWRP, selecting RCK is the correct choice. As always, never select the Wipe Data in the bootloader menu or you will brick.
Before flashing new ROMs, you should only have to do the "swipe to factory reset" option in the TWRP recovery. If you update your ROM with a newer version of that specific ROM, you only have to Wipe Cache and Dalvik Cache.

error updating ota

i tried to update my opo 64gb from 33r to 38r by ota when it asks me to
but when it reboots in recovery(twrp in my case, i'm rooted and i have twrp recovery nothing else, neither xposed or things like that) it gives me error about updater binary if i'm not wrong
then i reboot to system and obviously it remain 33r
how can i solve this problem?
i read of people that get the same error and cant even flash other zips...

Updating your recovery to the latest TWRP (2.8.1.0) should solve your problem.
It's a known issue.

What's the exact error you get please?
Transmitted via Bacon

babbo96 said:
i tried to update my opo 64gb from 33r to 38r by ota when it asks me to
but when it reboots in recovery(twrp in my case, i'm rooted and i have twrp recovery nothing else, neither xposed or things like that) it gives me error about updater binary if i'm not wrong
then i reboot to system and obviously it remain 33r
how can i solve this problem?
i read of people that get the same error and cant even flash other zips...
Click to expand...
Click to collapse
if your rooted why are messing around with an ota anyways. Download one of Calkulins completely stock zips and your done

timmaaa said:
What's the exact error you get please?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah we need the exact error to see what's going on. Other than that, ota zip flashing with twrp will work but u might have to manually select the zip...
Download the ota zip yourself into your phone is available in a thread here somewhere search for it, reboot into recovery, select "install zip", browse to the correct ota zip, swipe to flash, clear dalvik then clear cache.
//edit
Just saw you're on 33r. Download ota zip for 38r and 44s. Make sure you flash them in the correct order don't mix them up!
Sent From Bacon

solved flashing via fastboot factory images with bacon root toolkit(i'm lazy :silly of 33r to see if it would update it and it did
i flashed 38r ota and 44s one as well
anyway i'm considering flashing cm11 stable builds...is there the option for slowmotion and othe things like gesture on off screen?

babbo96 said:
solved flashing via fastboot factory images with bacon root toolkit(i'm lazy :silly of 33r to see if it would update it and it did
i flashed 38r ota and 44s one as well
anyway i'm considering flashing cm11 stable builds...is there the option for slowmotion and othe things like gesture on off screen?
Click to expand...
Click to collapse
CM11 doesn't come with the CameraNext camera so you need to install the apk manually, but once you do that you will have full functionality. It has all gestures.
A word of advice: don't be lazy, stay away from toolkits. Firstly, they're unreliable and I've seen them cause many issues for people. Secondly, the experience you gain from using fastboot and adb manually is priceless.
Transmitted via Bacon

I think cm11s 44s is ahead of cm snapshots in terms if fixes and stuff so I would stick with that then go to a custom kernel for further updates past 44s kernel
And I totally agree with timmaaa I learned about flashing etc on this phone from his threads and posts lol trust me a one click app won't help when things hit the fan... But do as you want, I wanted to learn the proper way
Sent From Bacon

ek69 said:
I think cm11s 44s is ahead of cm snapshots in terms if fixes and stuff so I would stick with that then go to a custom kernel for further updates past 44s kernel
And I totally agree with timmaaa I learned about flashing etc on this phone from his threads and posts lol trust me a one click app won't help when things hit the fan... But do as you want, I wanted to learn the proper way
Sent From Bacon
Click to expand...
Click to collapse
i know how to use fastboot(i'm not a genius but i know how to use it basically)
the fact is that i didnt know how to flash factory images so i used it. and i also learned how to do it couse i read the log of toolkit...
FASTBOOT FLASH (modem/system/recovery/logo/etc...) modem/system/recovery/logo/etc.img

timmaaa said:
CM11 doesn't come with the CameraNext camera so you need to install the apk manually, but once you do that you will have full functionality. It has all gestures.
A word of advice: don't be lazy, stay away from toolkits. Firstly, they're unreliable and I've seen them cause many issues for people. Secondly, the experience you gain from using fastboot and adb manually is priceless.
Transmitted via Bacon
Click to expand...
Click to collapse
so gesture of music(2 fingers to play/pause, right/left arrow to change song), circle for camera and doubletap2wake are present also in cm11 non-S stable?
are they better then cm11s in terms of stability and smoothness?
could you also suggest me a good kernel?

babbo96 said:
so gesture of music(2 fingers to play/pause, right/left arrow to change song), circle for camera and doubletap2wake are present also in cm11 non-S stable?
are they better then cm11s in terms of stability and smoothness?
could you also suggest me a good kernel?
Click to expand...
Click to collapse
Yes, all of the gestures are present. It's essentially the exact same ROM but without the fancy lockscreen and camera. The main difference being that it receives merged fixes and commits sooner than CM11S. The best kernel? Stock.
Transmitted via Bacon

[Resolved] Power button Not working + oneplus logo at boot turned red !

Hi Friends
The power button on my device does not unlock my phone (it is working well otherwise) also If I try to unlock using double tap to wake up, it does not happen. Here is what I did before this problem started:
I had stock CM11s (bootloader unlocked + rooted+TWRP), I backed up the ROM using TWRP. Then, I wanted to try out a few ROMs and hence I flashed MIUI Patchrom, then after using it for a few hours I flashed ColorOS by relic242, I used it for a day and then I flashed LiquidSmooth Lollipop current build. Then in the end I restored my CM11s using the TWRP restore. My oneplus logo is now red, please help me undo this. Also, I am having the unlocking problem which I described above + the oneplus logo at boot of my device is now red in color. please help.
Update: If I turn "prevent accidental wake up" off, the power button and double tap works, but if I turn it on these doesn't. Still buggy ! During calls the screen is always off, seems like there is a problem with the proximity sensor, which was not there earlier. Maybe after flashing any of those ROMs?
Thanks !

You're gonna need to flash the fastboot images to go back to being fully stock, go to my guide thread and look at section 8 for instructions.
Transmitted via Bacon

timmaaa said:
You're gonna need to flash the fastboot images to go back to being fully stock, go to my guide thread and look at section 8 for instructions.
Transmitted via Bacon
Click to expand...
Click to collapse
Can I flash the modem only ?

xyz_1232005 said:
Can I flash the modem only ?
Click to expand...
Click to collapse
when he clearly declares "fully stock" then you will need to flash ALL images ...
or what do you mean when he sais fully stock?

xyz_1232005 said:
Can I flash the modem only ?
Click to expand...
Click to collapse
No. What on earth.would flashing the modem accomplish anyway? It wouldn't accomplish anything, it's entirely unrelated to your problem. You need a clean slate, flash the fastboot images.
Transmitted via Bacon

timmaaa said:
No. What on earth.would flashing the modem accomplish anyway? It wouldn't accomplish anything, it's entirely unrelated to your problem. You need a clean slate, flash the fastboot images.
Transmitted via Bacon
Click to expand...
Click to collapse
It's not neccesary true. On CM11 we need cm11 compatible modem, on cm12 - cm12 compatible modem. Wrong modem causes problem with screen off/on, he can try to flash compatible modem only and see if it helps

Flashing Modem Works !
I flashed the CM11s Modem and it worked ! Thanks guys !

Flashing the modem worked for me also! I was facing the exact same problem due to trying new CM 12 nightlies.

gyroscope/ autorotation not working after 5.1 roms flashed.

No matter what cm 12.1/5.1 roms I flashed, the gyroscope sensor isn't working. If I flashed back to cm 12.0 roms or lower, it works again. What could be the issue?

sseng587 said:
No matter what cm 12.1/5.1 roms I flashed, the gyroscope sensor isn't working. If I flashed back to cm 12.0 roms or lower, it works again. What could be the issue?
Click to expand...
Click to collapse
Revert to some other cm12.1 build nightly instead or flash latest nightly build
May be it's a problem associated with that build

I tried other 12.1 rom, same results. Cm 12.0 is fine though.

Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip

I have this issue too ... Brand new OnePlus One, put TWRP on it, flashed the latest CyanogenMod 12.1 nightly. Looks like rotation is not working and when I look at apps that show pitch and roll values they are seemingly not getting output from the sensors.
I see that you fixed yours ... But what is this problem from? Did the 12.1 ROM come bundled with bad firmware or something?
When I flash a ROM, maybe I'm ignorant, but I presume that the right and proper firmware and radios are bundled in.
Any advise OP?
Cheers!
cg6ry79m

[email protected] said:
I have this issue too ... Brand new OnePlus One, put TWRP on it, flashed the latest CyanogenMod 12.1 nightly. Looks like rotation is not working and when I look at apps that show pitch and roll values they are seemingly not getting output from the sensors.
I see that you fixed yours ... But what is this problem from? Did the 12.1 ROM come bundled with bad firmware or something?
When I flash a ROM, maybe I'm ignorant, but I presume that the right and proper firmware and radios are bundled in.
Any advise OP?
Cheers!
cg6ry79m
Click to expand...
Click to collapse
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1

Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m

[email protected] said:
Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m
Click to expand...
Click to collapse
Same problem here, I think the problem is located in the firmware. So it is something that CM will have to modify. Because the latest firmware (like the one in the zip) is also included in the latest nightly builds.
If rotation is something you need badly you can try the following 2 options:
- use an app to do the rotation like: playstore:rotation manager
- flash the stock CM11 and the accompaning firmware back, reflash the firmware in attachement and then reflash the CM12.1 nightly. (untested)

[email protected] said:
Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m
Click to expand...
Click to collapse
Little update ... Rotation seemed to work for a minute but has since stopped. Frustrating.

Same issue here, all sensors are shown to be off by Sensor Kinetics from Play Store.
Flashing everything from the factory restore image via fastboot did not help...

I have been troubleshooting the issue of rotation/orientation sensors seemingly not working. What I have found on my new OnePlus One, running the latest CyanogenMod 12.1 nightly builds is this:
Once I root the device using SuperSu I cannot regain use of the sensors/auto-rotate. I use the app named Phone Tester and after the phone is rooted the comps/orientation sensors show no output.
If I unroot the phone and reboot several times, the orientation subsystem functionality returns.
No matter what firmware/Cyanogen ROM combination I use the result is the same.
I wonder if anyone else can confirm that their screen rotation ceases to function when the phone is rooted.
Cg6ry79m

davebugyi said:
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1
Click to expand...
Click to collapse
Nooby question ... Doesn't the Cyanogen Nightly that I flash contain the device's firmware also? So if I flash the firmware file above separately, will it not be replaced by the next nightly that I flash? Should I tell TWRP to flash both items every time?
Before, I flashed that firmware that is mentioned above. ... But I feel like maybe it was superseded when I flashed a nightly.
Educate me.
cg6ry79m

[email protected] said:
Nooby question ... Doesn't the Cyanogen Nightly that I flash contain the device's firmware also? So if I flash the firmware file above separately, will it not be replaced by the next nightly that I flash? Should I tell TWRP to flash both items every time?
Before, I flashed that firmware that is mentioned above. ... But I feel like maybe it was superseded when I flashed a nightly.
Educate me.
cg6ry79m
Click to expand...
Click to collapse
Yes, the nightly contains and will overwrite your firmware. When going from CM to a different ROM, you don't have to flash the firmware again. As long as the android version is the same ofcourse.
Abiut your problem, do you use Superuser or SuperSU? Make sure you flash the latest SuperSU zip. More people had problems with the built in one from TWRP
Sent from my A0001 using XDA Free mobile app

cantthinkofagoodname said:
Yes, the nightly contains and will overwrite your firmware. When going from CM to a different ROM, you don't have to flash the firmware again. As long as the android version is the same ofcourse.
Abiut your problem, do you use Superuser or SuperSU? Make sure you flash the latest SuperSU zip. More people had problems with the built in one from TWRP
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I had used the latest SuperSU. The problem persists even when I don't use SuperSU though. I feel like it is some sort of race condition as processes kick off during boot or something.
I wish I wasn't relying on voodoo to get the accelerometer/auto-rotate to work.
cg6ry79m

sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
Yes! Thank you this worked. Was getting really annoyed by this issue, thought I was gonna be stuck on 5.02 forever. Tried flashing different nightlies, different modems...
Flashed everything from the 20150505 Firmware, the first 8 steps in the guide quoted above. For some reason flashing each file manually works as opposed to flashing the zip with all of them- odd, but hey whatever works...

Great thanks that worked!!
Sent from my A0001 using Tapatalk

I wanted to close out this issue as I believe it has been resolved. This problem was also a case of TWRP not correctly flashing the firmware. I "downgraded" from the X.X.0.7 TWRP to that X.X.0.6 version that others have posted links to in other threads. Frankly the GUI on this version is better.
So I downgraded TWRP, reflashed the 9 July Cyanogen nightly build. Accelerometer, compass, and proximity sensor working fine. Survived reboots. Survived new nightly.
Thanks to you folks who posted the issue about TWRP not flashing firmware correctly.
cg6ry79m

sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
i have issue with gyroscope like this video:
https://www.youtube.com/watch?v=cXsB2LG1ftM
Thanks for this method but not working for me!
could you give me more detail working firmware
i try 8 step in fastboot mode with 20150515 and 20150518 firmware but the issue still here!

Which version of twrp do you use? And did you flash the latest su?
Sent from my A0001 using Tapatalk

davebugyi said:
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1
Click to expand...
Click to collapse
sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
Thaks guys it worked for me
Cheers!

TWRP downgrade works but strangely.

Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?

Unnecessary screenshot attached :good: enjoy~

Tiash420 said:
Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?
Click to expand...
Click to collapse
Did you try flashing the recovery img via TWRP itself? And are you using any theme on TWRP 3.x.x.x?

Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.

Tiash420 said:
Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.
Click to expand...
Click to collapse
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk

Renosh said:
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I get the notification quick settings bug, I mean, I can't get quick setting toggles directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that? Meanwhile my friend on the other hand downloaded the same version from the same place and he doesn't face those bugs. :'| Why is this happening to me?

Tiash420 said:
I get the notification quick settings bug, I mean, I can't get quick settings directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that?
Click to expand...
Click to collapse
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk

Renosh said:
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|

Tiash420 said:
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|
Click to expand...
Click to collapse
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk

Renosh said:
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well doesn't matter, I flashed Sultan's unofficial CM13 build via Kumajaya's TWRP 3.0.0.0 and it works fabulously! jgcaap can wait, I'm sure it's not much different in features and stuff! :3