What is the best way to install CWM on my TF300T, I am on the 4.2 bootloader, and I tried to put the CORRECT JB 4.2 version of TWRP 2.5.0 and it is like a split screen and will not function. Some time before that it asked for a password when I booted the recovery. I just want to start fresh with Clockwork Mod I guess.
Please point me in the correct direction.
Thank you
ScottBroker said:
What is the best way to install CWM on my TF300T, I am on the 4.2 bootloader, and I tried to put the CORRECT JB 4.2 version of TWRP 2.5.0 and it is like a split screen and will not function. Some time before that it asked for a password when I booted the recovery. I just want to start fresh with Clockwork Mod I guess.
Please point me in the correct direction.
Thank you
Click to expand...
Click to collapse
Not to be a douche but use the search function. And use twrp. Cwm is too buggy on the tf300. Its very easy for it to bug out and brick your pad.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mhays705 said:
Not to be a douche but use the search function. And use twrp. Cwm is too buggy on the tf300. Its very easy for it to bug out and brick your pad.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
well you are being a DB!
Do you not think I would search , too many posts with too many options.
TY for nothing. TWRP on TF3000T is very buggy btw.
ScottBroker said:
well you are being a DB!
Do you not think I would search , too many posts with too many options.
TY for nothing. TWRP on TF3000T is very buggy btw.
Click to expand...
Click to collapse
If you searched you would have seen all your questions are answered in the stickies. Also you would have seen twrp is recommended over cwm due to cwm bricking devices. I'm sure you would prefer that not to happen.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If anyone has some useful information, please let me know.
Thanks
ScottBroker said:
If anyone has some useful information, please let me know.
Thanks
Click to expand...
Click to collapse
First and foremost learn how to search. Its a damn stickied topic. Here is what your looking for took less than a minute to search. http://forum.xda-developers.com/showthread.php?t=2187982
If you learned to read you wouldn't have a double screened twrp.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have tried that and still get a split screen, that is why I want to just flash CWM.
I have looked at that thread as well..
ScottBroker said:
I have tried that and still get a split screen, that is why I want to just flash CWM.
I have looked at that thread as well..
Click to expand...
Click to collapse
Update to the most recent boot loader. I'm trying to tell you. You have to use twrp. Cwm bricks the tf300t while flashing ROMs. Everyone advises not to use it. I don't even think there's a guide here for it since its too much of a liability. If your getting a split screen you are doing something wrong. Reading everything and doing everything exactly right is the name of the game here. The tf300 is way to easy to brick. If your having problems just installing a custom recovery your best to just stay away from flashing on this device. You have to pay attention to boot loader version and firmware version or you are going to get errors. Your lucky you haven't hard bricked yet.
I know what I'm talking about. I didn't just fall off the turnip truck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mhays705 said:
Update to the most recent boot loader. I'm trying to tell you. You have to use twrp. Cwm bricks the tf300t while flashing ROMs. Everyone advises not to use it. I don't even think there's a guide here for it since its too much of a liability. If your getting a split screen you are doing something wrong. Reading everything and doing everything exactly right is the name of the game here. The tf300 is way to easy to brick. If your having problems just installing a custom recovery your best to just stay away from flashing on this device. You have to pay attention to boot loader version and firmware version or you are going to get errors. Your lucky you haven't hard bricked yet.
I know what I'm talking about. I didn't just fall off the turnip truck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the advise, but as you can see, I have almost 3 times the thanks than you have posts. But anyway, I have been flashing for years, I have had every Iphone, and every Galaxy and have not had problems like with the tablet. I like TWRP, I have the latest bootloader, I am on 4.2.....
Maybe I will just return to stock and start fresh again...
Thanks anyway
ScottBroker said:
Thanks for the advise, but as you can see, I have almost 3 times the thanks than you have posts. But anyway, I have been flashing for years, I have had every Iphone, and every Galaxy and have not had problems like with the tablet. I like TWRP, I have the latest bootloader, I am on 4.2.....
Maybe I will just return to stock and start fresh again...
Thanks anyway
Click to expand...
Click to collapse
FYI, I went back to stock, and reflashed, and now with your helpful guide, I am back on TWRP.
TY
ScottBroker said:
FYI, I went back to stock, and reflashed, and now with your helpful guide, I am back on TWRP.
TY
Click to expand...
Click to collapse
This is defiantly one of the most sensitive device to do everything on. Asus wasn't to friendly. Its like they want you to brick. And my bad about the rudeness extreme lack of sleep has made me very irritable.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Indeed flashing cwm is another way to brick the TF300. Lucky you didn't flash it.
The problem is that the latest bootloader changes the partition table on the TF300 - it makes /system larger in order to accommodate the larger Asus ROM. The issue is most of the legacy recoveries including the non 4.2 twrp and cwm don't understand this and thus the device becomes bricked as the partition table is now messed up.
sbdags said:
Indeed flashing cwm is another way to brick the TF300. Lucky you didn't flash it.
The problem is that the latest bootloader changes the partition table on the TF300 - it makes /system larger in order to accommodate the larger Asus ROM. The issue is most of the legacy recoveries including the non 4.2 twrp and cwm don't understand this and thus the device becomes bricked as the partition table is now messed up.
Click to expand...
Click to collapse
Gotta love sbdags knowledge and amazing rom
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Related
Ok so I have the update from Asus, I'm rooted with an unlocked bootloader and TW recovery on .17
Everytime I try and flash the zip, it fails. I have rootkeeper and I also tried flashing the second zip file that's inside the first zip. It fails almost immediately while verifying its size or whatnot.
I think I read that trying to flash CWM over TW could brick. Do I need to or is there a way to relock the bootloader?
Thanks guys!
Sent from my ADR6425LVW using xda premium
dopediculous said:
Ok so I have the update from Asus, I'm rooted with an unlocked bootloader and TW recovery on .17
Everytime I try and flash the zip, it fails. I have rootkeeper and I also tried flashing the second zip file that's inside the first zip. It fails almost immediately while verifying its size or whatnot.
I think I read that trying to flash CWM over TW could brick. Do I need to or is there a way to relock the bootloader?
Thanks guys!
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
You wont brick you're tablet if you switch recoveries, and you also don't flash them . Either way if your flashing stock Asus firmware in CWM read up and make sure you do it right. I bricked my tf300 trying to install the us .29 update. Haha
Sent from my ADR6300 using Tapatalk 2
Since you went through the trouble to help out the OP, I'll help you a bit. Technically, you do flash recoveries. How else would they get on the flash memory chips? Just because you don't flash recoveries through a recovery doesn't mean the process of installing them gets a new name.
Flashing = writing images/files to flash memory. How you do it doesn't matter.
I'm so sorry for my wording. guess I should have made it so a complete retard could follow what I was asking... I had zero time to write this question and just dumped it out there. Either way, I think you knew what I was saying. So yeah... thanks for the help! ← sarcasm? Naaaah....
Also, its kinda interesting how when you root devices using methods like ADB, to get a recovery.img on the system, the command is usually something like " fastboot FLASH recovery recovery.img "
Don't ya think...?
Sent from my ASUS Transformer Pad TF300T using xda premium
dopediculous said:
I'm so sorry for my wording. guess I should have made it so a complete retard could follow what I was asking... I had zero time to write this question and just dumped it out there. Either way, I think you knew what I was saying. So yeah... thanks for the help! ← sarcasm? Naaaah....
Also, its kinda interesting how when you root devices using methods like ADB, to get a recovery.img on the system, the command is usually something like " fastboot FLASH recovery recovery.img "
Don't ya think...?
Sent from my ASUS Transformer Pad TF300T using xda premium
Click to expand...
Click to collapse
I'm not sure how what I said was insulting, but I am quite sorry you took offense to what I said, and felt it was enough to call me a retard for. I do know that the file is flashed, but, like you I was short on time, and meant that you dont flash in in recovery. generally, unless its made to be a temp flash done in recovery.
At least EndlessDissent politely corrected me on my lack of abilty to communicate normally. and informed while doing it!
enomele said:
I'm not sure how what I said was insulting, but I am quite sorry you took offense to what I said, and felt it was enough to call me a retard for. I do know that the file is flashed, but, like you I was short on time, and meant that you dont flash in in recovery. generally, unless its made to be a temp flash done in recovery.
At least EndlessDissent politely corrected me on my lack of abilty to communicate normally. and informed while doing it!
Click to expand...
Click to collapse
All good man. Its not what ya say, its how ya say it and unfortunately via plain text, one can't really tell how ya meant to come off sounding. My apologies. Now can someone give me some guidance on how to get .29 on this thing? Lol
Sent from my ASUS Transformer Pad TF300T using xda premium
Have you checked the md5sum to make sure it matches the correct value? It could be a bad download.
EndlessDissent said:
Have you checked the md5sum to make sure it matches the correct value? It could be a bad download.
Click to expand...
Click to collapse
I haven't, just because I've downloaded it twice already. Just figured it had to be good by the second try :/
Are the md5's posted on the Asus site that ya know? Sorry. Still mad busy and can't check for myself just yet. I work for vzw corporate and we all know how slammed the retail locations can be. Ugh. Lmk if ya can. I appreciate everything you guys!
Sent from my ASUS Transformer Pad TF300T using xda premium
i flashed a stick rom and now getting unathorized software message on boot and cant get in to the phone, but I do have access to odin, am i screwed or what : (
moocowgal said:
i flashed a stick rom and now getting unathorized software message on boot and cant get in to the phone, but I do have access to odin, am i screwed or what : (
Click to expand...
Click to collapse
Go to my guide and follow section 6....also try reading a couple threads before posting. This the whole reason why verizon locked the darn bootloader in the first place. Research then flash, dont flash then research!!!
Edited for incorrect advice.
voodoomanx said:
http://forum.xda-developers.com/showthread.php?t=1762204
Download and flash root66 with odin. What stock rom gave you the triangle?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This is incorrect...you must flash the stock kernel before flashing a stock rom in odin. Op go to my guide and follow section 6.
I suggest doing a factory reset in recovery, immediately after you flash root66. My phone would not finish booting after ODIN'ing root66 coming from BeansRom 9. It was sticking at the Verizon 4g boot image for 20 minutes.
droidstyle said:
This is incorrect...you must flash the stock kernel before flashing a stock rom in odin. Op go to my guide and follow section 6.
Click to expand...
Click to collapse
Depends on what rom he flashed. That's why I asked. If he flashed a stock rom with stock kernel flashing root 66 in odin would work.
Sent from my SCH-I535 using xda app-developers app
voodoomanx said:
Depends on what rom he flashed. That's why I asked. If he flashed a stock rom with stock kernel flashing root 66 in odin would work.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Read the op...she is getting the verizon triangle of death...that means one thing, either she flashed a custom recovery via odin or flashed a custom rom that was packaged with a custom kernel on a locked bootloader. The advice you gave is incorrect for this situation. Im not here to argue, im here to help pass along correct information to keep bricks at a minimum. Sometimes i may come off a bit brash, but im just trying to get the point across. Seems silly to take a 600.00 device and turn it into a paper weight all because lack of research don it?
droidstyle said:
Read the op...she is getting the verizon triangle of death...that means one thing, either she flashed a custom recovery via odin or flashed a custom rom that was packaged with a custom kernel on a locked bootloader. The advice you gave is incorrect for this situation. Im not here to argue, im here to help pass along correct information to keep bricks at a minimum. Sometimes i may come off a bit brash, but im just trying to get the point across. Seems silly to take a 600.00 device and turn it into a paper weight all because lack of research don it?
Click to expand...
Click to collapse
All I did was ask what rom they attempted to flash. I don't care either way. Your guides have gotten me out of a couple jams. I wish people would read them first.
I'm also getting sick of all the warranty fraud going on.
Now that I reread the OP you are correct. I will edit my reply so as not mislead anyone.
Sent from my SCH-I535 using xda app-developers app
voodoomanx said:
All I did was ask what rom they attempted to flash. I don't care either way. Your guides have gotten me out of a couple jams. I wish people would read them first.
I'm also getting sick of all the warranty fraud going on.
Now that I reread the OP you are correct. I will edit my reply so as not mislead anyone.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
We all misread a post from time to time no biggie. You corrected me on a post in the ez unlock thread. The end result is to make sure the right information is getting passed around. :highfive:
Just saying. Nice catch droidstyle on saying "she" . I thought that was cool. Lol
Sent from my SCH-I535 using xda premium
Was gonna give TWRP recovery a try... I am currently using CWM and didn't know if it would be safe to just use the goo app and flash TWRP that way. I have always used CWM and wanted to try something new and just want to be safe when going about it.
Sent from my SCH-I535 using xda app-developers app
I tried it, but I didn't like much. To much switching pages to do things, such as format, erase cashed, and dalvic. But who knows you might just like it.
Sent from my SCH-I535 using xda app-developers app
Yes you can install TWRP any way you like. One recovery will simply overwrite the other. Nothing to worry about.
My only brick
The one time i ever truly bricked a phone after close to 30 times rooting and unlocking boot loaders was with TWRP and this phone. I am talkin complete brick, like qualcom drivers request show up on windows brick, the kind brick that you just throw at a window, because you got no charging light, no vibration, no light what so ever.
Btw i was only flashing a rom
I never touched TWRP after .
Thanks for the input guys..... Gonna stick with CWM for now. Seen a fair amount of negative stuff towards TWRP in the forums and don't want to risk anything.
Sent from my SCH-I535 using xda app-developers app
Been running TWRP since received pre-order device. No problems whatsoever.
prdog1 said:
Been running TWRP since received pre-order device. No problems whatsoever.
Click to expand...
Click to collapse
Seconded.
Used the gooapp to flash twrp and haven't had any problems. In fact I switched over from cwm because while installing liquidsmooth cwm kept giving me error 7. Everything I googled told me it was a problem with my recovery, so switched to twrp and presto
Although watch which version of twrp because I was reading the Cleanrom lite thread and ppl were having issues with the latest twrp at the time of their postings. It was around end of September that they were saying this, I believe.
Sent from my SCH-I535 using xda premium
prdog1 said:
Been running TWRP since received pre-order device. No problems whatsoever.
Click to expand...
Click to collapse
Thirded
prdog1 said:
Been running TWRP since received pre-order device. No problems whatsoever.
Click to expand...
Click to collapse
+1
Sent from my SCH-I535 using xda app-developers app
I used to use cwm and now have been using twrp and have never had a problem. This guy above you can't blame twrp for your brick you don't know if that's what it was. Twrp I like better cause I can move my backup folder and copy it even to another computer. Cwm has the blob folder which you can't see which files belong to which backup so you can't just move one backup you have do do them all
Tap'n
evolishesh said:
I tried it, but I didn't like much. To much switching pages to do things, such as format, erase cashed, and dalvic. But who knows you might just like it.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Don't know what you were looking out but CWM is the one where the wipes/format are on different pages. All wipe options in TWRP are on the wipe page right next to each other. Newest version now released.
Back in the day (droid eris days) there was cwm and twrp and twrp was thought of to cause more issues than anything so it was recommended to use cwm. Now it seems to have changed (at least regarding the gs3). Is this true? IS twrp that much better/stable/safer than cwm? I've never used twrp (have seen videos/screen shots) and it looks alot easier...well user friendly...just curious as to if it is more stable/safer or just as safe as cwm? When it comes to changing the recovery in a phone I view that as updating a bios in your computer...don't do it unless you really really need to (last time I upgraded a bios the power went out the same time....not a good day). Just curious as to fellow flashers opinion on the topic? Seems twrp has been getting alot more updates than cwm as well.
EI
Excessiveidling said:
Back in the day (droid eris days) there was cwm and twrp and twrp was thought of to cause more issues than anything so it was recommended to use cwm. Now it seems to have changed (at least regarding the gs3). Is this true? IS twrp that much better/stable/safer than cwm? I've never used twrp (have seen videos/screen shots) and it looks alot easier...well user friendly...just curious as to if it is more stable/safer or just as safe as cwm? When it comes to changing the recovery in a phone I view that as updating a bios in your computer...don't do it unless you really really need to (last time I upgraded a bios the power went out the same time....not a good day). Just curious as to fellow flashers opinion on the topic? Seems twrp has been getting alot more updates than cwm as well.
EI
Click to expand...
Click to collapse
I only used TWRP, its so much more innovative and easy to use with the touch based interface and i have absolutely no problems with it.
Another another note, probably not the right forum for this thread lol...
Yea I wasn't sure if this was the right forum or not.... But figured recovery deals with development sooooooo...
Sent from my SCH-I535 using xda app-developers app
Excessiveidling said:
Yea I wasn't sure if this was the right forum or not.... But figured recovery deals with development sooooooo...
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You were still in the wrong. Plus, there's already a dedicated TWRP recovery thread in the dev section.
To answer your question, TWRP really is a nice recovery. I usually stay a few versions behind the latest because what works now is good enough for me. I don't think you can go wrong with either TWRP or CWM, but having used CWM for so long I wanted to see what else was out and TWRP didn't disappoint. It's as safe as a custom recovery can be flashing modified software not intended for your phone.
Sent from my SCH-I535 using xda app-developers app
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Anyone?
Sent from my SCH-I535 using xda premium
Never mind...
Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium