Bricked? - Nook Color General

I tried to flash MIUI from TWRP recovery and it reboots right back to recovery. I used cwm from the sdcard, flashed there and when I take it out it reboots back to TWRP. I tried to flash other roms but they all failed both ways. Help? Please?
Sent from my DROID2

odj1041 said:
I tried to flash MIUI from TWRP recovery and it reboots right back to recovery. I used cwm from the sdcard, flashed there and when I take it out it reboots back to TWRP. I tried to flash other roms but they all failed both ways. Help? Please?
Sent from my DROID2
Click to expand...
Click to collapse
You may be in a recovery bootloop. Look at my tips thread linked in my signature to see what that is and some possible ways to get out of it.

leapinlar said:
You may be in a recovery bootloop. Look at my tips thread linked in my signature to see what that is and some possible ways to get out of it.
Click to expand...
Click to collapse
Worked perfectly after I used your CWM 5.5.0.4. Thank you so much. I and I bet a whole bunch of other Nook Color users that had issues with it, appreciate your help.

Related

Can't boot into recovery!

I just rooted my Nexus 1 Froyo per instructions on theUnlockr.com. I installed ADB first, Then proceded to root. I then flashed a recovery rom: recovery-RA-nexus-v1.7.0.1-cyan.img. This was successful. I then booted phone into recovery mode. Selected recovery and the first couple times I received a black screen with an exclamation point in the middle of a triangle next to green android. I flashed recovery rom once again and this time it allowed me to enter. I made my backup image and even booted into recovery mode again�wiped phone clean and restored image. I thought I was golden! Later I tried to boot into recovery mode again and I received same problem as mentioned above. I tried again no luck. I even flashed recovery rom again and It still dose not work. Why could this be happening? I even went through the steps to root phone again (that went well). But still no recovery mode. I even tried another recovery rom: recovery-RA-nexus-v1.7.0.1.img. It did the same thing. Worked one time and then nothing! I need to fix this before I load custom Roms.
Sent from my Nexus One using XDA App
follow this guide
http://forum.xda-developers.com/showthread.php?t=636795
Amritttt said:
follow this guide
http://forum.xda-developers.com/showthread.php?t=636795
Click to expand...
Click to collapse
I was able to flash recovery via your instructions but phone STILL will not boot into recovery mode. I hold down the volume key and power.....all I get is triangle with droid net to it. Im going to try and Un-root my phone and start from scratch! Thanks for the help!
you are getting the triangle with the droid because the recovery did not flash correctly, try usung rom manager if for nothing else, just to install Amon/clockwork
Poseidon20 said:
I was able to flash recovery via your instructions but phone STILL will not boot into recovery mode. I hold down the volume key and power.....all I get is triangle with droid net to it. Im going to try and Un-root my phone and start from scratch! Thanks for the help!
Click to expand...
Click to collapse
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
you are getting the triangle with the droid because the recovery did not flash correctly, try usung rom manager if for nothing else, just to install Amon/clockwork
Cool thanks for the advice! I did try Rom Manager and used Amon/Clockwork recovery. After flashing the Recovery Image I booted into recovery from Rom Manger. No problem! BUT.....when I rebooted phone from recovery menu I again went in to Rom Manager and tried to Boot back in to recovery and I got the triangle with the Droid next to it. I pulled battery and started phone again. I flashed Amon/Clockwork recovery again from Rom Mang. and again I was able to successfully boot in to recovery. This pattern goes on and on. It seams that every-time I want to boot into recovery I need to flash Amon/clockwork image. Somewhere phone is not retaining the information. Everything looks to work just fine as long as I Flash before I go into recovery. I'm sure this is not the way it should work. Any ideas?
khaytsus said:
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
Click to expand...
Click to collapse
Khaytsus,
When was I told to remove the two scripts? Where did this come from? Please let me know what they are for and why removing them would help? Also, if I do need to remove these would it be done by using Root File Manager, finding file and selecting delete? Sorry if I sound new to this.....it's because I am! LOL. Thanks for any help you can provide!
Try this.
http://forum.xda-developers.com/showpost.php?p=7378018&postcount=47
Poseidon20 said:
Khaytsus,
When was I told to remove the two scripts? Where did this come from? Please let me know what they are for and why removing them would help? Also, if I do need to remove these would it be done by using Root File Manager, finding file and selecting delete? Sorry if I sound new to this.....it's because I am! LOL. Thanks for any help you can provide!
Click to expand...
Click to collapse
It's documented in random places, of course the post below also has the same info. I don't know precisely what the two files do, but they apparently try to restore the recovery.
Trust me, it will fix the problem. Remove them, re-flash recovery.
khaytsus said:
It's documented in random places, of course the post below also has the same info. I don't know precisely what the two files do, but they apparently try to restore the recovery.
Trust me, it will fix the problem. Remove them, re-flash recovery.
Click to expand...
Click to collapse
Khaytsus,
You saved my Droid! You were right! deleting those 2 files worked. I'm well into flashing Custom ROMs. Your the only one who got it right! Good job! Thanks Again!
khaytsus said:
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
Click to expand...
Click to collapse
So, I'm not the OP, but I am having trouble deleting the files despite the fact that they are both say "YES" in read and write in properties. I tried to reflash from ROM Manager and I keep getting an error there. Not sure what to do.
BTW, I'm using a Galaxy Nexus. Would love some help as this is all uncharted terrain for me.
sadako12 said:
BTW, I'm using a Galaxy Nexus. Would love some help as this is all uncharted terrain for me.
Click to expand...
Click to collapse
You are in Nexus One Q&A Forum. Did you tryed with Galaxy Nexus Recoveries files and guides ?
ldFxl said:
You are in Nexus One Q&A Forum. Did you tryed with Galaxy Nexus Recoveries files and guides ?
Click to expand...
Click to collapse
I tried pretty much everything other than wiping the whole thing again. It's quite unfortunate.
sadako12 said:
I tried pretty much everything other than wiping the whole thing again. It's quite unfortunate.
Click to expand...
Click to collapse
If I understand, your problem is that you can't actually flash a custom recovery from ROM Manager ?
Which do you use ?
Are you trying to flash a recovery in recovery mode ?
Please link here files you tried to flash.
ldFxl said:
If I understand, your problem is that you can't actually flash a custom recovery from ROM Manager ?
Which do you use ?
Are you trying to flash a recovery in recovery mode ?
Please link here files you tried to flash.
Click to expand...
Click to collapse
I can't flash from ROM Manager. Initially, I didn't want to purchase the download capability. So, first, I used the program tools and flashed from there. I got Clockwork Mod to work, but then when I restarted it and went into "recovery," I got nothing.
Now, I can't flash at all.
The galaxy nexus should have fastboot capabilities, this is the best and safest way to flash your recovery partition
Be sure to use the proper recovery image for your device
If you need help finding it or setting up fastboot let me know
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
The galaxy nexus should have fastboot capabilities, this is the best and safest way to flash your recovery partition
Be sure to use the proper recovery image for your device
If you need help finding it or setting up fastboot let me know
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have only ever found a guide for a temporary flash. I would follow the instructions and then CWM wouldn't stick. =\
So here is the typical steps to follow
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
And that's it, were you using fastboot to just boot it? Were you doing another method? The more details you give the faster and more accurate your help will be
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So here is the typical steps to follow
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
And that's it, were you using fastboot to just boot it? Were you doing another method? The more details you give the faster and more accurate your help will be
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used instructions from http://androidforums.com/internatio...root-samsung-galaxy-nexus.html#enter-recovery.
The ROM wouldn't "stick" and then the USB wasn't even recognized by the end of everything.
Start by booting into your bootloader and writing down everything word for word on that screen here. Next boot to recovery and write down what you see there. Even better upload pics of each. Again the more detailed you can be the more help you can get
Sent from my Nexus 7 using XDA Premium 4 mobile app

