If you are a root user, you probably know what recoveries are, and you probably know what CWM and TWRP are. If you don't, please Google it, since this thread isn't about what recovery is...
I've been using CWM since my first Android device, Nexus S. However, after I switched to Galaxy Nexus, I've noticed this new recovery, which was TWRP, Team Win Recovery Project (Correct me if I'm wrong ).
Since I've used both as my daily recovery, I thought it'll be helpful for people to create a thread that compares these two
TWRP:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CWM:
These are version of recovery that I'm going to compare:
CWM version 6.0.1.0 Touch version for Galaxy Nexus
TWRP 2.2 for Galaxy Nexus
UI
Let's start with User Interface of these two recoveries. TWRP offers this fresh look that is not only easy to use, but also very intuitive. It has these big, yet polished buttons that makes using it a pleasure. I personally think that the UI is one of the strongest points of TWRP. CWM, on the other hand is just simple. It is just lines of options. For some, this might be great, but for a lot of people, including myself, it just not polished.
Navigation
Navigation is probably one of the most important elements of recoveries. TWRP offers really great navigation. Its "Swipe to Confirm" is one of my favorite, since this reduces the chance of flashing or wiping by mistake. It also offers this Back and Home button, which looks very familiar. CWM offers just easy-to-use navigation. That's it. Nothing too complicated. I find CWM to be just pick-it-up and flash kind of recovery.
Features
Now this is where TWRP shines big time. It offers soooooo many to the table than CWM. It has built in keyboard for naming backups and such. It has built in terminal, which can be pretty useful. It has built-in battery indicator and time, which is really handy. It also has built in file manager. It does all that with "basic features" such as flashing zip, factory resetting, mounting, and backup and restore. CWM just offers basic featues, nothing more. Of course, not a lot of people are gonna use terminal or file manager on recovery, but it is good to have a choice.
Compatibility
This is where CWM shines big time. Since, CWM was the only recovery until TWRP showed up, every mod and ROM is designed for CWM. Of course, since I am comparing Touch version, I have to mention that handful of mods doesn't work on CWM touch and only works on non-touch. This doesn't mean TWRP is only compatible with handful of mods. TWRP also works on most of the mods, but if there's a mod that you really want but only works on CWM, that can be a real pain in the rear end. Also I don't know if this also happens on other devices, but for Galaxy Nexus, if you want to flash stock ROM from Google developer site, TWRP won't let you.
Verdict
So which one is better? That's your personal opinion. Plus, I didn't create this thread to say which one is the best. I only created this thread so you guys know what each recoveries is right for you. I personally find CWM to be a little more stable and I find that CWM just works. However, TWRP offers these new and fresh features that advanced, and even just basic users and appreciate, but I still find that TWRP needs to work on some parts.
So which recovery do you use? I would like to know
I use TWRP for pretty much one reason only, it can mount through USB, which cwm can't do on the one s. Other than that I don't really find much difference in use, except that naming backups directly from recovery is nice
Sent from my HTC One S using xda app-developers app
Habarug said:
I use TWRP for pretty much one reason only, it can mount through USB, which cwm can't do on the one s. Other than that I don't really find much difference in use, except that naming backups directly from recovery is nice
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Oh there's no mount option on one s? You positive? Clockworkmod touch on galaxy nexus has that feature under mount I think. I can use adb to push files to the sdcard directory
Swyped on my Galaxy Nexus running AOKP nightly with Franco Kernel, overclocked to 1.4GHz
kyokeun1234 said:
Oh there's no mount option on one s? You positive? Clockworkmod touch on galaxy nexus has that feature under mount I think. I can use adb to push files to the sdcard directory
Swyped on my Galaxy Nexus running AOKP nightly with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
It's there, it's just that it does not work at least it did not work. I switched to twrp because of this and have never found a reason to switch back. On some units twrp also makes you able to flash boot through recovery (we don't have s off) but that doesn't work on mine.
Sent from my HTC One S using xda app-developers app
Habarug said:
It's there, it's just that it does not work at least it did not work. I switched to twrp because of this and have never found a reason to switch back. On some units twrp also makes you able to flash boot through recovery (we don't have s off) but that doesn't work on mine.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Haha ok
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
kyokeun1234 said:
I only created this thread so you guys know what each recoveries is right for you.
Click to expand...
Click to collapse
Should you not include 4EXT Recovery then also? That could be the right recovery for somebody.
kyokeun1234 said:
So which recovery do you use? I would like to know
Click to expand...
Click to collapse
Currently on 4EXT but wondering if I should go back to CWM.
Kavrocks said:
Should you not include 4EXT Recovery then also? That could be the right recovery for somebody.
Currently on 4EXT but wondering if I should go back to CWM.
Click to expand...
Click to collapse
Oops, I forgot 4ext :/ my apologies, but I never tried it, so I really can't give my opinion on it.
Swyped on my Galaxy Nexus running AOKP nightly with Franco Kernel, overclocked to 1.4GHz
Hello there !
I got question which could be silly for most of you but I really appreciate if someone would be nice to clear that for me.
When I want to do nandroid backup in clockworkmode recovery, everything is clean and simple. And backup folder is quite small. e.g. For Haier w910 that folder is about 25mb. And everything is saved. I can do wipe data formating and when I want back my earlier rom he is there with all settings and customisations.
When I try same thing to do through TWRP (on Huawei g510) I get few options for backuping. But if I want to backup all system and data and rom, TWRP shows me about 850mb.
Is there any options in TWRP to do nandroid backup of all system like in CWM Recovery ?
Thanks infront !
Good comparison.Anyway I love TWRP:laugh:
Another big plus for TWRP : its abitity to charge the battery.
MrAzerty said:
Another big plus for TWRP : its abitity to charge the battery.
Click to expand...
Click to collapse
Doesn't CWM do this as well? At least I've never noticed any battery drain when plugged in.
MattKneale said:
Doesn't CWM do this as well? At least I've never noticed any battery drain when plugged in.
Click to expand...
Click to collapse
Yup cwm also let the phone charge. Twrp just shows the battery percentage
Sent from my Nexus 4 using Tapatalk
Related
Close thread
charlieb620 said:
Ok. These are the only roms that load on my mytouch 4g.
RoyalThunder
IceGlacier
CM7
The rest of the roms just hang at the bootsplash and i have to pull battery and restore to previous rom.
Click to expand...
Click to collapse
Make sure tour using clockwork 3.0.0.6
Sent from my HTC Glacier using XDA Premium App
Do some reading. You are using the wrong recovery version for the roms you are flashing.....
Sent from my HTC Glacier using XDA App
Umm, well, he said icedglacier works (2.2) and cm7 (2.3) so I don't see how he can be using the wrong recovery.
lowandbehold said:
Umm, well, he said icedglacier works (2.2) and cm7 (2.3) so I don't see how he can be using the wrong recovery.
Click to expand...
Click to collapse
the problem exists between the phone and the couch.
op, review your process and try again.
mark manning said:
Make sure tour using clockwork 3.0.0.6
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
I have 3.0.0.6 loaded already. What should I try next?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC Glacier using XDA Premium App
darinmc said:
the problem exists between the phone and the couch.
op, review your process and try again.
Click to expand...
Click to collapse
I really don't understand what my quote had to do with your post...but ok. Like I said, the poster (not myself) is on 3.0.0.6, and if the other people would have read his original post they would have realized that since he said both froyo and gingerbread ROM's are working.
Now, are you doing a full wipe before trying a different ROM, and if so, are you going into mounts and storage and formatting boot and system? It's not always a requirement of flashing a ROM, but might solve your problem.
ok i tried that after i flashed cm7 now when i try to restore back into my iceglacier or my thunderbolt rom my phone just hangs what do i need to do to restore my backups properly right now my phone only boots into cm7 do i have to downgrade my clockwork recovery in rom manager or something?
lowandbehold said:
I really don't understand what my quote had to do with your post...but ok. Like I said, the poster (not myself) is on 3.0.0.6, and if the other people would have read his original post they would have realized that since he said both froyo and gingerbread ROM's are working.
Now, are you doing a full wipe before trying a different ROM, and if so, are you going into mounts and storage and formatting boot and system? It's not always a requirement of flashing a ROM, but might solve your problem.
Click to expand...
Click to collapse
he could have used 2.5.1.x to flash his first two ROMs, upgraded to 3.0.0.5 and flashed CM7, then tried flashing other froyo ROMs to no success. But that's beside the point. I don't know why I quoted you other than to point out that you made a lot of assumptions about what he did or didn't do and yet questioned the assumptions of others. The biggest problem is that very little information was given, forcing people to fish for info like we are playing fix his phone pictionary. Usually when someone doesn't give a lot of information about a problem it's because they didn't take the time to learn about what they were doing like they should have...
to op, if you want people to take the time to help you, take the time to explain what you did and what went wrong.
darinmc said:
he could have used 2.5.1.x to flash his first two ROMs, upgraded to 3.0.0.5 and flashed CM7, then tried flashing other froyo ROMs to no success. But that's beside the point. I don't know why I quoted you other than to point out that you made a lot of assumptions about what he did or didn't do and yet questioned the assumptions of others. The biggest problem is that very little information was given, forcing people to fish for info like we are playing fix his phone pictionary. Usually when someone doesn't give a lot of information about a problem it's because they didn't take the time to learn about what they were doing like they should have...
to op, if you want people to take the time to help you, take the time to explain what you did and what went wrong.
Click to expand...
Click to collapse
phone was shipped to me with cm7 rc3 on it. i flashed thunderbolt rom made a backup and than flashed ice glacier and made a back up. i tested out another gingerbread rom and didnt like so i wanted to go back to my thunderbolt rom. i went into cwm and picked restore backup. the whole process went but now my phone just hangs at the mytouch screen. the only thing im able to do now is boot back into cm7. it seems like i can only boot into gingerbread now.
are you wiping data at all? wiping cache partition and dalvik cache? I've never seen ROM Manager show 3.0.0.6, and since I don't have RM Premium out of curiosity is that the lastest version? How did you get the 3.0.0.6 recovery on your phone? Have you done all backup/restore from Rom Manager, or did you manually go into recovery? Did you follow the directions in the op of the ROM you were having trouble installing or did you just flash? by "boot back into CM7" do you mean restore your CM7 backup? what do you mean by "another gingerbread ROM?"
Answer these questions and someone MIGHT be able to begin to understand your problem enough so that they can help you.
My understanding is CW 3.0.0.6 is just a modified version of 3.0.0.5 to allow us to flash both Ext 2 and Ext 4. It's readily available in this forum.
Sent from my HTC Glacier using Tapatalk
charlieb620 said:
phone was shipped to me with cm7 rc3 on it. i flashed thunderbolt rom made a backup and than flashed ice glacier and made a back up. i tested out another gingerbread rom and didnt like so i wanted to go back to my thunderbolt rom. i went into cwm and picked restore backup. the whole process went but now my phone just hangs at the mytouch screen. the only thing im able to do now is boot back into cm7. it seems like i can only boot into gingerbread now.
Click to expand...
Click to collapse
darinmc said:
are you wiping data at all? wiping cache partition and dalvik cache? I've never seen ROM Manager show 3.0.0.6, and since I don't have RM Premium out of curiosity is that the lastest version? How did you get the 3.0.0.6 recovery on your phone? Have you done all backup/restore from Rom Manager, or did you manually go into recovery? Did you follow the directions in the op of the ROM you were having trouble installing or did you just flash? by "boot back into CM7" do you mean restore your CM7 backup? what do you mean by "another gingerbread ROM?"
Answer these questions and someone MIGHT be able to begin to understand your problem enough so that they can help you.
Click to expand...
Click to collapse
I am not sure what you have going on but I too havent ever seen Rom Manager show 3.0.0.6 but I too dont have the premium version. I saw you posted in my thread but you left alot of stuff out of your post. Like that you were having trouble flashing roms. My suggestion would be to download the latest rom manager and then download and flash the zip from my thread. Then replace your recovery with that one and try flashing some roms. Also if you have tried flashing Royal Glacier and cant, you can also check and make sure that the MD5 sums match with whats in the OP of the thread and your downloaded rom. I will be happy to try and help in any way I can. If you still cant get it then we need to get you set up with adb and have you send a logcat so I can try and see whats going on during boot.
You are most likely not running 3.0.0.6.
3.0.0.6 should have orange text where as 3.0.0.5 has green text.
cw 3.0.0.6 is technically not released yet and would not show up in the rom manager as in your pic. Something just seems weird with that. I do have the premium version as well, and have never seen that. I attached a thumbnail below for you to reference.
If for some reason you do have 3.0.0.6 installed re-download it and re-flash the image. That should take care of your problem.
I figured it out.
charlieb620 said:
I figured it out.
Click to expand...
Click to collapse
Mind sharing the answer?
hello....
i had this version 4.0.1.5 , and i had 3 problems...
-lose of performance
-much hotter sensation
-didnt charge my drain ZERO battery (it charges on power off, but you have to have some juice on battery)
DOWNLOAD 4.0.1.4 --> http://www.multiupload.com/UCJYHKQH23
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's the link to 4.1.0.4 so I can get it. I kinda wondered about that to. Thanks for the heads up.
Can't kind 4.1.0.4 in ROM Manager. Need a link to it possibly.
EDIT: NVM got it. It's in the stickies
Sent from my HTC Sensation Z710e using XDA Premium App
ronaldramsayii said:
What's the link to 4.1.0.4 so I can get it. I kinda wondered about that to. Thanks for the heads up.
Can't kind 4.1.0.4 in ROM Manager. Need a link to it possibly.
EDIT: NVM got it. It's in the stickies
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
DOWNLOAD 4.0.1.4 --> http://www.multiupload.com/UCJYHKQH23
CWM 4.1.0.4 isn't also free of problems
CWM 4.1.0.4 is reported by many to make devices unable to charge when phone is switched off. I also suffered from the same problem and updated to 4.1.0.5, which works perfectly for me. No Lags at all..
Not charging issue may create huge problem, if any of your fren dont use sensation.
I've got Quadrant scores upto 2650 on my sensation using setcpu and real life performance is also very good.
sorry but can someone please just tell me the adb commands to put on the sightly older version of cwm. i want to have access to phone off charging just in case i run my battery down! thanks all!
pnyppon said:
CWM 4.1.0.4 is reported to make devices unable to charge when phone is switched off. I also suffered from the same problem and updated to 4.1.0.5, which works perfectly for me. No Lags at all..
Not charging issue may create huge problem, if any of your fren dont use sensation.
I got Quadrant scores upto 2650 on my sensation using setcpu and real life performance is also very good.
Click to expand...
Click to collapse
this 4.0.1.4 was modded day 3/08/2011, works 100%
I think the issue is how you can know beforehand if your phone will charge an empty battery or not. It seems some are reporting version 4.1.0.4 is working for them, while others say not for them, but version 4.0.1.5 works!
pnyppon said:
CWM 4.1.0.4 is reported to make devices unable to charge when phone is switched off. I also suffered from the same problem and updated to 4.1.0.5, which works perfectly for me. No Lags at all..
Not charging issue may create huge problem, if any of your fren dont use sensation.
I got Quadrant scores upto 2650 on my sensation using setcpu and real life performance is also very good.
Click to expand...
Click to collapse
That was with the original 4.0.1.4. The updated 4.0.1.4 released by AlphaRev fixes this problem and allows you to charge with the phone off. I actually had the problem where 4.0.1.5 didn't charge my phone's battery.
ah i forgot, to use this .zip i just put on /sdcard and reboot into bootloader
and itll flash new recovery from there, correct?
greves1 said:
ah i forgot, to use this .zip i just put on /sdcard and reboot into bootloader
and itll flash new recovery from there, correct?
Click to expand...
Click to collapse
No. Download ROM manager from market, and click install CWM on ROM manager, then it'll do the rest for you. [but CWM 4.0.1.5]. As i have no problems at all with 4.0.1.5, i would suggest you to use the latest versions..
no i just turned off my phone and it showed orange led when plugged in
i ran:
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
status came back "discharging"
so that means im not charging with phone off, even though orange led is showing.
so ill go back to 4.1.0.4
pnyppon said:
No. Download ROM manager from market, and click install CWM on ROM manager, then it'll do the rest for you. [but CWM 4.0.1.5]. As i have no problems at all with 4.0.1.5, i would suggest you to use the latest versions..
Click to expand...
Click to collapse
Yes, but I do, and so do many others.
One can check whether 4.0.1.5 is working for you (thanks to show-p1984). Switch phone completely off (ie not fastboot) or remove the battery and put back but leave switched off, connect to pc via usb and run the following cmd in adb:
Code:
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
If the device is indeed charging while off then adb should return: -
Code:
Charging
If not, as was the case for me it will show as Discharging. In that case use the updated version of 4.0.1.4 from the S-Off sticky and not from Rom Manager.
Edit: Beaten to the punchline again LOL
tested again offline with 4.1.0.4.
"Full" and green led is on!
it worked perfect
greves1 said:
sorry but can someone please just tell me the adb commands to put on the sightly older version of cwm. i want to have access to phone off charging just in case i run my battery down! thanks all!
Click to expand...
Click to collapse
Fastboot flash recovery recovery.img
Sent from my HTC Sensation 4G using XDA Premium App
4.0.1.5 worksfor me
Seems like 4.0.1.5 works for me.
Just tried adb commands, and shows its charging..
BTW i use asian version of sensation. Wht abt u guys??
Can anyone please explain how the heck a recovery can do this? It makes no sense at all.
TheDeadCpu said:
Can anyone please explain how the heck a recovery can do this? It makes no sense at all.
Click to expand...
Click to collapse
+1 here.. At first I thought you were talking about Rom Manager but using the letters CWM by mistake... so you're really saying that a different recovery changes the clocks used in the rom you normally load?
Seems impossible to me, the recovery is a different kernel + boot that only gets booted when... well.. when you boot it . Your hboot loads the kernel from your ROM _or_ the kernel from recovery, so I fail to see where recovery can impact the ROM you installed.
TheDeadCpu said:
Can anyone please explain how the heck a recovery can do this? It makes no sense at all.
Click to expand...
Click to collapse
+ 1
Very interested to see someone make a well argumented reply also. :\
i ran the command and got discharging
The only reason it would do this is if it didn't clear the recovery kernel when it reboots from recovery.. But I've checked and it does.. so..
Unofficial ClockworkMod 5.0.2.7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This will work on the Htc Hero S and Should on the Design 4g. I have tested it on the Hero S and can confirm basic functions work, adb and along with backups. Otherwise I haven't tested anything more than that. Also to note while building this the Hero S is identical to the Design 4g. So kernels and recovery should interchange. Beyond that I am not sure as I haven't got that far.
Also please note I am aware of the so called other cwm build and the teamwin recovery. I can confirm as grad said teamwin also works on the hero s. How ever since you can't download the cwm build, I took it upon myself to build one. In which means this shares nothing in common and was built from my own source. Which you can tell by the 2FS in the tittle.
Sorry for the crappy pic but due to frame buffer issues getting it to display right. Screenshots are blurred in recovery.
What is added/done:
Up to date source of 5.0.2.7
Default clockworkmod 5 colors.
Built on the evo design 4g stock kernel.
Ext4 support for sdcard.
Other features I have not tested fully but welcome to feedback.
How to install:
Download one of the following files:
http://2fastroms.com/dm_eds/download.php?id=72
Md5sum: c9e731f8228524d29a3acbd7811ba81c
Once downloaded place the PH44IMG.zip on the root of your sd-card. Power down the phone, Hold volume down, pressing power. You should got to the h-boot screen where it will scan for the img file. It will prompt to update by pressing volume up. It will take a few secs to do it's thing prompting to hit power to reboot.
Once rebooted remove the PH44IMG.zip from your sd-card.
Credits:
Koush for his great recovery with out him it wouldn't have been possible.
Then the cm team just for putting some great stuff out
Confirmed working on the Evo Design. Many thanks to 2fast for porting this over!
No problem, I see you got the link to work. How ever I had to port it so I could have it
As unlike any other cdma phone between you guys and uscc. The hero s is identical down to the kernel and partitions. So worked out for the better
I'm having problems getting into hboot for some odd reason. I hold volume down and press power and the phone just boots up normally. What the heck am I doing wrong? This is such a noob problem to have. I'm embarrassed to ask, but I can't get it right to save my life.
lol Welcome to gingerbread sense. When you power down it doesn't truely power down. Pop the bottom off and flip the lever up to pop the battery out a bit. Then try it. If you still don't get to h-boot let me know.
Actually, I turned fastboot off in Settings > Power and it worked just fine after that.
I did get an error while trying to flash recovery. I believe it said CID incorrent. Updated Failed. Press power to reboot. I'm going to redownload recovery and try again.
Sent from my *rooted* EVO Design using xda premium app
---------- Post added at 01:23 AM ---------- Previous post was at 01:08 AM ----------
Keep getting the same error: CID incorrent. Update Fail. Press power to reboot.
I've had better luck booting into hboot by restarting the phone and holding only the vol down button as soon as the screen shuts off.
HampTheToker said:
Actually, I turned fastboot off in Settings > Power and it worked just fine after that.
I did get an error while trying to flash recovery. I believe it said CID incorrent. Updated Failed. Press power to reboot. I'm going to redownload recovery and try again.
Sent from my *rooted* EVO Design using xda premium app
---------- Post added at 01:23 AM ---------- Previous post was at 01:08 AM ----------
Keep getting the same error: CID incorrent. Update Fail. Press power to reboot.
Click to expand...
Click to collapse
Are you unlocked? Also I wasn't aware of the fastboot setting it to off. How ever it is quicker to do a battery yank for myself or use adb. It is just a new feature of gingerbread.
Yea, I'm unlocked. Even says so at the top of the hboot screen. I had to do a battery pull like you suggested previous to get the token to work.
Sent from my *rooted* EVO Design using xda premium app
So this is a workable recovery for the design 4g? If so, what's really the point without any roms anyways?
really like it
Gotta start somewhere, bro. Now, we need kernel source and S-off to start making custom ROMs.
Takes time. Patience is a virtue.
Sent from my *rooted* EVO Design using xda premium app
chugger93 said:
So this is a workable recovery for the design 4g? If so, what's really the point without any roms anyways?
Click to expand...
Click to collapse
There are two alternate recoveries for this phone now. If the only thing you use a recovery for is installing ROMs, there isn't much of a point right now. Those of us who do kernel/ROM development and use the other features of the non-standard recoveries welcome them.
chugger93 said:
So this is a workable recovery for the design 4g? If so, what's really the point without any roms anyways?
Click to expand...
Click to collapse
What is the point of being smart? Then who said roms don't exist? On another note as said you have a recovery to flash stuff. That or do it the hard way.
Hamp are you still getting the error? If so I will have to play with the .txt in the zip file. Though not sure why it won't work for you but did the other design.
Yes, I still get the same error. I found this. http://forum.cyanogenmod.com/topic/21681-cid-incorrect-update-fail/
Not sure what to make of it, though.
Anyone think this goldcard trick might help? I've generated one, but can't seem to figure out what to do from here.
Sent from my *rooted* EVO Design using xda premium app
Would this fix the error and allow me to flash recovery?
http://www.addictivetips.com/mobile...out-hex-editing/comment-page-1/#comment-44936
Sent from my *rooted* EVO Design using xda premium app
That shouldn't be needed. I know the error though but confused why it flashed on the other design 4g and not yours. As I know it installs fine on the Hero and the one confirmed the Design. Which the cid shouldn't be different from yours to the his. At the top of you h-boot it does say unlocked right? If so inside the zip is a .txt in which the h-boot reads from. Which there is also a cid in it, so let me try to comment it out to see if it works.
How ever add me on gtalk at bk95ta391, since you have the issue and I don't. I will play with it and shoot it to you to try.
2fast4u88 said:
That shouldn't be needed. I know the error though but confused why it flashed on the other design 4g and not yours. As I know it installs fine on the Hero and the one confirmed the Design. Which the cid shouldn't be different from yours to the his. At the top of you h-boot it does say unlocked right? If so inside the zip is a .txt in which the h-boot reads from. Which there is also a cid in it, so let me try to comment it out to see if it works.
How ever add me on gtalk at bk95ta391, since you have the issue and I don't. I will play with it and shoot it to you to try.
Click to expand...
Click to collapse
Just wondering could his cid be different if he did a sim unlock???
Sent from my ROOTED HTC Evo Design 4G.
If I helped you please press thanks
just posting to say thanks, i just did a nandroid backup on my hero-s and it seems like everything works great
i rooted using the first version of frigid's tool right when it came out but i've been yearning for cwm and it's awesome to finally have it!
i'd be glad to test any ROMs or anything else that you come up with!
I can't sign in to Google Talk for some reason. Pretty sure I didn't remove anything related to that after rooting. I'm going to try a different SD card and see if that helps.
Edit: pretty sure I didn't do a sim unlock. I'll try it and see if that helps.
Sent from my *rooted* EVO Design using xda premium app
UPDATE 8-18-12: OFFICIAL CYANOGENMOD NIGHTLIES ARE UP.
Hey Guys, I haven't seen anyone post this yet so I figured I'd give it a shot. First and foremost, I take ABSOLUTELY NO CREDIT FOR ANYTHING IN THIS POST. Let it be known that none of this is my work and the purpose of this post is to consolidate information into an easy-to-follow guide. Also, I take no responsibility for any damage you do to your own phone. It's your responsibility to understand the risks involved and do your research before you make ANY modifications. If you'd like to use this guide for a project you're working on or another thread, that's fine with me. All I ask is that you give credit where it's due.
BEFORE WE START. If you cannot follow detailed instructions, please don't bother using this guide as you're only going to waste your own time as well as mine. I won't be answering any questions or providing support for problems that are clearly covered in the guide.
Now that we've achieved an unlocked bootloader, Cyanogenmod's team is already at work and has a build of CM10 up and running. (It's technically an alpha, but for me EVERYTHING works perfectly: data, wifi, bluetooth, GPS, MMS, camera, camcorder, the whole nine. The only thing I've found to NOT be working is NFC). The post can be found on both Cyanogenmod and Austen Dicken's Google+ page. Those can be found here:
https://plus.google.com/117962666888533781522/posts
A word of caution:
Since I'm not a Cyanogenmod developer, I have no control on the stability of their posted builds. So if you go through the guide and your MMS isn't working, there's not a whole lot I or anybody else can do for you at the moment considering these are still alpha builds. Although I mentioned everything works currently for me, I can neither guarantee this nor help you troubleshoot technical issues as I am not the developer of the ROM itself. On the other hand, if you have any questions or problems following the guide, I'm happy to help you out to the best of my ability.
For this to work, you must be ROOTED and have an UNLOCKED bootloader. I'm not going to make a super-detailed write up on how to achieve both of these, but here's a general outline of steps for those that are new here. If you're already rooted and have your bootloader unlocked, you can skip straight to step 4.
Pre-install:
First, BACKUP EVERYTHING. Do a nandroid backup and backup your apps and data in Titanium if desired.
Install the latest Samsung USB drivers so your phone and your computer don't have any connection problems. Those can be found here:
http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
on the bottom under Manuals/Downloads and then Software.
I highly recommend backing up your IMEI incase something goes wrong. I'm not going to cover that here, all info can be found in this post:
http://forum.xda-developers.com/showthread.php?t=1791291&highlight=backup
You have been warned.
You need to have your SD Card formatted to FAT32. exFAT WILL NOT WORK. So if you're like me and have a 64GB SD card, neither Android nor windows will let you format to FAT32 natively, so you have a few options.
Using command prompt within windows:
http://www.xoomforums.com/forum/mot...-format-sd-card-especially-64gb-fat-32-a.html
Use a disk management program like Acronis Disk Director (I think they may have a free trial but don't quote me on that).
http://www.acronis.com/homecomputing/products/diskdirector/
Then, you may want to Odin back to stock using the latest Samsung firmware. Now, you DO NOT need to Odin back to stock for the rest of this guide to work. But it should fix any 4G/3G data problems you may have been having on custom k-exec ROMs and I thought it was a good idea to start completely fresh now that we have total freedom. So if you were having bad experience on any custom ROMs with a flaky data connection or GPS taking a long time to lock, give it a try and see if it fixes things for you.
If you're going to give it a try, both the Odin program and stock Odin firmware can be found in this post:
http://forum.xda-developers.com/showthread.php?t=1755386
Download the latest version of Odin and the latest stock firmware version. Extract the Odin zip and load it up. Click the PDA button, find the stock firmware you just downloaded. Boot into download mode on your phone by powering down, then powering back up while holding the home and volume down buttons. Click start in the odin window. This process should take a while. After your phone reboots, get through the setup and dial *2767*3855#. Your phone will reset and you'll be COMPLETELY back to stock and any radio/hardware connection issues should be fixed. If you're still having problems let me know.
Now, to the fun part.
1. Root your phone.
NoxiousNinja's GS3DebugFSRoot Tool is the easiest and most foolproof way I've found. Read the directions in the post and follow the instructions in the command prompt window. Very easy and lightweight.
http://forum.xda-developers.com/showthread.php?t=1792342
As you continue throughout this process, pay careful attention to the prompts as it will ask you for [y/n] responses that you must confirm. After finishing, go into the newly installed Superuser app and on the far left panel, click where it says "tap to check for updates." Then click "update" on the bottom EVEN IF YOU HAVE THE NEWEST VERSION. I don't know why it works, but it does.
2. Flash a custom recovery.
Download mmmeff's EZ Recovery flashing app from the play store. Just search for "EZ Recovery" and you'll find it. Once installed, make sure you allow root access, then select "CWM 6.0.1.0" from the dropdown (NOT THE TOUCH VERSION AND NOT TWRP . It just makes it easier on everyone if something goes wrong. I can personally confirm that the touch version is incompatible. Some users are reporting TWRP is working fine, so you can try that at your own risk but I can't provide any support if it doesn't work for you since I haven't tried it myself.), make sure you have the "Recovery" toggle selected on the left, and click "flash recovery". Don't worry about rebooting yet as we still have a few things to do. The thread for the app can be found at:
http://rootzwiki.com/topic/29698-72...-recovery-flashing-app-ya-dingus/page__st__10
3. Unlock your bootloader.
I've also chosen to use mmmeff's Bootloader unlocking app from the play store for this guide as it is universally acceptable no matter what operating system everyone is running. In the play store, search for "GS3 EZ Unlock". Once installed, again make sure you allow root access and then click the HUGE button in the middle. It only takes a few seconds and then you're done. Thread is here:
http://rootzwiki.com/topic/32456-app-ez-unlock-easiest-way-to-unlock-your-bootloader/
4. Flash Cyanogenmod.
First, you'll need some downloads. You can use the Cyanogenmod 10 Alpha build or a nightly CM10 build.
Cyanogenmod 10 ALPHA build:
http://goo.gl/RYzHT
MD5: 3662de3c8942f19dc95ca911207b1602
CM10 Nightlies can be found at:
http://get.cm/?device=d2vzw
Jellybean GAPPS:
http://goo.im/gapps/gapps-jb-20120726-signed.zip
Mirror:
http://www.mediafire.com/?63l7wtwlc09923c
MD5: f62cfe4a827202899919fd932d5246d7
Put both of these zips on the root of your SD card.
Before you get all trigger happy, we need to do some things first.
For those of you who are new at this, I'll say it again, BACKUP EVERYTHING. This next step will wipe everything on your phone.
INSTRUCTIONS FOR FLASHING A NEW INSTALL OF CYANOGENMOD:
Now, boot into recovery (power off and then power back on while holding the home and volume up buttons) and wipe SYSTEM, DATA, CACHE (all can be found in Mounts/Storage menu), and DALVIK CACHE (can be found in advanced menu). A system wipe is not technically necessary but I did it just to make sure I didn't have any problems. Then, go into "install zip from SD card," then "choose zip from SD card". First, flash the Cyanogenmod zip, and after that finishes flash the Gapps zip. Go back a couple levels, click "reboot system now," and you're done!
INSTRUCTIONS FOR FLASHING AN UPDATED BUILD OF CYANOGENMOD
Now that you have a working install of Cyanogenmod, it gets a lot easier. If you're currently on the Alpha build and are switching to the new nightly builds, I would HIGHLY recommend you perform a FULL wipe including system, data, and both caches. Some people moved from the alpha to nightlies and were having problems so if you do a full wipe the first time you'll be fine. If you want to update from a nightly build to a newer nightly, all you should need to do is wipe both caches.
I hope this helped at least a few people, I tried to arrange it into as easy of a guide as I could. Please let me know if you see any problems or necessary changes and I'll try to keep this thread updated as new builds are upped. TO EVERYONE THAT IS NEW HERE, PLEASE DO NOT BUG DEVELOPERS WITH STUPID QUESTIONS REGARDING RELEASE DATES OR PROGRESS. I can assure you that they're working hard, we got a full release the day after our bootloader got unlocked. So be patient, nightlies and beta versions of CM and AOKP will come soon enough.
If you're interested, after you're done you can try flashing a new radio and/or kernel. Unless you're having problems, I wouldn't recommend you try this unless you know what you're doing because you could make things worse. Consider yourselves warned. Radios and instructions can be found in Invisiblek's thread here:
http://forum.xda-developers.com/showthread.php?t=1788313
Do some research on kernels, but at the time of writing I can recommend imoseyon's Leankernel. That and instructions are here:
http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v05-beta-81612/
N00bs, Both of ^these^ steps above are completely optional and if you do choose to try them THIS THREAD is NOT the place to ask for support. Realize that before you start messing with stuff you don't understand.
If this guide helped you out, please consider hitting the thanks button.
Thanks
As per request, here's some initial screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you shure nothing will go wrong if we follow the steps you described. By the way its a great step by step description to get cm10. Can you post some screenshots of your phone. Thank you
I am itching to try it lol
Sent from my SCH-I535 using xda premium
I tried the 8/15 yesterday but flashed back to stock mainly because the phone wasn't seeing my ext SD card. Also it died on me I had to do a battery pull to get it back. I may have to try this out. Also I could not get WiFi tether to work or the built in portable hotspot. It sucks too because I actually pay for the service
Sent from my SCH-I535 using Tapatalk
majmuni said:
Are you shure nothing will go wrong if we follow the steps you described. By the way its a great step by step description to get cm10. Can you post some screenshots of your phone. Thank you
I am itching to try it lol
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm in the process of getting some screenshots up, and I can't 100 percent confirm that it will work for you but if you follow the instructions I think theres a great chance
cell128 said:
I tried the 8/15 yesterday but flashed back to stock mainly because the phone wasn't seeing my ext SD card. Also it died on me I had to do a battery pull to get it back. I may have to try this out
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
What do you mean it "wasn't seeing it"? Didn't it show up in certain apps or recovery or what?
snoshreddax21 said:
I'm in the process of getting some screenshots up, and I can't 100 percent confirm that it will work for you but if you follow the instructions I think theres a great chance
What do you mean it "wasn't seeing it"? Didn't it show up in certain apps or recovery or what?
Click to expand...
Click to collapse
I think it was the music app and a bunch of photos
Sent from my Nexus 7 using Tapatalk
Do have a md5 for cm10 file please
Sent from my SCH-I535 using xda premium
Flashed and currently booting hopefully I keep it for a whole day lol. Do love the stock experience better than touchwiz
Sent from my Nexus 7 using Tapatalk
cell128 said:
I think it was the music app and a bunch of photos
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
You might try reformatting your card in your computer, but if that doesnt work I had a similar problem a while ago. For me I had to dig around in the preferences of my music player to direct it to the right folder (it would be mnt/extsdcard/[music folder]). It might be trying to find your music/pictures in the phone's internal memory rather than its SD card.
majmuni said:
Do have a md5 for cm10 file please
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It was in the post on Cyanogenmod's Google+ page, OP updated. Sorry about that
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
I'm almost postive TWRP is your problem. I first tried it with the CWM touch version and that didn't work for me either. I think CM10/CM9 are very picky about which recoveries are compatible. Let me know how it goes for you.
digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk
cell128 said:
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
i used the unlock that was mentioned in the guide as people were reporting it was successful unlocks on the forums so i went ahead and used that.....im making my initial backup right now thru CWM non-touch and im gonna drop the zips for CM10 and gapps and will flash in the morn, im tired lol
one thing i did notice though is that for some reason my drivers are saying hardware id missing, and that only happened after root......i kept my imei but lost my hardware id lmao, i can still drag/drop files onto my phone but i have to switch from MTP to PTP mode for usb settings then switch it back to MTP to get access to the card/phone drives
digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
cell128 said:
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Cell is correct, make sure you are using the "CWM 6.0.1.0" version. I'll update the OP so others don't get confused.
Thank you for your efforts OP.
Some friendly advice to you newer enthusiasts; be aware of bugs. If the CM team says this is an alpha build, you will more than likely hit some bugs regardless of what you read elsewhere.
Sent from my SCH-I535 using xda premium
jaj6503 said:
Thank you for your efforts OP.
Some friendly advice to you newer enthusiasts; be aware of bugs. If the CM team says this is an alpha build, you will more than likely hit some bugs regardless of what you read elsewhere.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
That's a very good point, and let's just clarify right now, I'm not a cyanogenmod developer and I don't have any control over how stable these builds come out. So if you flash and all is well except your MMS isn't working, I can't do anything for you and you're in the same boat as the rest of us. Thanks for bringing that up, jaj.
Sent from my SCH-I535 using xda app-developers app
I decided to flash tonight.....almost had a heart attack them woke everyone else up when i screamed when it flashed over lol.....great write-up man
Sent from my SCH-I535 using xda premium
digitalsynner85 said:
I decided to flash tonight.....almost had a heart attack them woke everyone else up when i screamed when it flashed over lol.....great write-up man
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Glad to hear it worked out for you
Sent from my SCH-I535 using xda app-developers app
since I have TWRP, how can I change it to CWM? I want to be able to flash this using CWM.
slick_shoes said:
since I have TWRP, how can I change it to CWM? I want to be able to flash this using CWM.
Click to expand...
Click to collapse
If you download the EZ Recovery app from the play store and flash CWM as mentioned in the guide, it will just overwrite the preexisting TWRP image and you can continue on from there.
I'm not understanding why the version or type of recovery matters. What does 6.0.1.0 do that twrp doesn't do except for supporting kexec?
Maybe I misunderstood what recoveries are all about. I had 6.0.1.0 for kexec support. Now that the bootloader is unlocked I'm thinking of going back to twrp.
Flashing the cm10 build should write to system and place a boot.img with the kernel on the phone. I don't see how a recovery would make a difference in doing this.
Forgive me if I missed something. I'm not questioning your intelligence or anything, just a curiosity as I only switched to cwm to use lean kernel with kexec.
Perhaps I missed even more, I see there is an alpha build of cwm that explicitly states it's for unlocked phones. Color me confused.
Sent from my SCH-I535 using xda app-developers app
Hey guys, I never really got into modding my TF101 for some reason (really into modding my Razr Maxx) and am way behind the curve now. I tried doing all the research myself but to be honest it's super confusing.
I see a ton of different CWM installers and CWM versions and can't figure out what to do as a lot of the threads are really old. Is there a specific CWM version I need to be on? Could someone suggest a good CWM installer?
Also, I noticed the thread warning not to use ROM Manager. But I also read an article over at AP stating that the TF101 is the first tablet to get official ROM Manager support. Is it still unsafe to use?
Any and all help is greatly appreciated!
I always recommend Peri: (http://forum.xda-developers.com/showthread.php?t=1681155)
I_EAT_BABIES said:
Hey guys, I never really got into modding my TF101 for some reason (really into modding my Razr Maxx) and am way behind the curve now. I tried doing all the research myself but to be honest it's super confusing.
I see a ton of different CWM installers and CWM versions and can't figure out what to do as a lot of the threads are really old. Is there a specific CWM version I need to be on? Could someone suggest a good CWM installer?
Also, I noticed the thread warning not to use ROM Manager. But I also read an article over at AP stating that the TF101 is the first tablet to get official ROM Manager support. Is it still unsafe to use?
Any and all help is greatly appreciated!
Click to expand...
Click to collapse
I never used ROM manager as I never needed it... I use a recovery called TWRP... you use what you prefer but don't install cwm 5.x.x.x as it doesn't include access to internal memory.. so if don't know recovery you r installing then cope and paste the custom ROM.zip file in internal memory as well as external so you have access and set up file on both... download twrp and and install it...
Sent from my Transformer TF101 using xda app-developers app
Ok so I tried to install both TWRP and Peri but neither worked.
TWRP -
Used the recommended Goo.im method, rebooted once then nothing happened. Tried to boot into recovery, and got the Andy laying down with an exclamation point screen.
Peri -
Used the command prompt method per the instructions, the script said that everything worked. Tried to boot into recovery, got the same exclamation point screen.
What am I doing wrong? Am I missing something? You're help is greatly appreciated guys.
I_EAT_BABIES said:
Ok so I tried to install both TWRP and Peri but neither worked.
TWRP -
Used the recommended Goo.im method, rebooted once then nothing happened. Tried to boot into recovery, and got the Andy laying down with an exclamation point screen.
Peri -
Used the command prompt method per the instructions, the script said that everything worked. Tried to boot into recovery, got the same exclamation point screen.
What am I doing wrong? Am I missing something? You're help is greatly appreciated guys.
Click to expand...
Click to collapse
Dude have you rooted your tablet? Do you have recovery access? If yes then what recovery is it? Is it cwm, twrp or rogue recovery?
Sent from my Transformer TF101 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:40 PM ----------
Go to the following link and follow the instructions... watch YouTube videos if you need to...
http://forum.xda-developers.com/showthread.php?p=26893961
Don't forget to download and install universal naked driver which is mentioned in the above link along with a download link for it...
Sent from my Transformer TF101 using xda app-developers app
Yes I have it rooted...
I can't get any recovery to install, every time I try to reboot into it I get the black screen with the droid laying on his back and a red triangle with an exclamation point inside.
I_EAT_BABIES said:
Yes I have it rooted...
I can't get any recovery to install, every time I try to reboot into it I get the black screen with the droid laying on his back and a red triangle with an exclamation point inside.
Click to expand...
Click to collapse
Download the software from above link and use it to install recovery from it.... it will install a recovery called rogue recovery.... but remember to read instructions......
Sent from my Transformer TF101 using xda app-developers app
I_EAT_BABIES said:
Hey guys, I never really got into modding my TF101 for some reason (really into modding my Razr Maxx) and am way behind the curve now. I tried doing all the research myself but to be honest it's super confusing.
I see a ton of different CWM installers and CWM versions and can't figure out what to do as a lot of the threads are really old. Is there a specific CWM version I need to be on? Could someone suggest a good CWM installer?
Also, I noticed the thread warning not to use ROM Manager. But I also read an article over at AP stating that the TF101 is the first tablet to get official ROM Manager support. Is it still unsafe to use?
Any and all help is greatly appreciated!
Click to expand...
Click to collapse
Having come from a different device I feel your pain. For someone new to the TF101 the whole recovery thing is confusing. Although I already have version 5.8.1.8 of CWM on it when I got it, I wanted a recovery that handled both the internal store and an external one. Rogue's CWM based recovery did it for me. Following is the link for it:
Team Rogue CWM based Recovery
OK So I am going to try the method you recommended, but I can't figure out how to install the naked drivers. Could you deal with me being an idiot and help me? I unzipped the files, deleted the drivers that the TF101 automatically installs, but now what?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I_EAT_BABIES said:
OK So I am going to try the method you recommended, but I can't figure out how to install the naked drivers. Could you deal with me being an idiot and help me? I unzipped the files, deleted the drivers that the TF101 automatically installs, but now what?
Click to expand...
Click to collapse
Connect your tablet and remove all Asus sync, Asus drivers and then go to device manager and uninstall and delete all Asus/old drivers.
Unzip the universal naked driver to a folder and Now click F5 and as soon as unknown device shows up install required drivers by manually pointing towards unzipped folder.
Once the installation is complete ( if it fails try again till it succeeds, if windows keep installing Asus software then right click in device manager and use update driver option) go to apx mode by pressing volume up n power buttons together.. windows should install apx driver if it can't then it will show as unknown device.. again go to device manager right click on unknown device and install manually by pointing the installation procedure again towards naked driver and you r set... now run easy flash, select recovery( use twrp) and flash it... I hope you understood...
Sent from my Transformer TF101 using xda app-developers app