CM10 Stable Version OTA - AT&T, Rogers HTC One X, Telstra One XL

Just got an OTA from CM that says a stable build (CM10.0.0) is ready to be installed. My phone is currently running the 1109 nightly.
Has anyone gotten this and successfully installed? I'm about to try it, but wonder if we still need to flash the boot.img first, or if the actual OTA takes care of that. Would be completely awesome if it does.

If you have the old hboot then you can just ota. If you have the new one, fastboot flash boot.img
Sent from my HOX running Cyanogenmod 10

I'm currently running the CM10 nightly from 10/11 and tried the OTA upgrade to the stable version. Well, once I flashed the new version my wifi wouldn't turn on.
It's the same problem I've had previously. My wifi works fine on the 10/11 nightly, but anything after that and my wifi just won't turn on. It shows that it's off in my settings and when I try to turn it on it just hangs and never turns on.
No one else seems to be having this problem so I'm not sure what's going on. I would love to upgrade to the stable build but I need wifi to work. I ended up having to reflash the older ROM and Gapps, so my wifi is working fine now.
Anyone else have problems turning wifi on with the new version??

Thanks. Installed with TWRP and everything is working great.
Just didn't realize that CM even pushed OTAs. A coworker also got an OTA on his GS3 today and installed that way with no problem. They don't have the extra boot.img step to deal with.
danny39 said:
If you have the old hboot then you can just ota. If you have the new one, fastboot flash boot.img
Sent from my HOX running Cyanogenmod 10
Click to expand...
Click to collapse

danny39 said:
If you have the old hboot then you can just ota. If you have the new one, fastboot flash boot.img
Sent from my HOX running Cyanogenmod 10
Click to expand...
Click to collapse
Does this mean I need to wipe like I did the first time I installed CM10 or is there a way to do this as an update without losing apps and settings?
Also, is there a way to do this directly on the phone or does it need to be done over USB like I did with the initial ROM install? Sorry, this is my first update since rooting recently. I'd like to make sure I do this correctly.

ctennenh said:
Does this mean I need to wipe like I did the first time I installed CM10 or is there a way to do this as an update without losing apps and settings?
Also, is there a way to do this directly on the phone or does it need to be done over USB like I did with the initial ROM install? Sorry, this is my first update since rooting recently. I'd like to make sure I do this correctly.
Click to expand...
Click to collapse
You shouldn't lose apps or settings, but never hurts to do a backup anyway.
If you rooted from the 2.20 firmware: download the rom from CM and extract the boot.img file on the computer. Then put the two on the phone's sd card. From there, you do the same thing you did the first time. Flash the boot.img and then the rom and GApps. Everything should work fine.
If you came from 1.85, apparently you can install directly from the OTA on the phone.

Thanks for the help. Do I need to do fastboot on boot img from the computer as well, or is there a way to manage it on the phone?
I wish I could just do OTA updates like people on the older hboot.

ctennenh said:
Thanks for the help. Do I need to do fastboot on boot img from the computer as well, or is there a way to manage it on the phone?
I wish I could just do OTA updates like people on the older hboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1982442

ctennenh said:
Thanks for the help. Do I need to do fastboot on boot img from the computer as well, or is there a way to manage it on the phone?
I wish I could just do OTA updates like people on the older hboot.
Click to expand...
Click to collapse
I use FlashImageGUI to flash the boot.img on the phone. Only thing I do on the computer is extract the actual boot.img file from the ROM.

joe23521 said:
I use FlashImageGUI to flash the boot.img on the phone. Only thing I do on the computer is extract the actual boot.img file from the ROM.
Click to expand...
Click to collapse
Ok, just so I have it straight and because Flash Image GUI is warning me over and over: after I extract the correct boot.img I flash it using the Flash Image GUI, then use TWRP to install the boot.img, then the rom zip, then my gapps.zip? Thanks.

I was able to install it without flashing the boot.img. I was coming from the the latest nightly.
Sent from my One X using xda app-developers app

ctennenh said:
Ok, just so I have it straight and because Flash Image GUI is warning me over and over: after I extract the correct boot.img I flash it using the Flash Image GUI, then use TWRP to install the boot.img, then the rom zip, then my gapps.zip? Thanks.
Click to expand...
Click to collapse
Flash the boot.img with Flash Image GUI, ignore all the warnings. Then, it'll ask you if you want to boot into recovery. Say yes. Then in TWRP, just flash the rom and gapps zips. Don't touch the boot.img again.

