I was getting bored of my old rom, so i decided to install another one via CWM. When i went into recovery mode, i chose to do a factory reset. When the operation starts, my phone freezes at "Formatting /data..." and i need to take out the battery and try again. Is this common? Is there even a fix to this? For the rom I am trying to use, Android 4.2.2 Liquid Smooth, I need to reset in order to get past the boot logo.
I would try TWRP instead of that CWM. CWM only gives me as well as others issues; however, some people have no trouble at all with it.
Gorostone123 said:
I was getting bored of my old rom, so i decided to install another one via CWM. When i went into recovery mode, i chose to do a factory reset. When the operation starts, my phone freezes at "Formatting /data..." and i need to take out the battery and try again. Is this common? Is there even a fix to this? For the rom I am trying to use, Android 4.2.2 Liquid Smooth, I need to reset in order to get past the boot logo.
Click to expand...
Click to collapse
Down load goomanager then install twrp through goomanager. It will be way better than cwm.
Sent from my SGH-I747 using xda premium
seko666 said:
Down load goomanager then install twrp through goomanager. It will be way better than cwm.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
THanks alot! that really helped me, i like teamwin a lot better than CWM... I never tried TWRM because all i heard about was clockwork
Related
Hey guys I'm new to the forum so please tolerate my lack of knowledge. I've already flashed a few s3's with roms, so I'm familiar with process. I bought another s3, installed cwm recovery with odin, and then went into recovery and flashed su. Rebooted and made sure it was rooted.
I then did something different, which was updated to newer cwm recovery using rom manager. I rebooted into recovery using rom manager. I went through all steps and flashed darthstalker v3 (I've already flashed this on other s3's successfully many times). I rebooted system, but instead of booting into rom it keeps booting back into recovery (cwm, not android recovery). I can get into download mode and flash stock rom with odin. I tried repeating process and used twrp instead of cwm, but still can't boot into rom. It keeps rebooting into recovery (cwm or twrp). Any suggestions? Thanks in advance!
Sent from my SGH-T999 using Tapatalk 2
Does it do it with only that rom?
Sent from my SGH-T999
Have you tried clearing cache/davlik/data?
elmatador1973 said:
Hey guys I'm new to the forum so please tolerate my lack of knowledge. I've already flashed a few s3's with roms, so I'm familiar with process. I bought another s3, installed cwm recovery with odin, and then went into recovery and flashed su. Rebooted and made sure it was rooted.
I then did something different, which was updated to newer cwm recovery using rom manager. I rebooted into recovery using rom manager. I went through all steps and flashed darthstalker v3 (I've already flashed this on other s3's successfully many times). I rebooted system, but instead of booting into rom it keeps booting back into recovery (cwm, not android recovery). I can get into download mode and flash stock rom with odin. I tried repeating process and used twrp instead of cwm, but still can't boot into rom. It keeps rebooting into recovery (cwm or twrp). Any suggestions? Thanks in advance!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Try completely wiping your phone then PC Odin using root66 in download mode. Afterwards, let the phone sit for 15 minutes. Reboot the phone then download and install GooManager from the Play Store. Open the application and press the menu button to access the options. Press 'install openrecovery' and go through the installation process. You should now have no issue with your device.
Sent from my SGH-T999 using xda app-developers app
chrisram88 said:
Does it do it with only that rom?
Sent from my SGH-T999
Click to expand...
Click to collapse
I haven't tried it with a different rom, but I've repeated this process with different roms on several s3's. Only thing I did different was install cwm from rom manager. Thnx
se1000 said:
Have you tried clearing cache/davlik/data?
Click to expand...
Click to collapse
Yes, before and after rom installation. Problem remains.
Noobiologist said:
Try completely wiping your phone then PC Odin using root66 in download mode. Afterwards, let the phone sit for 15 minutes. Reboot the phone then download and install GooManager from the Play Store. Open the application and press the menu button to access the options. Press 'install openrecovery' and go through the installation process. You should now have no issue with your device.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Will try that tomorrow. I got hasty and hardbricked it ((. Foolishly flashed exitrecovery.zip, not realizing it was only for LG! Getting it unbricked tomorrow, and will try your suggestion. Thnx.
Hi guys,
I'm having some issues with my phone. I am using ClockworkMod 5.0.2.7 as my recovery. Here is what happened:
I was running the stable version of CM10 (10.0.0). I was having issues with random reboots and it was really laggy sometimes. To try and fix this, I wiped data, cache, davlik, and fixed permissions. After I did this, my phone was stuck in a bootloop. I couldn't get past the cyanogenmod loading screen. I booted into recovery, and restored my phone to a previous CM10 nightly that I had a backup of.
I then tried to flash CM10 again (10.0.0). I followed the steps here (note i did not use the dirty flash method):
http://forum.xda-developers.com/showthread.php?t=1926754
Once I tried to boot, I was still stuck in a boot loop. So I recovered again to the CM 10 nightly. Now I was using the CM 10 nightly fine, and I was playing a game and the phone froze. I pulled the battery and when I rebooted, I could never get past the cyanogenmod loading screen. So I booted into recovery again. Before I restored again, I saw this error on the bottom:
E: error in /cache/recovery/last_log
I was still able to recover to the CM 10 nightly, and I have since rebooted my phone and it was fine (although it did take longer than normal to boot back up).
So I'm wondering if my recovery has become corrupted? I don't really know what I should do next. Any help would be appreciated.
Thanks.
Odin flash CWM, then flash TWRP, and ditch the scripts.
TWRP 2.3.1.1
LoopDoGG79 said:
Odin flash CWM, then flash TWRP, and ditch the scripts.
TWRP 2.3.1.1
Click to expand...
Click to collapse
Thanks for the reply. Should I flash the same version of CWM that I'm using now (5.0.2.7)? Or does that not matter?
Also, should we always be using TWRP instead of CWM? I have never used that before.
kwstryk3r said:
Thanks for the reply. Should I flash the same version of CWM that I'm using now (5.0.2.7)? Or does that not matter?
Also, should we always be using TWRP instead of CWM? I have never used that before.
Click to expand...
Click to collapse
If you can flash, then just flash the file I provided. TWRP is more stable and used friendly. Ptmr3 recommendeds it. Just flash, reboot recovery and your good!! :thumbup:
LoopDoGG79 said:
If you can flash, then just flash the file I provided. TWRP is more stable and used friendly. Ptmr3 recommendeds it. Just flash, reboot recovery and your good!! :thumbup:
Click to expand...
Click to collapse
This would work too right? I don't really trust my CWM since it didn't work when I flashed CM10
http://forum.xda-developers.com/showthread.php?p=26200755
kwstryk3r said:
This would work too right? I don't really trust my CWM since it didn't work when I flashed CM10
http://forum.xda-developers.com/showthread.php?p=26200755
Click to expand...
Click to collapse
Yes, but, you have to use the image file, and be sure to rename it to the proper name. The TWRP image thru the TWRP website. Just double check its for our phone!!
If you want to keep using cwm, then you have to use darksidecachewipe after flashing, right before you reboot from cwm. The darksidesuperwipe script is used to factory wipe.
So before you leave cwm recovery screen flash DScachewipe zip, and should boot fine.
Loop dog is right, go to twrp recovery. Nice UI and no need for wipe scripts.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Thanks for the help guys. Has anyone installed TWRP using Goo Manager? The whole idea of Goo Manager sounds awesome, but one bug on their end would be bad for us.
I've used GooManager to install TWRP on numerous occasions. It has always worked great for upgrading to the latest version, replacing CWM with TWRP, etc.
I have had my GS4 for a few days now. Its rooted and running DarthStalker. When I reboot the phone esp from TWRP it just gets stuck on the GS4 screen. Its most of the time sometimes when I reboot from the screen it fixes it self, Or do a full wipe. Do I have to odin stock again? I got it working by full wiping DarthStalker and reinstalling again.
I had this issue too, i even tried to use cwm and see if that fixed the problem but it wouldnt even boot doing a full wipe, i odined back to stock and rerooted , installed twrp and i have no problems now.
unciviilized said:
I had this issue too, i even tried to use cwm and see if that fixed the problem but it wouldnt even boot doing a full wipe, i odined back to stock and rerooted , installed twrp and i have no problems now.
Click to expand...
Click to collapse
Issue has been experienced here as well. I may reinstall twrp if it continues and re-root if it continues after that. Good to hear its not just me
C.Sweat said:
Issue has been experienced here as well. I may reinstall twrp if it continues and re-root if it continues after that. Good to hear its not just me
Click to expand...
Click to collapse
I dont think it would do any good, after installing cwm i couldnt do anything just boot into recovery. So to get it running i pushed twrp .tar file thru odin but still had to fully wipe everytime i reboot it. So i just odined to stock. I was a little scared as a week before i had hard bricked an S3.
re: bootup issues
unciviilized said:
I dont think it would do any good, after installing cwm i couldnt do anything just boot into recovery. So to get it running i pushed twrp .tar file thru odin but still had to fully wipe everytime i reboot it. So i just odined to stock. I was a little scared as a week before i had hard bricked an S3.
Click to expand...
Click to collapse
Next time you have problems booting up normally or have bootloops for whatever reason, do a "factory reset"
in either cwm or twrp and nine out of ten times after doing that the phone will boot normally.
Misterjunky said:
Next time you have problems booting up normally or have bootloops for whatever reason, do a "factory reset"
in either cwm or twrp and nine out of ten times after doing that the phone will boot normally.
Click to expand...
Click to collapse
it didnt work for me, you even replied to my thread suggesting the same method.
I can't say I've ever been stuck on the Samsung logo, but I can't count how many times I've gotten hung up on the TWRP splash screen. :\
lordcheeto03 said:
I can't say I've ever been stuck on the Samsung logo, but I can't count how many times I've gotten hung up on the TWRP splash screen. :\
Click to expand...
Click to collapse
Yeah i still get that from time to time, still buggy.
Sent from my SGH-M919 using Tapatalk 2
Use this and you won't have anymore problem.http://forum.xda-developers.com/showthread.php?t=2281367
flash the zip in recovery.
So, I decided to root my wifes Galaxy S2 due to it being a little older and to get more out of it for her, however I seem to have got my self stuck in a bootloop.
-Downloaded Odin, flashed CWM recovery and rooted phone all relatively easy and with no issues. However I wanted to get CM 10.1.2 stable cuase thats what i run on my Nexus 4. Before i flashed, i ran a Nandroid backup from cwm and did a wipe data/factory reset and rebooted. this is where i got the boot loop, on the T-mobile screen. Tried restoring from the back up, and still boot looped. tried flashing CM and it boot looped on the CM splash screen. On the CM forum it seems someone else had this issue and that kinda how i got pointed here. CM Admin suggested downloading an updated Bootloader. I honestly looked all over this site and couldnt find ANYTHING. I can still get into Download mode, and Recovery mode with no issues.
Thanks for your time
CWM v 5.0.2.6
Samsung T989 (JB 4.1.2)
Rooted
EgoTrip26 said:
So, I decided to root my wifes Galaxy S2 due to it being a little older and to get more out of it for her, however I seem to have got my self stuck in a bootloop.
-Downloaded Odin, flashed CWM recovery and rooted phone all relatively easy and with no issues. However I wanted to get CM 10.1.2 stable cuase thats what i run on my Nexus 4. Before i flashed, i ran a Nandroid backup from cwm and did a wipe data/factory reset and rebooted. this is where i got the boot loop, on the T-mobile screen. Tried restoring from the back up, and still boot looped. tried flashing CM and it boot looped on the CM splash screen. On the CM forum it seems someone else had this issue and that kinda how i got pointed here. CM Admin suggested downloading an updated Bootloader. I honestly looked all over this site and couldnt find ANYTHING. I can still get into Download mode, and Recovery mode with no issues.
Thanks for your time
CWM v 5.0.2.6
Samsung T989 (JB 4.1.2)
Rooted
Click to expand...
Click to collapse
U need to flash the newest twrp recovery, a lot of ppl have been having issues with cwm lately so my advice would be to DL the twrp tar file and use that to root and not cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
soupysoup said:
U need to flash the newest twrp recovery, a lot of ppl have been having issues with cwm lately so my advice would be to DL the twrp tar file and use that to root and not cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I will try that, I use TWRP for my Nexus 4. That being said, do i have to go back to stock and unroot, or just flash TWRP and attempt to install CM?
EgoTrip26 said:
I will try that, I use TWRP for my Nexus 4. That being said, do i have to go back to stock and unroot, or just flash TWRP and attempt to install CM?
Click to expand...
Click to collapse
Just flash recovery then cm rom.
Sent from my SGH-M919 using Tapatalk 2
Thanks a million!
Thanks to both of you for prompt response, Used TWRP and at least got CM to flash and startup, so far so good. hope it works as well on the S2 as it does on my phone!
Thanks again
Hi guys, I managed to do something I've never heard of. To be fair, I try to follow directions pretty well, so I don't screw things up too often, and I'm not sure what to do now. Any help or guidance would be appreciated.
The symptom is that the phone will boot witht eh Samsung boot animation, I will see the Clockworkmod icon at the bottom, some Clockworkmod version information, then the phone will reboot. This will happen presumably indefinitely. I have watched it do it 3 times in a row and then pulled the battery. Post Philz, I get Android tablet icons instead of Clockworkmod icon and version info.
I loaded Whompasaurus http://forum.xda-developers.com/showthread.php?t=2039564 to my phone yesterday and I was about to load Venom http://forum.xda-developers.com/showthread.php?t=2121063 to my phone this morning (I had just copied it to the SD card). I told the phone to reboot into recovery by pressing the power button and selecting the option "reboot, recovery". The phone is now stuck rebooting attempting to enter recover and failing, or so it appears. I upgraded the Clockworkmod version to 6.0.4.3 yesterday, and that did act a little weird in my opinion, but since I had never done that before, I wasn't sure what to expect.
When I told it to upgrade in the Clockworkmod app, the phone powered off and I had to remove the battery to turn it back on. I booted to recovery and it said it was now at 6.0.4.3, so I booted normally. Back in the app it said it was 5.something. I kept poking around and it eventually asked for root access, which it hadn't before, and when I told it to upgrade the recovery this time, it actually rebotted the phone rather than turn it off.
I reflashed the CWM 6.0.4.3 recovery with Heimdall per these instructions (why aren't there proper instructions for Odin?!?!?! ermahgerd!!) via this link http://wiki.cyanogenmod.org/w/Install_CM_for_l900
That was successful but did not affect the symptoms.
I upgraded to Philz recovery thinking maybe I had to use a different recovery to reset the "boot to recovery" flag. I used this file and Odin, after resetting the Samsung driver: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900/philz_touch_6.26.6-l900.tar.md5
The process was successful, but did not change the symptoms. Instead of seeing a Clockworkmod icon and version info at the bottom, I see what looks like android icons at the bottom, and then the phone reboots.
What can I do to fix my phone? I can boot to downloader mode fine. I would prefer to use Odin, but it seems I have Heimdall set up and working too.
Try using Odin to glad twrp 2.6.x then if it works try flashing your desired recovery from recovery
Sent from my SPH-L900 using XDA Premium 4 mobile app
Team Win FTW!!! That fixed it!
jlmancuso said:
Try using Odin to glad twrp 2.6.x then if it works try flashing your desired recovery from recovery
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is there something special about 2.6.x? I saw that there's a 2.7.x available now. 2.6.x doesn't seem to like my 64GB SD card, or maybe something else is going on. I factory reset a few times and will upgrade to the latest TWRP and try to flash that latest Venom ROM now and see what happens.
*Edit* No, there's SDCARD, SDCARD1, and EXTERNAL_SDCARD and I didn't check all of them, that's all. Oy, oy, oy.... But I'm up to 2.7 and installing Venom now....
Are asking for ROM recommendations still a no-no?
Yeah still pretty much a no no. I have used all the roms here and they are all pretty good.
Now I do suggest that you flash philz 6.07.9 for your recovery. First is that it properly flashes 4.4 and TW 4.3 roms. Second it makes proper backups. Twrp still has issues with aosp 4.4 and TW 4.3.
Sent from my SPH-L900 using XDA Premium 4 mobile app