Ive just installed Clockwork Mod v4 and Cyanogenmod (latest) and i am stuck on a screen loop with repeatively shows the Cyanogen loop with the blue droid on the skateboard with a circle around him- it keeps repeating the full cycle over and over again, i have taken the battery out but nothing, help?
Try re-flashing the rom, see if it changes
Yeah i managed to fix it thanks to another guy on these forums- reflashing Clockwork did the trick.
Had exactly the same problem with my G5, Flashed one. Fine. Flashed the 2nd one and it boot looped, flashed a different firmware and the same thing happened, weird! Closed/repoened odin Disabled auto reboot and flashed CM7 and it was fine
i experienced this too when I first tried flashing cm7.1, plus the I5503DXJP7 baseband, after using the MAD rom for a good 4 months or so. I reflashed the stock 5503 rom, then upgraded the baseband and again experienced the boot loop.
i found a 5503 rom on samfirmware that came with the I5503DXJP7 baseband i needed. that one booted up fine. then i flashed cm7.1. that worked fine too. so this turned out to be a problem with the baseband (i think).
but cm7.1 came with this crazy loud headset volume and i use the g5 a lot for calling at work. had to go back to MAD2.0.9, this time flashed using CWM (very cool: thanks to whoever got that onto the G5)
I fixed this problem a while back aha, thanks for the replies though
Currently awaiting for my phone to be repaired -.-
I had the same problem...I repeated the steps and obivliously it worked
I used the CM7 for a while. I reflashed the stock ROM and the bootloop started. Than i freaked out and reflashed all by odin. It works.
Sent from my GT-I5500 using Tapatalk
Related
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
kim2rock said:
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
Click to expand...
Click to collapse
Download might have been corrupted or you flashed SC and then flashed the theme without rebooting in between.
Thanks jonesya13!
I'm pretty sure I rebooted in between, but I will try to re-download the file and then flash the theme again as you suggested.
This happened to me on both the 3.1 & 3.1.2 with superclean 2.9.2. I booted fully into superclean as well before flashing the theme after a cache/dalvik wipe. Battery pull worked both times. Rebooted normally after that.
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
kim2rock said:
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
Click to expand...
Click to collapse
I had the menu and home button problem as well, ended up flashing, I think the EC10 kernal, and it fixed that problem for me.
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
kim2rock said:
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
Click to expand...
Click to collapse
You might as well as update to jt's ec10. BLN + Sound + Color.. Epiiiic
Just wipe cache/dalvik
Rocking Frankenclean 2.9.2 Voodoo/EC10+Sound+BLN+Color/Nitro Ultra Honeycomb v3.1/XDA Premium
xHoLyx,
What might be some advantages of jt's EC10 over regular EB01, in your opinion? I'm not too familiar with kernel replacement, so reading relevant posts might take some time. thx!
I tried 2.2 out a few weeks ago and decided I couldn't live without Voodoo Sound and BLN so I decided to wait it out. Obviously we have these enhancements available for Froyo now, so I made the jump to JT's initial EC10 release.
Everything worked fine, I just didn't feel that "snappiness" I had before. I thought maybe it had something to do with being undervolted (even though only slightly.) I saw that there were some problems with imnuts initial kernals he posted and waited to flash the updated (fixed) link for 0328_imnuts_sv_voodoo.zip. I flashed last night, booted up, and played around for a little bit and everything was working great. I had it plugged in to charge overnight. That brings me to my issue...
I woke up this morning, reached over to turn my phone on and I got NOTHING. No boot, samsung, lights, nada...I thought "****, I really bricked my phone now." I tried booting into recovery using the 3-button combo, plugging it in my computer to try download mode, plugging my charger in different outlets,etc...The phone seemed like there was no sign of life. I was ready to head to Verizon before work then decided to plug in my car charger for ****s and giggles and sure enough...IT WORKED! It started charging and I turned the phone on. Now I am at work and the phone seems to be working just fine...I even have the usb plugged in my computer and it is charging now (The same one that didn't work this morning.) This has never happened to me before and it was pretty scary. I have had to ODIN before, but I was worried that wasn't even an option. Thanks god everything SEEMS to be working fine right now, though that made me a little concerned.
Do anyone have ANY idea what might have happened!? Thanks in advance.
EDIT: After a couple hours, I saw my battery start to wig out. It went from being at like 34% to flashing the "low battery" warning. It then turned off and did the exact same thing. I had to go out to use my car charger to get into recovery. I wiped cache/dalvik cach, and re-installed SC. Not sure if it's kernal/ROM/Theme with 3rd party battery supprt...
Voodoo'd Samsung Fascinate
Kernal: 0328_imnuts_sv_voodoo
ROM: Superclean 2.9.2
Theme: Nitro's Ultimate Honeycomb v3.1.2
Recently, I rooted my phone with unrevoked. At random times when turning on my Aria, at the Htc logo screen, my battery will vibrate multiple times before Cyanogen 7 android logo appears. I changed out my battery, unrooted then rooted again only to have this problem. I'm using the lasted Google gapps posted on XDA and don't think it's that. I tried stable and nightly r roms with no change. I believe it's possible that a bug in Unrevoked, Clockwork mod could be at fault. Again, this is at random times when turning on my phone. If anyone knows something are at times experienced this, please post it here.
I don't know what causes it exactly, maybe DT's apps2sd. But I have this too.
gods_archangel said:
Recently, I rooted my phone with unrevoked. At random times when turning on my Aria, at the Htc logo screen, my battery will vibrate multiple times before Cyanogen 7 android logo appears. I changed out my battery, unrooted then rooted again only to have this problem. I'm using the lasted Google gapps posted on XDA and don't think it's that. I tried stable and nightly r roms with no change. I believe it's possible that a bug in Unrevoked, Clockwork mod could be at fault. Again, this is at random times when turning on my phone. If anyone knows something are at times experienced this, please post it here.
Click to expand...
Click to collapse
This is not a problem with Unrevoked or Clockwork. It means the ROM you have installed has something weird going on that causes it to restart a few times before booting normally. This has happened to me also when using CM7, but only after I had installed a different kernel. It never happened to me with the original default kernel, and it's also never happened with any other ROM (CM6 or any of the Sense ROMs).
Just curious, but can you tell us exactly which ROM you're using, and whether you installed a custom kernel on top of it?
drumist said:
This is not a problem with Unrevoked or Clockwork. It means the ROM you have installed has something weird going on that causes it to restart a few times before booting normally. This has happened to me also when using CM7, but only after I had installed a different kernel. It never happened to me with the original default kernel, and it's also never happened with any other ROM (CM6 or any of the Sense ROMs).
Just curious, but can you tell us exactly which ROM you're using, and whether you installed a custom kernel on top of it?
Click to expand...
Click to collapse
I was using RC4, 7.0.3 and trying some of the latest nightly roms. This isn't my first Aria phone that I rooted. My first one didn't have this problem but I forgot which Google gapps version that was used at the time. If it were the gapps, the phone would go in a endless loop at the Cyanogen android boot screen but I'm having this multiple vibrate problem like it keeps rebooting at random on the HTC boot screen when turning on the phone. I changed out my battery for a new one which didn't fix it. At this moment, I unrooted and flashed the original stock rom and no problems are popping up. I believe it's a unknown bug in Clockwork.
gods_archangel said:
I was using RC4, 7.0.3 and trying some of the latest nightly roms. This isn't my first Aria phone that I rooted. My first one didn't have this problem but I forgot which Google gapps version that was used at the time. If it were the gapps, the phone would go in a endless loop at the Cyanogen android boot screen but I'm having this multiple vibrate problem like it keeps rebooting at random on the HTC boot screen when turning on the phone. I changed out my battery for a new one which didn't fix it. At this moment, I unrooted and flashed the original stock rom and no problems are popping up. I believe it's a unknown bug in Clockwork.
Click to expand...
Click to collapse
Well, I suppose it could be. You might want to try formatting boot and system partitions before installing the ROM to see if that clears it up. We already know Clockwork doesn't clear the system partition properly when installing ROMs that use Edify scripts.
here's my problem:
when ever i leave phone to be in deepsleep mode,
i cam back to find it looking for GSM signal with no hope,restarting fixing the signal.
tried diffrent roms, CM7, MIUI,with all kind of kernels nothing works
phone condition is fine,did't drop it or hardware issues on it.
was working great for last 6 months, but after i flashed a ton of diffrent CM roms this starts to happen,
my thoughts:
could it be a NVdat.bin issue doing this?
if so, what i can do to let the phone re build fresh ones,
+ i have old backup of EFS folder.
can you share your thoughts please?
I had the same thing happened to me and my friend's phone in the last week. Both running the ported gingerbread roms. Had to Odin back and finally working. Not sure if it was the Rom or something. My phone says it shows a baseband of UVKB5 which is the correct modem.
Finally flashed back to froyo and had it working, now just reflashed a gingerbread rom and it's working again.
Dattack said:
I had the same thing happened to me and my friend's phone in the last week. Both running the ported gingerbread roms. Had to Odin back and finally working. Not sure if it was the Rom or something. My phone says it shows a baseband of UVKB5 which is the correct modem.
Finally flashed back to froyo and had it working, now just reflashed a gingerbread rom and it's working again.
Click to expand...
Click to collapse
will try this option today and give a feedback.
thank u
Edit:
odining back to JFD solved the problem.
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?
had been trying roms for months now, and 2 weeks ago just starting bootlooping. was running carbon rom when the bootloop started. changed to padawan v2, bootloop went away for a few days and then came back. thought it was power button but when im in cwm it doesnt bootloop.
even all my backups they bootloop. today i went back to stock and using odin and reboots after the att logo.
is my phone done for? thanks
Try an emergency recovery with kies.
fixed it!
i would try it but keeps rebooting. would reboot within 1 minute.
so it turns out it was my radio, even the one in the stock rom would be no good.
i had to flash padawan twice so i would reboot much less frequent, i know why but it worked. then i downloaded a different radio version and seems to be working great. no more reboots after a few days, and i still get 4g on simple mobile.
i dont know how the radio was messing with the reboot but good thing it stopped, was about to give up on my phone.
ufuknut said:
i would try it but keeps rebooting. would reboot within 1 minute.
so it turns out it was my radio, even the one in the stock rom would be no good.
i had to flash padawan twice so i would reboot much less frequent, i know why but it worked. then i downloaded a different radio version and seems to be working great. no more reboots after a few days, and i still get 4g on simple mobile.
i dont know how the radio was messing with the reboot but good thing it stopped, was about to give up on my phone.
Click to expand...
Click to collapse
Hi, I wanted to know what radio version you flashed, because I'm getting the exact same error but none of the radios works for me, I'm also using padawan because of what you said.