yashsingh1/xdaforums huggingface dataset:
[T-Mobile myTouch 4G Slide] Fuzi0719:
So if we want to flash a Sense ROM, we need the older 5.5.0.4 or 5.0.2.7 CWM recovery, but if we want to flash a JB4.2 ROM we have to use one of the newer recoveries? That would make swapping ROMs a nightmare. I've wanted to try one of the JB4.2 ROMs but I normally play with them a bit then go back to Miktouch 0.7 as my daily. I don't relish having to flash different recoveries, too.
[T-Mobile myTouch 4G Slide] SilverL:
Unfortunately... thats all I got for you right now. I cant confirm. I think I have been able to flash the MikTouch with TWRP... but I cant remember since between all of what I've been doing testing and whats not I accidentally erased my SD and dont feel like putting such a large file back on my SD for no reason.

Like you said I dont relish flashing different recoveries and I'm not going back to an older recovery since all my work lies in JB 4.2 right now. You may be able to get around things by updating one of the binary files in the zip package, but I cant remember which one. Just because they updated the recovery source code this is one of the... repercussions...
[T-Mobile myTouch 4G Slide] demkantor:
Re: [Recoveries][Mar-13-13] TWRP 2.4.4.0 + CWM 6.0.2.7

I can confirm miktouch is flash able with twrp 2430, 2420, 2410 as well ss latest 4.2 ROMs, I was having an issue flashing scverhagen's cm 9.1 ROM (still haven't sorted that one out :mad: ) one of the things I was trying to do to get it to flash was changing recoveries, tried 6 or 7 different ones and I kept flashing back to miktouch and and a few other ROMs just to see what's up.

Have not flashed 2440 yet but I can't see why it wouldn't flash both unless something big changed between versions, if it did I would assume it would be twrp 3.0
[T-Mobile myTouch 4G Slide] butch87402:
Re: [Recoveries][Mar-13-13] TWRP 2.4.4.0 + CWM 6.0.2.7

I was just about to say the same thing the 230 version does both...thought it was ny newly bought 32gb sd card ...well good to know ill just go back to that version of twrp just thought I would ask
[T-Mobile myTouch 4G Slide] DoomGaZer:
Re: [Recoveries][Mar-13-13] TWRP 2.4.4.0 + CWM 6.0.2.7

I can confirm that TWRP 2.4.4.0 does NOT flash MikTouch and produces the aforementioned error every time. I tried several times the other day.
[T-Mobile myTouch 4G Slide] SilverL:
Meh. Have fun guys!

I think its the update-binary in the META-INF folder. try replacing the one in MikTouch with one from one of the future, better roms. -_-
[T-Mobile myTouch 4G Slide] Fuzi0719:
Except Miktouch is the only ROM where everything works like it is supposed to work without any "gotchas" :cool: I just tried 2.4.4.0 and can confirm it doesn't work with Miktouch. I put on 2.4.3.0 and it does. Also, on both I notice the time setting does not acknowledge the Daylight Saving Time switch. Checking that does not alter the time, it only alters the code at the bottom of the screen. I have to set my time zone to the zone in front of me to get the correct time.
[T-Mobile myTouch 4G Slide] SilverL:
Psh, that doesnt count as a rom. Its a mishmash of the stock and other sense(ie stock from htc) stuff. Of course it will work without gotchas it came from the developers then got twiddled with by others. Technically stock worked without gotchas too.
[T-Mobile myTouch 4G Slide] cryptic3:
There is a update to twrp but i dont see our device.... do we use the sensation device
[T-Mobile myTouch 4G Slide] anitgandhi:
Seeing as it just came out, silverL probably hasn't seen it yet, and therefore hasn't updated this. And even then, he doesn't have to.

DO NOT flash the official sensation one, you might brick the phone. Just wait it out. Regardless, 2.5 doesn't have massive changes over 2.4.4.0, so just sticking with 2.4.4.0 wouldn't be an issue
[T-Mobile myTouch 4G Slide] SilverL:
I will get to it eventually.
[T-Mobile myTouch 4G Slide] cryptic3:
No rush appreciate the work mate
[T-Mobile myTouch 4G Slide] SilverL:
Update TWRP, will try to get CWM updated sometime this week.... most likely the weekend...
[T-Mobile myTouch 4G Slide] Fuzi0719:
I and a few other people had some issues with 2.4.4.0, had to revert to 2.4.3.0 because of those. Hopefully, 2.5 solves that.
[T-Mobile myTouch 4G Slide] SilverL:
I doubt it. Cant say for sure since I'm too lazy to check every commit. The problem they had stemmed from an API update in the recovery. Because of it they couldnt falsh roms that used the old updater-binary. They could manually replace it in the rom zip file... but whatevs.
[T-Mobile myTouch 4G Slide] Fuzi0719:
nm
[T-Mobile myTouch 4G Slide] cuiltheory:
Well, the twrp does not like some roms. It will not flash where the cmw will flash with no problem. I like the twrp for the touch, but can not use it at present time. I try the cmw touch version, but did not work. Went into boot loop. Too bad that 4ext is not available. I had mt4g before and 4ext worked fine there.
[T-Mobile myTouch 4G Slide] SilverL:
This is false. The update should also be in CWM... the reason this CWM still works is because I have yet to build the latest CWM. The problem is not that TWRP does not like some roms, OLDER roms have an older updater binary which doesnt adhere to the new API. If the manufacturer of the rom is not updating the rom to the latest binary all you have to do is replace it yourself with one from an up-to-date rom.

4ext most likely still works because of the source it uses, which I can only assume is still using the older API, because it is closed source.

CWM Touch also uses closed source parts which means it has to be built by Koush's builder.

Again, if you want to be able to flash older roms replace the file. Its as simple as opening the zip file and putting the binary file from an up-to-date rom in it. The roms with this problem will continue to have the problem especially if they are no longer maintained.

PS. If CWM is not using the lastest API now... then thats cool.... but it may eventually. We'll see.
[T-Mobile myTouch 4G Slide] Fuzi0719:
TWRP 2.4.3.0 and CWM 6.0.2.7 don't give me any problem with my older ROM.
[T-Mobile myTouch 4G Slide] SilverL:
CWM 2.0.2.7 isnt the latest. I guess I wont be updating that. I dont have any problem roms to test with. I did once have a problem with flashing one zip file and after doing that switch worked fine. Oh well. Keep what works for you. Thats what I live by. :)
[T-Mobile myTouch 4G Slide] mattlowry:
when using twrp I would sometimes get errors flashing after wiping. so what I would do is after I fully wipe I reboot recovery. then flash rom. not just mt4gs same problem on note 2 as well
[T-Mobile myTouch 4G Slide] strapped365:
Twrp has been a disaster ever since I can remember. Hell on the N4 it was overheating and bricking devices, on the speedy it wouldn't flash Sense ROMs, plus all the issues here make it seem like a very buggy recovery in general.

Sent from my Nexus 4
[T-Mobile myTouch 4G Slide] SilverL:
I dont see how you guys have all these problems. Though I can see how the latest anything can be buggy... As far as overheating and bricking that can happen in any... hell every recovery... it would have happened here too if I made any mistake in the fstab.

I would build the latest cwm but that would require me to set up a CM-10.1 environment for it... since it wont build on the CM10 environment I currently use when building these recoveries.
[T-Mobile myTouch 4G Slide] strapped365:
Well the problems aren't just device specific. TWRP has many bugs across multiple devices. I don't think its user error or anything.

Sent from my Nexus 4
[T-Mobile myTouch 4G Slide] SilverL:
and it happens, every rom has its share of problems before they're perfect, even cwm had its problems, still does to this day where people complain about using it and rom manager. To each his own. Some will have problems, some wont.

Strange enough to say that they're both based on the stock recovery source. TWRP modified the code to cpp though...

Anyway both recoveries updated. Since CWM 6.0.3.1 didnt want to build in a CM1o initialized repo, I redid a CM10.1 environment to build it and rebuild TWRP in the same environment.

