Develop Bugs

[Recovery] Flashable Ones!!! - CWM - TWRP - Stock

Here are the latest CWM and TWRP ( http://forum.xda-developers.com/showthread.php?t=1809307) recoveries are all flashable from recovery itself, use these to swap back and forth or just because you are bored...
These were/have been previously posted over in sprint apps section, but I keep seeing people posting questions about need this one or that...so here they are for T-Mo.
Thanks goes to the original developers for these, and for the sharing and caring..
TWRP 2.4.2.0 - http://d-h.st/iMc
TWRP 2.4.1.0 - http://d-h.st/9cL
CWM 6.0.2.3 - http://d-h.st/jbT
CWM Touch 6.0.2.3 - http://d-h.st/8A9
Stock ... http://d-h.st/TzP

I made my own months ago, I have tars in my sig and zips in my DropBox (which I've linked several times). You seem to have taken offense at my questions, when I clearly pointed out I didn't want you to interpret them that way. My questioning was merely a vain attempt to learn something new. Not to tear you down, but for me to become more knowledgeable about a subject from someone who clearly knows more about Android than I do.

So, is it safe to flash these?

I could of used you yesterday. I was literally scouring yesterday looking for a flashable recovery. Ended up using adb and Odin to flash something.. Thx for this post.
Sent from my Nexus 7 using xda app-developers app

fasteddie5 said:
So, is it safe to flash these?
Click to expand...
Click to collapse
the CWM are for your phone. TWRP are for all GS III's...I would not have posted these here if they did not work. :victory:
OP updated with specific T-Mo builds so that md5 checks will alleviate anxieties...

Aerowinder said:
I tested both CWM Touch and TWRP myself this morning (latest versions for both). d2spr recoveries (the ones originally posted) absolutely fail the d2tmo assert check (for any zip that includes it).
As of 2012-02-17, 10:50AM EST:
The CWM Touch link is good (it was edited since my last post). Did not test CWM non-touch. Not sure why anyone would use it.
The TWRP 2.4.1.0 link is bad. This is still the d2spr version. Safe to assume the older versions are as well.
Stock recovery link is also bad.
Do not flash recoveries that are not for the T999.
Click to expand...
Click to collapse
The links to the recoveries are fine! The OP is updated with T-Mo provider specific stuff so that MD5/build properties match.
They work just fine. I do have links to sprint ones too. if anyone needs them...

Qverse said:
I agree Aerowinder is very correct ! It still contain the d2spr assert code. cwmtouch-naddict still contains d2spr assert code and will not install on a d2tmo device through recovery. It aborts..
Click to expand...
Click to collapse
good catch, wrong source for TWRP..Corrected and in OP
however, CWM Touch is correct as per what aero said in his post
check OP now. Correct TWRP is up! :cyclops:
source for stock recovery is here http://stockroms.net/file/GalaxyS3/SGH-T999/stockrecovery/T-Mobile-SGH-T999-Stock-Recovery.tar Posted from August 2012. source is attached, do what you want with it. :silly:
Choose to use or not, that is your choice.
I posted them here to help others, and hope someone appreciates them .... Good day

I'm not sure how often stock recovery is updated, but that one is probably from UVALEM.
All checksums match, but assert codes still haven't been removed/fixed. So none of these will flash.

Aerowinder said:
I'm not sure how often stock recovery is updated, but that one is probably from UVALEM.
All checksums match, but assert codes still haven't been removed/fixed. So none of these will flash.
Click to expand...
Click to collapse
try them now..
All should flash, thanks again

Naddict said:
try them now..
All should flash, thanks again
Click to expand...
Click to collapse
Looks good.

Do we just flash, or wipe cache/dalvik first?

fasteddie5 said:
Do we just flash, or wipe cache/dalvik first?
Click to expand...
Click to collapse
Just flash. No need for wipes, since this is replacing your recovery, and not touching your ROM.
Sent from the phalanges of my hand to the facet of your cranium.

Tried flashing CM touch, got install aborted.

fasteddie5 said:
Tried flashing CM touch, got install aborted.
Click to expand...
Click to collapse
redownload the package

Naddict said:
redownload the package
Click to expand...
Click to collapse
OK, I'll try again today. Thanks!

OK, downloaded again, and it failed again. Said, assert failed and some other stuff. I can post everything it says after it fails, if you like.

What device do you have?
If d2tmo, your build.prop has been altered.

Aerowinder said:
What device do you have?
If d2tmo, your build.prop has been altered.
Click to expand...
Click to collapse
TMobile Galaxy S3, running Infamous 4.4
Should I restore to stock rooted, and try that way?

It could be the metadata file within the zip. It's still tagged as d2spr. That file isn't needed, and probably isn't even being read. What is the error saying? I just figured it was a status 7.

Yes, I believe it was status 7.

[Q] Wind SGH-T999V CM Help

Okay, I'm new to Android and I heard this is the go-to spot for help. Anyway, this is what happened to my Wind SGH-T999V. Mind you i'm VERY new to this rooting thing
I rooted my S3 by using TWRP 2.6.3.0 and i used odin3 v1.85 and it worked. I downloaded a root checker and it said i'm rooted. Then i put CM 10.1.2 on my sd card and wanted to install it via TWRP recovery but it gave me an error that said "No MD5 filed found" or something along those line.
I then tried to use different versions of twrp ( twrp 2.6.1.0) and a different CM (10.1.1) but i still got the same "no Md5 found" error. So, a friend then told me to ditch twrp all-together and download CWM instead. So, I download recovery clockwork touch 6.0.3.7 and put it on my phone.
THEN, i tried to go back to the recovery boot place, but after that small blue font saying "recovery boot", my phone goes black. I dont see the old twrp recovery or the clockwork one.
I just really want to have Cyanogenmod on my phone, i've been having a hard time. Help please?

Just disable the md5 check, most or the ROM files are not going to include a hash file, but will flash fine. TWRP or CWM will error out if the flash fails.
Also, it sounds like your recovery install failed, just reinstall using ODIN and a file from @DocHoliday77 (I recommend TWRP over CWM, but it is just preference)

It's already unchecked.

Install TWRP and try again, should work without issue. Also, redownload the ROM file, preferably the latest version, 10.1.3RC2 (I think)
Sent from my T-Mobile T999L using TapaTalk 4 and delivered by Planet Express.

Can you link me the most STABLE CM that works with my Wind SGh-T999V?

qasde455 said:
Can you link me the most STABLE CM that works with my Wind SGh-T999V?
Click to expand...
Click to collapse
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.

http://get.cm/?device=d2tmo&type=stable
"Stable" is relative, the RCs are just as good.

Aerowinder said:
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.
Click to expand...
Click to collapse
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install

qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
You need to edit the install script because your device isn't supported. Or you can download Doc's version.

Actually I'm pretty sure cm includes the T999V, but I'm betting the firmware needs to be updated.
Look in Aerowinders Sig for the links to the firmware. In that OP you should find a link to the thread with the T999V firmware.
Or, you can go to my T999L thread and get the Rom there. But w/o updated firmware it may be buggy.
Sent from my SCH-I535 using Tapatalk 4

It's already unchecked.

qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
CM10.1.3 is now Stable and will be the last 4.2.2 build. It should has the all of the Asserts, including the MB7 one. Also, update your TWRP, the current is 2.6.3.0.

I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..

malibu.barbie said:
I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..
Click to expand...
Click to collapse
You should read the sticky threads, and use xdas search for terms or definitions anytime you run into stuff you aren't familiar with.
Sent from my SGH-T999V using Tapatalk 4

[Q] Can't install new ROMs

So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.

You need to give more info on the error
Sent from my SGH-M919 using Tapatalk

serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.

Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app

spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.

Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?

Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.

Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.

Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?

So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.

Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.

To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.

Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.

Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3

I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?

Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something

Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement

GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)

My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.

You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.

[Q] Slimbean 4.4 stable install

I'm running Slimbean 4.3 stable. Downloaded 4.4.2 stable and keep getting an error message and then installation aborts. Using CWM
I've tried using both methods
first wiping cache, dalvik, then installing zip
second wiping data/factory reset, mounts storage formatting system
Keep getting error message of metadata something and then install aborts. Never had an issue with upgrading Slimbean ROMs. Any suggestions?

Error message
set_metadata_recursive: some changes failed

You need the latest version of CWM in order to install KK ROMs.
I prefer Philz Touch from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att. You can install the latest zip from your current version of CWM.

audit13 said:
You need the latest version of CWM in order to install KK ROMs.
I prefer Philz Touch from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att. You can install the latest zip from your current version of CWM.
Click to expand...
Click to collapse
Thanks. Yes that did the trick. Pretty cool ROM so far but how do I get the phone to ring when I've got BT connected also???

Hat Trick said:
Thanks. Yes that did the trick. Pretty cool ROM so far but how do I get the phone to ring when I've got BT connected also???
Click to expand...
Click to collapse
I'm not sure as I have never used that ROM. Everytime I have used a custom ROM, the phone still emits my selected ringtone when connected to my bluetooth speaker.

Won't Load Any ROM

Running TWRP, I have tried three different ROMs with no luck. It would fail to install SlimKat and CM. MIMU v5 would install but never make it past the mi.com splash screen. I wiped cache/dalvik/system/internal storage each time and tried both sideload and SD card installs same results every time. Is there something I missed along the way?

Make sure you're on the latest recoveries, twrp 2710, philz 6.48.4 on 6050, and cwm 6045.
Outdated recoveries will fail to flash Roms and if you're on an ICS Bootloader you'll get assert failures.
Have you tried PC ODIN back to stock TW and re-do the process from there?

Spark91 said:
Make sure you're on the latest recoveries, twrp 2710, philz 6.48.4 on 6050, and cwm 6045.
Outdated recoveries will fail to flash Roms and if you're on an ICS Bootloader you'll get assert failures.
Have you tried PC ODIN back to stock TW and re-do the process from there?
Click to expand...
Click to collapse
i second this persons knowledge have fun starting from scratch and use Philz works best with ND8 bootloader for most users

Spark91 said:
Make sure you're on the latest recoveries, twrp 2710, philz 6.48.4 on 6050, and cwm 6045.
Outdated recoveries will fail to flash Roms and if you're on an ICS Bootloader you'll get assert failures.
Have you tried PC ODIN back to stock TW and re-do the process from there?
Click to expand...
Click to collapse
I swapped TWRP for Philz and still get the same assert failure with CM. MIMU loads the same and gets stuck but now it vibrates every 10 seconds or so while sitting. Idk if I'm installing it right though. The older version says install GAPPS but the newer one does not. Maybe they forgot to mention it? I might try a stock ROM tomorrow just to see

tnactim said:
I swapped TWRP for Philz and still get the same assert failure with CM. MIMU loads the same and gets stuck but now it vibrates every 10 seconds or so while sitting. Idk if I'm installing it right though. The older version says install GAPPS but the newer one does not. Maybe they forgot to mention it? I might try a stock ROM tomorrow just to see
Click to expand...
Click to collapse
okay for every AOSP rom you need to flash the gapps package that matches the Android number and just go back to stock and start over

tnactim said:
I swapped TWRP for Philz and still get the same assert failure with CM. MIMU loads the same and gets stuck but now it vibrates every 10 seconds or so while sitting. Idk if I'm installing it right though. The older version says install GAPPS but the newer one does not. Maybe they forgot to mention it? I might try a stock ROM tomorrow just to see
Click to expand...
Click to collapse
Is your phone the Sprint version? Usually an assert failure is caused from trying to flash a rom that is not unified, like a Sprint rom being flashed to Boost. If a rom is not unified, and your trying to flash a Sprint rom on Boost/VM, you must remove asserts from the rom zip, then rezip, then flash. But definitely Philz advanced CM is the best. TWRP used to cause many assert failures for me.
sent from my G3

joeyhdownsouth said:
Is your phone the Sprint version? Usually an assert failure is caused from trying to flash a rom that is not unified, like a Sprint rom being flashed to Boost. If a rom is not unified, and your trying to flash a Sprint rom on Boost/VM, you must remove asserts from the rom zip, then rezip, then flash. But definitely Philz advanced CM is the best. TWRP used to cause many assert failures for me.
sent from my G3
Click to expand...
Click to collapse
Its a Sprint phone and the Sprint labeled CM. I tried Spirit ROM and the GAPPS listed on their download page and its working fine. Idk why it didn't like the others but at least its up and running again

tnactim said:
Its a Sprint phone and the Sprint labeled CM. I tried Spirit ROM and the GAPPS listed on their download page and its working fine. Idk why it didn't like the others but at least its up and running again
Click to expand...
Click to collapse
using the PA Gapps they provided correct?

tnactim said:
Its a Sprint phone and the Sprint labeled CM. I tried Spirit ROM and the GAPPS listed on their download page and its working fine. Idk why it didn't like the others but at least its up and running again
Click to expand...
Click to collapse
Original CM or Philz Advanced?
sent from my G3

6th_Hokage said:
using the PA Gapps they provided correct?
Click to expand...
Click to collapse
Yes. And Philz recovery

tnactim said:
Yes. And Philz recovery
Click to expand...
Click to collapse
okay those are the Gapps i use when i try any AOSP rom

I'll keep them on my SD card then for whatever I may try next