h1m said:
I was able to install it without flashing the boot.img. I was coming from the the latest nightly.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Interesting. Did you root from the 2.20 firmware?

No Stable for me
The CM10 Stable release for HTC One X is not on get.cm and it does not come up on my ota check on the CM10 nightly (i have the latest nightly)
Any ideas

Hello everyone,
This is the issue i had, when going from 1109 to stable the system will not do a clean OTA, the system will not load, attempted cleaning everything but nothing worked, at one point i even corrupted my memory so i had to do a factory reset, lastly what i did was flash the boot.img again and reinstall the system this got everything back to work. so from experience it seems the stable will need to do a full reinstall.
I hope that will help other people.
EDIT: updated to 1114 but it seems that broke the search feature so going back to 10.0.0 :S

ozozdil said:
The CM10 Stable release for HTC One X is not on get.cm and it does not come up on my ota check on the CM10 nightly (i have the latest nightly)
Any ideas
Click to expand...
Click to collapse
Definitely there. http://get.cm/get/4LO

Excellent. Thanks so much. I managed to get it done. Here are my steps, FYI:
Coming from the 2.20 root with the latest hboot.
I downloaded but did not install the 10.0 stable update.
I went through my file browser to sdcard/cmupdater and copied the 10.0 evita zip to my Downloads folder.
After extracting the zip I copied the boot.img to the root directory of my sdcard. I don't think it has to be there, though.
I ran Flash Image GUI on the boot.img file, even with all the warning.
I then chose to reboot into recovery, where I installed the 10.0 evita zip, then installed the gapps zip.
Everything seems to work, including WiFi. I really appreciate all the help here at XDA. Hopefully my process above will help someone else.

deleted

That link is for the One XL Evita lte dual core version, I'm talking about the One X international hspa quad core version.
Thaks for thehelp anyway
Sent from my HTC One X using xda premium

Hey Guys
I'm struggling to locate an OTA for my HOX, is it only the XL that was updated with a stable release? as im unable to locate an endeavoru stable release for CM10?
I've taken a look through get.cm but cannot locate a copy anywhere? did we miss out? ?

Related

[Q] how to flash - really in trouble

