Database Info

ClockWorkMod 4+ for NS4G?

Does any one have a recovery.img of clockwork version 4 for the nexus s 4g?

http://forum.xda-developers.com/showthread.php?t=988686
NS4G version.

i have this one

ok hellcat i sent you an pm telling you how to use it

michaelpeerman said:
ok hellcat i sent you an pm telling you how to use it
Click to expand...
Click to collapse
You do realize it's the same thing I posted right?
All he did was put the .img in a zip file.
The instructions to flash it is to... well, if you're using his .zip which I don't recommend because a MD5 hash is missing. You can try downloading his file and verify it corresponding to that thread. You need to make sure the MD5 hash matches otherwise something could go wrong because you have a bad download.
1. Go to the page I linked, download a NS4G recovery with a color that you'd like on it.
2. Once its downloaded, put the img in your /sdk/tools/ folder.
3. Put your phone into bootloader mode.
4. Open command prompt
5. cd C:\wherever your sdk folder is
6. fastboot flash recovery ns4g-4002-color.img (replace color with the color you got)
E.G. if you downloaded the cyan one, it would be, fastboot flash recovery ns4g-4002-cyan.img
green? --- fastboot flash recovery ns4g-4002-green.img
and so forth.
7. reboot recovery
done.
Sent from my Transformer TF101 using XDA Premium App

worked like a charm mike, wish i woulda thought of that but then i again im lazy as someone put it in another thread
i downloaded that from the same place you linked about 4 hours ago
ok zephk i was just giving him the actual file is all, either way it worked out in the end, and with your link someone can find the color of their choice

hellcatt said:
i downloaded that from the same place you linked about 4 hours ago
Click to expand...
Click to collapse
Yeah but its not the original link. It's also put in a .zip file. Just wanted to explain to him that both of them are the same. So regardless it should work. Just OP should check its MD5hash before actually fastboot flashing it.

Ok let me clear things up. Hellcat was wanting it on his phone so he contacted me asking me how to install so i advidsed him to use the one click method by shabby penquin just replace the recovery in his file with this one and rename it to recovery

yes and it worked perfectly, didnt change anything at all except the version of CWM. do you think we should contact shabby penguin to maybe update his file?

hellcatt said:
yes and it worked perfectly, didnt change anything at all except the version of CWM. do you think we should contact shabby penguin to maybe update his file?
Click to expand...
Click to collapse
Duh. What did you expect to be changed within Clockwork? That's why the latest is 3.0.2.4 for the NS. Recoveries don't get updated all of the time.
Most of the changes aren't even for the NS tbh.

zephiK said:
Duh. What did you expect to be changed within Clockwork? That's why the latest is 3.0.2.4 for the NS. Recoveries don't get updated all of the time.
Most of the changes aren't even for the NS tbh.
Click to expand...
Click to collapse
so what are you saying im not allowed to want to update from 3.1.0.1?
so the one for the ns4g which is what we are talking about that is version 4.0.0.2 that YOU posted a link to that is now on my phone doesnt exist? coulda fooled me. thanks for visiting zeph

hellcatt said:
so what are you saying im not allowed to want to update from 3.1.0.1?
so the one for the ns4g which is what we are talking about that is version 4.0.0.2 that YOU posted a link to that is now on my phone doesnt exist? coulda fooled me. thanks for visiting zeph
Click to expand...
Click to collapse
No? I'm just saying that when you update your recovery you shouldn't be expecting much changes to be coming from it. Clockwork Recovery only gets updated to 4.0.0.0+ to support new devices. That's why the official Clockwork Recovery that is supported by ROM Manager & Koush's current version for the Nexus S is at 3.0.2.4 and not 4.0.0.2.
And I never said it doesn't exist. Yeah I didn't mention "official support" but you should know what I meant. Don't pretend like you don't know what I'm speaking about.

i dont know what youre speaking about, im a self admitted android moron and lazy one click user remember? lol. in fact your directions a few posts back might as well be in Aramaic because i think i was doing that but it wasnt working.
remember im the free floating un braced barrel ceiling guy
all i know is i wanted the same version on my new ns4g that i had on my original and couldnt figure it out after a few hours. and if i knew it was as simple as what mike told me i wouldve done that when i rooted......but i didnt
and now i feel like an ass for bothering anyone about it now that i found this
https://market.android.com/details?id=com.joeykrim.flashimagegui

