I seem to have some trouble getting back to the stock kernel of my HOX.
Earlier I placed a CM rom, and flashed the kernel according to the CM requirements.
Since then I'm experiencing trouble receiving text messages. They only appear when I open my (stock ) text app. I'm also not getting the voicemail icon, when having new voicemails.
I flashed the kernel that of my current ROM (via fastboot and app also. both say flashing went ok), but it doesn't seems to change. According to the ROM's information it would be the stock kernel.
Am I doing something wrong, and/or could my issues with the text have nothing to do with the kernel?
Current kernel version:
3.1.10-g7f360be
[email protected]#1
SMP PREEMPT
Current ROM:
Android Revolution HD 33.1 by Mike1986
When flashing the appropriate kernel of a ROM, always make sure to "fastboot erase cache" afterwards.
It could be that your issue has nothing to do with this, just thought I'd point that out.
Unfortunately it did not do the trick. Can my problems be related to the kernel?
Related
I am running the following:
Model Number:SPH-D700
Firmware Version: 2.2.1
Baseband Version: S: D700.0.5S.EC05
Kernel Version:2.6.32.9
Build Number: SRF 1.1.0/TwilightZone 1.1.0
Hardware Version: D700.0.5
I to had the same problem when installing:
"""I got the "$" when I typed in "adb shell" and superuser did show up in the app drawer, so I assumed it took, despite the error I received in cmd."""
However, when I click on an application within the SuperUser app, it gives me the following error: "The application Superuser (process com.noshufou.android.su) has stopped unexpectedly. Please try again." (with a "Forceclose" button)
I also get this error when a incoming call happens and sometimes with text msgs.
"The application Google services Framework(process com.google.process.gapps) has stopped unexpectedly." (With a Forceclose button)
How can I fix these problems? I'm a newbie to all of this, but I'm pretty quick with tech stuff. ... help!
Try reflashing your Kernel by itself through clockwork.
I recently encountered this issue when going to syndicate 1.1.1
For some reason, the Twilight Kernel wasn't flashing properly (or it is not included in the rom itself ) and everything superuser/root related was force closing causing all sorts of issues.
I flashed the Twilight Kernel again, and then in the about page, kernel said Twilight, and now everything works well.
EDIT - Nevermind, it doesn't say Twilight as the Kernel version, but for some reason it worked for me to reflash it.
CW re-flash worked - Contacts?
I did as you said and went into CW and re-flashed the ROM. Everything seems to be running great. However, I'm wondering if importing my contacts is what screwed my ROM up?
Are there any known problems with loading Contacts with custom ROM's?
Specifically Syndicate Frozen ROM?
abqdavid said:
I did as you said and went into CW and re-flashed the ROM. Everything seems to be running great. However, I'm wondering if importing my contacts is what screwed my ROM up?
Are there any known problems with loading Contacts with custom ROM's?
Specifically Syndicate Frozen ROM?
Click to expand...
Click to collapse
I havent read anything through the SRF thread about importing contacts messing anything up.
You may want to post ROM specific problems in their threads so this way the Devs and people that might be experiencing the same problems as you can chime in on
FORCE CLOSE CAME BACK! Dangit!
abqdavid said:
I did as you said and went into CW and re-flashed the ROM. Everything seems to be running great. However, I'm wondering if importing my contacts is what screwed my ROM up?
Are there any known problems with loading Contacts with custom ROM's?
Specifically Syndicate Frozen ROM?
Click to expand...
Click to collapse
After using the phone for a few phone calls the problem came back...
What can I do from here?
Will it screw things up worse if I try the entire process over again? (Root and ROM)
Any help will be greatly appreciated.
David
http://forum.xda-developers.com/showthread.php?t=1091680
I don't know when you downloaded the ROM but the updated the DL link to include the Kernel. I would suggest dling just the Kernel and try flashing that in CWM (Not the ROM, but the KERNEL).
If that doesn't work I would try flashing a different Kernel, either the Genocide or Vision 1.1.
If it still doesn't work then you will have to ask the impaler about it as he know way more than myself about this.
Hi There, I'll try and keep this short, this is regarding my brothers Desire HD:
he's running MIUI 1.7.8 - no problems. Ril 2.2.0018G, Radio 12.54.60.25U_26.09.04.11_M2
We thought we'd try a new ROM, did the usual, wiped data, dalvik cache etc etc. installed Cyanogen 7.0.3 through CWM
He prefers this new ROM. set everything up, then discovered a strange problem, an active call is dropped when the proximity sensor turns the screen off. I looked this problem up (someone else experienced it and did a "fastboot oem eraseconfig" I tried this and it said successful but didnt cure the problem...
I tried to flash the RIL 2.2.0018G in CWM (It said it flashed successful, but when i booted into the ROM, it still had the old RIL installed with the ROM not the new one i just flashed.
One other thing, the Radio that I had was: 12.54.60.25U_26.09.04.11_M2, something strange, the U changed to P after i installed Cyanogen7 ???
I used Nandroid to restore MIUI and the P changed back to a U, the RIL was obviously changed to the one that came with the MIUI ROM and all is now working again.
Q1, Why couldn't i flash a new RIL under Cyanogen (was i doing it wrong - just a normal flash through CWM?)
Q2, Why did the U change to a P in the radio name when i installed Cyanogen?
Q3, Any ideas to the cause of the dropped calls (if not answered in Q1 or Q2)?
I tried, but it still turned into a longer post. sorry.
thanks for your help.
Kevin
I'm not an expert, but I believe RILs can only be flashed in the recovery console. I know I flashed mine there and it worked. No idea why the letter changed
RILs can be safely flashed in CWM, with minimal harm. But do make sure that md5 provided by the dev is matching with yours. If the RIL is restored after rebooting, maybe the RIL is tied with the stock radio. Plus, RIL does not has any effect in AOSP rom.
The radio prefix can change due to rom/radio own setting and region. Read this http://forum.xda-developers.com/showthread.php?t=1068874
Reason of dropped call may caused by dialer that flagged as open application and would kill itself if its clashed with screen off command. Try to reflash/change kernel.
Sent from my HTC Desire HD using XDA App
to use cmd with the phone in fastboot mode you need the "fastboot.exe" file, also you need to make sure the cmd directory points in the correct path. Could be why you didn't actually flash anything.
This is my first post on XDA but i have floated around for a bit learning things and picking things up for a while now. I appreciate all that i have learner. I started with the Nexus One which my gf now uses and i have the Galaxy Nexus.
A bit confused though,
I have the CDMA unlocked and rooted on stock rom with TUNA 13u Kernel. Id really like to use Franco Kernel and a new rom.
My question is, can i just flash a 4.0.3 rom onto the phone or will i lose my radios and not be able to make calls? Ive seen leaked radios but wasnt sure if those were just if you had poor signal, which i dont.
This is the ROM i was going after - http://forum.xda-developers.com/showthread.php?t=1424701
This is the Kernel i was after - http://forum.xda-developers.com/showthread.php?t=1422956
fwiw i looked all over the GNex pages, or what i believed to be the proper ones to find the answer... only thing i see is "for 4.0.1 - 4.0.2" or "for 4.0.3 - 4.0.4"
but nothing stating how to get from one to the other.
Thanks a TON for any input!
J
ROM's usually don't contain radios. They do come with their own kernel. The radio is what controls how Android connects with the baseband and therefore whether or not you can make calls or not. If you don't flash a radio, you'll be able to make phone calls same as you do now (aside from odd issues like the phone.apk crashing).
Kernels never come with radios. Kernels have to be compatible with the ROM you're using. Your chosen kernel is 4.0.3+, so it will work on your 4.0.3 ROM.
Flash your ROM, wipe everything and then flash the kernel. If something doesn't work right, try wiping everything again. If that doesn't work, reflash everything. If that still doesn't work, well, that ROM isn't for you.
ATnTdude said:
ROM's usually don't contain radios. They do come with their own kernel. The radio is what controls how Android connects with the baseband and therefore whether or not you can make calls or not. If you don't flash a radio, you'll be able to make phone calls same as you do now (aside from odd issues like the phone.apk crashing).
Kernels never come with radios. Kernels have to be compatible with the ROM you're using. Your chosen kernel is 4.0.3+, so it will work on your 4.0.3 ROM.
Flash your ROM, wipe everything and then flash the kernel. If something doesn't work right, try wiping everything again. If that doesn't work, reflash everything. If that still doesn't work, well, that ROM isn't for you.
Click to expand...
Click to collapse
Flash ROM then Wipe everything??
Ok, so only the Kernel is dependent on version.
I can flash any version or rom i want to my phone as long as i have an appropriate kernel?
If i do then have an issue with calls it is only because that kernel and rom are not mating well with my radios.
recovery - clear cache - wipe - load from .zip - wait - reboot - wait some more -enjoy?
thanks a lot ATnt!
J
Right now my G2 is running Cyanogenmod-7.1.0 RC1. For the last few months any time I try to update past this version of the rom I lose my microphone. It works absolutely fine with 7.1 but when I go to 7.2 it breaks. For example, When I am on a call I can hear the other person but it is silent on my end. Voice recording programs do not work either, all that it records is a low level of static noise.
I have also tried CM9 and audacity beta4 with the exact same results. When I flash my phone back to 7.1 everything is fine.
Is there some way that I can flash just the old microphone drivers onto the new roms? I am competent enough to follow instructions but not enough to start breaking builds apart for the individual pieces so I don't know where to start.
I have always done a full wipe on everything before I flash.
Does anyone have any ideas? Thank you!
Currently I am running:
Radio: 12.52.60.25U_26.08.04.30_M3
Kernal: [email protected] #1
Mod: Cyanogenmod-7.1.0 RC1 vision
Build number: GRJ22
a
Didn't try any of those,
but this rom:
http://forum.xda-developers.com/showthread.php?t=1492461
works great on my HTC Desire Z with absolutely no issues
It does take a bit of customizing.
I've tried that rom as well but have a whole different issue with that one for some reason. I flash it and then start to reboot and once the phone gets to the white htc screen it freezes with a few horizontal lines running across it. I have to pull the battery and then flash back to my older rom. I have no idea what is going wrong there.
Here might be a dumb question...
Would it help to flash a new kernal? Are the appropriate kernals included in the roms already?
haymaker said:
I've tried that rom as well but have a whole different issue with that one for some reason. I flash it and then start to reboot and once the phone gets to the white htc screen it freezes with a few horizontal lines running across it. I have to pull the battery and then flash back to my older rom. I have no idea what is going wrong there.
Here might be a dumb question...
Would it help to flash a new kernal? Are the appropriate kernals included in the roms already?
Click to expand...
Click to collapse
Hi! Do you solve your problem? I have the same thing there. All the CM roms above 7.0.3 not working with microphone. Do you have still the Cyanogenmod-7.1.0 RC1 file rom and can you upload for me?
Thank you!
GT-I9195T - Telstra variant
I got my phone 3 days ago. WiFi worked fine. One hour after, i rooted and havn't had WiFi since
I did a lot of searching, and the best solutions i found involved flashing the stock kernel. Is this possible, with no backups? I'm a bit of a noob at this, i think i have a stock rooted kernel. I cannot get themes.
The problem with stock might be finding a Telstra Australia kernel.
Are there any other options? I messed about with wpa_supplicant.conf. No luck. Also removed Knox (to the best of my ability, only removed main app and cleared dalvik)
Solved!
How i fixed wifi: I managed to find a kernel that matches my original. After backing everything up, i followed this guide exactly, but used the new kernel instead.
http://forum.xda-developers.com/showthread.php?t=2364980
After flashing the kernel, i restarted the device to find that... nothing changed! but wifi was on! All my data survived the re-root and kernel flash. I thought that was pretty weird.
syskin interested
van0014 said:
Solved!
How i fixed wifi: I managed to find a kernel that matches my original. After backing everything up, i followed this guide exactly, but used the new kernel instead.
http://forum.xda-developers.com/showthread.php?t=2364980
After flashing the kernel, i restarted the device to find that... nothing changed! but wifi was on! All my data survived the re-root and kernel flash. I thought that was pretty weird.
Click to expand...
Click to collapse
Do you have cyanogenmod on now?
No, i'm on the standard kernel, as far as i know.
my settings says
Device status
Custom
Baseband: I9195TDVUAMH1
Kernel version
3.4.0- 1266356
[email protected] #1
Thu Aug 1 16:19:03 KST 2013
Build number
JDQ39.I9195TDVUAMH1
Serial number
R21D94ZK1HH
I'm still a bit new to rooting so i just posted everything. You should be able to understand it a bit better.