CWM Cache error [STRIKES AGAIN!] - myTouch 4G Q&A, Help & Troubleshooting

[Solved!!]
When I open CWM I always get this error (see attached image) I have tried flashing an older version of CWM and I still get it... I have searched a TON to find the answer to this and it seems really common on Nexus S owners but I haven't found a solution... But because of this I can no longer flash anything.
Any ideas? I have fastboot erased EVERYTHING even tried fastboot flashing a Nandroid that I KNOW is a good backup... it seems to work but when I go to boot the device I get stuck that the bootscreen :/
[Solved!!!]
Anyone ever runs into this issue, flash CWM 2.X.X.X go to mounts, mount cache then format it. I couldn't mount cache in 3.X.X.X but it worked in 2.X.X.X. Not sure why this worked but whatever! lol
UPDATE!!!
SO the CWM Ghost is back, once again. Still nothing out of the ordanary done on my part, just started getting random FC's and boom there it's ugly mug is when I go to CWM to fix permissions...
BUT, here is the problem, I'm trying to fix it how I did last time and when I go to flash the new recovery in Fastboot via ADB I get this error:
sending 'recovery' <4000 KB>... OKAY [15.390s]
writing 'recovery' ...FAILED <remote: image update error>
I have tried a few different CWM recovery downloads... any ideas?

dcwiker05 said:
[Solved!!]
When I open CWM I always get this error (see attached image) I have tried flashing an older version of CWM and I still get it... I have searched a TON to find the answer to this and it seems really common on Nexus S owners but I haven't found a solution... But because of this I can no longer flash anything.
Any ideas? I have fastboot erased EVERYTHING even tried fastboot flashing a Nandroid that I KNOW is a good backup... it seems to work but when I go to boot the device I get stuck that the bootscreen :/
[Solved!!!]
Anyone ever runs into this issue, flash CWM 2.X.X.X go to mounts, mount cache then format it. I couldn't mount cache in 3.X.X.X but it worked in 2.X.X.X. Not sure why this worked but whatever! lol
Click to expand...
Click to collapse
You know, even though you solved it, I still think you should send a note to koush... the creator of CWM....

faux123 said:
You know, even though you solved it, I still think you should send a note to koush... the creator of CWM....
Click to expand...
Click to collapse
I sent him a private message detailing what led up to the error (and may or may not have caused it) as well as a link to this thread.

dcwiker05 said:
I sent him a private message detailing what led up to the error (and may or may not have caused it) as well as a link to this thread.
Click to expand...
Click to collapse
glad you fixed it, as many ppl have had this issue and have yet to recover from it!!! also, since you had fastboot set up i am assuming you have the 85.2007 engineering bootloader, correct?
i saw this preview post and all i could say is the cwm ghost got another one but it seems you got lucky!!!

irrelephant said:
glad you fixed it, as many ppl have had this issue and have yet to recover from it!!! also, since you had fastboot set up i am assuming you have the 85.2007 engineering bootloader, correct?
i saw this preview post and all i could say is the cwm ghost got another one but it seems you got lucky!!!
Click to expand...
Click to collapse
I would say "lucky" as well. but i'm wondering if the 2.x recovery image might be the fix for this problem. If one could "brick" their phone with the same symptoms as this phone. Then flash the 2.x recovery and see if it fixes the problems.

Yeah I have 85. Bootloader, because I read to flash CM7 it was best to have that installed. As for me fitting lucky yeah I guess I did, I didn't realize this was one of those "end all" errors lol. Specially since I really have no clue what possessed me to flash the old clock work. Basically I felt there had been known issues with 3.X. so I thought "what would it hurt?" Turns out it helped!!! I'm using the phone now and everything is 100%
Sent from the depths of hell cuz XDA's app is THAT good!!

dcwiker05 said:
Yeah I have 85. Bootloader, because I read to flash CM7 it was best to have that installed. As for me fitting lucky yeah I guess I did, I didn't realize this was one of those "end all" errors lol. Specially since I really have no clue what possessed me to flash the old clock work. Basically I felt there had been known issues with 3.X. so I thought "what would it hurt?" Turns out it helped!!! I'm using the phone now and everything is 100%
Sent from the depths of hell cuz XDA's app is THAT good!!
Click to expand...
Click to collapse
Nice i'm going to remember this thread.

TOPSIDE for some new developments. See OP for update...