Hi all,
Apology if this questions may already been ask millions of time but I am really stucked at the moment and hoping that someone may guide me to the correct direction.
I have got HTC One X-LTE (Evita)
I managed to get S-OFF and also CID - 111111
It has TWRP 2.6
The last time I got it working was on the STOCK 4.2.2 I downloaded from the XDA - then I got into the issues of rebooting and loosing signal from time to time. so I went into my TWRP backup I had and reflashed it using my old backup made from my TWRP.
the reflashed failed and now I can only boot up to the HTC logo and then black screen.
I can get to the TWRP recovery and I have got fastboot and ADB on my PC.
When I run the fastboot devices command --> it shows device connected BUT when i try ADB command ---> no device is found.
It will be much appreciated if someone can guide me to the right direction as I am really stucked at the moment not sure where to start.
I tried searching in the forum but I don't think I went to the correct area/tutorial.
Please help
Thank you
When you made your twrp backup did you select system,data, and boot? If it's hanging at the HTC screen it seems there is not boot.img installed or one that is incompatible with your backup. Open whatever Rom your backup is made from and copy the boot.img to your fastboot directory. Then reboot the phone into fastboot mode and flash the boot.img using this command.
Fastboot flash boot boot.img
Then reboot the phone and see what happens
Sent from my HTC One XL using Xparent Red Tapatalk 2
ImagioX1 said:
When you made your twrp backup did you select system,data, and boot? If it's hanging at the HTC screen it seems there is not boot.img installed or one that is incompatible with your backup. Open whatever Rom your backup is made from and copy the boot.img to your fastboot directory. Then reboot the phone into fastboot mode and flash the boot.img using this command.
Fastboot flash boot boot.img
Then reboot the phone and see what happens
Sent from my HTC One XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply.
When looking at the TWRP backup I copied into my PC - does not have the .img - the one I can find is MD5
Can I use the existing ROM I donwload from XDA like : EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip
when I extracted EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip - I can see the "boot.img" can I use this one?
Thanks
ardabelati said:
Thanks for the reply.
When looking at the TWRP backup I copied into my PC - does not have the .img - the one I can find is MD5
Can I use the existing ROM I donwload from XDA like : EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip
when I extracted EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip - I can see the "boot.img" can I use this one?
Thanks
Click to expand...
Click to collapse
I had a somewhat similar experience with Viper 4.0 ROM - I managed to get Cyanogenmod installed correctly (particularly this one). Take a shot and see if it works - atleast your phone will be up and working.
sandys1 said:
I had a somewhat similar experience with Viper 4.0 ROM - I managed to get Cyanogenmod installed correctly (particularly this one). Take a shot and see if it works - atleast your phone will be up and working.
Click to expand...
Click to collapse
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
ardabelati said:
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
Click to expand...
Click to collapse
hmm - Im on ROM dated 09/13, which is not present now. Your best bet would be http://get.cm/get/aOM
Also remember to flash Google Apps (play store, etc.) which is packaged separately here - http://goo.im/gapps/gapps-jb-20130813-signed.zip
ardabelati said:
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
Click to expand...
Click to collapse
Did it work finally ?
sandys1 said:
Did it work finally ?
Click to expand...
Click to collapse
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
ardabelati said:
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
Click to expand...
Click to collapse
It sounds like it might be a bad download or something. I noticed u never mentioned wiping the phone before flashing, Are u clean wiping? And also what hboot are you on?
Sent from my HTC One X using xda app-developers app
ardabelati said:
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
Click to expand...
Click to collapse
You can either flash the kernel, which can be found in the Android Development section, flashing the kernel is just like flashing a ROM, just install in Beastmode. Or you can upgrade your firmware to 2.15, the instructions are I'm the first post of the ROM thread.
Asking which ROM is best/favorite/most stable is against the rules so we can't answer that question.
When you say the phone keeps rebooting, does it ever make it into the OS or is it boot looping (showing the boot animation then starting over)?
Sent from my Evita
timmaaa said:
You can either flash the kernel, which can be found in the Android Development section, flashing the kernel is just like flashing a ROM, just install in Beastmode. Or you can upgrade your firmware to 2.15, the instructions are I'm the first post of the ROM thread.
Asking which ROM is best/favorite/most stable is against the rules so we can't answer that question.
When you say the phone keeps rebooting, does it ever make it into the OS or is it boot looping (showing the boot animation then starting over)?
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply
When you said that flashing kernel is the same as flashing ROM, I did it By going to TWRP and the press install and locate the zip file. Is this what should be done?
What is beast mode?
Sorry for the basic questions
Thanks
Yeah that's how you install the kernel. It must be done after you install the ROM. I kinda worded my reply a bit weird, sorry about that. Beastmode is the name of the kernel, you can find it here:
http://forum.xda-developers.com/showthread.php?t=2165880
Sent from my Evita
I did try to flash it through recovery but it always failed. Not sure why. I copied the kernel zip file into my phone sd and then I went to recovery and press the install and located the kernel zip file but still failed.
Sent from my HTC One XL using Tapatalk 2
Which recovery version are you using?
Sent from my Evita
Recovery is 2.6.3.
The process failed on not able to fine the MD5 file or something like that. We don't need to extract the Zip file do we?
Cheers
Disable md5 checking in settings. You never need to extract a kernel or ROM zip.
Sent from my Evita
timmaaa said:
Disable md5 checking in settings. You never need to extract a kernel or ROM zip.
Sent from my Evita
Click to expand...
Click to collapse
I have checked the setting in TWRP and nothing is ticked.
When I flash the zip, it is still saying "failed due to md5 does not exists".
I am not sure which should be address first but I now noticed that there is an error : "unable to locate storage device"
also came out.
When I plug my phone to PC I can see the storage but why it is saying "storage device not found" in TWRP?
Thanks

Heartbleed vulnerability in Android 4.1.1

