Related
fixed...sorry...
Thanks for starting this thread. When i do a search for "bootloop" all threads have at least 500 postings and i really don't want to spend all day trying to find the part that pertains to this.
I've tried and tried to flash an ics rom (any ics rom) and today decided to flash cm9 stable. Still the same problem...stuck in a bootloop.
Btw. I always clear all 3 caches 3-5 times.
I would assume my problem is with ROM Manager/ because when I go back and load my backup, it says the md5 sum is missing or doesn't match. I'm a;lways able to find one of my backups that match. Any suggestions?
T-Mobile
CWM Recovery 5.0.2.7
Dewizzed V2.5.2
Kernel Version 2.6.35.14
Android2.3.6
If you have access to a computer, download the ROM you want to flash, and if you can boot into recovery on your phone do that and mount your sd card. You should be able to move the file via USB to your phone and flash it.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
...
Estimated Prophet Hawk said:
Thanks for starting this thread. When i do a search for "bootloop" all threads have at least 500 postings and i really don't want to spend all day trying to find the part that pertains to this.
I've tried and tried to flash an ics rom (any ics rom) and today decided to flash cm9 stable. Still the same problem...stuck in a bootloop.
Btw. I always clear all 3 caches 3-5 times.
I would assume my problem is with ROM Manager/ because when I go back and load my backup, it says the md5 sum is missing or doesn't match. I'm a;lways able to find one of my backups that match. Any suggestions?
T-Mobile
CWM Recovery 5.0.2.7
Dewizzed V2.5.2
Kernel Version 2.6.35.14
Android2.3.6
Click to expand...
Click to collapse
You should just backup ur phone up using ur recovery...thats what people mean when they say nandroid...
phordych05 said:
You should just backup ur phone up using ur recovery...thats what people mean when they say nandroid...
Click to expand...
Click to collapse
Unfortunately CWM won't do a reliable backup. With my Nexus One I never had these problems. I flashed countless ROM's from ROM Manager.
---------- Post added at 06:46 PM ---------- Previous post was at 06:27 PM ----------
RTFOP said:
If you have access to a computer, download the ROM you want to flash, and if you can boot into recovery on your phone do that and mount your sd card. You should be able to move the file via USB to your phone and flash it.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Downloaded CM 9.0.0 to PC, Rebooted into Recovery, connected to PC, Mounted USB, Dragged and dropped zip to SD card, wiped all three caches 3 times, installed zip from SD Card via CWM (should I use amon ra?), rebooted phone.....bootloop.
Estimated Prophet Hawk said:
Unfortunately CWM won't do a reliable backup. With my Nexus One I never had these problems. I flashed countless ROM's from ROM Manager.
Click to expand...
Click to collapse
so you think rom manager is better then cwm....really...?... ive never had a problem and im a flashaholic... but did you try a different kernel...?and you did a cache wipe after you rebooted the first time...?
phordych05 said:
so you think rom manager is better then cwm....really...?... ive never had a problem and im a flashaholic... but did you try a different kernel...?and you did a cache wipe after you rebooted the first time...?
Click to expand...
Click to collapse
I Thanks for the input. Not sure what the question is inferring. CWM is a recovery. Rom Manager isn't, but it only works (to my knowlege) with CWM.
Anyway. I'm looking for help.
Estimated Prophet Hawk said:
I Thanks for the input. Not sure what the question is inferring. CWM is a recovery. Rom Manager isn't, but it only works (to my knowlege) with CWM.
Anyway. I'm looking for help.
Click to expand...
Click to collapse
What recovery are you using? It is a known issue when flashing CM9, if you use non-touch recovery and you use it to wipe your cache partition, you will hang during boot. Download TDJ,s cache wipe script to the same sd card as your ROM. After your done flashing CM9 & Gaaps, flash his cache wipe script as your last step, and you should be able to boot up. His scripts are stickied. Some say they don't have this issue, but a lot do and can't get past the booty screen. Good luck and let us know.
Thanks for the help. I just flashed CWM Touch and it solved the problem. I'm now rockin' CM 9.0!
I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Same issue with Clockworkmod Recovery
Sorry to say I can't answer your question, but actually just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
I hate to say it but... use TWRP. It looks and works better. Trust me.
Sent from my SGH-T989 using xda app-developers app
whatiznt said:
I hate to say it but... use TWRP. It looks and works better. Trust me.
Click to expand...
Click to collapse
I trust you but on the Team Win Recovery Project's changelog you can see that it has not been updated in almost a year! CWM is updated much more frequently and also I enjoy having the touch version! Very convenient.
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
jalight27 said:
Just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
Click to expand...
Click to collapse
Thank you my friend. What you describe is exactly what happened to me. Tell me, what version of CWM Recovery do you have? Were you coming from stock? Which CM9 was it? Nightly, stable?
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Please pardon my ignorance as I am relatively new at all this. How do you downgrade CWM? I am unable to boot the phone into the ROM. Can it be done through Recovery? ODIN?
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Same version as you've got. Was actually coming from Jedi Mind Trick v8 and was going with the nighty. I loaded a backup of my stock ICS, which of course froze during the restore once it got to the cache, but I let it sit for like 15 min or so and then reset it and surprisingly it loaded up fine despite the fact that I had to reset it during the restore. I'm trying to follow up with the advice these two guys gave me on my post (really the same thing they've told you). With my extremely limited knowledge in this field I'm still working it all out and trying to make sure I ask the stupid questions so as not to mess anything up, well at least not too bad, lol.
mintharis said:
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Click to expand...
Click to collapse
Go into rom manager and scroll down to previous versions
VoiD_Dweller said:
Go into rom manager and scroll down to previous versions
Click to expand...
Click to collapse
I don't have ROM manager installed. Does it provide a tar that can be flashed via Odin?
Newer Recovery
Clockworkmod 6 doesn't need the Darkside tools anymore. I had a similar problem but it was causing my phone to lock up. Just try using the regular cache wipe and dalvik cache wipe and see if that works for you.
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Pugnap00 said:
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Click to expand...
Click to collapse
Can you please provide a link for the 5.0.2.7 tar you flashed?
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
CWM v6.0.1.4 has pretty much made my phone useless. When in Recovery I can't even scroll down or up. I even tried restarting my phone to downgrade but I have no response from my MENU, HOME, BACK or SEARCH button.
WORD OF ADVICE. PLEASE STAY AWAY FROM CWM v6.0.1.4.
EdwardLThompson said:
I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Click to expand...
Click to collapse
Simple Solution is that the Cache in your device is large, it has to be cleaned, For this use Darkside cache wipe. It Solves the problem.
suffuciently hungeom
mintharis said:
Can you please provide a link for the 5.0.2.7 tar you flashed?
Click to expand...
Click to collapse
Here you go,
Look at step 6, it will have links to the tar based on your carrier. Its actually 5.0.2.6, works just the same though.
http://theunlockr.com/2011/12/01/how-to-root-the-samsung-galaxy-s-ii-all-versions/
I hope this helps you!
That happened to me as well when I was going to update to CM10. The faq for CM10 says you need to update to a Touch version of CWM which ROM Manager really wanted to install the Touch version. CWM shows it's version 6 and the menus were different but when I was finally able to get a ROM to boot in Safe Mode it reported CWM as being version 5.x. I could not mount or dismount the Cache in CWM. ODIN brought it back to stock but I messed around with the partition checkbox and hard bricked it. Otherwise it looked as tho things would have been ok after using ODIN to start over.
Darkside's wipe wouldn't work (either version) in this case.
screw cwm im going to twrp
ok same thing happened to me..but there are files i need in the phone and i dont think i want to use cwm after this...so can i use odin to flash it to twrp and recover my files through the twrp usb mount?
(lol nvm, i flashed a older version of cwm through odin and then recovered my files then got twrp)
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Like I said in my earlier post had your exact problem and did exactly what was recommend here, and it worked beautifully. Solved all my problems, no residual effects to speak of. Now I can flash my roms in peace.
I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.
Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?
Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?
all,
I am using TWRP 2.5.0.0 yet i keep getting the boot loop. tried wiping multiple times. any ideas how to resolve this?
go into the thread TWRP and there they will explain how to get out of that problem the newest version had a bug with it so they made a flashable zip that will get you out the boot loop hope that helped http://forum.xda-developers.com/showthread.php?t=1768742 go there and start from like page 70 or so and you will get it
krazierokz said:
go into the thread TWRP and there they will explain how to get out of that problem the newest version had a bug with it so they made a flashable zip that will get you out the boot loop hope that helped http://forum.xda-developers.com/showthread.php?t=1768742 go there and start from like page 70 or so and you will get it
Click to expand...
Click to collapse
before updating i also tried 2.4.3.0. and had the same issue
technojinn said:
before updating i also tried 2.4.3.0. and had the same issue
Click to expand...
Click to collapse
i will try again
sometimes older recoveries behave different than others but i dont use TWRP so im not to familiar with it i stick with the tried and true if it aint broke dont fix it type of guy lol but when flashing that rom what rom was you on and how many times have you flashed before ? was you already rooted when you flashed that or did you do it through odin what were youre steps
technojinn said:
all,
I am using TWRP 2.5.0.0 yet i keep getting the boot loop. tried wiping multiple times. any ideas how to resolve this?
Click to expand...
Click to collapse
i'm using twrp 2.2.2.0, which is an older version, but it works just fine. i installed JMT JB 1.1 yesterday. didn't have any problem.
boot loop
ntdatter said:
i'm using twrp 2.2.2.0, which is an older version, but it works just fine. i installed JMT JB 1.1 yesterday. didn't have any problem.
Click to expand...
Click to collapse
i used clockwork mod to install Jedi Mind Trick Jelly Bean ROM and I'm in a boot loop. Can someone help please?
---------- Post added at 03:40 PM ---------- Previous post was at 03:17 PM ----------
rvmehta said:
i used clockwork mod to install Jedi Mind Trick Jelly Bean ROM and I'm in a boot loop. Can someone help please?
Click to expand...
Click to collapse
nevermind - fixed it by installing a newest version of clockwork mod and redoing the install.
Please remember with the newest TMo 4.1.2 base there is a preload partition that is wiped when you wipe cache/dalvik. You WILL bootloop without preload. Jamison has modified the old TDJ wipe scripts to add preload back in and I recommend using those instead of wiping from recovery. They can be found in his Infamous 4.1.2 ROM thread in development.
Can't enter recovery after restore, following bootloop
Hi Everyone,
I was running CM 10.1.2 and wanted to flash Jedi Mind Trick v6. Followed instructions to flash Darkside Super Wipe, then ROM, then Darkside cache wipe. Phone began to bootloop after showing the Deviant Developer boot image. I tried to do a full wipe with CWM recovery but it kept freezing on the cache wipe. When that failed I successfully restored a backup (AOKP JB-mr1_build-6) but was still experiencing a freeze with CWM anytime I tried to wipe. I thought that it might help to install TWRP so I installed goomanager and successfully installed the recovery from there but now I can't get into recovery at all (neither from CWM nor from TWRP). The AOKP is still working as well as it ever did but I'd like to reboot into recovery somehow and maybe even finish flashing Jedi Mind Trick v6. Does anyone have any idea what I may have done wrong here? I'm a relative noob and this is my first post so your patience is much appreciated. Thank you very much for any insight you might provide!
sleepingcrow123 said:
Hi Everyone,
I was running CM 10.1.2 and wanted to flash Jedi Mind Trick v6. Followed instructions to flash Darkside Super Wipe, then ROM, then Darkside cache wipe. Phone began to bootloop after showing the Deviant Developer boot image. I tried to do a full wipe with CWM recovery but it kept freezing on the cache wipe. When that failed I successfully restored a backup (AOKP JB-mr1_build-6) but was still experiencing a freeze with CWM anytime I tried to wipe. I thought that it might help to install TWRP so I installed goomanager and successfully installed the recovery from there but now I can't get into recovery at all (neither from CWM nor from TWRP). The AOKP is still working as well as it ever did but I'd like to reboot into recovery somehow and maybe even finish flashing Jedi Mind Trick v6. Does anyone have any idea what I may have done wrong here? I'm a relative noob and this is my first post so your patience is much appreciated. Thank you very much for any insight you might provide!
Click to expand...
Click to collapse
1) You used Darkside wipe with a version of CWM other than 5.xx.
2) You used Goo Manager.
Those are your problems. You need to Odin a recovery to fix it.
You can find a TWRP tar file here:
http://techerrata.com/browse/twrp2/hercules
Get rid of Goo and Darkside.
Hey guys,
So im having trouble flashing cm 10.1 or any other rom on my samsung galaxy s3 i747m (rogers)
i have read all the other forums but still cant figure out my problem. i rooted my phone a few days ago and everything worked perfectly, i started out with cwm recovery and i kept getting error 7... when trying to flash cm 10.1 nightly.
i thought at first maybe i have the wrong file but im pretty sure its not the case.
i then updated Supersu, that didnt solve my problem either.
then i deleter cwm recovery and installed twrp with goo manager (latest version)
and now i get failiure to install....
im sure i am going through the right process as i have watched many videos and read the forums
ex: backup/ wipe cache/ wipe dalvik cache/ factory reset/ then install rom / and gapps
gapps works but i am never able to install the cyanogenmod nightly always says failiure to install..
Please help!
This is a bootloader issue. Please check out and carefully look over the information provided at the top of post #2 of the link in my signature.
thanks
Thanks a lot, i got the bootloader file. however when i use ondin, should i load it with PDA or Bootloader?
ca.gs3 said:
Thanks a lot, i got the bootloader file. however when i use ondin, should i load it with PDA or Bootloader?
Click to expand...
Click to collapse
Pda
Sent from my SGH-T999 using xda app-developers app
So... i updater the bootloaders, worker perfectly, was successful.
tried to install cm 10.1 again, has failed me once again...
any ideas?
What fail message are you getting? What version of recovery are you running?
xBeerdroiDx said:
What fail message are you getting? What version of recovery are you running?
Click to expand...
Click to collapse
super su version: 1.27:supersu
bootloader: i747mvldlk4
goo.im version: 2.1.2
installed twrp directly from goo.im yesterday.
phone is samsung galaxy s3 version sgh 1747m
android version: 4.1.1
kernel version: 3.0.31-538866
The fail message on twrp comes out maybe 2 seconds after i run cm 10.1 zip.
Just says failiure to install
then i get the option to delete cache and dalvik cache which i had already dont prior to install.
do i also need to format data? it says it completely deletes everything from my phone... im worried it wipes my backup and i have nothing to go back to.
thanks
ca.gs3 said:
do i also need to format data? it says it completely deletes everything from my phone... im worried it wipes my backup and i have nothing to go back to.
thanks
Click to expand...
Click to collapse
You don't have to delete data I always do to get rid of clutter
It won't wipe your sd card (that option is in advanced wipe). You should always move your backups and important stuff to your sd.
Sent from my SGH-T999 using xda app-developers app
Try downloading again and check the md5 number
ca.gs3 said:
do i also need to format data? it says it completely deletes everything from my phone... im worried it wipes my backup and i have nothing to go back to.
thanks
Click to expand...
Click to collapse
When you boot into recovery, what TWRP version do you see at the top?
disengage said:
When you boot into recovery, what TWRP version do you see at the top?
Click to expand...
Click to collapse
From the op...
" I then updated Supersu, that didnt solve my problem either.
then i deleter cwm recovery and installed twrp with goo manager (latest version) "
Sent from my SGH-T999 using xda app-developers app
KorGuy123 said:
From the op...
" I then updated Supersu, that didnt solve my problem either.
then i deleter cwm recovery and installed twrp with goo manager (latest version) "
Sent from my SGH-T999 using xda app-developers ap
2.5.0.0 twrp
Click to expand...
Click to collapse
disengage said:
When you boot into recovery, what TWRP version do you see at the top?
Click to expand...
Click to collapse
Twrp 2.5.0.0 version