Database Info

[RELEASE][06/01/2011] ClockworkMod Recovery - current version - 3.0.0.5

Hi all, I thought to open this thread to keep all users updated to all the new release of the ClockworkMod Recovery for our Desire.
Current version: 3.0.0.5
FakeFlash zip for S-ON users
recovery-clockwork-3.0.0.5-bravo.zip
Flashable image for S-OFF users
recovery-clockwork-3.0.0.5-bravo.img
MD5: 0bd2a55504dd70641feb9c9b3ba5b1da
SHA-1: 0b6e77dedd8b954817d7210bf77c55f38da82278
Old versions:
2.5.1.8 (.zip - .img)
2.5.1.2 (.zip - .img)
2.5.0.7 (.zip - .img)
Changelog:
2011-01-06
fix /sd-ext wipe
fix android secure formatting
Add the volume command for seeing the current recovery.fstab. Support crazy HTC chargemode.
Refactor nandroid so the availability of boot backup is determined automatically. Boot backups are also no longer assumes to be on raw partitions, as they may be on a VFAT partition or someting different, such as in the case of Nook.
3.0.0.4. Provide an error message if an Amend zip is provided.
readd ext2/ext3 format support.
fix executable bit on e2fsck
Support for ext2 and ext3 update-binary.
2010-12-15
fix no select button
Added options for an internal SD card to be handled by recovery.
Exable uses in BoardConfig.mk:
BOARD_HAS_SDCARD_INTERNAL := true
BOARD_SDCARD_DEVICE_INTERNAL := /dev/block/mmcblk3p1
Setting BOARD_SDCARD_DEVICE_SECONDARY to the same value as
BOARD_SDCARD_DEVICE_INTERNAL will allow the device to
"fall back" to the internal SD card for other actions.
recovery: Remove condition around get_root_mtd_partition
Refactor recovery's block device handling to work across variant hardware in a cleaner fashion.
Fix write_raw_image on mtd devices.
Fix graphics corruption on some devices. BML restore needs to unlock first.
fix up bmlutils some more
2010-11-12
Supress "warning: comparison between signed and unsigned integer expressions" in minui/resources.c and mtdutils/mtdutils.c
2010-11-11
implement bmlutils
fix up implementation of int get_partition_device
Modify apply_patch to fail if trying to patch mtd on non-mtd devices.
Warning: Don't make a backup with Amon_Ra's recovery and restore it with ClockworkMod Recovery and vice-versa, you may USB brick your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sources available here: https://github.com/CyanogenMod/android_bootable_recovery
All credits to koush for this recovery, I only compiled them!

reserved for me.

I used unrevoked to root my phone and that put clockwork on.
So how do I go about putting this on? Flash the .zip with clockwork or flash the image via fastboot?
Cheers

unie said:
I used unrevoked to root my phone and that put clockwork on.
So how do I go about putting this on? Flash the .zip with clockwork or flash the image via fastboot?
Cheers
Click to expand...
Click to collapse
Fastboot.
Remember to S-Off.

2 newer version of recovery mod in one day
hard to choose between them
tnx for updating bro

wow thx pal for this, great staff =]

So, does it work with bravo-recovery-v1.5.3-CustomMTD.zip from http://forum.xda-developers.com/showpost.php?p=8578368&postcount=1?

Narfx said:
So, does it work with bravo-recovery-v1.5.3-CustomMTD.zip from http://forum.xda-developers.com/showpost.php?p=8578368&postcount=1?
Click to expand...
Click to collapse
Me also this interests.

as we all see, a clockwork is a one step ahead

does this have SLCD support?

Works fine here
Sent from my Desire with Oxygen, @XDA App

unie said:
I used unrevoked to root my phone and that put clockwork on.
So how do I go about putting this on? Flash the .zip with clockwork or flash the image via fastboot?
Cheers
Click to expand...
Click to collapse
both methods is working...

I have rom manager prem installed won't it auto update the recovery?

How do I setup?
Good day to you all ... How will everyone?
I wonder which of the 2 files I download to install and if I flash normally files?
How do I setup?
Thank you!

Pajorve said:
Good day to you all ... How will everyone?
I wonder which of the 2 files I download to install and if I flash normally files?
How do I setup?
Thank you!
Click to expand...
Click to collapse
as i see you are s-off so you can't use fake flash method,download the img file (the second one) so u just have to burn the recovery with unrevoked flasher tool, or the android flasher tool both are good and working.
soz i don't have time to search links, i think if u go a little down by pages u will find the android flasher.

