Help please...
I tried to flash CM7 onto my unlocked motorola Atrix 4g. Before doing so, I made a restore with Clockwork recovery and proceeded to flash the CM7 beta found on XDA. Before flashing, I made sure to wipe data/cache.
After doing this, my phone is stuck on the boot screen. I tried using the backup that I made to restore, but it says "can not find system.info" and finished. Then when rebooting it is still stuck at the boot screen.
Worst of all, my battery is now dead and wont charge! I searched and did some things in fastboot to try to fix it, but whenever I try to use fastboot, it gets stuck on "waiting for device".
Is there any way that I can save my phone or am I done for?
asdad123 said:
Help please...
I tried to flash CM7 onto my unlocked motorola Atrix 4g. Before doing so, I made a restore with Clockwork recovery and proceeded to flash the CM7 beta found on XDA. Before flashing, I made sure to wipe data/cache.
After doing this, my phone is stuck on the boot screen. I tried using the backup that I made to restore, but it says "can not find system.info" and finished. Then when rebooting it is still stuck at the boot screen.
Worst of all, my battery is now dead and wont charge! I searched and did some things in fastboot to try to fix it, but whenever I try to use fastboot, it gets stuck on "waiting for device".
Is there any way that I can save my phone or am I done for?
Click to expand...
Click to collapse
take your battery out and plug your phone into a wall charger. Then place the battery back in and let your phone charge.
After that fastboot flash romracer's recovery from the dev section. Reinstall cm7 and enjoy!
Sent from my MB860 using xda premium
Doing that to charge the battery didnt work
Also, I tried using romracer's recovery last night before the battery died, but it kept getting stuck on "waiting for device"
Did I use a wrong version of fastboot or something?
asdad123 said:
Doing that to charge the battery didnt work
Also, I tried using romracer's recovery last night before the battery died, but it kept getting stuck on "waiting for device"
Did I use a wrong version of fastboot or something?
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=9pYcgmLhUcQ
follow the instructions in that video to charge your phone, use a SPARE USB CABLE. do NOT hack apart your Motorola charger, you can pick up a USB cable for 2-3 bucks off the internet.
download the fastboot files from here: http://forum.xda-developers.com/showthread.php?t=1138092
after you get your phone charged (let it charge for about half an hour with that method) try to boot into fastboot and do a fastboot -w (this will wipe EVERYTHING)
download the latest recovery from here: http://forum.xda-developers.com/showthread.php?t=1204500
after you fastboot -w, you should flash Romracer's latest recovery by doing the command 'fastboot flash recovery <recovery.img name goes here>'
then boot into recovery mode and wipe Dalvik Cache, wipe Data, and wipe Cache.
after that, install CM7 beta. or any other ROM you want. you should proceed to make a backup immediately after your first boot into the device.
please don't ever try to flash anything if your phone is not at 100% charge.
Woo Thank you guys!
I went to a best buy and they switched out the battery for me and I was able to fix it with the directions you guys provided! Thank you so much!
Happened to me too. Minus the dead battery part. It was fine till I tried flashing fauxs 1.3ghz kernel. Then all hell broke loose
Sent from my MB860 using XDA App
I follow your instructions and i revived my atrix
thaks you so much!!!!
10 character
Hi all,
Today I wiped all data and cache from my device and installed VillainROM from CWM Recovery Manager. Install looked fine it said that it finished, so I went to reboot.
The device was stuck on the Samsung Galaxy S II logo with the yellow triangle (!) for around 10 minutes. I then turned it off cause I realized it wasn't going to boot.
Anyone have any idea why this happened? I restored a backup of my previous ROM and my phone booted up real fast and it was fine.
Could just be a bad download?
Sent from my GT-I9100 using XDA App
Try flash it again before it boots. IE: Flash from zip, then go back and falsh from zip again.
I've had to do that with CM...
OK will try that, cause the same thing happened to me when I installed Cyanogenmod straight from Rom Manager. Thx
Update: No go, I also made sure Deluxe Settings was uninstalled before I went into recovery. It's stuck at the boot screen.
However, upgrading my previous ROM (WanamLite v4.0) to WanamLite 5.2 worked fine and the device booted. It was exactly the same procedure in recovery mode but a different ZIP file.
Will try another ROM like LiteningRom and see if anything changes. I don't think it's a CRC error because I open up the files before I copy to the device to see if WinRAR pops any CRC errors.
I'd start on the thread a few up from yours.... the one that mentions if you have a boot loop
Sorry, I didn't realize it was a boot loop because it wasn't actually looping, just stuck on the image. Is that considered a boot loop?
Phone: EVO 3D hboot 1.5
What happened: I've been running and liking ScottsROM's CleanRom Reborn. Today I decided to try a few things. I used the Flash Image GUI app to flash TWRP 2.0 recovery. All seemed well with that. I was able to boot into recovery and reboot back to normal with ease and no issues. So I decided to try one of the Kushdeck's ICS Alpha roms just to see what it was like (knowing I was going to go right back to CleanRom since the camera still doesn't work in the Alpha ICS roms). So I boot into TWRP Recovery and perform a backup. Once it's done I reboot and open the Flash Image GUI app and install (as per joeykrim's instructions on using this app) the Kernal from the new ICS Deck Rom then boot into TWRP recovery to install the rest of the rom. I'm up and playing with ICS in a few minutes and all is smooth. After playing in ICS for a while I decide to go back to my CleanRom (the one I backed up before starting any of this), so I reboot back into TWRP recovery and clear all my caches and dalviks and also perform a wipe. After that's complete I then chose the restore option and let it do its thing. Once that finishes (no errors reported when it finished) I rebooted. Usually when booting up on CleanRom it goes straight into the CleanRom Boot animation screen. However here's where my problem begins (continue below):
Problem: Instead of getting the CleanRom Boot Animation I get the white HTC screen/Green HTC logo and after that clears the screen goes black(but still backlit) and the capacitive buttons at the bottom stay all lit up but that's it. Nothing else happens. Tried going back into recovery and clearing all caches again and re-restoring again but it just did the same thing...
Any advice or suggestions as to what I should do next? I'm currently redownloading CleanRom Reborn (since I'm at work) and was going to just try reinstalling the rom again.
phone wont load after restoring a back up
this happen to me when i was running lee's rom and i decided to flash warm's rom and i used the g u i flash tool to flash the kernal and every thing when well then boot into recovery and to flash the rom and the flash went well also and it booted up and played around with it and decided i didnt like it and i went back to lee's rom and what do you know im stuck in a boot loop and then i found out that some how i lost my boot.img so im willing to bet you have lost your's aswell so what you have to do is what ever rom you flashed i hop you have a back up copy of the zip of that rom on your laptop or desktop and extract the contence of that zip folder and it will create another folder now with in that folder you will see a boot.img this is what you need to to get your evo to boot up you will need to copy the boot.img file into the folder that you used to root your evo should be on your c drive then open up camand promt and typ fastboot flash boot boot.img and press enter and you have your evo 3d back enjoy
please forgive me if this has been asked before. i've tried searching but can't seem to find any fix. my phone was working great but i wanted to try a new rom since i was getting bored. my mistake.. anyway i have CWM recovery on my atrix and it worked good. i've flashed roms before.i was flashing between Neutrino ROM V2.9 and V3 trying to see if i could get the CMsettings to work on V3 without crashing. anyway after a while i gave up and decided to full wipe and just flash V2.9. after the ROM flash i reboot the phone but got a boot loop so i pulled the batter and tried to boot into recovery to wipe and flash again but when i select Android Recovery it just hangs at a black screen. what happened? can it be fixed quickly because my battery before the final flash was about 30%
BTW.. i've tried to reflash the recovery through fastboot and my compute the way i did it when i fist unlocked my phone and flashed the recovery but still no luck... still hang at blank screen after selection Android Recovery
never mind i fixed the problem.... had to flashed a different recovery (in this case TWRP) and then flash back to CWM recovery. idk the reason why but it worked and now my phone is back on and just in time with only 5% battery life left after all the trial and error flashing..
ok i figured out what caused my recovery to crash in the first place. its the gapp addon. when i flash that zip and reboot i get a boot loop and my recovery is gone. first i though it was the zip file that was damaged so i re-downloaded the gapp addon from Neutrino ROM V2.9 fourm but now chrome says the zip is infected so ok i went and download the full gapp addon for CM7 rom and that flashes without crashing my recovery but when the phone restarts i can't access half the gapp like market and gmail and a few others. they show that they are installed in Manage Applications but they don't show up in the app drawer.. whats the problem now? i've never had this problem before
I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer