Related
new to android,
got a few questions regarding franco kernel
1. should i install franco kernel? iam seeing that pretty much everyone is using it.will just installing it improve battery life? or do i also need to mess with clocks( which i rather not do)
2. using mahdi rom, will it work with it?
http://forum.xda-developers.com/oneplus-one/orig-development/kernel-franco-kernel-r1-t2800871
3. also i would need to download from the link that says: "for aosp roms" right?
4. in the link above it just says flash it, but in this guide http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 , in part 6, it says also wipe cache/dalvik, so should i wipe or not?
thanks in advance to all helpers =P
DjDafiDak said:
new to android,
got a few questions regarding franco kernel
1. should i install franco kernel? iam seeing that pretty much everyone is using it.will just installing it improve battery life? or do i also need to mess with clocks( which i rather not do)
2. using mahdi rom, will it work with it?
http://forum.xda-developers.com/oneplus-one/orig-development/kernel-franco-kernel-r1-t2800871
3. also i would need to download from the link that says: "for aosp roms" right?
4. in the link above it just says flash it, but in this guide http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 , in part 6, it says also wipe cache/dalvik, so should i wipe or not?
thanks in advance to all helpers =P
Click to expand...
Click to collapse
1. Depending on your device, and your app set up, it will make your device run smoother. But then there's ak kernel too. ak has more options and you have to tweak your own set up. Franco has his set up built into the kernel already to make it run optimized.
2. Yes
3. Yes
4. Yes
dude i just installed it and the screen was freaking out, like alot of random colors on parts of the screen and weird lines and sh!t, wtf, what do i do?
Update your ROM.
DjDafiDak said:
dude i just installed it and the screen was freaking out, like alot of random colors on parts of the screen and weird lines and sh!t, wtf, what do i do?
Click to expand...
Click to collapse
You downloaded the outdated Mahdi, download the latest from here
http://forum.xda-developers.com/one...m-2-7-oneplus-camera-4k-t2813107/post55644987
nicholaschum said:
You downloaded the outdated Mahdi, download the latest from here
http://forum.xda-developers.com/one...m-2-7-oneplus-camera-4k-t2813107/post55644987
Click to expand...
Click to collapse
do i have to reflash it entirely? or can i somehow update? i just dont want to go through the hassle of installing apps etc again, because i just did that.
but if i have no choice i will.
if you could please continue to reply quickly that would be great, as i only have about 8hrs till college starts tomorrow and i need my phone, thanks =P
DjDafiDak said:
do i have to reflash it entirely? or can i somehow update? i just dont want to go through the hassle of installing apps etc again, because i just did that.
but if i have no choice i will.
Click to expand...
Click to collapse
Just flash over your current set up. You won't lose data.
nicholaschum said:
Just flash over your current set up. You won't lose data.
Click to expand...
Click to collapse
exactly as those steps mentioned on mahdi's page?
Upgrading from an earlier version: (not recommended)
- Copy the ROM ZIP to your SDCard
- Boot into Recovery
- Flash the ROM zip from SDCard
- Reboot
DjDafiDak said:
exactly as those steps mentioned on mahdi's page?
Upgrading from an earlier version: (not recommended)
- Copy the ROM ZIP to your SDCard
- Boot into Recovery
- Flash the ROM zip from SDCard
- Reboot
Click to expand...
Click to collapse
Yep.
nicholaschum said:
Yep.
Click to expand...
Click to collapse
Thanks alot!!! it fixed it.
just to confirm, i still have franco kernel installed after flashing the mahdi update?, the two things aren't related right?
though i dont feel like the device is smoother, but not sure yet.
DjDafiDak said:
Thanks alot!!! it fixed it.
just to confirm, i still have franco kernel installed after flashing the mahdi update?, the two things aren't related right?
Click to expand...
Click to collapse
You need to flash the latest franco again. Mahdi flashes it's stock kernel.
---------- Post added at 04:18 PM ---------- Previous post was at 04:01 PM ----------
DjDafiDak said:
though i dont feel like the device is smoother, but not sure yet.
Click to expand...
Click to collapse
Kernels need to set in on your device. Give it a few hours. Also sometimes smoothness doesn't have to be felt, but how a piece of software runs is how efficient it is.
nicholaschum said:
You need to flash the latest franco again. Mahdi flashes it's stock kernel.
Click to expand...
Click to collapse
hmm now iam thinking its fixed just because its back to its original kernel again, you sure that if i flash franco now it will be good?
lets say it wont, will i be able to just flash mahdi 2.8 again, and fix it again?
DjDafiDak said:
hmm now iam thinking its fixed just because its back to its original kernel again, you sure that if i flash franco now it will be good?
lets say it wont, will i be able to just flash mahdi 2.8 again, and fix it again?
Click to expand...
Click to collapse
It's because of the old commits in the previous Mahdi releases. The kernel has the latest commits and the ROM was not updated for it. The one you downloaded was 09/03 version but the commit was weeks after 3rd of Sept, requiring a ROM update.Now that you have the latest, you won't experience any of these issues again.
alright, reflashing franco r21( also wiping cache/dalvik hopefully i need to do it again)
will edit in a sec.
edit: its good now =]
thanks ALOT for all 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!
First of all sorry if there are some solution in other thread but i was searching a lot and found nothing. Also i cannot ask this on the twrp thread because of the xda system that don't allow me to write there or on some other development thread because my account have few than 10 messages (very frustrating this).
I tried to install the twrp 2.8.6.0 and it's impossible to have it working, when i install it always i have a bootloop that don't allow the phone to enter to the recovery.
I tried all the ways to install it (app flashify, app twrp manager, app kernel adiutor, cmd, toolkit, through twrp 2.8.7.0, 2.8.4.0, 2.8.7 multirom) and still without luck. It's very strange because is THAT specific version (2.8.6.0) that don't work, when i flash other version like 2.8.7 works perfectly.
Anyone knows what's the problem?
mustang_ssc said:
First of all sorry if there are some solution in other thread but i was searching a lot and found nothing. Also i cannot ask this on the twrp thread because of the xda system that don't allow me to write there or on some other development thread because my account have few than 10 messages (very frustrating this).
I tried to install the twrp 2.8.6.0 and it's impossible to have it working, when i install it always i have a bootloop that don't allow the phone to enter to the recovery.
I tried all the ways to install it (app flashify, app twrp manager, app kernel adiutor, cmd, toolkit, through twrp 2.8.7.0, 2.8.4.0, 2.8.7 multirom) and still without luck. It's very strange because is THAT specific version (2.8.6.0) that don't work, when i flash other version like 2.8.7 works perfectly.
Anyone knows what's the problem?
Click to expand...
Click to collapse
Install either TWRP 2.8.6.0.6 materialised (personally tested works perfect) or the latest 2.8.7.0.5 materialised other users say it works with flashing firmware and works with encrypted systems
https://www.androidfilehost.com/?w=files&flid=30332
Sent from my A0001 using Tapatalk
Renosh said:
Install either TWRP 2.8.6.0.6 materialised (personally tested works perfect) or the latest 2.8.7.0.5 materialised other users say it works with flashing firmware and works with encrypted systems
https://www.androidfilehost.com/?w=files&flid=30332
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
And do you know if works well with the new Sultan CM13 versions? That's the problem i have, the other TWRP versions cannot flash correctly that rom and also i heard that the TWRP 2.8.6.0.6 don't flash the rom correctly, maybe I'm wrong.
Me and many people have this strange problem that don't allow us to flash the 2.8.6.0. Hope someone can help us.
Thanks anyway.
mustang_ssc said:
And do you know if works well with the new Sultan CM13 versions? That's the problem i have, the other TWRP versions cannot flash correctly that rom and also i heard that the TWRP 2.8.6.0.6 don't flash the rom correctly, maybe I'm wrong.
Me and many people have this strange problem that don't allow us to flash the 2.8.6.0. Hope someone can help us.
Thanks anyway.
Click to expand...
Click to collapse
The problem isn't flashing the ROM correctly its that you don't have the correct firmware so it gives an error and refuses to flash the latest Sultan builds. TWRP 2.8.6.0.6 or 2.8.7.0.5 both in that directory I posted earlier can flash the correct firmware. You'll need to download the latest CM13 flash that wipe again and then flash Sultan to have the latest baseband version
Renosh said:
The problem isn't flashing the ROM correctly its that you don't have the correct firmware so it gives an error and refuses to flash the latest Sultan builds. TWRP 2.8.6.0.6 or 2.8.7.0.5 both in that directory I posted earlier can flash the correct firmware. You'll need to download the latest CM13 flash that wipe again and then flash Sultan to have the latest baseband version
Click to expand...
Click to collapse
I did that you told me and now i have the Sultan cm13 working perfectly.
I didn't know that, thanks.
lets make this very clear:
I HAVE NOT DEVELOPED THIS, IT WAS LINKED IN ANOTHER FORUM BY ANOTHER MEMBER WHO ALSO DID NOT DEVELOP IT
this is actually developed by a member over at the Chinese website '7to' http://www.7to.cn, so its a recovery based on TWRP 3.2.1 but seems to have its own UI and feature set.
WORKING
Code:
[COLOR="Black"][LIST]
[*]Boots to TWRP!
[*]Can flash images to system (MUST BE ON SD CARD!!!!)
[*]ADB
[*]Mount system R/W
[/LIST][/COLOR]
NOT WORKING
Code:
[COLOR="Black"][LIST]
[*]Decryption
[*]Data backup
[*]Flash from internal storage (since it cant be decrypted)
[/LIST][/COLOR]
I am not responsible if you brick your device, flash with caution and ONLY on an 8.1 GSI where your current TWRP doesn't work.
This does not do anything to capacitive keys, if they work before flashing they will work after flashing
INSTALLATION
'fastboot flash recovery_ramdisk recovery.img
DOWNLOAD
https://drive.google.com/file/d/1RgerdkXY-B-8XV5buloeCyKYrA2B3Bvf/view?usp=sharing
Credit to whoever the creator of this is!
it boots up with TWRP, but flashing Gapps was failure.
UPDATE: I used Open Gapps, better try Ground Zero GZR Gapps...
TASON42 said:
it boots up with TWRP, but flashing Gapps was failure.
Click to expand...
Click to collapse
GZR apps 180313 works good.
GZR-GaPPs-arm64REv4-Zero-8.1-20180628 worked. thx.
UPDATE: HuRUpdater_0.4, Magisk 16.7 worked.
Flashed a kernel, magisk and xposed with this. Seems to be working great.
olishadyx said:
Flashed a kernel, magisk and xposed with this. Seems to be working great.
Click to expand...
Click to collapse
I haven't flashed anything with this yet, but at least it can do the basic stuff. Also, what kernel did you flash, I know there's the proto8 kernel (or whatever it's called) but I'm not too keen on it.
ambitiousButRubbish said:
I haven't flashed anything with this yet, but at least it can do the basic stuff. Also, what kernel did you flash, I know there's the proto8 kernel (or whatever it's called) but I'm not too keen on it.
Click to expand...
Click to collapse
Proto8 is what I installed. Haven't made my mind up on it yet. Battery drain is definitely worse so far but apparently it takes a few cycles to adapt.
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
ALWAYS BACKUP YOU’RE DATA BEFORE FLASHING.
This tutorial assumes you understand how to use adb and fastboot.
Your device’s bootloader has to be unlocked.
IMPORTANT NOTE: It seems some users need to flash a vbmeta image file provided by Google in order to boot and user the Custom Kernel. If you find yourself in a situation were you are not able to boot, please flash the attached vbmeta img along with the Kernel and if still bootlooping share the last_kmsg to determine what's driving the issue.
Download >> Link
Kernel Sources >>> Source
Join the Telegram Group for additional support - Link
Thanks to @afaneh92
11/08/2022 - Update
Upstream to 5.10.83
Based on S908EXXU2BVJA, SM-S908E_13_Opensource
You can now download file from Kernel Source page.
Only Test on SM-S908E for now but should work on all snap dragon android 13 should also should work on android 12 but not tested.
For permissive kernel you can go to the download page.
----------------------------------------------------------
Android 12 only..
07/25/2022 - Update
Upstream to 5.10.84
Added support for all S22 snapdragon devices.
Only tested on SM-S901/906/908 E (b0q, r0q, g0q)
07/11/2022 - Initial Set up
Upstream to 5.10.83
TTL Support
Low Memory Killer for Android
Wakelock Blocker enabled
Enabled more TCPs
Only tested on SM-S908E should work on SM-S9080 as well.
..
Awesome! I look forward to this project. Hopefully I can test it soon.
Any details I can share to confirm if the SM-S908N would work before flashing?
nonomancer said:
Awesome! I look forward to this project. Hopefully I can test it soon.
Any details I can share to confirm if the SM-S908N would work before flashing?
Click to expand...
Click to collapse
I only tired it on SM-S908E you can try it if it doesn't work just flash your boot.img
I look forward to see where this will progress. Oh, I miss the days of custom kernels and custom ROMS so much! I don't think I've ever enjoyed any phone more than I enjoyed the days of the Note 2, then life got busier. Nexus 5 was great too with custom ROMS, and the Pixel 2. These days it seems all the security measures by manufacturers (and it's understandable), is preventing a lot of crazy independent development.
Any
bklyn_syed said:
07/11/2022 - Initial Set up
Upstream to 5.10.83
TTL Support
Low Memory Killer for Android
Wakelock Blocker enabled
Enabled more TCPs
Only tested on SM-S908E should work on SM-S9080 as well.
Click to expand...
Click to collapse
Chance you can do a kernel for S901E?
skinza said:
Any
Chance you can do a kernel for S901E?
Click to expand...
Click to collapse
Try it, it should work since its gki kernel
bklyn_syed said:
Try it, it should work since its gki kernel
Click to expand...
Click to collapse
Do you think it'd be possible to flash the zip with the Franco kernel manager app?
skinza said:
Do you think it'd be possible to flash the zip with the Franco kernel manager app?
Click to expand...
Click to collapse
Thats what I use make sure you flash vbmeta disabler before flashing custom kernel
bklyn_syed said:
Thats what I use make sure you flash vbmeta disabler before flashing custom kernel
Click to expand...
Click to collapse
Awesome, one last thing, the vbmeta disabler, flash with Odin in user data same as when flashing it for twrp? Or fastboot?
skinza said:
Awesome, one last thing, the vbmeta disabler, flash with Odin in user data same as when flashing it for twrp? Or fastboot?
Click to expand...
Click to collapse
AP in odin
Doesn't work, says unsupported device, aborting
skinza said:
Doesn't work, says unsupported device, aborting
Click to expand...
Click to collapse
Ok ill fix the script and upload the file for test
Try this
skinza said:
Doesn't work, says unsupported device, aborting
Click to expand...
Click to collapse
Try the zip I uploaded
Thank you for your kernel mate, im Not rooted yet but will try in a few weeks when im on holydays
Goku1992 said:
Thank you for your kernel mate, im Not rooted yet but will try in a few weeks when im on holydays
Click to expand...
Click to collapse
Ok
bklyn_syed said:
Try this
Click to expand...
Click to collapse
Yep worked didn't need vbmeta disabler, just flashed the zip
skinza said:
Yep worked didn't need vbmeta disabler, just flashed the zip
Click to expand...
Click to collapse
Can you screenshot software information I want to make sure it works