[Q] Flashing a ROM help. - T-Mobile Samsung Galaxy S II SGH-T989

I am not new to this, I have experience with rooting htc and samsung devices. I have also searched, and searched, and searched with no luck on this.
However, I am stumped on this phone. I am using ODIN to flash the S/U script, I can gain root, install CWM and install it. I can load a ROM but one of 2 things happen: when I boot it up I get stuck in a boot loop, or it won't even install in the recovery.
I have a few questions / statements:
WHY am I getting stuck in this boot loop?
I am wiping cache/dalvik before I install the new ROM.
I am installing the ROM on the SD card vs the internal memory, is that why?
I got stuck 3 times in the boot loop, and I have had to use ODIN to flash my phone back to stock to start over.
Thanks in advance for the help.

If you have searched, and searched, and searched you would have realized that this is not development related.

for someone who's been around then, you should first off know that this belongs in q&a, not development.
that being said, which recovery are you using? i don't think that's your problem but a little more info would be helpful. also, which rom are you trying to use? when you're wiping, try using this, it'll wipe everything necessary. you only mentioned wiping your cache's so maybe that's it? in any case, flash the file i linked, then your rom. check the md5 on it and make sure it's a match. after you reboot, let your phone sit for 10 minutes and hopefully all will be well.

http://www.youtube.com/watch?v=JmvCpR45LKA

Mercuri82 said:
I am not new to this, I have experience with rooting htc and samsung devices. I have also searched, and searched, and searched with no luck on this.
However, I am stumped on this phone. I am using ODIN to flash the S/U script, I can gain root, install CWM and install it. I can load a ROM but one of 2 things happen: when I boot it up I get stuck in a boot loop, or it won't even install in the recovery.
I have a few questions / statements:
WHY am I getting stuck in this boot loop?
I am wiping cache/dalvik before I install the new ROM.
I am installing the ROM on the SD card vs the internal memory, is that why?
I got stuck 3 times in the boot loop, and I have had to use ODIN to flash my phone back to stock to start over.
Thanks in advance for the help.
Click to expand...
Click to collapse
If you look in the darkside rom thread, and some of the other rom threads, you will see three recommended wipes: darkside super, kernel and darkside cache. I would suggest you do all three.
Sent from my SGH-T989 using xda premium

Here is a big problem as well. You wipe cache and dalvik AFTER you flash the rom. I usually do it before as well but always after. That's like wiping before you **** and not cleaning up after
Sent from my SGH-T989 using XDA

odin version
jabberbox said:
http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I used an old version I couldn't get the latest one to work. But it wouldn't even load for me. It been a min sence ive used odin. But my replacement phone is at the house I'll pm you the steps I'll take. Everyone else try to be nice even if you think the question is stupid. Try to show some love
sorry i read wrong. i thought you couldnt gain root. as far as boot loops follow darksides wipe method it work. as far as my replacement phone rooted after first boot. my usb port is broke on my old phone
anyone know how to get back to stock with out it?
sence we are asking crazy ass questions?
dam auto correct

Questions go in the Q&A section

To those of you who helped by answering my question, thank you.
To those of you who told me I posted in the wrong sub section, get over yourself. Especially the guy with 13 posts.
I am wiping cache/dalvik before and after.
I am using CWM from the market, so it should be the newest version.
Ill check out the darkside thread.

You really don't need to wipe dalvik cache after a fresh rom install, unless you didn't delete the data partition (wipe data). And you certainly don't need to do it before and after.
Wiping cache and dalvik cache is really only useful if you make changes to the system but don't want to format the data. This includes flashing themes, and other enhancements, because most of them are replacing system files. On your first boot the dalvik cache gets built. (This is why a lot of devs recommend letting it sit for a bit before using it, it's giving it time to build the cache.)
The reason they tell you to wipe dalvik cache is let's say you're installing a theme, and it replaces systemui.apk and framework-res.apk, located in the system partition. The dalvik cache is already built for these files, so in some cases if you don't wipe the cache you'll boot loop. When you wipe dalvik, you are letting it be rebuilt with the current files.
Also, while we're on the subject, another misconception I see alot of, you don't need to wipe the dalvik cache after you wipe data. Dalvik cache is located on the data partition, it's a folder there. If you wipe the data partition, you've already removed it. (Not to be confused with cache partition, which is used for different purposes. That is it's own partition.)

Related

CM7 Stuck in Bootloop

Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn

acer ring from flex reaper rom, questions

So i just flashed this rom. and everything worked fine including the ring. So after, i flashed diff mods and colors for the acer ring and also the fix (that was updated 6/2/12 i believe?
then after taking some screen shots. a pop up said,
system ui has stopped unexpecticly. or something like that.
and now the botton in the center is gone. So i cant use it at all.
Checked settings and it is enabled.
What should i do to fix? just reflash any acer ring or just the fix. or just flash the hole rom again?
trevor7428 said:
So i just flashed this rom. and everything worked fine including the ring. So after, i flashed diff mods and colors for the acer ring and also the fix (that was updated 6/2/12 i believe?
then after taking some screen shots. a pop up said,
system ui has stopped unexpecticly. or something like that.
and now the botton in the center is gone. So i cant use it at all.
Checked settings and it is enabled.
What should i do to fix? just reflash any acer ring or just the fix. or just flash the hole rom again?
Click to expand...
Click to collapse
Reboot into recovery then wipe cache, dalvik, fix permissions then reboot check the ring.
Tapatalked from my Galaxy S II.
pio_masaki said:
Reboot into recovery then wipe cache, dalvik, fix permissions then reboot check the ring.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
ya. i got it working again.
i get nervous going into recovery to flash something. i already bricked my transformer tf300 last week. but i got it back up and running. i just get scared. I'm gunna do a noob mistake and permently brick one of my devices.
but i didnt wipe anything. i rebooted, but it was still gone, went in settings unchecked, checked acer ring, rebooted again then it was back
btw do you no how to change bookmarks in acer ring. too ur google/ chrome bookmarks instead of the stock ones?
I haven't noticed a way it seems to only show the stock browser, import them into the stock browser should put them on the ring too. Also delete from the stock any you don't want.
Huge edit: forgot to mention, any changes like flashing rings or mods etc. Should be followed by cache and dalvik wipe, and maybe fix permissions. That way old info is wiped so the new info can settle instead of it finding new info where it expects old info...make sense?
Flashing is fine provided you know what you're doing. Don't just do random things and you'll be OK. Only flash for your device, and mods meant for your rom, like the stuff civato posts for his FR rom. Recovery is safe as long as you use common sense and caution. If you don't know what something does, don't use it. Google it or ask, better to wait and know then guess and brick.
Generally always safe to do is wipe cache dalvik fix permissions. No data loss that you see occurs.
Safe if something broke and won't boot BUT you lose apps and settings is wipe data/ factory reset, done with wipe cache and dalvik and maybe fix permissions.
Wiping system wipes out android and you must flash a new rom or restore to boot into the system, and is always done with cache dalvik and data.
I strongly advise against partitioning from recovery if possible. If you must partition your SD card then use a PC tool not recovery. Don't initiate sd-ext wipes directly, if it happens on resets that's fine just don't do it by itself. I only mention this because on my phone we had a string of bricks due to bad recovery mapping and it was nuking our loaders instead. Stick to what I said and you're safe in recovery and flashing. I'm sure others can chime in with more info on this too.
Tapatalked from my Galaxy S II.
pio_masaki said:
I haven't noticed a way it seems to only show the stock browser, import them into the stock browser should put them on the ring too. Also delete from the stock any you don't want.
Huge edit: forgot to mention, any changes like flashing rings or mods etc. Should be followed by cache and dalvik wipe, and maybe fix permissions. That way old info is wiped so the new info can settle instead of it finding new info where it expects old info...make sense?
Flashing is fine provided you know what you're doing. Don't just do random things and you'll be OK. Only flash for your device, and mods meant for your rom, like the stuff civato posts for his FR rom. Recovery is safe as long as you use common sense and caution. If you don't know what something does, don't use it. Google it or ask, better to wait and know then guess and brick.
Generally always safe to do is wipe cache dalvik fix permissions. No data loss that you see occurs.
Safe if something broke and won't boot BUT you lose apps and settings is wipe data/ factory reset, done with wipe cache and dalvik and maybe fix permissions.
Wiping system wipes out android and you must flash a new rom or restore to boot into the system, and is always done with cache dalvik and data.
I strongly advise against partitioning from recovery if possible. If you must partition your SD card then use a PC tool not recovery. Don't initiate sd-ext wipes directly, if it happens on resets that's fine just don't do it by itself. I only mention this because on my phone we had a string of bricks due to bad recovery mapping and it was nuking our loaders instead. Stick to what I said and you're safe in recovery and flashing. I'm sure others can chime in with more info on this too.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
i thanked you for your last post i feel i owe you more thanks than replies you made specifically to me lol. yah i had no idea you had to wipe cache and dalvik and fix permissions. when flashing the acer ring. i thought only do that on roms. thats probably why my acer ring was giving me problems. havn't had one problem with it since i wiped.
but just to clarify, do you wipe cache/ dalvik before or after you flash (Acer ring for example) or both?
trevor7428 said:
i thanked you for your last post i feel i owe you more thanks than replies you made specifically to me lol. yah i had no idea you had to wipe cache and dalvik and fix permissions. when flashing the acer ring. i thought only do that on roms. thats probably why my acer ring was giving me problems. havn't had one problem with it since i wiped.
but just to clarify, do you wipe cache/ dalvik before or after you flash (Acer ring for example) or both?
Click to expand...
Click to collapse
Either or. Some say before flashing some say after. I do before and after but that's just because of my scripts doing it before I flash (full rom). Something like the ring I flash then wipe cache dalvik fix perms after, so any of the mods etc that are not rom installs. Full rom installs I full wipe before then flash everything then clear cache and dalvik. I only fix perms if I get FCs.
Tapatalked from my Galaxy S II.

Galaxy Note II Rogers Bootloop (HELP!!!)

I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
jethro650 said:
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1986893
This is the rom, i was using CMW to flash it, then it made me switch to TWRP (think its called that)......hope that helps.
Sorry I can't be of more help aside of redoing the installation of your recovery and redownloading the rom ( bad downloads happen) and making sure you do all the wipes (cache, dalvik cache and factory reset). If none of that works I'm sure someone more knowledgable than myself will chime in.
I've never run into a bootloop problem myself, but this might help you out :
hxxp://galaxynote2root.com/galaxy-note-2-tutorials/how-to-unrootunbrick-galaxy-note-2-with-stock-firmware/
Good luck
Have you had any luck with this yet? I've been unable to get my phone back up.
QuantumPSI said:
Have you had any luck with this yet? I've been unable to get my phone back up.
Click to expand...
Click to collapse
No luck, but then again i am a Mac user, so its a little more difficult for me to solve this problem.
Anirchy said:
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
Click to expand...
Click to collapse
Put another ROM on an sdcard. Take your battery out then press the button combo for recovery mode before you slip your battery back in. Then it'll force download mode. Reflash the new ROM after full wiping and you should be good.
Sent from my SGH-I317 using xda premium
Definitely a bad ROM. Run a MD5 checker against it prior to copying to the SD card. Note: your SD card could be the culprit.
If you have a recovery installed, ensure you WIPE everything, Fix permissions (i'm on CWM) and reflash the modem and carrier files POST rom install.
I experienced my first boot loop yesterday but I was able to recover from it thanks to a little common sense and patience. :fingers-crossed:
Good luck!
first of all, don't freak out, a bootloop isn't the end of the world. Sounds like it was a bad flash.
ppl above have obviously told you to wipe caches, and all that stuff and if it hasn't worked then you are still down and out.
I would suggest you get yourself into recovery - not going to explain that here as you said you were able to flash other roms and it didn't work and try flashing your nand backup - hopefully you have a nice clean backup from before you flashed. if so, clear caches, etc and then try flashing it it should be back to at least working.
your nand backup will have all your stuff in it as you would have had to backup from recovery, which means you'll at least still be rooted. you can then go ahead and get another rom - check the md5 and flash it

Stuck on boot screen

I have a rooted HTC Evo 4G. It is rooted with revolutionary and the s-off. I didn't root my device. I was playing with trying to install busybox from the busy box installer. It failed. But now that I have rebooted the phone(swapped a new battery on). It is stuck on the HTC EVO 4G white screen. I can get to the hboot screen and can get into recovery for Revolutionary CWM v4.0.1.4. I have tried some stuff. I'm here so it's safe to assume nothing worked. I have wiped the cache partition, I have tried the Fix Permissions option, Wiped Dalvik cache, wipe data/factory reset. I am knowledgeable with computers. Just not sure about this issue or which direct to go.
What can I do to get the phone back operational? Is there an image i can put on the sdcard and flash this thing with? I think I can manage that.
I'm so late in the rooting game here, there is so much information, not sure what I'm looking at. So I thought I would just go ahead and ask the questions. Maybe I won't get beat up too much and get pointed in the right direction.
I'm sure someone here can help you. A detail that you may have left out in your explanation is: what ROM you expect the phone to boot into.
Sounds like you just need to re-flash a ROM while you are in recovery.
Plenty of ROMs around here to choose from. I might recommend a very simple "stock" ROM for starters.
Later on, consider using a different recovery going forward. Evos historically have had issues with CWM. Try Amon Ra or SmelkusMOD...
Sent from my PC36100 using xda app-developers app
Yup, I would recommend Smelkus after you fix this
Go into recovery and make a full backup first (this way you can advance restore data later)
Then, as suggested above, grab a stock rom and flash it through recovery (making sure to wipe EVERYTHING)
Last, try to boot up your phone. It should work
Once it does, restore any data if you need to...if not, flash SmelkusMod recovery and then flash your rom of choice
Sent from my PG06100
I have the revolutionary recovery. Do I need to replace that with the smelkus mod?
a94cobra said:
I have the revolutionary recovery. Do I need to replace that with the smelkus mod?
Click to expand...
Click to collapse
You have the revolutionary BOOTLOADER. There is no "revolutionary recovery"
Sent from my PG06100
If you've wiped cache, dalvik cache, and factory reset your phone then you have no ROM to boot into. Flash a rom and you'll be good to go
kendallc123 said:
If you've wiped cache, dalvik cache, and factory reset your phone then you have no ROM to boot into. Flash a rom and you'll be good to go
Click to expand...
Click to collapse
Thats incorrect....the rom isn't stored on the data partition, which is what a factory reset wipes
ROMs are loaded from the /system partiton
Sent from my PG06100
CNexus said:
Thats incorrect....the rom isn't stored on the data partition, which is what a factory reset wipes
ROMs are loaded from the /system partiton
Sent from my PG06100
Click to expand...
Click to collapse
I was assuming he had formatted everything, including the system. If you didn't, my bad. Sorry

[Q] In need of some assistance.

So i have flashed for awhile and never have encountered this problem. i was on lbj7 i went back to stock. did Ota upgrade to 4.1.2, rerooted flashed another rom and now all it does is forceclose. How do i clean the system completly so i can reflash a fresh clean install. I normally wipe Delvik+cache+ factory what else can i include to insure i have a 100% clean flash?. Any and all help is appreciated thanks!
Wipe internal storage will erase anything on the internal just as it states. What ROM are you trying to flash? Also what recovery do you have and is it up to date. If you want the ultimate clean install I do this, make sure the and if you need gasps or any other file is on the external card
Wipe data, cache, dalvick, system this removes the ROM, internal and maybe even format data. Flash ROM wipe cache and dalvick and if you need to gasps the wipe cache and dalvick the boot. But make sure your recovery is up to date, I use twrp which is on 2.4.4 right now. And you have the correct gasps if needed. Good luck.
Sent from my SPH-L710 using Tapatalk 2
Hey Thanks Giantay.. I am trying to reflash Goodness 9.0.4. Its forceclosing Touchwiz and Apex and all the other.. I seem to have a Wakelock aswell Media is stuck at 40% Battery Useage. I use Cwm. Maybe i should switch to Twrp..
thaset said:
Hey Thanks Giantay.. I am trying to reflash Goodness 9.0.4. Its forceclosing Touchwiz and Apex and all the other.. I seem to have a Wakelock aswell Media is stuck at 40% Battery Useage. I use Cwm. Maybe i should switch to Twrp..
Click to expand...
Click to collapse
To install TWRP the easiest way just download Goomanager from the Play Store here https://play.google.com/store/apps/...anager&feature=nav_result#?t=W251bGwsMSwyLDNd open it go to settings and select Install OpenRecoveryScript, This will download and install TWRP's newest recovery. You could also check the md5sum to see if it's a good download. Sometimes the files that you download are corrupted but I have never had it happen, and I have flashed endless amounts of ROMs on different phones, but it happens people say. I am unfamiliar with that specific ROM but try searching in the thread for it to see if anyone else has had similar experiences and have a way to fix it. Searching is your friend, search and read a lot will ussually solve your problem, and if you don't turn up anything don't be afraid to ask a question instead of doing something that might be unsafe or worries you.
I did as u suggested and just tried re flashing using Twrp. Awaiting Results as first boot aproaches. Thanks again for the helping hand.
Just a heads up. Try and hit the thanks button on these forums if people help you in any way. I don't really care about it but it helps some people especially devs and what not.

Categories

Resources