Motorola Droid X :: Won't Boot Past Motorola Logo Nor Boot In To Recovery
Sep 16, 2010
I tried installing Tranquility and must have screwed something up because now my phone won't boot past the Motorola Logo. It's been sitting here like this for about 15min and I can't even boot into recovery by holding the power and home buttons. I don't know what else to do now. Idk if my phone is bricked but even if it is don't I need the SBF file to unbrick it and I can't find that file any where. I did a nand backup or whatever before doing any of this so hopefully that can help me. What should I do now?
I picked up a brand new Droid X, turned it on, got it all setup, and it downloaded my apps that I used to have on my old Droid. Then I rebooted it after all the apps were installed and updated, and now it will not move past the Motorola logo screen.
Searching around the internet I have found others that ran into this issue, but they were always rooting their phones. I also am not able to boot into recovery mode.
I have not rooted it, attempted to root it, or done anything other than as described above.
Is there anything I can do? Or do I have to just head back to Best Buy and demand a replacement unit?
I have rooted my device and then downloaded CWM and tried to install Cyanogen Mod, I have tried this before and it just rebooted with nothing happening. This time the device would not boot past the motorola logo. I took out the battery and attempted to boot but again the device got stuck at the moto logo.
I went to reboot my Droid because it was lagging a little and when it came back on it go stuck at the Cyanogen boot screen. I pulled the battery, put it back in and held the X to boot in recovery and my recovery won't come up either. It just skips right to the Motorola M and if it doesn't get stuck there it goes back to the Cyanogen screen.
I haven't made any changes to the phone at all so I am completely puzzled on why this is happening. I obviously can't take it back to Verizon since its rooted so if there is a way to fix this I really want to because I love my phone and my wife will kill me if it is screwed up.
This is to change the motorola logo that you see when you boot your phone to a custom image. This is separate from the boot animation seen afterwards.Tools/files you will need: 1) RSD Lite 2) droid sbf 3) SBFCodec 4) Photoshop (or paint, or whatever drawing program) 5) Hex editor (frhed is free and very easy to use) NOTE: I do not use sbf-recall because it complains about needing version 1.3, so I use SBFCodec instead.Steps: 1) Run SBFCodec and open up the sbf file. This will extract all the smg files and header files. 2) Using photoshop, create an image that is 480 pixels wide and 182 pixels tall. Each color should be assigned 8 bits (1 byte), or in paint, just make a 24 bit bmp file. Mirror the image, making the left become the right, and the right becoming the left. Save as a bmp file (photoshop method). 3) Using a hex editor, open up your image and erase the first 54 bytes of data. (and possibly the last 2 bytes of data if you used photoshop. the number of bytes remaining should be exactly 262,080) With the remaining data, reverse the bytes. (using frhed, the option is in the edit menu->Reverse bytes) 4) Using a hex editor, open up the CG42.smg file created in step 1 and erase all data except the last 64 bytes of data (these 64 bytes of data should be FF's in the file). Then paste in the remaining data from step 3 to the beginning of the file and save. Your final file should be exactly 262,144 bytes large. 5) Go back to the SBFCodec window and save (this creates the sbf) the sbf file and name it whatever you want. i.e. boot.sbf 6) Using RSD Lite, flash this sbf to your phone. It may take 5-10 minutes for the flashing to complete. (after the 10 minutes, it might say "failed", just click on the show device button once that happens and you'll have succeeded)You now have a stock phone with a custom boot image. Go ahead and root your phone and stuff. Sorry for the difficult instructions, this was the only approach I could think of to edit the boot logo.
Ever want to change the ugly Motorola boot logo on your Droid X or Droid 2? Now you can with DX/D2 Logo Changer on the market.For a gallery of all the images you can choose from see here.Special thanks to Team Black Hat who originally started work on changing the boot logo and the many people on these forums who created the images.If you created an image used in the app let me know and I will put your name in the about/help section.
I installed a custom bootlogo a while back, but my phone is giving me hardware trouble (keyboard and audio jack) so I will have to eventually have it replaced.I was wondering if anyone had the original "M" bootlogo, or could direct me to where I can find it.
So I decided to hijack the "Red Rage" boot animation and use it as the base of my animation. Mine just has some Georgia Bulldog love to it. Also I have modified my boot logo and no longer have the "M" its now a lot nicer. I will include the bootanimation.zip in case anyone wants this. Just place it in the /data/local/ folder. Do not Unzip it, leave it how it is. If you have another one there just rename it with a .bak extension in case you don't like mine. Its stretched a little vertically, not sure why not too noticeable tough. http://www.youtube.com/watch?v=0mAMNbLANnI
My Motorola Droid will no longer boot into recovery. the last time I was able to access it was when I rooted. Please help. I have tried the recovery console command in adb shell. It did not change anything.
I downloaded one of chevys kernel an I was going to install this kernel hoping for better battery life. Before I did, I tried booting into recovery and all I got was the M symbol. I then tried flashing alternate recovery(sprecovery) and then went to boot into recovery an that still didn't work. Does anyone have any suggestions? I don't know if its related to that download of the kernel or what. But this is very frustrating knowing I don't have recovery.
I KNOW my phones rooted, ive applied the update and ive been doing root things for quite awhile. However, when I go into rom manager, download a rom, and install it, it brings me to the normal recovery menu, the blue one with only 4 options. I reapplied the update.zip and still nothing. When I try to reflash the clockwork it says... An error occured when attempting to run priveleged permissions
I messed up the reinstall i was doing of flyx and it messed everything up. i cant boot past the M logo and i lost recovery so i have no idea what to do. It's sad because i've been doing all of this since the g1 but this is the first time i have been truly lost.
I restored my X using my nandroid backup. Upon following the steps to apply Apex's ROM, everyone was going fine. I signed into my google account on my phone. Once I made it to the home screen, everything was black and still is. No matter how many times I power cycle or pull the battery its black. How can I boot into recovery to run my restore again?
Instead of seeing the boring old Android logo or my service provider's logo, I'd love to see the standard text-based Linux boot screen that shows the status of all the hardware and configuration info as my phone boots. My current phone is an HTC EVO 3D running Cool ICS with Sense 3.6 and Revolutionary CWM.
I semi-bricked my phone. I installed Rubix Rom through Rom Manager and it installed over top of FlyX. It starts up like normal (just doesn't go to the Koush Recovery screen on startup). When I unlock the phone, there is just the status bar and everything else is completely black. I can connect usb and change how it connects.Is there a way to get into the Koush Recovery manually at startup somehow? I just want to flash back my backup. I'm at work and I'm using OSX so I can't exactly do the SBF (unless someone knows a way without having to set up a virtual machine).
I've been running Kangerade since shortly after it came out... And loving it.. Yet today I saw my phone was rebooting - and waited (figured it over heated or some such..) and waited... And waited... That android boot image does stop being cute after a while... Crap.. Just cycling... Go into recovery... Umm.. No seriously.. Go into recovery.... Go on.... Nope. (apparently latest ROM MAnager screwed up CWmod..) So... Can't load my phone... Can't restore backup..
I download ROM manager and flashed clockwork recovery, but it wouldnt let me boot into it. I tried from ROM manager and by rebooting and holding x. MY permission were all set correct, i dunno what happened. I have read else were that other people were having the same problem. I went ahead and flashed SPrecovery back and it worked.
I've been reading and I've downloaded the ROM Manager from the Marketplace. I've also downloaded a ROM to install. I have tried to boot my phone into recovery mode (pressing X while powering back on) and all I get to is a screen with the exclamation mark and a phone under it.
I downloaded rsdlite set up the drivers and flashed the 2.1 sbf, I was on the leaked 2.2. on Droid X it says to boot into recovery and wipe system and data, but if I try to go into recovery it just shows a triangle with a ! inside it. So I booted normally and its stuck at the red eye. help pleasee I really need my phone
I try to understand android boot sequence on my JB (under CM10). I found some docs and there should be specific partitions (boot, recovery, system, cache, data).
My understanding of the boot sequence is now:
A) normal boot: 1) Power ON -> 2) bootloader -> 3) boot-partition where i flashed the kernel aka boot.img -> 4a) system-partition with the OS (libs, UI, etc) where i unpacked over CWM my customROM.zip -> 4b) data-partition, where i unpacked google-apps.zip and installed all the apps -> 4c) cache-partition with user data
B) recovery boot (adb reboot recovery): 1) Power ON -> 2) bootloader -> 3) recovery-partition with CWM where i may unpack all the .zip stuff to proper partitions, or restore from sdcard, etc.
Is this correct? I wonder, because i didn't installed CWM into recovery-partition. It cames from install of CM10 (fastboot -i 0xfce flash boot boot.img), so it must be in boot-partition and not in recovery?
So, next confusion: i looked up to /proc/mtd and i don't see neither boot nor recovery partition here:
I did a backup with CWM and loocked the data. There aren't boot, and recovery backups:
# ls -lha /sdcard/clockworkmod/backup/2012-10-04.18.49.55/ d---rwxr-x 2 system sdcard_r 4.0K Oct 4 18:56 . d---rwxr-x 3 system sdcard_r 4.0K Oct 4 18:49 .. ----rwxr-x 1 system sdcard_r 1.6K Oct 4 18:54 .android_secure.vfat.dup ----rwxr-x 1 system sdcard_r 54.6M Oct 4 18:55 cache.yaffs2.img ----rwxr-x 1 system sdcard_r 360.2M Oct 4 18:53 data.yaffs2.img ----rwxr-x 1 system sdcard_r 212 Oct 4 18:56 nandroid.md5 ----rwxr-x 1 system sdcard_r 214.6M Oct 4 18:51 system.yaffs2.img #
So, i think i didn't understand the boot sequence and partition schema corectly.
I just used the pc36img.zip from the how to guide on rooting. It apparently worked this time but now I'm stuck at the boot screen. I suppose I have no ROM now? Where can I get one and what do I do with it. if that is indeed the problem?