Hey everybody.
I used to flash all sorts of roms on my old galaxy vibrant but I bought a new t989 a few months ago and I want to go to a custom from the stock tmob bloatware infested ICS. I already rooted via odin and installed clockwork recovery, which comes up just fine with the usual volume and power combo so i'm good there.
My question is should I flash my first rom (probably jedi mind trick 5 or x1,or if anyone knows a daily driver ready jelly bean??)
via clockwork mod like on my vibrant? or do I use twrp which I also have via goo manager? I prefer cwm because I am familiar with how to wipe cache, reset and flash with it but I can't figure out why some mods recommend one or the other.
Also,
I keep seeing some roms that come with a radio zip and was wondering if all roms require this or is it just certain roms?
Thanks in advance for any help. I just don't want to wreck my phone the first time. Remember, I've flashed a million times on my vibrant but never on my t989 so any pointers or heads up would be appreciated.
Get darkside wipe scripts (both wipe cache and super wipe)
Go ahead with the Jedi X1 ROM its very stable and fast as hell
But if you want Jelly Bean I recommend Galaxy SBean v8 or Liquidsmooth rc8 they're the most stable JB ROMs from what I experienced
Remember to always wipe dalvic cache and fix permissions (darkside cache wipe) after flashing a new ROM
After you flash your ROM and Gapps then boot that's when you can flash kernels, mods, and apk's so it would have a lesser chance of a soft brick
Happy Flashing!
Sent from my SGH-T989 using xda app-developers app
arthurgreeeen said:
Get darkside wipe scripts (both wipe cache and super wipe)
Go ahead with the Jedi X1 ROM its very stable and fast as hell
But if you want Jelly Bean I recommend Galaxy SBean v8 or Liquidsmooth rc8 they're the most stable JB ROMs from what I experienced
Remember to always wipe dalvic cache and fix permissions (darkside cache wipe) after flashing a new ROM
After you flash your ROM and Gapps then boot that's when you can flash kernels, mods, and apk's so it would have a lesser chance of a soft brick
Happy Flashing!
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Cool. Thanks for the reply. I went and grabbed super wipe and cache wipe. So essentially, I just put those two on my sd and flash like I do a rom zip from recovery and then flash the rom itself and do a darkside cache wipe after new rom is installed before restarting and booting for the first time? Do I still need to do factory reset/wipe or is that part of the scripts? I have the goo app so I can use twrp instead since it's recommended for almost all roms I will be installing. Any major reason why, besides that it has touch function and backup renaming? Is it safe to install from the goo app on stock rom?
I think I will probably try one of the jellybean roms you suggested. I just didn't want random reboots, and I heard that's an issue with jelly bean roms but I think that might have been specific to aokp ones or something. Occasional FCs aren't too big of a deal though.
One other thing though... how do I fix permissions? I kept reading about that but never did it. Do you mean in recovery or under superuser?
how to properly flash a rom
http://forum.xda-developers.com/showthread.php?t=1926754
just follow that and you should be fine.
you can fix permission in recovery. its under advanced in cwm and twrp.
merrygocow said:
how to properly flash a rom
http://forum.xda-developers.com/showthread.php?t=1926754
just follow that and you should be fine.
you can fix permission in recovery. its under advanced in cwm and twrp.
Click to expand...
Click to collapse
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
benjmiester said:
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
Click to expand...
Click to collapse
I usually do it after flashing. And you don't need to do it every single time. Also, there's no need to follow everything down to the letter when you flash, wipe cache/dalvik/factory reset/wipe system/fix permissions/sit for 10 mins/reboot/reboot again/etc. Flashing is like cooking. As long as you don't deviate too much from the recipe, you'll get edible food (or a working ROM). If it doesn't work out, just toss the food out and try again (softbricked phone, reflash). If you try something stupid, you'll set your kitchen on fire when you don't have insurance (comparable to hard bricking your phone).
I usually wait till I've restored all my apps before fixing permissions, and then sometimes I don't if everything is working fine. As for recovery, I know you're familiar with CWM, but I'd recommend spending some time using TWRP. It's really great. You don't need the scripts with TWRP, but since TWRP lets you cue up zips, you can set it to do super wipe, ROM, gapps, and cache wipe all in one go. Kinda cool. And if you're itching to try jelly bean, AOKP JB milestone 1 is stable and smooth. There are even a couple custom kernels for it and CM10 (which has also reached a stable version, though I haven't tried it).
Sent from my beastly Galaxy S 2.
Dark side super wipe and cache wipe work perfectly on 5.0.2.6! That's how I got PACman ROM on my phone. I didn't bother with fix permissions. Well, I would say don't worry unless the instructions specify to do so.
Either way, I like CWM because I used it on my Samsung Galaxy Ace. Its just the wipes are broken for this phone so the scripts have to be used and work perfect. Happy flashing!
Sent from my SAMSUNG-SGH-T989 using xda premium
benjmiester said:
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
Click to expand...
Click to collapse
no it's fine to use the scripts w/ cwm 5. just don't use the scripts on cwm 6. that's what he meant.
i usually fix permission after the first reboot & waiting 10-15 mins.
i second the twrp recommendation...however if you're flashing something old, then cwm is the way to go. i haven't had any problems flashing anything in cwm. the latest twrp however failed me after i tried to flash a gb theme for jugg lol.
merrygocow said:
no it's fine to use the scripts w/ cwm 5. just don't use the scripts on cwm 6. that's what he meant.
i usually fix permission after the first reboot & waiting 10-15 mins.
i second the twrp recommendation...however if you're flashing something old, then cwm is the way to go. i haven't had any problems flashing anything in cwm. the latest twrp however failed me after i tried to flash a gb theme for jugg lol.
Click to expand...
Click to collapse
Ok, just wanted to make sure on that one.
Thanks for all the input everybody. Hopefully I will get a chance to do my flash over the holiday. I plan on going with the Sbean V8. Really all of the roms out look excellent but this one looks good for a JB daily driver. I went ahead and downloaded Jedi X1 too though in case the sbean doesn't work out for whatever reason. I have to tether my phone at home for internet so I thought it might be good to have a backup just in case PDAnet doesn't want to work.
Is twrp ok to install from Goo manager on my stock rom or should I flash a new rom and then use it from then on? I just want to make sure it won't conflict with the stocker or the CWM that I have on it already.
benjmiester said:
Ok, just wanted to make sure on that one.
Thanks for all the input everybody. Hopefully I will get a chance to do my flash over the holiday. I plan on going with the Sbean V8. Really all of the roms out look excellent but this one looks good for a JB daily driver. I went ahead and downloaded Jedi X1 too though in case the sbean doesn't work out for whatever reason. I have to tether my phone at home for internet so I thought it might be good to have a backup just in case PDAnet doesn't want to work.
Is twrp ok to install from Goo manager on my stock rom or should I flash a new rom and then use it from then on? I just want to make sure it won't conflict with the stocker or the CWM that I have on it already.
Click to expand...
Click to collapse
--Update--
I got Sbean v8 installed and working just wonderfully! I used CWM for my install with the darkside superwipe and cache wipe scripts. Everything went fine and i'm very happy with the new rom. Thanks everyone. I hope this thread will help any other first flashers in the future.
Related
Ok I looked all over the place and I could find anything about this issue. I have the telus s2x t989d and I went on rom manager and downloaded cyanogenmod 9 for my phone( only one available). Then I went in to install it and when it finished it just stayed on the really cool cyanogen boot screen and I had to power off and restore. Ive tried it a few times and nothing changed. I wiped the cache and stuff too. what should I do?
Are you trying to lead it directly from the app or are you trying to flash from recovery? Rom manager is buggy on the t989/t989D series. Flashing from an app is not recommended AT ALL due to potential of bricking the device
I guess my question is, what's your exact process you took...(i.e. steps taken)
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Ya I have been using the app. Can I still use the app to download roms? And then can I go into recovery from the app or just exit it and reboot it myself?
LostMoonOfPoosh said:
Ya I have been using the app. Can I still use the app to download roms? And then can I go into recovery from the app or just exit it and reboot it myself?
Click to expand...
Click to collapse
its recommended to simply download the rom zip the boot into recovery and install there. I use cm9 stable with tdj Darkside kernel 6 and flash everything through twrp recovery never had a single boot loop in any room I've flashed. What rom are you running currently?
1.Download rom and place in external sd card.
2. Reboot into recovery
(You may want to wipe data/factory reset depending on what rom you are running and clean install are typically recommended unless coming from a previous version from same developer (i.e. cm, aokp, etc)
3. Flash darkside super wipe and cache wipe if using cwm non touch
4. Flash rom, gapps and kernel (if so desired on the gapps and kernel)
5. Reboot and wait 10mins
6. Reboot again and have fun!
Let me know if that helps
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
EnigmaticGeek said:
its recommended to simply download the rom zip the boot into recovery and install there. I use cm9 stable with tdj Darkside kernel 6 and flash everything through twrp recovery never had a single boot loop in any room I've flashed. What rom are you running currently?
1.Download rom and place in external sd card.
2. Reboot into recovery
(You may want to wipe data/factory reset depending on what rom you are running and clean install are typically recommended unless coming from a previous version from same developer (i.e. cm, aokp, etc)
3. Flash darkside super wipe and cache wipe if using cwm non touch
4. Flash rom, gapps and kernel (if so desired on the gapps and kernel)
5. Reboot and wait 10mins
6. Reboot again and have fun!
Let me know if that helps
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Click to expand...
Click to collapse
So I should just find the rom on my computer instead then?
Im downloading cyamogenmod 9 now from their website. I guess rom manager is pretty much useless for me then? I liked it because it would only show me roms that work for my phone so I dont make any mistakes.
ok I did it. but it didnt work... it just loaded up stock unrooted ics. with all my stuff gone. i have backups so im not worried about that, but i dont know why CM didnt flash...
LostMoonOfPoosh said:
ok I did it. but it didnt work... it just loaded up stock unrooted ics. with all my stuff gone. i have backups so im not worried about that, but i dont know why CM didnt flash...
Click to expand...
Click to collapse
I would use only super wipe
then flash ROM
reboot
wait ten minutes WITHOUT TOUCHING ANYTHING!!
reboot.
Its a proven formula that has worked for me, many, many times
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Also, super wipe and cache wipe are found here read OP carefully
http://forum.xda-developers.com/showthread.php?t=1477955
LostMoonOfPoosh said:
ok I did it. but it didnt work... it just loaded up stock unrooted ics. with all my stuff gone. i have backups so im not worried about that, but i dont know why CM didnt flash...
Click to expand...
Click to collapse
Stock unrooted ics? What recovery are you using, have you flashed a recovery through odin at all with this device?
EnigmaticGeek said:
Stock unrooted ics? What recovery are you using, have you flashed a recovery through odin at all with this device?
Click to expand...
Click to collapse
is work fist root then factory reset then flash.
kiruba8 said:
is work fist root then factory reset then flash.
Click to expand...
Click to collapse
You need to have a recovery flashed to your phone to even start the root process. Cwm, cwm touch, or twrp. All are available in the sticky section as well as development section. If you are running stock recovery then that's your primary issue.
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
LoopDoGG79 said:
I would use only super wipe
then flash ROM
reboot
wait ten minutes WITHOUT TOUCHING ANYTHING!!
reboot.
Its a proven formula that has worked for me, many, many times
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Also, super wipe and cache wipe are found here read OP carefully
http://forum.xda-developers.com/showthread.php?t=1477955
Click to expand...
Click to collapse
Ok i looked at the darkside link you gave me. Will it for sure work with the telus version s2?
LostMoonOfPoosh said:
Ok i looked at the darkside link you gave me. Will it for sure work with the telus version s2?
Click to expand...
Click to collapse
Yes, the only difference between T-Mobile and Telus versions is cosmetic. Telus is the T989D, T-Mobile is the T989. There is a reason why they are so closely named.
Sent from the pink Unicorn from the Darkside.
EnigmaticGeek said:
Stock unrooted ics? What recovery are you using, have you flashed a recovery through odin at all with this device?
Click to expand...
Click to collapse
oh ya I have CWM recovery flashed so im good in that department. Im going to try out darkside superwipe now and see if that helps.
well I used darkside and then flashed my rom. Now it wont even go past the telus loading screen... Ive restored back again. I made it alot farther than this with rom manager haha. I actually saw the cyanogenmod opening cinematic... Ill try the darkside cache wipe this time and see if that helps. I downloaded the rom right from the cyanogen website...
Well neither is working. It just stays in the Telus loading screen. Not even the Samsung screen will load. I don't know what else to do...
Sent from my SGH-T989D using xda app-developers app
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.
Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.
You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours
playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^
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?
tl;dr: What happens if I upgrade to CWM 6 after having used Darkside Superwipe on CWM 5?
And now the long explanation of what happened:
I have a Telus T989D, and I had installed the stock Telus JB ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2343748
I previously had CWM, but as per the instructions in the thread I installed TWRP, ran the Infamous Superwipe zip file, and then proceeded to flash the ROM.
Then today I decided to install CM 10.1. The first thing I did was flash CWM 6.x (I forget the exact version, but it was the latest one) from ODIN. Then I downloaded the latest stable build (CM 10.1.2). I then ran the Infamous Superwipe zip file again, and flashed CM 10.1. The result was that the phone would get stuck on the Cyanogenmod circle logo. I did some Googling and found out some people who had bootloops after installing Cyanogenmod, and it was suggested that this was due to a bad wipe, and that using Darkside Superwipe would fix the problem. So I proceeded to give Darkside Superwipe a try... Of course at the time I hadn't realized that 1) What I had was not actually a boot loop (it wasn't rebooting, it was just stuck at the logo), and 2) that Darkside Superwipe should not be used with CWM 6. After flashing the Darkside file, my CWM 6 would load up but would fail to flash ANY zip file that I selected (it would just get stuck on the first line, "Installing xxx.zip"). It would also fail to wipe the /cache partition (would freeze at "wiping /cache partition").
After soft-bricking my phone by trying to flash a different recovery from Heimdall, I ended up following a guide on this forum to flash the stock Gingerbread ROM from Odin. I then flashed CWM 5.0.2.7, did the Darkside Superwipe, installed CM 10.1, and now thankfully the phone works.
My question is... Does anybody know what happened here? And any ideas what will happen if I try to upgrade my CyanogenMod later on? Will I have any issues running CWM 5.x with CM 10.1 or 10.2? I'm a bit afraid of updating to CWM 6 since I have no idea what the result will be.
I later learned that Infamous Wipe is only to be used with TW-based 4.1.2 ROMs, since it adds a preload partition. Did I end up somehow messing up my partitions by using the Infamous & Darkside Superwipe files?
Sorry for the long post... I just figured I should give as much information as possible! I'd really appreciate it if anybody has an explanation for what happened (messed up partitions?) and how to fix it!
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Faruk88 said:
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Click to expand...
Click to collapse
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Faruk88 said:
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Click to expand...
Click to collapse
U can use goo manager if u want, but I will say this, sometimes too can cause soft bricks, in which case u would need Odin to recover , so in my professional opinion I would suggest using Odin from scratch
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app