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
Related
I recently got a GSM gNex and last night I decided to upgrade to JB using the OTA links posted here in the forum. I unlocked the boot loader, flashed twrp's recovery, installed SuperSU and then the JB 4.1.1 OTA file and everything went smoothly. Since after the upgrade, on my PC when I connect my gNex, I'm getting a "Fast boot read error" and my PC stopped recognizing the device. I switched to my Mac and got everything I needed done. Why am I here? Obviously I've been able to go into twrp recovery to do a lot of this stuff. But now, anytime I try to go into recovery mode, I get the screen with android lying on back with the exclamation point. I have to flash recovery (I've tried CWM, CWM touch, optimus prime touch) using fast boot every time I have to go into recovery. I tried going to recovery using ROM manager and that gets me to same situation. (Android on back).
Any thoughts?
Sent from my Galaxy Nexus using xda app-developers app
verruckterGeck said:
I recently got a GSM gNex and last night I decided to upgrade to JB using the OTA links posted here in the forum. I unlocked the boot loader, flashed twrp's recovery, installed SuperSU and then the JB 4.1.1 OTA file and everything went smoothly. Since after the upgrade, on my PC when I connect my gNex, I'm getting a "Fast boot read error" and my PC stopped recognizing the device. I switched to my Mac and got everything I needed done. Why am I here? Obviously I've been able to go into twrp recovery to do a lot of this stuff. But now, anytime I try to go into recovery mode, I get the screen with android lying on back with the exclamation point. I have to flash recovery (I've tried CWM, CWM touch, optimus prime touch) using fast boot every time I have to go into recovery. I tried going to recovery using ROM manager and that gets me to same situation. (Android on back).
Any thoughts?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If 4.1.1 is anything like 4.0.x, you'll have to rename/remove this file: /system/etc/install-recovery.sh
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.
hey guys i have a bell i747 galaxy s3 and ive been trying to flash jelly bam without any sucess, many people suggested to try twrp recovery, well i tried it and still didnt work so i was wondering how i can go back to cwm recovery.... ive read that i must unroot and go back to stock is this the only way i have tried in the past using rom manager to go back to cwm but after that recovery couldn`t read any md5 files so any suggestions would help
thanks
DLM2583 said:
hey guys i have a bell i747 galaxy s3 and ive been trying to flash jelly bam without any sucess, many people suggested to try twrp recovery, well i tried it and still didnt work so i was wondering how i can go back to cwm recovery.... ive read that i must unroot and go back to stock is this the only way i have tried in the past using rom manager to go back to cwm but after that recovery couldn`t read any md5 files so any suggestions would help
thanks
Click to expand...
Click to collapse
Firstly, what's going wrong with the TWRP process? If you're getting a "status 7", and you flashed TWRP using Goomanager, you have a d2can TWRP image instead of a d2att TWRP image, which is causing the problem; go here for the d2att image and instructions for its use.
If you still want to go back to CWM after that, just flash a CWM image in the normal fashion; it will overwrite whatever recovery image you currently are using (TWRP in this case).
smelenchuk said:
Firstly, what's going wrong with the TWRP process? If you're getting a "status 7", and you flashed TWRP using Goomanager, you have a d2can TWRP image instead of a d2att TWRP image, which is causing the problem; go here for the d2att image and instructions for its use.
If you still want to go back to CWM after that, just flash a CWM image in the normal fashion; it will overwrite whatever recovery image you currently are using (TWRP in this case).
Click to expand...
Click to collapse
thanks for the fast respond, i have downloaded the openrecovery for d2att because your right thats exactly what happends when i try to load that rom,, well im still kinda noob to this and im not sure if i should use the adb shell too write this command or using the terminal emulator and if the android terminal emulator will work from the playstore........also not sure of where i should put the file in.. thanks
thanks so much for your help it worked woohoo|!|!!||!
DLM2583 said:
thanks so much for your help it worked woohoo|!|!!||!
Click to expand...
Click to collapse
For a woohoo!!!!! you should probably hit the thanks button too,I'll get it for you this time.lol
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I'm totally boggled here, I've never had problems like this. I've rooted my T-999, no problems there, but when I install CWM, either the non-touch or touch versions, it doesn't boot into that recovery. When you recovery boot, either manual or through ROM Manager, it just boots to the stock recovery. I've tried re-installing through ROM Manager and through Odin, to no avail. I'm pulling my hair out...help!
Just use the the root 66 method and then use goomanager to install twrp recovery. Did this process for my brothers S III last night over the phone.
I had the same problem before. Tried multiple ways but the cwm recovery will not stick, even though it appears working in Odin. Only way I got cwm recovery to install is by going back to an earlier version os.
You need to find an earlier version of factory stock jelly bean or better yet ics and flash it with Odin. Make sure it's a factory image. After that just root and install cwm recovery with Galaxy s3 toolkit. Then just install whatever rom you like.
Sent from my SGH-T889 using Tapatalk 2
Ok, trying out these methods and will report back. Thanks.
whatsitsnamenow said:
I had the same problem before. Tried multiple ways but the cwm recovery will not stick, even though it appears working in Odin. Only way I got cwm recovery to install is by going back to an earlier version os.
You need to find an earlier version of factory stock jelly bean or better yet ics and flash it with Odin. Make sure it's a factory image. After that just root and install cwm recovery with Galaxy s3 toolkit. Then just install whatever rom you like.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Why do all that when you can flash the latest through ODIN; and get the correct partition tables setup, and that has root, and then install the recovery via an app? Seems more logical to me.
mt3g said:
Why do all that when you can flash the latest through ODIN; and get the correct partition tables setup, and that has root, and then install the recovery via an app? Seems more logical to me.
Click to expand...
Click to collapse
I was not aware you can install the recovery through an app. I'm not familiar with the process so maybe you can talk the op through it.
When I had my problem with the cwm recovery not sticking from Odin, it was when the jelly bean update was just release for T-Mobile. Just letting the op know that I had the same problem and how I got it working.
Sent from my SGH-T889 using Tapatalk 2
Okay I thought I was missing something. Ya the new update surprised me as well last night with ODIN not working to flash a recovery. It's available in CWM app ROM manager I prefer TWRP though which is available in GooManager via menu>Install OpenRecoveryScript>yes> so long as it says "2.4.1.0" and "D2TMO" then yes and boot recovery to install from there.
I followed mt3g's advice and did the root66 method and then installed via ROM Manager and I had success. Flashing a new ROM now. Thanks!
Cool bro.
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