I believe TrueBlue_Drew has a flashable zip for CWM 2.5.1.2 Have you tried that?

hello i need that recovery 2.___ for fix my problem same that! where i cant find_

vabeach454 said:
I believe TrueBlue_Drew has a flashable zip for CWM 2.5.1.2 Have you tried that?
Click to expand...
Click to collapse
I think I found what you are talking about HERE but from what I gather that needs your phone able to boot cuz it changes the recovery via Rom Manager. Sadly my phone doesn't boot, all I have is hboot and the 3.1.2.4 recovery available to use, both of which are basically broken. Thanks for the help and the idea though I really hope we come up with a way to fix this somehow. Any dev who needs a phone to experiment on, hit me up.

dcwiker05 said:
I think I found what you are talking about HERE but from what I gather that needs your phone able to boot cuz it changes the recovery via Rom Manager. Sadly my phone doesn't boot, all I have is hboot and the 3.1.2.4 recovery available to use, both of which are basically broken. Thanks for the help and the idea though I really hope we come up with a way to fix this somehow. Any dev who needs a phone to experiment on, hit me up.
Click to expand...
Click to collapse
Download zip from thread. Extract it to desktop or location of your choice. Go into the folders and find the recovery img that has 2.5.1.4 in the name. That is actually the 2.5.1.2 recovery. You can then re-name it to what ever you need to and push it to your device.
Hope this helps.

