yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S II SGH-T989] jg01:
Eugene, you are the bomb. As always, great work from you. Phone is working great, all the apps work ( if you perform the correct cleaning before installing the rom). The only issue I ran into, which a factory reset took care of, was applying the themes, if mixed and matched the them throught theme app, at times my system would blow up (then did a factory reset to get back to base), but if I did the same thing through the settings> Personal>customer theme, all works well.

The only thing I would ask for is...can you get this CM9?

Thanks again.

---------- Post added at 09:17 PM ---------- Previous post was at 08:59 PM ----------

I had the same issue. Here is how I fixed it.

1. from the recovery wipe cacnhe and dalvak ( this one is in advance)

2. go into the mount and storage, format system, data and cache

3. run DARKSIDE.SUPER.WIPE script ( found on XDA)

4. install ROM

5. do a factory reset to clear out any data left behind while the rom was created

6. install rom again

7. factory reset one ore time

8 . one other step I performed...this is up to you and very much recommended is, format the internal storage. this will clean out a crap left behind from old apps and previous roms. This is important, because a lot of apps will write to either your internal or SD storage, and when re-install in a new rom, they can pick up data from a previous install.

9 boot rom

---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------

I had the same issue. Here is how I fixed it.

1. from the recovery wipe cacnhe and dalvak ( this one is in advance)

2. go into the mount and storage, format system, data and cache

3. run DARKSIDE.SUPER.WIPE script ( found on XDA)

4. install ROM

5. do a factory reset to clear out any data left behind while the rom was created

6. install rom again

7. factory reset one ore time

8 . one other step I performed...this is up to you and very much recommended is, format the internal storage. this will clean out a crap left behind from old apps and previous roms. This is important, because a lot of apps will write to either your internal or SD storage, and when re-install in a new rom, they can pick up data from a previous install.

9 boot rom

---------- Post added at 09:18 PM ---------- Previous post was at 09:18 PM ----------

I had the same issue. Here is how I fixed it.

1. from the recovery wipe cacnhe and dalvak ( this one is in advance)

2. go into the mount and storage, format system, data and cache

3. run DARKSIDE.SUPER.WIPE script ( found on XDA)

4. install ROM

5. do a factory reset to clear out any data left behind while the rom was created

6. install rom again

7. factory reset one ore time

8 . one other step I performed...this is up to you and very much recommended is, format the internal storage. this will clean out a crap left behind from old apps and previous roms. This is important, because a lot of apps will write to either your internal or SD storage, and when re-install in a new rom, they can pick up data from a previous install.

9 boot rom
[T-Mobile Samsung Galaxy S II SGH-T989] anobi98:
How do you take screenshot? Googled and all I could find is vol down + menu btn but doesn't work.
[T-Mobile Samsung Galaxy S II SGH-T989] drekybaby:
Awesome, I have been waiting on this baby for a long time...... even with small issues I am just over-excited bout this!
[T-Mobile Samsung Galaxy S II SGH-T989] mightymike889:
Hold power button n Ull get an option ...that's the only way
[T-Mobile Samsung Galaxy S II SGH-T989] drekybaby:
I love it G...... been patiently waiting for anything like this!

---------- Post added at 04:13 AM ---------- Previous post was at 04:11 AM ----------

same issue , i did the wipe dalvik/cache and rebooted then pow themed! or just try the reboot i think that works also
[T-Mobile Samsung Galaxy S II SGH-T989] aplacetorest:
ok so i have no external SD now? It wont let me import my contacts because it says there is none saved on the sd card which i know is a lie. Someone PLEASE help.

EDIT.

Its under a folder called emmc? What is that? Thats all my internal storage and this doesnt seem to see it. How can i let the phone see the emmc folder so all my internal storage is shown?
[T-Mobile Samsung Galaxy S II SGH-T989] pakakid:
Has anyone gotten group me to work?
[T-Mobile Samsung Galaxy S II SGH-T989] naria01:
Same issues as everyone else
[T-Mobile Samsung Galaxy S II SGH-T989] parusia:
Go to settings/cyanogenmod settings/applications/ then checked use internal storage/reboot and you will be able to see it. After that your internal will be sdcard, and your external will be emmc.
[T-Mobile Samsung Galaxy S II SGH-T989] anobi98:
All that does is bring up the notifications/toggles drop-down menu:confused:
[T-Mobile Samsung Galaxy S II SGH-T989] skadude66:
They're is no APM in Miui for screenshots. They're is an APM, but it's outdated and would have to be adapted to this ROM.

Basically, just download a screenshot app if you want to take any screenshots.
[T-Mobile Samsung Galaxy S II SGH-T989] aplacetorest:
but even if the external is emmc that isnt a regularly scanned folder to detect files correct? Because when it was the other way around it didnt see my music on my internal

why cant the folders just be sd and external sd like normal so the phone can read everything? I dont understand this emmc business
[T-Mobile Samsung Galaxy S II SGH-T989] perknite:
You have to go to the toggle menu options and change it so that it shows one line of toggles. Then when you long-press power the power menu uptions will show.
[T-Mobile Samsung Galaxy S II SGH-T989] parusia:
Well is working perfect on my phone, all my music, and videos are in my external (emmc), and everything shows up in my phone. CyanogenMod and Miui are setup that way. You probably never use a CM or MIUI before, but believe me that is exactly how is supposed to work.:D
[T-Mobile Samsung Galaxy S II SGH-T989] aplacetorest:
Mine doesnt seem to be working correctly
[T-Mobile Samsung Galaxy S II SGH-T989] kokenjr:
I'm having this same problem. Could someone please give some insight into this...

Thanks.
[T-Mobile Samsung Galaxy S II SGH-T989] aplacetorest:
+1 for this
[T-Mobile Samsung Galaxy S II SGH-T989] stevekixs:
I had this problem too. Try wiping your cache or reflashing.
[T-Mobile Samsung Galaxy S II SGH-T989] darkamikaze:
/mnt/emmc was how it was back in the day I believe.

/mnt/sdcard started with samsung as internal

Just go through cmsettings>application>use internal. it's not that big of a deal.
[T-Mobile Samsung Galaxy S II SGH-T989] mainevent3405:
Hey Eugene, seems like youre making progress here with Miui. I want this more than ICS and have been trying to get Mark from Miuidevs to ccreate one for our phone. They have one for the i9100 but not for the T989. I so much want to use this but I need a stable rom. Most of you who are using this, are you using this for your daily and what are the MAIN issues if any?

Thanks in advance! :D
[Epic 4G Android Development] MДЯCЦSДИT:
First. Thanks.

×Marcusant
[Epic 4G Android Development] ÜBER™:
Sick!!!"
[Epic 4G Android Development] Nashdogg:
Wow, this looks great, can't wait to try it out. Thanks TeamWin:cool:
[Epic 4G Android Development] MДЯCЦSДИT:
This will probably work on all mtd roms afaik.

×Marcusant
[Epic 4G Android Development] darkierawr:
Niiiice
[Epic 4G Android Development] Dees_Troy:
Part of the trick with this build of TWRP is the inclusion of a new utility that I've started working on called injecttwrp. It's a work in progress. I'll be building upon this to inject our recovery ramdisk into existing Samsung boot images so that you can choose to keep TWRP installed as you install new ROMs or kernels regardless of what recovery is included with the kernel or ROM that you are installing.

https://github.com/TeamWin/Team-Win-Recovery-Project/blob/master/injecttwrp/injecttwrp.c

Note that this utility is not restricted to just working with TWRP. It could be used to inject any recovery that you wanted.
[Epic 4G Android Development] dnathan13:
Awesome, I use this for my Kindle Fire and love it. It also is the only current recovery that works with the new 3.0 kernel, but I think that is mainly a fire issue. I will try it when I get some time!
[Epic 4G Android Development] FrankyFiggz27:
anyone confirm it works on ics (aokp particularly)?
[Epic 4G Android Development] stevie13.xo:
This looks awesome

Just a thought.. marcusant.. could you build this recovery into nyan for sayyy cm7? :-p
[Epic 4G Android Development] ÜBER™:
Found the install for epicmtd... and as soon as it finished it booted me into recovery and attempted to flash and gave me a status 7... which is usually a signing failure.
[Epic 4G Android Development] thomasskull666:
Of course on the day I'm busiest is when this is released lmao. Thanks for the hard work guys, I'll be playing with this tomorrow for sure!
[Epic 4G Android Development] MДЯCЦSДИT:
The failure was an oddity with the formatting of our flash_image on ics as far as I can tell

×Marcusant
[Epic 4G Android Development] Dees_Troy:
I might just have to yank the zip until I can figure it out, the manual install should work and I have it working in CM9 too.
[Epic 4G Android Development] ÜBER™:
I mean it goes through everything but then stops towards the end... write_flash_image has an error and it shows E: /sdcard/goomanager/twrp.zip ... and aborts.. so what marcus said about the flash image.
[Epic 4G Android Development] pvtjoker42:
hmm.. a nice shiny new touch recovery to play with (since we heard rumors about CWM Touch for the Epic but it never materialized.)

Might have to give this a shot.

