Related
Hi, so I'm super green but itching to load custom kernel and rom... So my Evo is rooted and have seen some pretty sweet roms, lol, kinda scared to flash and not sure what roms go with what kernals, do I even need a new kernal? What I really want is a kernal I can overclock to 1198mhz, and a rom build based on honeycomb and or gingerbread that is 100% stable or as close as I can get... Help? Lol...
Sent from my PC36100 using XDA Premium App
hahah exited aren't you... welcome to the root world!
you asked for hc/gb. google hasnt released hc source code yet, probably not until ice cream, so there is none of that. you can however download cyanogen(mod) 7, which is almost totally stable.
http://mirror.teamdouche.net/?device=supersonic
there's the mirror link. download either rls4 or nightly 33. nightly 33 is a bit funky bcuz cyanogen is pulling an april fools prank saying he sold cm to teh duck revolution, and the rom is now called 'teh duck uber distro'. so maybe rls4 or just wait for the next nightly.
everything works. 4g (with one bug that there is an annoying fix for), hdmi (download hdmwin from the market) gps (with a fix) and everything else is perfect. it is still in beta/nightly stages, but should be done soon. it is my daily driver, as well as many other peoples. this rom is crazzzy popular. try it for sure.
start with stock kernel, but i'd try both savaged-zen and tiamat kernels on it. they will both give you much better battery. tiamat tends to give slightly better performance/quickness but savaged-zen (on custom SAVAGEZEN governer) gives fantastic battery. try them both!!!
again, welcome to the community. hope this helps.
Where do I get the kernals? And what process do I use? I have clockwork premium... I just don't wanna miss a step a jack myself
Also, is it gonna wipe my phone, do I need to wipe it? No issues with that though as I do it all the time... And thank you so much for the feedback BTW, still a little confused...
Sent from my PC36100 using XDA Premium App
ok, first of all, clockworkmod isn't the recovery you want to be using. download amon-ra's recovery here http://forum.xda-developers.com/showthread.php?t=705026 make sure you get the pc36img.zip. put the pc36img.zip on the root of your sdcard (that means not in any folders) MAKING SURE IT IS NAMED EXACTLY PC36IMG.ZIP. aka just dont rename it. then power off your phone, and once it is off, hold power and volume down. you will see a white screen with scateboarding droids at the bottom. this is your BOOTLOADER SCREEN also known as hboot, and you see it quite often. so hboot will scan your sdcard, and find the pc36img.zip. hit volume up to accept the 'update'. then once it is done, volume up again to reboot.
you can download kernels from the evo android development subforum right here at the xda.
so first flash your rom. you can either boot up into it, or just flash the kernel right away. flash the kernel just like you would a rom, but without wiping.
enjoy.
any other questions, ask away.
dkdude36 said:
ok, first of all, clockworkmod isn't the recovery you want to be using. download amon-ra's recovery here http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
100% agree. Amon Ra imo is the much more stable & user friendly recovery
Alright, so, can I do all this just from my phone? Is a pc recommended? Will my stock kernal overclock? Never flashed a rom before, I'm an electronic/computer tech so I pick up shniz pretty quick but still don't wanna b---- this sucker...
Sent from my PC36100 using XDA Premium App
you can do it all from your phone if you want. i perfer downloading on my pc and transferring from there in case i want to modify anything, but you can always just dload on phone. make sure the pc36img.zip isnt in download folder or anything if you do. it needs to be on the root. your stock kernel can't overclock sadly. if you have never flashed a rom before, then cm7 will be crazy different than stock rom. most custom rom's are based off the stock htc software, just modded. cm7 is aosp, which means it is stock GOOGLE software. htc spends quite a few months modifying htc sense into google software, so the speed and memory increase is very noticable. just wipe data, cache, and dalvik cache when switching roms. you might want to backup your apps and their data using titanium backup. just dont backup system data, that can cause problems. then flash the rom after wiping, flash any kernel or addons you want (dont forget to flash gapps if it is an aosp rom, bcuz if you dont u wont have the market or anything) and reboot. for any other mods you install after that on the same rom, just wipe cache and dalvik cache and then flash away. wiping data between roms is always reccomended. if you want to stick with the cm7 nightlys, then all you need to wipe is cache and dalvik. there is never much of a problem with just flashing one over the other without a data wipe.
and forgot to mention, you cant control amon-ra recovery with rom manager. but then again, rom manager is just a touch screen version of recovery. you get used to the volume/power keys pretty quickly.
ok, im freaking out now, my phone is locked in the cm little surfer droid with the arrow circling around been constantly running for about 45 mins, im fuct, really fuct without my phone!!! its my only internet too!!! PLEASE HELP!!!
Did you do a factory wipe, Clear the cache & wipe Dalvik?
Sounds like it just wasn't a good install. Do the above in recovery & reinstall your ROM
ya did you wipe? doesnt sound like it. make sure data, cache, and dalvik cache are all wiped successfully. also make sure you are using amon-ra recovery. cwm can sometimes give you problems.
I am fairly new to Android, but am comfortable with command line operation on other Unix systems, etc. I read every thread I can find on this, but did not find my problem described exactly (there are some similar problems), so here it is:
My phone is a GSM Galaxy Nexus, about a month old. I rooted and unlocked it right away using post 1 from this guide: [VZW/SPRINT/GSM][Guide] Ultimate Galaxy Nexus Guide (Unlock/Root/Flash Roms/FAQ) - thanks Jubakuba!
I did NOT use any of the toolkits or automated methods.
A couple of days ago, I decided to try loading another ROM. I read through post 2 of the above guide. I followed the instructions in that thread and flashed a Trinity ROM. The flash seemed to go fine, and completed normally, but when I rebooted the phone, it was stuck in the Google Lock screen bootloop. I was able to restore a nandroid to get it back to where it was before, and the phone operates normally, no resets, reboots, nada. I inquired in Jubakubas thread as well as in the Trinity ROM thread in the developers section, and got some suggestions, which I tried. None of them worked. I also tried flashing a few other ROMS, a CM9 ROM and the RASCREAM ROM, and they all do the same thing. I have tried flashing these without wiping data or cache or dalvik cache, wiping some of them and wiping all of them, and the results are always the same - boot loop, which I can restore using CWM recovery and my nandroid.
One of the posters in the developers forum suggested taking the phone back to unrooted stock condition, so I did that, using this thread: [HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid build / Return to stock - another excellent guide, which worked exactly as described.
After that, my phone was back to as new, and I had to go through the whole start-up and restore applications, etc. I made a new nandroid so that recovery would be relatively painless, etc. Not too tough. I then Rooted the phone (it was always unlocked) and tried flashing a ROM again, with exactly the same results. Again, I was able to restore my nandroid and get back to operational.
I guess my question at this point is what on earth could be causing this? Some of the threads on boot loops where peoples phones start to boot loop spontaneously suggest a hardware problem, but the fact that I have NEVER had a boot loop in a month of use while running 4.0.4 stock rooted and unlocked seems to point more toward software as the cause. I will say one thing - I am learning how to use CWM and the bootloader commands! But, I would really like to be able to use some custom ROMS, not that there is anything really wrong with stock - this is a great phone. But, please HELP!
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
d0msen said:
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into fastboot mode, then flashed the bootloader (bootloader-maguro-primela03.img) and radio (radio-maguro-i9250xxla02.img). I rebooted the bootloader, then went into recovery mode. From recovery mode, I selected "Install zip from sd card", "Choose zip from sd card", then selected the zip file in the /Download folder "TNP1536-384-Alpha86b-4.7-lto.zip". It went through its' install and said "System successfully corrupted" at the end and "Install from sdcard complete." I went back to reboot system rom and rebooted. Now, it is not looping anymore, but just sitting at the Google lock screen for about 2 minutes now. I will wait a few more minutes to see if it boots the rest of the way or starts looping, etc.
Okay, it has been 5-6 minutes with no additional changes, so I am pulling the battery. Powering it on now results in the same boot loop as before, so I will need to boot into bootloader mode and restore my nandroid.
are you wiping data when you flash the rom?
if not, you need to do that first inside of cwm
I would let it sit longer before pulling the battery
Sent from my Galaxy Nexus using xda premium
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
CYoung234 said:
"System successfully corrupted"
Click to expand...
Click to collapse
The
BOOM!
System successfully corrupted
Please freak out now
is a joke. By your account the kernel flashed successfully. Try flashing another kernel, perhaps not an Alpha version, although I've run that particular Alpha successfully. Do you have an app that sets kernel settings on boot by chance?
Hmmm thats a Kernel i think try another kernel.. Franco is a option ... maybe ur phone can't handle the undervolt of Trinity? I don't know worth a try download franco and post ur results here
Good luck
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The nandroid I am restoring to is stock 4.0.4. I will wipe everything, then try flashing a known stable aokp build, then report back.
efrant said:
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
Click to expand...
Click to collapse
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
CMNein said:
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
Click to expand...
Click to collapse
Yes, pretty much this. If you are updating CM9 to the next build, no need to wipe. If you are going from CM9 to AOKP, then you need to wipe.
Updating: no need to wipe.
New ROM: wipe.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You are correct, it is a kernel, not a ROM. I have tried 3 different Trinity kernels and one Franco kernel, all with the same results. The specific kernel I flashed for post #3 was TNP-1536-384-ALPHA86b-4.7-LTO.zip. The other two I tried were both stable releases. Morfic asked me to try the alpha kernel.
CMNein said:
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
Click to expand...
Click to collapse
Google Galaxy Nexus i9250.
CYoung234 said:
Google Galaxy Nexus i9250.
Click to expand...
Click to collapse
Okay, was asking in the event that you were also flashing Rascream, or Morfic's build of it.
Re: wiping, since we now know that we're just talking kernel here, wiping dalvik + wiping cache is indeed approaching useless, so they weren't leading you astray. I can't think of what would be causing you to boot loop however.
d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
CYoung234 said:
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
Click to expand...
Click to collapse
This got me thinking: is trinity even compatible with a stock ROM (regardless of it being 4.0.4)? Maybe that is why you were having issues.
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.
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.
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?