Google has officially stated that Android 4.1.1 is vulnerable:
http://googleonlinesecurity.blogspot.ca/2014/04/google-services-updated-to-address.html
This is a notice for anyone else on the Stock ROM as I am pretty sure this was the last supported update from HTC.
Pretty sure my wife's HTC One S (Ville) is on this version. Will verify when I get home. Time to root and flash her phone this weekend
Aceangel21 said:
Google has officially stated that Android 4.1.1 is vulnerable:
http://googleonlinesecurity.blogspot.ca/2014/04/google-services-updated-to-address.html
This is a notice for anyone else on the Stock ROM as I am pretty sure this was the last supported update from HTC.
Pretty sure my wife's HTC One S (Ville) is on this version. Will verify when I get home. Time to root and flash her phone this weekend
Click to expand...
Click to collapse
Anyway to patch this flaw myself using root access? I really don't have time to install and configure a new ROM...
I guess there is no official word from HTC neither...?
vacsed said:
Anyway to patch this flaw myself using root access? I really don't have time to install and configure a new ROM...
Click to expand...
Click to collapse
You could try this hack:
http://forum.xda-developers.com/showthread.php?p=51830870
rudolfm said:
You could try this hack:
http://forum.xda-developers.com/showthread.php?p=51830870
Click to expand...
Click to collapse
Could anyone with more programming skills than me try one of the following:
1) wrap this in a zip file we can flash from recovery
2) incorporate it into the Xposed framework
Many thanks if someone can accomplish this!
I think it's just HTC wanting us to buy new devices that's all.
Sent from my HTC One S using xda app-developers app
larrycl said:
Could anyone with more programming skills than me try one of the following:
1) wrap this in a zip file we can flash from recovery
2) incorporate it into the Xposed framework
Many thanks if someone can accomplish this!
Click to expand...
Click to collapse
Maybe you can try my patch: https://www.dropbox.com/s/tqxfjwwja3uaqsn/install-patch.zip
It uses a libssl.so from a LG Optimus L5 II (4.1.2) and it works on my TrekStor Surftab Ventos 10.1
If your device does't boot after you've installed it:
The patch creates a backup of your libssl.so at /system/libssl.backup.so, so just replace /system/lib/libssl.so with that backup file
Cheers, Xorg
Edit: updated link
HTC 800# When patch my One S 4.1.1: "I can't Comment"
Aceangel21 said:
Google has officially stated that Android 4.1.1 is vulnerable:
This is a notice for anyone else on the Stock ROM as I am pretty sure this was the last supported update from HTC.
Pretty sure my wife's HTC One S (Ville) is on this version. Will verify when I get home. Time to root and flash her phone this weekend
Click to expand...
Click to collapse
-- More or less revenue for HTC: Phonecon with HTC Toll Free#, US. Over 10 minutes tech reading to me how HTC is dedicated to security, ... customers .. asked when patch will issue for my 2012 HTC One S .. Answer: "I can't comment" .. Not planning on a 4th HTC in my life. /Ev :crying:
Link doesn't work
TheXorg said:
Maybe you can try my patch: http://tslink.tk/hb-inst-2
It uses a libssl.so from a LG Optimus L5 II (4.1.2) and it works on my TrekStor Surftab Ventos 10.1
If your device does't boot after you've installed it:
The patch creates a backup of your libssl.so at /system/libssl.backup.so, so just replace /system/lib/libssl.so with that backup file
Cheers, Xorg
Click to expand...
Click to collapse
Can you repost the link? I'd like to try it on my Archos 80 Titanium tablet. Stuck on 4.1.1 with no custom roms available for this tablet
htc is officially pushing heart bleed to t-mobile one s http://www.htc.com/us/go/htc-software-updates/
wendroid said:
Can you repost the link? I'd like to try it on my Archos 80 Titanium tablet. Stuck on 4.1.1 with no custom roms available for this tablet
Click to expand...
Click to collapse
New links:
New libssl.so: https://www.dropbox.com/s/wsg3a5ave2a8655/newssl.so
Flasheable ZIP: https://www.dropbox.com/s/tqxfjwwja3uaqsn/install-patch.zip
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thank you so much! I will try this soon
The OTA for T-Mobile is out.
http://support.t-mobile.com/docs/DOC-4262
dr3amsINdigital said:
The OTA for T-Mobile is out.
http://support.t-mobile.com/docs/DOC-4262
Click to expand...
Click to collapse
Do NOT update via the OTA update! It put me through a constant reboot cycle and I had to factory reset...
th3pr1nc30f3gypt said:
Do NOT update via the OTA update! It put me through a constant reboot cycle and I had to factory reset...
Click to expand...
Click to collapse
Did you have a custom recovery installed?
dr3amsINdigital said:
Did you have a custom recovery installed?
Click to expand...
Click to collapse
Yes now what?
knickerblogger said:
Yes now what?
Click to expand...
Click to collapse
I'm not sure how to fix it, but this is why you're not supposed to install OTAs if you're not on stock recovery.
Sent from my iPad using Tapatalk
I'm s off, have twrp installed and on stock ROM. Would like to install this update, or get a 4.2.2 or 4.3 stable fully functional ROM. Do you think flashing stock recovery and then ota would work even if I'm s off. Should still be able to boot an ruu from fastboot even if I boot loop. Suggestions on custom roms?
Edit: Used flashalot's recovery switcher to flash stock recovery, rebooted, then flashed the ota update. After update I lost root, but still have s off.
Plan on fastboot flashing another recovery, then flashing su binary again from the new recovery.
Hope this helps.
Sent from my HTC VLE_U using XDA Free mobile app
Anyone interested in that OTA zip ?
Sent from my HTC VLE_U using Tapatalk
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
This might help...
If you have the OTA.zip file... but custom recovery and such like TMUS application removed..
This will wipe your phone. Making a backup is not optional !!!
http://sadevil.org/blog/2012/12/23/manually-flashing-an-ota-update/
This looks somewhat straight forward.. If you want to get the OTA downloaded:
got to settings .. and manage to get the software update.. It will download eventually into your Download folder ..
Do not Apply the OTA at this point.. select install later!!!
pull the file on your PC/Mac/Linux box and modify as described in the URL above..
reboot your phone and the OTA should not bother you ... if you have pulled (like in remove) or at least renamed the OTA file..
Before you push Firmware.. and such make sure you have made a backup with CWM !!! or whatever method you are using!!!
also make sure you have your custom recovery image somewhere available and maybe a su.zip cwm file as you may loose root as well.. not sure..
If you have rooted your HTC one S your self - this should not be hard to DIY..
Currently I am at work and cannot try it out myself .. but definitly will do it once back at home later..
Godspeed to all of you brave hackers..
Superchill11 said:
I'm s off, have twrp installed and on stock ROM. Would like to install this update, or get a 4.2.2 or 4.3 stable fully functional ROM. Do you think flashing stock recovery and then ota would work even if I'm s off. Should still be able to boot an ruu from fastboot even if I boot loop. Suggestions on custom roms?
Edit: Used flashalot's recovery switcher to flash stock recovery, rebooted, then flashed the ota update. After update I lost root, but still have s off.
Plan on fastboot flashing another recovery, then flashing su binary again from the new recovery.
Hope this helps.
Sent from my HTC VLE_U using XDA Free mobile app
Click to expand...
Click to collapse
Same situation here. Stock ROM and Rooted and S-off. Constant nag to apply the OTA update but not working. Looking for a way to do it easy. How should I proceed? Don't want to wipe the phone and create all my settings again if possible. Can I reverse S-Off and apply OTA update somehow?
can any one provide me a link to the ota update

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!

