Related
So, there is Haus's thread which provides download links to the ROM, Kernel and Radios.
I am currently running Salvage Mod and a Tiamat kernel.
If I flash the 2.3 OTA ROM while still running the Tiamat kernel, will I run into issues?
Mindspin_311 said:
So, there is Haus's thread which provides download links to the ROM, Kernel and Radios.
I am currently running Salvage Mod and a Tiamat kernel.
If I flash the 2.3 OTA ROM while still running the Tiamat kernel, will I run into issues?
Click to expand...
Click to collapse
No because after you flash you will no longer be running the Tiamat kernel you will be running the new stock HTC kernel. Flashing the ROM flashes the kernel as well.
zone23 said:
No because after you flash you will no longer be running the Tiamat kernel you will be running the new stock HTC kernel. Flashing the ROM flashes the kernel as well.
Click to expand...
Click to collapse
Oh...
I was under the impression (based off the links provided in the other thread) that the ROM and kernel needed to be flashed separately.
Thanks for clarifying!!
Mindspin_311 said:
Oh...
I was under the impression (based off the links provided in the other thread) that the ROM and kernel needed to be flashed separately.
Thanks for clarifying!!
Click to expand...
Click to collapse
Generally no I flashed it on my EVO and didn't flash any thing else. You might want to go back and take another look I will as well but that generally not the case they come with the kernel.
To flash back to sense you don't have to do anything special. You don't have to nandroid back to sense or anything like that. The only thing you have to do is clear user data, cache, and dalvik cache then flash. You don't need to restore anything first. I saw your other post. Also I'm fairly positive that the ROM has the kernel but if you want to be safe download the kernel as well and just stick it on your storage card just in case.
Remember clearing user data will wipe all of your apps and data.
The kernel is a modified one just incase you have the brightness bug still I think.
When I flashed the new mikg v1.0 i know I still did but I flashed that kernel and it fixed it but I never flashed one of the new stock ROMs cause of the 1.0 sense on it.
Sent from my PC36100 using XDA App
I've been trying out multiple ICS ROMS for my R800x (FXP, AOKP, CM9, PlAyOPS and maybe something else, I've lost track) and I can only get the WiFi to turn on with PlAyOPS ROM. It's not a connection issue, I cannot actually get the WiFi to switch on, the slider is grayed out and it won't even slide over to the on position. I've tried the WiFi fix zips that are brought up on the ROM specific threads to no avail. I think I've tried every kernal/ROM/WiFi fix combination that I've come across. I'm currently using Keiran's 2.6.32.9 Darkforest kernal but I have also tried the FXP kernal and the LuPus v3 kernal.
The reason I'm not just sticking to the PlAy OPS ROM is that I use the bluetooth audio feature quite frequently in both my cars and it doesn't work correctly on PlAyOPS. I was able to get the bluetooth audio to work on FXP and, if I remember correctly CM9. I haven't tried bluetooth audio on AOKP yet. If I could get the WiFi to work on either of these ROMS I would be extremely happy.
I've been searching the internet and scouring this forum for a fix for my issue for nearly a month but I cannot find a solution for my specific problem. I greatly appreciate any assistance!
fuhrl said:
I've been trying out multiple ICS ROMS for my R800x (FXP, AOKP, CM9, PlAyOPS and maybe something else, I've lost track) and I can only get the WiFi to turn on with PlAyOPS ROM. It's not a connection issue, I cannot actually get the WiFi to switch on, the slider is grayed out and it won't even slide over to the on position. I've tried the WiFi fix zips that are brought up on the ROM specific threads to no avail. I think I've tried every kernal/ROM/WiFi fix combination that I've come across. I'm currently using Keiran's 2.6.32.9 Darkforest kernal but I have also tried the FXP kernal and the LuPus v3 kernal.
The reason I'm not just sticking to the PlAy OPS ROM is that I use the bluetooth audio feature quite frequently in both my cars and it doesn't work correctly on PlAyOPS. I was able to get the bluetooth audio to work on FXP and, if I remember correctly CM9. I haven't tried bluetooth audio on AOKP yet. If I could get the WiFi to work on either of these ROMS I would be extremely happy.
I've been searching the internet and scouring this forum for a fix for my issue for nearly a month but I cannot find a solution for my specific problem. I greatly appreciate any assistance!
Click to expand...
Click to collapse
Back up data, flash back to stock rom, install kernel, wipe data, cache &dalvic cache in recovery mode, re-install CM9 with the included FXP kernel and that should be it.
Xperia Player said:
Back up data, flash back to stock rom, install kernel, wipe data, cache &dalvic cache in recovery mode, re-install CM9 with the included FXP kernel and that should be it.
Click to expand...
Click to collapse
when you say install kernel, which kernel am i installing? the stock kernel or the FXP? when i re-install CM9 don't I have to install the FXP kernel first or will it automatically do it for me when i re-install CM9?
fuhrl said:
when you say install kernel, which kernel am i installing? the stock kernel or the FXP? when i re-install CM9 don't I have to install the FXP kernel first or will it automatically do it for me when i re-install CM9?
Click to expand...
Click to collapse
Install FXP kernel first, then flash CM9.
Sent from my unlocked R800x using XDA Premium
DubleJayJ said:
Install FXP kernel first, then flash CM9.
Sent from my unlocked R800x using XDA Premium
Click to expand...
Click to collapse
ok. thanks. Just as a clarification to the first part of the original response, I am installing the original stock kernel after i flash back to the stock ROM?
well, i went back to stock, flashed the kernal, wiped all my data, flashed the FXP kernal then re-installed FXP with no luck. I tried flashing the wifi zips after than without success. i guess i'm stuck with what i have unless there's something else i could try.
fuhrl said:
well, i went back to stock, flashed the kernal, wiped all my data, flashed the FXP kernal then re-installed FXP with no luck. I tried flashing the wifi zips after than without success. i guess i'm stuck with what i have unless there's something else i could try.
Click to expand...
Click to collapse
What version of FXP are you using, and what are the wifi zips called that you're using?
lightningdude said:
What version of FXP are you using, and what are the wifi zips called that you're using?
Click to expand...
Click to collapse
i used FXP 132. I know it's not the latest but I'm sure that it was when I downloaded it a month ago. The zips were cleverly named wififix2, WiFi_FiX_LuPuSv3 and the other was CDMA_mega_fix_v2_by_Leraeniesh. The last one had a WiFi fix in it by Atarii or someone like that.
had the same problem on my play (GSM version) here is what i did. and im sure it will work for you. flash the latest FTF for your device (Baseband).
when done Put the CM 9 Kernal on the phone. Boot in to recovery. do a factory reset. flash the CM 9 reboot and you are good to go.
nyvang101 said:
had the same problem on my play (GSM version) here is what i did. and im sure it will work for you. flash the latest FTF for your device (Baseband).
when done Put the CM 9 Kernal on the phone. Boot in to recovery. do a factory reset. flash the CM 9 reboot and you are good to go.
Click to expand...
Click to collapse
i've done that twice now. this has been extremely frustrating. i don't know why the wifi will work without fail on one ROM but not work at all on others.
just to make sure i'm doing this correctly. After I flash the original FTF am I flashing the CM9 kernel directly after that? Do I have to restore the original kernel at all?
Speaking of wifi problem I cant get wifi to work on GB tweaked running doomkernel V2.....odd.
Xperia Player said:
Speaking of wifi problem I cant get wifi to work on GB tweaked running doomkernel V2.....odd.
Click to expand...
Click to collapse
i think you have to flash doomlords wifi modules in recovery. it's what worked for me when i was using that rom.
http://forum.xda-developers.com/showthread.php?t=1579388
fuhrl said:
i've done that twice now. this has been extremely frustrating. i don't know why the wifi will work without fail on one ROM but not work at all on others.
just to make sure i'm doing this correctly. After I flash the original FTF am I flashing the CM9 kernel directly after that? Do I have to restore the original kernel at all?
Click to expand...
Click to collapse
The ftf has the stock kernel in it.
Sent from my SCH-I500
here is what i did step by step.
1 Flashed Everything back to original. using R800i_4.0.2.A.0.62_Generic Baseband. (stock kernel too) using flashtool form here http://forum.xda-developers.com/showthread.php?t=1351299
2 booted the phone.
3 shut down the phone
4 Flahs kernel provided with the rom.
5 Went to recovery. Ran a reset factory. clear cache, clear Dalvik, reset battery stats.
6 Flashed the rom. in this case FXP 135.
nyvang101 said:
here is what i did step by step.
1 Flashed Everything back to original. using R800i_4.0.2.A.0.62_Generic Baseband. (stock kernel too) using flashtool form here http://forum.xda-developers.com/showthread.php?t=1351299
2 booted the phone.
3 shut down the phone
4 Flahs kernel provided with the rom.
5 Went to recovery. Ran a reset factory. clear cache, clear Dalvik, reset battery stats.
6 Flashed the rom. in this case FXP 135.
Click to expand...
Click to collapse
did this work? i have the latest PACman JB rom for the r800x and im using the lupus v5 kernel that came with it. for some reason all the other roms have working wifi except cyanogenmod based roms....... why is this?
I flashed KT747 a two or three days ago. I just noticed that I am back to the stock kernel. I didn't flash back to stock kernel. The only thing I can think of is that I tried flashing the 10.1 12/10 preview build but CWM aborted right away due to bad download. So nothing should have been flashed. I have also made two nandroid backups since flashing KT747.
I didn't notice any big difference between stock kernel and KT747. I'm not sure if I'll relfash or not. I really just want to know what the heck happened
Turns out flashing nighties also flashes back to CM kernel.
cavolt said:
Turns out flashing nighties also flashes back to CM kernel.
Click to expand...
Click to collapse
Yes, flashing any ROM will over-write the kernel
Hi everyone,
I wasn't used to consider myself a too-much-noob anymore, but now I've plenty of doubts.
So, here's my problem: I've decided to give the latest ParanoidAndroid release a try and my maguro was "oem locked". Then, I've run the command "fastboot oem unlock" and copied all files I needed (PA rom, GlaDos v2.2 and latest GApps) into my /sdcard folder (usual job). I've rebooted into recovery (latest touch CWM), formatted /system, /data, /cache (usual full wipe), searched for the files and flashed them.
When it was time to reboot, the phone got stuck at the first screen (black, with the white "Google" and the white opened padlock). In other words, the bootanimation didn't even start.
Then, I've re-downloaded the stuff, double-checked all Md5 sums, re-copied everything in the sdcard but the result didn't change.
I've tried to re-flash the stock unrooted rom, then repeating the steps without formatting /system. I've also tried to not flash the kernel. No way the rom could even boot.
Now I'm seriously wondering what's wrong with what I've done . For completeness, my bootloader version is LC03 and the radio is XXLJ1 (same as the fully stock android bundle that can be found here)
I've also checked (maybe too much quickly, I may admit) the threads for PA and GlaDos, but I haven't seen anyone complaining about the same problem...
Could you guys please help me?
First of all....
all you need to do to wipe is select
FACTORY RESET in custom recovery
Secondly:
GlaDos 2.2 is probably not going to work with PA3.0
- Based on stock Android kernel Jelly Bean 4.1.1 JRO03C
Click to expand...
Click to collapse
Pirateghost said:
First of all....
all you need to do to wipe is select
FACTORY RESET in custom recovery
Secondly:
GlaDos 2.2 is probably not going to work with PA3.0
Click to expand...
Click to collapse
Thank you for the reply, but i've also tried the factory reset you mean (no results) and, for GlaDos, my bad, I've linked an XDA thread instead of the "original" updated thread on rootzwiki
Endriu90 said:
Thank you for the reply, but i've also tried the factory reset you mean (no results) and, for GlaDos, my bad, I've linked an XDA thread instead of the "original" updated thread on rootzwiki
Click to expand...
Click to collapse
i have been looking forward to a new GladOS...thanks for the link
in recovery, all you have to do is factory reset then flash the rom. thats it
EDIT:
which version of PA 3.0 are you trying to install
Pirateghost said:
which version of PA 3.0 are you trying to install
Click to expand...
Click to collapse
I've tried with all releases which can be found here
Flash Kernel too
Hi,
When the new PA version was uploaded (20 Feb), this was the warning posted by the developer:
WARNING
As I didn't have so much time, I couldn't make it booting with default kernel (Need to update prebuilt kernel). So if you're gonna use it BE SURE YOU FLASH A CUSTOM 4.2.2 KERNEL!
Click to expand...
Click to collapse
So I recommend you download any latest 4.2.2 kernel (AK kernel or franco) and flash it alongwith the ROM.
Hope this helps.
Regards,
Neeraj
neerajvd said:
So I recommend you download any latest 4.2.2 kernel (AK kernel or franco) and flash it alongwith the ROM.
Click to expand...
Click to collapse
Thank you guys, I've solved (I've tried just with the factory reset as said by pirateghost, but I was used to format /system, /data and /cache when it was time to flash roms like AOKP and everything used to work properly) (I was used to do the same with the Nexus S).
Now I'm running the 15feb release with the stock android kernel (which comes with the stock 4.2.2 factory bundle) and everything just works as expected.
Anyway, I still can't get the reason why GlaDOS shouldn't work with the 20feb release. I mean, it's a custom kernel and it should work as well as AK or franco kernels, shouldn't it? If I'm wrong, could you briefly tell me why? (sorry, I won't move to other kernels, as I personally love GlaDOS and it provides my GNex with the optimal equilibrium performances/battery life)
EDIT:
alongside the 15feb release, I've tried to flash GlaDOS (just factory-resetting before flashing), but nothing boots. Restored the backup, now I'm still running PA with the stock kernel
My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Shane24 said:
My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Click to expand...
Click to collapse
Hey man,
My suggestion is to use Odin to flash the stock image back to stock and see if the problem persists. If it does, I'd take it back to at&t for a new phone (if you've had it less than a year or you have some sort of insurance plan.)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 02:23 AM ---------- Previous post was at 02:18 AM ----------
If flashing back to stock fixes it, its user error. Make sure you're up to date on everything, I.e boot loader, recovery, everything. If that does nothing for you maybe try flashing the new version of CWM and see if it'll flash right that way.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Is it just me or is your lean kernel like years old? Isn't the newest version 7.2?
Same with your rom.. 2.9 is out?
Sent from my SGH-I747 using xda premium
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Shane24 said:
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Click to expand...
Click to collapse
Hey man,
If you're going to be flashing custom ROMs you should probably learn what a kernel is. Use the search feature or simply use google. In fact, the xda TV channel just put out a video on kernels this week on YouTube.
Anyways, as I said previously, make sure EVERYTHING is up to date. Including the ROM version. Dont worry about flashing kernels until you have a solid understanding of what they are. I'm almost positive that you are just flashing out of order. Just start from scratch, make sure EVERYTHING is up to date. Good luck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
What the guy above me said about TW roms is correct. Flashing the wrong kernel is not a good idea. Here's what I do on every flash
- wipe system, data, caches, etc.
- flash rom( and gapps if necessary)
- boot up rom and let it settle for 5 min, then boot back into recovery
-flash correct kernel for the rom's version(check kernel number in about device and custom kernels op), then wipe both caches and fix permissions.
-reboot and enjoy:laugh:
DMF1977 said:
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Click to expand...
Click to collapse
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Shane24 said:
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Click to expand...
Click to collapse
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
DMF1977 said:
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
Click to expand...
Click to collapse
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Shane24 said:
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Click to expand...
Click to collapse
What?
What DMF1977 was saying is just flash the ROM you desire to have on your device and just run the kernel that comes with the ROM. After running the ROM you chose for awhile, if you feel the need to flash a new kernel then and only then flash the correct version of Ktoonsez kernel. And its not surprising that if you tried to flash anything AOKP related with TW you got an error.
Just flash an AOKP ROM and Dont worry about flashing an additional kernel.
Goodluck
Sent from my SAMSUNG-SGH-I747 using xda app-developers app