Database Users

CM7 uh ohs

I just flashed CM7 supersonic after wiping everything as usual. However, once it began booting up it seems to have gotten stuck on the Cyanogenmod7 initial loading screen with the circular arrow that loops around the android on a skateboard. It has been doing this for an hour now. I just took the battery out and turned it back on and it is simply doing the same thing now. Any suggestions?

Wipe and reflash or restore a nandroid. Use caulkins format all zip.
Sent from my PC36100 using XDA App

Mine did this and I cleared the dalvik cache and it worked, hope it helps
Sent from my PC36100 using XDA App

bellasaurus said:
I just flashed CM7 supersonic after wiping everything as usual. However, once it began booting up it seems to have gotten stuck on the Cyanogenmod7 initial loading screen with the circular arrow that loops around the android on a skateboard. It has been doing this for an hour now. I just took the battery out and turned it back on and it is simply doing the same thing now. Any suggestions?
Click to expand...
Click to collapse
several people have reported when using clockwork recovery that it does fully delete cache data. most instructions I read suggesting deleting the cache twice.

gqstatus0685 said:
Wipe and reflash or restore a nandroid. Use caulkins format all zip.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
+1 I had a lot of issues with clockwork not wiping right and stupid problems because of it. The format all zip has saved me from ripping all my hair out lots of times so far.
It is here. It is at the bottom of the first post. And even though it says for 2.1/2.2 it will still work, formating at the recovery screen has nothing to do with your android version
http://forum.xda-developers.com/showthread.php?t=785271

bellasaurus said:
I just flashed CM7 supersonic after wiping everything as usual. However, once it began booting up it seems to have gotten stuck on the Cyanogenmod7 initial loading screen with the circular arrow that loops around the android on a skateboard. It has been doing this for an hour now. I just took the battery out and turned it back on and it is simply doing the same thing now. Any suggestions?
Click to expand...
Click to collapse
When you have been stuck here try holding down the power button. Usually I get the power down menu and just hit back and I'm good to go.
Sent from my PC36100 using XDA App

I had this same thing happen several times I just kept doing battery pulls and restarting the process eventually it worked. That being said, I've moved on to the new Fresh 4 Beta with Gingerbread now and I couldn't be happier. The CM guys do great work considering what they have for resources, but the HTC guys make better roms from a hardware standpoint, so a Sense Rom to me is just vastly superior. Not that I actually run the sense launcher.

Gingerbread 3.0

Where can I find the download link for the new gb.
Dinc

I'm not sure what you're asking for. Honeycomb 3.0 (which is not available for the Incredible) or Gingerbread with Sense 3.0?
Sent from my awesome sauce Incredible uisng Miui

I think gingerbread with sense 3.0. Sorry.
Dinc

There are several roms with what you are looking for in the development forum.

Oh ok. And do these install the same way. I'm still using the old clockwork recovery.
Dinc

Yes they should install like normal. Check the OP's for the ROM though. All require hboot .92 and CWM 3.0.0.x.
I recommend giving JoelZ's kingdm rewind 3d a go. very smooth

Yeah I'm still using the old cwm and I have never messed with cwm3 so how do I install the new newest cwm.
Dinc

You can use rom manager or you can flash the recovery manually in hboot. Files at www.dougpiston.com

RE: Multiple wipes
http://www.cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache

Not trying to start a big debate, just pointing out that wiping multiple times isn't doing anything but adding more time to your flashing process. Hopefully this helps.

I only wipe everything once, flash vr superwipe, then flash rom. Works fine on all.
sent from whatever damn rom im using this hour!

k_nivesout said:
Not trying to start a big debate, just pointing out that wiping multiple times isn't doing anything but adding more time to your flashing process. Hopefully this helps.
Click to expand...
Click to collapse
You obviously need to wipe three times and then flash the ROM twice. And reboot about 4 times. One each is not enough. Pull your battery a couple of times as well.

Is installing the new cwm the same as flashing a radio.
Dinc

If you take the time to read what I linked, it explains everything. When you're telling your recovery to wipe, it is a routine run within code. Doing a secondary wipe or even a third is just running the same exact command again. Logically, why would CWM run the same exact command differently, necessitating multiple wipes to get the same result?
There's no "randomness" built into the recovery that would result in the command not being run, or run differently, when you select it.
Its not like a physical action, where the more you wipe, the "cleaner" it gets. Again, it is a routine run within code, and it is not variable or random.
If there was any perceived benefit to the wiping procedure that you mentioned, I'm willing to bet that its due to wiping the /system and /boot partitions, which isn't done when you wipe data/factory reset and wipe cache in the main menu. This is something that should be, and usually is, included in the rom's updater script, but may be forgotten by the dev. Some people have mentioned that recovery version 3.0.0.8 does not work well with AMOLED incredibles. I can't speak for that myself, but in the event that there is a problem, the resolution would be using the 3.0.0.7 recovery, not wiping multiple times.
And I don't think you're correct in assuming that "all the devs" recommend the multiple wipe approach, I think you'll see that plenty do not, including the cyanogen dev who wrote the article I linked to (BTW, he is the one that got CM7 on the Droid X, a phone with a locked bootloader, so I'm assuming he might know what he's talking about.)
That is all..

snapper915 said:
Is installing the new cwm the same as flashing a radio.
Dinc
Click to expand...
Click to collapse
They are totally different, CWM is a recovery, radios are well, radios. They are flashed the same way though (in bootloader).

Awesome. Thanks. I don't have to rename any thing.
Dinc

cvbcbcmv said:
you mean like PB31IMG.zip? No, nothing like that.
Click to expand...
Click to collapse
Sweet. Thanks for everyone's help.
Dinc

