First time rooting. OG Droid FRG83G Build.
NOTE: i assure you i've utilized search feature but would not be surprised if this has been covered before and i missed it. apologies and thanks in advance.
having issues booting into CWM recovery. i'll retrace my steps:
successfully rooted via superoneclick
market->ROM Manager free
launch ROM manager
flash CWM recovery
backup current ROM
placed project elite v6.5 zip in SD root
(no issues thus far)
attempt to reboot into CWM recovery to wipe and install custom ROM: encountered first issue
will only boot into stock recovery. after a few attempts, rebooted normally and launched ROM manager, clicked flash CWM recovery again and then clicked boot into CWM recovery and this time it worked!
my question: when i clicked flash recovery the 2nd time what did that do relative to the backup i previously created? does it overwrite certain files/settings? should i have created another backup that corresponds to the 2nd flash?
even though i successfully booted into CWM recovery, i was scared there was an issue with my backup so i chose to reboot normally. i then proceeded to delete the clockworkmod folder from my SD, unmount, launch ROM Manager, re-performed: flash + backup to simulate the 1st time.
when trying to boot into CWM recovery i get the same issue as the first time: stock recovery mode.
are there any issues with me clicking flash and then booting into CWM recovery if a backup was previously created?
Thanks.
Related
Hey guys I've rom FROYO.XWJPA with ROOT and I want install CWM recovery from Rom Manager. Then i click Flash cwm recovery the operation is successful, but then I try reboot to cwm recovery my phene have still samsung recovery... what is wrong?
I had the same problem. I solved it by flashing an update.zip of the CWM recovery from the Samsung recovery. It worked by flashing two times, first time didn't work ^^
Pretty sure that ROM manager doesn't actually flash the recovery the way you think. It just allows you to boot into it from within the app. Open ROM manager up and try booting into it from there.
Or just install a kernel that has a built in CWM recovery.
Problem solved
Ok, in short I can't restore my rom after flashing Cyanogenmod 7 RC1. If I try to recover the phone remain locked in recovery mode.
That's the full story anyway:
Had a Galaxy S with Android 2.3.3 (Italy) rooted with CF-root
Made a backup with clockworkmod (no problem)
Made data/app backup with titanium backup (no problem)
Flashed Cyanogenmod 7 RC1 (no problem)
Restore Titaniun backup, have all my app back but had the first problem. None of my data has been restored, contacts, sms, calls... nothing. Why I ask?
Found that I can't access my sd card, read about the downgrade to froyo. Ok, time to restore to my original rom.
Made a restore of my nandroid backup, via rom manager.
BANG, phone hang up at boot on Galaxy S initial logo.
Ok, don't panic, restored an Eclair 2.1-u1 Rom via odin/download mode. Build XWJM7, Base XXJM3 (I read Flashing Eclair is safer)
Tried to update Android via Kies, but I get a message that my version cannot be upgraded.
Rooted Eclair via oneclickroot, installed rom manager/clockworkmod and tried again to restore my rom backup.
The restore seems to go Ok but the phone is stucked in recovery mode (2e). I get the Galaxy S logo for a few second, then logo disappear and reappear an phone go in recovery mode saying:
installing multi-csc
can't access to /system/csc/itv/system/
successfully applied multi-csc.
There is no way to go on, if I choose update.zip, phone go to clockworkmod recovery. Tried to restore an older backup, same result.
Now I'm again on Eclair.
So is there a way to have my original rom back via clockworkmod? Or I have to flash original CSC/MODEM/CODE via odin?
Thanks for helping.
I think your best choice is to flash from odin in download mode with a clean stock rom with re-partition to start again on a good base.
I made some other test.
Extracted the .img from cwm backup. The boot.img file is corrupted on both backup, file are identical so I though there's a problem backing up bootloader on my phone with cwm.
So I tried to recover all but boot. When I reboot (from eclair, cwm 2.5.1.2) in recovery mode I always get to android recovery 2e. As before if I select update.zip (and update is not present) system get me to cwm recovery. I select advanced restore and system ecc. but get the same problem the before: I get stucked in android recovery.
So again I flash via odin this time to gingerbread, rooted with cf-root, launch cwm manager tried for the last time to recover my damned backup.
And UA-TA! has my phone restored.
Any one has I idea why I was able to restore my rom (and app/data) only AFTER I restored my rom in another way?
I also made backup but it was giving error when i try to restor it
dadyal said:
I also made backup but it was giving error when i try to restor it
Click to expand...
Click to collapse
What error do you get?
I have CWM 4.00.15 installed and I tried to install Ryyu's Rom (Wipe) by putting it on the SD card and rebooting into recovery, then selecting the zip file and hitting apply. When the installation tried to update my kernel, it just froze and rebooted. I was then stuck on a boot loop between the Galaxy S screen and the CyanogenMod boot screen. I know that Ryyu's did not install correctly because the CyanogenMod boot screen was still there. I had to use 3 button recovery and erase cache, davlik cache and user data before trying to install AOSP Essence, but same problem happened. Installation dies and phone keeps rebooting in loops. Finally, gave up and went back to CyanogenMod Nightly and it worked.
Why can't I seem to install any other ROMs besides Cyanogen? I know I am doing something wrong, but not sure what. Any advice/help appreciated. Thanks.
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Br1g0 said:
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Click to expand...
Click to collapse
Hi,
this is what I initially did to get Cyanogen on:
1. Used Superoneclick root to root phone
2. Check that 3 button recovery and download mode works. Recovery version was 3e, so installed superlagfix from android market. This automatically installed ClockworkMod Recovery as well.
3. Use CWM and flashed recovery for Samsung Galaxy S i9000
4. Reboot into recovery and select the CyanogenMod zip file and click apply to install.
To install subsequent ROMs, I just put the zip file on my SD card, reboot into recovery and repeat step 4 above, after clearing cache and user data. It is after that I get stuck on boot loops.
I did do a Nandroid backup before my initial Cyanogen install so I can go back and restore it, but it would be Froyo.
when coming from CM / MIUI - Samsung based ROM
you MUST flash a 3 file firmware with pit and re-partition.
Cyanogen and MIUI use different partitions than samsung ROMs so this is why you are having issues.
Ok, just managed to flash Darky's EE 10.2 using Odin. Not sure if Odin is the ideal way, but it worked. Really enjoying Darky's. Thanks folks!
Hello,
I've been running stock rooted 4.1.2 for a while but my phone randomly reformatted itself last night so now I'm going to keep regular backups of my Rom.
I tried to boot into. CWM Recovery but I keep getting the stock recovery.. if I use Rom manager and flash CWM followed by an automated "reboot into recovery" then it boots into CWM but until I reflash CWM within Rom manager I can only get stock.
I want to try a few roms out so I'd like to "permanently" flash a custom recovery before making a backup!
iamtherealmungo said:
Hello,
I've been running stock rooted 4.1.2 for a while but my phone randomly reformatted itself last night so now I'm going to keep regular backups of my Rom.
I tried to boot into. CWM Recovery but I keep getting the stock recovery.. if I use Rom manager and flash CWM followed by an automated "reboot into recovery" then it boots into CWM but until I reflash CWM within Rom manager I can only get stock.
I want to try a few roms out so I'd like to "permanently" flash a custom recovery before making a backup!
Click to expand...
Click to collapse
try philz touch, it has a function to remove the auto-flash stock recovery. Otherwise there's a method in the general root thread if you want cwm.
Evening guys,
so 2 days ago I flashed the Philz Recovery for testing. While I had the recovery on I flashed the latest Nightly of the Slim Kat Rom + Cyodak Kernel also for testing.
Ofc I backed up my files be4 doing so. Today I just recovered my backup, went to recovery again but the Philz recovery was still there. '''kk no prob i thought,
just flash the CWM Touch recovery again'' so I did, rebooted back into recovery mode and what happened? Instead of booting into the cwm recovery, there's
still the philz recovery. While in philz on the bottom left it shows "Philz Touch 6.48.4 and ClockworkMod v6.0.5.0" So no Idea what to do and it gets frustrating tho..
Thx in advance .
You didn't flash CWM again, or not properly, unless you wouldn't have PhilZ still.
well there's nothing much I could do wrong. Reboot into Recovery -> Install Zip from ext. SD -> choose the CWM Recovery -> Install -> Reboot into Recovery and CWM should be there right?
Also i've tried to restore the backup which I made be4 installing the Philz recovery. Backup was a success but once i'll boot into recovery it's the philz recovery again.
Backups do not contain recovery.
rly? Cuz my backup backups also the boot.img + the recovery. Anyway what am I going to do now? I've tried several ways, even flashing the TWRP as a zip, flashing via flashify or Rom Manager, no matter what I do I always end up in the philz recovery even when it says flash successfull.
K4iZEN said:
rly? Cuz my backup backups also the boot.img + the recovery. Anyway what am I going to do now? I've tried several ways, even flashing the TWRP as a zip, flashing via flashify or Rom Manager, no matter what I do I always end up in the philz recovery even when it says flash successfull.
Click to expand...
Click to collapse
You can use fastboot to flash recovery.