Hopefully no one has any problems with either.
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
If this has already been covered I apologize but what IS dumlock and it's significance?
[T-Mobile myTouch 4G Slide] demkantor:
Its for s-on fellas, its to flash the boot.img for them, which I guess would be nice but its just one more thing that allows people to say, I guess unlocking is all I really need, when 9 out of 10 times they are better off gaining radio s-off
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
OK...now I understand. And I do agree with getting true S-Off but you have to admit that's a pretty nifty built in feature right there. I was thinking of giving this a spin myself. Have you and if so is it pretty solid?
[T-Mobile myTouch 4G Slide] demkantor:
Well no, it wouldn't do anything for me as when I flash a rom the kernel is also flashed, I'd have to add security flags for it to do anything
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
Will this not even flash a ROM & kernel together or are you only referring to the dumlock feature? The interface is GREAT but it would need both options I would think.
[T-Mobile myTouch 4G Slide] demkantor:
.never used it but I assume it would still work fine for you, feel free to test but I would just suggest using the twrp without it if you don't need it
[T-Mobile myTouch 4G Slide] Ziida:
yea- Don't use the dumlock features if you're already s-off
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
I got it now. The one with dumlock is for S-On....the one without is for S-Off. Thanks for your patience, it's been one of those days. LOL
[T-Mobile myTouch 4G Slide] anitgandhi:
It's basically 4ext smart flash for s on. Except the process isn't straightforward
[T-Mobile myTouch 4G Slide] butch87402:
Seems like a lot of work to me... And if you mess up you're screwed

