Database Develop

ROM Manager no boot loader

Hi,
Full version as a note. Droid 1
Flashed clockworkmod recovery (2.5.0.1), went fine. Made a backup of stock rooted ROM, worked fine. Next flashed bugless beast .6, while clearing data & cache, no problem.
Now i want to flash to cm - trying out different ROMs - trying to reboot into recovery or flash another ROM both fail to get me to a bootloader. Instead i see the motorola boot logo for 30-45 seconds, followed by what looks like a regular boot (motorola M, then Droid eye, & booted.). I have also tried fixing permissions.
If anyone has any idea why this is happening or can direct me to a forum link it would be greatly appreciated. Sorry if this is in the wrong section, and yea I've tried looking through the forums for a while.
Thanks

just a little baby sized pump...

This happened to me too after working perfectly for several months. All of the sudden I just couldn't get to clockwork. I am running CM7 Nightlies. After not being able to fix the issue for several days I decided that a full wipe via the .sbf method was in order. I've got everything up and running again but it was an annoying process. Can anyone out there help us to understand why this happened so we don't have to deal with this again?

Do you have a link for the method you described about? That would be really helpful!

An ever so slightly larger bump
I really am not trying to be lazy, but all the .sbf methods I've read so far seem require you getting to a boot loader. If I could get to a boot loader this wouldn't be a problem, as I made a back up of my stock ROM. I have a functioning bugless beast ROM, just no recovery / boot loader, and no way to flash back to my recovery.

And possibly solved..
One: Please pardon my ignorance, doing these things on my Eris was far easier, or at least what I got used to.
Two: Please also ignore the word boot loader in my previous posts, as it was the recovery console that I could not get to load. Sorry Again.
Three: Its magically working. My methods were unscientific to say the least, but the Droid is now in "ClockworkMod's Recovery v2.5.0.1".
Things I finally did:
NOTE - I DO NOT BELIEVE ANY OF THIS TO BE THE PROPER ORDER OF THINGS. PLEASE VERIFY WITH SOMEONE FAR MORE INTELLIGENT THAN ME. THE FOLLOWING REFLECTS THE PROCESS I DID, AND SHOULD PROBABLY NOT BE FOLLOWED UNLESS A MOD ACTUALLY SAYS THIS WAS CORRECT
1. Pulled Battery, hold power button down for a few seconds, and then put back in
2. Hold Up on D-pad while holding the Power Button
3. You see the following
Code:
bootloader 2c.7c
battery ok
ok to program
connect usb
data cable
4. Connect USB data cable to PC running RSD Lite. You will also want a .sbf recovery file from a trusted source.
5. Select the .sbf in RSD Lite. Tell it to start. I used the clockwork recovery only .sbf
*** Where things got officially weird for me ***
6. The .sbf file I told it to load seemed to work, as the progress bar moved. The phone almost instantly rebooted, back to the ROM I was running minutes earlier. Clockwork had not been working previously trying to reboot into recovery, but almost instantly upon trying this time, I was in recovery mode.
NOTE - The USB cable was still plugged in as well. I don't know which combination of things actually got this to work, but it did.
Hope this helps someone else out.

[Q] Can anyone help??? Deleted Folders with Rootexplorer.

Hi,
This is my first post so please if I'm in the wrong place or doing anything wrong please let me know.
My problem and yes I am the fool to blame! The other night I was playing with root explorer and decided it would be a "great" idea to delete all the folders on my Milestone A854, PDS DATA etc etc.
What harm could it do? I just reinstall a rom back on and all sorted...... Wrong! I reinstalled roms using mini mod and then sbf files with RDS lite both producing the same outcome. A phone that displays the "M" Motorola logo then turns off and tries again......repeatedly!
Any help would be GREATLY appreciated.

Hello,
I know for me, I did the same thing with my Motorola Droid. But the thing is I didn't know what files the Droid had when it was in factory mode. So I decided to flash back to the original, in my case Verizon, SBF file. Then I rebooted, and let my phone update itself to the latest version, then did the whole "rooting" process, with the same rom I've been using.
Hope that helps
~Jin

