yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] stremax:
don't be rude:)

the new back-up method from cwm recovery split the image in two parts first is the common for each back-up the second is the variable files which developers change in update, this method is maybe good if you flash rom"X.v1" then "X.v2" and so on, the common part is the same and only the modified part are backed-up, you got an huge first nandroid (in my case more than 1Gb) and then smaller one

previous method backed up everything, about same size for each back-up, this is convenient if you switch between roms

but, AFAIK, and having issue with 6.0 recovery I switched back to 5 non touch, the new one never run good on my NS and I find really odd the new method
[Nexus S Android Development] apatal:
Oh OK. Thanks for explaining. I guess I just might go back to bm's Carebear version then. I don't really like the light gray background too much. I still like the dark background and the cute bear. :)

Sent using the xda mobile app
[Nexus S Android Development] polobunny:
The biggest problem to me with the new v6 CWM is definitely the incremental backup. It's good for the casual person that makes a nandroid every rom update for some reason, but it sucks major for anyone trying different roms with different base. The blobs folder will become huge, actually bigger than what the full nandroid of the rom would be, and you have to keep it on your phone at all cost because modifying it or deleting it will explode your backup.

It becomes a hassle to manage several different configurations and it just doesn't seem worth it to me.

Is it possible Brainmaster 5.0.8.2 is simply a mislabelled 5.8.0.2? Can anyone check that? From the time it was posted by BM it seems to line up a little time after the release of official 5.8.0.2...
[Nexus S Android Development] DJBhardwaj:
Extremely Helpful :good:
[Nexus S Android Development] DJBhardwaj:
Today, I extracted Stock ICS IMM76D recovery and also discovered TSM CWM and TSM TWRP recovery images. Apart from this, I did made a zip for 5.8.0.2 too.

So, 4 new flash able recovery zips coming tomorrow.

Credits to

slukk

for TSM recovery,

polobunny

for sharing the 5.8.0.2 CWM edition &

stremax

for the explanation :cool:
[Nexus S Android Development] apatal:
Yes I have it installed and it does say 5.8.0.2 in recovery. All those numbers are quite confusing, I guess. :)

Sent using the xda mobile app
[Nexus S Android Development] DJBhardwaj:
Perhaps, 5.0.8.2 never existed. Koush directly updated for 5.0.2.x to 5.x.x.x due to his new introduced touch interfaced recovery. So it is definitely mislabeled :)
[Nexus S Android Development] polobunny:
You should update the OP with the other flashable recoveries submitted.
[Nexus S Android Development] DJBhardwaj:
Last one to upload then I will update the post ;)
[Nexus S Android Development] Setting.Out:
Yes..
[Nexus S Android Development] CataHd:
why in 6.x.x.x mount USB storage is not working in recovery?

the only one is working is 6.0.1.0
[Nexus S Android Development] Setting.Out:
It's a kernel issue in the recovery.. Try Philz.. it is an updated CWM with a working usb..
[Nexus S Android Development] andrei1015:
Not working for Nexus S or for CM10.1 or what? That's a pretty big bug in my opinion..
[Nexus S Android Development] Setting.Out:
The recovery has it's own kernel.. For the usb to mount it actually needs the older version of the kernel, which Philz recovery fixed, and the CWM that you are trying has not.

TWRP and Philz latest have working usb in recovery as well as older versions of CWM than you are currently trying..

This has nothing to do with ROM or the KERNELS for ROMS.. this is purely a recovery issue..
[Nexus S Android Development] andrei1015:
I had no idea recoveries have a different kernel o.O
[Nexus S Android Development] polobunny:
Yes, technically the recovery is a very very small and lightweight Linux distribution. So when you're booting in the recovery and then in Android, you're dual booting! :D
[Nexus S Android Development] Zunex95:
hi!

I'm having an issue with TWRP 2.5.0.0 I ttried to flash it a lot of times. Always the same results. I can't access it. Just stays at the splashscreen and flashes once every 5th second (loopiing I'm afraid). Now I'm locked out. Can't flash another because my USB port is not working on my phone. No system installed of course. Just to make it easier. Any advice or help please?

I'm without phone. Got warranty but the bootloader is unlocked. Any help would be very apriciated!
[Nexus S Android Development] smit.sanghavi:
Let me understand your condition:

Recovery: Not installed

AND

Not able to install because of probably corrupt recovery

AND

No other recovery on SD card too.

ROM: No ROM

OR

Malfunctioning ROM

AND

No other ROM on SD card.

USB: Not working so you cannot transfer any files to SD card.

Is that right what I understood from your post?
[Nexus S Android Development] Zunex95:
Recovery: It might be installed or not. I used the zip file method to install TWRP. When I try to get into recovery it just stays at the TWRP splash screen and flashes every 5 second once. Looping.

ROM: No ROM installed currently, but there's is a ROM flashable on the SD card. I just can't access the recovery as I mentioned above.

USB: I can only charge my phone. The USB part of my phone is dead or kinda dead. every 30th try it works for a limited time. For about 2-5 sec.

If I would be able to access the recovery.. baaam I'm good to go. But unfortunately I can't. I got fastboot to, but it's no use without USB connection. The only thing I can do now is to pray for that USB port to work for a minute so I can flash another recovery. I'm out of ideas now. So the thing is.. I need to either access the recovery somehow or initiate USB connection.
[Nexus S Android Development] smit.sanghavi:
If I were in your condition then I would also try as much as I could and transfer a recovery somehow through USB (even if it took many many tries). Recovery sizes are just a few MBs so a USB connection working for even 5 seconds would do the job.

If you want it done ANYHOW and FAST, then I suggest get the USB repaired at some local shop or something.

I know it will void your warranty but I can't think of any other way out. All the best :good:
[Nexus S Android Development] Zunex95:
thanks mate! any thoughts about the recovery? no way to access it? that splash screen doesn't mean anything? and sorry for the last nooby question but if I got that recovery transferred somehow. Then what? how do I flash it without my computer? Sorry if it's a dumb question but I'm only used to ADB or Fastboot..
[Nexus S Android Development] smit.sanghavi:
Naah, I can't think of anything to access it. I have never used TWRP so don't know about the splash screen.

As far as your 'nooby' :P question is concerned, what i meant by transferring recovery is by fastboot. If you can flash CWM or any other recovery through fastboot, then you can install the ROM you have in your SD card.
[Nexus S Android Development] Zunex95:
ahhh I see. Damn, I thought there is a way to flash it by pressing a button combination or something like that. Well I guess I'm gonna have a very long afternoon with full of headaches. Thanks for your help again. Let the war begin..
[Nexus S Android Development] Setting.Out:
http://www.wugfresh.com/nrt/

http://xdaforums.com/showthread.php?t=1766475

There are also threads about this in the general and Q&A sections... It's easy to use and will solve almost any issue you have with flashing..
[Nexus S Android Development] Zunex95:
thank you, but forgot one thing, My phone's USB port is dead. It can only charge. I'm searching for a trick to bring back that usb port back to life. even for a short time.. So I need some kind of a physical trick to make it work. Any ideas?
[Nexus S Android Development] andrei1015:
Just a heads up that both Nexus S and S4G received the small update to 6.0.3.3 :)
[Nexus S Android Development] 1eyedmonster:
This might help

xdaforums.com/showthread.php?t=1448374

Sent From My Nexus 7 MIUI Warlord

And The Unbeatable TROj@N in Pool Break Pro
[Nexus S Android Development] ironia.:
out cwm 6.0.3.4
[Nexus S Android Development] DJBhardwaj:
added cwm 6.0.3.4
[Nexus S Android Development] omartins:
Hi,

It's me or the fix permissions feature isn't available in this last cwm?
[Nexus S Android Development] polobunny:
It's not only you. Fix permissions is known to break some stuff anyway. If you don't need it, don't use it.
[Nexus S Android Development] omartins:
Hmm.. Wasn't aware of that detail. TWRP 2.6 keeps featuring that option...

RM
[Nexus S Android Development] 30floh00:
Well but the FP option was kinda useful after flashing a new kernel. Sometimes I could not change governor and stuff ..
[Nexus S Android Development] andrei1015:
6.0.3.6 was released for both crespo and crespo4g :)
[Nexus S Android Development] mrdjibrilo:
could someone make a zip of it?

edit: nvm i flashed it through cmd
[Nexus S Android Development] cheeze.keyk:
hi guys, noob question. how to change my recovery from TWRP to CWM? can i flash it just like flashing a rom? tia.
[Nexus S Android Development] smit.sanghavi:
Yes.

Just pick up any recovery from the 1st page of this thread and flash it like you flash a regular ROM.
[Nexus S Android Development] leap_ahead:
+1 always on 4.2 and 4.3 rom !
[Nexus S Android Development] kriout:
i'm going to buy a new screen cause my glass is cracked... in a thread lot of people said that some times touch doesn't work cause there could be more versione of the digitizer ( i'm on i9023 so with lcd screen ) . an user suggested that if u put the original recovery should recognize the new driver of the touch and should start working again ... but nobody tried ... if just changing the screen won't work, will flash the original jellybean zip recovery from this thread work ??? what do you suggest to do ??? how could i make a total restore? should i install the original rom ??'
[Nexus S Android Development] leap_ahead:
This need update
[Nexus S Android Development] explorer-10:
6.0.3.4 touch, i can't mount sdcard =(
[Nexus S Android Development] dark'em:
Me to!
[Nexus S Android Development] ironia.:
Try Philz recovery;)
[Nexus S Android Development] explorer-10:
neither does 6.0.3.6, not able to mount sdcard

UNLESS, unless...was there a 'mount USB storage' at the bottom that i possibly didn't see?
[Nexus S Android Development] dark'em:
the ''mouny usb is there'' but ti deosent do anythinh
[Nexus S Android Development] morrigan91:
To flash android 4.4 we need a cwm 6.0.4.3 based recovery, unfortunately Philz has not yet released his recovery so...

new cwm flashable zips:

6.0.4.3 Touch

6.0.4.3 non Touch
[Nexus S Android Development] leap_ahead:
anyone can usb mount with this ?
[Nexus S Android Development] Setting.Out:
Usb is still broken with this version.. :(
[Nexus S Android Development] orky87:
@ DJBhardwaj,

Could you please add the lates twrp recovery as its needed for kitkat roms to flash correctly.

Great work man keep it up...
[Nexus S Android Development] ej8989:
The latest official twrp for crespo is still 2.6.3.0 (does not support kitkat). Unless someone compiles a new one for us, we're stuck on cwm.
[Nexus S Android Development] morrigan91:
What's wrong with PhilZ 6 recovery? Much better than the cwm: a lot of options, configurable GUI, faster backup etc. :D
[Nexus S Android Development] Stickman89:
USB Mount working fine on the provided CWM 6.0.4.3 recovery. The driver just need's re-assigning via Device Manager.
[Nexus S Android Development] thientinh91:
cwm

I flash done cwm 6.0.4.3 it very good !
[Nexus S Android Development] developersdevelopers:
Could you explain what you mean by re-assigning the driver?
[Nexus S Android Development] Stickman89:
Probably not the correct terminology to use, I apologize.

Please ensure your device is connected to your machine and CWM is loaded.

On a Windows Machine do the following:

Navigate to Device Manager (Win + Pause|Break Key > Select 'Device Manager')

Locate device within the list that has an exclamation mark beside it (remove USB cable and reinsert to see if actions correspond with item visibility)

Ensuring that your USB cable is connected, right click on the device you located in Device Manager...

select 'Update Driver Software' > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Highlight 'USB Composite Device' (ensure 'Show compatatible hardware' was ticked before proceeding) > Finally Select Next.

The driver will now install. Once it has simply remove the USB Cable from your device and reinsert. This will initiate the re-assigned driver. You can proceed with mounting your Storage via CWM.

You should now see your device, Nexus S, is listed within Device Manager. You can proceed with installing the ADB driver's if you wish, or simply skip this step as it is not essential for USB Mass Storage operation.
[Nexus S Android Development] leap_ahead:
thanks working for me!!! can mount usb on cwm 6.0.4.3

---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------

not broken ! need driver!
[Nexus S Android Development] Keanu4:
Didnt want to bump an old thread, but the link for CWM-Touch 6.0.3.4 Falasbale Zip not working,

Edit:

Link on the first post needs to be updated for Nexus S users.
[Nexus S Android Development] iakoboss7:
i just used 2.5.0.0 twrp zip file and replaced the recovery.img with the 2.6.3.1 i downloaded from elsewhere and flashed it! everything worked fine! you can do the same with cwm probably!
[Nexus S Android Development] Keanu4:
Ok Neat... Pretty Good! will remember to try like that in future :)

... and there is a link that worked after 4 tries .. its on the previous page here.

I was getting error with 6.0.0.4 .. but with this latest one.. SlimKat install fine. I think, i can finally feel that Nexus S is performing good. i dont know why but with other roms it wasnt like that,

There are many files available on the forum elsewhere.. that are flashable zips but we cant install just anything right> we ned Nexus S specific files. e.g., even Galaxy Nexus file wont work? isnt it.
[Nexus S Android Development] iakoboss7:
of course you need specific recovery.img files for each device! but you can use any zip (if its purpose was to flash a recovery) like the one i used, to flash any recovery.img on any phone, u just have to replace the img inside with the one you want to use.
[Nexus S Android Development] smit.sanghavi:
You can use any zips but only the zips for your own recovery.

The updater-binary is different for each device.
[Nexus S Android Development] Nuclear_Geko:
The links for the roms are expired, at least for the latest version of Clockwork Touch recovery...
[Nexus S Android Development] smit.sanghavi:
Anybody here skilled enough to build the latest Philz Touch Recovery for crespo?

Philz said he doesn't plan to update for crespo anymore. :(
[Nexus S Android Development] ironia.:
attached
[Nexus S Android Development] Nuclear_Geko:
Much appreciated dude!
[Nexus S Android Development] anchang1:
Thanks a bunch!
[Nexus S Android Development] DJBhardwaj:
Updated!

Head over to the first post for more info :good:
[Nexus S Android Development] ilnanny:
subscribed, :D

Thank you so much.

Inviato dal mio Nexus S
[Nexus S Android Development] eddy_nugroz:
can u fix usb storage this build 6.0.1.9
[Nexus S Android Development] DJBhardwaj:
I'm so sorry but for now I can't. I barely get time out of studies. For fixing USB Storage, I would need to setup my whole linux machine again and build from source but again, my time doesn't allow me to do so :rolleyes:
[Nexus S Android Development] sperelli:
I read here and there, that there are some ricoveries breaking the phone, especially on 4.2.

Is it true?

I normally use cwm 5.0.2.x
[Nexus S Android Development] eddy_nugroz:
Use 5.8.0.2 work fine for me
[Nexus S Android Development] DJBhardwaj:
In my 2.5 years Android experience, I would say nothing as such happens and it never could.
[Nexus S Android Development] sperelli:
god be blessed.

time to come back to cwm, for twrp and similare are not really meant to please my taste. :fingers-crossed:
[Nexus S Android Development] gunner49:
Nice thread - Subscribed :)
[Nexus S Android Development] xbs:
Can we have TWRP 2.3.2.3?

This fixes:

Looks like we got forgotten,

so here is 2.3.2.3 which fixed the adding of a /0/0 when you preform a factory reset on any 4.2 rom.

This DOES NOT prevent the first /0 because that is needed and it is the way of the future, what it does is ensures that if you are already on a 4.2 ROM that is does not create yet another /0 under /0. If you dont understand what i mean, then you probably dont need to worry, just update it and all will be well and you wont have to fix something later.
[Nexus S Android Development] polobunny:
OP doesn't compile or create any recoveries you know, simply packages them in a recovery flashable zip. TWRP 2.3.2.3 isn't out for the Nexus S.
[Nexus S Android Development] DJBhardwaj:
I am right now aiming to compile CWM 6.0.1.9 for NS. When I am done with it, I will move on to TWRP 2.3.2.3 too :good:
[Nexus S Android Development] DJBhardwaj:
Got a little change of mind :highfive:
[Nexus S Android Development] polobunny:
Well scratch that. :P
[Nexus S Android Development] anshumandash:
Good compilation of recoveries. Thanks. :good:
[Nexus S Android Development] htchoi5609:
Thx :)
[Nexus S Android Development] ptr347:
thanks! problem: twrp 2.3.10 looks aliased like made for a higher res.

envoyé de puis mon Nexus s, aiiiiight ! (Michel rules the world)
[Nexus S Android Development] DJBhardwaj:
You have to cope with it. Just a minor issue ;)
[Nexus S Android Development] xis123:
I have CWM recovery right now, if I flash the Touch recovery.. what happens? does it simply get replaced?
[Nexus S Android Development] DJBhardwaj:
Yes, it will simply replace your current recovery ;)
[Nexus S Android Development] ejcleunamme:
Thanks for this man. I was able to change my recovery to touch cwm because its hard pressing buttons back and forth. To those who will download this using their phone make sure you set your browser agent to desktop cos u wont get the download option if its set to android.
[Nexus S Android Development] migueldbr:
there is nothing wrong with using TeamWin Recovery Project (TWRP) 2.3.1.0 on android 4.2 right?everything works properly?
[Nexus S Android Development] DJBhardwaj:
Yes, everything will work fine, there are no issues wih it.
[Nexus S Android Development] jwee5467:
I seem to have problems with my fix permissions on twrp 2.3.1.0 not sure why but it crashes and restarts.
[Nexus S Android Development] DJBhardwaj:
Works fine this side :rolleyes:

Anyone else facing the same?
[Nexus S Android Development] migueldbr:
i dont know if its normal, thats why i asked previously if twrp worked properly. when i was on cwm recovery, when i ran fix permissions it usually took a while to do it. with twrp it takes like one or two seconds. It really looks like it crashes but i dont know if its just faster. Is it normal?
[Nexus S Android Development] DJBhardwaj:
Yes its completely normal. No need to worry :)
[Nexus S Android Development] migueldbr:
ok i paid attention this time and i can confirm what jwee5467 said, actually it takes less than one second and it goes back to twrp logo and then to the home screen!

sorry about my misleading earlier post
[Nexus S Android Development] DJBhardwaj:
Oh, could you please clear cut what the issue is? :confused:
[Nexus S Android Development] migueldbr:
what do you mean? When i run fix permissions, it crashes and goes to the twrp logo and then to the recovery homescreen (just like when you boot into recovery). it does not fix permissions
[Nexus S Android Development] DJBhardwaj:
While on official TWRP that I posted (other than TSM TWRP), the "fix permissions" function runs fine for me. It just completes the task within 2 seconds. None crashes :confused:
[Nexus S Android Development] savantist:
CWM 6.0.2.2 for GSM:

http://jenkins.cyanogenmod.org/job/recovery/12993/artifact/archive/recovery.img

flash via fastboot

CWM 6.0.2.2 for CDMA/4G:

http://jenkins.cyanogenmod.com/job/recovery/12976/artifact/archive/recovery.img

flash via fastboot
[Nexus S Android Development] DJBhardwaj:
Could you confirm the USB Mount Storage to be working?
[Nexus S Android Development] dinuvali:
The CWM Touch 6.0.1.0 sends me to G Drive within the zip file so i extracted this link from the .htm file that gets downloaded when you use "Save Target As".

https:\/\/docs.google.com\/uc?authuser=0&id=0B46yaD9nFJdcNmY1Sms3YUZ0MTA&export=download&revid=0B46yaD9nFJdcb0VSd0UydnJvSnEzU1QzUXB6T00zaDZKQXJNPQ
[Nexus S Android Development] acquariusoft:
is possible have flashable zip?

also is possible have touch version?

tnx
[Nexus S Android Development] DJBhardwaj:
Yes, of course but only when we are confirmed that this image is fully functional. :angel:
[Nexus S Android Development] eddy_nugroz:
I have try that

but not boot to CWM

and last I build CWM touch 6.0.2.3 from This

USB Mount Storage not working :(

Edit:

see this http://changelog.bbqdroid.org/#crespo/cm10/1355639512 and this https://github.com/cyanogenmod/android_bootable_recovery/commit/ed99ff3bf0dbe0194fcf2c35b10bc317f9a495a1

what is mean ???
[Nexus S Android Development] DJBhardwaj:
Koush has commited 6.0.2.x series now, as soon as I am done with syncing source, I will try to compile that.

Else, the clear battery stats option has been finally removed from CWM officially.
[Nexus S Android Development] DJBhardwaj:
UPDATE

Added TWRP 2.3.3.0

Enjoy!

Also, does anyone have the RZRecovery image file for crespo?
[Nexus S Android Development] Articudos:
New cwm released for crespo!
[Nexus S Android Development] DJBhardwaj:
Thank you for the info.

I have downloaded the image files, now testing the flashable zips. If everything goes fine, I will upload ASAP :fingers-crossed:
[Nexus S Android Development] mypat:
Look at this please. http://xdaforums.com/showpost.php?p=35794551&postcount=2
[Nexus S Android Development] DJBhardwaj:
That's really nice of you. But I already added :confused:

I will add your links to the mirror, if its fine with you my friend?

Update! Dec 24, 2012

- Added ClockworkMod (CWM) 6.0.2.5 Touch

- Added ClockworkMod (CWM) 6.0.2.5 Non-Touch
[Nexus S Android Development] xbs:
TeamWin Recovery Project (TWRP) 2.3.3.0 keeps failing install... anyone??
[Nexus S Android Development] assassinoid:
110% correct.

i just install from official website at .img and install it via fastboot ... zip is not working properly ...
[Nexus S Android Development] mypat:
Thats why i warn you about it :) of course fine no problem :)
[Nexus S Android Development] jwee5467:
Goo manager works fine.
[Nexus S Android Development] DJBhardwaj:
I will fix the TWRP asap.
[Nexus S Android Development] DJBhardwaj:
TWRP 2.3.3.0 Fixed and link updated!
[Nexus S Android Development] Hordon:
With ClockWorkMod 6.0.2.5 Touch i can't mount the usb storage from the recovery switch back to 6.0.1 it works fine for me
[Nexus S Android Development] g33kt:
I can confirm this
[Nexus S Android Development] newbie1908:
yeah same problems with me. i can't mount usb storage on 6.0.1.9, 6.0.2.3, 6.0.2.5.

so, back to 6.0.1.0
[Nexus S Android Development] DJBhardwaj:
Mounting USB Storage is a backhead bug from Koush itself. I guess we need to report of it.
[Nexus S Android Development] gunner49:
Is a wipe of some sort necessary/recommended when flashing a recovery or even a kernel for that matter?

Thanks & Happy Holidays to all!
[Nexus S Android Development] apatal:
Not really, but if it makes you feel better before flashing, by all means wipe to your hearts' content. Happy holidays! :)
[Nexus S Android Development] gunner49:
@apatal Thanks bro!
[Nexus S Android Development] MrMat:
I've installed CWM 6.0.2.5 (flashable zip) and then I've wrongly pressed "install zip from sideload".. after that there is no way to go back into recovery unless removing the battery..

having the the two "install zip from....." one above the other is not the best IMHO

re-installed 6.0.1.0 version..
[Nexus S Android Development] xbs:
+1

There should be a back/cancel option to get out of that screen.