Thanks!
[Epic 4G Android Development] sonarchist:
........interface similar to Epic CM Team's test touch recovery; will await sign from Dees_Troy + flash again.

.........sent from today's android = 4.0.4
[Epic 4G Android Development] Dees_Troy:
I believe that the zip install should now be working!
[Epic 4G Android Development] ÜBER™:
Can't get it to download... won't show in my goomanager folder I made the mistake of enabling check signiture toggle and now it won't disable it when it tries to install it fails... and is not in the folder so I can toggle the sig verification and reflash via cwm....

Then I tried to share the link, copy it and then download via the browser its in the download folder now... I tried to flash that it says installation aborted (bad). Wtf?
[Epic 4G Android Development] stevie13.xo:
I couldn't get it to install on cm7 says error installing blah blah (bad).. tried to download it twice.. both times errors
[Epic 4G Android Development] Dees_Troy:
Re: [RECOVERY][Epic 4G]TWRP 2.4.0.0 touch recovery [2013-01-29]

Starting with the SGS3, all newer Samsung phones have shipped with a proper, separate recovery partition so it's infinitely easier to install and keep TWRP. The decryption also applies to the SGS2 but the SGS2 has recovery in boot. AFAIK, no one has successfully encrypted the original Epic 4G and I don't think that the stock ROM supports it either.
[Epic 4G Android Development] Jesse6749:
Troy, Thanks for the explanation which makes it clear why the stock roms over write TWRP. That is why if we want to use TWRP we have to use CM9 or CM10 based roms which unfortunately have issues that prevent me from using them cause I need my phone for work and the phone is issued by my company.
[Epic 4G Android Development] zman519:
Re: [RECOVERY][Epic 4G]TWRP 2.4.0.0 touch recovery [2013-01-29]

Why is the page that the op links to imposable to use from android cm9 browser or boat browser? I don't understand ?!? It for android so why does the page NOT let you downlaod the zips:eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::(

Rocking cm9.1
[Epic 4G Android Development] Dees_Troy:
The TWRP injection isn't possible on stock-based kernels. TWRP still doesn't support Samsung BML or rfs. I could probably add that support fairly easily but I don't think it's worth the effort as I don't think we'd get enough cooperation from ROM and kernel devs. There is technically an unused recovery partition on the Epic 4G and it would be possible to store a recovery ramdisk in that partition. Using that, we could make it so that the boot image could check this partition first and use the ramdisk from that location for recovery instead of using the recovery that's included in the boot image. We're doing something similar on the Sony Xperia devices and so far the response from other developers has been pretty good. However, again, TWRP has arrived so late in the development cycle for the Epic 4G (and SGS1 devices in general) that I'm afraid that we won't get enough cooperation to make it worthwhile. As a benefit to kernel devs, we could theoretically remove almost all of the recovery stuff from the boot image, freeing up at least a full 1MB for larger kernels.
[Epic 4G Android Development] Jesse6749:
Thanks Troy, I am glad I can use your recovery on most of my Android devices, cause it is my favorite recovery program. It"s a matter of fact I just installed CM10 so I could install your recovery on my Epic4G. Sadly I hear my employer might be getting our phones upgraded to Iphone 5 which I do not like but it is for work and free.
[Epic 4G Android Development] brickwall99:
Could anyone provide a link to a recovery flashable update to TWRP 2.4.0.0 or 2.4.1.0? The GooManager App says there are no new updates to install.

Thanks
[Epic 4G Android Development] AndyYan:
Re: [RECOVERY][Epic 4G]TWRP 2.4.0.0 touch recovery [2013-01-29]

There you go.

http://techerrata.com/file/twrp2/epicmtd/openrecovery-twrp-2.4.0.0-epicmtd.zip

Sent from HTC Incredible S @ CM10.1
[Epic 4G Android Development] brickwall99:
That worked. Thank you very much!
[Epic 4G Android Development] Dees_Troy:
I finally updated my build script so I can generate updates for the Epic 4G automagically along with all the other devices. Updated to 2.5.0.0 too!
[Epic 4G Android Development] Dropple:
Yay...

Thanks for this :thumbup:

Sent from my JellyBeer v.4.14 epicmtd (b3)
[Epic 4G Android Development] Unjustified Dev:
off topic

Thanks about to build this for the fascinate.
[Epic 4G Android Development] nikon120:
[MENTION=912474]Dees_Troy[/MENTION]:

I've noticed that the theme has graphical issues upon accessing recovery. The only way to clear up the misaligned pixels around borders and buttons is to reload the theme manually.

