[Q] [Problem][CWM Touch-6.0.2.7][Not Installing] - Galaxy S III Q&A, Help & Troubleshooting

Hello people....
I am new to SGS3 xda forum....i am from Pakistan...its been 2 weeks since i bought a SGS3 (second hand)...probably of 3mobile U.K...i was told by the seller that the phone was unlocked in Pakistan....as i tried system update from settings...it said that my phone was modified and could not be updated....so i decided to install CWM Touch on my SGS3 in order to create backup of my current stock ROM (4.1.1)...my phone is not rooted yet....i followed the instructions given in the following link:
http://jellybean-news.blogspot.com/2013/02/complete-guide-to-install-clockworkmod.html
Odin took 1 second and my phone was booted....Odin gave the Message ''Pass!''...everything went fine as it should have been...but when i went into the recovery mod...Stock Android Recovery is opening instead of CWM Touch....noting my phone is not rooted yet....it is also normally booting and everything is fine....can anybody guide me about the problem that i am currently facing...and its solution as well....?? Help Would Be Appreciated...
Edit:Just Flashed CF-Root Pakcage Including SuperSU and CWM Manager with CWM v5.5.0.4....now it goes into CWM...but still one noob question....have my previous stock android recovery and CWM Touch been automatically deleted/replaced?...or they still exist?? Thanks

Sounds like you were trying to install a cwm without being rooted.
Cwm replaces the stock android recovery. You could now try flashing the cwm touch through your current cwm. Make sure its a zip. If you come and ask for help You should really follow a guide on xda though. They are the best guides around.

Shehram Ahmad said:
Edit:Just Flashed CF-Root Pakcage Including SuperSU and CWM Manager with CWM v5.5.0.4....now it goes into CWM...but still one noob question....have my previous stock android recovery and CWM Touch been automatically deleted/replaced?...or they still exist?? Thanks
Click to expand...
Click to collapse
When you flash a recovery you will delete the previous recovery in doing so, your stock and touch are both gone - replaced with v5.5.0.4.
You can now boot into CWM and install a better recovery, try Philz touch recovery for instance.

Related

[Q] CF-root to ClockworkMod (for cyanogenmod), and non-responsive launcher

Hi all,
I rooted my SGS2 (KE7) with CF-Root ages ago and haven't done much since then, aside from take regular backups.
Looking at the Cyanogenmod stuff, I fancy giving it a go. All the guides talk about using the kernel at http://forum.xda-developers.com/showthread.php?t=1118693 .
Does anyone know if I can flash the cyanogenmod ROM using the recovery mode I have with CF-Root, or if I need to get use the kernel from the above patch first?
This morning I tried installing the kernel (from the CF-Root CWM), when my phone rebooted, the touchscreen worked on the unlock page but not once I unlocked (I use LauncherPro as my launcher). Rebooting into recovery mode didn't work (the phone just booted normally) so I reflashed CF-Root but still had the same problem however I could boot into recovery mode and restore this morning's backup.
Now, the phone boots (with the warning triangle, expected) but there is no response after I unlock for a minute or so. Setting the stock launcher back works but I'm confused about why this should happen and what I should do next.
Does anyone know why my non-stock launcher is now being non-responsive for the first minute after boot / what I can do to get it back?
Am I able to install cyanogen with CF-root, or do I need to use the kernel in the above link? and if so, do I need to do anything other than just flash and if not why didn't the phone boot into recovery when I tried it earlier?
Any suggestions gratefully received!
-Jeff
The cf-root kernel is all you need to install cm7.
peachpuff said:
The cf-root kernel is all you need to install cm7.
Click to expand...
Click to collapse
This is correct. However, after you install the cm7 .zip the first time, it will have only installed the kernel for cyanogen mod. So you will then need to boot back into recovery with 3 button mode and run the zip install again from there. You will then have CM7.
Electroz said:
This is correct. However, after you install the cm7 .zip the first time, it will have only installed the kernel for cyanogen mod. So you will then need to boot back into recovery with 3 button mode and run the zip install again from there. You will then have CM7.
Click to expand...
Click to collapse
Don't quite understand this. I've got the cm_galaxys2_full-39.zip (100MB), I was going to put this on the SD card, boot into recovery mode and install from there. Are you saying I need to do this same process twice? (and if so, why does it only install the kernel the first time when it is the complete zip file?)
Cheers,
-Jeff
CF-root => Cyanogen mod
Hello everybody,
There are a few threads that discuss this question, but they all draw a different conclusion.
This one for instance : http://forum.xda-developers.com/showthread.php?t=1367933 (or if the link is broken, search for : How can i use cf-root kernel for cm7?).
In the thread above they claim that CF-root is not compatible with CM7, however in this very thread there is said that when installing the .zip file twice, it should work just fine. As i'd like to install CM7 on my CF-rooted S2, i have to know for sure:
Is there a way to install CM7 on a CF-rooted device?
Many thanks
Rom manager doesnt work with cf root, so to flash cm7 download the zip, boot into recovery, and flash the zip twice, and it will work.
Make sure you wipe data and cache, and take backups before you do.
Sent from my GT-I9100 using Tapatalk
Ok, i'll give it a go .
Thanks for the quick response, it is much appreciated!

[Q] Cannot install Cyanogen... Confused with all the infos!!

I know it's been adressed many times in different ways, but the info I found yet is not clear so I need a little help! I am trying to install the latest stable Cyanogen mod, using Gingerbread 2.3.7.
I have a Galaxy SII from Bell that I rooted and unlocked when I got it last november. It came on 2.3.3 and I flashed an official 2.3.4 on it, mainly to improve the battery life (and it worked). I did that using Odin and it went well.
Now I try to install Cyanogen mod through ClockworkMod ROM manager, I download and launch the install from ROM manager but on restart the install fails because of the classic 3E recovery message that says the whole signature cannot be verified.
I was having doubts if my phone was even rooted, but since it is still unlocked and software like Titanium backup runs fine, I guess that confirms it!! I am not sure what route to take from here...
Right now here are the phone details...
GT-i9100 on 2.3.4, FW I9100XXKG2, Kernet 2.6.35.7-I9100XXKG2-CL375027 [email protected] #2
I'll appreciate any help!!!!!!
JFChamp said:
Now I try to install Cyanogen mod through ClockworkMod ROM manager, I download and launch the install from ROM manager but on restart the install fails because of the classic 3E recovery message that says the whole signature cannot be verified.
|Question = Q&A
Looks like you are yet another that has not followed the instructions and flashed a cwm and root kernel .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
OR are not following the instructions posted .
First time flashing CyanogenMod 7 to the Samsung Galaxy S II, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Clockwork mod recovery see
NEW HERE
http://forum.xda-developers.com/showthread.php?t=1134290
The instructions work as i have just installed by following the instructions in reply to an exact same post .
jje
Click to expand...
Click to collapse
Thanks jje... The instructions did work! Tough I tought I had bricked my phone at one point, on the final restart it would get stuck at the Samsung logon screen, but I forced it back in recovery, re-flashed from the zip and then it booted in CyanogenMod!!!
I really appreciate your reply

[Q] Reboot returns me to stock recovery

Hey there, I'm trying to root my S3 and a first step I wanted to make a nandroid backup, so i downloaded Odin and I used it to install recovery-clockwork-touch-6.0.1.0-i9300 onto my device, i rebooted into the recovery screen and I found myself in the stock recovery menu.
So i tried it once more, to no change in my situation, so I looked through the forums for a while and I found a thread by mskip about installing CWM and thankfully it had this
Stock Recovery being reflashed after a reboot?
There is an auto recovery restore system on stock roms that will reflash the Stock Recovery on a Stock Rom. If the restore files are renamed then CWM Recovery should not be overwritten after a reboot.
You need to be rooted and then delete or rename the following files:
Quote:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
You can then flash recovery without it being overwritten.
You can also do all this through the S3 ToolKit
**All credit goes to to Koush and anyone else responsible for ClockworkMod**
Click to expand...
Click to collapse
My problem being that I can't rename said files bacause my phone isn't rooted and the S3 toolkit requires rooting to do backups and such, and I can't root it because (unless I misunderstood) I need CWM installed.
So my question is : What can I do now? Can I root my phone in any other way ? Is there a way to get past this Stock recovery screen onto CWM?
Already thanks for reading and sorry for it being this long
Also I have a Samsung Galaxy S3 GT-I9300 I have Android 4.1.1 And I run Windows 7 on my PC
Ok, so I looked around a bit and I just rooted it without a backup, it seemed safe enough.
Root went well, I backed up right after just in case.
Use cf root and flash via Odin that will give you root and flash cwm. Then you can continue with your nandroid backup. All though you can do the full root procedure using that toolkit, its one of the options. Hope I could help
Sent From My Omega'd Galaxy S3 ...

[Q] S3-I9300 - boot loop and not getting into recovery!!!

Dear All,
I'm from India and I was on stock 4.1.2. Since I didn't want to root my phone, I installed cwm through odin and then installed philz touch recovery 6.00.8 and installed Neatrom lite v4.8. Everything was normal till today and I wanted to install the full version of neatrom(4.1.2), so I booted into recovery, but suddenly I'm getting into boot loop and not able to enter neither the recovery nor the phone. But I'm able to get into download mode... Please help!!!!! I didn't do anything except this.....:crying:
Dear All,
I reflashed cwm touch thru odin again and was able to get the phone working again!!! so, does the latest version of philz touch cwm is having any issues??? I'm not sure, if this is the right thread to be asked about this!!!!!
This is a commonly answered question. Please search before making a new thread. Glad that you fixed your phone. Make sure the rom you are trying to install is spefically for your phone. If there are any issues in philz touch you can find them at http://forum.xda-developers.com/showthread.php?t=2002953

[Q] Android System Recovery 3e

Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.

Categories

Resources