Database Users

2.3 OTA bricked my phone.

I have been running on stock 2.2 for a week or so now (SBF'd and was running with no issues)...not rooted or modified in any way. I did the OTA update for 2.3 and now my phone boots to the droid boot animation, and hangs. The boot animation completely freezes up, and the phone is unresponsive. Tried SBFing the 2.3 over and according to RSD that was completed successfully...but got the same thing on startup.
I got my phone the week it came out and have SBF'd many times, had rooted, ran all sorts of roms (as long as your counting different versions)...and of all things...an OTA update bricked it. Awesome.
I'll be heading to my local Verizon store in a few hours. Just thought I'd let you guys know.

That sucks Let us know how it goes at the store
With all the bootloader lockdown crap motorola put on these phones its just a matter of time before their own updates cause problems... anything strong enough to keep out hackers is also strong enough to cause serious problems when legit updates mess up...

Boot into stock recovery (power and hold X, then press the search key at the ! In the triangle)
Wipe data and cache
Reboot

karnovaran said:
Boot into stock recovery (power and hold X, then press the search key at the ! In the triangle)
Wipe data and cache
Reboot
Click to expand...
Click to collapse
^+1 this. Quite often when restoring the phone via an SBF it results in a bootloop which is corrected by performing a cache and data wipe through the stock recovery on the phone. It seems this can happen because the SBF doesn't actually wipe or replace /data and /cache

Another WIN for karnovaran!
karnovaran said:
Boot into stock recovery (power and hold X, then press the search key at the ! In the triangle)
Wipe data and cache
Reboot
Click to expand...
Click to collapse
Wow. Thanks! Worked like a charm.
Anybody that might have my same issue after installing the OTA, follow above steps, and wipe data in the stock recovery. My phone booted right up afterwards.
Thanks guy!

scsione889 said:
Wow. Thanks! Worked like a charm.
Anybody that might have my same issue after installing the OTA, follow above steps, and wipe data in the stock recovery. My phone booted right up afterwards.
Thanks guy!
Click to expand...
Click to collapse
Can I close this???

Cyanogem Mod - stuck on boot screen

Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.

Do you have a custom recovery like Amon_RA or ClockWorkMod installed?

cyrus_mc said:
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Click to expand...
Click to collapse
You'll be fine pulling the battery since you're only flashing a ROM... it's a NO NO when flashing Radio though. That being said... the CORRECT way to restart when you're in a bootloop or stuck on that particular screen is to use the three finger salute and reboot by holding down the power button, volume down button, and pressing the trackball. From there, I'd immediately hold down the volume down button, which will force the phone into the bootloader and you can enter Recovery from there. Do a FULL wipe of data and cache, as well as dalvik-cache from the Advanced menu, then flash the ROM.

uansari1 said:
You'll be fine pulling the battery since you're only flashing a ROM... it's a NO NO when flashing Radio though. That being said... the CORRECT way to restart when you're in a bootloop or stuck on that particular screen is to use the three finger salute and reboot by holding down the power button, volume down button, and pressing the trackball. From there, I'd immediately hold down the volume down button, which will force the phone into the bootloader and you can enter Recovery from there. Do a FULL wipe of data and cache, as well as dalvik-cache from the Advanced menu, then flash the ROM.
Click to expand...
Click to collapse
Yup this is what to do. Quick bit of info; You can get to the boot loader by simply holding the volume button down and pressing the power button, just a little easier to do

That's what I had to do. Mine also got stuck.
Sent from my Nexus One using XDA App

Hollow.Droid said:
Yup this is what to do. Quick bit of info; You can get to the boot loader by simply holding the volume button down and pressing the power button, just a little easier to do
Click to expand...
Click to collapse
Agreed. I was just referring to what to do if you're stuck on the X or in a boot loop. ;-)
Sent from my Nexus One using Tapatalk

You're stuck with stock recovery. Reboot back to ROM, install recovery, only then reboot to install ROM.

Hey guys I'm having a similar problem, however my phone gets stuck on the initial nexus screen. I've been working on the phone problem for the better half of the day and this is what i've done, what works, and what doesn't.
WHAT I'VE DONE:
Full wipe, including Devik
Played around with installing different radios.
Download CM7-RC1 from CWM and the computer
WHAT WORKS:
MIUI Roms
Stock Gingerbread Rom
MY Back-up, which has CM7 Nightlie #45
WHAT DOESN'T:
All Cyanogen Mods
I even tried the CM6.0
So I'm a little stump on how to get my phone to run the latest Cyanogen or matter of fact, any CM Roms. Maybe my phone wants something different in her life
Any help will be great guys...thx

How much time did you wait?
Did you try erasing /system?

Well I just waited for 5 hours leaving it on the initial Nexus screen, in hopes it might do something, but it was to no success.
/system? not quite sure where that is... I am assuming it's in the roots... I can only do what I can from the recovery.

Try to install LeoGingerbread, for example. Does it work?
If yes - right after it installs, try to flash CM7.

cyrus_mc said:
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Click to expand...
Click to collapse
Whenever you see "little green Android Logo and Exclamation", you can press volume up and power button together to get into the bootloader menu and reboot your N1. It seems like your custom recovery did not work. Try to flash Clockworkmod recovery 2.5.1.4 (not 3.0.0.5) or RA recovery again. It may help.

Jack_R1 said:
Try to install LeoGingerbread, for example. Does it work?
If yes - right after it installs, try to flash CM7.
Click to expand...
Click to collapse
Wow that actually worked, thanks... can you explain why this is needs to be done to get it to work?

LeoGingerbread executes "format /system", that actually works and cleans the remains of the old OSes. Some other ROMs do, too.

armyshawkeye said:
Wow that actually worked, thanks... can you explain why this is needs to be done to get it to work?
Click to expand...
Click to collapse
Because you still have the stock recovery installed, that is how you access the menu for it.

Here's a flashable script that does the same thing. It was put together by temasek - I'm just sharing...
http://db.tt/wdeoIMI
Sent from my Nexus One using XDA App

danger-rat said:
Here's a flashable script that does the same thing. It was put together by temasek - I'm just sharing...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
How I flash this? As a update.zip?

Yes. I believe it executes "FORMAT SYSTEM:" command, maybe more than once.

Yes, it formats system, boot, data, and cache, each twice...
It's quicker than flashing a full ROM to achieve the same results...
Sent from my Nexus One using XDA App

danger-rat said:
Yes, it formats system, boot, data, and cache, each twice...
It's quicker than flashing a full ROM to achieve the same results...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
CW Recovery has options to format system, and other partitions, under Mounts and Storage.
Sent from my Nexus One using Tapatalk

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic

syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App

Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??

Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App

OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App

syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!

syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.

last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.

You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???

Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.

lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.

Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.

lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!

And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?

syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App

OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!

Stuck in Android boot

need help! urgent! i was using cm 7.2 lastest maniacs and then made a wipe data because i wanted to go back to froyo, but when i restared the phone cm7 was still there so i decided to flash .sbf the nordic one (the one that i installed when i changed from Android 2.1 to Android 2.2) .. it started good but when it shows "Please Manually Power Up This Phone" Excecuted 100% In Process, the defy screen is just looping in Android boot, it shows the motorola logo then the android boot but it get stuck in there, i removed battery and change it but did not work and the phone just get stuck in Android boot. what can i do?

you must go to stock recovery and clear wipe data chace and you will be ok

nikolas60 said:
you must go to stock recovery and clear wipe data chace and you will be ok
Click to expand...
Click to collapse
But how to do it if the 2nd init isn't installed???
Sent from my MB525 using XDA

Try one new
You should try to flash a diferent sbf... a stock one, look here http://forum.xda-developers.com/showthread.php?t=966537

carlosmebratt said:
You should try to flash a diferent sbf... a stock one, look here http://forum.xda-developers.com/showthread.php?t=966537
Click to expand...
Click to collapse
Thanks men... but i got an answer that helped me out from twa_priv
"You need to wipe in Stock (Motorola) recovery, which is always there.
Shutdown the phone and then:
power + vol down
then push volume up and down at the same time"
at first there is just an android with a triangle but then you should do the vol up and down at the same time and there will be a stock motorola recovery!
thanks for everyone that helped me out with this stuff!

[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 :/