Hello, guys and girls.
So, I'm not an expert like most of you. I need help.
I will explain you what happend with my Nexus 4: I installed CyanogenMod 11 with the installer some weeks ago. Yesterday, I installed an app called "Touch Control", which would allow my phone to have Knock On feature. But it installed a kernel that would make this work. That kernel have MANY bugs, such as Wi-Fi do not work and changed colors. My phone does not have internet, because I don't have mobile data.
I do not have TWRP or CWM, just the simple CyanogenMod Recovery. And I can't install anything because of internet (I can copy .apk to my phone and insall it).
Here is what I would by happy to do: change that kernel to the default one (I didn't make its backup) or to any other kernel that works.
Ask, please, for any detail that can help.
Thank for you to reading my post.
Just something else: I don't want Knock On feature anymore. I just wan't my phone working properly.
What you did was install a AOSP kernel on a CM rom, that does not work well as you might have noticed, you need to dirty flash CM11 to get the default kernel back.
nibla101 said:
What you did was install a AOSP kernel on a CM rom, that does not work well as you might have noticed, you need to dirty flash CM11 to get the default kernel back.
Click to expand...
Click to collapse
I have a question: when I flash CM11, will the kernel be replaced? I heard that the kernel in Android phones is separate from the operating system.
caiodanielnunessantos said:
I have a question: when I flash CM11, will the kernel be replaced? I heard that the kernel in Android phones is separate from the operating system.
Click to expand...
Click to collapse
Yes it will, all roms come paired with a kernel otherwise they would not boot.
When you dirty flash CM11 it will replace ur /system and /boot(this is where the kernel is) but it will leave ur /data and /sdcard so your apps and settings remain.
nibla101 said:
Yes it will, all roms come paired with a kernel otherwise they would not boot.
When you dirty flash CM11 it will replace ur /system and /boot(this is where the kernel is) but it will leave ur /data and /sdcard so your apps and settings remain.
Click to expand...
Click to collapse
Thanks, I will try this.
The most easy way to get back to stock kernel (no matter which android u currently have) is to use a toolkit like Wugfresh and select the stock kernel option.
Only think u need is a pc with internet and the phone to be connected with the cable.
Related
Hello XDA,
First time posting so I have to ask in Q&A rather than the thread for MultiROM itself. I've been to these forums quite a few times for rooting and unlocking other's devices, but now that I have a Nexus 7 myself, it's time to start messing around with it.
So the situation for my problem is that I have successfully installed MultiROM and was able to boot up my stock image fine, but when I installed Cyanogenmod 10.0.0, the screen automatically goes to the boot screen for Cyanogenmod rather than asking which ROM to boot and then just hangs on that boot screen forever.
I have not used the kexec hardboot patches for anything yet so it can be that I should be using those somewhere along in the process.
Also, how do I go about uninstalling MultiROM so that I can start all over again? Do I just go into TWRP and hit "install" and choose the stock image for 4.2.1?
destructo322 said:
Hello XDA,
First time posting so I have to ask in Q&A rather than the thread for MultiROM itself. I've been to these forums quite a few times for rooting and unlocking other's devices, but now that I have a Nexus 7 myself, it's time to start messing around with it.
So the situation for my problem is that I have successfully installed MultiROM and was able to boot up my stock image fine, but when I installed Cyanogenmod 10.0.0, the screen automatically goes to the boot screen for Cyanogenmod rather than asking which ROM to boot and then just hangs on that boot screen forever.
I have not used the kexec hardboot patches for anything yet so it can be that I should be using those somewhere along in the process.
Also, how do I go about uninstalling MultiROM so that I can start all over again? Do I just go into TWRP and hit "install" and choose the stock image for 4.2.1?
Click to expand...
Click to collapse
It's overwriting the kernel with one of its own... that's the only thing I can think of. Flash a kernel that has MultiROM support like m or motley.
Mac of York said:
It's overwriting the kernel with one of its own... that's the only thing I can think of. Flash a kernel that has MultiROM support like m or motley.
Click to expand...
Click to collapse
Does this mean that I should find a version of CM that has one of those kernels? Or do i simply flash the kernel by itself and that would overwrite the CM kernel so that the problem would be resolved?
Also I tried installing Kaos Droid and chose the option to install the M kernel before CM actually and I remember that it also would just boot to a completely black screen and nothing past that. So i'm not sure if it's the kernel. But i did just successfully go back to stock and rooted again so that I will try out your suggestions tomorrow. Thanks.
destructo322 said:
Does this mean that I should find a version of CM that has one of those kernels? Or do i simply flash the kernel by itself and that would overwrite the CM kernel so that the problem would be resolved?
Also I tried installing Kaos Droid and chose the option to install the M kernel before CM actually and I remember that it also would just boot to a completely black screen and nothing past that. So i'm not sure if it's the kernel. But i did just successfully go back to stock and rooted again so that I will try out your suggestions tomorrow. Thanks.
Click to expand...
Click to collapse
You can flash the kernel separately and it'll be fine.
Sent from my Nexus 7 using Tapatalk HD
Alright, Ive had my nexus 7 for a while and I want to unlock it and root it. I havent decided what rom to use yet. (Would love input on good ones, 4.2.x) I plan on using the Motley kernel, but I was wondering in what order should I flash them in, should I flash the rom and gapps then let it boot up and settle in, and then flash the kernel? Or the opposite? (Kernel first, then rom). Just looking for an answer to the flashing order and feedback on good 4.2.x roms, I was thinking either Paranoid 2.99 Beta or CM10 Nightlies
ROM goes first; otherwise your custom kernel will be overwritten.
Sent from my Nexus 7 using Tapatalk HD
Alright thank you, now Im just wondering about a good 4.2.x rom
Ok Ive unlocked and root my nexus, and I try installing a custom recovery (TWRP) and then when I go to the reboot recovery option in Nexus toolkit, it boots to a droid with a red triangle, and wont do anything, I have to hold down the button till it restarts..
I went through most of the the Nakasig Tilapia ROMs (Nexus 7 3G) here on XDA and decided on this one from my signature (temasek's).
Also, tried some kernels (faux, motley) and decided on the franco one (based on the Battery Saving skills I saw in a study-type post).
Why this temasek's? I was searching and didn't find a ROM more flexible than the CyanogenMod at the moment. I may be mistaking (this is my oppinion).
It has a lot of options and customization you can do, BUT, this temasek's ROM has all of these and also his own features ( Tethering and portable hotspot was what I was seeking, you can also check the rest out).
Hope that helped. :silly:
Purevulcan0 said:
Ok Ive unlocked and root my nexus, and I try installing a custom recovery (TWRP) and then when I go to the reboot recovery option in Nexus toolkit, it boots to a droid with a red triangle, and wont do anything, I have to hold down the button till it restarts..
Click to expand...
Click to collapse
Sounds like you didn't actually flash a recovery.
Sent from my Nexus 7 using Tapatalk HD
I was wondering if it did, Im using Nexus Toolkit and it acts like it does something but it didnt seem to do anything and I still get the red triangle, what can I do?
Purevulcan0 said:
I was wondering if it did, Im using Nexus Toolkit and it acts like it does something but it didnt seem to do anything and I still get the red triangle, what can I do?
Click to expand...
Click to collapse
Ditch the toolkit first of all. The best way would be to use fastboot, but Goomanager and ROM Manager can flash them from within Android.
Sent from my Nexus 7 using Tapatalk HD
if running stock, just with root, you have to rename or delete the recovery-from-boot.p file. or the stock recovery will replace your custom recovery after every boot, every time.
from twrps' site.. http://www.teamw.in/project/twrp2/103
The stock ROM*will automatically replace TWRP with the stock recovery.* To prevent the stock ROM*from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->*File Manager.* Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak.
Click to expand...
Click to collapse
I grabbed ROM Manager from the play store and flashed it, Its working thanks and whats sideload, I saw that as an option
Purevulcan0 said:
I grabbed ROM Manager from the play store and flashed it, Its working thanks and whats sideload, I saw that as an option
Click to expand...
Click to collapse
to transfer from one device to another, computer to nexus 7.
Thank all of you so much, all probably just stay stock for a few days but I'm might switch, do you guys have any recommendation of kernels and Roms?
I'd like to recommend u to see the following thread to select your 1st ROM and Kernel.
[INDEX]All In One Nexus 7 Index Thread *JAN 3rd 2013
http://forum.xda-developers.com/showthread.php?t=2070419
Regarding ROM, personally I love ParanoidAndroid because of its customizability. But as your 1st choice, how about CM10?
About Kernel, I love Franco #25 for 4.1 and #31 for 4.2. To select Kernel, pls refer to the following thread.
[GUIDE] *NEW* 4.2.1 RESULTS! N7 'Best' Kernel? (Performance & Battery Tests)
http://forum.xda-developers.com/showthread.php?p=31620793
enjoy
Ok Ive been running Motley kernel for around a day now and its amazing, but I was thinking about testing cm 10.1, but I was wondering when I factory reset and clear the data, will it erase my Nandroid backup?
Purevulcan0 said:
Ok Ive been running Motley kernel for around a day now and its amazing, but I was thinking about testing cm 10.1, but I was wondering when I factory reset and clear the data, will it erase my Nandroid backup?
Click to expand...
Click to collapse
Just do a factory reset don't erase data or however it's worded. All the same it's never a bad idea to have a Nandroid on your PC or a USB drive.
davisac said:
Just do a factory reset don't erase data or however it's worded. All the same it's never a bad idea to have a Nandroid on your PC or a USB drive.
Click to expand...
Click to collapse
How do you access the backup on the device from the computer, I didn't think you could see root directory natively
Purevulcan0 said:
How do you access the backup on the device from the computer, I didn't think you could see root directory natively
Click to expand...
Click to collapse
TWRP saves the backup to the /SD/ and I thought CWM did as well. Even if it doesn't, copy the backup from the root to the /SD/ with your tablet then transfer to the computer.
Alright cool, I just flashed CM 10.1, what kernels work with it?
Purevulcan0 said:
Alright cool, I just flashed CM 10.1, what kernels work with it?
Click to expand...
Click to collapse
In other words Im wondering if I can flash Motley Kernel, the one I had before because I really liked it
Purevulcan0 said:
In other words Im wondering if I can flash Motley Kernel, the one I had before because I really liked it
Click to expand...
Click to collapse
Disregard all of that lol, I flashed over motley on Cm10.1 and it performs beautifully
Hello everyone, this is my first post on XDA and it is about Engle_Mars' CM10.1 port for MM2 (http://forum.xda-developers.com/showthread.php?t=2128318). I have a rooted MM2 (A953) running Android 2.2 Froyo, kernel version 2.6.32.9 and I wanted to try JB on my device, I installed Droid2Bootstrap (CWMRecovery is working just fine) and got his ROM on the SD card. My questions are:
A) Even though the ROM is based on the 2.6.32.9 Kernel, will it still run on my device? I am from Argentina and I purchased my phone at Personal S.A so it's running their custom Froyo Rom (System Version: Version.3.13.0.A953.Personal.en.AR)!
B) My phone's USB port is broken and the PC won't recognize it (Yes, I have tried a bunch of USB cables and other pcs as well), having this said, if I try the installation and end up in a boot loop will I be able to recover my device without RSDLite or a PC at all?
C) I have backed up my current ROM with CWMRecovery, will I be able to restore this backup if I want to downgrade or if the installation goes wrong?
Any help is very much appreciated, I am a complete noob as far as Android is concerned so sorry if I made any stupid questions, but I couldn't find any help on Google or other Forums. Thanks in advance!
matii2639 said:
Hello everyone, this is my first post on XDA and it is about Engle_Mars' CM10.1 port for MM2 (http://forum.xda-developers.com/showthread.php?t=2128318). I have a rooted MM2 (A953) running Android 2.2 Froyo, kernel version 2.6.32.9 and I wanted to try JB on my device, I installed Droid2Bootstrap (CWMRecovery is working just fine) and got his ROM on the SD card. My questions are:
A) Even though the ROM is based on the 2.6.32.9 Kernel, will it still run on my device? I am from Argentina and I purchased my phone at Personal S.A so it's running their custom Froyo Rom (System Version: Version.3.13.0.A953.Personal.en.AR)!
B) My phone's USB port is broken and the PC won't recognize it (Yes, I have tried a bunch of USB cables and other pcs as well), having this said, if I try the installation and end up in a boot loop will I be able to recover my device without RSDLite or a PC at all?
C) I have backed up my current ROM with CWMRecovery, will I be able to restore this backup if I want to downgrade or if the installation goes wrong?
Any help is very much appreciated, I am a complete noob as far as Android is concerned so sorry if I made any stupid questions, but I couldn't find any help on Google or other Forums. Thanks in advance!
Click to expand...
Click to collapse
A) Yep, new ROMs have custom kernels running with 2ndboot, that means that the running froyo kernel get replaced with a custom jb kernel on the fly. I'd recommend you flash the bootmenu v1.1 (from here http://forum.xda-developers.com/attachment.php?attachmentid=1183672&d=1341699135 , it's a newer (v5 versus v2), permanent recovery, you flash it using the "volatile" recovery in the bootstraper)
B) Nope, but remember to wipe data/factory reset on recovery so you don't get stuck. If you can't get to the custom recovery, stock recovery can be used to wipe.
C) Yes, but it's recommended yo do another backup with the newer recovery on the bootmenu, this is because CWM 5 has a newer backup format.
Remember most of the stuff has been already discussed here on xda. Some of the stuff for the defy applies to the MS2 as well (they're almost the same hardware-wise).
Good luck, and welcome to the milestone 2's rom scene
Lean946 said:
A) Yep, new ROMs have custom kernels running with 2ndboot, that means that the running froyo kernel get replaced with a custom jb kernel on the fly. I'd recommend you flash the bootmenu v1.1 (from here http://forum.xda-developers.com/attachment.php?attachmentid=1183672&d=1341699135 , it's a newer (v5 versus v2), permanent recovery, you flash it using the "volatile" recovery in the bootstraper)
B) Nope, but remember to wipe data/factory reset on recovery so you don't get stuck. If you can't get to the custom recovery, stock recovery can be used to wipe.
C) Yes, but it's recommended yo do another backup with the newer recovery on the bootmenu, this is because CWM 5 has a newer backup format.
Remember most of the stuff has been already discussed here on xda. Some of the stuff for the defy applies to the MS2 as well (they're almost the same hardware-wise).
Good luck, and welcome to the milestone 2's rom scene
Click to expand...
Click to collapse
Thanks a lot man! Glad to know people from Argentina actually care about technology! Gracias denuevo che
Launched a new version of the ROM today, I installed it in my M2 and it was much better without the Pdroid.
How i can root it?
My milestone entered in bootloop a few days afters the roms was installed, is this normal?
tioogu said:
My milestone entered in bootloop a few days afters the roms was installed, is this normal?
Click to expand...
Click to collapse
I really don't think it's normal, but if you haven't fixed it yet maybe you can do a restore wiping the cache and the partition (something like that). Like I said, I'm new to Android, not much I can help you with, sorry.
tioogu said:
My milestone entered in bootloop a few days afters the roms was installed, is this normal?
Click to expand...
Click to collapse
wipe data! bootloop stop...
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
cubeth said:
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
Click to expand...
Click to collapse
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
taodan said:
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
Click to expand...
Click to collapse
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
cubeth said:
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
Click to expand...
Click to collapse
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
taodan said:
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
Click to expand...
Click to collapse
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
cubeth said:
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
Click to expand...
Click to collapse
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
korockinout13 said:
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for your advice, I'll try to follow it and see if it works as soon as I've got back home.
Hey guys,
I've known about this whole modding thingy going on for android phones, and i've decided to give it a shot myself.
I took a backup of everything (copied everything.. didn't use any app for that. not too smart of me..)
Anyway,
I looked around and decided to install Hells Core kernel on my phone, along with Cyanogen Mod.
So after installing the SDK on my computer, unlocking the phone, rooting the phone with SuperSU and Clockwork Mod,
I got to installing the kernel.
I put it on my phone, rebooted into recovery mode, reset all data (dalvik cache and all..)
then I installed the kernel from a zip file I put on the phone, and it all went smoothly.
However, when I reboot my phone - it's all messed up!
The screen is all half yellow, and half is just black - not even text.
In the yellow part, you can hardly tell that it's the first welcome screen - because the text is too big to fit the screen.
Anyway, the whole phone is fk3d up.
I just wanna put it back to the original stock kernel and rom...
How do I do that now?
Thanks a lot guys..
This is urgent >_<
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
jd1639 said:
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
Click to expand...
Click to collapse
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
capzul said:
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
Click to expand...
Click to collapse
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
hassi4042 said:
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
Click to expand...
Click to collapse
Well, I flashed the kernel before I put the ROM, so this happened with HC kernel on stock ROM.
:X
you probably flashed the wrong version of the kernel
You did get the CM Version of Hells Core, right?
This happens to me all the time, just reflash the Roms .zip and you'll be fine.
Sorry to say that, but from your comments it's obvious that you messed up with wrong kernel's version and is not a fault of this specific kernel.
Also the zero kb downloads show bad downloads on your side again.
Sent from my ONDA A9 Core4
capzul said:
Hey guys,
I've known about this whole modding thingy going on for android phones,
Click to expand...
Click to collapse
Lol
Sent from my Nexus 4 using Tapatalk