HELP

Used this method to Root, unlock bootloader and get SU
http://forum.xda-developers.com/showthread.php?t=1202883
Flashed over CM7 beta, rebooted system, and I get stuck at the dual core screen. I think my battery was really low, because when I pull the battery, I get the "battery too low to flash". But its hard to tell when the battery is charging. Does it charge (AC) when I am in CWM? Or anytime when its plugged into AC?
IT dosent sound like a hard brick, just a soft brick perhaps. I hate rooting phones cause of this.

does not charge while in cwm but powered down it should charge

When I power down, and plug into outlet, it just boots up and stays at Dual Core screen with unlocked.
EDIT: Flashed a different ROM and it seems to be working fine. God damn Atrix and Cyanogen. Was never this hard on HTC Aria to do all this crap.

+1. BUT, you shouldn't need to flash, go into android recovery and factory reset and erase cache and reboot and you should be ok. I got stuck in boot loop the first timeI flashed CM7 prebeta 1 the first time. Good habit to wipe everything (except system) after installing ROMs.

Its backwards to me that you wipe everything AFTER installing ROMs.
But everything is working fine now.

It's just a precaution to make sure there is nothing to conflict with the new ROM

Phoneguy589 said:
It's just a precaution to make sure there is nothing to conflict with the new ROM
Click to expand...
Click to collapse
this works with CM7, but you don't want to get into the habit of doing it for every ROM. some ROMS have goodies built into the data partition, which you won't be able to get if you wipe it after installing

Alcapone263 said:
this works with CM7, but you don't want to get into the habit of doing it for every ROM. some ROMS have goodies built into the data partition, which you won't be able to get if you wipe it after installing
Click to expand...
Click to collapse
+1
I have one backup. I always manually format before flashing, personsally.
Sent from my MB860 using XDA App

[Q] cant load roms past bootanimation

everytime i flash a rom, it gets stuck at the bootanimation or the setup wizard any suggestions? i used to flash roms before but it started happening recently and i cant pinpoint why it freezes

My friend had that issue too. It turned out he wasn't wiping /system before he flashed. Too much crap built up in there from too many ROMs.

estallings15 said:
My friend had that issue too. It turned out he wasn't wiping /system before he flashed. Too much crap built up in there from too many ROMs.
Click to expand...
Click to collapse
I use 4ext app and do a ext 4 wipe and it seems to work okay for me. sometimes ill manually wipe all partitions but usually dont need to.

Yeah I tried wiping everything
I did factory and cache
Then dalvik
Then under mounts and storage I format system,data,and cache
Maybe I'll try 4 ext

Look at the logcat.

If you have clockworkmod lower than v3, and you flash a gingerbread rom, it naturally get s stucked by bootanimation. But if you have the latest one of the recovery, which supports ext4, and it stuck at the bootanimation (not the white splash screen), then you must wait until the drivers are initialized.
Sent from my Black Ice'd Glacier using XDA App

My cwm is the latest one I believe (5.0.2.0 or something like that)
I tried loading zipnets ice rom and it hangs at the clock animation
I tried the new sense 3.6 rom. (Forgot name) and sometimes it freezes at the bootamimation,setup, or at the home screen
What do you mean wait for drivers to install?
Sent from my Transformer TF101 using XDA

The first start after a rom install is always the longest one. That is usual. Try to wait about three - five mins and then it is done. After that you can use it.
Sent from my Black Ice'd Glacier using XDA App

Also after it boots, give it a few minutes to settle in and turn on mobile netowork ect.
Sent from my Sense 3.6 Glacier using XDA Premium.

How long should I wait? Last time I waited 20 mins and it was still frozen
edit: ok i tried 4ext and used the format everything except sd card and still get a frozen boot animation any other suggestions?

Did you follow Jack_R1's suggestion and run logcat?

so after hours of tinkering around these boards and through everyone's help, i found out i have the bad emmc which is what im assuming the problem is but why was i able to flash roms before? or was it just luck?

HELP! Odin and Heimdall won't work... Alternative to flash to stock?

First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
EDIT:
I have TWRP 2.5.0.3 on my phone

sebbo1 said:
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
Click to expand...
Click to collapse
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot

Colonel Sanders said:
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Click to expand...
Click to collapse
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.

sebbo1 said:
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
Click to expand...
Click to collapse
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.

Colonel Sanders said:
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Click to expand...
Click to collapse
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?

sebbo1 said:
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
Click to expand...
Click to collapse
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.

Colonel Sanders said:
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Click to expand...
Click to collapse
Are you talking about slimroms.net? If you are, which addons do I download?
EDIT: nevermind. I downloaded the AIO (all in one)

sebbo1 said:
Are you talking about slimroms.net? If you are, which addons do I download?
Click to expand...
Click to collapse
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.

Colonel Sanders said:
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Click to expand...
Click to collapse
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website

sebbo1 said:
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
Click to expand...
Click to collapse
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.

Colonel Sanders said:
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Click to expand...
Click to collapse
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?

sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I would say so myself, Odin back to stock, but since you have a mac and I'm not sure if Heimdall support the S4 try this:
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Format /data
Format /internal (If CWM-based recovery)
Flash ROM, addons, reboot

sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen

sebbo1 said:
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
Click to expand...
Click to collapse
That means the battery is low... Charge it up some... Check your PM for my gmail if you need some help, posting back and forth can take a while.

Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore

sebbo1 said:
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
Click to expand...
Click to collapse
Glad you got it going man, and enjoy Slim, it's hands down the best ROM there is if you prefer minimal with tons of customization options.