Related
Hi guys,
I have spent two nights reading many methods of rooting and flashing already, but I yet to come across a way to install CWM Recovery for my GT-I9100M without using a CF-root kernel.
The thing is, I want to keep the official 4.0.3 firmware I got from Kies.
I already figured out how to root without using a CF-root kernel. He does not have a CF kernel for my version anyways.
Back to my question. Is there a way?
I tried flashing the ZIP from ROM manager's website, but the recovery is only temporary. The next boot, it goes back to stock recovery.
In my Xperia X10, I could install CWM Recovery using a program after rooting. Not sure if I can do it for SG2.
fantobe said:
Hi guys,
I have spent two nights reading many methods of rooting and flashing already, but I yet to come across a way to install CWM Recovery for my GT-I9100M without using a CF-root kernel.
The thing is, I want to keep the official 4.0.3 firmware I got from Kies.
I already figured out how to root without using a CF-root kernel. He does not have a CF kernel for my version anyways.
Back to my question. Is there a way?
I tried flashing the ZIP from ROM manager's website, but the recovery is only temporary. The next boot, it goes back to stock recovery.
In my Xperia X10, I could install CWM Recovery using a program after rooting. Not sure if I can do it for SG2.
Click to expand...
Click to collapse
You can flash kernels and you will not lose your official firmware.
All you would have to do is root your device and make a nandroid backup before you flash anything. Then you would have a copy of your firmware. Worst case, if you lose the backup, all you need to do is go to www.sammobile.com and download the firmware and flash through odin.
Sent from my GT-I9100 using xda premium
...
I see. Custom kernel is the only way to get recovery.
One other question though, is it okay to flash a ROM using a temporary CWM recovery (ie. recovery flashed indepedent of kernel)?
fantobe said:
I see. Custom kernel is the only way to get recovery.
One other question though, is it okay to flash a ROM using a temporary CWM recovery (ie. recovery flashed indepedent of kernel)?
Click to expand...
Click to collapse
Yes, no issue at all
Sent from my GT-I9100 using Tapatalk 2
fantobe said:
I see. Custom kernel is the only way to get recovery.
One other question though, is it okay to flash a ROM using a temporary CWM recovery (ie. recovery flashed indepedent of kernel)?
Click to expand...
Click to collapse
yes i was on stock and i ran temp cwm to flash aokp all was fine.
Sent from my GT-I9100 using Tapatalk 2
hey guys,..my phone is galaxy s 2..i had it rooted when it had gingerbread...i recently had to upgrade it to ICS from a mobile service center and i lost root access..now i hav
Android version 4.0.4
build number IMM76D.XWLPW
now i see these threads sayin flashing/rooting this phone bricks it..
although i hav done it befor, iam no tech geek.. and now there are too many confusing ways
Any suggestions on safely rooting it again and threads on how to ... would be helpful..
please help me here guys ..
Download siyah kernel 4.1.5 and put it on the sd card. Then go recovery and flash the zio. Now you have root
Skickat från min GT-I9100 via Tapatalk 2
if you want to be save and don´t wanna touch your kernel try this
bihslk said:
Download siyah kernel 4.1.5 and put it on the sd card. Then go recovery and flash the zio. Now you have root
Skickat från min GT-I9100 via Tapatalk 2
Click to expand...
Click to collapse
And how is he going to manage that if he now has stock recovery??
If he has stock recovery he will need to flash the .tar version of Siyah via ODIN in download mode.
Please Atleast Read Stickies, i Beg You
http://forum.xda-developers.com/showpost.php?p=28388184
Get Siyah kernel from here
http://gokhanmoral.com
Flash via odin
Sent from my iPhone using Tapatalk
And don't even think about doing wipes of any kind.
TheATHEiST said:
And how is he going to manage that if he now has stock recovery??
If he has stock recovery he will need to flash the .tar version of Siyah via ODIN in download mode.
Click to expand...
Click to collapse
Actually, with 4.0.4, from stock recovery he could first flash the temp CWM recovery, and from there flash the zip of Siyah. That's what I did.
I wouldnt worry as this is 2 months old, and has been revived for some reason.
Anyway,he should have went back to GB and flashed siyah s2-v.2.6.14.tar if he didnt like ICS.
"noob ok...lazy noob not ok"
ctomgee said:
Actually, with 4.0.4, from stock recovery he could first flash the temp CWM recovery, and from there flash the zip of Siyah. That's what I did.
Click to expand...
Click to collapse
Yes, well that is different, your not actually flashing the kernel in stock recovery which was my actual point if you re-read.
TheATHEiST said:
Yes, well that is different, your not actually flashing the kernel in stock recovery which was my actual point if you re-read.
Click to expand...
Click to collapse
I was just pointing out that there WAS a way to do it. Don't get so ruffled.
Edit: you may have misunderstood, and may not know this. From stock recovery you can flash the temporary CWM recovery .zip file, then from temp CWM recovery you can flash the .zip for Siyah or whatever other kernel. No Odin necessary.
ctomgee said:
I was just pointing out that there WAS a way to do it. Don't get so ruffled.
Edit: you may have misunderstood, and may not know this. From stock recovery you can flash the temporary CWM recovery .zip file, then from temp CWM recovery you can flash the .zip for Siyah or whatever other kernel. No Odin necessary.
Click to expand...
Click to collapse
Again, you're still not flashing the kernel via stock recovery, your doing it via cwm. The user who I initially replied to advised to simply download siyah onto sdcard then reboot into recovery and flash it which ISNT possible.
What you're advising is completely different and again, doesn't use stock recovery. Yes ODIN isnt used but that wasnt my point in first place, It was simply that you cant flash Siyah via stock recovery.
TheATHEiST said:
Again, you're still not flashing the kernel via stock recovery, your doing it via cwm. The user who I initially replied to advised to simply download siyah onto sdcard then reboot into recovery and flash it which ISNT possible.
What you're advising is completely different and again, doesn't use stock recovery. Yes ODIN isnt used but that wasnt my point in first place, It was simply that you cant flash Siyah via stock recovery.
Click to expand...
Click to collapse
Actually, you said he HAD to use Odin. Which wasn't true.
But we're both nitpicking at this point. Let's just let this go, eh?
What is siyah anyway?
@theunderling
that could be my dault...
@gastonw
a custom kernel
[email protected] said:
@theunderling
that could be my dault...
@gastonw
a custom kernel
Click to expand...
Click to collapse
........
Sent from the little guy
[email protected] said:
@gastonw
a custom kernel
Click to expand...
Click to collapse
Is it the default kernel from the LSJ-leak?
Sent from the Matrix
Donnie Sins said:
Is it the default kernel from the LSJ-leak?
Sent from the Matrix
Click to expand...
Click to collapse
The one & only?
Sent from the little guy
yep...the one & only "custom" kernel..at least for me
Hello all,
About a week ago I ran into a problem with my phone which I thought was a software, which actually turned out to be a hardware issue with my sim card. Cutting a long story short, I flashed the official stock rom with Odin V1.85, and it passed and everything was back to default factory settings.
Having now got my issue fixed, I wanted to re-root my phone, in order to go back to the old ROM I was using [UltimaROM v12]. However after flashing various versions of CWM I cannot get my phone to root. I'm no stranger using Odin, I can usually install a new version of CWM in 30 seconds, but my phone is persistent on not rooting. I can't work out if maybe I've done something wrong, but it doesn't seem to be working.
I've tried running as Admin on W7, but it doesn't make a difference, I'd appreciate if one of you guys could help, as I used the search bar before, but it seems no-one has had this problem before.
Modem: XXEMC2
Kernel: Stock
ROM: Stock
Use TWRP or Philz recovery .
jje
I've tried those too, they don't work either.
bkss said:
I've tried those too, they don't work either.
Click to expand...
Click to collapse
Use framaroot aragorn exploit
Sent from my GT-I9300 using xda premium
What exactly is the problem? Phone not recognised? Flash failing? If so at what point? More details please
slaphead20 said:
What exactly is the problem? Phone not recognised? Flash failing? If so at what point? More details please
Click to expand...
Click to collapse
The problem is the recoveries will look as if they've installed fine through Odin getting a "passed" flag, but when I go to recovery it's still the default Android recovery. Therefore no root.
What root method are you using?
Chainfire one I believe. You basically install CWM recovery, then install SuperSU from .zip in CWM.
So you have rooted but can't install recovery?
Just flash one with mobile Odin,
Nope, no root yet, because I can't flash SuperSU.zip 'cause I'm still on the default recovery.
Just use the old cf root then update the recovery or use framaroot and flash recovery with mobile Odin
cf-root roots the phone as well as changes the stock recovery to cwm recovery! is this the exact one you flashed? http://forum.xda-developers.com/showthread.php?t=1695238
sriram231092 said:
cf-root roots the phone as well as changes the stock recovery to cwm recovery! is this the exact one you flashed? http://forum.xda-developers.com/showthread.php?t=1695238
Click to expand...
Click to collapse
I think he is using cf auto root
Mine is an i9300 rooted and running 4.1.2
I have downloaded the carbon rom 4.4,2 meant for i9300 and also the gapps to the phone' sd card,
Can I upgrade the phone via mobile Odin pro only? I don't have access to a PC or a mac.
Or is it better to go via CMWM?
Don't want to mess up my only phone
You can flash Philz through Mobile Odin and then flash the ROM through Philz.
Mobile Odin wants to wipe data and cache
xpmode said:
You can flash Philz through Mobile Odin and then flash the ROM through Philz.
Click to expand...
Click to collapse
Mobile Odin wants to wipe data and cache, plus wipe dalvik cache to install philz touch recovery.
Is that ok to do so? I made nandroid backup thru cwm recovery.
No need to flash through mobile odin...
There are flashable zips available for Phil's... you can just flash those through your current recovery..
And I would suggest change your modem to any modem after mg4...
Installing an aosp ROM would not affect anything related to modem but if you do flash any Samsung rom then that would be necessary...
Sent from my GT-I9300
Was able to update to philz recovery and did a new nandroid backup
kunal1540 said:
No need to flash through mobile odin...
There are flashable zips available for Phil's... you can just flash those through your current recovery..
And I would suggest change your modem to any modem after mg4...
Installing an aosp ROM would not affect anything related to modem but if you do flash any Samsung rom then that would be necessary...
Sent from my GT-I9300
Click to expand...
Click to collapse
Thanks for the suggestion. Flashed philz through CWM recovery.
Now should I use Mobile Odin pro to install 4.2.2 carbon or just through philz itself?
Seems Odin pro gives me ability to inject super user on install. Philz doesn't give me any such option.
What would you recommend?
freedomIndia said:
Thanks for the suggestion. Flashed philz through CWM recovery.
Now should I use Mobile Odin pro to install 4.2.2 carbon or just through philz itself?
Seems Odin pro gives me ability to inject super user on install. Philz doesn't give me any such option.
What would you recommend?
Click to expand...
Click to collapse
Actually I think Philz does allow you to flash root .I remember seeing the option in advanced or philz settings I think. You can then go on to download SuperSU from market and it will work fine
Don't have a PC or mac
whatsgood said:
Actually I think Philz does allow you to flash root .I remember seeing the option in advanced or philz settings I think. You can then go on to download SuperSU from market and it will work fine
Click to expand...
Click to collapse
Is the carbon rom pre rooted? Else I would have to depend on Odin to prerogative it for me.
freedomIndia said:
Is the carbon rom pre rooted? Else I would have to depend on Odin to prerogative it for me.
Click to expand...
Click to collapse
99% of custom roms are rooted you only have to root your device if you are on stock rom and not planning on flashing custom roms but want to install root apps
Thank you all
tallman43 said:
99% of custom roms are rooted you only have to root your device if you are on stock rom and not planning on flashing custom roms but want to install root apps
Click to expand...
Click to collapse
Thank you for clarifying that. Will update tomorrow on how the upgrade went. Appreciate your help.
I I rooted my S2 I777 using Frameroot-1.4.2 and flashed via Odin CWM 5.0.2.3 then I flashed AoCP KitKat from from GalaxyS2Root.com and now my phone is in a loop entering in recovery mode.
I flashed the rom on CWM and when I asked to reboot the system it start reboot and enter in recovery mode again.
I tried to flash the official rom from AT&T with Android 2.3.4 and even after I flash this rom it doesn't stop to enter in recovery mode.
First thing to do: perform a wipe/data from within recovery.
creepyncrawly said:
First thing to do: perform a wipe/data from within recovery.
Click to expand...
Click to collapse
It was done and still reboot in recovery.
I tried to install a stock rom via Odin 1,85 but I failed in all the tries then I tried via Odin 3.07 and it worked and I did a full wipe and rebooted the system and it got back to recovery mode then I did it again and it worked.
Now I'm using a stock Rom with Androind 4.2.1.
Before it works I've tried to install the stock Rom and it worked then I rooted the phone and installed CWM and it always reboot in recovery mode.
gsilva92 said:
...then I rooted the phone and installed CWM and it always reboot in recovery mode.
Click to expand...
Click to collapse
This part makes me think you use Rom Manager, and that would explain why it keeps rebooting. There's no need to install CWM separately as it's included in i777 kernels. Rom Manager will ruin your phone, stay away from it (see the sticky).
SteveMurphy said:
This part makes me think you use Rom Manager, and that would explain why it keeps rebooting. There's no need to install CWM separately as it's included in i777 kernels. Rom Manager will ruin your phone, stay away from it (see the sticky).
Click to expand...
Click to collapse
I don't use Rom Manager.
It was rooted before and I was using a KitKat Rom but I tried to flash the Rom I mentioned and it bricked.
I unbricked it and rooted and installed CWM then it started with the problem.
As I said now I'm using a stock Rom with Android 4.2.1.
You said CWM is included in i777 Kernels so if I root my phone I can simply get in recovery mode and use the stock recovery to flash the Rom?
You mentioned that you rooted the stock firmware and installed a custom recovery, but without knowing your root - recovery process, it's hard to say where things went sideways.
The kernel of the i777 does include the recovery, but the stock kernel cannot be used to flash custom firmware.
>>this guide<< is one of the more reliable ways to go from stock to custom firmware.
summary;
-framaroot to establish root
-mobile odin to install custom kernel
-custom kernel to install custom firmware
happy flashing
-Cyril
gsilva92 said:
I don't use Rom Manager.
It was rooted before and I was using a KitKat Rom but I tried to flash the Rom I mentioned and it bricked.
I unbricked it and rooted and installed CWM then it started with the problem.
As I said now I'm using a stock Rom with Android 4.2.1.
You said CWM is included in i777 Kernels so if I root my phone I can simply get in recovery mode and use the stock recovery to flash the Rom?
Click to expand...
Click to collapse
cyril279 said:
You mentioned that you rooted the stock firmware and installed a custom recovery, but without knowing your root - recovery process, it's hard to say where things went sideways.
The kernel of the i777 does include the recovery, but the stock kernel cannot be used to flash custom firmware.
>>this guide<< is one of the more reliable ways to go from stock to custom firmware.
summary;
-framaroot to establish root
-mobile odin to install custom kernel
-custom kernel to install custom firmware
happy flashing
-Cyril
Click to expand...
Click to collapse
Thank you.
I'll follow this guide and I'll post here if it worked for me.
cyril279 said:
You mentioned that you rooted the stock firmware and installed a custom recovery, but without knowing your root - recovery process, it's hard to say where things went sideways.
The kernel of the i777 does include the recovery, but the stock kernel cannot be used to flash custom firmware.
>>this guide<< is one of the more reliable ways to go from stock to custom firmware.
summary;
-framaroot to establish root
-mobile odin to install custom kernel
-custom kernel to install custom firmware
happy flashing
-Cyril
Click to expand...
Click to collapse
I tried to follow the instruction in the link you sent me but I failed doing it.
I searched on google and I saw that Odin has an option OTA / Update zip but mine doesn't have this option.
Is there something I should do before flash a custom rom?
I'm using Mobile Odin Pro.
gsilva92 said:
I tried to follow the instruction in the link you sent me but I failed doing it.
I searched on google and I saw that Odin has an option OTA / Update zip but mine doesn't have this option.
Is there something I should do before flash a custom rom?
I'm using Mobile Odin Pro.
Click to expand...
Click to collapse
Agreed, the instructions in that guide can be a little confusing.
First, are you sure you are using the AT&T Galaxy S II SGH-I777? Because you said several times in this thread that you are now running 4.2.1, but there is no such version of the os for this phone. The latest official AT&T stock firmware is I777UCMD8 which is 4.1.2.
If you affirm that your phone is SGH-I777 running UCMD8 firmware, and that you have root, then the next step is to use mobile odin to flash AJK v4.9 NoSwap kernel. Download the zip file from the Kernel thread. Open the zip file with an archiving tool such as win-zip, 7zip, etc. and extract the boot.img. Mobile odin will not recognize the zip file, but it will recognize the boot.img as a kernel, and will flash that. So transfer the boot image to the phone sd card and flash with mobile odin.
Next, you will find that the phone buttons don't work. Transfer the AJK v4.9 zip file to the sd card, enter into Clockwork Mod recovery and flash the AJK v4.9 zip file. This will fix the buttons. Now you have a working stock UCMD8 with custom AJK kernel. Now you are ready to flash what ever firmware you want. Hope this helps, and feel free to ask questions.
creepyncrawly said:
Agreed, the instructions in that guide can be a little confusing.
First, are you sure you are using the AT&T Galaxy S II SGH-I777? Because you said several times in this thread that you are now running 4.2.1, but there is no such version of the os for this phone. The latest official AT&T stock firmware is I777UCMD8 which is 4.1.2.
If you affirm that your phone is SGH-I777 running UCMD8 firmware, and that you have root, then the next step is to use mobile odin to flash AJK v4.9 NoSwap kernel. Download the zip file from the Kernel thread. Open the zip file with an archiving tool such as win-zip, 7zip, etc. and extract the boot.img. Mobile odin will not recognize the zip file, but it will recognize the boot.img as a kernel, and will flash that. So transfer the boot image to the phone sd card and flash with mobile odin.
Next, you will find that the phone buttons don't work. Transfer the AJK v4.9 zip file to the sd card, enter into Clockwork Mod recovery and flash the AJK v4.9 zip file. This will fix the buttons. Now you have a working stock UCMD8 with custom AJK kernel. Now you are ready to flash what ever firmware you want. Hope this helps, and feel free to ask questions.
Click to expand...
Click to collapse
Thank you.
I'm gonna try it and I'll post at night (in Brazil) when I come back from work.
creepyncrawly said:
Agreed, the instructions in that guide can be a little confusing.
First, are you sure you are using the AT&T Galaxy S II SGH-I777? Because you said several times in this thread that you are now running 4.2.1, but there is no such version of the os for this phone. The latest official AT&T stock firmware is I777UCMD8 which is 4.1.2.
If you affirm that your phone is SGH-I777 running UCMD8 firmware, and that you have root, then the next step is to use mobile odin to flash AJK v4.9 NoSwap kernel. Download the zip file from the Kernel thread. Open the zip file with an archiving tool such as win-zip, 7zip, etc. and extract the boot.img. Mobile odin will not recognize the zip file, but it will recognize the boot.img as a kernel, and will flash that. So transfer the boot image to the phone sd card and flash with mobile odin.
Next, you will find that the phone buttons don't work. Transfer the AJK v4.9 zip file to the sd card, enter into Clockwork Mod recovery and flash the AJK v4.9 zip file. This will fix the buttons. Now you have a working stock UCMD8 with custom AJK kernel. Now you are ready to flash what ever firmware you want. Hope this helps, and feel free to ask questions.
Click to expand...
Click to collapse
I did exactly what you said and it worked but when I tried to flash a custom Rom it failed and bricked my phone again.
And now I'm back to the first topic, it always reboots in the recovery mode.
I'll try to fix it again.
I didn't see the error it showed me when failed in flash the custom rom. I know I should have seen it.
Here is a video of my phone rebooting in the recovery mode.
gsilva92 said:
I did exactly what you said and it worked but when I tried to flash a custom Rom it failed and bricked my phone again.
And now I'm back to the first topic, it always reboots in the recovery mode.
I'll try to fix it again.
I didn't see the error it showed me when failed in flash the custom rom. I know I should have seen it.
Here is a video of my phone rebooting in the recovery mode.
Click to expand...
Click to collapse
What firmware did you try to flash? If you tried again to flash the "AoCP KitKat from GalaxyS2Root dot com" that you mentioned in your first post, that in itself could be the problem. In the past, many products from the GalaxyS2Root website have caused numerous and various types of problems, including similar to your issue. For most of the past two and a half years, we have been advising people to avoid the Galaxy S2 Root website and products. It is best to flash firmware downloaded from XDA-Developers.
If you are trying to install a version of kitkat on your phone, then you also probably need advice from someone more familiar with kitkat, like cyril279 or SteveMurphy. Maybe one of them will jump in and help.
gsilva92 said:
I I rooted my S2 I777 using Frameroot-1.4.2 and flashed via Odin CWM 5.0.2.3 then I flashed AoCP KitKat from from GalaxyS2Root.com and now my phone is in a loop entering in recovery mode.
I flashed the rom on CWM and when I asked to reboot the system it start reboot and enter in recovery mode again.
I tried to flash the official rom from AT&T with Android 2.3.4 and even after I flash this rom it doesn't stop to enter in recovery mode.
Click to expand...
Click to collapse
Just breezed through this and didn't see this mentioned but in the aocp kitkat forum here it states in the op you must be on cwm 6.0.4.4 or higher to flash their ROM. This is true for all kitkat ROMs I've tried so far. This may have been the source of your problem although usually most report getting a status7 error at this point but I'm not familiar with that cwm version you mentioned.
Also twrp works really well and it's touch based.
creepyncrawly said:
What firmware did you try to flash? If you tried again to flash the "AoCP KitKat from GalaxyS2Root dot com" that you mentioned in your first post, that in itself could be the problem. In the past, many products from the GalaxyS2Root website have caused numerous and various types of problems, including similar to your issue. For most of the past two and a half years, we have been advising people to avoid the Galaxy S2 Root website and products. It is best to flash firmware downloaded from XDA-Developers.
If you are trying to install a version of kitkat on your phone, then you also probably need advice from someone more familiar with kitkat, like cyril279 or SteveMurphy. Maybe one of them will jump in and help.
Click to expand...
Click to collapse
I'm trying to flash a Rom form XDA-Developers http://forum.xda-developers.com/showthread.php?t=2544790
I'll try to contact one of the users you mentioned. Thank you.
razen_kain said:
Just breezed through this and didn't see this mentioned but in the aocp kitkat forum here it states in the op you must be on cwm 6.0.4.4 or higher to flash their ROM. This is true for all kitkat ROMs I've tried so far. This may have been the source of your problem although usually most report getting a status7 error at this point but I'm not familiar with that cwm version you mentioned.
Also twrp works really well and it's touch based.
Click to expand...
Click to collapse
I'll try to flash twrp to flash KitKat. Thank you.
Good catch @razen_kain, the details were in the OP all along.
That said, The details of what you need to flash the firmware are in the OP of each Firmware thread, including the necessary kernel version, and where to find it.
Omni
Cyril279 said:
[...]
Recovery requirement (prior to flashing this firmware):
================
CWM 6.0.4.4+
--OR--
TWRP 2.6.3.0+
-Renderbroken's OmniROM kernel
-or- Flash Omni's Boot.IMG via MobileOdin
--------------------------------
SGH-S959G; (courtesy of @mr-cook)
TWRP 2.6.3.0.zip
--OR--
CWM 6.0.4.5.zip.[...]
Click to expand...
Click to collapse
CM 11
RenderBroken said:
[...]HOW TO INSTALL
Make sure you are on CWM 6.0.4.4+ before flashing ROM! Thanks to @mr-cook you can now download and flash just the recovery/kernel!
Other handy scripts you can use from mr-cook can be found: Here
Download 6.0.4.5 Recovery/Kernel created by mr-cook : Here[...]
Click to expand...
Click to collapse
AOCP 7.0
crt60 said:
HOW TO INSTALL
***(If you are on Jellybean or older, you will need the latest CWM recovery for the i777 to flash this ROM)***
***If you are having trouble with flashing the zip, you can try the odin version from here***
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------
gsilva92 said:
I I rooted my S2 I777 using Frameroot-1.4.2 and flashed via Odin CWM 5.0.2.3 then I flashed AoCP KitKat from from GalaxyS2Root.com and now my phone is in a loop entering in recovery mode.
I flashed the rom on CWM and when I asked to reboot the system it start reboot and enter in recovery mode again.
I tried to flash the official rom from AT&T with Android 2.3.4 and even after I flash this rom it doesn't stop to enter in recovery mode.
Click to expand...
Click to collapse
gsilva92 said:
I'm trying to flash a Rom form XDA-Developers http://forum.xda-developers.com/showthread.php?t=2544790
I'll try to contact one of the users you mentioned. Thank you.
I'll try to flash twrp to flash KitKat. Thank you.
Click to expand...
Click to collapse
If you go back to AT&T stock 4.1.2 I777UCMD8 to start over, here are a couple of ways to get the kernel you need. Please bear in mind that the only kernel that will boot UCMD8 into system is the AJK v4.9 kernel that you used before. When you install another kernel such as RenderBroken's CWM or TWRP kenrel, or the one from OmniRom, the system will no longer boot, but you will be able to boot into recovery, so just avoid trying to boot the system, and choose the option to boot directly into recovery. Or... pull the battery and then use the button combo to enter recovery.
1) Extract the boot.img directly from the OmniRom zip file, and flash that using mobile odin. In this case, once you have UCMD8 rooted, you can skip the step of flashing AJK and flash the OmniRom kernel directly. Reboot into the new recovery and flash OmniRom.
2) Flash the AJK kernel as in my previous instructions. Then enter recovery and flash RenderBroken's kernel. Boot directly into recovery and flash OmniRom.
cyril279 said:
Good catch @razen_kain, the details were in the OP all along.
That said, The details of what you need to flash the firmware are in the OP of each Firmware thread, including the necessary kernel version, and where to find it.
Omni
CM 11
AOCP 7.0
------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
I gotta say I didn't read the full info after flash the rom.
creepyncrawly said:
If you go back to AT&T stock 4.1.2 I777UCMD8 to start over, here are a couple of ways to get the kernel you need. Please bear in mind that the only kernel that will boot UCMD8 into system is the AJK v4.9 kernel that you used before. When you install another kernel such as RenderBroken's CWM or TWRP kenrel, or the one from OmniRom, the system will no longer boot, but you will be able to boot into recovery, so just avoid trying to boot the system, and choose the option to boot directly into recovery. Or... pull the battery and then use the button combo to enter recovery.
1) Extract the boot.img directly from the OmniRom zip file, and flash that using mobile odin. In this case, once you have UCMD8 rooted, you can skip the step of flashing AJK and flash the OmniRom kernel directly. Reboot into the new recovery and flash OmniRom.
2) Flash the AJK kernel as in my previous instructions. Then enter recovery and flash RenderBroken's kernel. Boot directly into recovery and flash OmniRom.
Click to expand...
Click to collapse
I did exactly what you said and it worked. Now I'm running OmniRom and I didn't have any problem during the process to flash and not even after.
Thank you everyone.
I'll be more careful next time.
gsilva92 said:
I gotta say I didn't read the full info after flash the rom.
I did exactly what you said and it worked. Now I'm running OmniRom and I didn't have any problem during the process to flash and not even after.
Thank you everyone.
I'll be more careful next time.
Click to expand...
Click to collapse
Welcome to the club :thumbup:
razen_kain said:
Welcome to the club :thumbup:
Click to expand...
Click to collapse
Thank you.