What ? http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.2.3-a700.img
You can install ?
Thank you.
davidcd13 said:
What ? http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.2.3-a700.img
You can install ?
Thank you.
Click to expand...
Click to collapse
I would advise you only install the CWM from the following thread;
http://forum.xda-developers.com/showthread.php?t=1791165
MD
Moscow Desire said:
I would advise you only install the CWM from the following thread;
http://forum.xda-developers.com/showthread.php?t=1791165
MD
Click to expand...
Click to collapse
Ok. Thank
It should work fine, as it is built from the CM device tree.
pawitp said:
It should work fine, as it is built from the CM device tree.
Click to expand...
Click to collapse
yes, I installed it and it works normally.
thank you.
[Acer A700] Last CWM Recovery
pawitp said:
It should work fine, as it is built from the CM device tree.
Click to expand...
Click to collapse
Yes, I installed it and it works normally.
You can see the last version of ClockWorkMod Recovery image at : clockworkmod.com/rommanager
Any problems with the wipes? I know some others had caused bricking.
ExtremeRyno said:
Any problems with the wipes? I know some others had caused bricking.
Click to expand...
Click to collapse
I think all the wipe issues in the early days, were caused by some folks who initially tried putting together a CWM, however, really didn't test it before releasing. Problem, they weren't using the correct partition information.
Lately, as far as I know, the more recent CWM builds don't have the bricking issue.
However, it is always possible you can brick your device. So be careful what you are doing. Most of the issues now days, are people mis-matching Bootloader-kernels and get stuck at the Acer screen. Wrong root method, etc.
MD
MD, could you get in touch with me as I can't seem to PM you anymore?
Related
Got stuck in a bootloop while trying to install a rom.
UPDATE Solved it, so I got it now.
What version of CM are you trying to install exactly? What's the full name of the zip? If it's CM10 not CM10.1 you may just need to downgrade your touchscreen drivers as described in http://forum.xda-developers.com/showthread.php?t=2159863. If it's CM10.1 you shouldn't need to do that.
I would highly recommend installing TWRP 2.6 instead of 2.5.
Are you SOFF? If not try http://forum.xda-developers.com/showthread.php?t=2155071. It keeps you from having to fastboot flash the boot.img every time.
Thank you for responding!
This helped thanks!
wizzrah said:
This helped thanks!
Click to expand...
Click to collapse
You're welcome!
Hello people! I had a problem installing CM 10.1 in my tf300t. First i try to install CM10.1 (cm-10.0.0-tf300t.zip ) with CWM. The bootloop was instantly and I try to install CM11 with TWRP but the result was the same. Sorry for my english! I wish to resolve this problem urgently.
P.D: The install was good in CM10.1 and CM11.
santipecollo said:
Hello people! I had a problem installing CM 10.1 in my tf300t. First i try to install CM10.1 (cm-10.0.0-tf300t.zip ) with CWM. The bootloop was instantly and I try to install CM11 with TWRP but the result was the same. Sorry for my english! I wish to resolve this problem urgently.
P.D: The install was good in CM10.1 and CM11.
Click to expand...
Click to collapse
CM10.1 probably requires a different bootloader than the one you are currently on and CM11 definitely requires a different bootloader and TWRP version. If you are on the Stock V10.6.1.27.1 and V10.6.1.15.3, you can follow these steps to get CM11: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
If you are on a different, older bootloader, you must upgrade by flashing the stock ROM first.
cmendonc2 said:
CM10.1 probably requires a different bootloader than the one you are currently on and CM11 definitely requires a different bootloader and TWRP version. If you are on the Stock V10.6.1.27.1 and V10.6.1.15.3, you can follow these steps to get CM11: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
If you are on a different, older bootloader, you must upgrade by flashing the stock ROM first.
Click to expand...
Click to collapse
First thanks for your quickly answer, second, how i know what is my version because i cant search it. For the cm11 i have the correct twrp version but sure i have a problem.
santipecollo said:
First thanks for your quickly answer, second, how i know what is my version because i cant search it. For the cm11 i have the correct twrp version but sure i have a problem.
Click to expand...
Click to collapse
You can find your bootloader by pressing volume down while powering on the device. It will appear in the top left corner.
cmendonc2 said:
You can find your bootloader by pressing volume down while powering on the device. It will appear in the top left corner.
Click to expand...
Click to collapse
Actually I find in CM11. What have i do? downgrade to CM10.0 and later enter in the post and then do the steps? thanks!
santipecollo said:
Actually I find in CM11. What have i do? downgrade to CM10.0 and later enter in the post and then do the steps? thanks!
Click to expand...
Click to collapse
Well it depends on your bootloader. You can only follow the steps from the post if you are on V10.6.1.27.1 or V10.6.1.15.3 or later. Nothing before that will work or CM11.
cmendonc2 said:
Well it depends on your bootloader. You can only follow the steps from the post if you are on V10.6.1.27.1 or V10.6.1.15.3 or later. Nothing before that will work or CM11.
Click to expand...
Click to collapse
I can fix it, i upgrade to CM10.0. My version is V10.4.2.19. What can i do to go CM11? Thanks for all!
santipecollo said:
I can fix it, i upgrade to CM10.0. My version is V10.4.2.19. What can i do to go CM11? Thanks for all!
Click to expand...
Click to collapse
OK so you need to flash the stock ROM, http://forum.xda-developers.com/showthread.php?t=1697227, Version: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 for your region. Then you can follow this: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
Hi. Please help. I have been running CM10.1 on my rooted tablet and I decided to try CM11. I don't know what I have done but CM11 did not work so I tried to go back to CM10.1, and that just gets stuck on the boot screen. I have tried several different Roms and they all get stuck on the boot screen. The only Rom that will work is CM9.1? I don't know what I could have done to cause this. I am running Philz Touch 6.12.8. Any help would be greatly appreciated.
Thanks
mattmust said:
Hi. Please help. I have been running CM10.1 on my rooted tablet and I decided to try CM11. I don't know what I have done but CM11 did not work so I tried to go back to CM10.1, and that just gets stuck on the boot screen. I have tried several different Roms and they all get stuck on the boot screen. The only Rom that will work is CM9.1? I don't know what I could have done to cause this. I am running Philz Touch 6.12.8. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
I think you need to replace your recovery twrp. Because I replace CM10 or CM11 works fine
http://forum.xda-developers.com/showthread.php?t=2548257
blue_drt29 said:
I think you need to replace your recovery twrp. Because I replace CM10 or CM11 works fine
http://forum.xda-developers.com/showthread.php?t=2548257
Click to expand...
Click to collapse
Yeah. I tried that and it is still the same. Thanks though
mattmust said:
Yeah. I tried that and it is still the same. Thanks though
Click to expand...
Click to collapse
i think you should flash back to stock then root then try new recovery and then flash the rom
i think the problem will be solved i do have same problem
Mohdsultan said:
i think you should flash back to stock then root then try new recovery and then flash the rom
i think the problem will be solved i do have same problem
Click to expand...
Click to collapse
I can't even flash back to stock. It still gets stuck on boot screen.
Thanks
Make sure you did a factory reset and format /system before.
Android-Andi said:
Make sure you did a factory reset and format /system before.
Click to expand...
Click to collapse
Yeah. I already did that. Thanks
@mattmust is it a verizon Tab?
Android-Andi said:
@mattmust is it a verizon Tab?
Click to expand...
Click to collapse
I'm not sure. I don't think so.
I also noticed when in recovery it says "E: unable to mount '/efs'"
mattmust said:
I'm not sure. I don't think so.
I also noticed when in recovery it says "E: unable to mount '/efs'"
Click to expand...
Click to collapse
Your EFS seems to be broken for some reason... that´s why it won´t boot into system....
this got reported in a german forum, because 2 guys flashed CWM 6.0.4.4-Touch on the device... CWM 6.0.4.4-Touch not released for the Tab 2 - it was for a different device and flashing that recovery brokes EFS for them.
Android-Andi said:
Your EFS seems to be broken for some reason... that´s why it won´t boot into system....
this got reported in a german forum, because 2 guys flashed CWM 6.0.4.4-Touch on the device... CWM 6.0.4.4-Touch not released for the Tab 2 - it was for a different device and flashing that recovery brokes EFS for them.
Click to expand...
Click to collapse
Yeah. That makes sense as I did put a version of CWM touch on. And the trouble started after that. Just need to try and find a solution to sort it now. Thanks for your help
mattmust said:
Yeah. That makes sense as I did put a version of CWM touch on. And the trouble started after that. Just need to try and find a solution to sort it now. Thanks for your help
Click to expand...
Click to collapse
Latest CWM Touch for our Device 6.0.2.7 ... i am sure you used a file for a different device and that broke your EFS!
Do you still have the file? you can upload it for me and send me a private message with the link, i can take a look on it. Please don't post the file here in the thread (i do not like to see someone else flashing it and breaking his efs).
I screwed up. I was updating twrp. I did something dumb and downloaded the blob for 2.2.1 instead of the new 2.7. Dumb I know...thought newest would be at the top of the list...I was wrong.
It installed 2.2.1. Now I cant get 2.7.1.1 to install. I tried flashing 2.6 from a zip in twrp and wont flash. Tried the toolkit and install 2.7 and it hangs on flashing recovery....
I tried installing with windows script and it hangs at flashing recovery. Any help would be appreciated.
Fear Knot said:
I screwed up. I was updating twrp. I did something dumb and downloaded the blob for 2.2.1 instead of the new 2.7. Dumb I know...thought newest would be at the top of the list...I was wrong.
It installed 2.2.1. Now I cant get 2.7.1.1 to install. I tried flashing 2.6 from a zip in twrp and wont flash. Tried the toolkit and install 2.7 and it hangs on flashing recovery....
I tried installing with windows script and it hangs at flashing recovery. Any help would be appreciated.
Click to expand...
Click to collapse
You're going to have to start over with the Asus blob ...
Shot me a PM and we can see if there is a solution for your issue ....
Thx Josh
Thanks Josh. I sent you a PM
Josh got me up and running. Thank you He did a great job
Fear Knot said:
Josh got me up and running. Thank you He did a great job
Click to expand...
Click to collapse
We just did a full wipe from fastboot of all partitions
Flashed the Asus blob, enabled nvflash ....
Thx Josh
@Fear Knot can you add SOLVED to your thread title....
lj50036 said:
We just did a full wipe from fastboot of all partitions
Flashed the Asus blob, enabled nvflash ....
Thx Josh
@Fear Knot can you add SOLVED to your thread title....
Click to expand...
Click to collapse
How about a link to the steps you took so others can follow it?
Unless of course, you enjoy doing this over and over and over [emoji12]
berndblb said:
How about a link to the steps you took so others can follow it?
Unless of course, you enjoy doing this over and over and over [emoji12]
Click to expand...
Click to collapse
Here are a few .
http://www.asus.com/us/
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
http://forum.xda-developers.com/showthread.php?t=2538028
http://forum.xda-developers.com/showthread.php?t=1426502
I did not know I was being watched.
Thx Josh
lj50036 said:
Here are a few .
http://www.asus.com/us/
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
http://forum.xda-developers.com/showthread.php?t=2538028
http://forum.xda-developers.com/showthread.php?t=1426502
I did not know I was being watched.
Thx Josh
Click to expand...
Click to collapse
[emoji102]
berndblb said:
[emoji102]
Click to expand...
Click to collapse
Ok, Im not sure what your on about here, but goodluck.
lj50036 said:
Ok, Im not sure what your on about here, but goodluck.
Click to expand...
Click to collapse
Just pulling your leg. Sorry if it came across other than friendly teasing. [emoji15]
berndblb said:
Just pulling your leg. Sorry if it came across other than friendly teasing. [emoji15]
Click to expand...
Click to collapse
No my bad.
@sbdags put me in my place ...
i am considering installing android L but i would like to keep using philz custom recovery. does anyone know if both are compatible?
regards
PhilZ Touch is no longer officially maintained, doesn't support encryption, and Lollipop uses encryption by default.
Lethargy said:
PhilZ Touch is no longer officially maintained, doesn't support encryption, and Lollipop uses encryption by default.
Click to expand...
Click to collapse
will have to go with cwm then!
thanks
cesar.maranhao said:
will have to go with cwm then!
thanks
Click to expand...
Click to collapse
Don't go with CWM, use TWRP.
Lethargy said:
Don't go with CWM, use TWRP.
Click to expand...
Click to collapse
why?
cesar.maranhao said:
why?
Click to expand...
Click to collapse
CWM is even more outdated.
Lethargy said:
CWM is even more outdated.
Click to expand...
Click to collapse
i see. thanks again!
(seems i am outdated myself haha)
Phil just posted that he now uses TWRP and when he is finished with his real life projects, he will push commits to contribute to the development of TWRP.
Can. I'm gonna have to learn whatever TWRP uses instead of extended commands. Is that Open Recovery Scripts?
rootSU said:
Phil just posted that he now uses TWRP and when he is finished with his real life projects, he will push commits to contribute to the development of TWRP.
Can. I'm gonna have to learn whatever TWRP uses instead of extended commands. Is that Open Recovery Scripts?
Click to expand...
Click to collapse
Never looked/checked but I think so
rootSU said:
Phil just posted that he now uses TWRP and when he is finished with his real life projects, he will push commits to contribute to the development of TWRP.
Can. I'm gonna have to learn whatever TWRP uses instead of extended commands. Is that Open Recovery Scripts?
Click to expand...
Click to collapse
It should help: http://www.teamw.in/OpenRecoveryScript
Primokorn said:
It should help: http://www.teamw.in/OpenRecoveryScript
Click to expand...
Click to collapse
Cheers dude.
I'm gonna have to re-write all my Tasker auto-nandroid profiles
I don't think TWRP works with L encryption either. At least it doesn't for me.
nirudha said:
I don't think TWRP works with L encryption either. At least it doesn't for me.
Click to expand...
Click to collapse
No it doesn't. Philz doesn't work with any encryption though. TWRP no doubt will be updated