Go to your "old" ClockworkRecovery and apply Update.zip
Worked fine for me!

goodmorning to you all.i've tried update through recovery but it didn't do it.it says 2.5.1.2 then the menu for reboot and after reboot still 2.5.0.7

konn4312 said:
goodmorning to you all.i've tried update through recovery but it didn't do it.it says 2.5.1.2 then the menu for reboot and after reboot still 2.5.0.7
Click to expand...
Click to collapse
I get this too. When I'm actually in recovery the version number is 2.5.1.2, but ROM Manager reports the version number as 2.5.0.7. ROM Manager also says the latest version is still 2.5.0.7. I guess it's ROM Manager that's wrong, rather than the actual recovery.

help
i did a backup using nandroid on this new recovery and now im in a bootloop...need assistance...

Why did you alter the source before you built it? You added your own name to the recovery screen, while I don't see that you changed or added any functionality of the recovery. Your changelog is identical to the github logs.

[ROOT] [KERNEL] [RECOVERY] - Root / Voodoo Lagfix / CWM Recovery

Hi all
Whipped this up for a friend. Thought we'd be nice and share
These packages will work on any current sw version for the Charge.
Please find below kernel and recovery packages hacked for the following:
permanent adb root
installs Superuser and su binary automatically on boot
includes Voodoo ext4 lagfix - CREDIT TO SUPERCURIO! http://project-voodoo.org/lagfix
lowmemorykiller tweaks
sdcard readahead cache speed tweak
If you are using Odin to flash, simply flash the below package. If you are using Heimdall, remove the zImage file from the below package and flash it.
After flashing the first time, you will hear a voice from the phone telling you what is occurring. The conversion to ext4 will take a few minutes. BE PATIENT. Once it boots, Superuser should be installed, and your phone's filesystem will be converted from rfs to ext4. To disable Voodoo lagfix and convert back to rfs, simply create a file on your sdcard inside the Voodoo folder, named "disable-lagfix". Then reboot your phone and listen for the voices again. This will also take a few minutes.
Please familiarize yourself with using Odin or Heimdall and have backup images on-hand if you are going to use this kernel. If you screw up, you will need them
I DO NOT have a Charge, these files have been tested by other users. As always I assume absolutely NO liability for anything that happens if you use this kernel. Phone blows up? It's on you to fix it
If you find this software helpful please click the "Thanks" or the "Donate" button. Either is fine by me. If you would like to investigate the changes that were made, please feel free to find them here, and here.
Enjoy.
EDIT
Uploaded 2nd version
EDIT
Uploaded 3rd version
changed the install scripts around
should copy files more efficiently
fix file ownership and permissions
UNTESTED!
EDIT
Uploaded 4th version
Confirmed root from independent user!
rewrote install process to preserve file path and permissions
will look into the bootanimation graphics issue
http://dl.dropbox.com/u/14764513/VoodooChargeKernel4.tar.md5
EDIT
Uploaded additional recovery file
Flashes custom version of ClockworkMod recovery 3.x
Recovery includes Voodoo specific options for enabling/disabling Voodoo lagfix
Flash with Odin or Heimdall just like the kernel files
HAS BEEN LIGHTLY TESTED! USE CAUTION AND HAVE A BACKUP!
if you do not have root:
* check adb shell and see if you get a '#' prompt. If so, you *have* root on adb, and you may install whatever you want in /system
* check to see if Superuser app is installed
* check to see if /system/xbin/su exists on your phone.
If you have problems, please post the results of those checks. Thanks.

LLGW. Headed to bed now but first thing in the morning, I wondering what I'm doing

Thanks jt!!!! Can't wait to flash this once my charge comes in the mail.
Sent from my SCH-I500 using XDA App

Ok, somebody use this to system dump ED2.
And, uh, is there matching Voodoo clockwork?

s44 said:
Ok, somebody use this to system dump ED2.
Click to expand...
Click to collapse
please
And, uh, is there matching Voodoo clockwork?
Click to expand...
Click to collapse
probably not

What verison of odin should I use? I just flashed this and it failed.

using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1

The kernel flash was successful, and the filesystem conversion took about 8 minutes to run. However, I was not rooted when the phone booted back up. Here is what I did, let me know if I missed a step:
Start on rooted ED1
Accept ED2 OTA
Lose Root
Flash new kernel using ODIN
After ~10 minutes, phone boots successfully, but I do not have root.

asenduk said:
using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1
Click to expand...
Click to collapse
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.

Where's my wifi? Anyone else facing an error when attempting to start wifi?

