Database Info

[Q] help? boot looped while flashing ics

so i only have a mac and i successfully flashed ics on one skyrocket that was already rooted but it didn't work on the other and is now stuck in a constant boot loop at the att splash screen. anybody know how i can fix this?

ShawnXVIII said:
so i only have a mac and i successfully flashed ics on one skyrocket that was already rooted but it didn't work on the other and is now stuck in a constant boot loop at the att splash screen. anybody know how i can fix this?
Click to expand...
Click to collapse
Reflash it boss.

i tried man like 4 times =/ and even different ics roms..nothings working

similar problem, mine starts loading the rom then freezes.

Are you guys following the instructions? Pull the battery and reboot into CWM and wipe the cache, dalvik cache, factory reset

Are you wiping and clearing multiple x's
Sent from my SAMSUNG-SGH-I727 using xda premium

i wiped dalvik, battery, and did factory reset, i flashed the ics radio then flashed the rom but nothing

ShawnXVIII said:
i wiped dalvik, battery, and did factory reset, i flashed the ics radio then flashed the rom but nothing
Click to expand...
Click to collapse
You have to wipe them at least 3 times. Pull the battery and wipe everything again multiple times

alright ill try it and let you know what happens

still nothing it gets to boot animation makes like a little click noise and reboots

ShawnXVIII said:
still nothing it gets to boot animation makes like a little click noise and reboots
Click to expand...
Click to collapse
You might have got a bad download. Redownload and check the md5 and make sure the download is good

You know what? This might be dumb reading some of the newer posts around here but are you using a newer recovery mod? Also use the darkside super wipe, I find it to work better than doing the wipes manually.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA

Try darkwipe, it was the way how I got ics to boot.
Sent from my SAMSUNG-SGH-I727 using xda premium

tried getting a fresh download, still no luck...ill try dark wipe tomorrow and let you guys know how it goes.
I don't think i have the latest cwm either but it worked for my phone i don't know what the deal is.

I use darkside wipe, clear cache and dalvik cache, then format /system /data and /cache.
I know its overkill but I find I pick up less ics bugs when I do it.

Have you tried the one click method?
Sent from my SAMSUNG-SGH-I727 using xda premium

The battery finally just died from all the reboots and I left it alone over night then it came on after I put it on the charger and rebooted but was still buggie so I used super dark wipe and flashed again and now it works great...I definitely recommend that wipe when flashing
Sent from my SAMSUNG-SGH-I727 using XDA

[Q] SUPERWIPE for NEXUS S?

Hey - has anyone tried using SUPERWIPE on NEXUS S?
eg http://forum.xda-developers.com/showthread.php?t=1477955
I have been having some problems with CWM not always wiping properly, and then me getting FCs and laggy responsiveness after installing well-rated ROMs.
Superwipe is said to do a better job, but does not seem to be for the NEXUS S per se, which is why I ask.

ac17 said:
Hey - has anyone tried using SUPERWIPE on NEXUS S?
eg http://forum.xda-developers.com/showthread.php?t=1477955
I have been having some problems with CWM not always wiping properly, and then me getting FCs and laggy responsiveness after installing well-rated ROMs.
Superwipe is said to do a better job, but does not seem to be for the NEXUS S per se, which is why I ask.
Click to expand...
Click to collapse
Not needed if you use a sacrificial lamb and do the aztec dance...

I used to use wipe zips until some versions of CM9 refused to install/boot afterwards. Now I manually mount and format data, system, cache, and boot prior to installing a rom. Haven't had a problem since switching to this method.
Sent from my Nexus S 4G using Tapatalk 2

http://forum.xda-developers.com/showthread.php?t=1365158

Super wipe is overkill and not needed . Most recoverys work great to wipe and flash any rom fine.
-XDA MODERATOR-

ac17 said:
Hey - has anyone tried using SUPERWIPE on NEXUS S?
eg http://forum.xda-developers.com/showthread.php?t=1477955
I have been having some problems with CWM not always wiping properly, and then me getting FCs and laggy responsiveness after installing well-rated ROMs.
Superwipe is said to do a better job, but does not seem to be for the NEXUS S per se, which is why I ask.
Click to expand...
Click to collapse
Wiping storage ain't like wiping your ass, 1 wipe suffices.