[Q] Stuck in Clockwork Recovery

I was trying to flash a new kernel, and so i wiped the 2 caches and now im stuck on the Clockwork Recovery Screen. I try rebooting, and all it does is just go back to the Recovery screen. Please help, i want to use my nook color again.
Do you have previously created backup on your SD card ?
If so just restore.
Unfortunatly, i didnt. I just got it a couple days ago and am brand new to all these mods.
me too
This just happened to me as well. I even had a backup image and restored, but it would still loop. I used the following zip which removes clockwork recovery (thanks to the OP that originally posted this) and it then it worked.
Give it a shot
OMG, I LOVE YOU! No really, thank you so much!!! It works perfect!
Your welcome...........
Solidsnake726 said:
OMG, I LOVE YOU! No really, thank you so much!!! It works perfect!
Click to expand...
Click to collapse
I think this is beginning of beautiful relationship
Some additional info that may be relevant or not...
Some users have reported that after clearing the dalvik cache in CWR (as part of the process to flash a custom kernel), the screen locks up and they are unable to return to the main recovery screen.
This was resolved by 1) hook up your nook to the wall charger, 2) hold the power button which will force a reboot, 3) after your nook reboots to its normal screen, restart the kernel flash procedure from the beginning, 4) after you clear the dalvik cache, do not touch anything for at least 30 seconds
After step 4, CWR usually doesn't lock up and you should be able to navigate back to the main recovery screen to finish the kernel flash process. For some reason or another, the nook just needs a little time after clearing the dalvik cache before you can press any buttons.
yan2000kee said:
This just happened to me as well. I even had a backup image and restored, but it would still loop. I used the following zip which removes clockwork recovery (thanks to the OP that originally posted this) and it then it worked.
Give it a shot
Click to expand...
Click to collapse
I have had the same issue as the OP using ROM Manager to install 3.0.0.5 on 1.1.0 using Auto-Nooter 3.0.0. I was able to use the quoted method to break out (for the record I did so before reading this post ). However, I ran into the problem again after a full reroot and am still looking for a permanent solution to the problem.
yan2000kee said:
This just happened to me as well. I even had a backup image and restored, but it would still loop. I used the following zip which removes clockwork recovery (thanks to the OP that originally posted this) and it then it worked.
Give it a shot
Click to expand...
Click to collapse
Sorry for being a noob but what do I do with this file? Just put it on root and run it in CWR?
Moorfrost said:
Sorry for being a noob but what do I do with this file? Just put it on root and run it in CWR?
Click to expand...
Click to collapse
Yes. Boot into CWR and select the zip file from the SD card and flash.
eyecrispy said:
Yes. Boot into CWR and select the zip file from the SD card and flash.
Click to expand...
Click to collapse
Thanx a million, worked like a charm.
Thanks... But one other question...
Thanks for this got me out of the CWR bootloop, but now I'm stuck on the android splash screen.
UPDATE: Just tried to start all over and now it got me a bit further, but to a black screen with a white banner up top that says "Android System"...
Another noob question, sorry. Will this also restore the stock BN recovery? Regardless, thanks.
lekofraggle said:
Another noob question, sorry. Will this also restore the stock BN recovery? Regardless, thanks.
Click to expand...
Click to collapse
yes it does , just did it my self
Lifesaver! Thanks!
Maybe this should be linked to original thread.. So that things are made clear..
Sent from my HTC Desire using XDA App
Sorry to bump this thread, but OP's issue of being stuck in CWR happens to me every time I try to install the overclock kernel on my Eclair nook.
Any advice on what I can do to successfully overclock?
Anoxymoron said:
Sorry to bump this thread, but OP's issue of being stuck in CWR happens to me every time I try to install the overclock kernel on my Eclair nook.
Any advice on what I can do to successfully overclock?
Click to expand...
Click to collapse
I found a work around. Open cwr..flash recovery, exit recovery, reboot from quick boot . Once rebooted go back to cwr flash recovery, reboot into recovery, clear cache flash zip..reboot. This has worked numerous times for me.
bratliff said:
I found a work around. Open cwr..flash recovery, exit recovery, reboot from quick boot . Once rebooted go back to cwr flash recovery, reboot into recovery, clear cache flash zip..reboot. This has worked numerous times for me.
Click to expand...
Click to collapse
This is assuming that CWR is on internal memory.. if you are booting CWR from SD.. you need to take out the SD card then boot up.