[Q] Stuck at boot screen

Flashed the latest RUU from HERE, and it boots into the OS perfectly.
Then, flashed Stock GPE from HERE and also tried LolliGPE from HERE. Both will not get past the boot screen, after waiting over 30min's.
In attempts to fix, the latest full firmware, TWRP, full wipe/dirty wipe, and DH's 5.1 firmware have been flashed, then the custom ROM's flashed again followed. Same issue is persists. Each time, trying to flash the RUU back, boots without issue.
Prior to flashing the latest RUU (hboot method, 0P6BIMG.zip), I have ran all the ROM's mentioned and others without issue.
I'm at a loss of what to try next, or why it's hanging. Right now, i'm leaving it for hours at the boot screen, but I doubt this is going to cure anything and only provide a hot phone during the whole time.
The phone is unlocked, S-OFF, and SuperCID.
Any suggestions i'm willing to try.
Update:
Woke up 6+ hours later, and it was still stuck on the boot screen.
Flashed the latest Fluent ROM found HERE, and it boots fine. Then did a full wipe (Cache, Dalvik Cache, Data, System), then the standalone data wipe, and factory reset. Installed GPE from HERE, and it stuck on the boot screen again after waiting 20min's...
Next step i'm going to try is 4.4.4 RUU, then full latest OEM firmware. If GPE doesn't boot still, i'll try DH's 5.1 firmware.
Still has the same problem.
I have no idea what else to try. Wish I never flashed that damn RUU file!
kcasner said:
Still has the same problem.
I have no idea what else to try. Wish I never flashed that damn RUU file!
Click to expand...
Click to collapse
The stock secure boot.img is probably what's causing you issues.
Choose a Rom, take it's boot.img and fastboot flash it.
fastboot flash boot boot.img
Then flash the Rom.
Profit...!?
Sent from my HTC6525LVW using Tapatalk
santod040 said:
The stock secure boot.img is probably what's causing you issues.
Choose a Rom, take it's boot.img and fastboot flash it.
fastboot flash boot boot.img
Then flash the Rom.
Profit...!?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
That was exactly it, what a relief. Thank you!
kcasner said:
That was exactly it, what a relief. Thank you!
Click to expand...
Click to collapse
Run files are not to blame or the problem. In fact, if you simply flash a full ruu file your phone would boot up fine.
Sent from my Nexus 6 using Tapatalk
dottat said:
Run files are not to blame or the problem. In fact, if you simply flash a full ruu file your phone would boot up fine.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's what I said in the first post/sentence. The boot.img in the RUU was the root cause for other ROM's not booting. This was verified 3x with identical results.
santod040 was spot on :good:
kcasner said:
That's what I said in the first post/sentence. The boot.img in the RUU was the root cause for other ROM's not booting. This was verified 3x with identical results.
santod040 was spot on :good:
Click to expand...
Click to collapse
I don't think you follow me.
The ruu is the same as stock.
Do you recall having to manually flash an insecure boot img before you flashed your first custom rom?
It's no different.
Sent from my Nexus 6 using Tapatalk
dottat said:
I don't think you follow me.
The ruu is the same as stock.
Do you recall having to manually flash an insecure boot img before you flashed your first custom rom?
It's no different.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Honestly can't recall. I follow; we're on the same page, different lingo.
kcasner said:
Honestly can't recall. I follow; we're on the same page, different lingo.
Click to expand...
Click to collapse
kcasner, I had exactly same issue as you. Could you explain a bit detail on how you get it fixed?
I want to flash DH5.1. Are these correct steps I should following:
1) open DH5.1 zip file, find the boot.img (I found there're two boot.img, stock/boot.img and elite/boot.img, I guess I should use later one)
2) fastboot flash the boot.img
3) boot into recovery to flash DH5.1
4) reboot
Thanks for help!

