Related
Wanting to try a different kernel but wanting to go back to stock if it doesn't go well (stock kernel). I know how to flash a kernel but not sure how to get back to stock kernel.
Just flash the stock kernel like anything else.
iElvis said:
Just flash the stock kernel like anything else.
Click to expand...
Click to collapse
Not sure exactly where to find that though. I believe also there is a difference between cm10 and sense kernel though, correct?
Also curious if since I've flashed a jb sense rom if my kernel also updated to jb kernel
scabbard1 said:
Not sure exactly where to find that though. I believe also there is a difference between cm10 and sense kernel though, correct?
Also curious if since I've flashed a jb sense rom if my kernel also updated to jb kernel
Click to expand...
Click to collapse
You need a sense kernel for sense roms, and cm/aosp/aokp kernels for those roms.
Stock no-wp sense kernel here: http://forum.xda-developers.com/showthread.php?t=2150219
Check About>Software information>More and it will tell you what kernel you're on.
If you flash a ROM, it will flash a kernel with the ROM. You can find that kernel in the ROM zip file (boot.IMG). Extract that file and flash it using fastboot to return to the kernel that was packaged with your ROM.
Sent from my One X using Tapatalk 2
jeffwyeh said:
If you flash a ROM, it will flash a kernel with the ROM. You can find that kernel in the ROM zip file (boot.IMG). Extract that file and flash it using fastboot to return to the kernel that was packaged with your ROM.
Click to expand...
Click to collapse
If hboot is <1.14 (or you are S-off), the kernel will just flash as the ROM. You can just dirty flash the ROM again.
If hboot is 1.14 or greater (and S-on), just extract boot.img and flash in fastboot as mentioned above. Kernel is part of boot.img.
Thanks so much for this info. I was going to post the same question
Question: Is the boot.img the kernel file? Thanks
petey006 said:
Thanks so much for this info.
Click to expand...
Click to collapse
There's a button for that.
petey006 said:
Question: Is the boot.img the kernel file? Thanks
Click to expand...
Click to collapse
Yes. But you can't flash just a boot.img in recovery. You would need fastboot for that. If you want the commands they're in the general stickies or I can post them here.
Sent from Xparent Red using my Venomized Evita
ImagioX1 said:
Yes. But you can't flash just a boot.img in recovery. You would need fastboot for that.
Click to expand...
Click to collapse
Depends on the hboot version and S-On or Off. But I already discussed those above.
---------- Post added at 11:30 AM ---------- Previous post was at 11:26 AM ----------
petey006 said:
Question: Is the boot.img the kernel file?
Click to expand...
Click to collapse
As I already said, the kernel is a part of boot.img.
There are other things in boot.img besides just the kernel:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images#Structure_of_boot_and_recovery_images
Although the terms boot.img and kernel are used nearly synonymously here. When "kernels" are posted, I think its always the entire boot.img package.
And in regards to your original question, it doesn't really matter.
To return to the stock kernel, just flash the stock boot.img.
redpoint73 said:
Depends on the hboot version and S-On or Off.
Click to expand...
Click to collapse
So you can flash a straight boot.img not in a zip or anything through recovery with s-off?
Sent from Xparent Red using my Venomized Evita
ImagioX1 said:
So you can flash a straight boot.img not in a zip or anything through recovery with s-off?
Click to expand...
Click to collapse
Wait, no. I was misunderstanding you. The kernel has to be a flashable zip to be able to install from recovery. Otherwise, I think you are right, if you just have the boot.img, you need to install with fastboot.
I've noticed that some kernel only works with sense roms (ElementalX).
Say for example, i want to flash another rom without sense ui.
Do i need to reflash stock kernel first? Or flash the boot.img (kernel?) inside the new rom zip file?
Also the stock kernel from the link has two files. One is "installer" and the other is boot.img. I need to install the installer file thur Recovery, correct? And also flash the boot.img to go back to stock?
Thanks i'm such a n00b.
petey006 said:
I've noticed that some kernel only works with sense roms (ElementalX).
Say for example, i want to flash another rom without sense ui.
Do i need to reflash stock kernel first? Or flash the boot.img (kernel?) inside the new rom zip file?
Click to expand...
Click to collapse
Sense requires a Sense kernel.
AOSP based ROMs require an AOSP kernel.
In general, you should install the kernel for the ROM that you are flashing. Some kernels may work over more than one ROM (do the research before you try it), but never a Sense kernel for an AOSP ROM, or vice versa.
petey006 said:
I've noticed that some kernel only works with sense roms (ElementalX).
Also the stock kernel from the link has two files. One is "installer" and the other is boot.img. I need to install the installer file thur Recovery, correct? And also flash the boot.img to go back to stock?
Click to expand...
Click to collapse
One or the other, you don't need both. If you are hboot 1.14 or higher, I don't know if the installer way will work. The boot.img way (in fastboot) will work, no matter what hboot you are on.
redpoint73 said:
Wait, no. I was misunderstanding you. The kernel has to be a flashable zip to be able to install from recovery. Otherwise, I think you are right, if you just have the boot.img, you need to install with fastboot.
Click to expand...
Click to collapse
I was about to say!! Thanks for clarifying.
Sent from Xparent Red using my Venomized Evita
Ok so i flashed francos kernel trough FKU updater app and i want to go back to stock just to compare the battery life and some stuff again and to decide what to use.
How can i flash stock kernel back, do i flash all factory images or is there .zip file to flash trough recovery, or there is another way to do this? thanks for your replays.
Hi,
Stock kernel here (recovery zip file): http://forum.xda-developers.com/showthread.php?p=47269605.
You can also take a look here to fastboot the boot.img (kernel): http://forum.xda-developers.com/showthread.php?t=2513701.
Alexandar92zr said:
Ok so i flashed francos kernel trough FKU updater app and i want to go back to stock just to compare the battery life and some stuff again and to decide what to use.
How can i flash stock kernel back, do i flash all factory images or is there .zip file to flash trough recovery, or there is another way to do this? thanks for your replays.
Click to expand...
Click to collapse
boot.img is the kernel. If you have the factory images you can just fastboot flash that,
Hammer_Of_The_Gods said:
Hi,
Stock kernel here (recovery zip file): http://forum.xda-developers.com/showthread.php?p=47269605.
You can also take a look here to fastboot the boot.img (kernel): http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
ok so i just download the zip and flash trough twrp right?
rootSU said:
boot.img is the kernel. If you have the factory images you can just fastboot flash that,
Click to expand...
Click to collapse
oh ok did not know that im quite new to this, but now i know thanks for information.
Alexandar92zr said:
ok so i just download the zip and flash trough twrp right?
Click to expand...
Click to collapse
That's right, download the right zip (4.4 or 4.4.1/4.4.2) put it "in your sdcard", reboot in recovery, flash and reboot, that's all
Hammer_Of_The_Gods said:
That's right, download the right zip (4.4 or 4.4.1/4.4.2) put it "in your sdcard", reboot in recovery, flash and reboot, that's all
Click to expand...
Click to collapse
thanks man i clicked on that thanks button
Alexandar92zr said:
thanks man i clicked on that thanks button
Click to expand...
Click to collapse
No worries, thanks
Last thing since you came from Franco kernel (the following procedure is specific):
The Gingerbread Man said:
Return to stock romz
Franco's kernel changes these system files below, so to change them back you can remove the .bak extension, or fastboot system.IMG and boot.IMG from a Google factory image which is probably easier and faster.
1 - Rename /system/lib/hw/power.msm8974.so.bak to /system/lib/hw/power.msm8974.so
2 - Rename /system/bin/thermal-engine-hh-bak to /system/bin/thermal-engine-hh
3 - Reboot to the boot loader and flash stock Kernel by downloading the Nexus images and then fastboot flash boot boot.img
...
Click to expand...
Click to collapse
So before flashing the stock kernel in recovery do the step 1 and 2 (even after if you forgot, it should be good).
Alexandar92zr said:
thanks man i clicked on that thanks button
Click to expand...
Click to collapse
May i suggest you start reading up before you get into serious rouble. Read the first 4 threads in the General section.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Hammer_Of_The_Gods said:
No worries, thanks
Last thing since you came from Franco kernel (the following procedure is specific):
So before flashing the stock kernel in recovery do the step 1 and 2 (even after if you forgot, it should be good).
Click to expand...
Click to collapse
ok lets see if i understood right.
im comeing from the stock rom just with francos kernel and now to go back to the stock i need to do step 1 and 2, how do i rename that files i connect my phone to pc or i need to download some file menager that can see that files? and about step 3 do i need to flash boot.img via fast boot or i can do it trough twrp as well?
sorry about the many questions but i do not want do do something wrong
Alexandar92zr said:
ok lets see if i understood right.
im comeing from the stock rom just with francos kernel and now to go back to the stock i need to do step 1 and 2, how do i rename that files i connect my phone to pc or i need to download some file menager that can see that files? and about step 3 do i need to flash boot.img via fast boot or i can do it trough twrp as well?
sorry about the many questions but i do not wont do do something wrong
Click to expand...
Click to collapse
With a file explorer, directly from your phone, (Root Explorer, Es File Explorer, etc...) follow the path to the files in point 1 and 2, rename the files and save. Then reboot in recovery and flash the stock kernel if you want to flash it via recovery (equal to step 3).
If you are not used with this kind of stuff (modify system files by yourself), flash the system.img and boot.img by following the link I provided above (http://forum.xda-developers.com/showthread.php?t=2513701).
Hammer_Of_The_Gods said:
With a file explorer, directly from your phone, (Root Explorer, Es File Explorer, etc...) follow the path to the files in point 1 and 2, rename the files and save. Then reboot in recovery and flash the stock kernel if you want to flash it via recovery (equal to step 3).
If you are not used with this kind of stuff (modify system files by yourself), flash the system.img and boot.img by following the link I provided above (http://forum.xda-developers.com/showthread.php?t=2513701).
Click to expand...
Click to collapse
i founded the files that i need to rename via es file explorer and now i understand it all and im not confused anymore about how to get stock kernel back.
im not used to this stuff yet because i rooted my phone yesterday and im quite new to this because last device i rooted and flashed lots of custom roms and stuff is to HD2 so i know the basic stuff but not much
and one of the topic question. why does my colors look a little diferent when i flashed the francos kernel? i know that there is something about color profiles etc. but i do not know where to start and look into that
Alexandar92zr said:
i founded the files that i need to rename via es file explorer and now i understand it all and im not confused anymore about how to get stock kernel back.
im not used to this stuff yet because i rooted my phone yesterday and im quite new to this because last device i rooted and flashed lots of custom roms and stuff is to HD2 so i know the basic stuff but not much
and one of the topic question. why does my colors look a little diferent when i flashed the francos kernel? i know that there is something about color profiles etc. but i do not know where to start and look into that
Click to expand...
Click to collapse
Okay, so all is fine to go back to stock, take your time and read all closely
About the colors, take a look here: http://forum.xda-developers.com/showpost.php?p=49561443 (links for profiles are down, for example: http://192.227.135.147/N5_ColorProfiles/Latest_Profiles/ from vomer).
Hammer_Of_The_Gods said:
Okay, so all is fine to go back to stock, take your time and read all closely
About the colors, take a look here: http://forum.xda-developers.com/showpost.php?p=49561443 (links for profiles are down, for example: http://192.227.135.147/N5_ColorProfiles/Latest_Profiles/ from vomer).
Click to expand...
Click to collapse
thanks i will look into this.
I made a stock kernel backup on Franco app and used it to restore back to stock kernel after using Franco was this process ok
Sent from my Nexus 5 using xda app-developers app
I am running stock rom with franco.kernel and would like to try out elementalx. What is the process to do this? Do i just have to download and flash this kernel in the recovery or is there something else that I need to do like flashing stock kernel first?
vlawrence0324 said:
I am running stock rom with franco.kernel and would like to try out elementalx. What is the process to do this? Do i just have to download and flash this kernel in the recovery or is there something else that I need to do like flashing stock kernel first?
Click to expand...
Click to collapse
Wouldn't the ElementalX thread be the beast place to ask this?
vlawrence0324 said:
I am running stock rom with franco.kernel and would like to try out elementalx. What is the process to do this? Do i just have to download and flash this kernel in the recovery or is there something else that I need to do like flashing stock kernel first?
Click to expand...
Click to collapse
This should be in Q/A FYI
You can find answers in the said thread, but basically dirty flash your current ROM and flash elemental over it
Sent from my Nexus 5 using xda app-developers app
vlawrence0324 said:
I am running stock rom with franco.kernel and would like to try out elementalx. What is the procan ess to do this? Do i just have to download and flash this kernel in the recovery or is there something else that I need to do like flashing stock kernel first?
Click to expand...
Click to collapse
Just flash the stock kernel (boot.img) in fastboot and after that Elemental in recovery.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Hi,
Only the boot.img is enough?
Because: http://forum.xda-developers.com/showpost.php?p=47583830&postcount=2.
Franco's kernel changes these system files below, so to change them back you can remove the .bak extension, or fastboot system.IMG and boot.IMG from a Google factory image which is probably easier and faster.
1 - Rename /system/lib/hw/power.msm8974.so.bak to /system/lib/hw/power.msm8974.so
2 - Rename /system/bin/thermal-engine-hh-bak to /system/bin/thermal-engine-hh
Click to expand...
Click to collapse
Flashing only the boot.img replace the system files above?
And from ElementalX kernel thread:
INSTALLATION
1. If you've been using another custom kernel, reflash your ROM without wiping data
Click to expand...
Click to collapse
So running the stock rom, I would reflash the boot.img and the system.img, or only rename the files mentioned above if your are confident with that (at least for me it's easier and faster)...
Hammer_Of_The_Gods said:
Hi,
Only the boot.img is enough?
Because: http://forum.xda-developers.com/showpost.php?p=47583830&postcount=2.
Flashing only the boot.img replace the system files above?
And from ElementalX kernel:
So running the stock rom, I would reflash the system.img, or only rename the files mentioned above if your are convenient to that...
Click to expand...
Click to collapse
Did it this way always and i never had an issue. OP can also dirty flash system.img and boot.img in fastboot.
Oeps already suggested.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
I have LG Nexus 5 Phone rooted recently. With Custom Recovery I have installed some Zips (Called Mods). One of the Zips is Corrupt and my phone is not responding at all. I want to remove the Custom Zip/Mod only as I don't wan to wipe off whole system.
Is there any way to remove that particular Mod using TWRP Manager or any other way without loosing my data/stuff on my phone.
Restore the backup you made before flashing it
Sent from my Nexus 5 using XDA Premium 4 mobile app
pepdavies said:
Restore the backup you made before flashing it
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am not able to find any backup. I think I have not created it. Does this application creates backup automatically?
If in worst to worst case there is no backup, what are all other options I do have here.
Hi,
pepdavies said:
Restore the backup you made before flashing it
Click to expand...
Click to collapse
This, yes... but I doubt he made a backup if he ask how to "remove" the mods...
@anshumangoyal, maybe the there is an "undo" zip file, a revert to stock zip file? What mod have you flashed?
Dirty flash your rom, no wipe, and you won't lose anything...
And no automatic backup, you need to do it yourself in recovery, first thing to do when you flash some stuff.
pepdavies said:
Restore the backup you made before flashing it
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hammer_Of_The_Gods said:
Hi,
This, yes... but I doubt he made a backup if he ask how to "remove" the mods...
@anshumangoyal, maybe the there is an "undo" zip file, a revert to stock zip file? What mod have you flashed?
Dirty flash your rom, no wipe, and you won't lose anything...
And not, no automatic backup, you need to do it yourself in recovery, first thing to do when you flash some stuff.
Click to expand...
Click to collapse
But, how to do this dirty flash. I cannot see any such option in TWRP. Do i need to install some another tool etc??
anshumangoyal said:
But, how to do this dirty flash. I cannot see any such option in TWRP. Do i need to install some another tool etc??
Click to expand...
Click to collapse
Boot in recovery, go to your rom zip file, flash and reboot...
Without more relevant info I can only say that...
Stock rom? Custom rom? Link to the mod you flashed?
Hammer_Of_The_Gods said:
Boot in recovery, go to your rom zip file, flash and reboot...
Without more relevant info I can only say that...
Stock rom? Custom rom? Link to the mod you flashed?
Click to expand...
Click to collapse
It's Stock ROM I have Rooted to, I am not using ay custom ROM. So whare to download this Stock ROM. And also once this Stock ROM is flashed do I need to root the phone again.
I may be asking very silly questions, but this is what I was able to know in last 1-2 months and "still Learning"
Ok, it seems you don't want to post a link to the mod you flashed, or at least say the name, I asked 2 times and maybe we could do a revert zip file for you if we know what you have flashed (it depends of what kind of mod) then...
Take a look here to return to stock: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Or flash a stock rom via recovery? Maybe easier for you...
EDIT: stock roms, flashable zip file: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4 (two first links), see above to flash...
Hammer_Of_The_Gods said:
Ok, it seems you don't want to post a link to the mod you flashed, or at least say the name, I asked 2 times and maybe we could do a revert zip file for you if we know what you have flashed (it depends of what kind of mod) then...
Take a look here to return to stock: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Or flash a stock rom via recovery? Maybe easier for you...
EDIT: stock roms, flashable zip file: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4.
Click to expand...
Click to collapse
Oops I am sorry, I was not aware of terminology here. If I see in System Setting I have Build Number: KOT49H and Kernel Version: 3.4.0-gadb2201
Is this information you are looking for. I had unrooted latest android software, which I rooted using wugFresh tool kit software on windows 8.
Model: Nexus 5, LGD820, D821
Android 4.4.2 KOT49H
I hope this will help out.
Nope, it's not what I asked but...
I gave you a link to some full stock roms (rooted) to flash in recovery: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4 (use the first one for example).
Put it on your phone via computer, reboot in recovery go to the zip file you've just put, flash the zip file and reboot, the modified files from the mods you flashed will be replaced by the original stock files.
Use this link to "learn" how to use some commands (manually) and return to stock when you encounter a plroblem: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Here you need to flash the system.img (I guess, since I don't know what you flashed), or "all"...
Maybe harder for you since you used a Toolkit the first time but with time and reading...
If it seems even too hard for you, then in your Toolkit is there an option to return to stock, reflash the system.img?
When I ask you what mod you flashed, I mean it's a theme? A kernel? A sound mod? A camera mod? Because if we know what you flashed, maybe we can do a revert zip file for you by replacing the files by the stock ones in the zip).
What is the exact name of the zip file, the last you flashed and gives you problem?
Read all closely and take your time...
Hammer_Of_The_Gods said:
Nope, it's not what I asked but...
I gave you a link to some full stock roms (rooted) to flash in recovery: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4 (use the first one for example).
Put it on your phone via computer, reboot in recovery go to the zip file you've just put, flash the zip file and reboot, the modified files from the mods you flashed will be replaced by the original stock files.
Use this link to "learn" how to use some commands (manually) and return to stock when you encounter a plroblem: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Here you need to flash the system.img (I guess, since I don't know what you flashed), or "all"...
Maybe harder for you since you used a Toolkit the first time but with time and reading...
If it seems even too hard for you, then in your Toolkit is there an option to return to stock, reflash the system.img?
When I ask you what mod you flashed, I mean it's a theme? A kernel? A sound mod? A camera mod? Because if we know what you flashed, maybe we can do a revert zip file for you by replacing the files by the stock ones.
What is the exact name of the zip file, the last you flashed and gives you problem?
Read all closely and take your time...
Click to expand...
Click to collapse
Thanks,
Now I understood. These were two Zips I installed were: cargo_N5_RebootMenu_KOT49H_odex.zip and cargo_only_Batt___rechts_odex_N5.zip
These were 2 mods I had.
anshumangoyal said:
Thanks,
Now I understood. These were two Zips I installed were: cargo_N5_RebootMenu_KOT49H_odex.zip and cargo_only_Batt___rechts_odex_N5.zip
These were 2 mods I had.
Click to expand...
Click to collapse
Ok, good.
The first: http://forum.xda-developers.com/google-nexus-5/themes-apps/mod-advanced-4-reboot-menu-odex-t2521809, you have a revert zip file (just below the mod you flashed): Back to stock: cargo_N5_Back_to_stock_RebootMenu_KOT49H_odex.zip.
The second: http://forum.xda-developers.com/goo...ps/mod-center-clock-battery-mod-odex-t2526039, same thing you have a revert zip file in attachment: Back_to_Stock_odex_N5.zip.
Download them and flash them to restore the original files, you really need to read closely before flashing stuff
Hammer_Of_The_Gods said:
Ok, good.
The first: http://forum.xda-developers.com/google-nexus-5/themes-apps/mod-advanced-4-reboot-menu-odex-t2521809, you have a revert zip file (just below the mod you flashed): Back to stock: cargo_N5_Back_to_stock_RebootMenu_KOT49H_odex.zip.
The second: http://forum.xda-developers.com/goo...ps/mod-center-clock-battery-mod-odex-t2526039, same thing you have a revert zip file in attachment: Back_to_Stock_odex_N5.zip.
Download them and flash them to restore the original files, you really need to read closely before flashing stuff
Click to expand...
Click to collapse
This is Super Find. I am sorry, I was not aware of this. Next time I will check this for sure and make sure I also take a backup before doing these nasty things. Many thanks again for your help.
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!