Develop Bugs

[Q] [HELP] Soft Bricked i9505

I rooted my GS4 yesterday and had no issues at all until i tried to flash a MOD to obtain wireless hotspot, but what i didnt notice was the MOD was for a Sprint version GS4. I know know if thats exactly what made my phone brick but im pretty positive because it was during the reboot that the phone got stuck on the TMO screen and apparently remaining soft-bricked. I spent the rest of the night and all of today reading and researching how to fix it myself before coming here to ask for help, so please bare with me.
I have already attempted to flash the official stock firmware using Odin, but it displays an error everytime saying it failed and something about AUTH. Sorry if im sounding vague, i am on a back up phone to use the internet and forgot to right down the exact message.. Anywho, i tried wiping everything and redoing the process and i even tried to flash the appropiate PIT file that i found but it still displays an error and says failed because of some AUTH or SEC problem.
Ive been at this diligently for almost 12 hours. My brain is filled with all these suggestions and methods that i have tried to use to restore my phone back to factory, but none of them have worked. I can still get into recovery and all that, so im assuming that there is still good chance i could fix the problem?
Also i am starting to get myself more and more confused about whether the firmware i downloaded is the right one i need for my phone, it seemed so at first but now i see theres TONS of region codes that can determine the firmware version?
Sorry if im all over the place, but i just dont know which step to take next..
I appreciate any help that is given, and im even willing to pay (some) bucks or maybe even (btc) for someone to walk me through what i need to do or what im doing wrong.
Thanks in Advance

Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?

Toleraen said:
Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?
Click to expand...
Click to collapse
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..

koolbreez12 said:
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..
Click to expand...
Click to collapse
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.

Toleraen said:
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.
Click to expand...
Click to collapse
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.

error post

If you can get into download mode i would suggest flashing stock with that then rerooting that way the program downloads all of the nessacary stuff on its own.

koolbreez12 said:
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.
Click to expand...
Click to collapse
Welcome!
Sent from my SGH-M919 using xda premium

cm installer?