Cool! - Thanks for the wipe all info.
It seems that I have never wiped 'Boot' in CWM and i have gone through countless custom ROMS by different makers.
Maybe that's the problem (I normally just do 'factory reset' and 'wipe Dalvik')
Is it true that if you wipe 'boot' in CWM (or if using the full wipe all script), that you need to have already put your new ROM on your SD card because you MUST follow a wipe of 'boot' straight away with an install of a new ROM, else you will brick your phone?

Oh, one final question - have you guys ever in CWM hit 'format sdcard' to fine that once you boot up and browse your SD card the format didn't work?

Braneless said:
I used to use wipe zips until some versions of CM9 refused to install/boot afterwards. Now I manually mount and format data, system, cache, and boot prior to installing a rom. Haven't had a problem since switching to this method.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Same here.......
10....0011....10101

ac17 said:
Cool! - Thanks for the wipe all info.
It seems that I have never wiped 'Boot' in CWM and i have gone through countless custom ROMS by different makers.
Maybe that's the problem (I normally just do 'factory reset' and 'wipe Dalvik')
Is it true that if you wipe 'boot' in CWM (or if using the full wipe all script), that you need to have already put your new ROM on your SD card because you MUST follow a wipe of 'boot' straight away with an install of a new ROM, else you will brick your phone?
Click to expand...
Click to collapse
My ROMs have never been on the root of my SD card (I like to organize all my ZIPs in folders)... Probably not a good idea haha. And I have always wiped boot last... never been bricked. I've been boot looped but that's always been a bad ZIP file's fault. And I make NANDROIDs for just such loops.
Sent from my Nexus S using Tapatalk 2

madd0g said:
Wiping storage ain't like wiping your ass, 1 wipe suffices.
Click to expand...
Click to collapse
Sent from my Nexus S using xda app-developers app

Braneless said:
I used to use wipe zips until some versions of CM9 refused to install/boot afterwards. Now I manually mount and format data, system, cache, and boot prior to installing a rom. Haven't had a problem since switching to this method.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Same thing for me.
And CWM wipes works perfectly. Don't be so lazy men.

Just do it this way.
One clicks and wipe zips will fail so you should learn what they are doing in case you need to do it yourself.
http://forum.xda-developers.com/showpost.php?p=27350690&postcount=4976

Dirty vs Clean Flash

A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...

Brian Gove said:
A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...
Click to expand...
Click to collapse
If I switch ROM's I factory reset then wipe cache and dalvik cache. If it's a theme for example I only wipe cache and dalvik cache since the theme is suppose to be made for your ROM right?....don't see the reason to reflash the ROM as well.

Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium

Il throw a vote to whichever works.. I usually dirty wipe.. If I have issues then clean it and try again.. With nightlies I tend to be fine dirty a lot, but even still I will do a clean every couple weeks just because..

why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form

So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app

What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?

xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Dirty wipe
Sent from a SYNERGIZED GalaxySIII

When I dirty flash, I wipe data cache n dalvik cache. Once I flash what I wanted, I wipe those two once again n select "fix permissions" just in case
Sent from my SCH-I535 using Tapatalk 2

apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Click to expand...
Click to collapse
I disagree. I believe a dirty flash also wipes system. If you are 100% certain that your ROM build effectively wipes system as part of it's install routine, then you could skip this step, however I always wipe system to be safe. This works for me and I rarely need to wipe data or sd card(s).
---------- Post added at 11:01 AM ---------- Previous post was at 10:57 AM ----------
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that?
Click to expand...
Click to collapse
When changing Kernels but not the ROM in a separate recovery session than a ROM flash, you don't need to "dirty wipe." Just wipe cache and dalvik. Dalvik wipe is key so that the dalvik virtual machine can be rebuilt by the new kernel.

Thanks for the info guys.

I usually dirty on nightlies until I have issues. Always clean when switching roms.
Sent from my SGH-I535 using xda app-developers app

It is always good to complete wipe when switching roms.
Sent from my SCH-I535 using xda premium

What if im just switching between stock rom nandroid backups? Can I just restore from one to one? I only have two backups anyways both for stock. Never flashed a rom before
Tap'n

grin0048 said:
This isn't meant to be rude or anything, I'm just honestly wondering if there's any logical reason to think this is substantively different than just not wiping data?
Click to expand...
Click to collapse
I find that this method works better than just wiping cache and dalvik, since im advance restoring data over a clean flash. both ways are considered dirty flashing tho.

I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?

coldhardtruth said:
I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?
Click to expand...
Click to collapse
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app

droidstyle said:
why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form
Click to expand...
Click to collapse
Factory reset doesn't touch the davlik(Which I speculate(Guess) has to do more with the kernel than anything)
apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This is what I meant as a dirty flash when I made the thread yes...
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Usually when I flash a new kernel, or a different kernel, I just wipe the davlik cache and I am fine. There was some reboots after the first boot on the AOSP ROMs but afterwards it ran fine.
SlimSnoopOS said:
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
SlimSnoop is correct. According to one of the developers of a very prominent ROM the IMEI issue was because our phones got confused sometimes(Randomly phone to phone) and tried to reset during a flash. The data it tried to reset was bogus, therefor losing IMEI. He is also correct far as the wiping battery stats. It's only usefull when you have really strange results with battery. Google for the real reason to use them.
Far as backing up your IMEI so you will never run into the problem of losing it.... go into your terminal (almost every ROM has a Terminal emulator)
Type this:
su
then hit enter. Grant permissions
then type:
reboot nvbackup
then hit enter. This will make your phone do some shyt and reboot, but you really shouldn't need to worry about your IMEI after this. Regardless of how many ROMs you flash or what you do or who you date or who you kiss, etc... blah blah....
This really should be the end all for the IMEI...

annoyngduck said:
Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
New rom only when their bases are different , like going from ics to jb, or the dev says to do it (Even then Ill try it without a wipe because im lazy).
Themes I never wipe anything
Nightlies never wipe anything.
Edit: If I do have issues I then go back and wipe delvik and cache . That usually straightens out any issues and allows me to keep my setup.

tonu42 said:
Hey but you know I'm right
Click to expand...
Click to collapse
Actually you're not right.
Sent from my SCH-I535 using Tapatalk 2

I seriously can't figure it out.

I've been tinkering with androids for well over a year now and have rooted unlocked and s-off'ed amongst other things many different devices. For some reason I'm having trouble flashing kernels to my s3. Yes I'm unlocked and yes I'm flashing aosp kernels to aosp roms and touchwiz kernels to touchwiz roms. The problem seems most persistent on aosp roms and yes I've also checked that they both had the same cm10 commits. The only kernel I could get to boot was clean kernel on beans custom. Other than that no other kernels will work. The device will boot then the screen will start glitching up and then eventually bootloop. I've also made sure to wipe dalvik and cache plus fix permissions. I've also tried just flashing the kernel after doing a full wipe and starting with a new rom and have root 66ed back to stock and re unlocked. Is there something I'm missing here? I'm getting frustrated as I love custom kernels. Oh and the latest combo I tried was liquid smooth rc3 and lean kernel 1.0. Thanks guys.
Sent from my SCH-I535 using xda app-developers app

did you try wiping cach, davik cach, and fix permissions AFTER flashing then reboot?
Ofc wipe cach and dalvik cache before also.

My usual process goes something like this
*Wipe Cache
*Wipe Dalvik
*Flash Kernel
*Wipe Cache & Dalvik again
*Fix Permissions
Works like a charm every time.
Samsung Galaxy S3

i have had the same trouble once...fixed it by flashing back to a stock kernel first.
try this:
wipe cache & dalvik
flash stock kernel.zip- http://db.tt/ceeDTAfz
flash custom kernel
reboot

Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app

sumredhed567 said:
Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app
Click to expand...
Click to collapse
stock kernel = stock TW kernel
Sent from my SCH-I535 using xda app-developers app

Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app

sumredhed567 said:
Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
another thing you might try is formatting system in cwm.

droidstyle said:
another thing you might try is formatting system in cwm.
Click to expand...
Click to collapse
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!

sumredhed567 said:
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!
Click to expand...
Click to collapse
now when you odin back to stock, your booting into stock recovery after flashing the rom(root66) and doing a data wipe/factory reset correct? you said full wipe, but just want to be clear. it may be corrupted internal memory and might need to be reformatted.