Yeah it looks like it killed wifi. I also am not rooted.

So if I flash back to rooted ED1 will it wipe my data?

azhockey said:
So if I flash back to rooted ED1 will it wipe my data?
Click to expand...
Click to collapse
I just reversed the filesystem changes and then flashed back to ED1. My data appears to be intact.

moondrius said:
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.
Click to expand...
Click to collapse
had to rename the file to .tar.md5 now its working..

asenduk said:
had to rename the file to .tar.md5 now its working..
Click to expand...
Click to collapse
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?

Updated OP with a new version. Anyone who has flashed the original version, please check adb shell and see if you get a '#' prompt. If you do, then you're technically rooted

NotATreoFan said:
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?
Click to expand...
Click to collapse
Superuser was installed but root was lost... Trying the updated version... On a positive note Quadrant is great! 1400-1550 avg
EDIT: wifi fixed with v2 but still no root.. will try from scratch and report back
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Everything has worked for me. Thank you.
Sent from my ADR6400L using XDA Premium App

yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin

devanmc said:
yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin
Click to expand...
Click to collapse
Click PDA and select the file then just hit start

[Q] "Install Updates" not appearing in recovery menu

First off, I tried to add the 3e recovery by replacing the Recovery file in /system/bin.
I couldn't find a recovery file in there..which I found to be pretty odd.. but I placed the 3e recovery file in there anyway.
I rebooted into recovery and it brought me to the blue recovery menu and it doesn't have the "Install updates" option.
Help!

DLXII said:
First off, I tried to add the 3e recovery by replacing the Recovery file in /system/bin.
I couldn't find a recovery file in there..which I found to be pretty odd.. but I placed the 3e recovery file in there anyway.
I rebooted into recovery and it brought me to the blue recovery menu and it doesn't have the "Install updates" option.
Help!
Click to expand...
Click to collapse
Did you remember to change the permissions for the recovery file?
What was done to your phone prior to your attempt to install 3e? And try selecting "reinstall packages" (first option in blue CWM) to boot into green CWM...what are you trying to do exactly? B/c I don't recall an install updates option in CWM.

oops - I meant to say it didn't have the "reinstall packages" option in the menu. Hm.. I think I should use Root Explorer. Currently I'm using Super Manager but it has no option to change permissions, that I could find.

DLXII said:
oops - I meant to say it didn't have the "reinstall packages" option in the menu. Hm.. I think I should use Root Explorer. Currently I'm using Super Manager but it has no option to change permissions, that I could find.
Click to expand...
Click to collapse
Than that must be your problem, the permissions have to be set, Root Explorer is WELL worth the money. Once you get it the permissions should all be good just uncheck the group/write box, then try booting into recovery and reinstalling packs

Hm.. so I bought Root Explorer, changed the permissions but it's still doing the same thing. Am I doing something wrong?
Btw I found a recovery file, but it's not in /bin. It has a different date on it, and it says rwxr-xr-x on it.

DLXII said:
Hm.. so I bought Root Explorer, changed the permissions but it's still doing the same thing. Am I doing something wrong?
Btw I found a recovery file, but it's not in /bin. It has a different date on it, and it says rwxr-xr-x on it.
Click to expand...
Click to collapse
I think those permissions are what the original recovery is set to (and what the 3e recovery needs to be set to) what size is the file? If that is the original, rename it to something like recovery.orig

It is 404.77K in size. Should I move this to bin?

DLXII said:
It is 404.77K in size. Should I move this to bin?
Click to expand...
Click to collapse
No, I'm pretty sure that's the original cuz the 3e recovery file I extracted from the zip when I did 3e is 306.64k and right outta the zip the 3e recovery permissions should be --xrwxr-x which you need to change to match the original.
So here's what I would do, rename the file in question to recovery.orig.
Next I would start over, find the 3e recovery zip and extract it.
Go to extracted and find the recovery file(306.64k, --xrwxr-x) from that zip and copy it.
Scroll up to the parent folder (..) press till it goes away basically.
Find System/Bin and scroll down to a recovery file if any is in there. (you can either delete it or rename)
Make sure you hit the mount button at the top.
Hit paste, and change the permissions of that recovery file to the correct format and see if that works for you.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Permissions should look like this, disregard the "radiooptions."
Sent from my B.A. Infuse 4G

I followed everything you did, but I still bumped into this. Maybe the 3e recovery file I downloaded could be corrupted?

Ok, it's not applying the 3e it looks like, one more thing, you said the original recovery was not in system/bin(didn't catch that on your last post),you should probably put the recovery.orig file in the system/bin location with the new 3e recovery file, not sure if it will help. It's just weird that reinstall packages is not showing up.

I went ahead and did that, but for some reason the original recovery (renamed recovery.orig) isn't renamed, like as if it never saved any changes that I did.
Anyways, I renamed it and added it to system/bin along with the 3e recovery file and set the permissions correctly. Both have the same permissions, actually.
I booted into clockwork and it's still the same screen.

Ya they should have the same permissions, well damn, I've troubleshot every way I knew how...
Here is a LINK for an ODIN back to stock that will put you back to stock but give you root and modded 3e, since apparently your phone is being uber difficult. Just follow the instructions including the samsung kies drivers (download Kies here)
This is what I use whenever I have problems and it works for me every time

Thank you a lot for your patience and your help! I really appreciate it. I'll try the link out. Hopefully it'll work on a rogers phone..

DLXII said:
Thank you a lot for your patience and your help! I really appreciate it. I'll try the link out. Hopefully it'll work on a rogers phone..
Click to expand...
Click to collapse
No problem, I've been in your shoes, trust me, and I wasn't aware you were on a rogers infuse, so you rooted using THIS method? I'm not sure if 3e is the same for ATT and Rogers, but I know rooting is different along with many other things. The link I gave you might not work on rogers infuses, I wouldn't want you to brick your phone.

Yea i used that method. Hm.. I guess I'll just lay low with rooting until I find a solution. Thanks!

Well it's late here, but maybe tomorrow someone with more Rogers Infuse expertise will chime in, sorry, I know the ATT infuse pretty well just not Rogers
If I run across anything useful, I'll post it here

THIS link should solve your issues, specifically for Rogers.

[Q] Root or restore after Flash?

