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.

Cannot Access CWM Recovery Mod

[SOLVED -- Read my last post]
Posting on forum was my last resource, but I've tried literately almost everything I can possible find.
I already bricked my phone and had to unbrick, do everything (update firmware etc) all over again.
I am at a point where I am afraid to do something new to my phone now without knowing what they are...
Please bare with me, I am not familiar with exactly what flashing is or whatnot, I just followed the instructions and got where I am....
K, recently I decided to wipe my phone CLEAN and update to new CyanogenMod 9 from factory mode.
So, I have Captivate, I897. It was ECLARE with 2.1 firmware.
I have updated to 2.3.5 (Gingerbread [I897UCKJ2]), Rooted.
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
I installed Clockwork mod (Free version).
My goal is to install CyanogenMod 9, and part of the process requires me to enter the CMW Recovery Mod.
I dont even know what this looks like, but all I know is whenever I boot my phone, after the AT&T logo animation it seems to go into this "messed up" screen, where as if my phone is broken. Stays there for 3 seconds and then continues to boot back to its OS.
In ROM manager, it says Flash ClockworkMod Recovery (You must have the clockworkmod recovery installed to flash and restore ROMs!)
Another option within ROM manager is, Reboot into Recovery (Boot into Recovery mode for manual management.), which if I do access it, it takes me back to that AT&T logo animation and that "messed up" screen again, but this time it stays there. Where all kinds of colored pixels are on my screen as if my screen is broken. It will only continue to boot back to my OS if I press power button or some sort.
Im guessing that's my Recovery Mod, which my phone for some reason cannot see?
So I tried "Download ROM (Upgrade to ROM Manager (premium) to access the full list of ROMs!", hoping this may cure that messed up screen effect, which I think is the Recovery Mod for all I know... When I click to install, it gives me Confirm Phone Models. None are my phone model for me to install.. (It only gives me Google Nexus S / Google Nexus S 4G / Samsung Epic4G / Samsung GalaxyS i9000).
Earlier, I was looking at this, http://forum.xda-developers.com/showthread.php?t=1127578
which is a way to fix recovery mod(?) But I have NO idea how to even install those files... Maybe not the .tar file but the other one.
Please help? Am I the only one experiencing this kind of problem? Couldnt find anywhere else on youtube / google / forum..
Thank you VERY much in advance, really appreciate it..
-Dan.

danroh said:
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
-Dan.
Click to expand...
Click to collapse
This is your likely problem right here. The Kernel that is installed during the rooting process and typically when you install custom roms is what is responsible for installing and therefor you being able to access the CWM recovery. Flashing back to the stock kernel likely messed things up for you.
http://forum.xda-developers.com/showthread.php?t=1300843
Now if you follow that link it will take you to several one click options for flashing your phone to stock gingerbread but with a kernel containing CWM. Also keep in mind that it is possible you could have wifi issues if you've had them in the past, but if your goal is to get to CM9 just ignore the wifi for the time it shouldn't be an isuse in the end.

Hey OP,
See this.... TRusselo's Flashing Guide
Sent from my SAMSUNG-SGH-I897 using xda premium

You need Gingerbread bootloaders.

Thanks guys! I figured out the problem and solved it!
Like you guys said, I didnt have the bootloader. The gingerbread I installed was the no bootloader version. After reinstalling to the one with bootloader, I was able to access the recovery mod and that "rainbow screen" glitch was no more.
Thank you!

Phone Won't Start. Endless Loop.

I've flashed CM 9.1 rom 2 weeks ago. Everything was perfect (well, ok camera app was a bit laggy). I installed it through CWM, like wiki says.
2 days ago, I was using phone as Navigation, and battery depleted to 0 (phone switched off). When I plugged it into a charger, battery charging animation was displayed, then phone switched off and so on (loop). Same situation is when I power on. CM logo endless loop.
Recovery doesn't start, download mode is working tho.
I checked different battery, same thing.
Is it software related problem ? Should I just flash phone again via ODIN or Heimdall?

I had something similar like this a few months ago because my nephew was pressing random buttons. I did indeed just reflash the phone again. Lucky for me I had a backup of my data so that fixed most of my problems.
Hope you figure it out,

Currently, I've flashed hardcore Kernel (CM wiki page) to flash CM9.1 rom.... it gives me Status 7 error (get.prop("ro.product.device")). Same with CM 10 Nightly.
Flashing Slim ICS gives me Status 0 error.
What should I do?

Hey just flash stock GB firmware via Odin then u r good to go...
Do post results
If my post helped, don't mind hitting THANKS

Yes it helped. Thanks.
Strange tho, stock 2.3.6 feels faster than CM9.1

Solved - Locked Boot Screen, Unable To Access Custom Recovery Image.

Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.

*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.

Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app

Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX

http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app

SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.

Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.

When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.

SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.

After restart device is bootlooped on mi.com logo

Hi,
Today my device was lagging and I restart it. Just after that I get the bootloop (showing MI.com logo). I can't open the recovery menu using the Power + Vol+ combination, but at least I could load FASTBOOT using Power + Vol-.
Using terminal command "fastboot reboot recovery" also doesn't help. I can't turn off the device as well - after some time showing me the logo device reboots again.
History - I have flashed my device ~1.5 year ago using OrangeFox + MIUI 11 raphael. The reason why I did it was my stock firmware didn't allow me to use NFC, there just was no option to enable it. After flashing everything was fine until today. Btw, device is unlocked. I am not sure what ROM version did use exactly because pretty much time passed already.
I spent a day googling for a solution, but didn't find anything.
What can be the reason? Is there a way to fix it?

If you haven't tried it yet, I'd suggest you flash your latest backup (if any) or flash the stock ROM again.

@TrulyPain no, I dont have any backup unfortunately.
Regarding the flashing stock ROM
1. Before I used OrangeFox to flash the device but now I cant boot recovery mode. Is there a safe way to do so?
2. Does only stock ROM fit? No custom?
Tried so many different approaches today. None of custom recoveries worked. I tried to use stock recovery - same result.
The only thing I didn't try is Mi Flash Pro stock ROM flash, but before that I wish to be sure I tried everything else.
Also, the repair specialist told me (remotely, he didn't check the device) that potentially it can be the memory hardware problem and advised me to visit Xiaomi official repair service. But.. it's pretty complicated for me currently.

romahaaa said:
Does only stock ROM fit? No custom?
Click to expand...
Click to collapse
I would recommend starting with the stock ROM as you can then more easily see if it is a hardware-related problem or not. Also, it sets a suitable environment for any custom ROM installed afterward. This, as many custom ROMs, don't contain all partitions and need some partitions to be written by the stock ROM, e.g., the "OEM" partition.
After you have installed stock ROM - if everything works fine - you can install any custom ROM of your choice following the recommended instructions.

We tried 2 difference ways to flash to phone using stock ROM, but no luck. Seems the problem was in the motherboard. Left it for repair, but.. doesn't mater already, as everything has lost. After that case I move to iPhone back - there would never happens this **** with data lost in unexpected cases.
Thanks for the help