Database Users

MultiROM 10.0.0 Problem

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

Stuck at google logo, recovery mode doesn't work?

I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.

calavera-pw said:
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
Click to expand...
Click to collapse
before you do anything, use your recovery to see if the rom zip is located in /data/media/0/. if its there, flash it from that location.

Are you able to boot into recovery?
If yes, it could be as simple as plugging your tablet into the computer and mounting the usb, drag and drop the rom, and flash it without using a toolkit (only recovery). I'm not familiar with jrom flasher, but i will say the more variables there are, the more chance of a problem.
If no, you're best off running the stock factory image through your computer, found here: https://developers.google.com/android/nexus/images#nakasi. I had your problem at one point, and could not even boot into recovery. After trying to install cwm through adb (which failed), and a number of toolkits, the factory image was what brought my nexus back to life.
I remember reading that sometimes a wipe can delete your recovery as well as your system (and whatever else you have on your n7), although i dont know if that was ever fixed, as i got my tab replaced a month or two ago and havent rooted it again yet. There was some type of command or .zip or something that should be used to keep recovery after wipes. When i expirienced problems such as yours, it was also from a bad wipe from a toolkit. Using just the recovery afterwards, i never expirienced any issues, even without the recovery fix.
I would definitely try simms suggestion first if you can access recovery. If that fails, try one of the above processes.
PS, even if you can access recovery, if at this point you just want to go completely stock, the factory image will work regardless.
cheers

Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.

calavera-pw said:
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
Click to expand...
Click to collapse
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:

appoos said:
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
Click to expand...
Click to collapse
ADB
Sent from my Galaxy Nexus

Pirateghost said:
ADB
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This dint work in my windows 8

appoos said:
This dint work in my windows 8
Click to expand...
Click to collapse
You're holding it wrong. ADB works on my Win8 machine

Pirateghost said:
You're holding it wrong. ADB works on my Win8 machine
Click to expand...
Click to collapse
can you tell me the procedure..

appoos said:
can you tell me the procedure..
Click to expand...
Click to collapse
no.
in the other thread that YOU created, you were given links to follow and the instructions are already there. i dont hold hands

I could do it with ADB..thanks guys

N8000 Native Linux Thread