will it work with i747m? (canadian version, it's not listed as a supported device, and the android app says im not supported :s)
also, how do they expect you to make a nandroid backup without root?

ejatds said:
will it work with i747m? (canadian version, it's not listed as a supported device, and the android app says im not supported :s)
also, how do they expect you to make a nandroid backup without root?
Click to expand...
Click to collapse
Yeah the second I saw that (Rogers GS3) I just stopped. I swear this phone, or rogers, or samsung, does _NOT_ want me putting CM on this device.

If you want to risk bricking/soft bricking, then don't try it. The d2att version might work, but it also might not. And yeah, AT&T bugs me too with their super slow updates and the soon to be added Samsung Knox for the 4.3 update

You know guys, it's a pretty easy phone to deal with once you rack your brain for a night and understand everything. No use for CM installer.

polobunny said:
You know guys, it's a pretty easy phone to deal with once you rack your brain for a night and understand everything. No use for CM installer.
Click to expand...
Click to collapse
I agree completely. This device is perhaps one of the easiest I have rooted. It is easier now than it was a year ago.
While I like CM, I foresee some problems coming up because even with the process made "simple", someone will screw it up royally. I'm of the mind that if you don't know how to do it and don't want to take the time to read up and learn how to do it properly, you should not be rooting and installing a custom Rom whatever the means of doing so.
Sent from my Inspire 4G using xda app-developers app

Not sure where else to post about it but I'll ask here.
I've successfully rooted my Rogers GS3 using the how-to section and installed CWM and installed version 5.5.0.4 just fine. But things started acting up once I tried to install CM 10.2 nightly and CM 10.1 stable. (From what I've read the Rogers GS3 is supposed to be treated exactly like the AT&T version) During the flash I got a status 7 error something something getprop assert error. Search around the forums and one solution was to get rid of some lines of code in the actual ROM itself. Tried that, still same error.
So I tried downloading the newest version of CWM off their site but it was a .img file rather than a odin flashable .tar.
Using the tool here http://forum.xda-developers.com/showthread.php?t=2281287 To convert the .img to .tar and while the file converted properly odin said the recovery was invalid.
So I was stuck for about a week stressing out about it and CM installer app/Desktop client came out which was pretty cool. Opened it up and it says it's not applicable to this phone. Don't know where else to go but no where at all with this.

[Q] i747 refuses to install new ROMs

So this is kind of a longshot, Im hoping one of you guys will be willing to help. About a year ago I installed CarbonRom 4.2.2 on my AT&T Galaxy S3 i747, everything was fine with the installation except my 4G lte stopped working. I was researching and asking for weeks about what the solution could be, because obviously it could have been anything. Well sometime around then I edited my build.prop because someone on a forum post said it fixed their 4G problem. I was naive and didnt understand the implications of what the build.prop was so I never made a backup and edited it. (I fixed the 4G problem since)
It didnt break my device or anything, but now whenever I try to install a new rom it fails as I get an error that looks like this
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
After this started happening, I figured I was happy my device still worked and gave up trying to install new roms. However this week I bought myself a Galaxy Gear, and the naive fool I am didnt realize it wasnt compatible with Galaxy S3's running 4.2.2. So I was hoping if anyone had any ideas as to what I can do to fix the error and get me up to 4.3 or 4.4.
*A few other things* I tried last night to install a new rom to see if it would work or not, I got the above error and searching my memory card, the only ROM that would install was Carbon 1.6.1 d2mtr which I have a feeling is the wrong type of rom for my ATT i747. Also my build.prop says the following things:
ro.product.model=SCH-R530M
ro.product.name=d2mtr
ro.product.device=d2mtr
ro.build.product=d2mtr
etc
I feel like its a longshot, but if anyone has any clue or any ideas, it would be appreciated with the utmost gratitude!
~James

Edit the build.prop and change d2mtr to d2att. Do this for all 3. You can change the model to SGH-I747 if you like, but it probably wont matter.

SpiderJames said:
So this is kind of a longshot, Im hoping one of you guys will be willing to help. About a year ago I installed CarbonRom 4.2.2 on my AT&T Galaxy S3 i747, everything was fine with the installation except my 4G lte stopped working. I was researching and asking for weeks about what the solution could be, because obviously it could have been anything. Well sometime around then I edited my build.prop because someone on a forum post said it fixed their 4G problem. I was naive and didnt understand the implications of what the build.prop was so I never made a backup and edited it. (I fixed the 4G problem since)
It didnt break my device or anything, but now whenever I try to install a new rom it fails as I get an error that looks like this
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
After this started happening, I figured I was happy my device still worked and gave up trying to install new roms. However this week I bought myself a Galaxy Gear, and the naive fool I am didnt realize it wasnt compatible with Galaxy S3's running 4.2.2. So I was hoping if anyone had any ideas as to what I can do to fix the error and get me up to 4.3 or 4.4.
*A few other things* I tried last night to install a new rom to see if it would work or not, I got the above error and searching my memory card, the only ROM that would install was Carbon 1.6.1 d2mtr which I have a feeling is the wrong type of rom for my ATT i747. Also my build.prop says the following things:
ro.product.model=SCH-R530M
ro.product.name=d2mtr
ro.product.device=d2mtr
ro.build.product=d2mtr
etc
I feel like its a longshot, but if anyone has any clue or any ideas, it would be appreciated with the utmost gratitude!
~James
Click to expand...
Click to collapse
Well it's fairly simple, go back in your build.prop, find all the "d2..." (w/e you changed it to, I'm guessing d2mtr) and change it back to d2att. As well as changing the SCH-R530M to SGH-I747 if it's in there.
That should let you flash the I747 ROMs. Another mod you can make is in the updater-script of the ROM zip you're trying to flash. You would have to add or change the "d2att" to "d2tmr".
Side note, a SCH-R530M (MetroPCS variant) isn't an SGH-I747, which is the US variant. Did you edit your build.prop so it thinks that you have an SCH-R530M or do you actually have a MetroPCS variant or the S3?

DocHoliday77 said:
Edit the build.prop and change d2mtr to d2att. Do this for all 3. You can change the model to SGH-I747 if you like, but it probably wont matter.
Click to expand...
Click to collapse
Thanks for the quick response. I tried doing just that a few times and still getting the same error.

BWolf56 said:
Well it's fairly simple, go back in your build.prop, find all the "d2..." (w/e you changed it to, I'm guessing d2mtr) and change it back to d2att. As well as changing the SCH-R530M to SGH-I747 if it's in there.
That should let you flash the I747 ROMs. Another mod you can make is in the updater-script of the ROM zip you're trying to flash. You would have to add or change the "d2att" to "d2tmr".
Side note, a SCH-R530M (MetroPCS variant) isn't an SGH-I747, which is the US variant. Did you edit your build.prop so it thinks that you have an SCH-R530M or do you actually have a MetroPCS variant or the S3?
Click to expand...
Click to collapse
I have just an S3, I believe I was reading a forum post of someone who said he fixed his phone not having 4G after updating to a ROM on 4.2.2 and he posted his build.prop. I did not have much knowledge of android and was naive enough to believe that editing my build.prop like his would fix it. I did not edit it word for word, but I can see I edited the lines that said d2mtr, etc.
However, I just tried editing all the d2mtr lines and I'm still getting the same error

SpiderJames said:
I have just an S3, I believe I was reading a forum post of someone who said he fixed his phone not having 4G after updating to a ROM on 4.2.2 and he posted his build.prop. I did not have much knowledge of android and was naive enough to believe that editing my build.prop like his would fix it. I did not edit it word for word, but I can see I edited the lines that said d2mtr, etc.
However, I just tried editing all the d2mtr lines and I'm still getting the same error
Click to expand...
Click to collapse
Did you edit it with the right permissions? Make sure your edit saved. Also you might have missed one.
Once you make the edit, reboot and reinstall the recovery for your device as it probably has the d2tmr one atm.
Sent from my SGH-I747M using XDA Free mobile app

If editing the build.prop on a computer, make sure you are using Notepad++.
If all else fails, flash your firmware via Odin, root using Towelroot, then install your recovery and flash your rom.
Bwolf may be right about the recovery you are using, so try that first.

[Q] - [SOLVED] Chainfire rooted, on 4.3, Cannot get CM 10 to install. Need help!

Hello,
I keep running into issues trying to install CM 10. I have done backups, factory reset / cache wipe / davik cache wipe and I still cannot install the zip file of CM 10 from my external SD card. When trying to install CM 10, I get hit with an error
The phone as rooted using Chainfire's tutorial and I have root checker ensure that the phone is rooted, so I know I did it correctly (as I am using SuperSU).
Is the T-Mobile bootloader locked? I cannot get a straight answer on this. Some threads say yes, other no based on Google searches. I keep looking up and down for ways to unlock the bootloader for 4.3 and cannot find anything concrete other than for Verizon users.
I thought I found the root66 image would correct this, but I followed the steps and Odin indicated to me that it did not pass but showed failed instead! Is there another way?
Thanks for any / all help!
EDIT: Changed post based on last night's findings

Have u Factory ressetted the phone before installing CM ROM?

Yes I did! I updated my OP due to messing with the phone last night.

Bootloader is not locked, only at&t and Verizon is locked AFAIK.. Anyway you are getting errors because that build is old and is probably not recognizing your newer bootloader.. Why CM10 and not give CM11 a try?

serio22 said:
Bootloader is not locked, only at&t and Verizon is locked AFAIK.. Anyway you are getting errors because that build is old and is probably not recognizing your newer bootloader.. Why CM10 and not give CM11 a try?
Click to expand...
Click to collapse
I just downloaded CM 11 to my SD card and tried flashing it. I am getting the following errors:
getprop("ro.bootloader") == "T999UVUEMJC"
getprop("ro.bootloader") == "T999VVLDLL1"
getprop("ro.bootloader") == "T999LUVAMB7"
getprop("ro.bootloader") == "T999VVLDMF2"
getprop("ro.bootloader") == "T999VVLUEMK5"
getprop("ro.bootloader") == "T999LUVUBMK4"
E:Error executing updater binary in zip ' (FILE PATH)'

I think I got it! I followed this video on youtube to the letter and it worked!!
https://www.youtube.com/watch?v=QW1znjDLe-k
I also made sure to go here and use the right version of GAPPS. I was using the wrong version so it was giving errors.
http://download.cyanogenmod.org/?device=d2tmo
Thanks again all... This community rocks!

BimmerFerret said:
I think I got it! I followed this video on youtube to the letter and it worked!!
https://www.youtube.com/watch?v=QW1znjDLe-k
I also made sure to go here and use the right version of GAPPS. I was using the wrong version so it was giving errors.
http://download.cyanogenmod.org/?device=d2tmo
Thanks again all... This community rocks!
Click to expand...
Click to collapse
I actually ran into this issue as yours too! Did you remove every assert stuff like in the video? cause I tried asserting my bootloader and it still didnt work.

YPG70 said:
I actually ran into this issue as yours too! Did you remove every assert stuff like in the video? cause I tried asserting my bootloader and it still didnt work.
Click to expand...
Click to collapse
Yes. I removed everything that had assert on it like in the video. Based on what I have seen / read, you must be VERY certain it is the right version or it could brick your phone.
The rooting process IMO didn't seem too high risk, but when it came to flashing new software, I feel like this could be what really could damage your device if you are not careful.

Yes, be extremely careful when messing with the assertions in an updater script! I've seen several people hard brick because they did this to force an incompatible rom or mod to flash! They are there for a reason.
People just get too comfortable doing and recommending it I think. Whenever new firmware is released, it's a good bet that your favorite rom will work fine but the script doesn't include it. This makes for tons of threads and posts asking and instructing people how to do this, but rarely are there warnings included for anyone who comes across the thread in the future. (I'm guilty of this one too!)
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Firmware to fix Wifi on Virgin Mobile variant?

Howdy, I'm currently playing with bigsupersquid's unofficial cyanogenmod 13.1 rom for the Virgin Mobile variant of this phone. Everything on it works great except for the wifi which seems not to activate at all - also preventing me from using my tethering. I was forwarded to update the firmware for this device to Lollipop, but outside of the "A5-DUG" variant, I seem to be having trouble finding it. Can anyone provide me the right directions or place to start for this? Any help would be appreciated, thanks!

davidw.roggenkamp said:
Howdy, I'm currently playing with bigsupersquid's unofficial cyanogenmod 13.1 rom for the Virgin Mobile variant of this phone. Everything on it works great except for the wifi which seems not to activate at all - also preventing me from using my tethering. I was forwarded to update the firmware for this device to Lollipop, but outside of the "A5-DUG" variant, I seem to be having trouble finding it. Can anyone provide me the right directions or place to start for this? Any help would be appreciated, thanks!
Click to expand...
Click to collapse
yer lucky, I don't often browse the regular forum, just the threads I've already posted in.
however, I obviously need to add this link to the OP for cm13 (and maybe cm12 as well.)
http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
straight from the horse's mouth (htc,) that link.
getting it installed without M$ windows is challenging but can be done, requires some searching. with window$ it's relatively painless after downloading the 2+GB file and installing drivers and such.
I know some people are picky about questions in dev threads but I've always welcomed discussion there, so feel free to ask anything else in the ROM threads.

bigsupersquid said:
yer lucky, I don't often browse the regular forum, just the threads I've already posted in.
however, I obviously need to add this link to the OP for cm13 (and maybe cm12 as well.)
http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
straight from the horse's mouth (htc,) that link.
getting it installed without M$ windows is challenging but can be done, requires some searching. with window$ it's relatively painless after downloading the 2+GB file and installing drivers and such.
I know some people are picky about questions in dev threads but I've always welcomed discussion there, so feel free to ask anything else in the ROM threads.
Click to expand...
Click to collapse
I'm guessing that this is the process to use a RUU and revert back to stock to get the OTA update? I went through a huge debacle trying to find just this and managed to get it to work with a stroke of luck. I'm actually using your Cyanogenmod 13.1 without much issues. I'll leave a bug report in your thread. Thanks again!

davidw.roggenkamp said:
I'm guessing that this is the process to use a RUU and revert back to stock to get the OTA update? I went through a huge debacle trying to find just this and managed to get it to work with a stroke of luck. I'm actually using your Cyanogenmod 13.1 without much issues. I'll leave a bug report in your thread. Thanks again!
Click to expand...
Click to collapse
How do you get lucky? I am on CM 13.1 and still can't get wifi. I have the RUU and tried through windows and just got errors.

tucker1003 said:
How do you get lucky? I am on CM 13.1 and still can't get wifi. I have the RUU and tried through windows and just got errors.
Click to expand...
Click to collapse
Here, for everyone having firmware issues on chl, I spent all day uploading the zip RUU.
Make sure your phone is charged first. Very bad juju for it to die during firmware flashes.
I'm not sure if it needs stock recovery installed to use it or not. May not install without it and that'd be a hassle. Follow the instructions linked in my cm13 first post for installing stock recovery if you're wanting to play it safe.
Definitely
fastboot oem lock
before putting the 0P9CIMG.zip on external SD and rebooting into HBOOT. Or it won't flash.
Then remove the sd card after it is finally done. It'll take a few reboots to finish.