Hi all
I'm new in this and I'll like to know if it is possible to overclock the Sony Xperia M (C1904).
Do I need a custom kernel to overclock my device?
If someone has made it please let me know, or if there is a thread about it, guide, etc.
I just want info about overclocking this device.
Thanks
thexperiafan said:
Hi all
I'm new in this and I'll like to know if it is possible to overclock the Sony Xperia M (C1904).
Do I need a custom kernel to overclock my device?
If someone has made it please let me know, or if there is a thread about it, guide, etc.
I just want info about overclocking this device.
Thanks
Click to expand...
Click to collapse
In order to overclock your device you need a custom kernel which allows overclocking and therefore an unlocked bootloader.
For now there is only one custom kernel "Elixer" for our device, working properly with the 4.1.2 firmware version.
After you flash this kernel you can set the maximum CPU frequency to 1,566 GHz with various programs from the play store (e.g. No-frills CPU Control).
Thanks and...
Ydraulikos said:
In order to overclock your device you need a custom kernel which allows overclocking and therefore an unlocked bootloader.
For now there is only one custom kernel "Elixer" for our device, working properly with the 4.1.2 firmware version.
After you flash this kernel you can set the maximum CPU frequency to 1,566 GHz with various programs from the play store (e.g. No-frills CPU Control).
Click to expand...
Click to collapse
Thanks bro!
So, if i install the Elixer kernel on my device I will be able to overclock it: ok.
I just have problems understanding how to install a Custom kernel. and there is no tutorial on the elixer thread.
Thanks again!.
thexperiafan said:
Thanks bro!
So, if i install the Elixer kernel on my device I will be able to overclock it: ok.
I just have problems understanding how to install a Custom kernel. and there is no tutorial on the elixer thread.
Thanks again!.
Click to expand...
Click to collapse
Follow this tutorial here to unlock your bootloader.
Then download and install the latest version of FlashTool from http://www.flashtool.net/
Run flashtool,connect your usb cable while holding volume up button until the led turns into blue.
Click the thunderbolt icon->fastboot mode->select a kernel to flash (elixer2.0.img) and wait for it to finish.
Boot your device and if you see the elixer logo instead of the sony one everything went good.
Got it.
Ydraulikos said:
Follow this tutorial here to unlock your bootloader.
Then download and install the latest version of FlashTool from http://www.flashtool.net/
Run flashtool,connect your usb cable while holding volume up button until the led turns into blue.
Click the thunderbolt icon->fastboot mode->select a kernel to flash (elixer2.0.img) and wait for it to finish.
Boot your device and if you see the elixer logo instead of the sony one everything went good.
Click to expand...
Click to collapse
Hey, thank you for the fast response.
Ok so if I have rooted my device and unlocked the bootloader I just have to follow step by step the guide of flashtool and it's all done?
No need to do more? don't need to install CWM? or do another thing?
Dude, you have helped me a lot thanks for that.
Related
SEtweak kernel for Xperia S.
Intro:
I know I failed last time (with Play - it was stolen) and left development. But let's be serious this time.
Since it'll take a bit to set up everything again, I've taken DooM's ramdisk (hope you don't mind) for the first test.
Note: I don't have the device so I can't test it. If you want to, you can donate via Donate button on the left.
Sony finally published everything we need to build kernel.
Due to some possible bootloader problems, kernel might not work.
Features:
Codepage 852 (purely selfish reasons )
NLS UTF-8 (Native Language Support)
NTFS support
TUN/CIFS support
Default governor set to 'ondemand'
Prerooted
init.d support
Coming soon:
More governors
Recovery
Download: be patient
Best regards,
Blagus
Cool.
Ive unlocked my bootloader already so ill test it for you.
Im not rooted yet tho. I did have the rooted rom installed form another thread but i was having issues with app crashes so i flashed the stock .67
Hi there,
I hope the kernel wil be pre rooted and have some nice features....
I will try it
I need someone to send me kernel.sin of 6.0.A.3.62 firmware.
Hi there,
You can download it here : https://github.com/DooMLoRD/Xperia-2012-Official-Kernel-Sources and if its not there you can find it here http://eddy.uni-duisburg.de/bin4ry/L...1257-3921).ftf
Blagus said:
I need someone to send me kernel.sin of 6.0.A.3.62 firmware.
Click to expand...
Click to collapse
Im uploading it now for you
Edit:
Done
https://rapidshare.com/files/1187401250/kernel.sin
Don't bother Blagus. At this point, you can't really use a custom boot image due to a bootloader bug.
deovferreira said:
Don't bother Blagus. At this point, you can't really use a custom boot image due to a bootloader bug.
Click to expand...
Click to collapse
Really? Any more info on that?
It seems to affect some units at this point, I know of others which can boot just fine though using the instructions provided by Sony. This is the one thing preventing CM9 porting at this point.
deovferreira said:
It seems to affect some units at this point, I know of others which can boot just fine though using the instructions provided by Sony. This is the one thing preventing CM9 porting at this point.
Click to expand...
Click to collapse
hi defer,
what is the bug exactly?
i faced some issues yesterday when testing out kernels on a users device...
whenever we tried hotbooting the kernel (fastboot boot kernel.elf) the bootloader always returned "Wrong range" even though i used exactly the same ranges as given by Sony....
the test kernels are posted here:
http://forum.xda-developers.com/showthread.php?p=23868276#post23868276
if anyone wants to try them
I don't know the specifics of the bug, but it's in the bootloader it might be anything really, no way to know. However, what happens is that the bootloader is able to boot signed kernel.sin files but not the unsigned kernel.elf
Hii Everyone as we all know our phone is in a big problem which causes our phone to lag like **** after every few hours
Well i have a simple solution for that
This tutorial is divided into two parts
1)For users using my Ultimate Rom V2
2)For general users (Even though i recommend using My Rom For Best Performance)
1)For Ultimate rom Users
i)Go To system>etc And Delete init.d folder and delete all the folders in etc which were created in 1969
ii)*Xposed framework is the main reason for your lag and i learnt it the hard way so if you have installed the framework and any of its modules
Then uninstall the modules and uninstall the framework FROM INSIDE THE Xposed APP
iii)Copy and replace my build.prop in system folder from the second post(Dual Sim Only)
add ro.debuggable=0 at the end of the build.prop for all versions
iv)*Only for Dual Sim Version( Download The TWRP Recovery/Kernel from this link from the second post
v)After flashing go into recovery and flash the Fly on Mod Tweaks zips provided in the second post
vi)download no frills cpu from playstore and set performance/ondemand and noop (Dont worry if the phone restarts without warning just check if the governer and I/O Were set)
vii)If you did everything write you will have a lag free fast phone now
2)For General Users
i)Go To system>etc And Delete init.d folder if it exists and delete all previous tweaks that you may have enabled
ii)*Xposed framework is the main reason for your lag and i learnt it the hard way so if you have installed the framework and any of its modules
Then uninstall the modules and uninstall the framework FROM INSIDE THE Xposed APP
iii)Copy and replace my build.prop in system folder from the second post(Dual Sim Only)
add ro.debuggable=0 at the end of the build.prop for all versions
iv)*Only for Dual Sim Version( Download The TWRP Recovery/Kernel from second post
v)After flashing go into recovery and flash the Fly on Mod Tweaks zips provided in the second post
vi)download no frills cpu from playstore and set performance/ondemand and noop (Dont worry if the phone restarts without warning just check if the governer and I/O Were set)
vii)If you did everything write you will have a lag free fast phone now
Files to download
1)Fly On Mod By slaid480 (Go To his thread and press the thanks button,excellent work by him)
Mod filesFlash in recovery)
http://www.mediafire.com/download/zv825xeuyb8cwot/Signed_Fly-On_Mod%E2%84%A2_V4.0-Beta9.zip
http://forum.xda-developers.com/attachment.php?attachmentid=2187824&d=1376469987
2)TWRP Recovery By abcdjdj *ONLY FOR DUAL SIM VARIANTS(Press the thanks button on his thread and learn how to use the recovery)
http://forum.xda-developers.com/showthread.php?t=2764408
3)My build.prop (Only For Dual Sim Phones if you want for single sim Provide me the build.prop)
Please rename it from build.prop.txt to build.prop before replacing
add ro.debuggable=0 at the end of the build.prop for all versions of t2 ultra
Please post your Reviews and questions so i can further work making this phone work better:victory:
I can't find the init.d folder in system>etc (stock rom)...
Just did all other steps but now the rom is not booting anymore
elcattaro said:
I can't find the init.d folder in system>etc (stock rom)...
Just did all other steps but now the rom is not booting anymore
Click to expand...
Click to collapse
which model lte or dual
please dont tel me that u didnt read the instructions properly
Ashwin Prabhunerurkar said:
Please post your Reviews and questions so i can further work making this phone work better:victory:
Click to expand...
Click to collapse
Xposed doesn't cause any problems. This ram problem would occur even without Xposed. I have been using my phone since 72 hrs with Xposed and a lot of heavy multi tasking and gaming.
Adding ro.debuggable=0 to the build.prop is of no use as the value needs to be changed in the default.prop (you need to unpack the ramdisk). It will continue to remain 1 even after adding it to the build.prop. Try running the "getprop" command in the terminal emulator app after adding the line in the build.prop. You'll still get the output as [ro.debuggable] : [1].
The Performace governor locks the CPU freq to the max. It would certainly smoothen out the UI but it would cause a lot of battery drain. And when your phone restarts automatically after setting the cpu governor, it means that a kernel panic has occured. You can check /proc/last_kmsg for the error log. After your phone restarts, it will revert back to the default governor.
abcdjdj said:
Xposed doesn't cause any problems. This ram problem would occur even without Xposed. I have been using my phone since 72 hrs with Xposed and a lot of heavy multi tasking and gaming.
Adding ro.debuggable=0 to the build.prop is of no use as the value needs to be changed in the default.prop (you need to unpack the ramdisk). It will continue to remain 1 even after adding it to the build.prop. Try running the "getprop" command in the terminal emulator app after adding the line in the build.prop. You'll still get the output as [ro.debuggable] : [1].
The Performace governor locks the CPU freq to the max. It would certainly smoothen out the UI but it would cause a lot of battery drain. And when your phone restarts automatically after setting the cpu governor, it means that a kernel panic has occured. You can check /proc/last_kmsg for the error log. After your phone restarts, it will revert back to the default governor.
Click to expand...
Click to collapse
Yes I agree.
Tried many times your fix instructions on my d5322 (ex xm50h) dual sim but no results... Waiting for @abcdjdj release with fixed ramdisk :good:
Why is Sony T2 stuff being posted in the Z2 forum?
The T2 and Z2 are very different devices. Different CPU, different GPU, different RAM capacity, different screen size etc etc.
If any Z2 users flashed T2 ROM's or followed advice that was meant for a T2 they would likely brick their phone.
It seems VERY bad that T2 devices specific things are being posted randomly to the Z2 forum?!
abcdjdj said:
Xposed doesn't cause any problems. This ram problem would occur even without Xposed. I have been using my phone since 72 hrs with Xposed and a lot of heavy multi tasking and gaming.
Adding ro.debuggable=0 to the build.prop is of no use as the value needs to be changed in the default.prop (you need to unpack the ramdisk). It will continue to remain 1 even after adding it to the build.prop. Try running the "getprop" command in the terminal emulator app after adding the line in the build.prop. You'll still get the output as [ro.debuggable] : [1].
The Performace governor locks the CPU freq to the max. It would certainly smoothen out the UI but it would cause a lot of battery drain. And when your phone restarts automatically after setting the cpu governor, it means that a kernel panic has occured. You can check /proc/last_kmsg for the error log. After your phone restarts, it will revert back to the default governor.
Click to expand...
Click to collapse
some modules of xposed specific to xperia cause heavy lags, and yes i am already using the default.prop
by my method i can go upto 24 hrs without restarting but flashed your kernel now so waiting for the 72 hr magic as mentioned by you
fix for volume by arjun
http://forum.xda-developers.com/showpost.php?p=53543982&postcount=167
It Works nicely try it
Ashwin Prabhunerurkar said:
fix for volume by arjun
http://forum.xda-developers.com/showpost.php?p=53543982&postcount=167
It Works nicely try it
Click to expand...
Click to collapse
Hi.
Iam a proud user of a T2 Ultra, but i have one problem, i cant unlock the bootloader but if i can root the device without unlocking it it will be great.
Can U Plz Help me? Is it possible?
fastkiller said:
Hi.
Iam a proud user of a T2 Ultra, but i have one problem, i cant unlock the bootloader but if i can root the device without unlocking it it will be great.
Can U Plz Help me? Is it possible?
Click to expand...
Click to collapse
sorry but currently if you want root you will have to unlock bootlader
just unlock the bootlader you wont be missing out on anything
Ashwin Prabhunerurkar said:
sorry but currently if you want root you will have to unlock bootlader
just unlock the bootlader you wont be missing out on anything
Click to expand...
Click to collapse
Well i would like to unlock the bootloader, but when i go to the service menu i got Unlock Bootlock=No, can i unlock it using another method?
fastkiller said:
Well i would like to unlock the bootloader, but when i go to the service menu i got Unlock Bootlock=No, can i unlock it using another method?
Click to expand...
Click to collapse
you probably got your phone with a contract so you have an unlockable bootloader as far as i know there is no way to unlock the bootloader if it is locked with a telco you may try asking your telco where you bought it if they can help
Ashwin Prabhunerurkar said:
sorry but currently if you want root you will have to unlock bootlader
just unlock the bootlader you wont be missing out on anything
Click to expand...
Click to collapse
No more unlocking the bootloader required for T2 Ultra Dual
fastkiller said:
Hi.
Iam a proud user of a T2 Ultra, but i have one problem, i cant unlock the bootloader but if i can root the device without unlocking it it will be great.
Can U Plz Help me? Is it possible?
Click to expand...
Click to collapse
try this thread: http://forum.xda-developers.com/t2-u...-dual-t2806708
Q&A for [ROM][GSM+CDMA][Play+Neo L]Slimbean 5.1.1[MULTIBOOT][02-03-2014]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][GSM+CDMA][Play+Neo L]Slimbean 5.1.1[MULTIBOOT][02-03-2014]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
bootloop
after flashing slimbean zip package my xperia neo l get stucks at sony logo continuously for about 3-4 hrs and i cant even get into recovery mode.... what should i do??
cool.saquib said:
after flashing slimbean zip package my xperia neo l get stucks at sony logo continuously for about 3-4 hrs and i cant even get into recovery mode.... what should i do??
Click to expand...
Click to collapse
flash stock ftf and custom kernel..than install the rom as i said in OP..dont flash all together..flash the rom, reboot, flash neo l patch, reboot.
i flashed stock ftf file then unlocked bootloader , rooted phone, installed cwm 5.1 for neo l
then after that i flashed slimbean 5.1 zip and it said installation aborted due to error!!!
i dont know how to flash the kernel as it is an .img or .iso file...??
sorry for bother you..i have problem..i can't see gallery or something like that to see picture or play video..currently i use slimbean v5.1.1
sorry for my bad english
Maybe install other from play storen, ie quickpic? And u cant look for pictures using slim explorer?
Sent using C6833 - AICP/GreatDevs
update
update the link please
screen flicker issue
i flashed the slimbean rom successfully its working fine with no other issues than SCREEN FLICKERS .... even auto brightness is off.....please provide a fix for this...
Can you install doomskernel on the slimbean 5.1.1 rom?
I want to overclock past 1.6 ghz, but Lupus's kernel is locked to 1.6 ghz.
stuck on SONY TURBO logo
i have MT25i. after trying to install this rom device is now stuck on sony turbo logo.
i say what i did so you can tell whats wrong
1)rooted my phone
2)installed CWM and its recovery
3)my build was 4.1.B.0.631
4)fastbooted turbo kernel 3.1.1 using flahstools
5)opened CWM and wipe data twice. then wipe cache and didn't reboot
6)installed rom
7)rebooted by opening the battery
8)done the same thing for 2 other zip files
but right now when i put battery the sony turbo logo comes and after some time led is white and after that the phone reboots and this procedure goes in a loop
I have to say that i am able to go into recovery
and to let you know this is my FIRST TIME EVER to install a custom ROM.
what do i dooooooooo???????
@whydoesntthiswork
If u have play u can use older version of doomkerbel, which allow oc to 2ghz or extremekernel which allow 3ghz, but device is less stable than on 1,6.
Dont know about neo l.
@up
U need to format system, data and cache after u flashed turbo, coz it has different partition layoult and wont boot with stock one.
Sent using R800i - DiXperia 3 'Enormous'/LuPuS_GB
ch3mn3y said:
U need to format system, data and cache after u flashed turbo, coz it has different partition layoult and wont boot with stock one.
Sent using R800i - DiXperia 3 'Enormous'/LuPuS_GB
Click to expand...
Click to collapse
i did wipe data/factory reset
then wipe cache
is this enough?
No. u need format all three partitions (CWM->mounts and storage). Not sure about TWRP.
And dont forget about system, as its size too needs to be changed
Sent using R800i - DiXperia 3 'Enormous'/LuPuS_GB
ch3mn3y said:
@whydoesntthiswork
If u have play u can use older version of doomkerbel, which allow oc to 2ghz or extremekernel which allow 3ghz, but device is less stable than on 1,6.
Dont know about neo l.
@up
U need to format system, data and cache after u flashed turbo, coz it has different partition layoult and wont boot with stock one.
Sent using R800i - DiXperia 3 'Enormous'/LuPuS_GB
Click to expand...
Click to collapse
I don't think the extremekernel works with jellybean. I tried it and it just puts me in a boot loop. I think it's gingerbread only.
Guys there is another problem. Wifi doesn't work. I use turbo kernel 3.1.1 and i have neo l
And also. The camera is the other way round
@whydoesntthiswork
It won't work, but it's only way. There is no ICS+ kernel with OC higher than 1.6ghz. I'm not sire about DooMKernel for ICSbeta.
@mthcom
Are You usng Neo L turbo kernel or PLAY one? And if I'm not mistaken there need to be patch for Neo L, so rom will work.
EDIT: There is Neo L patch for SlimBean.
Sent using R800i - DiXperia 3 'Enormous'/LuPuS_GB
Wifi problem
I have changed my kernel to the neo l kernel and camera got ok and isnt upside down anymore
but about wifi. it connected in the first moments after installation. but now it doesn't recognize or connect to my network.
what do i dooooo?
@ch3mn3y
mthcom said:
I have changed my kernel to the neo l kernel and camera got ok and isnt upside down anymore
but about wifi. it connected in the first moments after installation. but now it doesn't recognize or connect to my network.
what do i dooooo?
@ch3mn3y
Click to expand...
Click to collapse
Guys is there anybody who can guess what is the problem?
If I need to guess, Your problem is that Your kernel has something called "wifi modules". They are different than rom has built in, so You need to flash it by Your own. Check kernel's thread for something like this.
Sorry that I didn't answer before, but I didn't check XDA for few days and as I'm not subscribed to this thread and You didn't mention me, I wasn't aware about Your post.
ch3mn3y said:
If I need to guess, Your problem is that Your kernel has something called "wifi modules". They are different than rom has built in, so You need to flash it by Your own. Check kernel's thread for something like this.
Sorry that I didn't answer before, but I didn't check XDA for few days and as I'm not subscribed to this thread and You didn't mention me, I wasn't aware about Your post.
Click to expand...
Click to collapse
I use turbo kernel
Developer says that the modules are included in the kernel detected automatically by the kernel
@ch3mn3y
Guys I need help in rooting Xperia T2 D5303 single sim LTE. But after using PRF with Lollipop firmware. There is no Sony logo when booting only a Powered by android appears after awhile, I wonder why? But it works. After I check the cpu settings I foundout that My Minimum Cpu Freq was at 787 MHz by default. I think it has to be in 300 MHz. But it doesent. I cant even seem to install modded Play Store too. Is there any proper way of rooting it? Please tell.me, I really want Lollipop on my T2. By the way I used an an Customized France ftf file downloaded from XperiaFirmware. What is the best version anyway? After decrypting the files in Flashtool, I did notninclude the files in the boot folder when I bundled it. Isbit required? Please help....
In order to get a proper root follow these instructions:
http://forum.xda-developers.com/t2-ultra/general/r-problems-t3096863
About the booting logo, my phone do that too, I don't see a problem with that. On the other hand, the 787 MHZ is a real issue and may be related with the lag that many users had informed. I also found this problem and I used No-frills CPU controll to get the 300 MHz as the minimum clock freq. I haven't had the time to check if there is any difference.
Hello,
You can download trickster mod from play store. It is nice application for kernel settings modifications.
Thanks
hi all
I just bought the Red Magic 5g ......and I love the device but my question is is it worth rooting will I get more out of it or less if I did root please advise me and what are the best practices to do so ........
thank you
i dont think you should root this device... finger print scanner, triggers and bank apps wont work after rooting the deive
Stavrozo said:
hi all
I just bought the Red Magic 5g ......and I love the device but my question is is it worth rooting will I get more out of it or less if I did root please advise me and what are the best practices to do so ........
thank you
Click to expand...
Click to collapse
you can in two ways.
both have their faults.
unlocking bootloader, to root and install custom recovery / rom disables the fingerprint scanner. making it very difficult to reenable it.
using the bypass method allows you to root and install custom recovery and roms, but stock system is not writable.
both ways wipe your phone, you will lose all your data if not backed up.
depending on your use of the device the bypass method more recommended as you keep your fingerprint scanner. and have the ability to get root, install custom recovery, kernel and do some modifications to the phone not normally possible on a locked stock device.
you can use my root guide in my sig to root, it has step by step directions, with a zip that has everything needed to root either a 5G or a 5S device.
Patrick Morgan said:
you can in two ways.
both have their faults.
unlocking bootloader, to root and install custom recovery / rom disables the fingerprint scanner. making it very difficult to reenable it.
using the bypass method allows you to root and install custom recovery and roms, but stock system is not writable.
both ways wipe your phone, you will lose all your data if not backed up.
depending on your use of the device the bypass method more recommended as you keep your fingerprint scanner. and have the ability to get root, install custom recovery, kernel and do some modifications to the phone not normally possible on a locked stock device.
you can use my root guide in my sig to root, it has step by step directions, with a zip that has everything needed to root either a 5G or a 5S device.
Click to expand...
Click to collapse
So you suggest I do the bybass method...
OK so If I put a custom karnel with the bybass methods with the the 7.14 update will it work that's one...
2. What features will I lose??
Stavrozo said:
So you suggest I do the bybass method...
OK so If I put a custom karnel with the bybass methods with the the 7.14 update will it work that's one...
2. What features will I lose??
Click to expand...
Click to collapse
by pass method saves your fingerprint scanner from being lost. so its a much better option if you want to root and use custom things.
by using a 5S rom, 7.14 ( is one of the combined roms based on the 5S kernel) you need to use a 5S kernel.
there is one overclock kernel available for the 7.14 rom. you can find a link on the first post of my mega thread, under the section Custom Kernel.
follow the links and download the V3 version of the kernel from Matts page.
the V3 version is the latest version at the moment.
the only bug on 5G devices is the game space button is reversed, and this stops the advanced options menu in game space from opening.
otherwise, I have not read about any other bugs.
Patrick Morgan said:
by pass method saves your fingerprint scanner from being lost. so its a much better option if you want to root and use custom things.
by using a 5S rom, 7.14 ( is one of the combined roms based on the 5S kernel) you need to use a 5S kernel.
there is one overclock kernel available for the 7.14 rom. you can find a link on the first post of my mega thread, under the section Custom Kernel.
follow the links and download the V3 version of the kernel from Matts page.
the V3 version is the latest version at the moment.
the only bug on 5G devices is the game space button is reversed, and this stops the advanced options menu in game space from opening.
otherwise, I have not read about any other bugs.
Click to expand...
Click to collapse
Wait It won't work with the 5G 7.14 firmware?? I didn't understand this part sorry
Ya I want to add only the custome kernel for now....
Stavrozo said:
Wait It won't work with the 5G 7.14 firmware?? I didn't understand this part sorry
Ya I want to add only the custome kernel for now....
Click to expand...
Click to collapse
7.14 and 8.11 are combined roms for both 5s and 5g devices.
The kernel on these roms are based on the 5s
The old OC kernel matt made, which he has posted here on the 5g fourms dont work correctly with 7.14 and 8.11
He and the dev for LoS stumbled across a random build of thier LoS kernel booted on the 5s
This version seemed to be stable on the 7.14 and 8.11 roms, so matt built an OC kernel using thst LoS type as a base.
So that new OC kernel posted on the 5S fourms (and linked in my rom thread on my sig) will boot on the new updated roms 7.14 and 8.11
So tbe most up to date rom would be either 7.14 or 8.11 depending on your region.
And OC kernel would be the one posted on the 5s forums, Matt said v3 is the best for now.
This combination works on the 5g also.
Patrick Morgan said:
7.14 and 8.11 are combined roms for both 5s and 5g devices.
The kernel on these roms are based on the 5s
The old OC kernel matt made, which he has posted here on the 5g fourms dont work correctly with 7.14 and 8.11
He and the dev for LoS stumbled across a random build of thier LoS kernel booted on the 5s
This version seemed to be stable on the 7.14 and 8.11 roms, so matt built an OC kernel using thst LoS type as a base.
So that new OC kernel posted on the 5S fourms (and linked in my rom thread on my sig) will boot on the new updated roms 7.14 and 8.11
So tbe most up to date rom would be either 7.14 or 8.11 depending on your region.
And OC kernel would be the one posted on the 5s forums, Matt said v3 is the best for now.
This combination works on the 5g also.
Click to expand...
Click to collapse
Nice.... Ok....now to make sure I will do the bybass method with the v3 of the kernel...
One last question does the shoulder buttons still works??
Device is Root solution
Device is Root solution