Stock firmware problem after Cyanogenmod

A friend of mine suggested that I try Cyanogenmod, so I decided to flash my Galaxy Mini. The first problem was the bootloop, and no matter how many times I wiped the phone, it was always stuck at the Android text. So I decided to try the Honeycomb mod. Same happened. So I decided to flash it with Android 2.3.6 from sammobile.com. At last, it started working. However, Google Play still sees every application as "installed" (but of course they aren't), and when I try to delete from GP, nothing happens. After trying to install other applications, I realized that I cannot install anything from the market. Any idea how I could solve this problem? I would be very grateful.
did you flash your costom rom trough clockworld mod recovery (CMW)???
lackhoo said:
did you flash your costom rom trough clockworld mod recovery (CMW)???
Click to expand...
Click to collapse
He can't flash it by an another way
Sent from my GT-I9400 using XDA Premium
lackhoo said:
did you flash your costom rom trough clockworld mod recovery (CMW)???
Click to expand...
Click to collapse
Yes I did. I used CWM 5.0.2.6. The funny part is that after being turned off 3 times, Google Play started working But if there's a solution to the bootloop problem I would love to hear it. I searched this forum and the internet and nothing, even though I followed a cyanogenmod wiki's guide.
did you wipe two times before and after flashing cyanogenmod rom
How old is your sd card? because same happened to me. I needed to format my sd card.
Rekesz said:
Yes I did. I used CWM 5.0.2.6. The funny part is that after being turned off 3 times, Google Play started working But if there's a solution to the bootloop problem I would love to hear it. I searched this forum and the internet and nothing, even though I followed a cyanogenmod wiki's guide.
Click to expand...
Click to collapse
Thanked accidentally.
Anyway, tour problem is the CWM you used, didnt u see the DONT USE sign in the version 5.0.2.6 thread? 5.0.2.8 would avoided those errors in flashing custom ROMs
Sent from my GT-S5570 using xda premium
My SD card is as old as my phone, about 9 months old.
No, I didn't see the sign, and to be honest, I didn't even know that there was a 5.0.2.8 version. Do you think it would work with that?
try flash cm7 trough this recovery---->forum.xda-developers.com/showthread.php?t=1342190 i think this in the best cmw........
Rekesz said:
My SD card is as old as my phone, about 9 months old.
No, I didn't see the sign, and to be honest, I didn't even know that there was a 5.0.2.8 version. Do you think it would work with that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1529863 there it is.
I'm sure it works. 5.0.2.6 had some issues as said in the thread, but 5.0.2.8 or 4.0.0.5 works fine. Try it
PM me anything GT-S5570
So I downloaded the new recovery, flashed it via Odin, and now nothing works. When I enter recovery it says that it can't mount /cache/log and /cache/recovery (I think it says these two). I looked around and found that it could be stuck in a bootloop, but luckily Android loads. However, I can't root my phone due to several errors, so I can't install Cyanogen mod. I think I'll give up now But thanks for all the help!
Rekesz said:
So I downloaded the new recovery, flashed it via Odin, and now nothing works. When I enter recovery it says that it can't mount /cache/log and /cache/recovery (I think it says these two). I looked around and found that it could be stuck in a bootloop, but luckily Android loads. However, I can't root my phone due to several errors, so I can't install Cyanogen mod. I think I'll give up now But thanks for all the help!
Click to expand...
Click to collapse
This happens because you are in stock ROM, this errors are normal.If you want ONLY to root your phone you should use stock recovery. Otherwise you can proceed.
PM me anything. GT-S5570
Trublood_ said:
This happens because you are in stock ROM, this errors are normal.If you want ONLY to root your phone you should use stock recovery. Otherwise you can proceed.
PM me anything. GT-S5570
Click to expand...
Click to collapse
Okay. So I flashed the stock ROM back so I can use the stock recovery. Phone rooted-->still getting the same error :/ Sorry for bothering you all so many times, but I just can't understand why this does not work.
Rekesz said:
Okay. So I flashed the stock ROM back so I can use the stock recovery. Phone rooted-->still getting the same error :/ Sorry for bothering you all so many times, but I just can't understand why this does not work.
Click to expand...
Click to collapse
We are here to help you
What error? That one on CWM recovery
PM me anything. GT-S5570
Trublood_ said:
We are here to help you
What error? That one on CWM recovery
PM me anything. GT-S5570
Click to expand...
Click to collapse
Thanks very much Here is what I did step by step:
I returned to the stock recovery by installing the stock firmware. I rooted the phone with stock recovery. Then I installed CWM recovery 5.2.0.8, but I still get the same error in CWM: it can't mount a few things. I still tried installing Cyanogen without wiping, and of course it's stuck at the boot screen with the Android text (I had a feeling that it wouldn't work if the recovery is not fully operational, so I did not want to lose every contact for nothing again). I read that this problem can be solved by formatting the SDCard, so I tried formatting it with PC and the phone also, but nothing. So now I'm back to the stock firmware and recovery with my phone rooted and no idea how to solve any of the problems.
Rekesz said:
Thanks very much Here is what I did step by step:
I returned to the stock recovery by installing the stock firmware. I rooted the phone with stock recovery. Then I installed CWM recovery 5.2.0.8, but I still get the same error in CWM: it can't mount a few things. I still tried installing Cyanogen without wiping, and of course it's stuck at the boot screen with the Android text (I had a feeling that it wouldn't work if the recovery is not fully operational, so I did not want to lose every contact for nothing again). I read that this problem can be solved by formatting the SDCard, so I tried formatting it with PC and the phone also, but nothing. So now I'm back to the stock firmware and recovery with my phone rooted and no idea how to solve any of the problems.
Click to expand...
Click to collapse
Flasging CyanogenMod without wipes? Seriously? Thats exactly why it never worked!! CWM cant mount somethings because you were in stock ROM
Use some backup program to backup contacts, apps, whatever and flash cyanogenmod wiping data and cache before and after.
Sent from my GT-S5570 using xda premium
Rekesz said:
A friend of mine suggested that I try Cyanogenmod, so I decided to flash my Galaxy Mini. The first problem was the bootloop, and no matter how many times I wiped the phone, it was always stuck at the Android text. So I decided to try the Honeycomb mod. Same happened. So I decided to flash it with Android 2.3.6 from sammobile.com. At last, it started working. However, Google Play still sees every application as "installed" (but of course they aren't), and when I try to delete from GP, nothing happens. After trying to install other applications, I realized that I cannot install anything from the market. Any idea how I could solve this problem? I would be very grateful.
Click to expand...
Click to collapse
You Should get gapps for it or you should download .apk for any site........:good:
Thanks Button Ready For You.....:good:
Trublood_ said:
Flasging CyanogenMod without wipes? Seriously? Thats exactly why it never worked!! CWM cant mount somethings because you were in stock ROM
Use some backup program to backup contacts, apps, whatever and flash cyanogenmod wiping data and cache before and after.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
This was just a trial run due to the new CWM recovery. If you read back, I already wrote that I tried wiping both data and cache before and after flashing Cyanogen mod. This "mounting" problem only came up with the new CWM recovery, 5.2.0.8.
The basic Google Apps were all there, since I used a rom from sammobile.com, downloaded programs like poweramp were the ones that did not work.
Rekesz said:
This was just a trial run due to the new CWM recovery. If you read back, I already wrote that I tried wiping both data and cache before and after flashing Cyanogen mod. This "mounting" problem only came up with the new CWM recovery, 5.2.0.8.
The basic Google Apps were all there, since I used a rom from sammobile.com, downloaded programs like poweramp were the ones that did not work.
Click to expand...
Click to collapse
And you tried wipes using 5.2.0.8 version? The mounting problem happened with me only in this recovery too, maybe because it is updated, different or whatever but I flashed and everything was good. Anyway, stay with stock, it seems better for you.
Sent from my GT-S5570 using xda premium
Trublood_ said:
And you tried wipes using 5.2.0.8 version? The mounting problem happened with me only in this recovery too, maybe because it is updated, different or whatever but I flashed and everything was good. Anyway, stay with stock, it seems better for you.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
Yes, I guess I will stay with the stock :/ Though I'll try again when a new CWM recovery and a new Cyanogen mod come out.

Problem with flashing & booting recovery? Go here!

Hey guys,
when I tried flashing CWM on my new HTC One it just booted in normal mode over and over.
I tried every recovery-image available and it nerver worked.
While playing around I finally got it working without flashing the recovery image to the boot partition!
No need to copy root files and CFW files before flashing the recovery!
Instructions
Unlock your device at http://www.htcdev.com/bootloader/
Reboot into bootloader
> fastboot flash boot boot.img - thanx to Paul O'Brien
> fastboot reboot-bootloader
> fastboot flash recovery recovery.img - thanks to Flyhalf205
> fastboot erase cache
After this you should be able to enter recovery via bootloader or 'adb reboot recovery'.
The recovery image is CWM Touch 6.0.2.8 which worked great for me, didn't try the other ones right now.
I hope I could help
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Nekromantik said:
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Click to expand...
Click to collapse
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
zantekk said:
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
Click to expand...
Click to collapse
Ah ok.
only issue for me now is aroma freeze issues.
Nekromantik said:
Ah ok.
only issue for me now is aroma freeze issues.
Click to expand...
Click to collapse
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
zantekk said:
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
Click to expand...
Click to collapse
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Device still rebooting
Can't flash recovery
same here - no access to recovery so far
Same for me too
Why ?
Got a HTC One from Orange france, and NO RECOVERY seems to stick. That thing boots, but i cannot enter recovery
I've tried using the AiO-Kit to flash CWM touch and normal as well as TWRP as well as the two CWMs manually and then this method. Still can't get access to recovery though
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Lothaen said:
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If you mean clearing the cache as mentioned in that thread I've tried it with no success
SoLdieR9312 said:
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Click to expand...
Click to collapse
Had the same problem again and again flashing TrickDroid on my HTC One (M7). Can confirm, that avoiding touch will relieve things but freezes can still occur. A few times I even could not reset the phone long-pressing the power + volume up buttons, means I was completely stuck on the frozen aroma screen (since a battery pull is not possible with this device). For anybody who may be in the same situation, try the "[FONT="Courier New]fastboot reboot[/FONT] command, this still came through and rebooted the device.
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
pwr2wh8 said:
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
Click to expand...
Click to collapse
Yes, worked for me. I had the same issue. While flashing Renovate rom, Aroma crapped out right at the end where it was installing the kernel. I was then stuck on boot image until i found this thread.
Also, for what it's worth, i thought I'd flash the boot image again after i got my device running again but it killed my wifi. I had to reflash the rom as wifi in settings was `out of order`....
//edit: okay. i've been able to reproduce the crashing. seems it's an aroma/rom issue (i couldn't tell one way or the other). what matters here is flashing boot image with the provided image does the trick. whatever magic it does, i'm able to flash cwm recovery 6.0.3.1 but I have to flash boot image before, else flashing recovery is fruitless.
anyways, thanks. this thread help me solve what i thought was `bricked` device.

[q] cannot install cm 11!! :(

Hi guys I downloaded CM 11 from cyanogenmod.org for the Atrix HD and when I try to download it I get the error ''Status 7'' with CWM Recovery. Have you guys been able to install it with the file from the web site?? Please help :crying:
Are you running the latest recovery?
Phil recovery iss more up to date then the cwm itself
audit13 said:
Are you running the latest recovery?
Click to expand...
Click to collapse
Yes I am running cwm recovery 6.04.4e
SVLAN said:
Phil recovery iss more up to date then the cwm itself
Click to expand...
Click to collapse
How do I replace CWM recovery for Phil recovery?? Any guide??
Download and flash in recovery
Sent from my MB886 using XDA Premium 4 mobile app
Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=2302599
penser
audit13 said:
Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
Like I mention in every one of these threads, Status 7 is, at least 99% of the time, a bad download. Redownload and verify the MD5 checksum.
The MD5 for the official nightly is "513639551c586888db38bc9b17c7dab2". Use this program to verify the MD5 checksum.
helldogg75 said:
Download and flash in recovery
Sent from my MB886 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you. I just flashed that recovery and it worked.
I'm having the same problem with every single 4.4 and 4.4.x rom. I've tried removing the lines of code method already, running 6.0.2.8 cwm
ph3dia said:
I'm having the same problem with every single 4.4 and 4.4.x rom. I've tried removing the lines of code method already, running 6.0.2.8 cwm
Click to expand...
Click to collapse
4.4 needs the latest CWM to install. Try using Philz Touch Recovery or install the latest img from the Clockwork website.
I don't know if any of you guys solved your issues but you need to download cm11 onto external SD card then download philz touch version of cwm also on ESD card. Flash philz touch in your already existing cwm whatever version that may be. I forgot if it will boot back into recovery automatically but get back into recovery. If you are soft bricked get back in recovery by holding the power and vol up button I think and just flash rom as normal wipe data/cache/dalvik etc. That's how fixed my status 7 and flashed OSE 4.4.2 and loving it. Hope I helped.
Black_halo said:
I don't know if any of you guys solved your issues but you need to download cm11 onto external SD card then download philz touch version of cwm also on ESD card. Flash philz touch in your already existing cwm whatever version that may be. I forgot if it will boot back into recovery automatically but get back into recovery. If you are soft bricked get back in recovery by holding the power and vol up button I think and just flash rom as normal wipe data/cache/dalvik etc. That's how fixed my status 7 and flashed OSE 4.4.2 and loving it. Hope I helped.
Click to expand...
Click to collapse
So I was able to update my recovery but now every single rom that I try to flash ends up stuck at the motorola logo. I don't know what to do. I can still get into recovery but no rom works.
ph3dia said:
So I was able to update my recovery but now every single rom that I try to flash ends up stuck at the motorola logo. I don't know what to do. I can still get into recovery but no rom works.
Click to expand...
Click to collapse
Moto logo? Are you trying to go back to stock?
Black_halo said:
Moto logo? Are you trying to go back to stock?
Click to expand...
Click to collapse
Nah, it's the dual core technology right before the animation for the startup. I posted a thread about the problem.
ph3dia said:
I'm having the same problem with every single 4.4 and 4.4.x rom. I've tried removing the lines of code method already, running 6.0.2.8 cwm
Click to expand...
Click to collapse
Try flashing Phil's Recovery, it should be version 6.0.4.5. Once I flashed Phil's I have not had a failed flash of any 4.4 Rom.
Here is the link in case you need it.
http://forum.xda-developers.com/showthread.php?t=2552622
PeteSeiler2010 said:
Try flashing Phil's Recovery, it should be version 6.0.4.5. Once I flashed Phil's I have not had a failed flash of any 4.4 Rom.
Here is the link in case you need it.
http://forum.xda-developers.com/showthread.php?t=2552622
Click to expand...
Click to collapse
That's what I've been running
ph3dia said:
That's what I've been running
Click to expand...
Click to collapse
Maybe try going back to stock and starting over. Whenever I have strange problems like this and everything checks out, I revert to stock and start over.
PeteSeiler2010 said:
Maybe try going back to stock and starting over. Whenever I have strange problems like this and everything checks out, I revert to stock and start over.
Click to expand...
Click to collapse
That was the first thing I tried, I just get a black screen once the phone tries to boot up.
ph3dia said:
That was the first thing I tried, I just get a black screen once the phone tries to boot up.
Click to expand...
Click to collapse
Did you use fastboot commands or the RUU?
Sent from my Atrix HD using XDA Premium 4 mobile app

Categories

Resources