ok so i rooted and unlocked the bootloader. after that i installed rom manager, flashed the recovery, and than tried to flash the romracer's CWM and now i keep getting the triangle with the android when i go into recovery. any fix for this?
Did you delete the install_recovery.sh file with root explorer?
Sent from my MB860 using XDA App
where do i find that file? btw it didnt say that in the tutorial
mac208x said:
where do i find that file? btw it didnt say that in the tutorial
Click to expand...
Click to collapse
In /system/etc.
That's only if you had Tenfars recovery installed beforehand though. Might want to make sure your downloading the right version from RomRacers thread. Also make sure your downloading the one one the right side (the CWM flashable one) and not the fastboot version.
Sent from my MB860 using xda premium
i did, i dont know why this is happening to be, i want to flash aura rom
mac208x said:
i did, i dont know why this is happening to be, i want to flash aura rom
Click to expand...
Click to collapse
Just reflash ROM Manager CWM in the app, and use that to flash Aura. Should work. Rom Managers version works, most just prefer RomRacers.
Have you tried installing RomRacers CWM via fastboot? Instructions in his OP (the .zips on the left side).
Sent from my MB860 using xda premium
Swiftks said:
Just reflash ROM Manager CWM in the app, and use that to flash Aura. Should work. Rom Managers version works, most just prefer RomRacers.
Have you tried installing RomRacers CWM via fastboot? Instructions in his OP (the .zips on the left side).
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
i prefer not to use commands im rlly bad at it
mac208x said:
i prefer not to use commands im rlly bad at it
Click to expand...
Click to collapse
I had the same issue..
Download ES file explorer and go to settings..
Select "Mount file system - Mount /system as writable"
Delete or rename install-recovery.sh.
Boot into fast boot (power and volume down) press up volume when u see fast boot.
Plug in usb.. start fastboot
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
You will now have a working CWM.
install-recovery.sh cannot be renamed/deleted because the file system is read-only
so how do i delete it? >.<
nvm got it
Related
how can I put my phone in stock recovery mode? I tried holding both volume keys down and power, it just powercycles. Even if let go on the second screen off. if I continue on holding - it just powercycles. If i hold vol down and power - it goes into download mode...
I have Clockwork installed. If I start recovery from ROM Manager it bypasses stock recovery straight to Cloclwork menu. I am trying to install battery percentage indicator, which I can only do thru stock recovery menu. How can I start stock rec mode?...
Also it says DO NOT INSTALL this lag fix http://forum.xda-developers.com/showthread.php?t=765820 using ROM MANAGER. So how can I install it then??
in clockwork recovery theres an option to boot into regular recovery. i believe its in advanced settings?
adb is your friend. seriously, how have people on this forum not figured this out yet? (I don't actually even know how to reboot into recovery with just the buttons off the top of my head)
either "adb reboot recovery" or download "Terminal Emulator" from the marketplace type "su" and then "reboot recovery"
bmvik said:
how can I put my phone in stock recovery mode? I tried holding both volume keys down and power, it just powercycles. Even if let go on the second screen off. if I continue on holding - it just powercycles. If i hold vol down and power - it goes into download mode...
I have Clockwork installed. If I start recovery from ROM Manager it bypasses stock recovery straight to Cloclwork menu. I am trying to install battery percentage indicator, which I can only do thru stock recovery menu. How can I start stock rec mode?...
Also it says DO NOT INSTALL this lag fix http://forum.xda-developers.com/showthread.php?t=765820 using ROM MANAGER. So how can I install it then??
Click to expand...
Click to collapse
delete "update.zip" on internal sdcard. make sure to reinstall clockwork recovery again using rom manager after u r done.
make sure whatever ur installing is rename to update.zip for stock recovery to work.
for lagfix use this http://forum.xda-developers.com/showthread.php?t=751864
unzip it. connect ur phone with usb debugging. click lagfixme wait for it to prompt for superuser then it will do the rest for you
Kaik541 said:
adb is your friend. seriously, how have people on this forum not figured this out yet? (I don't actually even know how to reboot into recovery with just the buttons off the top of my head)
Sorry, I'd like to learne to use adb, I am a noob.
either "adb reboot recovery" or download "Terminal Emulator" from the marketplace type "su" and then "reboot recovery"
Click to expand...
Click to collapse
I knew I could do it using terminal emulator but I need to learn commands
akachay said:
delete "update.zip" on internal sdcard. make sure to reinstall clockwork recovery again using rom manager after u r done.
make sure whatever ur installing is rename to update.zip for stock recovery to work.
for lagfix use this http://forum.xda-developers.com/showthread.php?t=751864
unzip it. connect ur phone with usb debugging. click lagfixme wait for it to prompt for superuser then it will do the rest for you
Click to expand...
Click to collapse
Should I delete it from my internal after I have the battery indicator installed, should I get rid of that update.zip? I did a backup using ROM Manager before adding the battery indicator. So I have my former ROM and Current ROM backed up.
OMG, I've been going crazy trying to get my phone into boot screen all night. Thanks for this!
Rhiannon224 said:
I knew I could do it using terminal emulator but I need to learn commands
Should I delete it from my internal after I have the battery indicator installed, should I get rid of that update.zip? I did a backup using ROM Manager before adding the battery indicator. So I have my former ROM and Current ROM backed up.
OMG, I've been going crazy trying to get my phone into boot screen all night. Thanks for this!
Click to expand...
Click to collapse
yea delete update.zip(battery indicator). open rom manager to install your clockwork recovery which will automatically put an update.zip(clockwork recovery) back on ur sd card. thus "update.zip" is just a rename for whatever program/file.
Also there is an app called quick boot in the market. Its free and will take you to stock reboot and recovery without going through the whole hold power
And vol up and down at same time. Is super easy to use. It have icon on my phone next to rom manager so one will be clockwork recov, and the othe stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
Is there a way to make clockwork the default? I'm so used to using adb I do reboot recovery then go ARRRGH I wanted clockwork!
thanks guys!! I ended up using that app from the market. And renaming the battery zip file to update.zip
gunnyman said:
Is there a way to make clockwork the default? I'm so used to using adb I do reboot recovery then go ARRRGH I wanted clockwork!
Click to expand...
Click to collapse
reboot thru ROM manager, it will take you to Clockwork right away, right?
bmvik said:
reboot thru ROM manager, it will take you to Clockwork right away, right?
Click to expand...
Click to collapse
well yeah but I seem to be able to type ./adb reboot recovery faster
I have a kernel that replaces stock recovery with clockworkmod. I'm trying to work out whether I can actually distribute such a thing, and also how to incorporate downloading it into my kernel build script so that I don't need to include it with the sources.
Sent from my SAMSUNG-SGH-I897 using XDA App
Unhelpful said:
I have a kernel that replaces stock recovery with clockworkmod. I'm trying to work out whether I can actually distribute such a thing, and also how to incorporate downloading it into my kernel build script so that I don't need to include it with the sources.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm pretty sure Koush said he wanted this from the start. The reason he changed the way clockwork recovery works for our phones was because recovery and the system are handled by the same part of system code, unlike with other phones.
He wanted to make it available to be incorporated into other kernels/ROMs instead of relying specifically on his kernel (which is why the roundabout happened from earlier where he offered the stock kernel to revert to)
It doesn't use a custom kernel, it's started from an update.zip normally.
Sent from my SAMSUNG-SGH-I897 using XDA App
Does our recovery system work the way it does because of lack of fastboot?
Another idea. is there something we can add to build.prop or perhaps init.rc so a command such as adb reboot clockwork would work? Just spitballing here.
Unhelpful said:
It doesn't use a custom kernel, it's started from an update.zip normally.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Unless I'm mistaken, his original method did require a custom kernel or modified the stock kernel which is why he offered the stock kernel for people to reflash when he provided the final release.
Sent from my Samsung SGH-i897
I recently did a back up if my stock mt4g using clockwork. When I went to do a restore of that rom and rebooted it stayed stuck on the mt4g load screen. Anyone else have this problem? Did I do something wrong?
Sent from my HTC Glacier using XDA App
what version of clockwork did you use to make the backup?
3.0.0.5
Sent from my HTC Glacier using XDA App
spokenjeremy said:
3.0.0.5
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Welcome to brick world, that's exactly what destroyed my phone and, like you, I was running 3.0.0.5 If you ever do get the phone working again let me know how you did it, please?
Not sent from my MyTouch 4G because it's a brick now!
xs11e said:
Welcome to brick world, that's exactly what destroyed my phone and, like you, I was running 3.0.0.5 If you ever do get the phone working again let me know how you did it, please?
Not sent from my MyTouch 4G because it's a brick now!
Click to expand...
Click to collapse
The reason your phone appears to be bricked is it (CWRM 3.0.0.5) is a ext4 recovery image, and 2.2 is a ext3 ROM....
. If you find a 2.x version of CWRM you can flash it via the ADB commands and restore the phone.
OR
boot into recovery and flash the CM7 w/ gapps then download CWRM ( the free one ) and flash 2.x that way. You'll have to scroll to the bottom and select one of the 2.x recovery images.
If you can get into Recovery or into fastboot your phone is not truly bricked.
I have CM7 installed and Rom Manager, but when i try to flash an older recovery it says it cannot be flashed. How exactly would you flash the 2.X version via ADB? Thanks.
xs11e said:
Welcome to brick world, that's exactly what destroyed my phone and, like you, I was running 3.0.0.5 If you ever do get the phone working again let me know how you did it, please?
Not sent from my MyTouch 4G because it's a brick now!
Click to expand...
Click to collapse
You nor he is bricked.
Pentlander said:
I have CM7 installed and Rom Manager, but when i try to flash an older recovery it says it cannot be flashed. How exactly would you flash the 2.X version via ADB? Thanks.
Click to expand...
Click to collapse
If you can get into CwM recovery then just flash my zip and use the 3.0.0.6 recovery that is included. Then make sure that you make/restore all backups from recovery and not rom manager. Rom manager is not compatable with CwM 3.0.0.X when it comes to making nandroids.
Thanks a lot, but i keep running into and issue at the recovery. I followed the instructions from your thread, and i got into the blue recovery screen, but it says
"E:Can't mount CACHE:recovery/command
E:Can't mount DATA:data/recovery/log"
And the only option to restore is the Applysdcard:update.zip and that fails
Pentlander said:
Thanks a lot, but i keep running into and issue at the recovery. I followed the instructions from your thread, and i got into the blue recovery screen, but it says
"E:Can't mount CACHE:recovery/command
E:Can't mount DATA:data/recovery/log"
And the only option to restore is the Applysdcard:update.zip and that fails
Click to expand...
Click to collapse
So, that is the stock recovery. You need to choose the 3.0.0.5 version from "All ClockworkMod recoveries" if using my zip. If that wont work, try sending a new recovery via fastboot or terminal emulator.
You can set up adb/fastboot by checking out the link in my sig and using the command (make sure you rename the recovery to recovery.img for ease of use)
Code:
fastboot flash recovery recovery.img
or you can try terminal method by placing the recovery on your sd card and renaming it recovery.img Then open up TE and type "su" then the flollowing
Code:
flash_image recovery recovery.img
If that doesnt work, then let me know and we will find some other things to try.
Whoops haha. Thanks for all the help it's working great now
Pentlander said:
Whoops haha. Thanks for all the help it's working great now
Click to expand...
Click to collapse
What step got it working again for you?
neidlinger said:
The reason your phone appears to be bricked is it (CWRM 3.0.0.5) is a ext4 recovery image, and 2.2 is a ext3 ROM....
If you can get into Recovery or into fastboot your phone is not truly bricked.
Click to expand...
Click to collapse
Can't do either.
UPDATE: To fix 3.0.2.4 from not formatting /system
Open rom manager and select settings, and check erase recovery. hit menu again and select clear cache, then flash 3.0.2.4 again.
now if your in recovery and you cant boot back up to use rom manager, use the file below. It will allow you to restore your backup then once booted back up use the method above to fix 3.0.2.4.
The reason im leaving custom over 3.0.2.4 is bc i know fastboot flash with this one will allow you to restore without wiping recovery or clear cache or anything else.
http://www.mediafire.com/file/b8ejhqbf3tgnsoe/recovery.img - this is CMW 3.0.1.4 just altered for installing zips. linking for people needing a recover img to boot up
To install:
1. If in recovery, open ur terminal on ur pc and type adb reboot boatloader
2. Once in bootloader it will load fast boot and say fastboot usb in red
3. cd to the folder with fastboot.exe and also place recover.img in that folder
4. then enter fastboot flash recovery recovery.img
5. adb reboot recovery
6. restore your backup and boot up
RafficaX said:
Little FYI for all, cwm recovery wont format system on a restore. made a backup, tried a flash and went to restore and it fails formatting system.
So be careful with flashing and all bc yo may not be able to restore currently with cwm.
UPDATE: format system in menu also fails! be careful bc you pretty much cant restore or flash atm!
Click to expand...
Click to collapse
Oh how I miss Amon_Ra
jlevy73 said:
Oh how I miss Amon_Ra
Click to expand...
Click to collapse
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
RafficaX said:
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
Click to expand...
Click to collapse
QFT
can't wait for amon-ra
raffica, what version of CWM worked for you?
MYxdaUSERNAME said:
raffica, what version of CWM worked for you?
Click to expand...
Click to collapse
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Thanks for the heads up I agree I always loved CWM on my N1 but it started giving me all kinds of grief for several different reasons so I finally went to Amon Ra.
RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
Can you help me out and provide it because right now i cant even boot
RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
superchilpil said:
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
Click to expand...
Click to collapse
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
nosympathy said:
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
Click to expand...
Click to collapse
See that's what I thought, but wasn't sure
Sent from my ADR6300 using XDA Premium App
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
jgrimberg1979 said:
Can you help me out and provide it because right now i cant even boot
Click to expand...
Click to collapse
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically and I followed the steps from 7 on to regain root. Worked for me, but now I have to start over. Hopefully they will get CWM working again. I will be much more careful about what I delete from now on. I think I will freeze it in TiBackup first to make sure everything is still working correctly. Hope this helps.
lynseyw said:
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically
Click to expand...
Click to collapse
This is the exact procedure I used when the same thing happened on my N1
i added the recovery.img i used to OP with instructions for those stuck in recovery or bootloader.
jeffnucci said:
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
Click to expand...
Click to collapse
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
miketoasty said:
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
My battery died and am in the same position. Got an expensive paperweight at the moment. I'll try to get another battery today and give this a try. After fooling around with it last night, the computer wouldn't even recognize the phone. Ughh!
RafficaX said:
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
Click to expand...
Click to collapse
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
miketoasty said:
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Where did you get 3.2? 3.0.2 you mean?
I have hacked my phone and successfully rooted it with the help of AlpharevX and the guide to root by Nejc. But after that everything is fine except onething. While the phone is charging and I turn off the phone then the red led continues to light up even when i disconnect the cable. And after that the power button does not work until i reinsert the battery... Earlier before rooting and S-off this did not use to happen. Please help!
Flash clockworkmod recovery 3.1.0.2 or +.
Sent from my HTC Wildfire using XDA App
bharatgaddameedi said:
Flash clockworkmod recovery 3.1.0.2 or +.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
pls help how to flash a recovery, i do it through rom manager and update to 3.x.x.x, but i can only access that recovery through rom manager and when i try to access recovery through fastboot (or whatever its called) or reboot in recovery i end up with clockworkmod 2.5.0.1 recovery. help!
Pls see the below thread "What I like being rooted."
Can't type it once again.
Sent from my HTC Wildfire using XDA App
thank you for your help but where can i find Flash clockworkmod recovery 3.1.0.2 or + for htc widfire
You can find the Recovery.img file here:
http://forum.xda-developers.com/showthread.php?t=1014498
This file needs to be flashed in HBoot or through pc by flash commands?
saurabhr2 said:
This file needs to be flashed in HBoot or through pc by flash commands?
Click to expand...
Click to collapse
Can be done in both ways.
When through hboot menu, the recovery.img along with android-info.txt are to be packed into a zip file named PC49IMG.ZIP and kept at the root of memory card.
When from fastboot flash the recovery.img is to be kept in folder where fastboot.exe lies and use it with android sdk. The command is already said.
Sent from my HTC Wildfire using XDA App
I also suffer from an unusual problem. After installing clock work mod recovery and rooting ....I decided to factory reset my phone(God knows what made me do this). And When It rebooted then 2 things dont work the htc scenes and the setup app. It is not leading to any other problem ( I can live with it) but still I would like to remove this problem..... No matter what i do or how many times i restarted the phone these 2 things just dont work
I did not take part in making this recovery at all, I am just posting it.
Before flashing the recovery flash this first to clear up some memory for it. (thanks to James Sullins for the file)
The instructions and download are in the link below:
http://teamw.in/project/twrp2/75
I will have more support for this recovery once I get the tp(getting it soon)
brigked said:
I did not take part in making this recovery at all, I am just posting it.
The instructions and download are in the link below:
http://teamw.in/project/twrp2/75
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Let's see if it's worth it...
Sent from my SGH-I777 using Tapatalk
ceo.mtcl said:
Let's see if it's worth it...
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
It is definitely pretty nifty. Downloaded and installed last night just as it came out.
ceo.mtcl said:
Let's see if it's worth it...
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
lol, worth it? it's the mac daddy of recoveries.
i need to remove some stuff from /boot to get this installed. anyone know what i can get rid of?
contents of /boot
uimage.clockworkmod
moboot.splash.webos.tga
proc
dev
moboot.default
bin
lost+found
config-2.6.35-palm-tenderloin
etc
usr
boot-genesis.tar.gz
uimage-2.6.35-palm-tenderloin
updatefs-info
sbin
genesis-update.xml
.
boot-image.tar.gz
lib
uimage.cyanogenmod
image-update.xml
uimage.webos
sys
moboot.splash.cyanogenmod.tga
..
boot.bin
uimage
uimage.moboot
system.map-2.6.35-palm-tenderloin
realroot
update-uimage
_________________________
update: i removed update-uimage. it was also the largest thing in there. checking out twrp now.
b.huss2 said:
i need to remove some stuff from /boot to get this installed. anyone know what i can get rid of?
contents of /boot
uimage.clockworkmod
moboot.splash.webos.tga
proc
dev
moboot.default
bin
lost+found
config-2.6.35-palm-tenderloin
etc
usr
boot-genesis.tar.gz
uimage-2.6.35-palm-tenderloin
updatefs-info
sbin
genesis-update.xml
.
boot-image.tar.gz
lib
uimage.cyanogenmod
image-update.xml
uimage.webos
sys
moboot.splash.cyanogenmod.tga
..
boot.bin
uimage
uimage.moboot
system.map-2.6.35-palm-tenderloin
realroot
update-uimage
_________________________
update: i removed update-uimage. it was also the largest thing in there. checking out twrp now.
Click to expand...
Click to collapse
Can upost your updated zip
Sent from my Touchpad using xda premium
I use the zip method through recovery and now I cannot boot twrp says invalid size and clockwork will not boot either
Sent from my PC36100 using xda premium
Crsdr37 said:
Can upost your updated zip
Sent from my Touchpad using xda premium
Click to expand...
Click to collapse
there is no updated zip. that was the contents of my /boot partition on my touchpad. i read in another forum that i could remove that file that was taking up all the partition space. i tried to flash the twrp zip file and it flashed but could not boot into twrp recovery, so i pulled the file from /boot and noticed it was too small so it didn't flash complete because of no more room. i removed "update-uimage" and pushed "uimage.twrp" and now all good. after messing around in twrp for a bit i decided to go back and remove clockworkmod too
b.huss2 said:
there is no updated zip. that was the contents of my /boot partition on my touchpad. i read in another forum that i could remove that file that was taking up all the partition space. i tried to flash the twrp zip file and it flashed but could not boot into twrp recovery, so i pulled the file from /boot and noticed it was too small so it didn't flash complete because of no more room. i removed "update-uimage" and pushed "uimage.twrp" and now all good. after messing around in twrp for a bit i decided to go back and remove clockworkmod too
Click to expand...
Click to collapse
I was able to update to TWRP, however, after reboot and chosing recovery, it doesnt automatically get into TWRP like it used to do with CWM. Is there a way to get this to automatically get into TWRP without having to select it from moboot menu?
dallas.maverick said:
I was able to update to TWRP, however, after reboot and chosing recovery, it doesnt automatically get into TWRP like it used to do with CWM. Is there a way to get this to automatically get into TWRP without having to select it from moboot menu?
Click to expand...
Click to collapse
Mine never went to cwm automatically. I always had to choose it from the menu. If there is a way to do this I would like to know as well.
b.huss2 said:
Mine never went to cwm automatically. I always had to choose it from the menu. If there is a way to do this I would like to know as well.
Click to expand...
Click to collapse
With CWM as the only recovery, whenever you press and hold the hardware power off button, you get an option to reboot and when selecting that, if you chose reboot into recovery, with CWM, it will take you straight into recovery. With TWRP, it doesn't. Anyone who still has CWM only can test this, but it would be nice if we can get same thing work with TWRP. For now, I have removed CWM completely from my touchpad and am using TWRP only.
dallas.maverick said:
With CWM as the only recovery, whenever you press and hold the hardware power off button, you get an option to reboot and when selecting that, if you chose reboot into recovery, with CWM, it will take you straight into recovery. With TWRP, it doesn't. Anyone who still has CWM only can test this, but it would be nice if we can get same thing work with TWRP. For now, I have removed CWM completely from my touchpad and am using TWRP only.
Click to expand...
Click to collapse
Yea, I am familiar with the reboot menu, and with cwm as my only recovery it never did that for me. I always had to choose it from the moboot menu. At least as long as I can remember anyway.
Incorrect uimage size.?? Tried acmeinstaller and cwm zip
Sent from my Touchpad using xda premium
op updated with zip to remove the update-image prior to flashing the recovery
Ok so if you have already flashed the initial zip and it gives incorrect size any way to remove that? I did the acmeuninstaller and the option for twrp was still there after reflashing with just cwm
**Edit- Went into CWM flashed the clean boot zip and then reflashed twrp and we are in business this is a kick ass recovery.**
I think the Team Win site is down. Is anyone having problems with the link?
Sychodrama said:
I think the Team Win site is down. Is anyone having problems with the link?
Click to expand...
Click to collapse
No problem here
Sent from my Nexus S 4G using xda premium
Sychodrama said:
I think the Team Win site is down. Is anyone having problems with the link?
Click to expand...
Click to collapse
Yeah, the site went down yesterday (at least for me), but I used a cached page of it and the direct download links still worked.
As the site is down, what exactly is this version?
Thread Closed as an official one was opened.
Jug6ernaut