http://teamw.in/project/htcdumlock
[T-Mobile myTouch 4G Slide] anitgandhi:
you should try to make these official! cuz they seem solid to me (well atleast twrp, i can't speak for CWM)
[T-Mobile myTouch 4G Slide] Crestus:
I'll second this. TWRP works like a champ on my device! :D
[T-Mobile myTouch 4G Slide] demkantor:
and we have a third! so... can we request your work be added to the official list or how does this work?
[T-Mobile myTouch 4G Slide] anitgandhi:
Twrp is open source so I doubt they'd mind. I'm sure they might have to check a few things to make sure we're OK to be included...the double shot isn't on their interest list but that's cuz not many have it
[T-Mobile myTouch 4G Slide] SilverL:
Update TWRP to 2.6.0.0 and CWM to 6.0.3.3
[T-Mobile myTouch 4G Slide] butch87402:
Yeaaaaaaah been waiting for an update
[T-Mobile myTouch 4G Slide] SilverL:
Hope you guys didnt miss me too much.

Update TWRP to 2.6.3.0 and CWM to 6.0.3.6

Had them and forgot to upload them.... sorry.
[T-Mobile myTouch 4G Slide] Dukenukemx:
Glad to see you're back.
[T-Mobile myTouch 4G Slide] Fuzi0719:
Argh! I discovered that Windows 8.1 won't allow adb or fastboot. Thankfully, I still have my Windows 7 installation to boot from and that allowed me to fastboot flash the new twrp recovery.
[T-Mobile myTouch 4G Slide] SKAm69:
Really? At least it works on Windows 8.0 as I have just flashed the new twrp with fastboot.
[T-Mobile myTouch 4G Slide] demkantor:
http://xdaforums.com/showthread.php?t=2347317
[T-Mobile myTouch 4G Slide] Fuzi0719:
I had found that thread and tried every suggestion, doesn't work for me (or this phone). I had previously had adb/fastboot working on Win8, but after the "upgrade" to 8.1, I get nothing. I'm just glad I still have my dual-boot to Win7.
[T-Mobile myTouch 4G Slide] SilverL:
Updated CWM to latest version. Will be needed for future 4.4 builds so devs dont need to worry about finding the right repo with the mod to allow older recoveries to flash.

TWRP is build from a recent pull but version number hasnt changed because it has only had cleanups since.

Happy New Year guys!!
[T-Mobile myTouch 4G Slide] Xaekai:
TWRP doesn't seem to allow me to flash certain roms, examples include scverhagen's CM9.1 and MikTouch. It throws an assert.

Ah well, CWM works fine for them. But I like having a touchscreen enabled recovery, it's sexy.
[T-Mobile myTouch 4G Slide] acwest:
adb on TWRP

I am using the TWRP 2.6.3.0, and seem to be unable to use adb with it. All of the posts I have seen regarding this problem seem to be focused on getting the correct Windows usb driver to recognize the device, but as I am not using Windows (with it's rather ridiculous USB stack) this should not be a problem. Has anybody had similar issues on OS-X?
[T-Mobile myTouch 4G Slide] acwest:
adb revisited

I looked at the problem a little bit more, and it seems likely that there is something wrong in the adb code in this version of TWRP. The Vendor ID and product ID in TWRP match the ones when the phone is booted normally, which is about the only thing I could think of which might be interfering with things. Does adb work for anybody in TWRP 2.6.3.0?
[T-Mobile myTouch 4G Slide] FRooter:
[MENTION=2878915]SilverL[/MENTION], would you mind if I hosted a mirror of your recoveries for the myTouch 4G Slide? My interest stems from this model phone being the default issued to everyone at my workplace, and I wanted to share with faster download speed, via both HTTP and FTP. If you desire or prefer, I am happy to provide you with full access to file management.
[T-Mobile myTouch 4G Slide] SilverL:
That would be nice. My friend who was doing the hosting recently had to stop his account. So I currently have nowhere to host.
[T-Mobile myTouch 4G Slide] FRooter:
I've followed-up via e-mail and PM. I look forward to assisting any way I can. :]
[T-Mobile myTouch 4G Slide] SKAm69:
CWM link seems down
[T-Mobile myTouch 4G Slide] FRooter:
Which CWM link, newer or older? The newer of the two appears working for me:

# wget -N http://www.stetsentech.com/lomarb/cwm6046.img
--2014-04-08 18:55:26-- http://www.stetsentech.com/lomarb/cwm6046.img
Resolving www.stetsentech.com... 66.147.244.241
Connecting to www.stetsentech.com|66.147.244.241|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6490112 (6.2M) [application/octet-stream]
Saving to: “cwm6046.img”

100%[========================================>] 6,490,112 1.77M/s in 3.6s

2014-04-08 18:55:30 (1.71 MB/s) - “cwm6046.img” saved [6490112/6490112]

# md5sum cwm6046.img
9d37a1029b9f5e79bbef8cb55632e7d7 cwm6046.img
# sha1sum cwm6046.img
0861f3c04f652ae96f94bb662c53f6d7e04af94b cwm6046.img

Here's an alternate download location: cwm6046.img via HTTP or cwm6046.img via FTP
[T-Mobile myTouch 4G Slide] SKAm69:
The alternate links worked, thanks.

BTW ther TWRP 2.7 is out, I hope SilverL will make it for us too :)
[T-Mobile myTouch 4G Slide] Dukenukemx:
I've tried both recoveries and get this with some roms.

assert failed: getprop("ro.product.device") == "doubleshot" || get.prop("ro.build.product") == "doubleshot"

But going back to the official ClockworkMod Recovery 5.0.2.7 doesn't cause this issue.
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
Same here (trying to flash MikTouch to S-OFF):

assert failed: getprop("ro.product.device") == "E:Error executing updater binary in zip

Have since went back to 2.2.2 but I'll probably have to upgrade to satisfy my backup. Is the newer version required to access the newer ROM's?
[T-Mobile myTouch 4G Slide] abe5:
Yes, new ROMs will require a custom recovery's latest version. The same applies to new GAPPS packages.

Therefore, flashing an old ROM means downgrading the custom recovery.
[T-Mobile myTouch 4G Slide] HDR:
Can someone please re-up these somewhere?

Nvm, found this, TWRP 2.7

https://www.copy.com/s/SPiSXSSxRJHV/Android/Recoveries/twrp2.7-doubleshot.img

Not mine, found in the 4.4.4 ROM thread.
[T-Mobile myTouch 4G Slide] Emmanuel U:
Yea I built that when I was trying to fix the recovery adb problem, personally I haven't fully tested all features to make sure it's stable but it should be fine as it's bassed off my cwm 5504
[T-Mobile myTouch 4G Slide] PsychoPhreak:
Links on page one all appear broken. Anyone have a mirror of the older version, 6.0.3.6? Trying to flash my doubleshot currently running kitkat back to an older CM version.

Found 5.5.0.4 in EmmanuelU's backup files, should that be sufficient/new enough to flash ICS or JB roms?
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
I would go older CWM (5.5) for older ROM, or risk getting an assert failure. But if you are looking for new ...

http://www.rootfiles.org/pub/mirror/silverl/cwm6046.img

http://www.rootfiles.org/pub/mirror/silverl/twrp2630.img

http://www.rootfiles.org/pub/mirror/silverl/twrp2630dl.img

...the mirror links are near the end of the thread (TWRP ones I guessed at, but appear to download).
[T-Mobile myTouch 4G Slide] PsychoPhreak:
The 5.5 I found worked perfect to flash the CM9.1 ICS img I wanted, thanks!
[T-Mobile myTouch 4G Slide] FRooter:
Here are links to the older set, also in the same location

http://www.rootfiles.org/pub/mirror/silverl/cwm6036.img

http://www.rootfiles.org/pub/mirror/silverl/twrp2630-old.img

http://www.rootfiles.org/pub/mirror/silverl/twrp2630dl-old.img

I've opened the directory index so it's no longer 403 Forbidden when trying to browse the specific path.

Parent directory: HTTP / FTP / FTPES

Not much else is in there for [MENTION=2878915]SilverL[/MENTION] at the moment, but I can try to add more if needed.

---------- Post added at 01:40 PM ---------- Previous post was at 01:32 PM ----------

cwm6036.img worked best for me to flash CM9.1; I didn't have such great luck using the more recent cwm6046.img.
[T-Mobile myTouch 4G Slide] Dukenukemx:
It should be noted that the older recoveries work, where the new ones don't work. The new ones don't verify the device properly.
[T-Mobile myTouch 4G Slide] steve_77:
So just to clarify - if i re-flash TWRP 2.6.3.0 as my recovery - from my understanding it will :

1) charge while in recovery