I've also noticed that when the screen goes dim, that it never returns to full brightness. When performing backups this is prevalent since it takes time to perform the work. If I just leave the phone alone, the screen dims like normal. However, if I go to check progress, the screen doesn't un-dim and I'm left to either remember button placement or just completely reboot recovery and keep phone from going dim.

No issues like this on my Nexus 7 running 2.5.0.0, so appears to be an issue for just the Epic right now.

I've had to go back to CWM in the mean time.
[Epic 4G Android Development] AndyYan:
Same issues kept me from using 2.5.0.0, but 2.4.0.0 seems okay. And you could still use TWRP's backups with it instead of switching to CWM's format.

Sent from HTC Incredible S @ CM10.1
[Epic 4G Android Development] jeffreyjicha:
If you boot into TWRP, check out the settings, because I had the dimming problem as well, but I changed it so the screen doesn't dim.
[Epic 4G Android Development] nikon120:
That a decent workaround, but I wanted to report the bugs.
[Epic 4G Android Development] jeffreyjicha:
I hate to revive less active threads, but I was wondering if TWRP 2.6.3.0 is only for Android 4.3
[Epic 4G Android Development] AndyYan:
Is this April Fool's Day?!?! The TWRP 2.6.1.0 and 2.6.3.0 zips on both TechErrata and Goo.im contains no recovery image at all! They have a size of ~170KB versus 2.6.0.0's 2+MB... Could somebody clear this up, or is this really, really a joke (please don't! :D )?
[Epic 4G Android Development] Sterist:
good eye. i havent gotten into digging yet but i flashed it and.. well, you know lol.. wont boot

time to dig up odin again
[Epic 4G Android Development] Unjustified Dev:
Nope your right it has no ramdisk recovery.IMG in it . looks like they forgot it
[Epic 4G Android Development] Darkangels6sic6:
Great.... now i soft bricked my sisters phone

---------- Post added at 04:57 PM ---------- Previous post was at 04:53 PM ----------

Why do they still have a bad link up???? Are they purposely trying mess up phones?

Thats like the poor ally and no warning that the flash tool bricked many phones.
[Epic 4G Android Development] DynamicN:
You take 100% responsibility when you flash anything on a phone, regardless of whether it is working or not. YOU chose to flash it, period.
[Epic 4G Android Development] Darkangels6sic6:
And how did I know someone would be so quick to jump in with that ridiculous out of place mumbo jumbo. I asked legit question on a serious matter. I have every right to be upset and ask a logical question. I didnt rant or flame. I never said none of it was my fault. I didnt lie or go off topic. Dont be so quick to goody goody jump everyones comments so illogically.
[Epic 4G Android Development] DynamicN:
All I'm saying is this sentence right here that you said "Why do they still have a bad link up???? Are they purposely trying mess up phones?" makes it sound like the devs are purposely trying to mess up phones. Do you really think that's their intention? People have busy lives and for most of us this is just a hobby so they probably forgot to take down the old links.
[Epic 4G Android Development] Darkangels6sic6:
Ignored. Anyway. Obvious warning do not flash the last two or three builds. I'm imagining someone else messaged the dev, but I did just in case.

Of course re flashing a recovery through Odin alone does not fix it. Still fairly easy with proper odin tools. Just had to start from stock.
[Epic 4G Android Development] Unjustified Dev:
Dees troy maintains a lot of phones and face it. The epic is out of the book for him because it doesn't have a dedicated recovery partition. I guess it's easier to maintain other devices. I can try to get a twrp some time soon. BTW I have an epic touch
[Epic 4G Android Development] Darkangels6sic6:
It does work. I got twrp going. Just do not use the last couple. As far as jb and kk however I do not know.
[Epic 4G Android Development] Unjustified Dev:
Just got twrp 6.3 on epic touch bringing it to the epic 4g tomorrow hopefully.
[Epic 4G Android Development] BigOnes69:
I have been using TWRP for over Year just upgraded to 6.3 works fantastic. CyanMod 10.1. Nightest kernel.
[Epic 4G Android Development] kstephens98:
From where did you get 6.3?
[Epic 4G Android Development] BigOnes69:
2.6.3 Most people know that it was abbreviated. That is most people.
[Epic 4G Android Development] Luthiensdad:
Hello, where are you finding 2.6.3? Latest working version I could find was 2.6.0.0....
[Epic 4G Android Development] kstephens98:
Yes, this. Where can we find 2.6.3?
[Epic 4G Android Development] AndyYan:
People could be talkin about Epic 4G Touch again...

Sent from Samsung Galaxy Nexus @ CM11
[Epic 4G Android Development] BigOnes69:
Default [RECOVERY][Epic 4G]TWRP 2.6.3.0 touch recovery [2013-09-16]

CHANGELOG for 2.6.3.0:

-Proper backup and restore of SELinux contexts (thanks to Tassadar)

-Pull in some ROM information for backup name generation

-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3

-Add 1200x1920 theme (thanks to Tassadar)

-A few other fixes and tweaks

Its their post and their software if they want to call it divinewillthoughtprocess or miserylovescompany2.10.111.999.6663 that is their business.
[Epic 4G Android Development] didhiy:
Look at the size in the download link ;) it doesn't contain recovery img at all..
[Epic 4G Android Development] Sterist:
if its ok to ask, will there ever be another TWRP update for this old dinosaur? :confused:
[Epic 4G Android Development] blaze2051:
2021 almost 2022 and still no sign of this mysteries TWRP 2.6.3.0 must have been a fairy tale
[Epic 4G Android Development] KennyG123:
Not the one Marcus tried to brick my phone with

