Develop Bugs

[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

AOSP roms will NOT run! Driving me crazy...

So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?

I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app

iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.

Do you by chance have a refurbished s2?

The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?

es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app

es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.

Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!

es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?

UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.

es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?

tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...

I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.

DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?

TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/

Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk

yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways

wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.

DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.

Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte

[Q] Cm 10 to Cm11?

Me and my son rooted our S3's a while ago. We have Cm 10 nightly "Oct 28/12" and want to update to Cm 11 nightly but I think we have to do something different as to a normal rom update? I think I read we have to update the kernal or something first but didn't understand it. We have the newest Clockworkmod 6.0.4.3. If someone could point us in the right direction it would be greatly appreciated. Thanks

Frostman5555 said:
Me and my son rooted our S3's a while ago. We have Cm 10 nightly "Oct 28/12" and want to update to Cm 11 nightly but I think we have to do something different as to a normal rom update? I think I read we have to update the kernal or something first but didn't understand it. We have the newest Clockworkmod 6.0.4.3. If someone could point us in the right direction it would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Alright first of all, which was the last official AT&T software update you did? If your at least updated to 4.1.2, you'll be good. As for the update, since it is a different update, a clean flash is necessary. First, you have two options, can get the latest CM 11 nightlife from
http://download.cyanogenmod.org/?device=d2att
OR, there's an excellent ROM by a developer named PwnCakes193, called Quantum which is based on CM 11, but based on community feedback and comparing it to the official CM 11 bug thread, Quantum is a lot more stable. It doesn't get updated daily but at least every 2-4 days (no promises). If you decide to check it out, make sure to read the thread twice and read a few of the latest comments here:
http://forum.xda-developers.com/showthread.php?t=2390147
For both these, you'll need the latest GApps. I recommend Paranoid Android GApps from here:
http://forum.xda-developers.com/showthread.php?t=2397942
Don't let the name trick you, you can use these GApps for any 4.4.x ROM (I recommend the Modular package).
Once you have a ROM and GApps downloaded and on your phone, the flashing process will be like this for CWM:
Wipe data/factory reset>wipe cache
>format /system>format /cache> wipe dalvik cache. Flash ROM, flash GApps, wipe cache, wipe dalvik cache. After this, you should be good as gold, so just setup and download your apps and that's it!
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Thanks a lot for your help. I have 4.1.2 on my phone .Do I not have to update the kernel ? As I think awhile ago I tried updating to 4.2 and it wouldn't go and someone said I needed to update the kernel,,but that was awhile ago maybe things have changed.I 'll try your method and let you know how it goes. thanks

ok I wiped everything they said to then tried to install Quantum 4.3 and says installation aborted "status 7" I remember this from last time and I never went any further because someone said I had to update the kernel?

its not the Kernel, I guess my bootloader isn't in the assert command of the roms approved bootloaders, so it won't load it. so I guess I have to update my bootloader,,,hmmm

Frostman5555 said:
its not the Kernel, I guess my bootloader isn't in the assert command of the roms approved bootloaders, so it won't load it. so I guess I have to update my bootloader,,,hmmm
I have I747MVLLH1,,its not in the list on the rom,,I remember this from last time and i stopped,,More reading
Click to expand...
Click to collapse

Frostman5555 said:
its not the Kernel, I guess my bootloader isn't in the assert command of the roms approved bootloaders, so it won't load it. so I guess I have to update my bootloader,,,hmmm
Click to expand...
Click to collapse
Are you trying to install 4.3 or Quantum v3?, Because Quantum v3 is 4.4.2 KitKat. Do you have a Canadian Galaxy S3? There might be something related to this in the ROM thread. Double check to make sure your recovery is the latest. If I had to guess, its probably be the boot loader, just be careful and read twice before you do anything.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

It was the bootloader. Updated it with Clockworkmod to the newest Canadian one"DLK4" then the Quantum v3 went on smooth . thanks for the help

Frostman5555 said:
It was the bootloader. Updated it with Clockworkmod to the newest Canadian one"DLK4" then the Quantum v3 went on smooth . thanks for the help
Click to expand...
Click to collapse
Sure thing, glad I could help. If you feel brave, PwnCakes just posted v3.15 about 5 minutes ago, which is the latest 4.4.2. If you decide to, you'll need a clean flash and latest GApps.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Drx,does the 3.12 have the google now working?I can't seem to get it to work.Also what would be the procedure to put 3.15 on now that I have 3.12 on,,thanks

Frostman5555 said:
Drx,does the 3.12 have the google now working?I can't seem to get it to work.Also what would be the procedure to put 3.15 on now that I have 3.12 on,,thanks
Click to expand...
Click to collapse
Yup, all versions have Google Now working. Have you made sure that there's no updates pending for it in the Play Store? Make sure that after every update, even a dirty flash, that you install GApps. If you forget to, the search bar will bring up a Gingerbread looking search app, and a lot of the Google apps and services will not work. For a "dirty" flash (no apps or data is lost), my process goes like this: wipe cache>wipe dalvik cache> format /system (no data will be lost)> Install ROM> Install GApps> wipe cache and dalvik. You should only use this if you are on the ROM already, not if it is a completly new ROM. Hope this helps!

[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] StockMOD Custom ROM 4.3 RLS2.1 Question

am I able to flash this StockMOD Custom ROM 4.3 RLS2.1 for att or tmobile, over my existing stock 4.4.2, my modem as of now is i747UCUFNE4 but the rom description says to flash the 4.3 modem or it wont get data? someone help me out
heres the rom url http://forum.xda-developers.com/showthread.php?t=2504903

do not flash the older modem. just flash the rom and youll be good to go.

DocHoliday77 said:
do not flash the older modem. just flash the rom and youll be good to go.
Click to expand...
Click to collapse
since im coming from stock 4.4.2 do I only wipe cache n dalvik before flashing

You will most likely have to factory reset since you are downgrading.
You can try just wiping dalvik, but if it hangs at boot youll have to factory reset.

one more question
DocHoliday77 said:
You will most likely have to factory reset since you are downgrading.
You can try just wiping dalvik, but if it hangs at boot youll have to factory reset.
Click to expand...
Click to collapse
Thank You I tried wiping cache n dalvik, it hung but I went back in to twrp n wiped cache n dalvik again after install, worked like a charm!!!!!
hank you very much but can you answer me one question is there anyway you or another could port the revolutionary s5 v3 to the i747 it looks so amazing they only have it for the s3 i9300 not the s3 i747

Afaik, porting from tbe i9300 is a pretty difficult process. The device is very different from ours. Not saying it isnt possible, but I dont think we've really ever had any ports from that device.
I wont be able to try as I just have too much on my plate already and not enough time as it is. Sorry....maybe someone else will tackle it....

DocHoliday77 said:
Afaik, porting from tbe i9300 is a pretty difficult process. The device is very different from ours. Not saying it isnt possible, but I dont think we've really ever had any ports from that device.
I wont be able to try as I just have too much on my plate already and not enough time as it is. Sorry....maybe someone else will tackle it....
Click to expand...
Click to collapse
well thank you very much for responding you've been a very patient n helping hand if you could maybe you could pass it around to some of the other developers you are in contact with I know of about 30 people personally that would love to have that on there i747 not counting the people ive seen on here asking for a rom from the s5 but no big deal THANKS AGAIN

I was watching this thread because I had the exact same question. I tried installing the "StockMOD Custom ROM 4.3 RLS2.1" and my S3 wouldn't even boot past the Samsung screen. I left it there for 15 minutes and nothing. I tried wiping dalvik/cache from recovery and then it wouldn't even get that far. From that point on when I tried to reinstall the ROM it would go by and then when it got to the rebooting stage it would tell me "No OS installed. Are you sure you want to reboot?", or something of that nature. I then installed the Deodex Debloat Version from here: http://forum.xda-developers.com/showthread.php?t=2540998 and it installed/booted on the first try. Only problem is that Wi-Fi does not work & not sure of what my next step should be to get Wi-Fi working. I came from 4.4.2 OTA. Should I install the 4.3 modem or try flashing the StockMOD Rom again? I'm confused because it was stated that it didn't need to be installed.
Edit: I installed the StockMOD ROM directly over top without wiping anything and it worked. If I just want the "Deodex Debloat" version should I wipe, reinstall that ROM, then install the 4.3 modem since it didn't work before?
Edit: Second time flashing the Deodex Debloat ROM & Wi-Fi is working but now I have no data/4G. Help! LoL.

plastic_green_head said:
I was watching this thread because I had the exact same question. I tried installing the "StockMOD Custom ROM 4.3 RLS2.1" and my S3 wouldn't even boot past the Samsung screen. I left it there for 15 minutes and nothing. I tried wiping dalvik/cache from recovery and then it wouldn't even get that far. From that point on when I tried to reinstall the ROM it would go by and then when it got to the rebooting stage it would tell me "No OS installed. Are you sure you want to reboot?", or something of that nature. I then installed the Deodex Debloat Version from here: http://forum.xda-developers.com/showthread.php?t=2540998 and it installed/booted on the first try. Only problem is that Wi-Fi does not work & not sure of what my next step should be to get Wi-Fi working. I came from 4.4.2 OTA. Should I install the 4.3 modem or try flashing the StockMOD Rom again? I'm confused because it was stated that it didn't need to be installed.
Edit: I installed the StockMOD ROM directly over top without wiping anything and it worked. If I just want the "Deodex Debloat" version should I wipe, reinstall that ROM, then install the 4.3 modem since it didn't work before?
Edit: Second time flashing the Deodex Debloat ROM & Wi-Fi is working but now I have no data/4G. Help! LoL.
Click to expand...
Click to collapse
if you flashed it without wiping cache n dalvik- dirty flash then it should have worked unless u came from another 4.4.2 rom mine is working fine
correct me if im wrong

If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.

DocHoliday77 said:
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
Click to expand...
Click to collapse
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all

DocHoliday77 said:
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
Click to expand...
Click to collapse
Why exactly will it not work to flash a MJB kernel?
Boston78 said:
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
Click to expand...
Click to collapse
I would get either no wifi or no data depending on which modem was used after flashing the rom.
01 - Via TWRP (2.7.1.0) dirty flash d2att_4.3_MJB_Debloat_Deodex_v1.2.zip
02 - Reboot without wiping cache/dalvik = freeze at AT&T logo
03 - Wipe cache/dalvik = freeze at AT&T logo
04 - Factory Reset = success with the exception of no wifi
05 - Flash MJB modem = Wifi now enabled but no data. (baseband unknown/imei null)
06 - Flash NE4 modem = data/baseband/imei restored, but no wifi again
07 - Flash UCUEMJ2_Insecure_kernel.zip + wipe cache/dalvik & reboot = somplete succcess (wifi+data all working)
At least for my experience Doc is 100% correct. Not sure how you were able to flash the StockMOD ROM without having to flash a kernel. Especially when "How to flash" on the StockMOD page says "5. Flash Kernel (For WiFi)". Not saying you are lying, just that I don't understand why you didn't need to.

Boston78 said:
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
Click to expand...
Click to collapse
Are you using this rom along with the included kernel? Or something different?
plastic_green_head said:
Why exactly will it not work to flash a MJB kernel?
I would get either no wifi or no data depending on which modem was used after flashing the rom.
01 - Via TWRP (2.7.1.0) dirty flash d2att_4.3_MJB_Debloat_Deodex_v1.2.zip
02 - Reboot without wiping cache/dalvik = freeze at AT&T logo
03 - Wipe cache/dalvik = freeze at AT&T logo
04 - Factory Reset = success with the exception of no wifi
05 - Flash MJB modem = Wifi now enabled but no data. (baseband unknown/imei null)
06 - Flash NE4 modem = data/baseband/imei restored, but no wifi again
07 - Flash UCUEMJ2_Insecure_kernel.zip + wipe cache/dalvik & reboot = somplete succcess (wifi+data all working)
At least for my experience Doc is 100% correct. Not sure how you were able to flash the StockMOD ROM without having to flash a kernel. Especially when "How to flash" on the StockMOD page says "5. Flash Kernel (For WiFi)". Not saying you are lying, just that I don't understand why you didn't need to.
Click to expand...
Click to collapse
As for why, starting in 4.3 (MJB) samsung moved the modules required for wifi to work. They are now included in a different partition. Custom kernels (or rather any kernel but the original stock) look for the modules (drivers) to be in /system/lib/modules (the location on earlier builds). Since they are not there, the system doesnt know how to use the wifi radio resulting in no working wifi.
We got lucky with the MJ2 kernel. It was the first 4.3 leak, and just by chance I tried it on a different leak (for the T999) while trying to figure out the wifi issue and it worked! They simply had not made the change in that test build. Pure luck! The kt747 kernel works because it was built from source and modified to use its own modules which are included in the kernel package.
It has been a good while, so as for where the modules are located now im not suren. But if you browse to /system/lib/modules and find wlan.ko, youll see it is symlinked to /system/lib/modules/prima/prima_wlan.ko. Youll also notice there is no prima folder or file. In older builds, the wlan.ko file was actually there.
Hope that made sense and hope I got most of it correct. (Going from memory)

DocHoliday77 said:
Are you using this rom along with the included kernel? Or something different?
As for why, starting in 4.3 (MJB) samsung moved the modules required for wifi to work. They are now included in a different partition. Custom kernels (or rather any kernel but the original stock) look for the modules (drivers) to be in /system/lib/modules (the location on earlier builds). Since they are not there, the system doesnt know how to use the wifi radio resulting in no working wifi.
We got lucky with the MJ2 kernel. It was the first 4.3 leak, and just by chance I tried it on a different leak (for the T999) while trying to figure out the wifi issue and it worked! They simply had not made the change in that test build. Pure luck! The kt747 kernel works because it was built from source and modified to use its own modules which are included in the kernel package.
It has been a good while, so as for where the modules are located now im not suren. But if you browse to /system/lib/modules and find wlan.ko, youll see it is symlinked to /system/lib/modules/prima/prima_wlan.ko. Youll also notice there is no prima folder or file. In older builds, the wlan.ko file was actually there.
Hope that made sense and hope I got most of it correct. (Going from memory)
Click to expand...
Click to collapse
whatever kernel that was built into the rom is what im on I listed it in my reply before, I haven't flashed anything else ONLY THE ROM, mine booted right up n works great,

The more I think about it, it makes sense to me in both situations.
Id expect it to work on 4 4.2 because the wifi drivers are still in the same location, so as long as youre on 4.3 or above, it should work, as it apoears to do for you. But there are ithers who it did not work for and they have to use one of those other kernels. So it could be newer drivers not being compatible. Either way, if wifi is not working, I do know the kernel change will fix it.

DocHoliday77 said:
The more I think about it, it makes sense to me in both situations.
Id expect it to work on 4 4.2 because the wifi drivers are still in the same location, so as long as youre on 4.3 or above, it should work, as it apoears to do for you. But there are ithers who it did not work for and they have to use one of those other kernels. So it could be newer drivers not being compatible. Either way, if wifi is not working, I do know the kernel change will fix it.
Click to expand...
Click to collapse
well I have a twrp backup of it on my phone if you have some way of opening it, maybe somehow I could send it to you n whatever you find may be a tremendous help to you in how to fix the wifi n not having to flash the other kernels

I dont think there would be anything in a nandroid backup that would help. But tbh, right now I have no intention of digging into it any further. First because we already do have a pretty simple solution, and second because im already swamped with other projects and problems I've promised others I would work on.