hellcatt said:
i dont know what youre speaking about, im a self admitted android moron and lazy one click user remember? lol. in fact your directions a few posts back might as well be in Aramaic because i think i was doing that but it wasnt working.
remember im the free floating un braced barrel ceiling guy
all i know is i wanted the same version on my new ns4g that i had on my original and couldnt figure it out after a few hours. and if i knew it was as simple as what mike told me i wouldve done that when i rooted......but i didnt
and now i feel like an ass for bothering anyone about it now that i found this
https://market.android.com/details?id=com.joeykrim.flashimagegui
Click to expand...
Click to collapse
Okay now I have no idea what you're talking about because you're talking irrelevance now. But anyway, the OP has what he looked for in this thread. Congrats. I only responded to give him his answer on that he was surprised that there wasn't much changes within the recovery.
Nothing is really ever changed in a recovery as it is 100% functional. The Clockwork Recovery version only really increases because of additional support of Clockwork recovery for other Android phones, tablets.

[Q] Rom/kernel devs?

just Got my Mytouch today !! i dev for the epic 4g but since i gained employment at Tmobile ive decided to get another phone just curious
how many rom/kernel dev's are there ?

lol.. we just got it rooted. Roms should be out within another month or so..

a month lol not even that long my dude

Well I saw CM7 is being ported by nightly to the sensation. You know the sensation and the mt4gs are like twins with different personality. Also to get a camera apk to work on other rom didnt they released the source for this phone on htc dev site.
Sent from my myTouch 4g Slide.

Yea, I suspect that the first beta roms will start appearing in a few weeks, maybe sooner. But I wouldn't expect stable roms to start showing up for at least a month.
The camera is going to be one of the things holding it back.
I, personally, would like to see some almost stock roms with CPU control....I would like to see sense go away, but it appears that would effect the camera to some extent. Either way, I'm happy to have root at this point. At least I was able to uninstall the bloakware and crap that I couldn't seem to stop running in the background.

Well when I get home tonight ill give a look into the source codes that htc released. I'll let you guys know if the frameworks is in it or not.
Sent from my myTouch 4g Slide.

I can try and port a sense 3.0 rom for you guys, but i'll need testers for it. And to the above poster, porting from Sensation to MT4GS isn't easy, this device has WVGA, while Sensation uses qHD instead.

Ace42 said:
I can try and port a sense 3.0 rom for you guys, but i'll need testers for it. And to the above poster, porting from Sensation to MT4GS isn't easy, this device has WVGA, while Sensation uses qHD instead.
Click to expand...
Click to collapse
If you do this, try and incorporate the stock camera .apk from the tmobile rom.
I REALLY think it's totally sense specific like the other sense rom cameras.

ratchetrizzo said:
If you do this, try and incorporate the stock camera .apk from the tmobile rom.
I REALLY think it's totally sense specific like the other sense rom cameras.
Click to expand...
Click to collapse
That camera has been ported already, I'll try and include it, but i'll need testers since i don't have a 4g slide. I'm doing this to speed up development and i have experience with the whole porting thing.

Ace42 said:
That camera has been ported already, I'll try and include it, but i'll need testers since i don't have a 4g slide. I'm doing this to speed up development and i have experience with the whole porting thing.
Click to expand...
Click to collapse
Really?! To what phones ? I went to check if HTC uploaded the Doubleshot source code and nop not there XD.

sonicjam said:
Really?! To what phones ? I went to check if HTC uploaded the Doubleshot source code and nop not there XD.
Click to expand...
Click to collapse
Not by htc, by members of xda of course. I've used the MT4GS camera on a rooted ver of the MT4G's 2.3.4 build and it works fine.
And on another note, i've finished the alpha port, i'll upload it to multiupload
EDIT: Heres the test rom
http://www.multiupload.com/GR0ELB5XY4
I recommend that you guys do a nandroid prior to trying the rom.

DOWNLOADING - I'll keep you updated!

going to take my girlfriends's phone today and try the rom, thanks.

initial install has me hanging at splash screen.
redownloading to make sure it wasn't just a bad download.
interestingly, the install in CWM took like 5 seconds.. literally. so fast I couldn't even read what it was doing.
will report back shortly.
edit: second go-around with a fresh download and I'm still stuck at splash screen. formatted /data, /cache, /system and deleted .android and android-secure on my sd card prior to flashing.
do you need a logcat, Ace?

