[Q] Recovery ClockWorkMod v3.1.0.0 - Nexus S Q&A, Help & Troubleshooting

Hello, I saw here : http://mirrorbrain.cyanogenmod.com/cm/recoveries/
that the recovery clockworkmod v3.1.0.0 is arrived ! But on the Nexus S, the recovery official is the 3.0.2.4 and the recovery custom v3.0.2.5 (thx)
But, I like have the update to recovery, so I wanna know if there are the recovery 3.1.0.0 for the Nexus S or if a person can modified the recovery 3.1.0.0 in order to it work on the NS ???
Thanx

No idea where those 3.1.0.0 come from. The latest version in the source repository is 3.0.2.8.
However, looking over the commits, there seems no reason for you to upgrade, since you already have 3.0.2.5, which removes the menu entries for hard bricking your phone (format bootloader, radio, recovery).

How you knows that the last recovery clockworkmod is the 3.0.2.8 ?
It's bizar because there are recoveries 3.1.0.0 .... ?

You can look at the git repository commit log:
https://github.com/CyanogenMod/android_bootable_recovery/commits/gingerbread
The version is in the Androik.mk file line 29:
https://github.com/CyanogenMod/android_bootable_recovery/blob/gingerbread/Android.mk
It says 3.0.2.8.

If this was even a genuine clockworkmod why would you want it ?
i dont see any point in rushing to get the updates before they are supported through rom manager ,, unless it adds many extra features you need!!

Okey. Thx for your posts

dopeypopey123 said:
If this was even a genuine clockworkmod why would you want it ?
i dont see any point in rushing to get the updates before they are supported through rom manager ,, unless it adds many extra features you need!!
Click to expand...
Click to collapse
Rom manager is showing 3.1.0.0 as the current version.

Related

[HELP]Problem with ClockWorkMod 6.0.3.2 (Touch) on HTC One SV

Hello, I'm using T-Mobile (UK) HTC One SV with JB (rooted)
I follows this link to root my phone and thus I've got the JB CWM version listed in the link.
The problem is when I boot into recovery mode into the CWM, the screen is shifted a bit to left and the cropped/shifted part is appearing on the right! (I hope I'm making some sense with this 'shifted screen' explanation. I'd like to post a screenshot if someone can help me with getting a screenshot in recoverymode) Anybody else facing this problem? If yes, how can I fix it?
On a slightly different note, I'd like to admit that whilst following the rooting procedure mentioned above, I tried to be a 'smart arse' and tried flashing CWM 6.0.3.8 on the device, which just wouldn't load /data with error
Code:
Can't mount /data
and same with cache and respective logs. And because of that I wasn't able to do a backup either. I tried, quite a few times, to format the SD card into FAT32 etc but it was having none of it! :crying:. Then when I slapped myself for not following the procedure, like a good boy , and got the same CWM listed in the link, I was able to do backup and no errors were being displayed in regards to mounting of /data. :good: I thought I'd share my experience on for others to learn from.
This screen flickering is a know problem of this touch recovery.
Its not developed to the end.
I recommend you to use TWRP recovery which is fully functional.
old.splatterhand said:
This screen flickering is a know problem of this touch recovery.
Its not developed to the end.
I recommend you to use TWRP recovery which is fully functional.
Click to expand...
Click to collapse
Thanks for quick reply. I've never used TWRP and to be honest, quite new to this depth of rooting, recovery etc. Does TWRP offer similar set of features as CWM? And is there a 'touch' TWRP for this device on JB? If so, could you kindly post me the link.
Most up to date version you will find here:
[TWRP 2.6] Updated 9/21/13 All variants TWRP recovery 2.6
Another (older):
[Recovery] TWRP Recovery 2.x
Yes, all touch and has more features than cwm.
old.splatterhand said:
Most up to date version you will find here:
[TWRP 2.6] Updated 9/21/13 All variants TWRP recovery 2.6
Another (older):
[Recovery] TWRP Recovery 2.x
Yes, all touch and has more features than cwm.
Click to expand...
Click to collapse
Thanks a lot! I shall give it a try

[RECOVERY][ICS] CWM Recovery for HTC Desire SV

Here's a new ClockworkMod Recovery for the HTC Desire SV, attached below. For installing and rooting, see this guide.
Facts & figures:
- Based on CWM Recovery 6.0.1.2
- For Android ICS (4.0.4)
- Includes kernel from htcdev.com
0.8 Version:
- Screen offset when scrolling
- Can't mount /cache errors
0.9 Version (latest):
- More elegant way of patching the screen offset fix
- Added sd-ext
Credits go to Koushik for CWM Recovery in general. Source files can be found here, on github.
Remember to backup your firmware before flashing, and use "fastboot boot recovery-cm_magnids-eng-ics-0.8.img" first.
Let me know by posting if it works, and hit thanks button!
jheller said:
Here's a new ClockworkMod Recovery for the HTC Desire SV, attached below. For installing and rooting, see this guide.
Facts & figures:
- Based on CWM Recovery 6.0.1.2
- For Android ICS (4.0.4)
- Includes kernel from htcdev.com
0.8 Version:
- Screen offset when scrolling
- Can't mount /cache errors
0.9 Version (latest):
- More elegant way of patching the screen offset fix
- Added sd-ext
Credits go to Koushik for CWM Recovery in general. Source files can be found here, on github.
Remember to backup your firmware before flashing, and use "fastboot boot recovery-cm_magnids-eng-ics-0.8.img" first.
Let me know by posting if it works, and hit thanks button!
Click to expand...
Click to collapse
thanks
Installed this and works great. No more flickering..
However, when i try to flash int2ext, i am getting unable to mount volume ./external_sd.. Any fix to this issue. I am sure it is an recovery issue and since you mentioned it as "added ext_sd" support, i thought it would solve this mounting issue.
Any update on this from would be of great help.. Thanks in advance.
tried the same and installed 0.8 first and then 0.9.....now there is no flickering and a nice interface....thanks
thanks a lot...
one request can u update cwm recovery??
crazy89 said:
thanks a lot...
one request can u update cwm recovery??
Click to expand...
Click to collapse
I'm affraid I have to disappoint you, I stopped further development of this recovery for the HTC Desire SV. The issue with HTC is the s-on functionality, which prevents modification of the system apps, so I bought a Moto G 2nd gen.

[NEED HELP] I want to build CWM Recovery 5.0.2.8. Please help me.

Hello everyone,
I have a tablet naming HCL ME V1 and it supports only CWM Recovery 5.0.2.8 only.(I flashed it and it booted into recovery mode, no other recovery is booting.)
The recovery which i dowloded(5.0.2.8) has emmc partitions and my tablet have MTD partitions (when i flashed it started giving error like: cant mount cache\recovery\last_log. etc etc.)
so i edited the ramdisk(i replaced cwm recovery.fstab with stock recovery.fstab) but it didn't work for me.
So i decided to build it from source.
I know that CWM Recovery sources are with the CyanogenMod sources.
I want to download Cyanogen Mod 7 sources as zip because I don't have high-speed internet connection. So i will download it at another place.
So, I need a proper guide to build CWM recovery 5.0.2.8
Cwm online builder didn't help me.
And it will be helpful if a kind and experienced dev can make it for me.
Anyone also can look at here:
forum.xda-developers.com/showthread.php?t=2505430
Send by a GROWING N00b
If you have the basics, Give this a try..
http://builder.clockworkmod.com/
Thanx for suggestion.
But i tried that but it didnt work for me.
Any other help.
Send by a GROWING N00b
Can i make it using android_bootable_recovery...
I downloaded form Github(from CM source).
Send by a GROWING N00b

[POLL] CWM v/s PhilZ-Touch v/s TWRP

Hello folks,
Since a long time now...we all are using mostly these three recoveries:
1)Clockworkmod(CWM) Recovery (by @Koush)
2)PhilZ-Touch Recovery (by @Phil3759)
3)TWRP Recovery (by TeamWin)
...for getting our ROM flashing and other jobs done.
This thread is meant to compare these three recoveries in terms of it's global usage. It's just like a survey.
So...everybody is requested to vote on the poll for their most used recovery. Thanks
Just a few words before you vote:
You are welcomed to post the reason for liking and using the recovery you voted for. But please don't post something like: "I have only Advanced version (without any GUI and Touch) of PhilZ-Touch Recovery for my device, so I like TWRP", "Touch doesn't work in my TWRP, so I like CWM", "I have the latest version of CWM but not of PhilZ-Touch Recovery for my device, So I vote for CWM". These reasons are because your device is not officially supported by the developer of the recovery. Vote here only if you are using/used the officially supported build of the recovery.
Recovery is a choice. So, everybody is gonna like different recovery for their different aspects/advantages. Just vote on the Poll and leave a post so that we can know that which of these recoveries are mostly used by users and why. Multiple options are enabled in the poll but please try to vote in only one option...for the recovery you use the most.
Please NOTE: This thread is no way meant to insult any of the developer(s) of above recoveries. This thread is just to know the popularity of these recoveries among the users...can be rather called a 'survey'.
Vanilla CWM is no match for Philz Advanced edition - way more features and fast backup speed if exfat modules have been incorporated. TWRP comes a close second with its file manager and terminal, and is also very quick
shoey63 said:
Vanilla CWM is no match for Philz Advanced edition - way more features and fast backup speed if exfat modules have been incorporated. TWRP comes a close second with its file manager and terminal, and is also very quick
Click to expand...
Click to collapse
I respect your opinion.
But, Are you sure? I hope Vanilla=Stock.
Can you just tell me a feature that's more in vanilla cwm (than philz-touch)?
I do agree that it's code is very neat (really) and the UI is simple...but when it comes to features...TWRP and PhilZ-Touch wins (Acc. to me).
However, cwm has started addition of new features like- Swipe-Touch, Menu color's changing, etc nowadays.
Vanilla (stock) Cwm is no match for Philz = Philz is waaay superior :thumbup: Sorry if my post was confusing to you
Sent from my C6603 using xda app-developers app
I wouldnt say either is superior to the other. They all have their own lil niches and ppl like each for whatever reason.
They are all good recoveries and choice is good.
PlayfulGod said:
I wouldnt say either is superior to the other. They all have their own lil niches and ppl like each for whatever reason.
They are all good recoveries and choice is good.
Click to expand...
Click to collapse
Ofcourse, that's what I said in first post.
My personal rank:
1. PhilZ Touch
2. TWRP
3. Carliv Touch
4. CWM
I'm using MTK6589.
TWRP because PhilZ errors out on CM-11 update
I just installed TWRP on my P3113 because PhilZ-Touch 6.53.6 could not update CM-11 to the 20140810 nightly & the recovery log says that the file could not be found after logging lots of errors.
PhilZ was looking in as: /sdcard/0/cmupdater/cm-11-20140810-NIGHTLY-p3110.zip
whereas the file was in: /storage/emulated/0/cmupdater
Interesting in that the 1st CM-11 was installed by PhilZ by using PhilZ to do a fresh install.......
PhilZ looks to be quite nice but something need to be changed in the location checking for the CM-11's version; don't know if other versions has a change of naming directories for the Tab 2 7 P3113/P3110.
Will be staying with TWRP for now; kinda like the PhilZ tho.
For my opinion, PhylZ can will be the better Recovery because if dev make compatibility theme and add TWRP options supports to PhylZ, it will make a full Recovery :good:
I super like philz one touch 'clean to install new rom'
I just use them but here's my take:
CWM - Older and more known. Works when all others may fail.
Philz - Almost the same as CWM but has more features - including touch for some devices when CWM doesn't have it - and little extra features like cleaning for new ROM which automatically does what you need.
TWRP - IMO it's prettier and has very good features - but the support on devices is less than the older CWM.
So currently I use PhilZ, but using AROMA for GAPPS seems like TWRP would have worked - failed on PhilZ. Found workarounds.
As stated, everyone has reasons for their choices and preferences. Really, I didn't see that much of a pull to go TWRP (used on other devices) since I had alternatives, and I didn't need to go CWM because - IMO - PhilZ is the same with added features.
I have only used TWRP, stock recovery and CF-Auto-Root custom recovery that flashes SuperSU.
PiotrGrochowski said:
I have only used TWRP, stock recovery and CF-Auto-Root custom recovery that flashes SuperSU.
Click to expand...
Click to collapse
It was fun helping Phil port his recovery to other devices, but it is now deprecated, and the dev no longer active. TWRP is the way forward now.
Philz is the best, always
Hello folks Philz is my favourite and the best recovery always. Maybe u for not know, after the release of TWRP I had contacted Koushik Koush Dutta to involve the special features of TWRP in the next version of CWM. But he was busy working in Cyanogen so he appointed Philip who then developed the CWM Advanced edition Philz Touch.
Now let me say why should u must use Philz or if not possible then CWM touch. Recovery refers to a mode on an Android device to recover and save your device during any emergency. By chance of the touch screen of it phone gets damaged then u can use non touch facility in CWM or Philz.
So if possible use CWM and Philz, and if it's not available for urgent device then contact me on : [email protected]
I will help u out.
Thank You...
i like: "They are all good recoveries and choice is good"
I have only used TWRP for the time being, but it seems to be the only recovery I will ever need.
Feature-packed, simple to use and just plain awesome!
Bhargav97 said:
Hello folks,
Since a long time now...we all are using mostly these three recoveries:
1)Clockworkmod(CWM) Recovery (by @Koush)
2)PhilZ-Touch Recovery (by @Phil3759)
3)TWRP Recovery (by TeamWin)
...for getting our ROM flashing and other jobs done.
This thread is meant to compare these three recoveries in terms of it's global usage. It's just like a survey.
So...everybody is requested to vote on the poll for their most used recovery. Thanks
Just a few words before you vote:
You are welcomed to post the reason for liking and using the recovery you voted for. But please don't post something like: "I have only Advanced version (without any GUI and Touch) of PhilZ-Touch Recovery for my device, so I like TWRP", "Touch doesn't work in my TWRP, so I like CWM", "I have the latest version of CWM but not of PhilZ-Touch Recovery for my device, So I vote for CWM". These reasons are because your device is not officially supported by the developer of the recovery. Vote here only if you are using/used the officially supported build of the recovery.
Recovery is a choice. So, everybody is gonna like different recovery for their different aspects/advantages. Just vote on the Poll and leave a post so that we can know that which of these recoveries are mostly used by users and why. Multiple options are enabled in the poll but please try to vote in only one option...for the recovery you use the most.
Please NOTE: This thread is no way meant to insult any of the developer(s) of above recoveries. This thread is just to know the popularity of these recoveries among the users...can be rather called a 'survey'.
Click to expand...
Click to collapse
in my opinion, twrp is better as it offers more options and it has an interface built from scratch.

Latest TWRP not working

Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Install the 3.0.3-0 common TWRP, then try to format data (Wipe ->Format Data-> type yes). Reboot recovery once and then perform a wipe of all partitions (Wipe->Advanced Wipe-> select everything). If you get stuck at "updating partition details..." just wait. It could take as long as five minutes some times to get unstuck.
This is the link for the thread of Slim6, the mm rom I recommend by Andi:
https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-slim6-t3414798/page1
And this is an aosp mm rom also by Andi, try it if above fails
http://builds.unlegacy-android.org/aosp-6.0
Flash both with TWRP 3.0.3-0
If problems continue, post the recovery log (you can find it after reboot at /cache/recovery/ )
landetta said:
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Click to expand...
Click to collapse
have you used the twrp on the http://andi34.github.io/ website? and roms compiled before 3/22/16 dont flash with common twrp when I updated twrp I had downloaded the zip and went into twrp to flash it I havent used a pc at all to install twrp and root . so I just put the zip on my sd card and it updated it did you update twrp with odin?
Thank you for your reply,
Yes I used the recoveries from Android Andi, and yes I have installed recoveries in zip form through recovery and Odin. Unfortunately neither have worked. I did use the latest recoveries when I tried to install the newer roms but it just gets stuck, I can't even make nandroid backups it also gets stuck with the newer recoveries.
Edit:
@ john99ap Sorry i just got home, I tried what you said but it just got stuck at both wipes, I waited 10 mins but a no-go. I found the logs, I couldn't paste them in here because it exceeded character length so I put it in pastebin. I didn't know which log to use so I am giving you the ones that I think are more relevant
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
landetta said:
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
Click to expand...
Click to collapse
I can't find anything in these logs
I need the log in which you try to install the zip file.
Try this:
-Install TWRP 3.0.3-0 (if it's not already there)
-Reboot and delete all recovery logs you can find
-Install the zip without doing anything else before or after so that the log is as clean as possible
-Post any log you find
PS: you could upload logs in your reply by hitting the button with a stapler on the bottom left corner
Thanks for your reply, sorry about the old logs, here are the new ones like you requested. Hopefully you find something in these new ones. Thanks again for all your help BTW I don't have any staples in my advanced reply so I had to use Pastebin again sorry. I think its because of my low post count.
pastebin/UcntGLTZ
pastebin/Fq8V7WUf
PS: Not even the reboot button works on 3.0.3-0.
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
john99ap said:
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
Click to expand...
Click to collapse
Awe thanks anyways dude, I really appreciate you trying. One last thing, on Andi's website he say that device specific 3.0.0-0 recovery should work to flash the latest roms. If anyone can confirm this maybe I can get the new roms working on it. Thanks again for all your help john99ap :good:

Categories

Resources