Apologies if this has already been covered but I have seen so many old conflicting threads with regards to 6.0.1.2 Touch Recovery.
Therefore I need some clarification.
Is 6.0.1.2 safe to use as I have read people have had several problems and even bricked devices.
Guys in your opinion should I go back to 5.5 or is 6.0.1.2 stable enough to use.
I use it every day I've never had a problem until now
Related
So just to make it first stated, im no newb to this forum. i flash all the time. i just had my phone unbricked by Connexion2005 and the crew over at mobiletechvideos.com they did a fantastic job at restoring my vibrant to its previous luster. my problem now is i cannot find a way to flash clockwork recovery. ive downloaded rom manager from the market and tried flashing then rebooting to the recovery environment. but nogo. still on stock recovery. ive tried some of the older versions and none of them work either. what am i doing wrong? i also found others with the same issue in the clockwork thread in the dev section. someone shed some light for a fellow modder.
Hi,
I've inadvertently installed Clockwork recovery over Romracer's and was wondering whether it's worth changing back to Romracer's recovery or to just stay on Clockwork?
I heard a while ago that Clockwork wasn't recommended for some reason but I can't remember why. Is that still the case and does it really matter which recovery we use?
Many thanks.
Back then clockwork's wasn't wiping the data & cache properly. Nowadays they're on par I believe, romracer's certainly has better support for us through the thread in the development section.
Romracers!
Thanks for your help guys, I think I'll go back to Romracer's then.
Much appreciated
I'm not new to android customization so i know what unlocking the bootloader entails, but my question is, is it worth it? There doesn't seem to be that much development going on for the TF201. My main issue with the Prime is that it seems a bit sluggish and unstable at times, which seems to imply a software issue rather than a hardware issue. If i unlock and flash a custom rom and kernel, would i see significant improvement in speeds or stability. I don't want to void warranty if i don't get a tangible benefit from it.
sputnik767 said:
I'm not new to android customization so i know what unlocking the bootloader entails, but my question is, is it worth it? There doesn't seem to be that much development going on for the TF201. My main issue with the Prime is that it seems a bit sluggish and unstable at times, which seems to imply a software issue rather than a hardware issue. If i unlock and flash a custom rom and kernel, would i see significant improvement in speeds or stability. I don't want to void warranty if i don't get a tangible benefit from it.
Click to expand...
Click to collapse
I unlocked my bootloader because of the unstability and the asus crap. I have now installed on my prime AOKP and motleys kernel (1,6ghz). I think it is worth it, but thats my opinion.
It was worth it to me...I'm currently running Primalicious Odexed Final version and the performance has been way better. Battery life is also way better...wiping cache and dalvik would definitely help with the sluggish performance, but as you know, you'd need CWM or any other custom recovery...hence, unlocking the bootloader is def worth it.
Thank you guys, that's exactly what I wanted to hear. Last question before I unlock, is flashing roms and kernels as simple as wiping data and caches through recovery and flashing the .zip file, or is it more involved? I remember reading a thread that talks about .blob files or something like that. I'm just trying to get as much info as I can before I do this, so I don't mess anything up. There doesn't seem to be much information available unfortunately. And I guess everyone is running the latest CWM recovery which is the touch recovery, right? Any problems with that? I know that TWRP 2.0 hard-bricked my Evo and that he CWM Touch recovery has bricked a few Samsung Epic 4G Touch phones when flashing between GB and ICS kernels. But this was likely a Samsung ICS kernel issue that wasn't playing well with the recovery.
sputnik767 said:
Thank you guys, that's exactly what I wanted to hear. Last question before I unlock, is flashing roms and kernels as simple as wiping data and caches through recovery and flashing the .zip file, or is it more involved? I remember reading a thread that talks about .blob files or something like that. I'm just trying to get as much info as I can before I do this, so I don't mess anything up. There doesn't seem to be much information available unfortunately. And I guess everyone is running the latest CWM recovery which is the touch recovery, right? Any problems with that? I know that TWRP 2.0 hard-bricked my Evo and that he CWM Touch recovery has bricked a few Samsung Epic 4G Touch phones when flashing between GB and ICS kernels. But this was likely a Samsung ICS kernel issue that wasn't playing well with the recovery.
Click to expand...
Click to collapse
Yes, you can flash roms and kernels just over the recovery (zip).
And there are no problems with the cwm touch recovery, the how to for that and the blob file can you see here. But i would flash the twrp recovery, i use it because it is more comfortable. I dont know about hard bricks because of that.
dom2215 said:
Yes, you can flash roms and kernels just over the recovery (zip).
And there are no problems with the cwm touch recovery, the how to for that and the blob file can you see here. But i would flash the twrp recovery, i use it because it is more comfortable. I dont know about hard bricks because of that.
Click to expand...
Click to collapse
Thanks, that's all I need. The TWRP 2.0 issue I had was only related to the HTC Evo and no other device as far as I know. But it did kill my phone and many others, so as you can imagine I'm weary of using it. But don't think that I'm trying to say anything negative about TWRP in general, it was just the Evo that it had issues with.
Hey there!
I've got a little problem with my SGS2... it seems that I have two recoveries installed on my phone which seem to start up as they wish.
First I've got an (orange I think) 4.x version which seems a bit buggy and where I can't seem to choose zips on the internal sd.
Then there's the (blue I think) 5.x version which I preferably would like to use.
Normally the 4.x version starts up when rebooting from Rom Manager. Often when I use reboot in the 4.x version it jumps to the 5.x version. I can't seem to find a consistent behaviour so it's hard to describe what happens. Also I didn't intend to have a dual recovery... this just appeared out of the blue some day.
I didn't manage to flash the newest Miui 2.7.6: shortly after the system is fully running it crashes and the phone reboots. I couldn't find other people with this issue so my first guess is to resolve my recovery issues...
Any ideas?
Yes
Stop rebooting to recovery from rom manager. If you use the button combination you should get your blue recovery.
Thanks for the hint!
But are there still two recoveries located on my phone? Could this cause any problems?
get rid
I'm pretty sure I've read that rom manager has caused quite a few problems with the sII, I'd just delete the app and do without.
I'll definitely do that... I haven't heard too many good things about it actually.
However, there's really something wrong here. I tried to flash recovery touch.. the first time it said it installed fine but actually nothing happened. The second time I tried, right after the install the touch version was running. When I do a reboot though it's not there anymore. What to do?!?
Recovery is built into the kernel. If you flash a recovery independent of the kernel, it will only persist until the next reboot. If you want touch recovery, find a kernel with touch recovery (quite a few have it, search the development forums to find one you like).
So Rom Manager tempers with the kernel when flashing a new recovery?
Or is it some kind of temporary thing like when I flashed recovery within recovery?
Thanks for the replies... I'm interested to learn more about this stuff!
please do not use rom manager
it has bricked many s2
A while back, I was really into Android phone hacking. I remember rooting my sister's HTC Droid Incredible and installing ClockworkMod Recovery on it with ROM Manager. I remember that the Touch version was still in beta back then.
Fast-forward a few years, I'm starting to get "back into" Android stuff again. I've been doing some research, and it seems like CWM Recovery has basically...disappeared. Everyone says to use TWRP now. I can't find any recent posts on it, it's no longer on the official website, and the most recent threads related to it are a few years old. What exactly happened? Was it discontinued or something?
It just seems a little odd to me that I couldn't find any thread referring to CWM Recovery no longer being developed or anything. It almost feels like it vanished or something.
CWM is basically obsolete. Other recoverys like TWRP are constantly updated, add new options, adapted to news os ( like mm o ng ) but the development of cwm is discontinued. If recovery not is constantly updated, is losing strength. If u looking for a cwm based recovery, u can use for example PhilZ touch, is a custom recovery like Twrp, but is completely based on the sources of CWM.
xdedeone said:
CWM is basically obsolete. Other recoverys like TWRP are constantly updated, add new options, adapted to news os ( like mm o ng ) but the development of cwm is discontinued. If recovery not is constantly updated, is losing strength. If u looking for a cwm based recovery, u can use for example PhilZ touch, is a custom recovery like Twrp, but is completely based on the sources of CWM.
Click to expand...
Click to collapse
So the devs never officially discontinued it, and kind of "let it be"? That's kind of odd...