pmcqueen said:
initial install has me hanging at splash screen.
redownloading to make sure it wasn't just a bad download.
interestingly, the install in CWM took like 5 seconds.. literally. so fast I couldn't even read what it was doing.
will report back shortly.
edit: second go-around with a fresh download and I'm still stuck at splash screen. formatted /data, /cache, /system and deleted .android and android-secure on my sd card prior to flashing.
do you need a logcat, Ace?
Click to expand...
Click to collapse
Yes, please upload one. And remember guys to make a nandroid always just in case.
Sent from miuiTouch 4G

Ace42 said:
Yes, please upload one. And remember guys to make a nandroid always just in case.
Sent from miuiTouch 4G
Click to expand...
Click to collapse
well I'd happily provide, but I can't get it. never run into this when trying to pull logcat.. judging from that error message, it sounds like /system isn't being written to during install? I dunno. let me know if I can help any other way, or if you have a suggestion for pulling a logcat another way.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\mark.abrahamsen>adb logcat
- waiting for device -
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
restoring my backup for now.

I NANdroided, wiped data/cache/dalvik and installed from zip. Like pmcqueen said it flew through the install and rebooted automatically on me. It doesn't look like it actually rewrote/installed anything because my custom boot animation was still there from before. Unlike pmcqueen mine booted up fine, pretty fast actually, but acted as if I had just performed a fresh wipe of the ORIGINAL ROM; it took me through the MT4GS video and was the same rom, only as if I had just performed a factory reset. I wonder if it's clockwork that didn't perform the necessary functions? Are the files/folders/locations different on the MT4GS and that's why it didn't write anything? I didn't get any error messages... It's been a long time and I don't remember how to run logcats, so refresh me, and I'll hook you up. But it sounds like it just didn't install anything at all.

I think I know the issue, i'm working on it right now. I'm about to upload the 2nd test in a few minutes.

Ace42 said:
I think I know the issue, i'm working on it right now. I'm about to upload the 2nd test in a few minutes.
Click to expand...
Click to collapse
(patiently refreshing...)

unclespoon said:
(patiently refreshing...)
Click to expand...
Click to collapse
It's gonna be some time for some reason multi drops my upload speed to around 100KB/sec, it's at 50% right now.
Edit: 2nd Alpha is up, really hoping this ones a keeper
http://www.multiupload.com/7ZZRBBZBUM
#Removed non-compatible files and made other edits

How do we get a true CWM recovery, an not just a boot hack

Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.

jimbridgman said:
Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.
Click to expand...
Click to collapse
a few things.
1. it was not anything you did that made me wipe recovery, it was just me being a complete idiot
2. basically I think we need to figure out how to modify what you cat'd over. then we can pull an image from a similar device that has a true cwm recovery and edit what we need to like the specific partitions in order for it to work on our phone. then we can just cat it over and bingo! working full cwm.
3. why is it that stupid things I do always end up leading to great discoveries on here. this is like the 3rd time it has happened.
so any ideas on how to mount that file in a way we can actually look at it.
---------- Post added at 09:39 PM ---------- Previous post was at 09:22 PM ----------
Some more stuff I found: http://www.clockworkmod.com/rommanager
That has official cwm recovery builds for all supported devices. many have images, I think all the ones with unlocked bootloaders. those images would be flashed with fastboot, or probably could be cat'd over like we did.
others have flashable zips (all the moto devices) and i think those are all the ones with lockked bootloaders. I don't have tie to dig into what they really do right now, but i appears that they just copy some files for recovery to /etc and other places suggesting those devices have a different recovery method
I still think the biggest priority is figuring out how to see the contents of the images with our recovery stuff and those for other devices.

I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!

JRW 28 said:
I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!
Click to expand...
Click to collapse
what is BP tools even
Sent from my MB865 using xda premium

lkrasner said:
what is BP tools even
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I've wondered the same thing????

JRW 28 said:
I've wondered the same thing????
Click to expand...
Click to collapse
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too

lkrasner said:
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too
Click to expand...
Click to collapse
Yea but even on a normal boot I could never get past the red moto screen, tried several times hopi g to get into CWM and not have to RSD back.
Just wierd that normal boot wouldn't work but BP tools did?

The only difference I could see is an app called CQATest in the drawer. Has many different tests available. About 50+
Sent from my MB865 using xda premium

made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.

So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff

lkrasner said:
made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.
Click to expand...
Click to collapse
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl

lkrasner said:
So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff
Click to expand...
Click to collapse
I suspected that might be the case.