Thanks Jin,
My problem here is I don't know what it had in the first place? I've tried flashing stock UK SBF but that just puts you in the Motorola boot loop so no opportunity to update.
Any further help/suggestions would be greatly appreciated.
Dave

im sorry if i get it wrong, so u cant get to recovery mode or sort of? i deleted one of the folder on /data n /system before, but i managed to entered recovery mode. n did the rest via console.

Yes I have and can still get to open recovery.
What could I try and do from there? I've tried with updates through this method the same way you put on custom firmware ( put the rom file in the open recovery updates folder).
So what do I need to do via console?

Still stuck with this one have tried stock sbf and custom roms all same problem BOOTLOOP have tried taking battery out then factory reset still same. Don't understand what wenderis means by "do the rest via console" ? So if any one out there can get my brick back to life you will be loved forever.

Unable to Restore Bionic Back to Factory Settings

My son rooted my bionic, installed Safestrap and Eclipse launcher. The phone was working great. I changed phones and wanted to give the Bionic to a friend but wanted to wipe it clean before doing so. I decided to do a factory reset from the system settings. (I've done this before with no problem but that was before the phone was rooted.) Now when I start up the phone, all I get is the screen that says SAFESTRAP: DISABLED. Starting in 10 seconds. Then I get the red circle with the white M but nothing happens. It just cycles between the red circle and the safestrap disabled screen. I've messed around with the menu on the safestrap disabled screen but can't figure out how to get the phone started again. I don't know what version of anything I had because I can't access settings. I've spent hours searching the forums and have tried various unbrick methods with RSD Lite but nothing has worked. I honestly don't know what I'm doing and am unfamiliar with some of the lingo. Can anyone point me in the right direction and give me step by step instructions on how to restore the phone back to factory settings. Thanks in advance!

It sounds like your son installed eclipse which is a custom ROM on slot 1. The safestrap menu once opened under boot options has a button that says stock ROM. Hit that and then hit activate and then boot. You will then be back on your stock ROM. It sounds like you erased the custom one when you factory reset which is why it won't boot in slot 1, its BC there's nothing there. Once you get back on your stock ROM just uninstall the superuser app, and as far as most people would know it would be just as before. No need to rsd lite back to completely original unless you are giving it back to the carrier. If you still want to do that I would need to know specifics about what android version you are on etc to further assist you. However I recommend just switching to stock and uninstalling superuser and safe strap.
Sent from my XT875 using xda premium

DanRyan85 said:
It sounds like your son installed eclipse which is a custom ROM on slot 1. The safestrap menu once opened under boot options has a button that says stock ROM. Hit that and then hit activate and then boot. You will then be back on your stock ROM. It sounds like you erased the custom one when you factory reset which is why it won't boot in slot 1, its BC there's nothing there. Once you get back on your stock ROM just uninstall the superuser app, and as far as most people would know it would be just as before. No need to rsd lite back to completely original unless you are giving it back to the carrier. If you still want to do that I would need to know specifics about what android version you are on etc to further assist you. However I recommend just switching to stock and uninstalling superuser and safe strap.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply.
When I go into Stock ROM from the Boot Options menu, it tells me it's Currently Active. If that's the case, how do I reboot the phone so I can get to the point where I can uninstall superuser and safe strap? Thanks.

If its already active and you have already tried rebooting then we may have a more serious problem. If you haven't hit reboot system then try that. If that doesn't work and year you've already done a factory data reset then I would say hit the restore button and see if your son made a backup. If there isn't one there then I would say you will have no choice but to learn to use RSd lite.
Sent from my XT875 using xda premium

That's because it flashed the stock boot image, the rooted settings stayed. You need to flash a diffrent boot image unroot then do factory reset. First time you did it you didn't do factory reset! Next time just reformat your sd card and you'll be fine! Good luck !
Sent from my HTC6435LVW using xda app-developers app

DanRyan85 said:
If its already active and you have already tried rebooting then we may have a more serious problem. If you haven't hit reboot system then try that. If that doesn't work and year you've already done a factory data reset then I would say hit the restore button and see if your son made a backup. If there isn't one there then I would say you will have no choice but to learn to use RSd lite.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
I tried rebooting the system through Safestrap menu. It rebooted back to the SAFESTRAP: DISABLED screen.
I found the backup file, hit restore and it said restore was successful. However, I'm still stuck at the SAFESTRAP: DISABLED screen. I did more research on the internet and this is what I did with RSd lite based on a youtube video I found on how to restore the bionic:
I downloaded the motorola drivers, file name: Motorola_End_User_Driver_Installation_5.9.0_32bit.msi
I downloaded RSd lite 5.7 (also tried RSd lite 6.4.1)
I downloaded cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip
I tried installing the motorola drivers but got the error message that the drivers couldn't load successfully because a newer version was installed. (I searched the internet for a later version of the motorola drivers to see what version I might have but couldn't find a version newer than 5.9.0).
So I moved to RSd light. I located the cdma_targa zip file, hit decompress only. Once done I hit Start and there are 24 steps. I get a fail at step 5 with the message: Failed flashing process. 5/24 oem fb_mode_set -> Phone returned FAIL. I tried with RSd lite 5.7 as well as 6.4.1 and it always failed at step 5. Not sure what to try next or why this is so difficult. The YouTube video seemed so straghtforward. Thanks.

