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.

Accidentally bricked my phone :( please help?

So here's what happened from the beginning:
I used Safestrap to try out ICS on this thing and got a backup of my original rom and everything went smooth. While on ICS (one of the CM9 nightly builds, 6/29 i think) i decided to go back to my unsafe system, the original gingerbread, it was my understanding that we were able to switch between the two with no problems. When i switched, i was in a bootloop so i tried to restore my backup which had magically disappeared. After that, i decided to try and go back to the original stuff through flashing the FXZ (VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml). got the idea and followed the instructions of a video on youtube by droidforums "HOW TO Unbrick Factory Reset Droid4 D4 via Flashing FXZ in Fastboot". now im stuck in bootloop and have no recovery to flash anything and i dont know what to do from here. anything i can do other than take it to a verizon store and play dumb? all i need is to get this thing working again, gingerbread, ICS or jellybean, idc which lol
thanks in advance

Random94 said:
So here's what happened from the beginning:
I used Safestrap to try out ICS on this thing and got a backup of my original rom and everything went smooth. While on ICS (one of the CM9 nightly builds, 6/29 i think) i decided to go back to my unsafe system, the original gingerbread, it was my understanding that we were able to switch between the two with no problems. When i switched, i was in a bootloop so i tried to restore my backup which had magically disappeared. After that, i decided to try and go back to the original stuff through flashing the FXZ (VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml). got the idea and followed the instructions of a video on youtube by droidforums "HOW TO Unbrick Factory Reset Droid4 D4 via Flashing FXZ in Fastboot". now im stuck in bootloop and have no recovery to flash anything and i dont know what to do from here. anything i can do other than take it to a verizon store and play dumb? all i need is to get this thing working again, gingerbread, ICS or jellybean, idc which lol
thanks in advance
Click to expand...
Click to collapse
I would try downloading the fastboot files again, from here,
http://sbf.droid-developers.org/cdma_maserati/VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml.zip
Then download Motorola USB drivers from here,
http://www.mymotocast.com/download/MDM?platform=windows
Finally, download RSDLite from here,
http://www.mediafire.com/?5mvfxv88twuvh34
Then, boot your droid 4 by holding the VOL DOWN + POWER briefly then release the POWER button and you should be on a black bootloader screen (NOTE: if it boots to the Moto symbol here, shut it down holding the buttons until it turns off then immediately release and hold them down again)
Scroll down to AP Fastboot using the VOL DOWN key then press VOL UP to select it
Once in this mode plug your phone into the usb on your computer and after windows installs drivers run rsdlite
RSDlite should detect your device and you can flash the fastboot file by browsing to it
It should take about 10 minutes or so, and you should have a factory phone again

While i was wating for this to download i decided to check out the recovery from that menu. i did a factory reset and rebooted and it booted up fine. i gues something on there was from ics and was screwing things over? Idk points is it worked lol. thanks so much for the reply though

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.

[Q] Boot lopp w/ AP, Plz help.

Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!

I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.

I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?

Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....

Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.

[Q] Custom Rom -> Tried to put in Stock. Now Soft Bricked [FIXED!]

I'm completely stumped on this. I'm new to Custom Roms.
So a long time (a little over year aprox) I bought an GT-N7000 from an at-the-time friend (no longer friends)
He factory reset and installed a custom rom (Paranoid Android) on it. (Such a nice gesture..)
Now, speed forth Christmas last year, I bought a Galaxy Note 3 for myself, and I then sold off the N7000 to my older brother.
Now my brother comes to me and tells me that his phone is acting weird.
I take a look and notice that the phone has apparently partitioned itself into several drives, making the phone run incredibly slow and he keeps getting an annotation going "There's way too little space left!"
Now, as I mentioned I'm new to custom roms and that kind of stuff, but my initial "brilliant" idea was to simply factory reset it, and install the Stock Rom on it.
I grabbed a Stock rom from Sammobile that had a country that at least was english in nature (UK) I unfortunately live in Denmark, and so therefor it was impossible to find a Stock rom that fits it.
I grabbed it, loaded it onto ODIN3 and went into Recovery Download Mode. And I started installing it. Everything went smoothly.
Then when the phone restarted it started boot looping.
I looked and searched everywhere for fixes. Problem was, looking at the first few fixes I've seen include links to .PIT files that are either dated or ancient in nature.
androidayos.com and android.gs both had a fix, but their links was either out dated or not helpful for my specific case.
And so I beseech thee oh mighty XDA Developers.
Have you a solution/help that might be what I need.
I've read that I should go into a recovery mode that allows me to look at the files. (Read that I could do so by holding the Home Button + Power button when it turned on. But such a function didn't seem to work on the N7000.)
I've also tried looking at installing Paranoid Android again, but that requires access into the Recovery Mode. Which I, again, do not have.

PIT files are dated because they never change. They have been the same since device manufacturing date.
So did you reset before odin install? Recovery mode is by pressing the power + vol up + home together.

nokiamodeln91 said:
PIT files are dated because they never change. They have been the same since device manufacturing date.
So did you reset before odin install? Recovery mode is by pressing the power + vol up + home together.
Click to expand...
Click to collapse
Well, I had to flash in phillz to actually get a recovery mode to work.
But I managed to do just that, and then whipe the caches and I could then get the stock rom flashed onto it.
Which then got the phone to work properly.
No failures to report yet.
So for the moment a full-on success story!