Develop Bugs

PLEASE HELP!! clockwork recovery won't boot to recovery

Not sure what i did...must have accidently hit something in ROM Manager.....
Phone boots up fine..but when i go to reboot into recovery my Splash screen flashed then just goes blank. After reflashing recovery the splash screen just starts flashing like crazy. I cannot get into recovery. Ive tried uninstalling and reinstalling rom manager, fixing permissions, reflashing the recovery but nothing seems to be working. I've tried finding an answer that works but i cannot find anything.

Update, i have the SLCD on my phone. I ended up rerooting the phone and flashing the additional package for the SLCD which seemed to correct the problem.
Hope this is helpful for anyone else who may have this problem.

I've been having problems with also, what is the "extra package" for SLCD?

http://jonsuh.com/2010/11/root-your-droid-incredible-how-to/
That link has the instructions. Alternatively you can use rom manager to flash a different recovery, meaning Aman-ra it works well with SLCD i have one. I hate to say this but i would strongly suggest not using Rom manager with SLCD until they have a fix with clockwork in a new build or they get the option to flash a differe CW recovery because when you open RM it tells you that you must install CW and when you accept it doest install it but its a version that does not play well with SLCD.
Ofcourse if I am wrong and anyone wants to interject I am new to this site and would'nt mind the the expertise

It's not a ROM Manager issue, and the fix for SLCD is pretty well documented on this and other forums. Problem really is what you're seeing in the news - fragmentation of the Android platform where you have multiple flavors running on multiple versions of hardware and no two are always the same - even in the same product lines.
Once you get Clockwork on, and the SLCD fix, ROM Manager works fine.

still having troubles
I have tried the method above as well as other methods of installation from the SD card, but the clockwork fix just goes blank once I select something and when I installed Amon_RA it completely froze up....Any suggestions?

captndisaster said:
I have tried the method above as well as other methods of installation from the SD card, but the clockwork fix just goes blank once I select something and when I installed Amon_RA it completely froze up....Any suggestions?
Click to expand...
Click to collapse
Use the trackball to select options, not the power button.

[Q] Gingerbread, recovery mode = FAIL

Hey guys!
I've tried to update my android 2.2 to gingerbread, both with the official update and the oxygen update, with the same result: my phone reboots, starts doing something - I get a green statusbar - and after about 1/4th of the bar it all ends up with a phone with a read exclamation mark and a red triangle.
The first time I got there, I though this was something that should happen, and left my phone around for two hours without anything happening.
I googled around and ended up doing a hard reset, which didn't change a thing.
I then tried to go into recovery mode from the boot meny, and end up with the exact same result.
So... what the hell is happening? Anyone got a clue? I would really appreciate some kind of sollution!

Its probably because you have a corrupted update file.
Try downloading it again.
If your branded to a certain carrier, then download the update for that carrier.

I've downloaded the update each time I've tried to make the update. I've tried with the oxygen ROM too, and tried loading recoverymode both from boot menu and clockworkmod. Nothing works. Amen...

So let me get this straight, you are trying to do OTA updates with a custom ROM + clockworkmod!?
It does not work like that. OTA updates are ONLY for 100% stock phones (ok, you can have Radio S-OFF, but no root). As you are using a custom ROM, why don't you just flash a Gingerbread based ROM instead of trying to mess around with OTAs, which obviously is impossible?

Uh, well, I have the standard ROM, but I did not know that it's impossible to install OTA updates when my phone's rooted. But it obviously doesn't work out
I've tried with the oxygen gingerbread release too, but same **** as I described in my original post happens. So what I've done:
- Install OTA update - failed
- Install oxygen-rom - failed
then, Hard reset +
- OTA update, without root - failed
- go into recovery mode from boot-menu - failed
hard reset + root +
- oxygen gingerbread - failed
- recovery mode from boot meny - failed
- recovery mode from ROM manager - failed
I really hoped that a hard reset would do the trick, but there you go...