Okay, just breathe. This is not unfixable but it is probably going to require more than a little patience and some research. There is a wealth of knowledge in the forums here at xda and the answer is almost certainly there there to find. Once you open the forums use the search all forums tab to search key words like you error message. I found this: http://forum.xda-developers.com/showthread.php?t=2242075
Like the member who chimed in on our convo said the answer seems to be with the boot image. However I've never had this specific problem before. So I'll look a bit later and check back in. Maybe another member will weigh in and maybe you'll find a piece of gold in the forum!
Sent from my XT875 using xda premium

You need to edit the .xml file and remove all of the getvar lines and then it will flash properly in RSD Lite.
You can also use fastboot to flash the partitions separately but given your level of understanding, I would recommend using RSD Lite with the edited .xml and avoiding the need for command line and multiple operations.
The full xml.zip will restore your device completely and you can start fresh and re root and try SafeStrap again.

In need of some help.

Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.

Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium

darknessrise1234 said:
Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.

DeVoe41 said:
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.
Click to expand...
Click to collapse
read this
http://forum.xda-developers.com/showthread.php?t=2226527

Make sure you have the adb drivers installed on your computer and I've noticed this phone is weird about chargers find one that works for data too. U will know cause if you have adb installed through myth tools and you reboot into fastboot mode then your computer will recognize it. Make sure the only thing in the firmware folder in myth tools is your .zip whatever stock att firmware you want. Then in myth tools install stock and make sure you type in the response 2 when it asks if you are in fastboot mode or normal. Fastboot is choice 2. I'm a flashaholic I've tried every rom in our development forum lol. I have bricked my AHD more times then anyone should this always worked for me. Try these things see if they help
Sent from my MB886 using xda app-developers app

Clean Flash
DeVoe41 said:
Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.
Click to expand...
Click to collapse
I have a suspicion that for some odd reason, as Mythtools probably should have taken care of this, that there are some lingering files and caches that would cause any rom to fail upon install. I just posted something about this earlier today.
Read my post on this thread:
http://forum.xda-developers.com/showthread.php?t=2394238
PM me with any questions or problems and click the Thanks button if I helped.

I'm sorry I forgot to update I was able to get the phone working just had to do it through command prompt forcing you to file . The issue I had was using safestrap to install a ROM which somehow killed root access and the bootloader was not unlocked so and pretty much bricked the phone.
Sent from my MB886 using xda app-developers app

For recent custom roms, you must use a CWM with an unlocked bootloader.

[Help] Atrix HD won't enter recovery mode no matter what!

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.