I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app

sumredhed567 said:
I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
follow section 6 of my guide...link in sig!

Always perform a full/mega wipe as:
1) Wipe data/factory reset
2) Wipe cache partition
3) Wipe dalvik cache
4) In mounts/storage section wipe /system
5) wipe /data
6) wipe /cache
7) wipe /preload
Then flash new ROM.
For flashing a kernel, please perform steps 2 and 3.

[Q] [Beanstalk] Random Reboots

Over many iterations of Beanstalk my phone has had random reboots, sometimes hanging at the beanstalk logo, other times it will just freeze and i'll push the power button for screen on and nothing will happen. I'm trying to figure out if my hardware is flakey, anyone know an app for that? Or if maybe my installation procedure is the problem (it is posted below). I did a clean install of 1.205 yesterday and already 3 crashes. I wiped the dalvik and regular caches this morning after the 3rd crash to see if that may help. Any advice is appreciated. I dirty flashed 1.205 before and it didn't even seem this bad so not sure if it is completely random or what. Thanks!
Installation Procedure:
Flash Clean Wipe - Stock UCLB3
Factory Reset (Erase SD)
Flash Again w/ Bootloaders
Factory Reset (+Erase)
Flash Clean Wipe - Entropy Kernel
Factory Reset (Erase SD)
Copy CM9, Bean ROM, Gapps to SD Card
--CWM CM9--
Flash CM9
Reboot System (Do NOT use 'reboot recovery' in advanced)
System Hangs -> 3 Finger CWM Boot
Mounts -> Storage
Format system, data, cache
Flash CM9 again
Reboot
After boot -> Factory Reset (DO NOT erase SD)
--CWM--
wipe date/factory reset
wipe cache
advanced -> wipe dalvik cache
Install Beanstalk ROM
recovery reboots
auto resume install (if not flash zip again)
Install gapps
wipe cache
advanced -> wipe dalvik
After boot -> Factory Reset (Erase SD)
Also, I am not overclocking or undervolting, someone suggested that before so I turned it all off.

Sounds like your restoring apps and data with titanium backup or something. Are you? If so, that explains the reboots. I highly doubt it's the rom
Sent from my SGH-I997 using Tapatalk 2

eZdubzitmk4 said:
Sounds like your restoring apps and data with titanium backup or something. Are you? If so, that explains the reboots. I highly doubt it's the rom
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
I seriously doubt it is the ROM, not trying to blame it.
Trying to figure out if my hardware is going flakey and causing it, if I'm doing something wrong with the install, or some other thing I'm messing up.
I do restore with Titanium, but I only restore apps, not data.
The only other major thing I have changed that I can think of is the DPI to 182.

Ok the apps you restore, are any of them backups you made when you where on a gingerbread rom?
Like, say you were on GB and backed up some apps. Then flashed ICS, then JB, and then restored apps?
Sent from my SGH-I997 using Tapatalk 2

eZdubzitmk4 said:
Ok the apps you restore, are any of them backups you made when you where on a gingerbread rom?
Like, say you were on GB and backed up some apps. Then flashed ICS, then JB, and then restored apps?
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Nope, all backed up from previous JB ROMs. :\
Do you know any apps that can test the cpu/ram to see if it is going wonky? I looked but only found one that doesn't support the Infuse.

blastagator said:
Nope, all backed up from previous JB ROMs. :\
Do you know any apps that can test the cpu/ram to see if it is going wonky? I looked but only found one that doesn't support the Infuse.
Click to expand...
Click to collapse
Use cpu spy.
It will tell exactly what the cpu uses and if it's going into deep sleep (very important).
I'm thinking there is an app that's preventing the phone from going into deep sleep
Sent from my SGH-I997 using Tapatalk 2

eZdubzitmk4 said:
Use cpu spy.
It will tell exactly what the cpu uses and if it's going into deep sleep (very important).
I'm thinking there is an app that's preventing the phone from going into deep sleep
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
It actually hasn't crashed since I erased the two caches again. Hope I'm not jinxing it now. Been up 35 hours. 53% of that time in deep sleep.