Why you little......! (Homer impression)

LOL
[Epic 4G Android Development] || Acer ||:
This is awesome! Can't wait for a finalized version!
[Epic 4G Android Development] sonarchist:
@Dees_Troy:

Does installing TWRP recovery permanently replace CWM5.5.0.4?...................TWRP appears to be working fine using marcusants' Nyan4.2 test kernel; just wondering about the likelihood of returning back to CWM once TWRP is installed.

*IE, to restore a CWM nandroid........or to advanced restore Data Only from a CWM nandroid.

.........sent from today's android = 4.0.4
[Epic 4G Android Development] DRockstar:
flash_image is a binary normally included as an extra for CWM to flash kernels and recovery kernels, and is known to work under a variety of file systems automatically (yaffs2, ext4, and even rfs)... you may need to include this by default... afaik, koush wrote this, but I believe it is open source... Hope this helps.
[Epic 4G Android Development] KennyG123:
My guess is you would need to reflash CM9 or A CM9 kernel with normal recovery in it like shadowkernel.
[Epic 4G Android Development] || Acer ||:
Hmm, maybe the CM Team could just post a completely stock CM9 kernel so people always have a way back, rather than reflashing?
[Epic 4G Android Development] MДЯCЦSДИT:
I'll post a CWM5 restore script.

×Marcusant
[Epic 4G Android Development] DRockstar:
The recovery for CM 7/9 has to be included in the boot kernel, I had fought for the recovery to be put in its own partition to make things easier, but it's more complicated than that, I recall it being that once you change the boot mode to recovery boot while on mtd, it can't be changed back to normal boot again... it would take a massive effort to try to resolve this, perhaps to the point of trying to interpret the leaked bml sources, or reverse engineering it... mkasick had to break it all down for me with a red crayon at one point.

I wanted to point this out so that you would have some insight as to why this can be more complex than you'd might expect.
[Epic 4G Android Development] MДЯCЦSДИT:
Teamwin manages this by injecting the recovery into the boot partition. During the time of the mtd port, I remember the whole issue over recovery also.

×Marcusant
[Epic 4G Android Development] DRockstar:
Possible solution: have TWRP recovery as a fakeflash zip, that can be loaded with any recovery... this is the method I used to test cwm builds, and is even used by the official bml epic rom manager... perhaps the twrp app can be tweaked for this, and you can load the twrp zip from the regular cwm during a 3 finger boot... unless DeesTroy can in fact find a way to rewrap the recovery portion of the boot kernel, which would be nice.
[Epic 4G Android Development] Dees_Troy:
I'm still learning about Samsung but it's very unlikely that I will be able to change the MTD setup. I have come up with a way to pull apart at least some MTD boot images using the code here:

https://github.com/TeamWin/Team-Win-Recovery-Project/blob/master/injecttwrp/injecttwrp.c

With this I can inject a new recovery ramdisk into many boot images for SGS1 devices. TWRP has this feature integrated and automated, so it can automatically re-inject the TWRP ramdisk after you install a new ROM or kernel. This way, if your favorite developer doesn't make a build with TWRP, you can still keep using TWRP.

A fakeflash zip might be ok, but I prefer the more permanent solution of win injection. We try to provide the best user experience that we can. Once you start using TWRP on a regular basis and see how fast and easy-to-use it is, I hope that you'll agree that having to manually run a fakeflash zip everytime you wanted to use TWRP would be a huge step backwards. Sure the initial leap to TWRP if you have a lot of backups with CWM might be a bit tough, but within a few weeks you'll probably have everything that you need moved over to TWRP anyway.
[Epic 4G Android Development] matrixzone5:
Jjust what i wanted :) okay capacitive buttons its time to get unplugged ... helllllooooo on screen buttons* :D