jimbridgman said:
I suspected that might be the case.
Click to expand...
Click to collapse
any ideas why.
Sent from my MB865 using xda premium

jimbridgman said:
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl
Click to expand...
Click to collapse
mine gave me a ramdisk.cpio.gz and a kernel.gz, I didn't extract that. it was also a pearl script, so probably the same one.
Sent from my MB865 using xda premium

I know I have posted here way to many times. But I want to get this to work.
It seems motorola has done more weird **** to their recovery partitions. Normally you can use certain scripts and binaries to separate a boot or recovery image (they follow the same format) into the ramdisk and kernel. That SHOULD be all that is in them. you can then modify the ramdisk to your liking, or use the kernel with cwm or the like to make it work. However it seems there is more to our image than just the ramdisk and kernel. when I extract them and repack them it seems to work fine, but the result is 5.5MB instead of 9.4MB with no modifications.
Does anyone have any idea what the deal is with that? I think if we can figure out that part we should be able to get a true custom recovery.
P.S. are you sure we cannot replace our boot.img with this same copying method? That is if we could even figure out how to modify it. Is there a hardbrick risk in trying? if so, Any volunteers?
EDIT: so our boot image will unpack and repack to the same exact size, so I think that means we could theoretically edit the ramdisk if that would do any good. the question still remains whether the phone checks its signature on boot or only upon flash

Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium

Harrison85 said:
Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I can make a small change that would make it un verified then someone could copy it over and see if it boots. the problem is I am not 100% sure we would be able to restore to the original if it would not boot. I am 99% sure we would be fine, but I don't want to risk bricking completely. My guess is jim will know if it is safe to test or even worth trying, but if you want to be the guinea pig just tell me and I'll send you instructions.

By all means throw Me instructions and I will give it a shot right now
Sent from my MB865 using xda premium

Nevermind. I was sort of wrong. Both images separate just fine and can be recombined, but extracting the ramdisk seems to not extract the whole thing, it is much smaller when it is repacked. therefor you cannot really edit it at all.
Any ideas why?? I think it is just Moto being a pain in the ass as usual.

lkrasner said:
Any ideas why?? I think it is just Moto being a pain in the ass as usual.
Click to expand...
Click to collapse
That is it in a nutshell. They pack their boot image in a different way from all other phone manufacturers, and not in a standard way for android. That is why Moto has their own "special" non-standard bootloader. They use a bitblast to package the boot image files, on top of the standard tgz, so the important files are "zip blasted" on top of the others in "superbit blocks", so there is not much we can do, unless we can de-a-line them, but that is not something I even want to start poking at.

[RECOVERY] ClockWorkMod Recovery [Updated 7/22/12 - New Info]

EDIT: Koush is working hard on compiling CWM6 for all the newer devices. He already has a working version for the international S3 up so we should be looking at getting it here shortly. Notable differences, 720p support. Once it is official for us I will post it. If it is fully functional I will remove everything except my port, and the stock option that way people are not confused, but can still have some preference if need be.
Edit 2: When pushing a new recovery do it TWICE before using. I know mine works fine. My version should display as v.5.8.4.5
Edit 3: ROM Manager does NOT work with any recovery except the official recovery by Koush. You CAN boot into recovery via ROM Manger on the others, but that is it.
I am not responsible for your newly formed brick! I am also not an ADB expert, please search if you need help! ROM Manager DOES work with this version, you must install recovery manually first, then use ROM Manager to boot into recovery. Since we don't have any custom ROM's yet I can't say it works to install them.
Use whatever method you are comfortable with to push this, be it ADB or Terminal Emulator. CWM Standard can be installed via ROM Manager. The direct link for the Touch version is posted below to avoid purchase costs. Not superseding paying, Koush specified that pushing the recovery manually is free of charge.
Terminal Emulator commands: (Thanks - pdinphx)
Remember to change the name of the recovery, OR change the command line to reflect the name of the recovery! (Replace recovery.img with the appropriate img file name.)
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
# reboot recovery
Click to expand...
Click to collapse
Lastly, DO NOT donate to me for this, PERIOD. This is none of my work, all I did was push a couple buttons.
Credit: Koush for Recovery Builder (and for the Official Sprint Version)
Samsung for everything essentially
And everyone who made a tutorial for Terminal Emulator and/or ADB that people might be using.
All Recoveries:
Touch - My CWR Touch Port
Stock Recovery - from Sammy's update (this is the stock Android recovery)
CWM Recovery Official Standard: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.4.9-d2vzw.img
CWM Recovery Official d2spr Touch http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.9-d2spr.img