victorx said:
hello i need that recovery 2.___ for fix my problem same that! where i cant find_
Click to expand...
Click to collapse
Download this navigate to this (C:\Users\YOURUSERNAME\Recovery_2.5.1.2_to_RomManager.zip\sdcard\clockworkmod\download\mirrorbrain.cyanogenmod.com\cm\recoveries\) extract the recovery 2.5.1.2. Rename it recovery.img and try to flash it via adb in hboot (fastboot flash recovery recovery I BELIEVE that is the command I can't honestly remember but a quick google search will yield you a adb guide no problem

TrueBlue_Drew said:
Download zip from thread. Extract it to desktop or location of your choice. Go into the folders and find the recovery img that has 2.5.1.4 in the name. That is actually the 2.5.1.2 recovery. You can then re-name it to what ever you need to and push it to your device.
Hope this helps.
Click to expand...
Click to collapse
I can't push to my device which is the COMMAND problem. Now when I try to push via ADB I get an error saying write---FAILED. I have tried a few other tricks I have been told as well about like repartitionion the cache via ADB and that doesn't work either. So I hope this works for the OP

Related

Booting into clockwork recovery

I don't know how I did it, but everyone else is trying to boot into Clockwork Recovery mode successfully...and the whole pull the battery mode doesn't work 100% of the time...buuuut...I CANT STOP!
I can't stop booting into Clockwork. Every time I turn my phone on, it boots into the Clockwork Recovery, without fault. I've rebooted almost 30 times now and every time its done the same thing. Once it reboots into recovery, it will allow me to reboot the phone and then it boots normally. I really want to fix it, its annoying. The phone still works without any issues, its just really annoying that I have to sit there and watch it boot up to get it to the actual phone.
I don't want to unroot and start over with it all because I've made so many small changes to the phone and made it my own.
Sooo, pleeeeeeeeeease anyone with any info or fixes; let me know!
Mine did that too so I flashed the SBF and started over from scratch. I am afraid to try the D2 Bootstrap again for that reason. For now I can live with it. Did you find a fix yet?
How does this work?
When your device boots up, there is a init.rc script in your boot image that runs various components found in /system. The Droid X recovery bootstrap mimics the "logwrapper" binary. The hijacker then looks for "/data/.recovery_mode", and if it finds it, it unmounts /system to prevent android from starting. It then starts up recovery instead.
That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
kwheel596 said:
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
Click to expand...
Click to collapse
Glad it worked. It happened to me too and I just used the sbf file to restore everything. Did you use any mount adb commands before you had that problem?
To be honest I have no idea, I've had android phones for a while so I was just flying through the commands and don't remember what was typed
Unable to remove "ClockworkMod Recovery"
[/QUOTE]That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?[/QUOTE]
So, I looked throughout my sd card, and have been unable to find any ".recover_mode" file.. I still get the ClockworkMod Recover screen EVERY time I reboot my device.. I have rooted and unrooted multiple times to try and figure out this problem, as well as searched through this website for answers.. I am not finding any.. HELP!?
Ultimately, I would like to just restore my phone to factory so I can pass it on to a friend..
Thanks in advance for everyone's help!
Chenoaem
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
enkrypt3d said:
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
Click to expand...
Click to collapse
nevermind... forgot to hit the search key! doh!

[Q] Unable to boot HTC Glacier

I'm unable to boot my Glacier, I am able to get into the boot menu though. i was wondering if there is any way at all where i could perhaps just wipe everything and just reinstall the OS, or any other ways to fix this. any help would be very much appreciated.
two things:
1.Can you get in to recovery through the boot menu?
2. if you can't, download http://www.megaupload.com/?d=V4NAODYZ and make sure it's named PD15IMG.zip and put in on the sd card (Not in any folders) and go to the boot menu and then bootloader and it will reset the entire phone.
It would be helpful of you provided information regarding how to ended up where unable to boot. Based on what you provide we can give you "correct" feedback to fix your issue.
truthfully i have no clue on how it bricked. My little brother did something and will not tell me, but i think it had something to do with him trying to root the phone or something with that gingerbread mod.
mwake456 said:
truthfully i have no clue on how it bricked. My little brother did something and will not tell me, but i think it had something to do with him trying to root the phone or something with that gingerbread mod.
Click to expand...
Click to collapse
You are going to need to find out what he did or how far he got
listen i can't find out, all i know is clockwork mod is installed, when i get into the boot menu it looks for a PD15diag on the sd, and clockworkmod can't mount /cache/recovery/command, /log, /log, /last_log, /last_log
Dude if your brother screwed up your phone make him tell you what he did.
another can't mount cache error huh? sorry to tell ya i think your phone is f***ed dude. i would search for "cwm can't mount cache error" or something like that and see if anybody has a solution, but i'm pretty sure this means your emmc chip is fried.
what does it say when it looks for the pd15img.zip file? does it update?
it says no image.
mwake456 said:
it says no image.
Click to expand...
Click to collapse
so let me see if i got this right. Please correct me if i'm wrong. You boot bootloader > it scans for pd15img.zip and finds nothing (like normal) > you go to recovery via bootloader > in recovery it says a bunch of can't mounts and fails etc.
correction i got it to now read the pd15img.zip file after formating it to a FAT32 sd, but so far it's now given me the Fail-PU for bootloader, Boot, Recovery, System, Userdata, and splash1 and seems to be hanging at radio_V2
tjlawson09 said:
so let me see if i got this right. Please correct me if i'm wrong. You boot bootloader > it scans for pd15img.zip and finds nothing (like normal) > you go to recovery via bootloader > in recovery it says a bunch of can't mounts and fails etc.
Click to expand...
Click to collapse
Yes, basically. i found out that this happens on the clockworkmod 3.0, so i've been trying to find out how to downgrade it to try and see if that'll work.
sorry pal nothing i can do for you. search for failed emmc chip or can't mount in cwm and read those posts just to clarify that your emmc is fried. maybe someone figured it out??? doubt it though.
Hmmmm alright well if anyone else could help me out on this that would be fantastic, I'm trying not to believe a chip is fried
Sent from my HTC Glacier using XDA App
Same issue
mwake456 said:
it says no image.
Click to expand...
Click to collapse
I am having a hell of a time with this too. I tried flashing a theme, and well... now i can't get past the bootanimation. I've tried reseting with the stock image, and I get the same reply. NO IMAGE.
If you find an answer, please let me know.
Yeah, are you using clockworkmod 3.0?
Sent from my HTC Glacier using XDA App

[Recovery] ClockworkMod Recovery flashable from bootloader

Someone asked if it was possible to flash ClockworkMod Recovery through hboot instead of using RomManager. The answer...yes.
Primary reason something of this nature may be useful, as I see it, is if your recovery is damaged, your ROM is bootlooping, and you don't want to use or have access to ADB.
In that case you would:
remove your sdcard from your phone
place the zip on the root of the sdcard (using an adapter or another phone) and make sure it is named the appropriate "PG05IMG.zip"
place the sdcard back in your phone
boot to bootloader as if you're installing a radio (power+VolDown from powerOff). It will then find the zip, recognize it as recovery and ask if you want to install (if it does not prompt then select "Bootloader" from hboot).
Follow the instructions and after it finishes flashing pull your battery to power off (since the ROM will be bootlooping and hboot will constantly find the zip)
Now remove the sdcard and delete the zip (via adapter or other phone) like you did to put it on the sdcard, then place the card back in the phone.
Boot back to bootloader (Pwr+VolDwn)
Select "Recovery" and use CWR to wipe data/cache, flash a new rom, restore, or whatever you wish.
Obviously not the only reason since some people prefer this method over RM but clearly in that case the whole sdcard switching mess is unnecessary. Just do steps 2 and 4 and reboot when prompted like you do with radios.
Remember to remove any PGO5IMG.zip from your sdcard when done.
If this isn't useful to you, so be it. I just figured I'd throw this out there. Maybe it will help someone.
I will keep this updated as new versions come out for those few that find it useful.
**Credit to Koush and jcase**
All I did was decide to throw them in a zip that was useful in some situations for panicking users.
Updates
8/9/2011: Added latest official stable for mecha (4.0.1.5) released 8/8/2011.
8/30/2011: Added latest official stable for mecha (5.0.0.1) released less than an hour ago. Added mirror.
8/31/2011: Added latest official stable for mecha (5.0.0.8)
9/1/2011: Added latest official stable for mecha (5.0.1.0)
9/5/2011: Added latest official stable for mecha (5.0.2.1)
2/1/2012: Added touch based CWR released this morning (5.8.0.2) *NOTE: Have not personally tested.
If any of these cause problems please let me know immediately.
Latest Official=5.0.2.1
jcase modded=4.0.0.5
Mirror: http://www.mediafire.com/?9zt68cegl6qa3
MD5:
66750618ecfba292c0b0e42c50c2c3ee - (CWR3.1.0.2)PG05IMG.zip
1f390edad7e87310fe80b3264a57b14b - (CWR4.0.0.5)PG05IMG.zip
6aac529cedcd2b22afac7391a4cb7efb - (CWR4.0.1.5)PG05IMG.zip
bf25b2601441b9fffb7d68954c4ff3b5 - (CWR5.0.0.1)PG05IMG.zip
dfe1ddf0c574977ee2c1828735ef2dc0 - (CWR5.0.0.8)PG05IMG.zip
8474c8d607177b0144eec624dea687b7 - (CWR5.0.1.0)PG05IMG.zip
c4c1d9c5e553fd7b151352551b931369 - (CWR5.0.2.1)PG05IMG.zip
58557e1e355c795d748c2e6c66251f0a - (CWR5.8.0.2)PG05IMG.zip
Absolute_Zero said:
Someone asked if it was possible to flash ClockworkMod Recovery through hboot instead of using RomManager. I didn't see the need at the time but I took a few minutes to throw together a test. Let me know if it works for you or not.
I tested flashing the stock recovery from the custom firmware, confirmed it had replaced CWR, then used this to install CWR back.
Primary reason something of this nature may be useful, as I see it, is if your recovery is damaged, your ROM is bootlooping, and you don't want or have access to ADB. In that case you would just pull your sdcard, place this on the root (via adapter or someone else's phone) named the appropriate "PG05IMG.zip", place back in your phone, and boot to bootloader as if you're installing a radio. It should then find it, recognize it as recovery and ask if you want to install.
Additionally, seems if it is as easy as swapping the .img out which is all I did, then the original custom upgrade firmware flashed in the last step of the root guide could include this. Then you'd have CWR immediately after finishing the permaroot guide.
If this doesn't work and doesn't have any use for anyone, so be it. I just figured I'd throw this out there.
BTW, this is ClockworkMod Recovery 3.1.0.2 (latest for mecha at time of posting).
Note1: Only tested on Engr hboot with S-off obviously
Note2: I don't have access to an MD5 generator where I am so people that test this should have a booting ROM with RomManager or at least know how to manually reflash ClockworkMod Recovery if it doesn't work.
Click to expand...
Click to collapse
Good work.on this... A LOT of people are going enjoy it!! It is also a great way to install the modded 4.0.0.5 Clockwork with the boot to bootloader option.
I always had to "flash recovery" in adb.
Props!!
Sent from my ADR6400L using XDA App
good post will definitely come in hand props
DroidTh3ory said:
Good work.on this... A LOT of people are going enjoy it!! It is also a great way to install the modded 4.0.0.5 Clockwork with the boot to bootloader option.
I always had to "flash recovery" in adb.
Props!!
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
There's a modded 4.0.0.5 CWM Recovery out there?? Where can I find the post for this ?
Sword.Zero said:
There's a modded 4.0.0.5 CWM Recovery out there?? Where can I find the post for this ?
Click to expand...
Click to collapse
Post a link to it and I'll make one when I get home. That way I can test again. Hopefully the modded one you speak of is fully stable and functional.
Absolute_Zero said:
Post a link to it and I'll make one when I get home. That way I can test again. Hopefully the modded one you speak of is fully stable and functional.
Click to expand...
Click to collapse
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment (CWR4.0.0.5)PG05IMG.zip
DroidTh3ory said:
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment 661641
Click to expand...
Click to collapse
In your case it would probably be easier to just use flash_image from terminal on the phone (i.e. flash_image recovery /sdcard/recovery.img) assuming your current rom has it (if not just search and download it) or you have RM installed. The main case I saw this being useful was if you didn't have or want to use ADB and your ROM was unusable (e.g. bootlooping). I may add Jcase's modded recovery to the OP as well since it seems useful/wanted by some.
I thought the one JCase made had issues with nandroid backups installing? I could be wrong but for some reason I remember that issue for several people.
Mustang302LX said:
I thought the one JCase made had issues with nandroid backups installing? I could be wrong but for some reason I remember that issue for several people.
Click to expand...
Click to collapse
I have been using for a good month now on 3 different bolts... Never had a issue??
Absolute_Zero said:
Additionally, seems if it is as easy as swapping the .img out which is all I did, then the original custom upgrade firmware flashed in the last step of the root guide could include this. Then you'd have CWR immediately after finishing the permaroot guide.
Click to expand...
Click to collapse
actually,thats allready how it is ive rooted mr2 twice and the mr1 upgrade allready has clockwork installed.
it is that easy,i have done this,and i have also removed the hboot and stock recovery from PG05IMG RUUs so that i could flash without destroying recovery and my eng bootloader.
thanks for putting it together and offering the download, it has many uses, as people will see. the biggest one allready having been mentioned,if something screws up your OS and recovery,its easy to get it back.
did you make up your own android info file? or what did you take it from?
again thanks for posting this,it was commonplace to install inc recoverys in hboot,and ive done it on the eris as well
DroidTh3ory said:
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment 661641
Click to expand...
Click to collapse
thanks for the download. has he put up any posts on it? or is it still being developed?
scotty1223 said:
thanks for the download. has he put up any posts on it? or is it still being developed?
Click to expand...
Click to collapse
I believe he has it posted on rootzwiki
Sent from my ADR6400L using XDA App
cool,thanx... ill go over there and look for it.
edot:
here if anyone else wants it
Thanks for this. Just flashed 4.0.0.5 after being afraid/too lazy to do it through ADB (which is also a pain because I have it on my Windows partition whereas I regularly use Mac).
scotty1223 said:
actually,thats allready how it is ive rooted mr2 twice and the mr1 upgrade allready has clockwork installed.
Click to expand...
Click to collapse
Figures. It was too simple of a concept not to have been done but I didn't see anyone that had done it in Tbolt. I also hadn't seen anyone mention it was in the custom firmware either and I didn't have time to check this morning before I left for work. I guess I can pull that part out of the OP since you say it's already in there.
thanks for putting it together and offering the download, it has many uses, as people will see. the biggest one allready having been mentioned,if something screws up your OS and recovery,its easy to get it back.
Click to expand...
Click to collapse
Exactly my reasoning. I've seen to many people unaware of what to do in that situation
did you make up your own android info file? or what did you take it from?
Click to expand...
Click to collapse
I checked a few from the firmware and radios and they all looked the same so I just pulled one of those.
again thanks for posting this,it was commonplace to install inc recoverys in hboot,and ive done it on the eris as well
Click to expand...
Click to collapse
First HTC android phone I've owned but as I said, makes sense it would have been done a long time ago for other HTC phones.
DroidTh3ory said:
I believe he has it posted on rootzwiki
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Hey get out of here, you've got candy to make! I keeeed I keeeed! Great work on the recovery guys, VERY useful!
Sent from my ADR6400L using XDA Premium App
DroidTh3ory said:
I have been using for a good month now on 3 different bolts... Never had a issue??
Click to expand...
Click to collapse
Yup. Been using it since it's release. Restored many backups with absolutely no issues.
Absolute_Zero said:
Figures. It was too simple of a concept not to have been done but I didn't see anyone that had done it in Tbolt. I also hadn't seen anyone mention it was in the custom firmware either and I didn't have time to check this morning before I left for work. I guess I can pull that part out of the OP since you say it's already in there.
Click to expand...
Click to collapse
id be willing to bet most people dont know,lol.they prolly just blindly downloAd rom manager and flash it. i checked to see if it was there,after seeing this as one of the last statements in the root post: Reboot your phone. You should now have full root permissions, an engineering kernel and recovery.
Absolute_Zero said:
First HTC android phone I've owned but as I said, makes sense it would have been done a long time ago for other HTC phones.
Click to expand...
Click to collapse
its one of the things i really love about htc. i got used to installing recoverys,splash screens,etc. on my incredible,then started experimenting with img files on my eris,and discovered it was quite possible to simply move the images around kinda neat if you want to try a leaked ruu but dont want to wait for someone to post a CWM flashable roms. just pull out the hboot and stock recovery and flash away
it was quite common to manipulate things in hboot on the inc,but never mentioned in the eris forum,where most of the gurus frowned upon the s-off bootloader.kind of a shame... more bricked eris's prolly could have been revived after the clockwork fiasco if s-off was part of the common root process.
thanx for the android info info. when i make them up,it doesnt seem to matter which one i use. i dont think it even checks the text inside,i think you just need a text document titled "android info" lol
Thank you for the updated 5.0.0.1 cement recovery.
cam30era said:
Thank you for the updated 5.0.0.1 cement recovery.
Click to expand...
Click to collapse
Autocorrect fail? or did you have a problem with 5.0.0.1?