Wilson3q CM12 to MIUI 7

Hello all,
I want to move from CM12 (Wilsons3q) to the latest MIUI 7 Global Stable. Im having a problem getting my phone recognized through the MiFlash program I originally used to get to CM12. I go into fastboot mode on the phone but the program does not recognize the phone. Ive tried this on 2 different computers. I installed the universal ADB drivers and still nothing. Does anyone know why the phone isnt recognized anymore?
I searched through the previous topics and found no answer to my question. Thanks guys
Solved.
Turns out all I had to do was flash the .zip from MIUI with TWRP recovery
It failed the first time so I did it a second time and it worked great.
Leaving this here for anyone else who may run into the same question/ problem
gotmicah said:
Solved.
Turns out all I had to do was flash the .zip from MIUI with TWRP recovery
It failed the first time so I did it a second time and it worked great.
Leaving this here for anyone else who may run into the same question/ problem
Click to expand...
Click to collapse
you flash the update zip through twrp recovery?
NO! Dont flash the update.zip
Download the global version from miui.
the name of what I flashed was "miui_MI4iGlobal_V7.1.1.0.LXIMICK_15c5da242c_5.0.zip"
gotmicah said:
NO! Dont flash the update.zip
Download the global version from miui.
the name of what I flashed was "miui_MI4iGlobal_V7.1.1.0.LXIMICK_15c5da242c_5.0.zip"
Click to expand...
Click to collapse
i download the miui latest version just rename it into update zip. because want to install in stock recovery. so, mean i can directly flash that zip?
fidows said:
i download the miui latest version just rename it into update zip. because want to install in stock recovery. so, mean i can directly flash that zip?
Click to expand...
Click to collapse
Oh I see. I didn't know you were using stock recovery. Im not sure completely, but im assuming that would be safe.
Edit: on second thought, maybe not. I dont have enough information about your situation, what ROM are you running now? im not sure how the stock recovery interacts with different ROMS
gotmicah said:
Oh I see. I didn't know you were using stock recovery. Im not sure completely, but im assuming that would be safe.
Edit: on second thought, maybe not. I dont have enough information about your situation, what ROM are you running now? im not sure how the stock recovery interacts with different ROMS
Click to expand...
Click to collapse
i mean this. im now in miui7. just to make sure if i flash cm13 then. can i flash the miui7 zip directly from twrp?

Categories

Resources