I was running Starburst v1.9 and saw a thread on Themes & Apps with ICS transitions. I downloaded both just in case (ICS Transitions & Revert back to stock). I went into Root Explorer and checked my Clockwork/Backup and saw that I had a backup in there. I booted into Recovery and flashed the theme transitions for ICS zip and thus problem began.
I then went to restore to restore the backup and it seems like that file was corrupted because it wouldn't restore. I ended up flashing the revert zip file and wiping my rom. It doesn't boot but I can still get into recovery. I believe that the issue is that the theme was made for the v1.9.5 and I had v1.9 of Starburst.
I was messing around with it and I was able to boot back in and click on the Android to set it up. After a while the phone will go crazy and the screen will flicker on and off. The buttons at the bottom became useless. How can I recover from this.
** I used my friend's Sensation and downloaded v.1.9.5 and threw it on my SD. I booted into Recovery and flashed the ROM and it still won't boot up. Any suggestions? **
The phone booting up I think was a luck of the draw thing. Since then the phone has not been able to boot into the actual ROM. I've been without a phone since yesterday and I'm planning on going into the Sprint store and getting it swapped.
Did you wipe system, data, cache, and dalvik?
THEN reflash the rom?
Yes. I was a flashaholic on my Evo.
I notice another thread in q&a with people the same issue as mines. I'm lost and haven't had my phone working for two days now.
Here's what I did:
Delete system, wipe factory reset, cache and dalvik, flashed ROM.
Could it be kernel related? I'm confused. I have a wedding tomorrow and this couldn't have happened at a worse time. Coincidentally something happened on my At&t dumb phone so I'm phoneless.
stupid suggestion...is your battery low?
with the evo it would see corrupted if the battery was low. may not apply, but hey its a shot.
if you cant figure out, theres always Odin to cure your issues
ReDL the ROM and reflash. Try mounting USB storage while in recovery. Alternatively, Odin the stock .tar for a full refresh.
If you've already retired reflashing I'd go with odin back to stock
Sent from my SPH-D710 using xda premium
here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here
playya said:
here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here
Click to expand...
Click to collapse
Awesome. The wedding made me forget about my phone but now that it's over I'm missing it.
I will flash to stock and re-root.
Sent from my Nexus S 4G using XDA App
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.
Hi, I've decided to go back to stock so I flashed the 2.3.6 MD5 file via odin. The flash was successful but when the phone booted up, all i get is FCs and cannot go any further. tried flashing 2.3.5 and 4.0.3 and both ended up with the same results.
does anybody know whats going on?
Not sure what you did wrong or why it's acting up, but odin this one instead
http://forum.xda-developers.com/showthread.php?t=1705565
It's the official ICS and I Odin back to stock using this yesterday and haven't had any problems with this.
If you want to go back to GB let me know and I'll post some files I have for that, but I'm not sure why you would want to.
Powered by the SGSII soon the SGSIII
Finally I got it to work. I flashed the stock ROM and flashed clockwork recovery immediately afterwards. Then I wiped the data, cache, davlik cache, and fixed permissions.
Sent from my SGH-T989 using Tapatalk 2
Hey, I used to run CM9 on my phone, and eventually got tired of not having a few things work, so I flashed back to stock (rooted) GB for the time being. I was wondering what are the steps to go from what I have flashed now, to something like sbrissen's AOSP JB ROM or CM10. Like what files should I flash and in what order so I don't brick my phone?
Stumpalitious said:
Hey, I used to run CM9 on my phone, and eventually got tired of not having a few things work, so I flashed back to stock (rooted) GB for the time being. I was wondering what are the steps to go from what I have flashed now, to something like sbrissen's AOSP JB ROM or CM10. Like what files should I flash and in what order so I don't brick my phone?
Click to expand...
Click to collapse
Things you'll need: Odin, EL26 file (.tar version), Calks format all, JB ROM (I like CM10 but it's up to you) and Gapps for JB
Make a nandroid (if you dont have a custom recovery, go to next step). Boot into Odin mode and open up Odin on your computer and flash the EL26 file in the PDA version (turn off F reset time). Then go to recovery, (make a nandroid if you didn't before), wipe data, cache, and dalvik cache, (optional but recommended: flash Calks format all) and then flash whichever ROM you want and then flash the jb gapps and reboot
Almost all of the devs have instructions on their threads so you could follow that too. Hope this helps and happy flashing!
Sent from my Epic 4G Touch using XDA Premium
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.