Hi,
I have a issue that im not used to... i recently got a Nexus 5, and first thing i did was to unlock, root and install aokp rom(nightly)
Then i wanted to install Franco Kernel, using Francos own app to try flash... the device reboots, and are stuck on the google logo.
Have no other choice to enter fastboot mode, and reflash rom(to have it overwrite the kernel), and it starts up again.
Then tried to download kernel zip and flash it in TWRP instead, but with the same result. Also tried changeing to CWM but it doesnt work with encrypted devices.
I have always used AOKP + Franco Kernel on my older devices, but now it seems impossible.
I dont know why it doesnt work, but i have some ideas, and hope someone can put me in the right direction.
1. My device is encrypted and that makes it fail.
2. AOKP lastest nightly rom is not compatible with Franco Kernel or vice versa.
3. Something is broken...
Regards
Ranarn
aokp is cm based(CAF) i believe, which would make it incompatible with any aosp kernels.
simms22 said:
aokp is cm based(CAF) i believe, which would make it incompatible with any aosp kernels.
Click to expand...
Click to collapse
Ah that makes sense, but i guess something have changed then, since i have AOKP + Franco running on 2 older devices.
ranarn said:
Ah that makes sense, but i guess something have changed then, since i have AOKP + Franco running on 2 older devices.
Click to expand...
Click to collapse
yea, just last week cm source went back to CAF.
I know chaos kernel is CAF supported, I would give that a shot. I am still running 9.1 and it works the way I want it to for me (before they went CAF).
mistahseller said:
I know chaos kernel is CAF supported, I would give that a shot. I am still running 9.1 and it works the way I want it to for me (before they went CAF).
Click to expand...
Click to collapse
Ah thanks alot for the answers... not i know what kernels i can look for...
Related
Hi,
I need some help. I am an XDA lurker and have learned a ton. I am mostly aware of the usual fixes for these things, but I can not return to any other ROM than a CM10. CM10 data and camera are not working great, even though I LOVE this ROM and LOVE these developers, I can't use it yet.
Firtst, my backups are gone, I know, I know. But they are gone. I tried flashing NoSympothy and invisibleK,s stock ROMs but I get frozen at the Galaxy SIII screen everytime.I have tried all the usual system wiping drills, cache, data, etc... Formatted everything. I have downloaded from multiple sources. It seems like it doesn't like ICS now?
I am rooted and UNLOCKED! Woohoo, thanks Adam!!!!!
Any suggestions?
Recoverys to CM10 work. New flashes to CM10 work. But no stock image or stock rom?
rude53 said:
Hi,
I need some help. I am an XDA lurker and have learned a ton. I am mostly aware of the usual fixes for these things, but I can not return to any other ROM than a CM10. CM10 data and camera are not working great, even though I LOVE this ROM and LOVE these developers, I can't use it yet.
Firtst, my backups are gone, I know, I know. But they are gone. I tried flashing NoSympothy and invisibleK,s stock ROMs but I get frozen at the Galaxy SIII screen everytime.I have tried all the usual system wiping drills, cache, data, etc... Formatted everything. I have downloaded from multiple sources. It seems like it doesn't like ICS now?
I am rooted and UNLOCKED! Woohoo, thanks Adam!!!!!
Any suggestions?
Recoverys to CM10 work. New flashes to CM10 work. But no stock image or stock rom?
Click to expand...
Click to collapse
You have to flash the stock kernel as well as the ROM. Try flashing the Synergy latest nightly build it includes a custom kernel as long as your bootloader is unlocked.
Thanks,
I had a feeling it was something with the kernel. I wasn't sure what was included though. I think I tried to get synergy from here on my phone and it just kept opening new windows instead of downloading. I will grab the just the kernel from somewhere and let you know. I'll update in an hour or so. Thanks for the next few steps to try. Much appreciated!
That was it THANKS!!!
adclem said:
You have to flash the stock kernel as well as the ROM. Try flashing the Synergy latest nightly build it includes a custom kernel as long as your bootloader is unlocked.
Click to expand...
Click to collapse
Stock ROMs include the stock kernel. They will work as a one flash wonder. Your issue more sounds recovery based. Which recovery from which app were you using? It more sounds lime maybe you're still on a kexec recovery which is why you couldn't flash stock but synergy latest worked (or something of the sort, maybe other way around)
Sent from my Galaxy S3 using Tapatalk 2
Done a bit of research now and all the keywords I have searched through haven't returned any results of this particular issue.
I have flashed CM10 (Stable) to the XL, has installed and boots fine, however there is 0 feedback from the touchscreen so i can't use it at all.
I couldn't really find anyone else with a similar issue. Has anyone run into this, or know what may be causing it?
Have downloaded numerous times, different versions of twrp, everything's been cleared out/wiped (both before and after flash).
I'll add that I have not had this issue at all elsewhere, EXCEPT where yesterday I updated stock to the latest version to give it a go (was hoping for more of a JB experience...). In this case there is / was a bug with TWRP where if you installed Android 4.1 (Latest stock), the touch would no longer work in TWRP. Luckily the TWRP dev updated to 2.3.3.1 today, fixing the touch again (which some themes such as viper require). But I have no idea if any of this is related, shouldn't be though,given the rom should work standalone...
Any ideas would be great. I battled to overcome that damn TWRP mess (seen above) that I got myself into, then I got past a boot issue and now that I'm booted the damn touch doesn't work lol.
Hope to hear some good news,
regards.
Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source.
-known issue, but only yesterday I told h8rift and Rohan who previously were unaware of the issue.
-The change is in firmware delivered with 3.17
-Requires kernel update to resolve issue.
-Twrp easy to fix.
-Cm and others not so easy and may require waitng for source from HTC.
twistedddx said:
Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source.
-known issue, but only yesterday I told h8rift and Rohan who previously were unaware of the issue.
-The change is in firmware delivered with 3.17
-Requires kernel update to resolve issue.
-Twrp easy to fix.
-Cm and others not so easy and may require waitng for source from HTC.
Click to expand...
Click to collapse
Thanks for your reply. I just tried installing JellyBam now and alas the same issue, checking here confirms things
Can you recommend a Kernel that will work for the mean time? I was actually looking at some of the kernels, but didn't really go anywhere with it.
You can only use roms and kernels made from 3.17 for the time being.
twistedddx said:
You can only use roms and kernels made from 3.17 for the time being.
Click to expand...
Click to collapse
This sucks. I can't find a single rom/kernel that is compatible with whatever this 3.17 'thing' is (what's this the version of?). Can i roll back this version?
I can't even use the RUU to go back to stock because now the phone has blank version numbers and details and errors out.
My restores also don't work. Only JB roms actually boot now and all of them don't have any touch screen support. I AM able to get touch support if i install the ElementX JB kernel, however that then throws infinite "nfc and android.phone process-stop" messages (just after applications are being upgraded w/ the first boot of a JB rom).
Just looking to make the phone work
Playing around with Joker and have got the phone back into a working state. *phew*
xlmama said:
I can't find a single rom/kernel that is compatible with whatever this 3.17 'thing' is (what's this the version of?). Can i roll back this version?
I can't even use the RUU to go back to stock because now the phone has blank version numbers and details and errors out.
Click to expand...
Click to collapse
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
twistedddx said:
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
Click to expand...
Click to collapse
Thanks for your help. I'm now not clueless about my phones fate. :victory:
I have the same issue - updated to Andriod 3.17 about a week ago, and decided to flash CM10 afterwards. As a result, I am stuck with no touchscreen functionality.
Have there been any updates the past few days in terms of ROM's being released that will work on 3.17? How far into the future are we talking about before a release of CM10 will become available?
Is there no way to revert back to ICS and thus have a fully functioning version of CM10?
Is there any news on this issue ?
It's not possible until HTC releases kernel source. There's nothing the devs can do. You can only run sense roms
Sent from my VENOMized HoxL
twistedddx said:
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
Click to expand...
Click to collapse
Not mine, tried it twice. The only ROM I've been able to get running is PA 2.54, and the only way I could get the touchscreen to work is by flashing the Kernal from Hatkas ROM. Even that fc'd NFC to the point repeatedly So I'm thinking if I can find [or get help finding] a 3.17.661 kernal that will work with PA, I'll be golden.
I think I may be having the same problem, though I don't remember ever upgrading to 3.17. Is what you all are seeing like the screen doesn't even turn on? It just stays black, but the power button and volume button seem to be responsive? I can't even seem to get into recovery or bootloader, and this all started when I flashed the latest CM10 nightly.
Never mind.
Magickalhack said:
Not mine, tried it twice. The only ROM I've been able to get running is PA 2.54, and the only way I could get the touchscreen to work is by flashing the Kernal from Hatkas ROM. Even that fc'd NFC to the point repeatedly So I'm thinking if I can find [or get help finding] a 3.17.661 kernal that will work with PA, I'll be golden.
Click to expand...
Click to collapse
You do realized you flashed a sense kernel for an aosp Rom?... And you're wondering why it gave you FC's?
I'm on hboot 1.09, did not do OTA update, and the touchscreen works on CM 10.1 90% of the time, but sometimes I open it up and it doesn't respond. Hitting the sleep button twice fixes it but it's annoying. Would the above fix do anything for me? What else could be the problem?
slash178 said:
I'm on hboot 1.09, did not do OTA update, and the touchscreen works on CM 10.1 90% of the time, but sometimes I open it up and it doesn't respond. Hitting the sleep button twice fixes it but it's annoying. Would the above fix do anything for me? What else could be the problem?
Click to expand...
Click to collapse
Do you use s2w? That causes that issue
Sent from my VENOMized HoxL
Hello!
I've had a search of my issue but so far not been able to find any related answers
I'm wanting to try the other kernels that are available, Trinity, Elemental etc However, when i flash the different kernels it leaves the UI of the current ROM installation corrupt and I can't even get past my lock screen. Status bar is at the bottom and the rest of the UI is shifted up. Reflashing franco fixes the problem and the ROM returns to normal.
Is this simply a case of needing to reinstall the ROM, and I'm just being lazy and expecting kernels to be swappable like this?
Many thanks for any help.
mebbez said:
Hello!
I've had a search of my issue but so far not been able to find any related answers
I'm wanting to try the other kernels that are available, Trinity, Elemental etc However, when i flash the different kernels it leaves the UI of the current ROM installation corrupt and I can't even get past my lock screen. Status bar is at the bottom and the rest of the UI is shifted up. Reflashing franco fixes the problem and the ROM returns to normal.
Is this simply a case of needing to reinstall the ROM, and I'm just being lazy and expecting kernels to be swappable like this?
Many thanks for any help.
Click to expand...
Click to collapse
because you are on franco kernel, you will need to dirty flash your rom first(without wiping anything). franco kernel also changes system files. dirty flash your rom, gapps, and new kernel, then boot up.
simms22 said:
because you are on franco kernel, you will need to dirty flash your rom first(without wiping anything). franco kernel also changes system files. dirty flash your rom, gapps, and new kernel, then boot up.
Click to expand...
Click to collapse
Thanks a lot for the fast reply. I'll give it a shot!
Does dirty flashing the rom have an effect on the overall performance? Is it always better to do a clean install when trying to get the most out of your device?
Thanks again.
mebbez said:
Thanks a lot for the fast reply. I'll give it a shot!
Does dirty flashing the rom have an effect on the overall performance? Is it always better to do a clean install when trying to get the most out of your device?
Thanks again.
Click to expand...
Click to collapse
na, doesnt affect a thing. i dirty flash nearly 100% of the time
simms22 said:
na, doesnt affect a thing. i dirty flash nearly 100% of the time
Click to expand...
Click to collapse
brilliant, i've done the dirty flash and now trying out elemental kernel and working with no issues at all.
Thank you so much for the help.
ps. praise science for OTG cables!
mebbez said:
brilliant, i've done the dirty flash and now trying out elemental kernel and working with no issues at all.
Thank you so much for the help.
ps. praise science for OTG cables!
Click to expand...
Click to collapse
I bought the FKU app and I've been using it with the kernel updates for a good amount of time, but now I installed AOKP and used the app to auto-flash r34 and I got stuck at the the Google with the open lock screen. I thought it was a corrupt download or something, so wiped it and installed r33 from franco's archives. Same thing. r32, same thing. I even installed CM11 and retried and got the same result.
If anyone is having the same problem let me know!
Franco's kernel does not work with CM11 anymore, it's written all over Franco's kernel thread.
I'm not sure about AOKP, but if it's based on CM11, or if they went the same road as CM, that will not work as well.
Hello,
I searched for this issue but couldn't find the exact problem being experienced by others, so I'm asking about it now.
So I'm using the latest MultiROM and Lollipop firmware (the 02/09 one). I simply can't get any Lollipop ROM to stop bootlooping with a recent kernel. Boeffla, AK, Tyr, etc. all bootloop with every LP ROM I've tried, regardless if they're set as primary or secondary in recovery.
The only way I can get a ROM to boot is with a kernel meant for CM11/S, like AK r77 and Sensei r77, though I can't get the radios to work with these. But newer kernels simply won't work, period.
Am I missing something here? I thought the latest firmware and a recent kernel with kexec-hardboot was all I needed.
Edit: Also seems to happen with a fresh install of the latest CM nightly. Using the default kernel that comes with CM, too. There must be something that I am missing here...