Related
Grab it here:
General: http://koush.tandtgaming.com/recoveries/
Direct Link: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.4-inc.img
Use unrEVOked v3.1 to flash custom recoveries (at your own risk, of course)
1) Download
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.4-inc.img
2) DO NOT PLUG IN YOUR PHONE
3) Run unrEVOked v3.1
4) Under FILE choose CUSTOM RECOVERY
5) Point to the img file
6) Plug in your phone
Updated, no issues. Thanks!
Thanks. I updated without issue.
is it better than the old?
Sent from my Incredible using XDA App
jdkoreclipse said:
is it better than the old?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Yes.. it's 0.0.0.3 times better than the old!
If you rooted with unrevoked 3.0 can you just use that with this image?
Sent from my Droid Incredible using the XDA App
Flashed to 2.5.0.4 no problem. But ROM Manager still indicates 2.5.0.1 is installed.
So how do I get ROM Manager to indicate the right recovery version?
UPDATE: Just after I posted this...I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
i don't really see a point in updating since it already works for me now...
rom manager reports the older version for me, but booting into recovery it is reporting the newest .4 version
Lexus One said:
Flashed to 2.5.0.4 no problem. But ROM Manager still indicates 2.5.0.1 is installed.
So how do I get ROM Manager to indicate the right recovery version?
UPDATE: Just after I posted this...I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
Click to expand...
Click to collapse
ROM Manager cannot flash recovery because NAND is still locked. Only through the unrevoked tool does NAND temporarily unlock in order to flash clockwork. So if you followed the steps correctly using the unrevoked tool then you have the correct version. Booting into recovery (I think you can't boot through ROM Manager, boot manually or via boot loader) should show the updated version.
Lexus One said:
I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
Click to expand...
Click to collapse
Boot into recovery via ROM Manager. Note the version. Then boot into recovery "manually" (hold volume down while powering on). Note the version again. Notice anything different?
elborak said:
Boot into recovery via ROM Manager. Note the version. Then boot into recovery "manually" (hold volume down while powering on). Note the version again. Notice anything different?
Click to expand...
Click to collapse
recovery by ROM Manager I get 2.5.0.1
recovery by vdown & Pon I get 2.5.0.4
Thanks, now I'm confused even more. Why are they different? And when I go back into ROM Manager it still reports 2.5.0.1. So my original question still stands: How do I get ROM Manager to display the correct version of recovery which is really 2.5.0.4? Even more...why does the recovery manager report 2.5.0.1 when booting into recovery via ROM Manager? This is reallyyyy strange!
I answered your question two posts back...
s197 said:
I answered your question two posts back...
Click to expand...
Click to collapse
Thanks for responding. I understand. But that doesn't answer my question about how to get ROM Manager to report the correct version. Do you know the answer to this?
What is even more confusing is when I boot into ClockworkMod recovery from the ROM Manager and the version of ClockworkMod Recovery is reported on screen as 2.5.0.1 when it is really 2.5.0.4....this just blows me away! It is like ROM Manager is substituting its own version number into the newer version of recovery.
Lexus One said:
Thanks for responding. I understand. But that doesn't answer my question about how to get ROM Manager to report the correct version. Do you know the answer to this?
What is even more confusing is when I boot into ClockworkMod recovery from the ROM Manager and the version of ClockworkMod Recovery is reported on screen as 2.5.0.1 when it is really 2.5.0.4....this just blows me away! It is like ROM Manager is substituting its own version number into the newer version of recovery.
Click to expand...
Click to collapse
If i understand this correctly: The version that ROM Manager reports and boots into is actually a virtual version. This is because, due to the fact that NAND isn't unlocked yet ROM manager can't actually write to it, So when it is "flashing the recovery" it really is only flashing a "virtual recovery". This is why you could on some phones have an older version of recovery flashed and ROM manager would report a newer version that is available.
In short to answer your question, you can't get ROM manager to report the newer version until rom manager has that newer version in it's list, which it currently does not. And even when it is in the list it makes no difference anyway, because unless you boot into recovery using the power button and volume button, the recovery that you boot into will be a virtual one anyway.... so it really makes no difference what ROM Manager is reporting.
And if i am incorrect in my understanding then, disregard all of this but i remember another post with all this in it.
obsidianblackhawk said:
<snip> And if i am incorrect in my understanding then, disregard all of this but i remember another post with all this in it.
Click to expand...
Click to collapse
Thanks. I appreciate your feedback on this. It would explain why I am seeing a different version for the ROM Manager. What I still don't understand is why ROM Manager misleads you into thinking you are booting to the recovery partition. I mean, why even have an option in the program to "Reboot into Recovery" if you are really NOT booting into the recovery partition, but rather a virtual recovery. So, what would happen if you tried to use the virtual recovery as opposed to the real recovery (which in this case is a different version)? Anyone know, or have tried it?
Lexus One said:
Thanks. I appreciate your feedback on this. It would explain why I am seeing a different version for the ROM Manager. What I still don't understand is why ROM Manager misleads you into thinking you are booting to the recovery partition. I mean, why even have an option in the program to "Reboot into Recovery" if you are really NOT booting into the recovery partition, but rather a virtual recovery. So, what would happen if you tried to use the virtual recovery as opposed to the real recovery (which in this case is a different version)? Anyone know, or have tried it?
Click to expand...
Click to collapse
other than flashing a new recovery, the recovery that rom manager boots into works exactly the same as the "real one" in fact i don;t do it the "hard way" any more.
This is probably a dumb question but do I open the img file after I plug in the phone?
Lexus One said:
how to get ROM Manager to report the correct version.
Click to expand...
Click to collapse
Easiest way is this:
1) Uninstall ROM Manager.
2) Reinstall ROM Manager.
ROM Manager will now display no version, as opposed to the wrong version.
And then...
Never again use the "Flash ClockworkMod Recovery" command in ROM Manager. If you want to update recovery, use the unrevoked flasher with the custom recovery option.
Changes?...
We all know this is Koush's Work But Just Figured I Would Post It Up Here in case anyone needs it............
Thank you. Is there anyway to flash through Rom Manager
Sent from my Nexus S using Tapatalk
Zehlek said:
Thank you. Is there anyway to flash through Rom Manager
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
yea it should b the first option in the menu
aam6906 said:
yea it should b the first option in the menu
Click to expand...
Click to collapse
I flashed it, but now I am unable to boot into recovery. It takes me to the bootloader instead.
The only way I can get back into recovery is to flash and older version of CWM. Is anyone else having this issue?
Same problem here, with i9020.
i've a german nexus s (.23) it works very well!
RickROM said:
I flashed it, but now I am unable to boot into recovery. It takes me to the bootloader instead.
The only way I can get back into recovery is to flash and older version of CWM. Is anyone else having this issue?
Click to expand...
Click to collapse
I had that problem and I just flashed it a second time in rom manager and it works
Sent from my Nexus S using Tapatalk
Zehlek said:
I had that problem and I just flashed it a second time in rom manager and it works
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I flashed it multiple times in ROM Manager, and I could never get it to work. I will try again later.
Fix permissions then reboot, I had the same issue and that fixed it
Sent from my Nexus S using XDA Premium App
Im having the same issue can't boot into recovery now
Where can we find the changelog?
Darrien13 said:
Im having the same issue can't boot into recovery now
Click to expand...
Click to collapse
I have the same proble. I have to flash back to CWM 3.0.0.0 to able to go to recovery mode. I'm not sure whether it's becuase I rooted my wiht this methode "Root & custom recovery WITHOUT oem unlock & wipe ".
Any suggestion? Or just stay with CMW 3.0.0.0?
You can try this one. In the same forum. http://forum.xda-developers.com/showthread.php?t=988686
yup it killed my recovery mode too. reverting back!
brrip said:
yup it killed my recovery mode too. reverting back!
Click to expand...
Click to collapse
It also killed my recovery.
This killed my recovery too. I did as Suprakarma suggested and all is well.
From within RomManager, run the fix permissions script.
(This had a problem on my device, it appears it doesn't like the BusyBox that Titanium Backup installed, so I had to install a new copy from the market).
Once that script's finished, reboot, then reinstall recovery from Rom Manager. Boot into recovery.
Hope that helps.
nop working i fix permition and flash recovery and stell same no working
Sent from my Nexus S using XDA Premium App
Just out of curiousity, can anyone confirm if this recovery works on the i9023 or i9020a?
Sent from my Nexus S using Tapatalk
I am back on 3.0.0.5 after trying to fix permissions. I will try again later.
we can always use an extra mirror
some times Koush website goes down for long period of times
HTC Pushed an update to my HTC One Dev Ed tonight..
1.29.1540.16
When it tries to flash the update it just goes into TWRP recovery. No other actions.
I then drilled down to the directory that it downloaded to /data/media/downloads and tried to flash with TWRP.. no dice.
Here is the update.. but honestly I don't know what it does.
any Idea on what is preventing the flash?
deligator said:
HTC Pushed an update to my HTC One Dev Ed tonight..
1.29.1540.16
When it tries to flash the update it just goes into TWRP recovery. No other actions.
I then drilled down to the directory that it downloaded to /data/media/downloads and tried to flash with TWRP.. no dice.
Here is the update.. but honestly I don't know what it does.
any Idea on what is preventing the flash?
Click to expand...
Click to collapse
It only work on stock recovery, not on any custom recovery like TWRP or CMW.
lucky76 said:
It only work on stock recovery, not on any custom recovery like TWRP or CMW.
Click to expand...
Click to collapse
any workaround? ... other than going back to stock recovery.
deligator said:
any workaround? ... other than going back to stock recovery.
Click to expand...
Click to collapse
You must go back to stock recovery in order for the update to successfully flash on your device.
You don't need the update from HTC, just go and flash the latest revolution 10.2 rom, it is running 4.2.2 and it has some nice performance tweaks. And it isn't modified so it's running sense 5.
Sent from my HTC One using xda premium
deligator said:
any workaround? ... other than going back to stock recovery.
Click to expand...
Click to collapse
jlevy73 said:
You must go back to stock recovery in order for the update to successfully flash on your device.
Click to expand...
Click to collapse
How to do you go back to a stock recovery? Been down that road and it still didn't update.
akk60 said:
You don't need the update from HTC, just go and flash the latest revolution 10.2 rom, it is running 4.2.2 and it has some nice performance tweaks. And it isn't modified so it's running sense 5.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
For some of us, going to a different ROM is not a viable choice, and frankly a solution to load a different ROM does not answer the original question.
Hi I have the same problem here.
When I try to install stock 4.2.2, the phone reboot & automatically enter TWRP & thus stock update was unable to run.
kennfebruary said:
Hi I have the same problem here.
When I try to install stock 4.2.2, the phone reboot & automatically enter TWRP & thus stock update was unable to run.
Click to expand...
Click to collapse
None of the HTC direct updates will work while TWRP is installed.
you will have to
Fastboot flash (stock recovery .img)
then the updated from HTC works with no problems. pst if you can't find the img
Hi guys I downloaded CM 11 from cyanogenmod.org for the Atrix HD and when I try to download it I get the error ''Status 7'' with CWM Recovery. Have you guys been able to install it with the file from the web site?? Please help :crying:
Are you running the latest recovery?
Phil recovery iss more up to date then the cwm itself
audit13 said:
Are you running the latest recovery?
Click to expand...
Click to collapse
Yes I am running cwm recovery 6.04.4e
SVLAN said:
Phil recovery iss more up to date then the cwm itself
Click to expand...
Click to collapse
How do I replace CWM recovery for Phil recovery?? Any guide??
Download and flash in recovery
Sent from my MB886 using XDA Premium 4 mobile app
Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=2302599
penser
audit13 said:
Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
Like I mention in every one of these threads, Status 7 is, at least 99% of the time, a bad download. Redownload and verify the MD5 checksum.
The MD5 for the official nightly is "513639551c586888db38bc9b17c7dab2". Use this program to verify the MD5 checksum.
helldogg75 said:
Download and flash in recovery
Sent from my MB886 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you. I just flashed that recovery and it worked.
I'm having the same problem with every single 4.4 and 4.4.x rom. I've tried removing the lines of code method already, running 6.0.2.8 cwm
ph3dia said:
I'm having the same problem with every single 4.4 and 4.4.x rom. I've tried removing the lines of code method already, running 6.0.2.8 cwm
Click to expand...
Click to collapse
4.4 needs the latest CWM to install. Try using Philz Touch Recovery or install the latest img from the Clockwork website.
I don't know if any of you guys solved your issues but you need to download cm11 onto external SD card then download philz touch version of cwm also on ESD card. Flash philz touch in your already existing cwm whatever version that may be. I forgot if it will boot back into recovery automatically but get back into recovery. If you are soft bricked get back in recovery by holding the power and vol up button I think and just flash rom as normal wipe data/cache/dalvik etc. That's how fixed my status 7 and flashed OSE 4.4.2 and loving it. Hope I helped.
Black_halo said:
I don't know if any of you guys solved your issues but you need to download cm11 onto external SD card then download philz touch version of cwm also on ESD card. Flash philz touch in your already existing cwm whatever version that may be. I forgot if it will boot back into recovery automatically but get back into recovery. If you are soft bricked get back in recovery by holding the power and vol up button I think and just flash rom as normal wipe data/cache/dalvik etc. That's how fixed my status 7 and flashed OSE 4.4.2 and loving it. Hope I helped.
Click to expand...
Click to collapse
So I was able to update my recovery but now every single rom that I try to flash ends up stuck at the motorola logo. I don't know what to do. I can still get into recovery but no rom works.
ph3dia said:
So I was able to update my recovery but now every single rom that I try to flash ends up stuck at the motorola logo. I don't know what to do. I can still get into recovery but no rom works.
Click to expand...
Click to collapse
Moto logo? Are you trying to go back to stock?
Black_halo said:
Moto logo? Are you trying to go back to stock?
Click to expand...
Click to collapse
Nah, it's the dual core technology right before the animation for the startup. I posted a thread about the problem.
ph3dia said:
I'm having the same problem with every single 4.4 and 4.4.x rom. I've tried removing the lines of code method already, running 6.0.2.8 cwm
Click to expand...
Click to collapse
Try flashing Phil's Recovery, it should be version 6.0.4.5. Once I flashed Phil's I have not had a failed flash of any 4.4 Rom.
Here is the link in case you need it.
http://forum.xda-developers.com/showthread.php?t=2552622
PeteSeiler2010 said:
Try flashing Phil's Recovery, it should be version 6.0.4.5. Once I flashed Phil's I have not had a failed flash of any 4.4 Rom.
Here is the link in case you need it.
http://forum.xda-developers.com/showthread.php?t=2552622
Click to expand...
Click to collapse
That's what I've been running
ph3dia said:
That's what I've been running
Click to expand...
Click to collapse
Maybe try going back to stock and starting over. Whenever I have strange problems like this and everything checks out, I revert to stock and start over.
PeteSeiler2010 said:
Maybe try going back to stock and starting over. Whenever I have strange problems like this and everything checks out, I revert to stock and start over.
Click to expand...
Click to collapse
That was the first thing I tried, I just get a black screen once the phone tries to boot up.
ph3dia said:
That was the first thing I tried, I just get a black screen once the phone tries to boot up.
Click to expand...
Click to collapse
Did you use fastboot commands or the RUU?
Sent from my Atrix HD using XDA Premium 4 mobile app
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
hello
first off cool but i think this needs to go some where else maybe wrong
sorry to be annoying i just dont want u to get yelled at if its in the wrong place
bnb25 said:
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
Click to expand...
Click to collapse
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
RockasKane said:
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
Click to expand...
Click to collapse
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
bnb25 said:
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
Click to expand...
Click to collapse
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
I did the upgrade on my device no problems GOT ROOT then had issues. After root any changes ie: install zip, backup
The unit would get stuck in recovery mode. Recoveries tried TWRP, PhilZtouch, CWM
SDcard issues were fixed with Nextapp SDfix after root
Anyone having any other issues?
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
andrewhall said:
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
Click to expand...
Click to collapse
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
no. I booted into recovery while the phone was off. 3 key Combo.
Ok, sorry to hear that.
The workaround seems to work with everybody, thats why I asked.
RockasKane said:
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
Click to expand...
Click to collapse
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
andrewhall said:
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
Click to expand...
Click to collapse
Great!
But you must thank @gr8nole... Great and hardworking guy and all the development crew that contributed with great fixes