ClockworkMod Touch Recovery For Shift

Now available for the Evo Shift, go try it out and let us know what ya think about it!
If it aint broke, don't fix it.
VICODAN said:
If it aint broke, don't fix it.
Click to expand...
Click to collapse
I don't care I would still like a ICS touch recovery for the shift that works with rom manager.
I saw this a couple of days ago. I wouldn't mind getting it.
Sent from my PG06100 using Tapatalk
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
notsointeresting said:
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
Click to expand...
Click to collapse
Yeah according to koush's twitter he just "hacked" touch into cwm recovery so I'm sure he'll work on it more. Twrp is a nice recovery and koush is a really good recovery developer so I'm sure he'll make it better if possible. It's funny after finding out about twrp 2.0 being in development before it was even released I asked koush if it was possible to have touch in cwm. Now we're getting it lol.
notsointeresting said:
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
Click to expand...
Click to collapse
Using it on my NS4G and honestly I like it better than TWRP. Everything being larger is reassuring, in TWRP I was always nervous because there was such a small area to select. With the items being so close in TWRP I always wanted my volume keys to work so I could make fine maneuvers and in CWM Touch they do. So you can use it just like regular CWM or with touch. Nice if you mess up your touch screen. And of course it also works with ROM Manager. I downloaded it from the site but I may actually donate the $2 for it too.
Touch recovery has just become available on my SHIFT!!! CHECKIN' IT OUT NOW, VERY COOL!
Let Me Put My Shift In U
letmeputdatipin said:
Touch recovery has just become available on my SHIFT!!! CHECKIN' IT OUT NOW, VERY COOL!
Let Me Put My Shift In U
Click to expand...
Click to collapse
I know I tested it for him last night but it's not stable. I wouldn't purchase it quite yet. Download it from the site and test it out. It will boot into recovery for about 5-10 secs format your cache then reboot to system/rom. Strange bug. It would be nice if someone else could confirm this.
sparksco said:
I know I tested it for him last night but it's not stable. I wouldn't purchase it quite yet. Download it from the site and test it out. It will boot into recovery for about 5-10 secs format your cache then reboot to system/rom. Strange bug. It would be nice if someone else could confirm this.
Click to expand...
Click to collapse
I just flashed it through fastboot and haven't seen that issue. I'm actually in the process of making a backup
Edit: Weird thing.. made a backup and rebooted, everything was gone. It brought my ROM completely back to barebones.. even gapps were gone. Restoring with Touch now to see what happens.
Sent from my Android powered Tenderloin
crump84 said:
I just flashed it through fastboot and haven't seen that issue. I'm actually in the process of making a backup
Edit: Weird thing.. made a backup and rebooted, everything was gone. It brought my ROM completely back to barebones.. even gapps were gone. Restoring with Touch now to see what happens.
Sent from my Android powered Tenderloin
Click to expand...
Click to collapse
Hmm, well I did fastboot erase recovery before flashing, not sure if that has anything to do with it. What recovery did you flash this on top of, just the previous cwm recovery? You can also report bugs to him on irc freenode #koush
sparksco said:
Hmm, well I did fastboot erase recovery before flashing, not sure if that has anything to do with it. What recovery did you flash this on top of, just the previous cwm recovery? You can also report bugs to him on irc freenode #koush
Click to expand...
Click to collapse
Yeah I was coming from the previous version of cwm. I just did a restore and everything is fine. Ill probably mess with it a little later when I have some free time.
Sent from my Android powered Tenderloin
I'm not at my pc to try fastboot again but I did flash the previous cwm recovery and it works fine. Then I flashed the new touch recovery with the flash_image command in terminal emulator and I'm getting the same results as before. This is really annoying me because I would like to get this recovery working and I don't know WTH is going wrong here. Maybe it's the new firmware update? I doubt it. Anyways hope to here from more people that try this out.
Edit: when I get a chance later I'll flash with fastboot without running the fastboot erase recovery command and see how it goes.
I must have got lucky... I used joey krim's GUI Flash App and flashed it over the top of the prior clockwork mod recovery... I'll spend a little time tonight trying to replicate...
Sent from my PG06100 using Tapatalk
Well just used the touch recovery to flash my first ROM and had no issues. Maybe my first experience was fluke.
Anyway, liking this recovery so far.
I'm gonna be using GUI flash like Drob since its just easier for me
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
jrny99 said:
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
Click to expand...
Click to collapse
I'm nit sure about that (although I feel it should be .zip but probably wrong), but you could use Flash Image GUI from the Market or use fastboot from your PC. You'd just stick the .img file in the same folder as fastboot, cd there and type "fastboot flash recovery whateveryounamedit.img". Personally I like Flash Image, works well for flashing kernels too.
jrny99 said:
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
Click to expand...
Click to collapse
Yeah, just to reiterate what J-Ice already said... don't rename the img, just flash through fastboot.
I can confirm this is not working for at least one other person on the latest firmware update via twitter messaging...I've tried GUI, fastboot, flash_image, all same results.