How would this work if we use recovery for custom kernels?

Let me figure out one thing at a time, lol. I am a newb dev. I know almost nothing about custom kernels aside from how to flash them on a device with an unlocked bootloader.

AtLemacks said:
Placeholder.
I am currently using the Recovery Builder Koush made for CWR. If anyone beats me to the punch, let me know because we don't need a thousand different CWR versions. I planned on building a touch version.
Click to expand...
Click to collapse
good luck with this, i've tried several recovery.img's on his builder site
none of them worked for me
since he doesn't have source (i still dont understand why) it might be a bit
do we have twrp for this?

I don't think we have any recoveries aside from the one you ported. You input the image from the update tar?

AtLemacks said:
I don't think we have any recoveries aside from the one you ported. You input the image from the update tar?
Click to expand...
Click to collapse
i didn't port that recovery, its the exact one from the e4gt team
i tried using the one from the stock image (in the sticky on this forum)
i think we might have better luck (although more work) getting TWRP going on this
we have source code with that, plus it has more features

True... Is anyone from TWRP getting the phone?
Took nearly 10 minutes but I got a recovery output img from the builder. I am about to jump off here really quickly though, I have to be up at 4:30am. I'll PM you the img and you can take a look.

invisiblek said:
i didn't port that recovery, its the exact one from the e4gt team
i tried using the one from the stock image (in the sticky on this forum)
i think we might have better luck (although more work) getting TWRP going on this
we have source code with that, plus it has more features
Click to expand...
Click to collapse
Just used TWRP today for the first time on my Prime. I really like it and was hoping it would come to this. My vote goes to TWRP. I'm no good with dev work but can try and help out if needed. I'm a good tester lol

Haro912 said:
Just used TWRP today for the first time on my Prime. I really like it and was hoping it would come to this. My vote goes to TWRP. I'm no good with dev work but can try and help out if needed. I'm a good tester lol
Click to expand...
Click to collapse
In my experience, never test what a dev wont test, lol. I'll gladly brick my phone as I have backups. I wouldn't push something I am not sure about onto you.

Just in case votes are being counted <wink> I vote TWRP.
Sent through mental telepathy...or my G-Nex

AtLemacks said:
In my experience, never test what a dev wont test, lol. I'll gladly brick my phone as I have backups. I wouldn't push something I am not sure about onto you.
Click to expand...
Click to collapse
If the dev won't put on it a phone they own then it won't go on mine. But if they have it and aren't having issues then I will test and see if I get any. 2 people never use their hone the same way.

http://goo.im/devs/birdman/twrp8.img
Sent from my r00ted SCH-I535 using Tapatalk 2

Mean Sixteen said:
Just in case votes are being counted <wink> I vote TWRP.
Sent through mental telepathy...or my G-Nex
Click to expand...
Click to collapse
I second this. I have never liked CWM. Rather have Amon Ra but this isn't an HTC phone. Lol.
Sent from my ADR6425LVW using xda app-developers app

For all you that like TWRP!! Here you go!​

Woo Hoo. Now if I could only make it Tuesday NOW so I could root mine and install TWRP.
Can't wait and I am guessing I will be able to flash a custom kernel by then.
Sent through Mental Telepathy...or my TF201

For those potentially still interested I will try to work on this more tonight and test it out. I had to work 5 hours late due to a big fire/hazmat call at a factory out here. I smell like peppermint now because it was a potpourri fragrance plant -_-... Post progress of my testing later.

appdroid said:
For all you that like TWRP!! Here you go!​
Click to expand...
Click to collapse
Can't wait to flash this tomorrow.
Sent from my Ally using XDA

NightxFall said:
Can't wait to flash this tomorrow.
Sent from my Ally using XDA
Click to expand...
Click to collapse
flash it just like cwm in the root thread
i'm going to update the thread on that too, thanks for reminding me

invisiblek said:
flash it just like cwm in the root thread
i'm going to update the thread on that too, thanks for reminding me
Click to expand...
Click to collapse
anybody have any luck with TWRP seeing internal sd contents?
**edit** or cwm for that matter?

Nope, testing right now finally. No luck even booting.

[TWRP] Who wants TWRP on ARIES?

