Basically I wasn't paying attention while trying to delete backups in Safe Strap and started to flash a backup on my stock slot. I instantly did a battery pull and killed it, but ever since then I can't get it to boot. It goes to the red Motorola symbol then the screen goes black and it just sits there with the hardware buttons lit up.
I can access AP fastboot mode and the default Android recovery by holding down the volume keys plus power at boot up. I've already tried using RSD Lite to FXZ and tried wiping everything in recovery. But to no avail.
Does anyone have a possible solution to this problem or is it time I finally took the plunge and got a newer phone? Thanks for reading this.
Sent from Electrolyte, my Nexus 7 running Xenon HD ROM.
Vepaot said:
Basically I wasn't paying attention while trying to delete backups in Safe Strap and started to flash a backup on my stock slot. I instantly did a battery pull and killed it, but ever since then I can't get it to boot. It goes to the red Motorola symbol then the screen goes black and it just sits there with the hardware buttons lit up.
I can access AP fastboot mode and the default Android recovery by holding down the volume keys plus power at boot up. I've already tried using RSD Lite to FXZ and tried wiping everything in recovery. But to no avail.
Does anyone have a possible solution to this problem or is it time I finally took the plunge and got a newer phone? Thanks for reading this.
Sent from Electrolyte, my Nexus 7 running Xenon HD ROM.
Click to expand...
Click to collapse
I did something similar, except I was altering init.rc files manually, and the phone bricked pretty hard. If RSD Lite doesn't work, you can use fastboot from linux to step through the XML file line by line.
If you unzip your ROM's install file, you should see something like a bunch of files in a system directory, then an XML file in a MANIFEST directory. That XML file is essentially a list of commands that RSD Lite runs, and they line up pretty much one-for-one with fastboot command line parameters.
Fastboot from linux:
http://forum.xda-developers.com/showthread.php?t=1263009&highlight=fxz
Related
first of all i would like to thank anyone who tries to help me. i am somewhat new to the motodroid i own an evo and i am trying to help a friend. the phone is a verizon motodroid 1. the phone has been rotted for about a year he was running i think buggless beast at the time it died the initial problem was his baseband along with a few other software info went to unknown status. first he tried a backup, after not fixing the problem he contacted me and i decided to take a look at it after researching on multiple websites the best conclusion i found was to download the drivers for the phone, rsd lite, and the sbf files to reflash the phone back to stock.
i tried all of this with no good results know the phone wont boot past the M logo screen in the boot animation. the phone is unable to restore any backups at this point. every time i run rsd lite it seems to work and at what i believe is the end i get a fail. then when i hold up on the d-pad when turning on the device it reads.
bootloader
2c.7c
code corrupt
and the phone is now unable to charge the battery also the only thing i was successful at accomplishing was flashing the sbr recovery but still could not flash any rom or the update zip that someone had mentioned to flash
any help would be appreciated
ok my best hit at it is resetting the hone. i bought a used droid 1 and the previous owner had left the " connect the dot " lock screen on it so after googling some **** i came accross a site that said something about booting into recovery. hers the steps
slide screen up and press and hold " x " and power until you get a triangle on your screen. now press both, the volume up key and camera simatainiously untill text appears then select reset or factory reset. this worked for me so hope this helps.
that was all done before i tried to use rsd lite and had no results after using rsd lite it completly removes the stock image then rewrites a new one. the problem is the removal of the image passes but writing the image fails so i am left with nothing.
I need some help please. I seem to be in a pickle, though I’m not bricked. (At least, not yet.) So I rooted my phone last night, using [GUIDE][NOOB]Step-By-Step Instructions for New Stock Bionic Owners. Everything went great, and I got root. I followed the guide to get the .901 update, which went fine. Tried the ROM suggested, and liked it. Thought I would try Eclipse v2.1. I installed it, but I like Visual Voicemail, so I decided to use my Nandroid that I did right after root and revert back. Here is where problems started.
After the restore, it wouldn’t boot. Passed the Moto Dual Core logo and hung up. Allowed 10 minutes and after nothing, I flashed back to the backup I made after installing Eclipse. It booted fine. So I decided to go back to stock rom, debloat it how I like it and just run the debloated stock. Here is where problems started. I can’t find a flashable copy of the stock. Just a couple of guides on using RSD Lite. This is for Bricked Bionic’s, but I decided to try it, since one of the guides said it works to get back to OTA.
Downloaded the RSD Lite and the full system file to flash. I put my phone into the mode to flash (Power + Volume Down), unpacked the file with RSD Lite and tried to flash. Got an error.
Failed flashing process. Failed flashing process. 1/15 flash cdt.bin"cdt.bin"-> Phone returned FAIL.; phone connected.
Now, when I reboot my phone, it goes back to the Fasboot Flash Mode screen saing (Failed). I can boot into recover (Volume Up + Volume Down + Power) and do a Normal Boot, and it boots fine.
I tried a Factory Reset, and it just reset’s on Eclipse v2.1.
I want to simply get back to stock. Rooted or unrooted, I don’t care. I’ll reroot if I need to.
I also tried to download the STOCK Deodexed files. The links are dead. Figured if I went back to one of those stock images, I could unroot and see if everything was ok.
Suggestions?
Hmm..I think your mistake was in safeboot when you tried to go back to original back up you were suppose to toggle safe system so that it would be disabled. From there you would've been able to restore your original system and boot up just fine. It was mentioned in the guide through some posts.
Sent from my DROID BIONIC using Tapatalk
ms0chez said:
Hmm..I think your mistake was in safeboot when you tried to go back to original back up you were suppose to toggle safe system so that it would be disabled. From there you would've been able to restore your original system and boot up just fine. It was mentioned in the guide through some posts.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
So I need to turn Safe Mode off in SafeStrap and flash? I had thought about that, but I was worried about totally bricking the phone. I'm pulling SafeBoot now, and will try the flash.
EDIT...
SafeMode is off, and rebooted. I'm back to .875 Stock Rooted. So far, so good.
I can either flash from here (haven't tried yet) or stay here. When I boot, I'm still booting into Fastbook with (Flash Failure). Any way to get that off, other than flashing back to stock and locked through RSD Lite?
Your mistake was trying to restore from the un safe system. You can toggle safe system and you'll be ok. Or, reinstall a ROM to your safe system.
To clarify: don't flash a ROM with safe system disabled. toggle back to safe mode, and then pickup my directions from the format /system step. You can try another ROM no problem then.
I bet you can find the visual voicemail APK and add it whichever ROM. Copy paste into system/app directory.
Thanks. I'm used to flashing with the Thunderbolt and the XOOM. Not used to safestrap, just normal CWM.
Any idea how to stop the phone from booting into Fastboot? Having to do it the long way still. I'd be happy staying this way, if I can get that resolved.
Actually the problem was you tried to restore to a backup of a pre .901 system which has different radios which flashing doesn't like.
As for the flash failure, get the fxz files and put them in a folder with adb and fastboot. Then run this command in a prompt:
fastboot flash device_tree.bin
When you get a flash failure you just need to flash something to fix it; flashing device_tree.bin won't affect anything.
Its one solid file with a weird extension. Is there a way to unpack it? I am out right now and don't know the extension by heart.
Its a zip, just extract it
Sent from my DROID BIONIC using XDA App
Now, I'm scratching my head. (Again) I've worked with ADB with my Xoom, so I'm not a noob at that part. ADB doesn't see my phone. My computer does, and the phone know's it's plugged in. However when I try to flash the file, it can't find the device. I checked "adb devices" and it's not on the list.
So I decided to go ahead and flash completely back to stock with RSD Lite. Still get's the same error message. (I did check the MD5 SUM on the file. It's correct.) Safe Mode is off in Safestrap. Here is what the Fastboot screen looks like on my phone.
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Since I've not seen the Fastboot screen on this phone until this started, I don't know if the (S) has meaning. Like, it thinks the phone's still in SafeMode?
I noticed one of the options in safestrap is to disable safestrap. Thought about trying that, but.... Unsure.
So I have a rooted Atrix HD that I tried to restore to stock using the original fastboot files from this thread:
http://forum.xda-developers.com/showthread.php?t=1853522&page=2
I ended up getting error messages with the 1st xml file so I used the modified one in Post #14 of the same thread.
Phone appears to flash properly but gets stuck at AT&T logo and RDS makes me power cycle the phone after an eternity.
When I do and get back into fastboot it says pass and thinks everything is good.
Bad news for me is I'm stuck at the AT&T logo and can't move forward.
I can still get into boot mode selection menu so that appears to be good but I'm at a loss on how to recover this thing into a working phone again.
Anyone have any insight?
Battery life was right around 50% when I started.
Maybe RDS puked since it wasn't at 75%?
Any help would be greatly appreciated.
Make you are using the latest version of RDS 6.1.4 and make sure that your cable is perfect and that your phone is detecting properly.
I think I figured out part of my problem.
Used the modified xml file for 144 with the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file.
RDS lets it flash but never gets past the AT&T logo.
Now if I try to go back and flash with the right file for the modified XML I get 1/24 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I think I might have borked this phone......
windago said:
I think I figured out part of my problem.
Used the modified xml file for 144 with the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file.
RDS lets it flash but never gets past the AT&T logo.
Now if I try to go back and flash with the right file for the modified XML I get 1/24 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I think I might have borked this phone......
Click to expand...
Click to collapse
That fastboot is not for Retail AT&T devices.
Well after booting phone into BP tools to let it charge all night I attempted to reflash this morning with a full battery and a new USB cable using the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file and we're back in and now on 4.1.1.
Time will tell if we're back to normal for good.
What is the BP tools you mentioned? Because I've known that it's imposible to charge the phone while it is stcuked into bootloop or even being in the Bootloader screen.
jics91 said:
What is the BP tools you mentioned? Because I've known that it's imposible to charge the phone while it is stcuked into bootloop or even being in the Bootloader screen.
Click to expand...
Click to collapse
BP Tools is the fifth option available when I boot into the boot mode selection menu by pressing Vol Up/Vol Down + Power.
Boot Mode Selection Menu (10.9B)
Available Boot Modes:
Normal
Recovery
AP Fastboot
Factory
BP Tools
I ended up plugging the phone into my Galaxy S3 wall charger last night and then selecting BP Tools when I entered the Boot Mode Selection Menu.
A simple battery icon appeared telling me I had 9% battery left.
This morning after keeping it plugged in all night I had 100% battery.
As I stated earlier after a full charge I was able to flash using RSD lite and now have a working phone again.
windago said:
BP Tools is the fifth option available when I boot into the boot mode selection menu by pressing Vol Up/Vol Down + Power.
Boot Mode Selection Menu (10.9B)
Available Boot Modes:
Normal
Recovery
AP Fastboot
Factory
BP Tools
I ended up plugging the phone into my Galaxy S3 wall charger last night and then selecting BP Tools when I entered the Boot Mode Selection Menu.
A simple battery icon appeared telling me I had 9% battery left.
This morning after keeping it plugged in all night I had 100% battery.
As I stated earlier after a full charge I was able to flash using RSD lite and now have a working phone again.
Click to expand...
Click to collapse
Congrats. I know exactly how that feels. I was in a similar situation not too many days earlier! It is a little sad that there is very little help online when you get stuck when trying something on this phone. You end up having to figure things out by yourself.
windago said:
Well after booting phone into BP tools to let it charge all night I attempted to reflash this morning with a full battery and a new USB cable using the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file and we're back in and now on 4.1.1.
Time will tell if we're back to normal for good.
Click to expand...
Click to collapse
So flashing this worked for you? I think someone tried this a week or so ago and it bricked their phone.
Sent from my MB886
ReverseZero said:
So flashing this worked for you? I think someone tried this a week or so ago and it bricked their phone.
Sent from my MB886
Click to expand...
Click to collapse
Please no one try that file... it will only work on bootloader-unlocked Atrix HD devices since it is not a build meant for retail AT&T devices.
Makes sense. Don't think I'll be trying that.
Sent from my MB886
As mattlgroff stated:
Please do not flash the file I linked to/reference to in my OP.
He's a developer and has much more insight into the workings of these files then I do.
I'm not sure why mine worked but I defer to his statement about not flashing that particular file.
I was on stock JB. Rooted with new exploit. Installed bootstrap and custom ROM. Wanted to get back to stock, so I uninstalled bootstrap, and flashed MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip.
RSD failed with 'getvar' and 'oem'. I then edited the xml, removed 'getvar' and 'oem', and retried the flash. RSD failed at system.img.
I then booted the phone into fastboot and did the whole thing manually thru fastboot and terminal. This time everything went through okay. I rebooted the phone into stock recovery and erased cache. But now the phone is stuck in bootloop on the red m logo.
What am I missing?
I am having trouble to flash back to stock ICS with RSD lite everytime i use it and connect my phone it says USB connected but that is it. I cannot find the associated file anywhere to flash back to stock any ideas?
I've got an Atrix HD and I've been trying to flash HoloBlur since a while now.
I'm presently on 4.1.1 (98.4.20.MB886.ATT.en.US).
I used the Motochopper tool to gain root access. Success.
I used the Motoapocalypse tool to unlock bootloader. Success.
I've used the Myth Tools to flash the inbuilt CWM as well as other versions of it. I've also tried installing CWM through fastboot. All of the methods which I use tell me that the recovery was flashed successfully. However I cannot enter recovery mode at all. I've used to Myth Tools to enter recovery. Failure. I've powered down and tried the Vol-Up and Power button combination. Failure. I just get the image of the dead Android.
Also, in the fastboot mode, pressing the Vol-Up or Vol-Down buttons does not do anything.
I know for sure that I'm rooted. The Super User app is fully active. I've removed AT&T bloatware to confirm this. The app is fully functional.
I also am certain that the bootloader is unlocked. I've verified this through the fastboot mode.
I don't have a clue about what am I doing wrong. I just cannot enter recovery mode at all.
Any help regarding this will be greatly appreciated!
Reinstall cwm through adb? Is the phone still working?
Sent from my MB886 using Tapatalk 4
salafra 367
The phones working perfectly fine. The only problem is that I can't enter recovery mode no matter what. I've tried flashing recoveries through fastboot, adb, toolkits, everything. The phone merely shows the dead Android when it enters recovery.
Rabie Haider said:
The phones working perfectly fine. The only problem is that I can't enter recovery mode no matter what. I've tried flashing recoveries through fastboot, adb, toolkits, everything. The phone merely shows the dead Android when it enters recovery.
Click to expand...
Click to collapse
Try starting from scratch using RSD Lite to flash yourself back to stock. Then begin the process again, minus unlocking the bootloader, since you already did that.
I really don't want to do that. Since I dont have access to any recovery at this time, I cant make a Nandroid backup. Which means in case things go bad with the flashing, Ill be stuck with a bricked phone.
did u rename the file install_recovery.sh?
devilsking said:
did u rename the file install_recovery.sh?
Click to expand...
Click to collapse
No. However I just tried doing this.
I downloaded CWM Touch 6.0.3.6 from m0ndul's thread.
I extracted the package. Copied the recovery image to moto-fastboot folder as well as recovery folder for Myth Tools.
I entered fastboot and used 'fastboot flash recovery recovery.img'. Fastboot gave me success notification.
I restarted the phone and entered recovery. The phone shows the dead Android image.
So then I renamed the file to 'install-recovery.sh' in both fastboot and Myth folders.
Both fastboot and Myth Tools give me success notification.
However on entering recovery the same dead Android image comes up. :crying:
You should definitely RSD or MythTools back to complete stock and do the process over again, as mentioned above. It is the only conceivable fix to this strange problem at the time. As long you don't unplug the chord during RSD flashing then nothing will go wrong, I've had to do it about 3 times. I may be wrong, but I'm pretty sure that if an RSD flash was unsuccessful you wouldn't be able to use that nandroid backup in the first place, fastboot would be pretty much the only place you can go.
Even if it didn't work (very highly unlikely), this is another way to do it that will definitely work: http://forum.xda-developers.com/showpost.php?p=40929335
Here's all you need: http://sbf.droid-developers.org/dinara/list.php The third ATTUS and the Mexico Retail are the only two that will work.
I have the AT&T model as well and I have used the Mexico Retail zip every time without fail.
Replace the XML file inside of the zip with this one so that it flashes properly: https://www.box.com/s/num1eshkf0c2or2h4160
It is completely safe, just don't do it during shceduled power outages, storms, don't touch the data cable, and let it do its thing until it boots back up.
Can you boot your phone? If you can, install Root Explorer and change the recovery file name by adding .bak to the end, then try to install cwm.
Neighbor808 said:
You should definitely RSD or MythTools back to complete stock and do the process over again, as mentioned above. It is the only conceivable fix to this strange problem at the time. As long you don't unplug the chord during RSD flashing then nothing will go wrong, I've had to do it about 3 times. I may be wrong, but I'm pretty sure that if an RSD flash was unsuccessful you wouldn't be able to use that nandroid backup in the first place, fastboot would be pretty much the only place you can go.
Even if it didn't work (very highly unlikely), this is another way to do it that will definitely work: http://forum.xda-developers.com/showpost.php?p=40929335
Here's all you need: http://sbf.droid-developers.org/dinara/list.php The third ATTUS and the Mexico Retail are the only two that will work.
I have the AT&T model as well and I have used the Mexico Retail zip every time without fail.
Replace the XML file inside of the zip with this one so that it flashes properly: https://www.box.com/s/num1eshkf0c2or2h4160
It is completely safe, just don't do it during shceduled power outages, storms, don't touch the data cable, and let it do its thing until it boots back up.
Click to expand...
Click to collapse
SOLVED!
I followed instructions from the CWP thread by some other members.
I've had dozens of Androids and I've flashed things hundreds of times but nothing got as messy as AHD did.
In short, bootloops, nuclear warfare and whatnot later, I'm running HoloBlur.
Thanks a million for your assistance.
Rabie Haider said:
SOLVED!
I followed instructions from the CWP thread by some other members.
I've had dozens of Androids and I've flashed things hundreds of times but nothing got as messy as AHD did.
In short, bootloops, nuclear warfare and whatnot later, I'm running HoloBlur.
Thanks a million for your assistance.
Click to expand...
Click to collapse
How did you fix it?
UPDATE:
Nevermind... JUST Remove ~/system/etc/install-recovery.sh it keeps on overwriting the recovery when you boot.
Just That?
MGA2009 said:
How did you fix it?
UPDATE:
Nevermind... JUST Remove ~/system/etc/install-recovery.sh it keeps on overwriting the recovery when you boot.
Click to expand...
Click to collapse
Just that?
you did the whole thing to replace files on the rsd thing? or this is the noobsafe method to get into the recovery?
BTW i'm noob...
clopezloud said:
Just that?
you did the whole thing to replace files on the rsd thing? or this is the noobsafe method to get into the recovery?
BTW i'm noob...
Click to expand...
Click to collapse
That's way to install custom recovery since renaming that file is the necessary step before flashing custom recovery.
First of all, I've looked around for answers, and I seem to find the same solution everywhere, which is OK. It just doesn't work for me.
Here's the drill. My Moto X was sitting in a drawer for a year or two. I took it out a while ago to update it and see how 5.1 worked on it. I put it back in the drawer as an emergency phone. Last weekend I took it out, to find that it's stuck in Fastboot. the up volume key scrolls, and down volume key does nothing (originally down scrolls, up chooses) and the power button reboots.
Long story short, I was able to get my computer to recognize my phone (tried for hours until I realized it was the cable, use the right cable and voila!) I unlocked the bootloader via Motorola, and after hours of trying was able to flash everything I thought was necessary (boot, recovery, motoboot, system, and so on). However, in every thread and video, the "fastboot reboot" command makes the phone reboot into the actual OS, whereas mine just keeps rebooting into fastboot, regardless of what I flash.
I don't notice anything off, so hence why I recur to everyone in here to give me some advice on what I could be doing wrong. I've downloaded stock roms so far. I get a partition error with .zip files so always have to flash the images individually.
Please let me know if I'm missing any details, and/or what other information I should provide.
Thank you!!
SantiagoEB24 said:
First of all, I've looked around for answers, and I seem to find the same solution everywhere, which is OK. It just doesn't work for me.
Here's the drill. My Moto X was sitting in a drawer for a year or two. I took it out a while ago to update it and see how 5.1 worked on it. I put it back in the drawer as an emergency phone. Last weekend I took it out, to find that it's stuck in Fastboot. the up volume key scrolls, and down volume key does nothing (originally down scrolls, up chooses) and the power button reboots.
Long story short, I was able to get my computer to recognize my phone (tried for hours until I realized it was the cable, use the right cable and voila!) I unlocked the bootloader via Motorola, and after hours of trying was able to flash everything I thought was necessary (boot, recovery, motoboot, system, and so on). However, in every thread and video, the "fastboot reboot" command makes the phone reboot into the actual OS, whereas mine just keeps rebooting into fastboot, regardless of what I flash.
I don't notice anything off, so hence why I recur to everyone in here to give me some advice on what I could be doing wrong. I've downloaded stock roms so far. I get a partition error with .zip files so always have to flash the images individually.
Please let me know if I'm missing any details, and/or what other information I should provide.
Thank you!!
Click to expand...
Click to collapse
Flash system.img and boot.img then flash twrp.img and boot into twrp and flash your stock ROM for your device