As the title says, I installed the wrong kernel when trying to root my phone... and now my phone wont boot
unfortunatly I don't know which kernel version I originally had so I'm a little worried that I'll have to spend all night trying every possible kernel version until it boots...
Can anyone suggest an easier way? is there a universal kernel that will get me at least to the menu section?
thanks for looking guys
Can you boot into Download mode? If so, which Android version are you on right now?
Yeah I can boot into download mode and I'm running version 4.1.2
I'm downloading I9100XWLSD_I9100MOBLSC_MOB.zip which I think is the original ROM and I'm hoping it comes with the original kernel as well...
I should just flash them both with odin right?
EDIT: download finished and I'm a little confused, there's 2 files within it
I9100XWLSD_I9100MOBLSC_I9100BULS1_HOME.tar.md5 and SS_DL.dll
I really have no idea what to do with these... do I remove the .md5 extension and unzip the .tar? help :S
booboob31 said:
Yeah I can boot into download mode and I'm running version 4.1.2
I'm downloading I9100XWLSD_I9100MOBLSC_MOB.zip which I think is the original ROM and I'm hoping it comes with the original kernel as well...
I should just flash them both with odin right?
EDIT: download finished and I'm a little confused, there's 2 files within it
I9100XWLSD_I9100MOBLSC_I9100BULS1_HOME.tar.md5 and SS_DL.dll
I really have no idea what to do with these... do I remove the .md5 extension and unzip the .tar? help :S
Click to expand...
Click to collapse
Yup, that should set things right.
BTW, which kernel did you flash?
immortalneo said:
Yup, that should set things right.
BTW, which kernel did you flash?
Click to expand...
Click to collapse
It was XWKDD_insecure.tar
booboob31 said:
It was XWKDD_insecure.tar
Click to expand...
Click to collapse
If you're interested in a little tinkering, you could try flashing Siyah v6 beta 5 kernel via odin, and see if your phone boots up. Siyah v6 supports JB 4.1.2, and it will replace your current kernel. So, theoretically, your phone should boot back up.
Maybe it was already clear, but just flash the Siyah kernel first, before you try flashing a whole rom. Flashing Siyah might solve the whole problem, and you will have root access afterwards.
Donnie Sins said:
Maybe it was already clear, but just flash the Siyah kernel first, before you try flashing a whole rom. Flashing Siyah might solve the whole problem, and you will have root access afterwards.
Click to expand...
Click to collapse
Yeah that's what I did Donnie and it worked a charm, thanks to both you and immortalneo. :highfive:
Just to confirm I can go ahead and install any rom now without fear of the "superbrick" bug? or would I still need to source an insecure kernel first?
Thanks again, it's a load off my mind
booboob31 said:
Yeah that's what I did Donnie and it worked a charm, thanks to both you and immortalneo. :highfive:
Just to confirm I can go ahead and install any rom now without fear of the "superbrick" bug? or would I still need to source an insecure kernel first?
Thanks again, it's a load off my mind
Click to expand...
Click to collapse
No problem, good for you.
This brickbug can only appear in stock 4.0.4 recovery, so you are safe.
You can try to flash other kernels (.zip files) as well through CWM. But pay attention that you search for the right ones, that are made for your device and your Android version.
Related
So.. forgive my ignorance, but I installed the leaked update for the skyrocket last night and was able to just flash a cwm tar with only recovery in it and then superuser to root. I take it thats impossible with the i777?
sulpher said:
So.. forgive my ignorance, but I installed the leaked update for the skyrocket last night and was able to just flash a cwm tar with only recovery in it and then superuser to root. I take it thats impossible with the i777?
Click to expand...
Click to collapse
Give it a little time. Should be soon.
It hasn't been posted, but it has been.
No not me, I am sticking with my base, too lazy to restart and haven't found a reason why to change.
Hmm worked for the skyrocket ics leak... cant be including a GB kernel with it or id bootloop? And skyrocket has no cwm with ics kernel...
sulpher said:
Hmm worked for the skyrocket ics leak... cant be including a GB kernel with it or id bootloop? And skyrocket has no cwm with ics kernel...
Click to expand...
Click to collapse
skyrocket has separate recovery partition.....their CWM isnt injected into kernel....
Pirateghost said:
skyrocket has separate recovery partition.....their CWM isnt injected into kernel....
Click to expand...
Click to collapse
Ah okay, what i was wondering. Thank you.
sulpher said:
So.. forgive my ignorance, but I installed the leaked update for the skyrocket last night and was able to just flash a cwm tar with only recovery in it and then superuser to root. I take it thats impossible with the i777?
Click to expand...
Click to collapse
A few people have been able to root it with odin mobile. The question is how to get CWM recovery into that new leak.
sam1forever said:
A few people have been able to root it with odin mobile. The question is how to get CWM recovery into that new leak.
Click to expand...
Click to collapse
Install Entropy's kernel with Odin, or Mobile Odin. He's posted his updates several times, but I don't remember where I saw them. You could just extract them from one of the Samsung ICS roms around here.
EDIT: Looks like recovery isn't possible with the leak, due to Entropy getting call audio to work before the leak. You'd have to stay with the stock leak kernel, which means Odin'ing back to stock, then cwm kernel, then nandroid restore if you want to get back. You could probably use Mobile Odin to load the back-to-stock + root package, and load a CWM kernel all in one flash . See the below, quoted post from him.
Entropy512 said:
Source doesn't really matter - I9100 trees basically fully support I777 at this point, there is almost no difference. There's a good chance it'll mostly work, just like a single kernel worked for I777 and I9100 bases in the Gingerbread days.
However, call audio won't work though due to the libaudio workaround. I have no intention of turning this off or doing dual-builds with two different defconfigs for a leak. When official ICS comes around I'll look into other options.
Firmware developers could do a "reverse Hellraiser" with libaudio, but since there's no NFC I have no interest in the leak. UC bases suck - when ICS came out I was damn close to declaring UC bases supported for my Gingerbread kernel because only those on UC bases seemed to have stability problems starting with the I9100 update3 source merge (which made I9100 bases awesome.)
. . .
Click to expand...
Click to collapse
Man this sucks. I am now stuck with UCLC2. So there is no way for now that we can root this version of ICS and have a CWM?
brokebackamigo said:
Man this sucks. I am now stuck with UCLC2. So there is no way for now that we can root this version of ICS and have a CWM?
Click to expand...
Click to collapse
WOW.
So you bring up a two day old thread...then assume the information in it is current...and decide not to read ANY of the more up-to-date threads in these forums that have to do with rooted ICS? Go read.
mattdm said:
WOW.
So you bring up a two day old thread...then assume the information in it is current...and decide not to read ANY of the more up-to-date threads in these forums that have to do with rooted ICS? Go read.
Click to expand...
Click to collapse
Your comment did not really help me, but yeah I found my answer hiding in this clutter of useless comments. The answer to my question was NO.
brokebackamigo said:
Your comment did not really help me, but yeah I found my answer hiding in this clutter of useless comments. The answer to my question was NO.
Click to expand...
Click to collapse
Just odin a kernel with CWM and then flash the rom task posted. It has both root and CWM. If you read up you would know this.
brokebackamigo said:
Your comment did not really help me, but yeah I found my answer hiding in this clutter of useless comments. The answer to my question was NO.
Click to expand...
Click to collapse
Ok, if you want to have a rooted version of the UCLC2 leak, here are the steps:
1. Download Odin on your PC.
2. Use it to flash back to stock. This will reset your bootloaders to the old ones.
3. If you use the ROM in that thread, it will already have root access. Download Mobile Odin from the Market.
4. Use Mobile Odin to flash a CWM enabled kernel.
5. Use CWM Recovery to flash the rooted UCLC2 leak.
Done. All this information was already posted before you posted in this thread; all you had to do was go find it.
Thanks for the tip. I had already tried those steps. The only thing I was doing wrong was that I wasn't wiping anything before I flashed thru odin. I was stuck with the Google app framework error. Thanks again.
Cheers.
Sent from my SGH-I777 using XDA
Pirateghost said:
skyrocket has separate recovery partition.....their CWM isnt injected into kernel....
Click to expand...
Click to collapse
Thanks for that nuggit of info you just saved me some time.
Are you a Skyrocket user?
Im currently trying to service ICS leak on both varriants
Phatboyj420 said:
Thanks for that nuggit of info you just saved me some time.
Are you a Skyrocket user?
Im currently trying to service ICS leak on both varriants
Click to expand...
Click to collapse
i had a skyrocket for a bit, but found little time to maintain a rom for it, so i sold it.
brokebackamigo said:
Thanks for the tip. I had already tried those steps. The only thing I was doing wrong was that I wasn't wiping anything before I flashed thru odin. I was stuck with the Google app framework error. Thanks again.
Cheers.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
I have the same error when i try and flash back to stock, i cant get past the activation screen. Please help me im stuck on sgh i777 uclc2 leak and cant get off cause i dont have root.
If you follow the instructions in the back to stock thread exactly, you should be able to do it.
Hey there!
So I've read a bit lately on rooting my S2 and what not (as I decided to give it a go), and after flashing CWM Touch to my S2 I loved it and found it so much easier to install ZIP's and what not. However, on boot it disappeared, then to find that it was only a temporary Flash and when I rebooted the phone, it simply reverted back to the normal CWM.
Now before asking me to use Google or search for a thread, by god I did that. And after looking for almost 2 hours, I found nothing that gave me a definite answer whether it was possible or not. And so this is why I'm creating a thread.
So is it possible to flash CWM touch on my S2 permanently (like other phones have), or do I have to stick with the volume/power button edition.
Thanks everyone! And thanks in advance.
The recovery, it's part of the kernel so which ever version of ClockworkMod the kernel shipped with that will always be there. If you really want touch recovery, you can flash Siyah Kernel and you'll be rooted and have its touch recovery.
Sent from my GT-I9100 using Tapatalk 2
nicholas1520 said:
The recovery, it's part of the kernel so which ever version of ClockworkMod the kernel shipped with that will always be there. If you really want touch recovery, you can flash Siyah Kernel and you'll be rooted and have its touch recovery.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Hmm I hoped that wasn't the case.
But isn't there a way to use ODIN3 to flash the kernel with a custom recovery, such as the CWM touch?
Sorry if that sounds stupid, I just am new to all this.
Not sure if you are allowed to bump this or not, but I just did.
Really want to know if it is possible to flash CWM touch on the kernal guys!
xxshabsxx said:
Not sure if you are allowed to bump this or not, but I just did.
Really want to know if it is possible to flash CWM touch on the kernal guys!
Click to expand...
Click to collapse
Why don't you just keep a touch cwm.zip file in your download folder and flash that after you flash a new rom?
Sent from my GT-I9100 using xda premium
kilometers4 said:
Why don't you just keep a touch cwm.zip file in your download folder and flash that after you flash a new rom?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks for the reply.
And I do have the CWM touch zip in my internalSD but there isn't and point flashing it if everytime I reboot the phone and it goes back to the stock kernel.
I just want to know if there is a method possible to flash CWM touch into the kernel, and make it permanent, or at least fine a .tar version of it so I can flash it using odin
Once again I'll bump this.
Does no one have a solution at all?
xxshabsxx said:
Once again I'll bump this.
Does no one have a solution at all?
Click to expand...
Click to collapse
Edited. Sorry, I re-read the thread. As already stated, you'll need to flash a kernel that has the version of recovery you want. If you want a different version of recovery with a specific kernel, you'll need to start making your own kernels.
ctomgee said:
Edited. Sorry, I re-read the thread. As already stated, you'll need to flash a kernel that has the version of recovery you want. If you want a different version of recovery with a specific kernel, you'll need to start making your own kernels.
Click to expand...
Click to collapse
Well I cannot find a .tar version of CWM touch so I guess I won't be able to flash the kernel.
xxshabsxx said:
Well I cannot find a .tar version of CWM touch so I guess I won't be able to flash the kernel.
Click to expand...
Click to collapse
It's in the kernel. Check out RedPill. It has touch recovery.
ctomgee said:
It's in the kernel. Check out RedPill. It has touch recovery.
Click to expand...
Click to collapse
Hmm I saw RedPill but wasn't a fan of it, I really do like CWM
Does anyone know if there is a kernel that has CWM touch in it? For CM10 preferably.
xxshabsxx said:
Hmm I saw RedPill but wasn't a fan of it, I really do like CWM
Does anyone know if there is a kernel that has CWM touch in it? For CM10 preferably.
Click to expand...
Click to collapse
Why don't you just look at the kernels in the development section, specifically for one with touch recovery? You could have found all the available options and tried them out by now.
Or are you just being lazy?
ctomgee said:
Why don't you just look at the kernels in the development section, specifically for one with touch recovery? You could have found all the available options and tried them out by now.
Or are you just being lazy?
Click to expand...
Click to collapse
No I'm not lazy, sorry if I came across that way. I am usually one to simply find something on my own, but for this I simply cannot.
I've looked and cannot find what I asked for in the OP, and am still looking and found nothing. So I simply asked a question to make sure that there isn't a possibility that it can be done.
Anyway it doesn't seem possible at the moment, so I guess I'll wait.
Hey everyone,
Sorry if the Answer was staring me in my face but I'm not sure about upgrading to the CyanogenMod because of the superbricking I might get..
If any help can be given as to whether I am safe to do it, it will be much appreciated, My android version is 4.0.4, Build number imm76D.XWLPT.
I have just rooted it with XWLPW-ROOT-CWM6, and It seems to have rooted fine.
Will be much appreciated if I can get any help as to whether I can Flash it with CyanogenMod and everything will be fine..
Thanks again
EDIT: Yeah I just realized about having the Superbrick bug, I must have a kernel that is not liable to bricking, I rooted it with PhilZ touch 3 and when I go into recovery mode it says CWM Base version: 6.0.1.8 at the bottom, Am I safe from the bug?
You're safe as long as you don't perform a wipe from stock recovery in 4.0.4 (and not all phones have an insane chip). So yes, you can flash CM.
Sent from the Matrix
Donnie Sins said:
You're safe as long as you don't perform a wipe from stock recovery in 4.0.4 (and not all phones have an insane chip). So yes, you can flash CM.
Sent from the Matrix
Click to expand...
Click to collapse
Thanks alot dude!
EDIT: Sorry, do you know which CyanogenMod I should flash? I just want to upgrade to one that is fully working, but there are many in the index and I dont know which one to flash :s THANKS!!
and If I dont do a wipe? wont it be stuck at boot as the Guide says it will?
I highly recommend you read the discussion thread for the version of CM you're wanting to try in General section. So you can get a handle on other people's experiences with it, bugs/flaws/annoyances/features/etc. I never flash a rom without reading the first 10 pages of those threads & the last two weeks or so worth of posts so I know what I'm in for.
I agree. And you always have to perform a full wipe if you change firmware.
Sent from the Matrix
Donnie Sins said:
I agree. And you always have to perform a full wipe if you change firmware.
Sent from the Matrix
Click to expand...
Click to collapse
yes thank you I will, but do I wipe my phone before I install CM? or..? during it..? I'm scared of this superbricking ^-^, I have flashed my GS1 before with no problems, but problems arose and I've been out of the game for a while, and have forgotten phones and roms etc for quite a bit ^-^
THANKS AGAIN
AndroidTerminator said:
yes thank you I will, but do I wipe my phone before I install CM? or..? during it..? I'm scared of this superbricking ^-^, I have flashed my GS1 before with no problems, but problems arose and I've been out of the game for a while, and have forgotten phones and roms etc for quite a bit ^-^
THANKS AGAIN
Click to expand...
Click to collapse
I assume you've read guides about how to flash a rom? Copy the zip-file to your phone, back up, wipe and flash.
You don't have to be scared of this superbrick bug because you're already running a custom kernel.
Sent from the Matrix
Donnie Sins said:
I assume you've read guides about how to flash a rom? Copy the zip-file to your phone, back up, wipe and flash.
You don't have to be scared of this superbrick bug because you're already running a custom kernel.
Sent from the Matrix
Click to expand...
Click to collapse
really? I'm running a custom kernel because I rooted my phone right..?
AndroidTerminator said:
really? I'm running a custom kernel because I rooted my phone right..?
Click to expand...
Click to collapse
You're running Philz-kernel aren't you?
Sent from the Matrix
Donnie Sins said:
You're running Philz-kernel aren't you?
Sent from the Matrix
Click to expand...
Click to collapse
Well, I was trying to root my phone so I don't think so, now that I think of it no, its only root and clockwork recovery mode thingymajig because file size only 7mb so if it was only root, my build number and everything is as same as before ^-^,
That's what I am so confuzzled about, I need to downgrade to a custom rom that must come with a custom kernel right to be able to upgrade to cyanogen right...? otherwise ill brick it?
No. Make sure you flash a custom kernel (for example Siyah) with Odin. Then there's no need to flash other firmware first before upgrading. Just wipe your device in CWM (after the back up), and flash the rom you want.
Sent from the Matrix
Thanks, thing is a lot of things are outdated like the guides, do you know if I can use the latest odin which is out that apparently is for the S3? I've spent two days trying to do research on this and im failing quite badly :'(
AndroidTerminator said:
Thanks, thing is a lot of things are outdated like the guides, do you know if I can use the latest odin which is out that apparently is for the S3? I've spent two days trying to do research on this and im failing quite badly :'(
Click to expand...
Click to collapse
Make sure you have kies installed or at least the drivers.
Reboot into download mode
Run ODIN 1.85
Flash Siyah kernel (.tar) via PDA section
Boot into recovery run backup
Wipe data/factory reset
Flash CM zip file.
TheATHEiST said:
Make sure you have kies installed or at least the drivers.
Reboot into download mode
Run ODIN 1.85
Flash Siyah kernel (.tar) via PDA section
Boot into recovery run backup
Wipe data/factory reset
Flash CM zip file.
Click to expand...
Click to collapse
YES, [email protected][email protected][email protected]! so so much, easy when explained like that, I'm knowledgeable and pick things up quickly but you have made this easier for me, thanks for the help DD: <3
AndroidTerminator said:
YES, [email protected][email protected][email protected]! so so much, easy when explained like that, I'm knowledgeable and pick things up quickly but you have made this easier for me, thanks for the help DD: <3
Click to expand...
Click to collapse
Btw, if you have any apps/appdata you need to restore after wipe you can restore them from your nandroid backup using appextractor.
I have flashed paranoidandroid 3.15 on my galaxy s3 a couple weeks ago, aside the occasional screen that win't turn on I haven't had any problem, but I set my mind on flashing a new kernel in order to be able to change thez governor. I tried to flash air kernel on, I did exactly what I was told: Boot into recovery, clear cache/delvik, installed kernel from sd card, and rebooted. But after the phone being rebooted, I still had the stock kernel.
My question is, why did this happen, and how do I fix it?
All help is appreciated
what recovery? link to the kernel?
Glebun said:
what recovery? link to the kernel?
Click to expand...
Click to collapse
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
vonniel said:
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
Click to expand...
Click to collapse
Kernel is for nexus s not galaxy s3
Sent from my GT-I9300 using xda premium
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Glenbun. Only mismatched, corrupted, or missing boot loaders can kill a phone.
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Glebun said:
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Click to expand...
Click to collapse
Glebun u have a point, even other incompatible components of recovery zip packages can brick the phone.
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Glebun said:
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Click to expand...
Click to collapse
Wow, I feel so dumb ^^' I'll be more careful next time around.
What kernel would you recommend for me?
I recommed stock mb5 or speedmod k2-12 kernels for you
Bahadirafro said:
I recommed stock mb5 or speedmod k2-12 kernels for you
Click to expand...
Click to collapse
Well, I don't really know either of them, I don't mind stock, but I want to change things, sometimes it just isn't up for the task, or uses up battery when I would rather it didn't, without even knowing what they do, and looking around, I found the perseus kernel, I would like some opinions on the kernel, I would be very grateful if you told me if it fits me, if it's compatible with ParanoidAndroid, and finally if you have a better suggestion for a kernel.
http://forum.xda-developers.com/showthread.php?t=1691401
read the first post of the thread to find out if it's compatible with your ROM.
and try it to see if it suits you
If I'm running TWRP can I still download kernels that say they are meant for CWM?
yes
My phone just gets stuck in a black screen when I try to boot into recovery. It happend once a few days ago, and i soloved it by going again to stock by odin and rooting it again. It booted to recovery the first time, i flashed carbon rom nightly 26 and now when I try to update, it doenst boot again. What is happening?
Info+New Kernel/Recovery
francantabria said:
My phone just gets stuck in a black screen when I try to boot into recovery. It happend once a few days ago, and i soloved it by going again to stock by odin and rooting it again. It booted to recovery the first time, i flashed carbon rom nightly 26 and now when I try to update, it doenst boot again. What is happening?
Click to expand...
Click to collapse
Firstly: Please give more detailed information (which kernel do you use, which ROM did you use before the problem occurred?)
Secondly: It is possible that you can't acess recovery mode anymore when flashing new updates. Happens with CM 10.2 OTA Update right now. The solution would be to flash a new recovery using Heimdall (Open-Source ODIN alternative) [Didn't try that, but should theoretically work] or, mor simple, a new kernel. Dorimany v9.34 is suited perfectly for that. Download here: http://dorimanx.shine.sk/ .
H3llwar said:
Firstly: Please give more detailed information (which kernel do you use, which ROM did you use before the problem occurred
Secondly: It is possible that you can't acess recovery mode anymore when flashing new updates. Happens with CM 10.2 OTA Update right now. The solution would be to flash a new recovery using Heimdall (Open-Source ODIN alternative) [Didn't try that, but should theoretically work] or, mor simple, a new kernel. Dorimany v9.34 is suited perfectly for that. Download here: http://dorimanx.shine.sk/ .
Click to expand...
Click to collapse
Well, i used Carbon Rom for a few weeks, so that was definitly the rom. Talking about the kernel, I dont even know how to install one.. haha Now in kernel version it says..
3.0.64 CM gb07657a
[email protected] #1 (I dont know what kernel it is)
Yeah but even if I dont want to flash an update, just boot recovery, I cant. Have you any link to know about Heimdall? Or how to install Dorimany? Im a beginner I have to say.
Thanks
francantabria said:
Well, i used Carbon Rom for a few weeks, so that was definitly the rom. Talking about the kernel, I dont even know how to install one.. haha Now in kernel version it says..
3.0.64 CM gb07657a
[email protected] #1 (I dont know what kernel it is)
Yeah but even if I dont want to flash an update, just boot recovery, I cant. Have you any link to know about Heimdall? Or how to install Dorimany? Im a beginner I have to say.
Thanks
Click to expand...
Click to collapse
You installed a Kernel while rooting your phone: Its the .tar that you have to put into the PDA section in ODIN. There are Kernels with .tar and .zip: .tar files are only flashable using Odin while .zip files are flashed using the recovery just like you flash ROMs. I guess your Kernel is a custom CM Kernel (CM for Cyanogen Mod). Carbon ROM is probably based on CM. There is currently no other workaround to get your recovery back then flashing a new kernel/recovery. I am currently working on an easy workaround for this problem, but it will take a while.
Dorimanx is downloadable here http://dorimanx.shine.sk/ and should be compatible: Just flash it like you did when rooting your phone in the beginning, just with Dorimanx .tar in PDA. Recovery should work again afterwards.
My mistake: It's Dorimanx, not Dorimany
Hit Thanks and just ask if you need additional help!
H3llwar said:
You installed a Kernel while rooting your phone: Its the .tar that you have to put into the PDA section in ODIN. There are Kernels with .tar and .zip: .tar files are only flashable using Odin while .zip files are flashed using the recovery just like you flash ROMs. I guess your Kernel is a custom CM Kernel (CM for Cyanogen Mod). Carbon ROM is probably based on CM. There is currently no other workaround to get your recovery back then flashing a new kernel/recovery. I am currently working on an easy workaround for this problem, but it will take a while.
Dorimanx is downloadable here http://dorimanx.shine.sk/ and should be compatible: Just flash it like you did when rooting your phone in the beginning, just with Dorimanx .tar in PDA. Recovery should work again afterwards.
My mistake: It's Dorimanx, not Dorimany
Hit Thanks and just ask if you need additional help!
Click to expand...
Click to collapse
Yeah, I remember.. it was siyah kernel.
So in your opinion I should flash Dorimanx by Odin then? No other way to fix isnt it? and.. in dorimanx page, which one of all them should I download?
francantabria said:
Yeah, I remember.. it was siyah kernel.
So in your opinion I should flash Dorimanx by Odin then? No other way to fix isnt it? and.. in dorimanx page, which one of all them should I download?
Click to expand...
Click to collapse
1. Yes you should
2. Not right now, maybe in the future, flashing recovery.img using Heimdall would probably help, but I didn't try it myself and using Heimdall is quite complex
3. In General: The newest .tar (9.34/8.34) as you can't use .zip files
When you want to use Stock Samsung ROM: Version 8
When you want to use CM/AOKP based ROM: Version 9
Remember: No ICS Support!
Hit Thanks and just ask if you need more help.
H3llwar said:
1. Yes you should
2. Not right now, maybe in the future, flashing recovery.img using Heimdall would probably help, but I didn't try it myself and using Heimdall is quite complex
3. In General: The newest .tar (9.34/8.34) as you can't use .zip files
When you want to use Stock Samsung ROM: Version 8
When you want to use CM/AOKP based ROM: Version 9
Remember: No ICS Support!
Hit Thanks and just ask if you need more help.
Click to expand...
Click to collapse
Ok.
But every aosp rom, like Carbon PA and these are based either in AOKP or CM, isnt it?
The newest one is 9/39, is that the one?
francantabria said:
Ok.
But every aosp rom, like Carbon PA and these are based either in AOKP or CM, isnt it?
Click to expand...
Click to collapse
CM & AOKP are actually based on AOSP, so Yes, every AOSP ROM should work.
H3llwar said:
CM & AOKP are actually based on AOSP, so Yes, every AOSP ROM should work.
Click to expand...
Click to collapse
I did what you said and after installing Carbon Rom again recovery is gone.. so I suposse it is Carbon problem. I will do it again and install a different rom
francantabria said:
I did what you said and after installing Carbon Rom again recovery is gone.. so I suposse it is Carbon problem. I will do it again and install a different rom
Click to expand...
Click to collapse
I agree, the problem results of the ROM: But you have to flash dorimanx after carbon because carbon replaces the current kernel with its own CM custom Kernel. It should work just fine with carbon when it's flashed after installing carbon.