I did the wrong thing and assumed my phone was still rooted after using t-mobile's upgrade from froyo to gingerbread.
I flashed my phone and now I am stuck on the manual mode screen. I assume (oh boy) I cannot place a custom rom since my phone wasn't rooted and therefore doesn't have permission to write to the phone. (I can't flash bootloaders)
At this point my data on phone is trashed I am sure, but I do have the contents of my sd card intact. I didn't backup before I started - hijole! I know.
I am not sure if I can use Super one click to root and continue to install a custom rom, or I should go back to base line and restore to original. Problem is I don't know how to goto the original at this point, and I don't know if super one click will work with my phone at its current state.... Argh! Will post pic of screen when I go to lunch today... Thought i had it with me on my iPhone. I assume to much!

Can you be more specific on the manual mode screen and what it looks like? Just to clarify, when you flashed from Froyo to GB (using Kies Mini, I assume) you did lose root. However, that does not prevent you from flashing a custom ROM. You can use ODIN or Heimdall to flash a ROM, then use one of those again to flash a kernel with root, with CWM, with voodoo lagfix, all of the above, or use SuperOneClick (the latest) to root it.
I'm guessing you might be able to get into download mode which means you could ODIN RaverX3X's 2.3.6 Stock (http://forum.xda-developers.com/showthread.php?t=1353176) which is the Kies Mini official update just repackaged for ODIN. That will get you onto stock 2.3.6. From there you have options

I am supplying a pic of the "Manual Mode" I was referring to, and yes I did originally use Kies to upgrade from Froyo to GB. Again thanks for the info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So it won't show since I am new to this forum
NEVERMIND, found the upload feature in this forum

djlalorocks said:
So it won't show since I am new to this forum
NEVERMIND, found the upload feature in this forum
Click to expand...
Click to collapse
Sweet, so you have it working?

I think he says is stuck on that screen.
Do a battery pull on your device to turn it off, then put it back in. To put it into download mode for odin, hold volume up+down while plugging your phone into your pc. Then use odin to flash.
Sent from my SGH-T959V using XDA App

The problem he initially had is the rainbow screen and, although he can get into download mode, he's been unable to get his computer to see the phone. Thus he couldn't use ODIN to re-flash a good ROM.
djlalorocks, can you verify the state of the phone now? The screenshot you gave, by the way, is the CWM recovery screen. If we can get a good CWM-based ROM onto your SD card then you could flash from there.
Do you have an SD card reader for your computer you can use? I know the phone's not working in mass storage so that option is out.
Edit: My apologies; I went back and re-read what you wrote. When I saw that you found the upload feature I thought you meant you got a ROM to upload to the phone. I didn't realize you meant the picture of the screen. I'm slow sometimes

Haven't had a chance to work on it... I am on a mac, and yes I can place files onto a sd. My windows computer is having usb driver issues.

djlalorocks said:
Haven't had a chance to work on it... I am on a mac, and yes I can place files onto a sd. My windows computer is having usb driver issues.
Click to expand...
Click to collapse
Heimdall (open source alternative to ODIN) works on the MAC, I believe. Regardless, if you can download Raver's Kj6-Rom-CWM-Offical-GB-2.3.6, put it on the SD card, go into the recovery screen (the one where you made the screen shot), use the volume down key to scroll to "install zip from sdcard", press the power button to select it, then select "choose zip from sdcard", scroll to where you put the file mentioned above, select it with the power button, then scroll to "Yes - Install sgs4g-OfficialGB2.3.6.zip" and select it.

Cannot install stable CM10.2

My capasitive back, home and recent apps buttons has stopped working so I would like to have the on screen buttons as I do on my Nexus 10.
I tried to root the device to be able to modify the /system/build.props file. I used the superboot method but that din't work as I have S-ON. I then continued trying to install CM 10.2, and in the process, when installing CWM recovery, that asked If I wanted to root and I did. I then booted back in to the stock ROM now with root but after changing the build.props file it just reverted after reboot. I then continued to flash the CM10.2 and gapps for 4.3, but the device fails to boot... Now I have reverted to backup and use the button savior, but I don't like it...
I suspect that trying to flash this superboot messed up something... ? On one of the start up screens I have a disclaimer in red about HTC development software which came up after I tried to flash that...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anybody help me?

Having root does not grant you automatically rights to modify system files. For altering build.prop you should have mount /system partition in R/W mode before trying to edit the file. Even if you have root, /system is read only so you cannot save changes. You could mount system as R/W either by ADB commands issuing the following from command prompt:
su
adb shell mount -o rw, remount /system
Or by mounting system R/W from the root file Explorer you're using
Sent from nowhere over the air...

I used root explorer to alter the file, and before edit i clicked the mount r+w button. I read somewhere that on-screen buttons does not work on HTC sense anyways, so I may have to install CM or an other rom... I tried to flash just the CM10.2 an not the gapps now, but it fails to boot. The HTC splash screen comes up, the screen goes black, the splash comes, goes black, and so it goes...

I forgot to flash the boot.img... inside the zip

buestad said:
I forgot to flash the boot.img... inside the zip
Click to expand...
Click to collapse
Although this is for another HTC model, the basic idea should get you started again.
http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/

I Guess that when i tried the superboot, that did something to my kernel. Inside the .bat file it actually flashes the boot (isn't that the kernel?)
Cyanogenmod also has a note in the install procedure which I initialy didn't do:
Note:
This device, if unlocked with HTCDev Unlock, must have its kernel flashed via fastboot. Extract boot.img from the CyanogenMod .zip package and flash it from the bootloader with: fastboot flash boot boot.img
Click to expand...
Click to collapse
So I flashed the boot.img inside the Cyanogenmod .zip first, than I wiped and installed the Cyanogenmod .zip from the CWM recovery. I ended up using the M7 snapshot of CM11, and that worked! I then flashed gapps for Android 4.4.
After everything was up and running I edited the /system/build.props using root explorer (I mounted /system as r+w inside root explorer) adding the line qemu.hw.mainkeys=0, rebooted and got the softkeys!

So what happens if you flash TWRP as the link says?

808phone said:
So what happens if you flash TWRP as the link says?
Click to expand...
Click to collapse
I din't use TWRP. I used CWM Touch 6.0.4.8.
I probably could just flashed the boot.img after the device didn't boot, but I reverted to backup, and started over and started with the boot flash...

buestad said:
I din't use TWRP. I used CWM Touch 6.0.4.8.
I probably could just flashed the boot.img after the device didn't boot, but I reverted to backup, and started over and started with the boot flash...
Click to expand...
Click to collapse
Can you get to the boot loader menu?
You can still flash TWRP on there and follow the instructions. If you really want CWM afterwards, simply flash CWM back on. I would try the link since it is talking about stopping your boot loop.

808phone said:
Can you get to the boot loader menu?
You can still flash TWRP on there and follow the instructions. If you really want CWM afterwards, simply flash CWM back on. I would try the link since it is talking about stopping your boot loop.
Click to expand...
Click to collapse
As I said: I'm OK! Flashing the boot.img from inside the zip did the trick. Everything is working like a charm now.

buestad said:
As I said: I'm OK! Flashing the boot.img from inside the zip did the trick. Everything is working like a charm now.
Click to expand...
Click to collapse
Oh OK! Great you got it going.