2) it will be backward compatible with the older twrp versions should i ever need to reflash my backups (current version is TWRP 2.6.0.0)

is this correct?
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
Quick note:

1) I seen the plus sign next to battery, and maybe even it increasing over time in TWRP 2.6.3, so I assume it charges. But I am not sure. These days I'm still using 2.2.2 due to the ROM I stuck with.

2) It is. I restored a 2.2.2 backup once with 2.6.3, without a hitch (although forget the reason why).
[T-Mobile myTouch 4G Slide] steve_77:
what rom are you using, that you cant move to 2.6.3 (?) - im hoping this is compatible with Emmanuel U's KKDS series of ROM's....
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
I'm using the older CM 10.1. I used JellyBeanDS and KitKatDS (v1.3) with 2.6.3, no problems. But with 10.1 I got assert failures on install (typical with the newer TWRP's and older ROM's), so I had to go back.
[T-Mobile myTouch 4G Slide] steve_77:
TWRP v.2.6.3.0 w/ 'mount usb storage' button and NTFS SD Card

Um so Ive been having some issues lately - this is my 4th time installing KKDS 1.4 - the first time was dirty (over 1.3), the second I tried ART instead of dalvik ( big mistake), the third somehow had a bad SD card, the fourth i tried formatting my SDcard NTFS as i was tired dealing with FAT issues and sdcards that just decided to quit on me. Sadly however i seem to have a version of TWRP v.2.6.3.0 which has the coveted 'mount usb storage' button - however i just realized that although kkds 1.4 supports NTFS cards and i have not had any issues (fingers crossed) and have a much more robust filesystem than FAT, however TWRP does not have innate NTFS support. :( I have grown to really love nad appreciate TWRP but does anyone know if i switch back to the oldschool CWM and use the latest version 6.0.4.6 if it offers sdcard NTFS support ?

aside from backing up my SDCard and reformatting with FAT32 are there any other options for recovery. If I didnt have LINK2SD and a secondary EXT4 partition on the same SD card that has NTFS i could just swap out the cards and insert a FAT32 SD and be don with it but then I wont have backups of any of the Apps sittign on my EXT4 second partition....

Is there any hope?
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
You could swap with a FAT32 SD card

temporarily

, to handle the backup and install process. Then, instead of rebooting after flash, power off, and swap the cards back again, power on.

Mind you, if you are not doing a dirty flash this time, all the stuff on the Link2SD partition is moot (since you will have to re-install those apps and move to to that partition) anyway.
[T-Mobile myTouch 4G Slide] steve_77:
True I considered that, but I sometimes like to experiment around and reinstalling all the apps on ext4 is often a pain. Was thinking how hard would it be to convince the TWRP and CMR teams to utilize Emaunuel U's KKDS 1.4 kernel which seems to support NTFS already? Guess I was hoping that there was something i could flash that would allow me to do nandroid backups and recoveries on NTFS sdcard. :(
[T-Mobile myTouch 4G Slide] Emmanuel U:
https://copy.com/Tm3YjawXh86i7CEz try this, the graphics driver may be borked so when so touchscreen won't be accurate (I think it'd offset to the right) you'll see what I mean lol but try installing with that. It has some hacks in it
[T-Mobile myTouch 4G Slide] steve_77:
LOL, Tried it last night, see what you mean about the video driver, but alas still no dice on handling NTFS SD cards :(

I was really hoping for it to work but nope, did these hacks include your WildKernel that comes with your KKDS 1.4 ROM... dont know what it is but that ROM seems to support NTFS perfectly, I doubt cyanogenmod put support in for NTFS in there, perhaps they did, personally I thought all the magic was coming from your kernel . And hence why I was hoping that you might be able to convince the good folks running the TWRP and CMR projects (TWRP in particular) to utilize your kernel for native NTFS support. As i've had nothing but trouble with several older FAT and FAT32 cards, and am not big on the undocumented ExFat and was really hoping you might be able to show how your kernel is superior to the native one included in TWRP 2.6.3.0. But the file you referenced sadly still error-ed out when trying to mount my first NTFS partition (the second being EXT4). I also noticed that the file did also not include the super handy option to 'mount usb storage' under the mount option tab, perhaps not all versions ow TWRP have this very handy feature.

Anyhow - I do very much appreciate you giving it a shot, as you mentioned the display driver was pretty funky, but Im just not looking forward to backing up my NTFS card contents somewhere and reformatting to FAT.... just wish there were other options. Granted FAT is super widespread, so I certainly cant blame it for the demise of 2 SD cards, but thought id try NTFS which works beautifully with your ROM, but I cant seem to use any recovery at the moment to do backups. :(

Thanks again for your help Emmanuel, keep up the good work!
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
Another option [MENTION=2640302]steve_77[/MENTION], if you are looking to avoid FAT file-systems, is to format your first partition Ext2. If you are using linux at home, that would be a natural choice (natural for the android OS as well), but if not, you can always get a Ext2fs driver for your Windows (or Mac) PC, which should be able to read (and write) no problem. I had one for my old Win2K laptop back in the day, they probably only got better since then.

A quick google search brought up an open source solution.
[T-Mobile myTouch 4G Slide] Emmanuel U:
Alright if that didn't work then NTFS is definitely not supported by TWRP. Asking them to add features is almost pointless unless your a large group of people whose phones are bricking because of it. I'd add it myself, but frankly I dont trust myself enough with coding into a recovery to try and port over NTFS support (I dont want to bring our phones lol). If you really want to use an NTFS format then use a computer adb based backup. You can find a few tools online (recommended) or even do it yourself on your computer by adb pull /data data-backup then with SU, adb push data-backup /data