Stuck at google logo, recovery mode doesn't work?

I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
calavera-pw said:
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
Click to expand...
Click to collapse
before you do anything, use your recovery to see if the rom zip is located in /data/media/0/. if its there, flash it from that location.
Are you able to boot into recovery?
If yes, it could be as simple as plugging your tablet into the computer and mounting the usb, drag and drop the rom, and flash it without using a toolkit (only recovery). I'm not familiar with jrom flasher, but i will say the more variables there are, the more chance of a problem.
If no, you're best off running the stock factory image through your computer, found here: https://developers.google.com/android/nexus/images#nakasi. I had your problem at one point, and could not even boot into recovery. After trying to install cwm through adb (which failed), and a number of toolkits, the factory image was what brought my nexus back to life.
I remember reading that sometimes a wipe can delete your recovery as well as your system (and whatever else you have on your n7), although i dont know if that was ever fixed, as i got my tab replaced a month or two ago and havent rooted it again yet. There was some type of command or .zip or something that should be used to keep recovery after wipes. When i expirienced problems such as yours, it was also from a bad wipe from a toolkit. Using just the recovery afterwards, i never expirienced any issues, even without the recovery fix.
I would definitely try simms suggestion first if you can access recovery. If that fails, try one of the above processes.
PS, even if you can access recovery, if at this point you just want to go completely stock, the factory image will work regardless.
cheers
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
calavera-pw said:
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
Click to expand...
Click to collapse
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
appoos said:
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
Click to expand...
Click to collapse
ADB
Sent from my Galaxy Nexus
Pirateghost said:
ADB
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This dint work in my windows 8
appoos said:
This dint work in my windows 8
Click to expand...
Click to collapse
You're holding it wrong. ADB works on my Win8 machine
Pirateghost said:
You're holding it wrong. ADB works on my Win8 machine
Click to expand...
Click to collapse
can you tell me the procedure..
appoos said:
can you tell me the procedure..
Click to expand...
Click to collapse
no.
in the other thread that YOU created, you were given links to follow and the instructions are already there. i dont hold hands
I could do it with ADB..thanks guys

Categories

Resources