The Note 10.1 as a device, is very capable of running Linux ARM at high speeds. Like the TF700, an effort exists to have a fully functional OS on our devices (http://forum.xda-developers.com/showthread.php?t=2070139) however the recent development has been slow after the developer abandoned the project. The little documentation we do have is limited, (http://thermatk.github.io/opensgn-easy/), and is only focused on Arch. The OS itself is functional but unusable as it often crashes. Kali also exists but really requires no work as it is stable enough for pentesting and is not intended as a general use platform.
Scope of the thread: provide a focused go to source for information related to the development of a better kernel for Linux, and the porting of different distros to the Note 10.1.
Current progress: bootable Arch Linux system with support for sound, WiFi, BT, touchscreen, wacom digitizer, partial GPU acceleration, charging, usb otg, battery. Not stable.
Goal: fully functional Linux distros on the note 10.1, with updates as needed.
Why is this posted in the Android dev section?
Whatever drivers we are missing, since they simply aren't existent on Linux can be ported. The general area does not give this project the necessary attention. This is groundbreaking really, not many tablets are able to run Linux, not even the nexus 10 (yet). With Linux this tablet really gets what it deserves and becomes a great multimedia platform.

Looking forward to your progress.
Sent from my GT-N8000 using Tapatalk HD

Djinn Moto said:
Looking forward to your progress.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
I have not gone far, that is the issue. I can set up a bootable Debian distro, but I can't get framebuffer to work. This results in a blank screen. Any advice?

Not DualBoot, but really working thing!
So, i've follow this tutor and after first boot in linux my tablet won't booting back to android. What i did? I've flash recovery.img into boot partition and now i have working recovery and opportunity to flash different boot images. So, what we need? I've attached two files: boot_linux.zip and boot_android.zip. You sould extract boot.img from zip of your ROM and place it into boot_android.zip. If you flash boot_linux.zip, tablet will be boot in linux (linux.img, placed on internal sd (if you use android 4.2 you must place this image in /data/media), if boot_android.zip - android.
Thank you for your attention and sorry my eng. Good luck!

xxxTy3uKxxx said:
So, i've follow this tutor and after first boot in linux my tablet won't booting back to android. What i did? I've flash recovery.img into boot partition and now i have working recovery and opportunity to flash different boot images. So, what we need? I've attached two files: boot_linux.zip and boot_android.zip. You sould extract boot.img from zip of your ROM and place it into boot_android.zip. If you flash boot_linux.zip, tablet will be boot in linux (linux.img, placed on internal sd (if you use android 4.2 you must place this image in /data/media), if boot_android.zip - android.
Thank you for your attention and sorry my eng. Good luck!
Click to expand...
Click to collapse
Did you create a different image or did you use the included Arch Linux? If you made your own could you post the partition image or .img? Also, Linux should boot only when you hold the volume up key and power since the recovery partition which contains the kernel is booted then. Thanks for the script regardless, it can be a better solution to people who wish to boot Linux exclusively (which i dont wish to, yet).
Sent from my GT-N8013 using xda app-developers app

It`s included img. I know about recovery, but it`s not working for me - after first boot i can`t boot in android.

xxxTy3uKxxx said:
It`s included img. I know about recovery, but it`s not working for me - after first boot i can`t boot in android.
Click to expand...
Click to collapse
Did you by chance select reboot into recovery when you were in Android? It sets a recovery flag that Linux can't remove, so it constantly tries to boot back to recovery.
Use ODIN to flash CWM or TWRP and you'll be able to get back to Android with no problems.

darksabre_x said:
Did you by chance select reboot into recovery when you were in Android? It sets a recovery flag that Linux can't remove, so it constantly tries to boot back to recovery.
Use ODIN to flash CWM or TWRP and you'll be able to get back to Android with no problems.
Click to expand...
Click to collapse
Good catch. I never experienced that because I'm on stock rom rooted and don't have advanced reboot menu.
Sent from my GT-N8013 using xda app-developers app

Also is anybody willing to create a functional ubuntu image? I've made progress with linux deploy and can install through vnc most programs (even chromium succeeded and runs), but again, no framebuffer when I try to boot it natively. I am not great with Linux, and as a result when I've tried to compile the recovery and modules from the GitHub source, I've failed. Many thanks to whoever attempts this.
As a heads up, don't bother with Debian, dependencies are messed up. Half of the things I attempt to apt-get don't have an install candidate or dependencies are missing... Possibly a bad repo is causing this? Dunno.
Sent from my GT-N8013 using xda app-developers app

Linux on Note 10.1 abandoned???
Sent from my Nexus 4 using xda app-developers app

[Q] Need some help urgently - backed into a corner while flashing a new rom

So this evening decided to go back to CM11 after using stock for a while on my N4. So I downloaded the latest CM11 nightly, along with the latest PA gapps. I did a full wipe in recovery, then flashed CM11, followed by a flash of the gapps. However, it immediately appeared that the gapps file must have been bad (gave me the red exclamation triangle android background). So rebooting leaves me in a endless bootloop. Only problem is I don't have another gapps file saved on my SDcard. And to make matters worse (yeah I know) I didn't nandroid my system prior to this, though I do have everything (apps, etc) saved on my SDcard. Now my problem is, I need to find a way of loading a new gapps file onto my phone. I have tried ADB, but I suspect that as a result of the factory reset I no longer have USB debugging on, as I can't connect to the device in ADB. I am becoming more than a little stressed right now, as I need to get this phone back up and running. Does anyone have any idea what I might do next?? I am not a total newbie to flashing roms, been at it a few years now, but this is the first time I've been stuck like this. Ugh! Please help! :crying::crying::crying:

joeski27 said:
So this evening decided to go back to CM11 after using stock for a while on my N4. So I downloaded the latest CM11 nightly, along with the latest PA gapps. I did a full wipe in recovery, then flashed CM11, followed by a flash of the gapps. However, it immediately appeared that the gapps file must have been bad (gave me the red exclamation triangle android background). So rebooting leaves me in a endless bootloop. Only problem is I don't have another gapps file saved on my SDcard. And to make matters worse (yeah I know) I didn't nandroid my system prior to this, though I do have everything (apps, etc) saved on my SDcard. Now my problem is, I need to find a way of loading a new gapps file onto my phone. I have tried ADB, but I suspect that as a result of the factory reset I no longer have USB debugging on, as I can't connect to the device in ADB. I am becoming more than a little stressed right now, as I need to get this phone back up and running. Does anyone have any idea what I might do next?? I am not a total newbie to flashing roms, been at it a few years now, but this is the first time I've been stuck like this. Ugh! Please help! :crying::crying::crying:
Click to expand...
Click to collapse
Nobody has a suggestion? This isn't looking good...
What is strange to me is, even after doing another factory reset, it still boots to the same CM boot screen and is stuck in a boot loop. I have no idea what is going on here. And at the very least, at least I have everything still on my SDcard (backups of apps in TB, and all my other locally saved stuff...just that now I have no idea of how to get to any of it, or how to load on a working rom & gapps so I can have something to boot to!)

Do a full wipe, flash CM11 without Gapps. It should boot but you won't be able to sign in to google and all that jazz. Just use the browser and download another gapps, then flash it.
Your computer won't detect ADB because ADB is only when android is running. If you're running a sideload-enabled recovery, you can push a zip and flash it through ADB.

exb0 said:
Do a full wipe, flash CM11 without Gapps. It should boot but you won't be able to sign in to google and all that jazz. Just use the browser and download another gapps, then flash it.
Your computer won't detect ADB because ADB is only when android is running. If you're running a sideload-enabled recovery, you can push a zip and flash it through ADB.
Click to expand...
Click to collapse
I've tried this now (wipe, and then flash of CM) and its STILL stuck at the damn CM boot animation. I just don't understand what the problem is here. I have never, ever had something like this happen before. Could it be a bad nightly? And if so, how the hell am I going to get another flashable rom onto my SDcard??

joeski27 said:
I've tried this now (wipe, and then flash of CM) and its STILL stuck at the damn CM boot animation. I just don't understand what the problem is here. I have never, ever had something like this happen before. Could it be a bad nightly? And if so, how the hell am I going to get another flashable rom onto my SDcard??
Click to expand...
Click to collapse
Hmmm, yeah it could be.
1 : Download a ROM. Check the MD5 checksum.
2 : Copy the ROM to your ADB folder and rename it to something easy (eg: Rom.zip)
3 : Fire up CMD, Navigate it to your ADB folder
4 : Boot your phone into recovery, find for a function called "ADB Sideload" or something along those lines.
5 : In CMD, type in "adb sideload *romname*.zip
6 : ??
7 : Enjoice.
This can be done for any type of flashable files.
or yknow. just return back to stock and do everything all again if you're uncomfortable doing this.

exb0 said:
Hmmm, yeah it could be.
1 : Download a ROM. Check the MD5 checksum.
2 : Copy the ROM to your ADB folder and rename it to something easy (eg: Rom.zip)
3 : Fire up CMD, Navigate it to your ADB folder
4 : Boot your phone into recovery, find for a function called "ADB Sideload" or something along those lines.
5 : In CMD, type in "adb sideload *romname*.zip
6 : ??
7 : Enjoice.
This can be done for any type of flashable files.
or yknow. just return back to stock and do everything all again if you're uncomfortable doing this.
Click to expand...
Click to collapse
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...

joeski27 said:
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
Click to expand...
Click to collapse
Ah, it shouldn't matter that much. Instead of CMD just use terminal(that's what it's called in OSX right?).
didn't work? what error did you get?

joeski27 said:
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
Click to expand...
Click to collapse
Yeah its not working, just brings up the splash of command prompts that comes up with you don't enter a proper adb command.

joeski27 said:
Yeah its not working, just brings up the splash of command prompts that comes up with you don't enter a proper adb command.
Click to expand...
Click to collapse
Enable sideload on your phone and then try using "adb devices", do you get anything? or random splash of commands again?

exb0 said:
Enable sideload on your phone and then try using "adb devices", do you get anything? or random splash of commands again?
Click to expand...
Click to collapse
No that's what I've been countering the whole time; I have ADB sideload set on the phone, and then after cd'ing my way to the folder with adb, I try "adb devices" and nothing, doesn't see the device at all. WTF?

joeski27 said:
No that's what I've been countering the whole time; I have ADB sideload set on the phone, and then after cd'ing my way to the folder with adb, I try "adb devices" and nothing, doesn't see the device at all. WTF?
Click to expand...
Click to collapse
sounds like a driver issue. You're gonna have to fix that or there's almost no way of fixing your phone :/

Hang on....sideload looks like its working! But I ain't out of the woods yet, won't celebrate til it gets there, AND if it boots...

Now I guess the best bet is to try a fresh rom rather than a fresh gapps, would you say? I'm downloading both now, just wondered which would be my best bet. I mean at this point I just need something that will allow me to boot.'
By the way when a sideload is performed where is the sideloaded file saved? Just wondering where to find it when the time comes to flash.

joeski27 said:
Hang on....sideload looks like its working! But I ain't out of the woods yet, won't celebrate til it gets there, AND if it boots...
Click to expand...
Click to collapse
#prayforjoeski27 goodluck!
---------- Post added at 05:38 AM ---------- Previous post was at 05:37 AM ----------
joeski27 said:
Now I guess the best bet is to try a fresh rom rather than a fresh gapps, would you say? I'm downloading both now, just wondered which would be my best bet. I mean at this point I just need something that will allow me to boot.
Click to expand...
Click to collapse
try flashing a rom without gapps first. if the rom boots then wipe and reflash rom with gapps.

exb0 said:
#prayforjoeski27 goodluck!
---------- Post added at 05:38 AM ---------- Previous post was at 05:37 AM ----------
try flashing a rom without gapps first. if the rom boots then wipe and reflash rom with gapps.
Click to expand...
Click to collapse
Sounds like a plan. This time I'm loading the latest snapshot release of CM rather than the damn nightly, lol. At least we know that that version *should* reliably boot up....and we'll know shortly...going to save the rom to the appropriate folder, rename, and sideload....

joeski27 said:
Sounds like a plan. This time I'm loading the latest snapshot release of CM rather than the damn nightly, lol. At least we know that that version *should* reliably boot up....and we'll know shortly...going to save the rom to the appropriate folder, rename, and sideload....
Click to expand...
Click to collapse
I think all nightlies should boot up (i mean it IS cyanogen mod...). I think you just got a bad download. Remember to check MD5 if it's available!

exb0 said:
I think all nightlies should boot up (i mean it IS cyanogen mod...). I think you just got a bad download. Remember to check MD5 if it's available!
Click to expand...
Click to collapse
WOO HOO! Friggin thing booted, baby! Hello CM welcome screen! Never looked so beautiful!
So now I just need to 1) get a fresh gapps, 2) load it on to my SD via android file transfer, do a fresh wipe in recovery, flash CM again, followed by the fresh gapps, and I should be in business...yes?

joeski27 said:
WOO HOO! Friggin thing booted, baby! Hello CM welcome screen! Never looked so beautiful!
So now I just need to 1) get a fresh gapps, 2) load it on to my SD via android file transfer, do a fresh wipe in recovery, flash CM again, followed by the fresh gapps, and I should be in business...yes?
Click to expand...
Click to collapse
Congrats!
You can try just flashing gapps on top of it, that's what I do. but if you're worried you can do a full wipe and flash it again. Completely up to you!

