I have a brick, I'm trying to unbrick.
How I got here: I downgraded from JB to ICS, that worked fine. I backed up phone in cwm. When the phone turned on, the message: serivce required, code corrupted appeared.
I have downloaded RSD lite and the correct file and I'm trying to flash. To do this, I press volume UP and then power, correct? I have tried every combination, but the same message above appears.
I have tried using this unbrick: http://forum.xda-developers.com/showthread.php?t=2184877 and it worked before, but not this time.
Any ideas?
Thanks
Related
I had a perfectly running milestone on SHOLS_U2_02.27.B (Arabic Build). I flashed the phone using rsdlite 4.9 using G.O.T. 2.2.1 UK sbf. Everything worked perfect and the phone booted up and I had android 2.2.1.
When I tried to get into recovery mode nothing happened. I tried using the camera+power and x+power and it still didn't work.
I rooted the phone using universal androot and used quick boot to boot in recovery. I got the exclamation mark in a triangle, however, pressing the volume up and camera didn't work after like 50 tries.
I thought that something was wrong so I flashed the phone back to my original build using rsdlite.
Rsdlite works fine until it reboots the phone. The phone gets past the motorola logo however it gets stuck on the android logo. The android logo appears disappears appears... and so on. I left it there for 30 minutes and the same thing kept happening.
I reflashed back to G.O.T. UK 2.2.1 and it worked again, no problems.
I tried many official builds (UK 2.0, Arabic 2.1,Arabic 2.1update2,UK 2.1) and I get the same results.
I tried the G.O.T. 2.2.1 Telus sbf and it worked.
So to sum it all up, I can't flash anything but a G.O.T. build and I can't get into recovery mode. I can only get into bootloader.
Thanks for any help in advanced...
im new to moto droid , but if it seems to be bricked try a unrooting guide, that tends to get you back to were you need to be.
and if that does not work i say trying to download rom manager and flashing " clockwork recovery"
hope this helps bro
I tried rom manager and the main problem is that I can't access recovery so any unrooting/recovery guides are useless.
At this point I believe that the phone is damaged. I think I'll just flash it with an official rom and then return it as non working.
Have you tried restoring nandroid via ADB?
Hmm I have no idea how, could you tell me how or link me to a guide please?
Have you tried flashing the 90.78 Bootloader? cos this Bootloader allows you to enter the recovery mode by pressing the 'X'+power button and volume up+camera button after the triangle with exclamation mark appears.
Don't forget to extract G.O.T OpenRecovery.zip/Androidiani OpenRecovery.zip at the root of your sdcard. Once you've entered the recovery 2e(all the alphabets are in blue), select apply update. Without OpenRecovery installed in your sdcard,the apply update is useless.
If those method still couldn't get into the recovery mode,i suggest you need to flash vulnerable_recovery.sbf after you flash to stock ROM or any one you like. Google for OpenRecovery_v1_46_SHOLS. In the zip file contains the .sbf
I am on the 90.78 bootloader, I tried everything you just said before and nothing works. At this point I believe it's a hardware error. I will just flash the phone with the official sbf and replace it using warranty. Thanks for the suggestions though.
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.
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.
EDIT: Everything booted up after while, just took a really long time for it to completely boot.
I had my xt1060 Verizon Dev Edition rooted and unlocked running Android 5.1. I wanted to flash it back to factory, so I downloaded "XT1060_GHOST_VERIZON_5.1_LPAS23.12-39.7-1_cid2_CFC.xml.zip" from firmware.center. Then I used the commands from Motorola's Restore to Factory guide, to flash the files.
That caused a bootloop to occur and have the screen to stay at the warning bootloader unlocked screen. So then I downloaded "XT1060_GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip" and tried that, and still the same thing.
I had an old copy of "MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml" which I've used before to flash back to factory and I tried that. And now whenever I try to boot it up, it'll go into motorola's recovery and the image of the Android opened up keeps flashing on the screen, assuming that it's in a bootloop.
Up until this point I've been using osx-fastboot to flash the files, so I pulled out my old Windows laptop which had a copy of RSD Lite in it, and attempted to flash "XT1060_GHOST_VERIZON_5.1_LPAS23.12-39.7-1_cid2_CFC.xml.zip", which I tried the first time. I was able to get through that successfully, however it still did the same thing as before where the recovery was stuck in a bootloop.
I found this thread on here, and I followed the instructions for RSD Lite and the manual flash, neither worked did the same thing as when after I tried RSD Lite the first time. However the manual flash got farther, but is just sitting at the Verizon boot screen, and that's where it is right now for the last 15 minutes.