Step 1) From the root of your android device tree:
Code:
mkdir -p .repo/local_manifests
curl http://teamacid.github.com/manifests/sgh-t959v/TWRP/twrp.xml > .repo/local_manifests/twrp.xml
Step 2) Wait for noiphonehere to update his tree to include my commit, the sync your device tree to match his
OR (for the impatient)
Cherry pick my commit yourself:
https://github.com/fbis251/android_...mmit/fe504f4d7602432d5de97585698af963aafdd0ab

heard that idevice is kinda excited when seeing this haha

Nice.
I might add this.
Sent from Aries within the 1st Galaxy

Is it more of a personal preference or is TWRP better then CWM?
Edit .... is this simply to allow users to switch to TWRP if I build with CWM?

Have you guys heard of 4ext touch recovery?

Dwack said:
Is it more of a personal preference or is TWRP better then CWM?
Edit .... is this simply to allow users to switch to TWRP if I build with CWM?
Click to expand...
Click to collapse
TWRP includes a file manager in recovery, so if something goes horribly wrong and you need to replace a required init.d script file, you can actually do it without needing a computer for your ADB.
It also looks pretty. And is touch friendly. Friendly touch. Good touch. Mhmm.
But it's the file manager that makes me choose TWRP over CWM any chance I get.
Cooptx said:
Have you guys heard of 4ext touch recovery?
Click to expand...
Click to collapse
According to what its developer says at http://www.4ext.net/status_update.php we're unlikely to ever be supported.
Unlikely:
Older Samsung devices like:
Samsung Galaxy SII
Samsung Galaxy Note
Click to expand...
Click to collapse
Maybe we should focus on recovery options that actually work for our phone?

I was asking if you have ever heard of it. I wasn't asking for it

Theraze said:
TWRP includes a file manager in recovery, so if something goes horribly wrong and you need to replace a required init.d script file, you can actually do it without needing a computer for your ADB.
It also looks pretty. And is touch friendly. Friendly touch. Good touch. Mhmm.
But it's the file manager that makes me choose TWRP over CWM any chance I get.
According to what its developer says at http://www.4ext.net/status_update.php we're unlikely to ever be supported.Maybe we should focus on recovery options that actually work for our phone?
Click to expand...
Click to collapse
Well....
Nexus S has the same hardware we have....

http://forum.xda-developers.com/showthread.php?t=1646108
For all your file managing needs

i've used it. it's nice.

TWRP will be pretty awesome
I tried CWR Touch on my friends SGS2 and its a bit buggy. CWR is ok but TWRP makes it easier and has a file manager too!

It already is. If things go to plan tonight I might have a present for you guys .

@FBis251: Yo man, , sr that I thought u asked how was the TWRP kernel flashing man so I told u it was normal but just after flashing a ROM via TWRP, I knew what u asked It couldn't flash properly (or mayb just my compile got this not yours ^^)

daothanhduy1996 said:
@FBis251: Yo man, , sr that I thought u asked how was the TWRP kernel flashing man so I told u it was normal but just after flashing a ROM via TWRP, I knew what u asked It couldn't flash properly (or mayb just my compile got this not yours ^^)
Click to expand...
Click to collapse
After using your kernel, TWRP wouldn't backup or flash anything. Gonna go back to stock and work my way back up because I can't flash anything with CWM in it.
Sent from my SGH-T959V using xda app-developers app

Whoa weird. I've been able to restore/backup properly on mine. I need to mess around with the cm10.1 based version of it since all of my testing has been on team acid's aries cm9.
The JB kernel might be adding problems to TWRP, but on ICS it's still working fine, even flashing noiphone's cm10.1 build worked from TWRP.

Yeah I ran in to this last night trying to back and flash a new ROM. I could restore from an old back up, it was fine until it reached the recovery part then it freaked you out.
I had to one click.
Sent from my SGH-T959V using xda premium

johnadelic said:
Yeah I ran in to this last night trying to back and flash a new ROM. I could restore from an old back up, it was fine until it reached the recovery part then it freaked you out.
I had to one click.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Okay I know exactly what you mean and was able to replicate the issue. I'll try to see what's going on behind the scenes for this since a boot.img restore should only take a second or two when you recover from a backup.

Something about color/overlay image could not be applied (something like that) in adb shell adb logcat when u go into recovery with twrp.
Sent from my SGH-T959V using Tapatalk 2

Has anyone compiled a flash able yet?....just curious.
From my T959W running Illusion