Database Users

More boot loops, not like the others

Ive got the following on the HBOOT screen
GLACIER PVT ENG S-OFF
HBOOT=0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Clockwork v3.0.0.6 (using this method http://forum.xda-dev...ad.php?t=944681 )
Okay so with that for reference, I'd like to find out why I can't flash CM7 without the blue Andy bootloop. I understand that a fresh install takes time to load, I gave it 30mins before a battery pull, I then returned the battery, hit the top power button and let that sit for another 20. Before I flashed the ROM (through recovery) I made the following wipes in this order; wipe data/factory reset and then wipe cache partition. I've flashed other ROMs that have flashed without issue (Ice Glacier 1.1.6 themed and Royal MIUI) but, lets face it CM owns. Any help would be appreciated. Thank you for reading this.

DHSdrone said:
Lets face it CM owns.
Click to expand...
Click to collapse
No, Sense owns.
With that out of the way, the only thing I can think of is a corrupt download. Try re-downloading the zip to your PC and copying it to your SD. My other thought was a bad recovery, but since you've successfully flashed other ROMs, that doesn't seem likely.

you didn't wipe dalvik in advanced, do that and bootloop will stop...

darinmc said:
you didn't wipe dalvik in advanced, do that and bootloop will stop...
Click to expand...
Click to collapse
Little known fact, if you wipe data, you already wiped dalvik.

option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Mmmhmm, the only thing it could be is bad download or some other mysterious gremlin lol
Sent from my HTC Glacier using XDA Premium App

option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Well then I retract my statement...

when you say bad or corrupted download I assume your talking about the recovery. I thought the same as well, Ive tried both versions of what was posted as the correct, best, and or easiest method of clockworkmod recovery. Im not sure if both versions were in fact the same recovery.img but they both worked for the roms Ive flashed except for cm (nightly 29, cm7-rc2, rc3,and rc4). The fact tjat I cant get this to work, only makes me want it more.

DHSdrone said:
when you say bad or corrupted download I assume your talking about the recovery.
Click to expand...
Click to collapse
No, I mean the CM7 download. The actual ZIP file that you flash.
As far as recovery versions, only 3.0.0.5 and 3.0.0.6 can flash CM7.

Ive tried flashing several different versions of cm7, starting with rc-2 through rom manager. When that gave me my first boot loop I went back to the method I was more familiar with. With trying the different versions I don't see how they were all currupt or broken downloads. I haven't tried any of the cm froyo roms yet.
As far as my earlier statement of "cm owns" I mean no disrespect of any of the other rom developers (including those that did work properly the first time). Ive just came from the G1 and cm is the only rom I ran. Sense may be the best way to go, it's not something Ive given much consideration or time.

I have had the same issue except mine seems to be all 2.3 (Gingerbread) based roms, they all go to bootloop. I have no problem however flashing any of the 2.2 based roms. I also have cwm 3.0.0.6

I had the same issue everytime with different nightly releases. After wiping everything and formatting boot and system still would do it. I found if you wipe then install cm7 only the phone boots fine then reboot setup wifi if your using it the go back into recovery install gapps and it works fine.
Sent from Teh retardarded duc using XDA Premium App

Im unable to get a full boot. After reading several similar sorties I've always turned off all wireless radios. Will post a logcat later today.

Ok so was able to get mine to Boot completely Finally!!! I am somewhat of anoob so sorry if it seems confusing.
1.From recovery wipe data/ factory
2. Wipe cache
3.Advanced > wipe dalvik
4.Mounts>format boot
5.Mounts>format system
6.Advanced> partion SD card (I believe I used 256) No swap partition(dont know if it matters)
7.Mount USB and transfer cm7 and Gapps
8.Flashed cm7 only not apps.
9.Reboot phone (should boot all the way up)
10.Go back to recovery and flash Gapps
11.Reboot phone
My phone booted up very quickly. I hope this helps anyone else out there with the same issue

no more loop da loops
After searching google, and then to various forums, and finally giving up and posting to 2 separate forums, Ive come to say THANK YOU !!! You are all evil geniuses of the highest degree and I bask in your greatness. Ive been overlooking one thing, that is the "if things go bad, try the sd-card format" well I did and it worked. Now that the derp has left my head, and the panic has subsided I can see now that my problem was in fact like many others, and the answers were right in front of me. Again thanks for being patient and coming together as a community to help me out.

[Q] my defy is dead after installing CM7

after i have installed CM7 it was missing markets so i try to go to recovery menu but not work so i install recovery menu system after that my defy only start at CM7 logo and nothing happened after not working at all helllllllllllllllllllllp?

Think you need to restart.
And remember this time, flash gapps after installing CM for your market to come back

I don't think you're supposed to install any kind of recovery from within CM7 since supposedly there should be one already.
You can always try the SBF flashing route, but don't do that if your battery is low.

glycolysis said:
I don't think you're supposed to install any kind of recovery from within CM7 since supposedly there should be one already.
You can always try the SBF flashing route, but don't do that if your battery is low.
Click to expand...
Click to collapse
He´s right... you´ve damaged your recovery, so there is no other way - you have to start from flashing froyo again.

CM7 has its own boot menu so you are not supposed to install any boot menu or 2nd init after that. If the boot menu is corrupt only option is to start from scratch Froyo SBF.

Read FAQ of CM7. Install CM7>Install Universall pack of Google apps from link on CM7 threat and if it stuck on CM7 logo wipe cache partition and dalvik, don't wipe data and then wait few minutes for build everything. If it stuck still reboot phone on battery. It works for me.

[Q] Defy (MB525) screen all black, unable to boot. Please help!

Hi folks!
I think I've messed up my workphone (Defy MB525) in some wierd way.
I had Cyanogen Mod 10 installed and should only do an update to another nightly, but by mistake I chose a cm7-file instead and flashed it. After that I got stuck in a bootloop, whatever ROM i tried to install or how I did :/
I then tried to reset the phone with an original SBF-file using RSD Lite 5.6. The sbf-file I am using is JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf (found in http://forum.xda-developers.com/showthread.php?t=1828639 first post)
My intention fo flash the sbf-file was to restore the phone to its original state and from that point re-rooting it and after that install cm10 again.
But now to my problem, I just cant to do anything with the phone. The screen is all black and I cannot do anything :/
RSD Lite recognizes the phone and I can flash sbf-files to it. It goes to 100% progress but when it is supposed to boot up after flashing, it takes just a second or so...and RSD Lite then says "Passed" on result leaving me with the black screen yet again.
Only time I can see something on the screen is during the flashing. The sceen says "SW update In progress...". Other then that, always black:crying:
Really really stuck here and dont know what to do. If anyone has an idea and the time to help me, I would be in ever grateful!
Best regards,
/marmeladov

http://www.mediafire.com/?muqlua3xu36gcdr
http://www.mediafire.com/?6ecarbv4gxspdx5
Download that, unrar it to a folder
Flash Firmware 1, let the phone boot up and done.
If you want ROOT, enter to Motorola Recovery (Volume up + power, when the Android appears press Volume up + Volume down) then factory reset and wipe data, reboot phone on BL mode (Volume down + power) and flash Firmware 2.

Feche said:
http://www.mediafire.com/?muqlua3xu36gcdr
http://www.mediafire.com/?6ecarbv4gxspdx5
Download that, unrar it to a folder
Flash Firmware 1, let the phone boot up and done.
If you want ROOT, enter to Motorola Recovery (Volume up + power, when the Android appears press Volume up + Volume down) then factory reset and wipe data, reboot phone on BL mode (Volume down + power) and flash Firmware 2.
Click to expand...
Click to collapse
Thanks a ton for helping me in desperate times
I managed to get the phone working again using your files and this link http://forum.xda-developers.com/showthread.php?t=1216982
Then I got the problem with 128mb internal memory, but solved it.
Now I have cm9 up and running with no issues. I tried Epsylons CM10 from http://forum.xda-developers.com/showthread.php?t=1768702 but it lagged and were really really slow for some reaseon :/

Epsylon builds are outdated, you should try Quarx CM10 or CM10.1

Feche said:
Epsylon builds are outdated, you should try Quarx CM10 or CM10.1
Click to expand...
Click to collapse
Thanks, had some issues installing Quarx CM10. Never managed to get it up and running, might've been a kernel issue or something. The led just turns RED :/
On my Google Nexus CM10 was more smooth then 10.1, so I figured I'd better try CM10 on the defy due to weaker hardware. But I might have wrong there since I havent tried.

Did you wipe cache?

Feche said:
Did you wipe cache?
Click to expand...
Click to collapse
Yep, I wiped factory, cache and dalvik. But still chrashed. Will try again today though. Can report back and see if I get better luck
Thanks a ton for trying to help me btw, highly appretiated!

marmeladov said:
Yep, I wiped factory, cache and dalvik. But still chrashed. Will try again today though. Can report back and see if I get better luck
Thanks a ton for trying to help me btw, highly appretiated!
Click to expand...
Click to collapse
Make sure that you are using latest Quarx build (http://quarx2k.ru/cm10.1-nightly-defy+/2.6.32/cm-10.1-20130415-NIGHTLY-mb526.zip)
What OS are you using right now? no problem mate

That is the file I've tried but for some reason I just cant get passed the red motorola-logo. the phone gets stuck in a bootloop like this; Red Motorola-Logo, LED turns green...Red Motorola-logo...and then it loops like that. Dont know what to do :/
I use Win 7 x64.

marmeladov said:
That is the file I've tried but for some reason I just cant get passed the red motorola-logo. the phone gets stuck in a bootloop like this; Red Motorola-Logo, LED turns green...Red Motorola-logo...and then it loops like that. Dont know what to do :/
I use Win 7 x64.
Click to expand...
Click to collapse
Do this:
Enter recovery
Wipe cache, data and dalvik
Install Quarx CM10 (http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/CM10-20130409-NIGHTLY-mb526.zip)
Install 4.1.2 gApps (http://goo.im/gapps/gapps-jb-20121011-signed.zip)
Reboot and let it boot up.
Once you are with CM10, do this:
Enter recovery
Wipe cache, data and dalvik
Install Quarx CM10.1 (http://quarx2k.ru/cm10.1-nightly-defy+/2.6.32/cm-10.1-20130415-NIGHTLY-mb526.zip)
Install 4.2.2 gApps (http://goo.im/gapps/gapps-jb-20130301-signed.zip)
Reboot
Good luck

Feche said:
Do this:
Enter recovery
Wipe cache, data and dalvik
Install Quarx CM10 (http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/CM10-20130409-NIGHTLY-mb526.zip)
Install 4.1.2 gApps (http://goo.im/gapps/gapps-jb-20121011-signed.zip)
Reboot and let it boot up.
Once you are with CM10, do this:
Enter recovery
Wipe cache, data and dalvik
Install Quarx CM10.1 (http://quarx2k.ru/cm10.1-nightly-defy+/2.6.32/cm-10.1-20130415-NIGHTLY-mb526.zip)
Install 4.2.2 gApps (http://goo.im/gapps/gapps-jb-20130301-signed.zip)
Reboot
Good luck
Click to expand...
Click to collapse
I think I give up. Dont understand what I am doing wrong. Have rooted and installed custom roms on htc hero, htc sensation xe, htc wildfire, galaxy nexus..but this phone. Neever had even close to the issues I'm having with this one :/
I followd your steps on installing cm10. But when both the rom and gapps are installed and I reboot it reboot the following happends; red motorola-log, blue led - red led. And bootloop. Nothing else :/
Read somewhere that I have to install a kernel separately, is that true?

marmeladov said:
I think I give up. Dont understand what I am doing wrong. Have rooted and installed custom roms on htc hero, htc sensation xe, htc wildfire, galaxy nexus..but this phone. Neever had even close to the issues I'm having with this one :/
I followd your steps on installing cm10. But when both the rom and gapps are installed and I reboot it reboot the following happends; red motorola-log, blue led - red led. And bootloop. Nothing else :/
Read somewhere that I have to install a kernel separately, is that true?
Click to expand...
Click to collapse
Nope, the kernel is on the .zip
Are you sure that you wiped data and cache?

Feche said:
Nope, the kernel is on the .zip
Are you sure that you wiped data and cache?
Click to expand...
Click to collapse
It is advised to wipe cache and Dalvic cache after installing zip files.
Moreover, when I installed full Gapps I got system partition full, so instead I installed minimal Gapps:
http://forum.xda-developers.com/showthread.php?p=34616788
Green lens Defy

I simply dont know if I'm doing something wrong (think not) or if my phone is messed up. But I get the same result after following your guides several times. I cant get passed the motorola-logo after flashing cm10. The Led turns red (indicating somethings wrong?) and then reboots again. Keeps going adn going :/

[Q] PAC-man on Nexus 4 stuck in bootloop! What do I do?

Hi. My Nexus 4 got stuck in a bootloop while attempting to flash the PAC-man ROM and I have no idea what to do!
I am a total noob at this, so I'll just go through the details. I cleaned Dalvik and Cache and then flashed the files: pac_mako-22.2.0-rc1(Downloaded from official PAC-ROM site) and gappsinverted-jb-20130308-signed(From rootzwiki). After flashing these two, I tried starting the phone. The minigame turned up and then it moved on to the 'PAC is LOADING' screen. It stayed like that for 15 minutes... The only way I knew the phone hadn't hung was because there was the constant movement of the loading bar. So I got into TWRP recovery again and flashed Paranoid Android back so the device would be usable again.
I really want to try PAC-man and would be grateful to anyone who can help me out...

noobvorld said:
Hi. My Nexus 4 got stuck in a bootloop while attempting to flash the PAC-man ROM and I have no idea what to do!
I am a total noob at this, so I'll just go through the details. I cleaned Dalvik and Cache and then flashed the files: pac_mako-22.2.0-rc1(Downloaded from official PAC-ROM site) and gappsinverted-jb-20130308-signed(From rootzwiki). After flashing these two, I tried starting the phone. The minigame turned up and then it moved on to the 'PAC is LOADING' screen. It stayed like that for 15 minutes... The only way I knew the phone hadn't hung was because there was the constant movement of the loading bar. So I got into TWRP recovery again and flashed Paranoid Android back so the device would be usable again.
I really want to try PAC-man and would be grateful to anyone who can help me out...
Click to expand...
Click to collapse
You have to also wipe DATA when you flash a new ROM. Use the factory reset option.

also, your gapps are out of date. you got stuck at rebuilding the dalvik, which is kinda normal for android 4.3. all you have to do, should have to do, is force reboot once or twice until the dalvik gets rebuilt, then itll boot.

simms22 said:
also, your gapps are out of date. you got stuck at rebuilding the dalvik, which is kinda normal for android 4.3. all you have to do, should have to do, is force reboot once or twice until the dalvik gets rebuilt, then itll boot.
Click to expand...
Click to collapse
Sorry, but I don't know what you mean by 'force reboot'. Could you walk me through the steps please? Thanks!

noobvorld said:
Sorry, but I don't know what you mean by 'force reboot'. Could you walk me through the steps please? Thanks!
Click to expand...
Click to collapse
Hold the power button for about 10 seconds.

You are trying to use 4.2.2 gapps on 4.3 rom

[Q] Google screen hangtime

I apologize if there is a thread for this but if it exists, I cant find it.
My nexus 4 lags for 5 minutes on Google screen, THEN still boots. I also have no wifi... Even after reflashing boot img, and doing a full wipe
I recently messed up my CWM recovery, and was stuck on stock. I was able to fix it, reflashed CWM using abd and fastboot, everything was successful. Ever since, when my phone loads, it stays on the Google screen for 5 minutes, before it ever starts the rom bootup. This is not just a specific rom, its even happening on stock ROM. My phone does boot, so this is just a OCD fix now, but a 7-10 minute boot for my phone... is kinda crazy. Does anyone have a solution?

xtjx09 said:
I apologize if there is a thread for this but if it exists, I cant find it.
My nexus 4 lags for 5 minutes on Google screen, THEN still boots.
I recently messed up my CWM recovery, and was stuck on stock. I was able to fix it, reflashed CWM using abd and fastboot, everything was successful. Ever since, when my phone loads, it stays on the Google screen for 5 minutes, before it ever starts the rom bootup. This is not just a specific rom, its even happening on stock ROM. My phone does boot, so this is just a OCD fix now, but a 7-10 minute boot for my phone... is kinda crazy. Does anyone have a solution?
Click to expand...
Click to collapse
Try dirty flashing (only wipe cache and dalvik cache) your exact ROM.

abaaaabbbb63 said:
Try dirty flashing (only wipe cache and dalvik cache) your exact ROM.
Click to expand...
Click to collapse
I will try but I dont think its gonna fix it... worth a shot. But I also found out I have no sound... I'm kinda getting worried here.