Database Users

HELP! Odin and Heimdall won't work... Alternative to flash to stock?

First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
EDIT:
I have TWRP 2.5.0.3 on my phone

sebbo1 said:
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
Click to expand...
Click to collapse
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot

Colonel Sanders said:
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Click to expand...
Click to collapse
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.

sebbo1 said:
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
Click to expand...
Click to collapse
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.

Colonel Sanders said:
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Click to expand...
Click to collapse
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?

sebbo1 said:
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
Click to expand...
Click to collapse
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.

Colonel Sanders said:
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Click to expand...
Click to collapse
Are you talking about slimroms.net? If you are, which addons do I download?
EDIT: nevermind. I downloaded the AIO (all in one)

sebbo1 said:
Are you talking about slimroms.net? If you are, which addons do I download?
Click to expand...
Click to collapse
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.

Colonel Sanders said:
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Click to expand...
Click to collapse
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website

sebbo1 said:
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
Click to expand...
Click to collapse
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.

Colonel Sanders said:
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Click to expand...
Click to collapse
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?

sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I would say so myself, Odin back to stock, but since you have a mac and I'm not sure if Heimdall support the S4 try this:
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Format /data
Format /internal (If CWM-based recovery)
Flash ROM, addons, reboot

sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen

sebbo1 said:
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
Click to expand...
Click to collapse
That means the battery is low... Charge it up some... Check your PM for my gmail if you need some help, posting back and forth can take a while.

Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore

sebbo1 said:
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
Click to expand...
Click to collapse
Glad you got it going man, and enjoy Slim, it's hands down the best ROM there is if you prefer minimal with tons of customization options.

[Q] Wiping didn't work, messed up restore - now can't boot into TWRP

First time flashing CM, and I may have messed up.
I rooted, installed TWRP, everything went perfect. I made a backup, and then tried to do a factory wipe. The wipe ended with the messages "unable to mount /system", "... /cache" and another one. I still tried to flash, and it just immediately got stuck, nothing happened. I rebooted, and everything worked fine. It was the Samsung stock image and all my apps were still there. I'm assuming it just didn't wipe at all.
I then went full retard mode, and tried to do a restore. I wanted to be sure my phone wouldn't fail on me in the recent future because some random stuff may have been partially wiped or something. Feel free to tell me I have the IQ of a chimp.
This completely messed things up, as it just got stuck at "Restoring System...". Eventually I restarted it with the power button. Now it can't boot normally, it can't boot into recovery mode, which just leaves download mode.
Any way I can fix this and subsequently install CM properly? I'm using TWRP 2.6.3.0. I've been told it's recommended to use 2.5, as the other version may have some issues (including not being able to recognize partitions). Only download mode still seems to work, so maybe there's a way to flash my phone back into the living world?
Versions:
Team Win Recovery Project 2.6.3.0
CyanogenMod 10.1.3 (RC2 jfltexx)
Thanks!

No idea really but maybe try to flash default rom/recovery etc with odin?

I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Sent from my GT-I9505 using XDA Premium 4 mobile app

HANDSY said:
I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Click to expand...
Click to collapse
I got the Samsung stock ROM of july, flashed it using download mode, and everything was back! I then rooted it again, and installed CMW (see versions below). I went into recovery, and tried to do a backup. It told me it failed: "Error while making a backup image of /data!". I then wondered if it may have been due to a lack of storage (which could very well be, as that was the issue before and the old backup by Teamwin was probably still on it somewhere), so I rebooted my phone. That's when it just failed and kept showing the Samsung logo at boot. I tried flashing my ROM again, again the logo. Then I did a factory reset using the regular recovery (cache and data reset), which fixed it. Now all my apps and data are gone, but that's no problem.
I'm back at the unrooted Samsung stock image now. Any ideas what I did wrong? These were the versions I used:
CF-Auto-Root-jflte-jfltexx-gti9505
i9505-cwm-recovery-6.0.3.2(0611)
Odin3 v3.07
I did nothing more than root, install CMW, try a backup and then it all went to ****. I'm surprised a backup can even do that.

Mmm I'm not too familiar with the internal workings of backups. Perhaps something was corrupted during flashing? Glad to hear that you have got your phone working again. There is an updated version of CMW somewhere in the original development thread.
Sent from my GT-I9505 using XDA Premium 4 mobile app

i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.

Chillzone said:
i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.
Click to expand...
Click to collapse
I tried CMW 6.0.3.6 and the Google Play 4.3 ROM as you said, and it works perfectly! I didn't try a backup this time, as it didn't exactly have anything to back up anymore.
Finally my precious vanilla Android again, I missed it since I switched from my Galaxy Nexus to my S4. Thanks a lot guys!
Edit: I do seem to be having one issue. Quite frequently after it's booted, and I enter the SIM pin, the message "Unlocking SIM card..." stays there indefinitely. I can use the phone but the message covers everything up. This doesn't always happen, but quite often. I've read some ROMs can't handle SIM lock, like CM. This is a Google Play edition, however. Is it normal that this doesn't work?
I can seem to fix it by holding the power button, and choosing "Unlock SIM" from the menu. I guess it's not that bad as I don't often reboot my phone.

Can´t boot nexus 4- blue screen problem

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.

[Q] soft bricked ls980

so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.

omega52390 said:
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
Click to expand...
Click to collapse
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?

XxZombiePikachu said:
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
Click to expand...
Click to collapse
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
edit hang on ive got a 10.2 nightly and jb gapps i might have something here will report shortly... nvm i think... it locks up saying "using legacy property environment for update-binary...please upgrade to latest binary"

omega52390 said:
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
Click to expand...
Click to collapse
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup

XxZombiePikachu said:
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
Click to expand...
Click to collapse
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.

omega52390 said:
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
Click to expand...
Click to collapse
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm

XxZombiePikachu said:
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
Click to expand...
Click to collapse
thats the thing i've only ever had trouble with adb coudl never wrap my head around it let alone get it to work

w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD

omega52390 said:
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
Click to expand...
Click to collapse
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

XxZombiePikachu said:
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
for some reason cm is still failing to load im going to try installing cm then putting on furnace kernel
edit i remember and succeeded in recreating my secret recipe. first i have an old twrp and 10.2 unofficial nightly thats where i am now. next ill put on a new CWM philz and try putting my CM backup on

another update i finally got my cm 11 backup running however it appears there is damage to the install from back when i made the backup do you know of anyway of repairing an install w/o having to do a reset? really the only noticable problem right now is that i can't use any live wallpapers :/

[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