Again, you cannot get any OTA because you have ClockworkMod.
Sent from my Desire HD using Tapatalk

So... How do I get any update if I can't install Oxygen either? (assuming Oxygen's ROM also qualify as OTA...)

Flash this ROM from CWM Recovery like any other ROM. Its Gingerbread with root, nothing else added.

Thanks!
But I'm still having serious problems getting into recoverymode, or even backing up my existing ROM. It seems whenever I do ANYTHING that requires my DHD to reboot, it ends up with the phone-with-red-eclamationmark-sign. No matter if I've done a hard reset either...

Holene said:
Thanks!
But I'm still having serious problems getting into recoverymode, or even backing up my existing ROM. It seems whenever I do ANYTHING that requires my DHD to reboot, it ends up with the phone-with-red-eclamationmark-sign. No matter if I've done a hard reset either...
Click to expand...
Click to collapse
The red exclamation mark is the stock recovery, so you dont have clockwork recovery. I would recommend starting from scratch installing clockwork then all should be good

Oh, nice to know But I used ROM manager to flash clockwork recovery (at least it said so).
When you say start form scratch, would that imply hard reset, root it, flash CWR and hopefully it will work?

Holene said:
Oh, nice to know But I used ROM manager to flash clockwork recovery (at least it said so).
When you say start form scratch, would that imply hard reset, root it, flash CWR and hopefully it will work?
Click to expand...
Click to collapse
Yes, you did S-off? As that would explain why clockwork didn't flash

Oh, well, uhm.
No.
Damn Thanks!

Help please - trouble with CWM / Recovery, new ROM

Hello all,
I'm sorry if this is the wrong place to post, but I thought I'd give it a try.
I own a Desire myself and the rooting / flashing a new ROM process was pretty easy so I thought I can help a friend out and put a custom ROM on his new Motorola Defy. Turns out I sucked at it. *ahem*
Right, the problem is as follows:
I got the brand new device, used SuperOneClick to root it, tried ROM Manager to install ClockworkMod CWM and it said Defy isnt supported in ROM Manager. So I google'd and it came up with this [german] (not allowed to post links), which basically gave me CWM.zip with an apk in it, which installed "System Recovery" and gave me the option to "Install System Recovery" and Reboot into Recovery - successfully bootet into CWM 2.5.1.8 , alright.
I did a nandroid backup and then wiped everything, selected the ROM on the sdcard to install MIUI 1.9.9 ROM, which worked fine. After it finished installing, I chose reboot system now.
Now what happens is:
I try to boot normally: I Only get the Motorola logo on screen and nothing ever happens
I boot into recovery like I used to know (Power + VolDown), I get a screen with a yellow exclamation mark and the android robot on it. Figured out that both volume keys take me to Android System Recovery Utility. I wiped everything again, that didn't help. I tried giving it the CWM.zip as an update.zip but it refuses that because it's apparently not properly signed. I can't do anything else in there. It also gives me a couple of errors "E: Can't moint CACHE:recovery/command" (/caller, /log)
Please, can anybody help me out? It seems I can't boot any ROM from it right now, nor do I know how to get CWM back in to at least even restore the nandroid backup (which I still have).
I would love to, at the end of the day, have a rooted device with CWM running and MIUI 1.9.9. If that doesn't work, at least can I restore the CWM backup somehow to have to stock ROM running?
I would really appreciate any help very much and realize I may be in over my head, it just seemed too easy on the Desire I previously used. Thanks a lot!

[Q] Stuck with no OS, no emmc access Epic 4g Touch