exb0 said:
Congrats!
You can try just flashing gapps on top of it, that's what I do. but if you're worried you can do a full wipe and flash it again. Completely up to you!
Click to expand...
Click to collapse
Hey thanks a million for the help on this one! Like I said, I've done quite a bit with rom tinkering over the last few years, but sideloading was a first for me tonight. Though it is very good to know for the future! More importantly, however (and this is really not like me) in the future I either A) have to make sure I have enough SD space for nandriods, or B) keep a previous, working zip of a rom on the SD when I go to flash a new one (which is what I have always done but have not recently).
Again, thanks a bunch!!!! :highfive:

joeski27 said:
Hey thanks a million for the help on this one! Like I said, I've done quite a bit with rom tinkering over the last few years, but sideloading was a first for me tonight. Though it is very good to know for the future! More importantly, however (and this is really not like me) in the future I either A) have to make sure I have enough SD space for nandriods, or B) keep a previous, working zip of a rom on the SD when I go to flash a new one (which is what I have always done but have not recently).
Again, thanks a bunch!!!! :highfive:
Click to expand...
Click to collapse
No problem as long as you're willing to learn I'm willing to help! if you ever run into any other problems feel free to PM me. I'll try to help as much as I can. :good:

[Q] Installed kernel, phone is f*cked up...

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