Related
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.
I use ClockWorkMod on an HTC EVO 4G ( Rolls Eyes ),
I have been trying to install a more customized rom on my Evo and I cannot seem to do it.
-I'm Not New To Android Or Linux-
But I sometimes get a Status 7 Error or a " BAD " Error and cannot install any rom.
ANY IDEAS?!
jonahly said:
I use ClockWorkMod on an HTC EVO 4G ( Rolls Eyes ),
I have been trying to install a more customized rom on my Evo and I cannot seem to do it.
-I'm Not New To Android Or Linux-
But I sometimes get a Status 7 Error or a " BAD " Error and cannot install any rom.
ANY IDEAS?!
Click to expand...
Click to collapse
What rom are you installing? A status 7 error only occurs when there are problems with the updater-script, and i dont think any dev would release a rom with a faulty updater script
Check the md5sum of your downloaded file, and download over a hardline and transfer to your phone if needed because it may just be a bad download that corrupted your the updater-script
Also try flashing other roms, and what version of CWM are you using? Try smelkus-mod recovery
CNexus said:
What rom are you installing? A status 7 error only occurs when there are problems with the updater-script, and i dont think any dev would release a rom with a faulty updater script
Check the md5sum of your downloaded file, and download over a hardline and transfer to your phone if needed because it may just be a bad download that corrupted your the updater-script
Also try flashing other roms, and what version of CWM are you using? Try smelkus-mod recovery
Click to expand...
Click to collapse
Rom: I've been trying a few, they never really work at all.
I have tried flashing others.
5.0.2.2 ( Unless I forgot )
jonahly said:
Rom: I've been trying a few, they never really work at all.
I have tried flashing others.
5.0.2.2 ( Unless I forgot )
Click to expand...
Click to collapse
Switch over to smelkus-mod and see if that fixes it
Did you check the md5sums and they line up?
The problem is in your opening sentence; Clockwork Mod. Read my guide in my signature. It'll tell you all you need to know
From the Hip-Phone
The Status 7 Error is not a script error either. It is an error installing the boot.img. This has become an ever more popular error on the evo. If you check you recovery log it will show everything installed fine until it got to the boot.img install and then it errors out. So please lets stop calling it something it is not.
jlmancuso said:
The Status 7 Error is not a script error either. It is an error installing the boot.img. This has become an ever more popular error on the evo. If you check you recovery log it will show everything installed fine until it got to the boot.img install and then it errors out. So please lets stop calling it something it is not.
Click to expand...
Click to collapse
It means that something went wrong with the updater-script, not necessarily that something is an error in the script itself, no ones calling it something that its not
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
madtorq said:
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
Click to expand...
Click to collapse
Are you on a Canadian carrier?
Sent from my SGH-I747 using xda app-developers app
Nope, southern california ATT.
I edited using vim and did it cleanly, no chance of a carriage return or something stupid contributing to this.
Are you on the proper bootloader?
mrhaley30705 said:
Are you on the proper bootloader?
Click to expand...
Click to collapse
I have tried running the zip manually from recovery mode in CWM, tried installing it from Rom Manager where it reboots and automatically selects it and I have tried directly from the CM10 update button within the About Phone settings menu.
Is that what you are referring to?
No. Have you installed the jelly bean bootloader? If not, you will need to update them before cm, or any aosp based Rom, will install.
Also, you need the latest modem too.
mrhaley30705 said:
No. Have you installed the jelly bean bootloader? If not, you will need to update them before cm, or any aosp based Rom, will install.
Also, you need the latest modem too.
Click to expand...
Click to collapse
I do not follow, what is the jelly bean bootloader? I understood it to be an alternative to CWM? Why have I been able to flash every update for CM10 until this?
Link to this jelly bean bootloader update?
Bootloaders are not a type of recovery. Perhaps you should read through this:
http://forum.xda-developers.com/showthread.php?t=1903437
Then this:
http://forum.xda-developers.com/showthread.php?t=2292957
madtorq said:
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
Click to expand...
Click to collapse
I have the same problem. Guess I'll never get 10.1, because it looks like you have to put a new bootloader on it, not sure why, and it risks a hard brick. It doesn't make any sense to require a new bootloader, seeing as I already have cyanogenmod 10, but the devs chose that for their reasons. I really want the camera in 4.2.
Well, if you've flashed any of the stock ROMS here, rooted or not rooted, you've flashed bootloaders.
well I guess I am confused. I am currently running cm-10.1-20130411-EXPERIMENTAL-d2att-M3.zip with the same bootloader I flashed with Odin back when I got the phone in september 2012. My roomate got the same phone except on sprint and we flashed his with the appropriate CM10.1 experimental release for the sprint phone. Since then we both have been updating via the built in CM updater and he has been able to go to the new stable CM 10.1.0 release today and has not flashed any new boot loader or anything, just updated CWM like I did.
So my question to you mrhaley30705, which no amount of searching or reading links has helped me thus far, is this something specific to the ATT version of the Galaxy S3? I do not understand what changed and why he can do it and I cannot.
More importantly, will flashing the newer boot loader you suggested require a wipe of everything? The only post actually referencing this for my phone is http://forum.xda-developers.com/showpost.php?p=41503727 and it is vague to say the least.
Your answers are much appreciated.
Here is the screen shot of what was posted on g+ by cm. I would say he is on the new bootloader. If you check the second link I posted above, there's a way to tell which bootloader you and your buddy have.
It doesn't wipe anything. You'll probably never notice the difference, with the exception of being able to run aosp based ROMS
thank you, that is informative, but still leaves me confused since I am running 4.2.2 (although the build is before that May release) and I am currently running I747UCLH9.
Checking my roomate's phone he is running XXXXXXLJ7 so either he started with a newer one or something. I guess that clears it up. Also, this thread was very helpful incase anybody searches and stumbles on my posts: http://forum.cyanogenmod.com/topic/73407-how-to-update-bootloader-and-do-i-need-to-do-this/
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
Hello, I have a T-Mobile T999L (baseband UVUBNF4) and I'm not able to install the AOKP nightly. I flash the ROM via Clockwork Recovery after a data, cache, and dalvik cache wipe, and still nothing. I have tried other ROMS (PAC-ROM and Carbon stable releases) using the same method (as well as wipes) and they install perfectly. For AOKP, I get stuck on the boot animation. I have tried several times and searched a lot of threads, but I didn't find a solution.
I'm not sure if bump posts are allowed, but I haven't received a response yet. Can anyone please help?
android_noob12 said:
I'm not sure if bump posts are allowed, but I haven't received a response yet. Can anyone please help?
Click to expand...
Click to collapse
is your recovery the latest ? have you tried twrp or philz recoveries ?
just a thought.
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
is your recovery the latest ? have you tried twrp or philz recoveries ?
just a thought.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Yes I have the latest CWM. I haven't tried the other recoveries. Would that make a difference?
worth a try in my opinion. tried redownloading the ROM? could be a bad download. check the md5 sum's to make sure they match? full wipe? IDK after that.
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
worth a try in my opinion. tried redownloading the ROM? could be a bad download. check the md5 sum's to make sure they match? full wipe? IDK after that.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
I'm still really new to flashing, so I lack some basic knowledge. How do I compare md5 sum? Also, I just recently installed slimkat on my phone and it's working perfectly. In total, I made 3 successful attempts at installing ROMs on my phone, with the AOKP ROM as the only failure, so there seems to be an issue with the latest nightly build.
android_noob12 said:
I'm still really new to flashing, so I lack some basic knowledge. How do I compare md5 sum? Also, I just recently installed slimkat on my phone and it's working perfectly. In total, I made 3 successful attempts at installing ROMs on my phone, with the AOKP ROM as the only failure, so there seems to be an issue with the latest nightly build.
Click to expand...
Click to collapse
when you go to download the AOKP , there will be a md5 # , this should match what you actually download. also , CWM should (i dont use it , so i'm guessing) have an option to always check md5 before flashing. if it does , it would be a good idea to enable it IMHO. if there is an issue with latest nightly , maybe try the one before latest or wait for next one. also , reading that thread ,AOKP, might shed some light.
"all i can really do , is stay out of my own way and let the will of heaven be done"