I am having an issue with flashing CWM via Odin and keeping it there. I flash CWM via ODIN, I've tried 3 diff versions of CWM , Red One, Voodoo (blue one) and the 3.0.0.8 via rom manager (orange one) each time i flash one, i can boot into after flashing it via ODIN, but when i reboot the phone. CWM is gone and its back to the factory samsung recover "for all devices" nonsense. I have been able to obtain root by flashing via the SU zip method and I have root, i just can't flash a rom b/c cwm wont stick....any ideas? search returns nothing!
Thats because you need a modified kernal for cwm to stick.
Here is the modified stock kernal for a froyo rom. put this in the pda function of odin.
http://goo.gl/QCYxT
droidstyle said:
Thats because you need a modified kernal for cwm to stick.
Here is the modified stock kernal for a froyo rom. put this in the pda function of odin.
http://goo.gl/QCYxT
Click to expand...
Click to collapse
you my friend have received a thanks, and are a great asset to these boards. It would have been easier for you to tell me to "research" but instead, you took the time to even give me a link.
+1 to you.
I appreciate the kind words sir, thanks!
even though i have flashed the kernel you have provided, my phone contiues to boot into stock recovery. (also thanks to providing the download link and thanks to person who asked question)
daskydivr said:
even though i have flashed the kernel you have provided, my phone contiues to boot into stock recovery. (also thanks to providing the download link and thanks to person who asked question)
Click to expand...
Click to collapse
did you odin a cwm recovery after the modified stock kernal?
Make sure your battery is removed when entering download mode to flash cwm via odin.
Once it shows successful, remove the cable.
insert battery and immediately enter cwm using the 3 finger method.
Flash a custom stock kernel.
choose "reboot system now"
let the system boot up.
then boot back to cwm recovery and flash your rom of choice.
droidstyle said:
did you odin a cwm recovery after the modified stock kernal?
Click to expand...
Click to collapse
ok now im odin the gingerbread leak, but i want Cyanogenmod, ill get a cwm recovery and try again or could you provide a link with one please?
daskydivr said:
ok now im odin the gingerbread leak, but i want Cyanogenmod, ill get a cwm recovery and try again or could you provide a link with one please?
Click to expand...
Click to collapse
If you want cm7 dont odin the gingerbread leak...Follow this guide.
http://forum.xda-developers.com/showthread.php?t=1212239
thanks im trying it out now!
Related
So i updated OTA to 2.2 and then rooted my Fascinate. Now I'm trying to flash a new rom using Rom Manager but whenever I try to install a rom or reboot into recovery i get the error
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
And then it puts me in Stock Android Recovery. Any ideas on why this is happening and how I can fix it? Thanks
RepAZ said:
So i updated OTA to 2.2 and then rooted my Fascinate. Now I'm trying to flash a new rom using Rom Manager but whenever I try to install a rom or reboot into recovery i get the error
And then it puts me in Stock Android Recovery. Any ideas on why this is happening and how I can fix it? Thanks
Click to expand...
Click to collapse
The consensus seems to be not to use ROM manager and to ODIN Clockwork Recovery Manager. Unfortunately there seems to be a little mentioned bug where CWM won't stay after the 1st time you reboot and I can't find a solution to this yet.
phonefiend said:
The consensus seems to be not to use ROM manager and to ODIN Clockwork Recovery Manager. Unfortunately there seems to be a little mentioned bug where CWM won't stay after the 1st time you reboot and I can't find a solution to this yet.
Click to expand...
Click to collapse
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
islandtime said:
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
Click to expand...
Click to collapse
Island beat me to it but he is exactly correct. I kept the stock kernel at first but i had to ODIN CWM 2 times as the first time it was blue but after 2nd time it was red. But the best way is to flash a custom Kernel which will keep it red
islandtime said:
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
Click to expand...
Click to collapse
What I meant to say is what you said above: you can boot into CWM right after you flash it, but if you restart again it will go into stock recovery.
fitti28 said:
Island beat me to it but he is exactly correct. I kept the stock kernel at first but i had to ODIN CWM 2 times as the first time it was blue but after 2nd time it was red. But the best way is to flash a custom Kernel which will keep it red
Click to expand...
Click to collapse
I've ODIN'd CWM multiple times but it still gets overwritten with the stock recovery. I'd like to stick with the stock ED01 kernel but can't find any ZIPs to flash this kernel via CWM.
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Allmaechtig said:
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
I can't find anything on that, can you point me to the thread you followed?
Allmaechtig said:
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
No, what is needed to get into CWM is you need to flash CWM via Odin. Take the battery out when going into download mode. After flashing, unplug the USB cable and put the battery back in. When you go to start the phone, boot straight into recovery. The stock kernel reflashes recovery on every boot, so if you boot the phone normally, the phone will continue to have stock recovery. Once in CWM, flash a custom kernel and you'll be set as the custom kernels don't reflash recovery on boot.
imnuts said:
No, what is needed to get into CWM is you need to flash CWM via Odin. Take the battery out when going into download mode. After flashing, unplug the USB cable and put the battery back in. When you go to start the phone, boot straight into recovery. The stock kernel reflashes recovery on every boot, so if you boot the phone normally, the phone will continue to have stock recovery. Once in CWM, flash a custom kernel and you'll be set as the custom kernels don't reflash recovery on boot.
Click to expand...
Click to collapse
This is unfortunate because I used to run a version of CWM just fine with the stock EB01 kernel. With the current CWMs I finally found a way to get it to work with the stock kernel: rename /system/etc/install-recovery.sh.
got it working yay
BlackHoleSlam said:
got it working yay
Click to expand...
Click to collapse
Tell us how.
i just waited some time and placed the debinged rom from adrenylne on my sd card then used the 3-30 tar and put my self in red voodoo flashed a different kernel theme then rom and all is good
So today i root my fascinate 2.2.1 ED04 with super one click which was successful, now only problem is getting the right CWM to to apply on blue stock recovery mode it give me a "installion abort" error message, so one help please !!!
Are u familiar with Odin? You can't flash anything in stock recovery so you need Odin to flash the cwm recovery
Sent from my SCH-I500 using XDA App
what file do i need to flash to gain cwm via odin ?
adrianp89 said:
what file do i need to flash to gain cwm via odin ?
Click to expand...
Click to collapse
first one here is the one you want:
http://forum.xda-developers.com/showthread.php?t=1046905
you need to use odin to install CWM, put the .tar CWM file in the PDA section of odin and press START, DO NOT PUSH ANY OTHER BUTTONS IN ODIN
adrianp89 said:
So today i root my fascinate 2.2.1 ED04 with super one click which was successful, now only problem is getting the right CWM to to apply on blue stock recovery mode it give me a "installion abort" error message, so one help please !!!
Click to expand...
Click to collapse
You also need to go and change a few file extensions if you are planning on staying with any stock ED build the file names to edit and a description are here if that is what your after. Its down the OP a bit but before the first reply post.
Hi, I have a Galaxy S2 with stock ROM 4.0.3 and stock Recovery. I wanted to know if there is a way of flashing Custom Rom without rooting the phone or ADB. Would this method work? http://forum.xda-developers.com/showthread.php?t=1501719 I would just proceed till the step "Choose CWM.zip and wait until CWM recovery appear." Would this work? i need custom recovery so i can flash a custom ROM.
Thanks again
No you cant flash a Custom ROM from stock recovery, you need a custom recovery and root access on your phone for flashing custom roms
the method you linked is only for rooting, the recovery appearing is only a temporory one from which you can only install SU-Busybox-Installer.zip.
masantula said:
Hi, I have a Galaxy S2 with stock ROM 4.0.3 and stock Recovery. I wanted to know if there is a way of flashing Custom Rom without rooting the phone or ADB. Would this method work? http://forum.xda-developers.com/showthread.php?t=1501719 I would just proceed till the step "Choose CWM.zip and wait until CWM recovery appear." Would this work? i need custom recovery so i can flash a custom ROM.
Thanks again
Click to expand...
Click to collapse
hey u have 2 root ur phone 2 install custom rom's and that method in the link is ok
after that u downld latest CWM recovery.zip by searching the same on the thread and install 2 get the CWM in ur app drawer
masantula said:
Hi, I have a Galaxy S2 with stock ROM 4.0.3 and stock Recovery. I wanted to know if there is a way of flashing Custom Rom without rooting the phone or ADB. Would this method work? http://forum.xda-developers.com/showthread.php?t=1501719 I would just proceed till the step "Choose CWM.zip and wait until CWM recovery appear." Would this work? i need custom recovery so i can flash a custom ROM.
Thanks again
Click to expand...
Click to collapse
I didn't test it myself, but I think that it will work.
If the custom ROM is provided as Odin-flashable tar file, you don't need a CWM recovery to flash it. Just put the ROm tar file into PDA section of Odin and flash it to your phone.
Only if the custom ROM is available as CWM-flashable zip file, you need to flash a kernel containing CWM recovery first.
I prefer to flash CF-Root kernel from Chainfire with Odin. It contains CWM Manager app and CWM recovery of cause.
When you are in doubt, stick to the flashing instructions of the ROM developer - usually in the corresponding ROM thread.
P.S.:
As soon as you have CWM recovery, create a nandroid/system backup.
So you will be able to go back to your current system, if something goes wrong with the new ROM.
Good luck !
Oh cool, lemme try it
masantula said:
Hi, I have a Galaxy S2 with stock ROM 4.0.3 and stock Recovery. I wanted to know if there is a way of flashing Custom Rom without rooting the phone or ADB. Would this method work? http://forum.xda-developers.com/showthread.php?t=1501719 I would just proceed till the step "Choose CWM.zip and wait until CWM recovery appear." Would this work? i need custom recovery so i can flash a custom ROM.
Thanks again
Click to expand...
Click to collapse
All you need to do is download cwm recovery from here http://clockworkmod.com/rommanager in your SD card and flash the Dowloaded zip from stock recovery .
Once you flash, your stock recovery will be converted to cwm recovery
After that flash any custom rom of your choice. Simple and short
Sent from my GT-I9100 using xda premium
ZACQ8 said:
No you cant flash a Custom ROM from stock recovery, you need a custom recovery and root access on your phone for flashing custom roms
the method you linked is only for rooting, the recovery appearing is only a temporory one from which you can only install SU-Busybox-Installer.zip.
Click to expand...
Click to collapse
No you can flash any ROM you want, just like any other cwm.
I have used it multiple times, but the Queston is can you do it the first time, before you choose that busy box installer.
Edit: yes you can flash any rom just fine
Pressed quote twice..
safepacket said:
All you need to do is download cwm recovery from here http://clockworkmod.com/rommanager in your SD card and flash the Dowloaded zip from stock recovery .
Once you flash, your stock recovery will be converted to cwm recovery
After that flash any custom rom of your choice. Simple and short
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Oh okay, so if i flash the ZIP file my Stock recovery will change to CWM recovery, sweet..thats simple caz i just wanted custom recovery so i can flash custom rom....Thanks again Will follow your method..
ZACQ8 said:
No you cant flash a Custom ROM from stock recovery, you need a custom recovery and root access on your phone for flashing custom roms
the method you linked is only for rooting, the recovery appearing is only a temporory one from which you can only install SU-Busybox-Installer.zip.
Click to expand...
Click to collapse
Thanks for that info, i thought this would work...gracias..
masantula said:
Oh okay, so if i flash the ZIP file my Stock recovery will change to CWM recovery, sweet..thats simple caz i just wanted custom recovery so i can flash custom rom....Thanks again Will follow your method..
Thanks for that info, i thought this would work...gracias..
Click to expand...
Click to collapse
2 different statements quoted above ....
please let me know if you flashed a custom rom successfully without rooting (flashing busybox installer zip) the phone.
goodluck...
ZACQ8 said:
2 different statements quoted above ....
please let me know if you flashed a custom rom successfully without rooting (flashing busybox installer zip) the phone.
goodluck...
Click to expand...
Click to collapse
I'm not following the step i had asked about, i am going to follow the steps that safepacket told me about. seems simple and direct..
masantula said:
I'm not following the step i had asked about, i am going to follow the steps that safepacket told me about. seems simple and direct..
Click to expand...
Click to collapse
exactly that is the step you asked about, will not work.....
I can confirm it works.....
Flashed new dx9 after full wipe.
From recovery choose the cwm zip
From that touch cwm flashed aosp rom.
So it works just fine.
atifsh said:
I can confirm it works.....
Flashed new dx9 after full wipe.
From recovery choose the cwm zip
From that touch cwm flashed aosp rom.
So it works just fine.
Click to expand...
Click to collapse
Oh cool, that's good to know, gracias...now i have plan B if the first doesn't work for me. Gracias
Hi ,
I am currently having 4.1.2 official on my SGH-I777, recently rooted it and have mobile odin lite installed.
Need CWM recovery installed so that i can flash SuperNexus2 rom. So i have downloaded recovery-clockwork-6.0.1.0-i777.zip file from clockworkmod dot com website . Can i flash it directly from the stock recovery which i have now? or any other safe method you can suggest.
In some thread, there was a mention to flash boot.sys file from other kernel using Mobile odin which will get cwm installed.
If this is the way to go, please suggest a safe Kernal. I am just looking to get a stable daily driver for now, as i dont have an alternate phone.
Thanks in advance
the stock recovery isn't good for much, so no, it won't allow you to directly flash the cwm recovery.
Once you're rooted and have mobile odin (&the odin i777 kernel) installed, you're halfway there.
http://forum.xda-developers.com/showthread.php?t=2452388
Happy flashing.
cyril279 said:
the stock recovery isn't good for much, so no, it won't allow you to directly flash the cwm recovery.
Once you're rooted and have mobile odin (&the odin i777 kernel) installed, you're halfway there.
http://forum.xda-developers.com/showthread.php?t=2452388
Happy flashing.
Click to expand...
Click to collapse
If i flash boot.img extracted from AJK, will i be able to boot into the stock 4.1.2 which i already have, or should i directly start proceeding with CWM and the new ROM, just want to make sure before i start.
...side note warning... Do not use Rom Manager with the i777. If ya do u could possibly brick ur phone. There is a Stickied thread in this forum warning of this.
....no back to the regularly scheduled topic.
skarthik21 said:
If i flash boot.img extracted from AJK, will i be able to boot into the stock 4.1.2 which i already have, or should i directly start proceeding with CWM and the new ROM, just want to make sure before i start.
Click to expand...
Click to collapse
I think the nomswap version will allow you to boot to stock 4.1.2, but I can't promise that, I've never tried it. You should prepare as though you won't be able to return once you hit [flash firmware] from Mobile Odin. It's all covered in the guide.
skarthik21 said:
If i flash boot.img extracted from AJK, will i be able to boot into the stock 4.1.2 which i already have, or should i directly start proceeding with CWM and the new ROM, just want to make sure before i start.
Click to expand...
Click to collapse
Yes, if you use AJK v4.8 NoSwap you will be able to boot into your 4.1.2 system.
Also, if you are new to the I777, you should know that the recovery, including CWM recovery, is a part of the kernel, and not in a separate partition, so it can not be flashed separately from the kernel.
creepyncrawly said:
Yes, if you use AJK v4.8 NoSwap you will be able to boot into your 4.1.2 system.
Also, if you are new to the I777, you should know that the recovery, including CWM recovery, is a part of the kernel, and not in a separate partition, so it can not be flashed separately from the kernel.
Click to expand...
Click to collapse
Thanks, guys i was able to flash noswap and was able to boot up into existing 4.1.2
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.