Related
i'm trying install cm9 or miui 4 or aokp but am running into a problem where i can't flash anything from cwm bundled with cm7. i'm doing these exact steps as stated here in Part 1:
with calk's el29 installed (with Rogue 1.1.2 based off cwm 5.0.2.7), i booted into recovery and wiped data except for battery stats. i flashed cm7 from here. i immediately booted into cm7, then immediately rebooted back into cwm recovery. from here, i tried flashing cm9, miui 4, aokp alpha 1, and aokp alpha 2. they all fail saying "E: can't open /sdcard/romname.zip (bad) Installation aborted."
what am i doing wrong?
I would flash cm7 again, boot, then reboot into recovery again and try to flash another ics ROM. Just make sure to remember not to wipe data until after you flash an ics ROM and gapps
Sent from my SPH-D710 using Tapatalk
Back in the vibrant days (tmobile galaxy s) if you had any problems with flashing the "fix" was to start all over via Odin and a rooted stock ROM...
Dunno if that is something that is still a good idea to do.. But worth a try...
paranoid android85 said:
I would flash cm7 again, boot, then reboot into recovery again and try to flash another ics ROM. Just make sure to remember not to wipe data until after you flash an ics ROM and gapps
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
i've tried aokp and miui4. no bueno. in fact, it wont flash anything i have, including calk's wipe all script.
Bear gri11z said:
Back in the vibrant days (tmobile galaxy s) if you had any problems with flashing the "fix" was to start all over via Odin and a rooted stock ROM...
Dunno if that is something that is still a good idea to do.. But worth a try...
Click to expand...
Click to collapse
tried that like 4 times lol. i'm actually gonna try copying all the ics roms onto my sdcard again, this time from within android itself. all the roms had been transferred over while usb was mounted in cwm and i noticed the transfers would pause at times or not complete at all, forcing me to start them over. perhaps that's the problem.
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.
Being new to Android I succeeded in rooting, installing TWRP to my Tmobile SII..
Then I went ahead and backed up my current stock ROM..
Then went and downloaded CM10 from their website since it's stable.
I erased the old ROM and installed CM10 as the guide suggests.
After booting, however, I had a problem. The phone was very laggy and trebuchet was constantly crashing.. I then decided that this ROM must not be stable and looked for more stable ROMS..
GalaxySbean_V13.5
MIUI.us_hercules_v4.1_2.12.28_Eng_Deo_ZipA_Signed_0xD34D
rootbox_hercules_unofficial_Feb-20-13
.. and couple more.. All running very slowly.. and crashing constantly..
What am I missing?
Is it a problem that I didn't format the internal memory?
If it makes a difference.. TWRP is version 2.4.1.0
Thank you!
I am hoping I can find something faster.. I'm sick of the stock Samsung.. :crying:
What was your flashing method or steps you took to flash? Also, update to the latest TWRP 2.4.3.0 and get the latest version of the ROM you want to flash. Also, CM10 is not as smooth as 10.1 so you might want to give the latest nightly a go.
EDIT:
A good setup would be:
-CM10.1 latest nightly
-Cerux Kernel ASDK (They both are good)
-Latest gapps (3-1-13 I think)
-Crossbreeder mod
batezippi said:
Being new to Android I succeeded in rooting, installing TWRP to my Tmobile SII..
Then I went ahead and backed up my current stock ROM..
Then went and downloaded CM10 from their website since it's stable.
I erased the old ROM and installed CM10 as the guide suggests.
After booting, however, I had a problem. The phone was very laggy and trebuchet was constantly crashing.. I then decided that this ROM must not be stable and looked for more stable ROMS..
GalaxySbean_V13.5
MIUI.us_hercules_v4.1_2.12.28_Eng_Deo_ZipA_Signed_0xD34D
rootbox_hercules_unofficial_Feb-20-13
.. and couple more.. All running very slowly.. and crashing constantly..
What am I missing?
Is it a problem that I didn't format the internal memory?
If it makes a difference.. TWRP is version 2.4.1.0
Thank you!
I am hoping I can find something faster.. I'm sick of the stock Samsung.. :crying:
Click to expand...
Click to collapse
Basically wipe factory defaults and go into mounts and format system. Flash the rom of your choice. I use a custom kernel which supports overclocking and custom governors which may help with the problem. Also you should run fix_permissions to fix the pesky FC's. I run Liquid Smooth with All Star Kernel and it is very fast and smooth. Stay away from anything 4.2 as it isn't stable yet.
batezippi said:
...After booting, however, I had a problem. The phone was very laggy and trebuchet was constantly crashing.. I then decided that this ROM must not be stable and looked for more stable ROMS...
Click to expand...
Click to collapse
I'm not an expert, but I noticed that every ROM post suggests leaving the phone alone for 10 minutes or so after first boot. Did you give CM time to settle after the flash? The ROMs all seem to need time to settle according to the forum posts. I'm running ptmr3's Jedi CM Build 2, which is android 4.2.2. It seems quite stable to me at the moment, but it also seems better after having used it for a few days and rebooted a couple times.
treefrog321 said:
I'm not an expert, but I noticed that every ROM post suggests leaving the phone alone for 10 minutes or so after first boot. Did you give CM time to settle after the flash? The ROMs all seem to need time to settle according to the forum posts. I'm running ptmr3's Jedi CM Build 2, which is android 4.2.2. It seems quite stable to me at the moment, but it also seems better after having used it for a few days and rebooted a couple times.
Click to expand...
Click to collapse
Hmm.. To be hones.. I didn't!
I am going to update TWRP and then I am going to go for this one
http://forum.xda-developers.com/showthread.php?t=1885619
EDIT*
Did that:
TEAMWIN Recovery (TWRP) 2.3.3.0 or later
Wipe
Cache
Dalvik cache
Factory Reset
System
Flash Rom
Reboot
Wait a few minutes
Reboot
Done with flash procedure
Phone is still laggy and very unresponsive.. Unusable! What am I doing wrong?
I'm very new to ROMs and phone tweaking in general, having only flashed less than a dozen ROMs and various tweaks in the last month, but I've never encountered any issues.
My steps:
I use CWM
Nandroid backup
Wipe data
Wipe cache
Darkside Super Wipe
Flash ROM
Flash GAPPS
Wipe dalvik
Fix permissions
Reboot
Wait at least 10 minutes, never less(if you only waited literally a few minutes that might be an issue?)
Reboot, set up Google, etc.
Done.
Never encountered any issues in my young flashing life.
Try this rom
Wanna good fast stable rom? Then try All Star v7....
You might wanna try wiping cache/dalvik factory reset and system a couple of times before flashing. Sometimes that helps
So today i have had nothing but problems with flashing roms. I was on the PAC rom nightlies, but decided to go back to touchwiz roms due to the wifi calling. I tried flashing wicked v4, booted fine but once i reboot, got stuck at the samsung boot logo. tried reflashing/wiping/flashing other roms, including PAC again, all would result in getting stuck at the samsung boot logo. so i used odin to go completely back to stock. That wouldnt boot at first, so i tried wiping data in stock recovery, luckily that got it to boot. I then re-rooted and tried to flash infamous 2.5. same thing, got stuck at the samsung boot logo. finally, i was able to get infamous google edition to boot, but isnt what i want (since it doesnt have wifi calling), but is the only thing i could get to boot.
So does anyone have any idea why my phone is being so moody, or am i just having a bad day?
edit:i will attempt to try and flash infamous 2.5 when i get out of work to see if my phone is in a better mood, but right now i just need a working phone
edit 2: if its relavent, before i used odin, i was using twrp recovery, but after odin, i used clock work mod touched
I also having the same problem, by just rebooting on jedi it goes into bootloop. My guess is either the kernel or the recovery (no expert). On my friends ATT it bootlooped only because I didn't flash the required Ktoons kernel. As for Tmobile I'm not sure of the bootloops, but to fix it i just dirty flash a rom and it works but it happens usually after i flash some add ons.
Both of the problems here are kernels, change to another kernel, should fix these problems.
Good luck
If that does not work, come back here, we will figure something else out.
just tried flashing infamous 2.5, this time with ktoonz kernel, same result, stuck at samsung.
Going to try wicked v4 this time
TheAtheistOtaku said:
just tried flashing infamous 2.5, this time with ktoonz kernel, same result, stuck at samsung.
Going to try wicked v4 this time
Click to expand...
Click to collapse
You tried infamous with it stuck kernel?
But I know what you mean been experiencing that with some Rom as of late not sure what's the deal...
Famously Infamous
mgbotoe said:
You tried infamous with it stuck kernel?
But I know what you mean been experiencing that with some Rom as of late not sure what's the deal...
Famously Infamous
Click to expand...
Click to collapse
yes i have tried it with the kernel it comes with, same result.
still downloading wicked.
What recovery are you using? I know twrp latest is very buggy for most people...also I heard its not fully cleaning people phones for a flash and what not..Im quite sure its a recovery bug for you
mgbotoe said:
What recovery are you using? I know twrp latest is very buggy for most people...also I heard its not fully cleaning people phones for a flash and what not..Im quite sure its a recovery bug for you
Click to expand...
Click to collapse
ive used twrp before i odind back to stock. but now i have been using clockwork mod touch, still having the same problem
after flashing kernal wipe cache,dalvik and fix permissions that should work
LIL_ROOKIE said:
after flashing kernal wipe cache,dalvik and fix permissions that should work
Click to expand...
Click to collapse
i have been doing that after every new flash.
anywho, wicked v4 is booting with ktoonz kernel, and after a reboot its continuing to boot, so im not going to press my luck and stay on wicked. though i still would like to know whats going on.
TheAtheistOtaku said:
i have been doing that after every new flash.
anywho, wicked v4 is booting with ktoonz kernel, and after a reboot its continuing to boot, so im not going to press my luck and stay on wicked. though i still would like to know whats going on.
Click to expand...
Click to collapse
You're not "formatting data" correct? Should only "wipe data". Not format.
norml said:
You're not "formatting data" correct? Should only "wipe data". Not format.
Click to expand...
Click to collapse
no im not formatting data lol i know the difference
TheAtheistOtaku said:
no im not formatting data lol i know the difference
Click to expand...
Click to collapse
LOL, I'm sorry, just that I have seen soooo many ppl getting bootloops or stuck samsung screens, because of that and also not knowing exactly what to wipe. Just trying to help.:victory::highfive:
norml said:
LOL, I'm sorry, just that I have seen soooo many ppl getting bootloops or stuck samsung screens, because of that and also not knowing exactly what to wipe. Just trying to help.:victory::highfive:
Click to expand...
Click to collapse
its no problem
Check SD card
I had a similar issue where my S4 just decided to go into a bootloop on the way to work. A coworker of mine's wife's S3 did the same exact thing and we were finally able to pin it down to both having a SANDISK 32GB micro sd card. Once I pulled the card (after having ODIN'd back to stock and pulling my hair out my desk =/) the phone booted right up. Since all I had on there was music I stuck it in after the phone booted, reformatted it from the stock odin restore (MDL), and I haven't had any issues since. Just figured I'd let you know what caused me to go insane for a few hours since it wouldn't boot after flashing anything at all and only occasionally boot from a clean odin restore or fresh wicked flash. After talking to another guy at work that has a note II, S3, and S4 apparently I'm not the only one that's had this issue pop up.
Since I fixed it I've been running Infamous GE (Infamous Kernel) and The leaked GE 4.3 build without issue.
Wow, SanDisk sd cards have been really sucKing lately. I'll try taking out my sd card if it ever happens again
Sent from my SGH-M919 using Tapatalk 4 Beta
31337_haxer said:
I had a similar issue where my S4 just decided to go into a bootloop on the way to work. A coworker of mine's wife's S3 did the same exact thing and we were finally able to pin it down to both having a SANDISK 32GB micro sd card. Once I pulled the card (after having ODIN'd back to stock and pulling my hair out my desk =/) the phone booted right up. Since all I had on there was music I stuck it in after the phone booted, reformatted it from the stock odin restore (MDL), and I haven't had any issues since. Just figured I'd let you know what caused me to go insane for a few hours since it wouldn't boot after flashing anything at all and only occasionally boot from a clean odin restore or fresh wicked flash. After talking to another guy at work that has a note II, S3, and S4 apparently I'm not the only one that's had this issue pop up.
Since I fixed it I've been running Infamous GE (Infamous Kernel) and The leaked GE 4.3 build without issue.
Click to expand...
Click to collapse
I'm using a PNY SD card... just flashed the 7.2 version of infamous, and out of 20 boot attempts, 2 or 3 booted past the GS4 logo.
seems to work if I go back into recovery and factory reset, boot again, and that's the only way I've gotten past the GS4 screen.
Im using TWRP
I've since figured out the problem. For whatever reason when you wipe the cache & dalvic with twrp, sometimes something happens where your internal memory fills up completly, leaving you with no space. Formating the internal from twrp fixes that, but of course you loose everything not on your sd card. Can confirm this problem in twrp 2.6.0 also, since it happend a few times for me
I now just use clock work mod touch, and haven't had the problem since. Pity though,I prefer twrp
Sent from my SGH-M919 using Tapatalk 4
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
chirantan.f said:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
Click to expand...
Click to collapse
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
i would also like to note here that i tried installing AOSP based ROMs also, and AOKP didnt work, got stuck at nexus like boot animation forever, but when i tried installing CM10.1.2 (which is what i was running when i tried to get back to TW based ROM) it worked perfectly, so for now i am back to CM, but i would really get back to flashing different ROMs and trying them out. just makes me wonder if CM is the reason i am not able to install anything else, just a thought...
has anybody else tried going to any other ROMs from CM 10.1.2?
your help is appreciated!
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
Click to expand...
Click to collapse
thanks for your reply, but i have tried doing that, i also wipe data and system along with cache and dalvik before installing any new ROM.
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
Click to expand...
Click to collapse
i have latest recovery , TWRP 2.6.0.0 and i have given more than an hour to boot up and still nothing. i have been flashing ROMs like an addict since i got this phone last year, but when CM 10.1 stable was released i stayed on it till today, but now i cannot install any other ROM, i can odin to stock 4.1.1 ROM or install cm 10.1.2 which i did just now, but no other ROM, either TW based on AOSP based is working...which is very weird for me.
Were you able to fix this issue at all? I am facing the same issue, in my case, the phone was encrypted on stock TW. I roooted and put in CM 10.1.2 and now when I try installing Dandroid, the install itself would work but I am struck at the "type password to unlock the screen". If I reflash CM10.1.2, I can login fine. Any pointers?