Hi all,
I'm new to trying to root the E4GT and I've gotten in a bit of a jam. I don't think I'm completely borked because I can still easily get the phone into download mode or Clockwork recovery, but I'm stuck on what to do next and I want to proceed carefully so I don't accidentally turn this into a hard brick.
Because I'm on Linux, not Windows, after reading up on rooting the E4GT I installed heimdall. It's not the most intuitive program in the world but I eventually worked out rooting it using "heimdall flash --kernel ~/path/to/zImage" where the "zImage" in question belonged to Zedomax v3 as linked from epic4gtouchroot.com. That seemed to work brilliantly as I was able to boot into what appeared to be a reset phone, now with a generic Android boot animation rather than the default Sprint advert, and I had the Superuser app.
From there, I decided to try Strongsteve's Odex blue and I booted into Clockwork. Without even thinking about it I wiped the factory data and cache partition, and then started looking into what I needed to do, only to learn that my external SD was going to be inaccessible from here so I had the .zip file in the wrong place. I proceeded to reboot my phone to set things right but I was shocked when the phone simply appeared to turn off after the (new, rooted) boot animation played. The phone then becomes unresponsive until the battery is pulled, at which point it becomes responsive again.
Because it boots the Samsung logo (with the yellow warning triangle) and part of the boot animation, I have plenty of time to get it into download mode or Clockwork, but I don't know what my next move is. I guess (based on a bad experience with trying to root a Kindle Fire) that this is still recoverable, though. Should I just flash a stock/stock rooted ROM? Reflashing the Zedomax kernel doesn't seem to work like it did before. Has anyone encountered this? Does anyone have a link to a recovery method that should be reliable in this situation? Thanks in advance and please remember LINUX -- i.e., no Odin.
[[ PS - I pretty much described the whole process above, but in case anyone was wondering, let me explicitly state I do not have a working nandroid backup. I only got Clockwork after rooting successfully, and I didn't think wipe data/cache was potentially a brick! :\ ]]
UPDATE: Solved! I was able to successfully flash the zImage from the stock rooted kernel here. Phone is working (and rooted) once again!

[Need help] Weird things happen when trying to install FXP's JB rom

Hi all,
I am new here and I don't know exactly where to post but I have been in a weird situation and really need help. I already did my homework trying to search for solution and it takes me all night long without success so please help me out!
My phone situation: lt18i, bootloader is unlocked, ClockWorkMod recovery installed. When trying to flash with custom kernel:
- Jelly Bean kernel, it said flashing is successful. However, after that I can no longer boot into ClockWorkMod recovery, although my phone's led is blue indicating that I am in fastboot mode. My guest is the recovery partition is wiped after I flash the custom kernel, so I tried to flash ClockWorkMod again. Then I got a failure, the terminal said "wrong range" (most of the time) and "the file size is too large" (some other times).
- Ice Screem Sandwich kernel, it also said that everything is ok. Then I flash ClockWorkMod recovery. This time it worked ok.
I really don't understand why ClockWorkMod recovery disappears everytime I try to flash a JB kernel, although the kernel itself contains CWM recovery I believe. And the wrong range message keeps appearing in terminal, I search around in the Internet but no result found!
So all my efforts to install JB were in vain. I am in a even more serious situation that I lost my backup and now I am stuck with the boot flash animation and my phone now is soft-bricked.
Does anyone experienced such situations? Any suggestion to help me get out of this situation will be greatly appreciated.

That's really weird
Read your full descriptive problem.......:crying:
THAT'S REALLY WEIRD....
DON'T know that this solution will work or not
try to install other JELLY BEAN KERNEL
i know a kernel but its for arc with 0% error fix(IF YOU KNOW WHAT IS THAT 0% PROBLEM if not then ignore)
svantesonCM10FXP136_boot
YOU CAN TRY THIS BUT DON'T BLAME IF SOMETHING MORE WEIRD OCCURS..:silly:
----------------------------------------------------------------------------------------------------------------------------------------------------
IF YOU THINK I HELPED THEN SHOW IT BY PRESSING THE THANKS ICON:good:

Reflash a stock ROM and start over, and you're backup should be on your SD card so don't think you will have lost that.