Related
I am not very much familiar with all intricacies of Android system but i have played around rooting and putting customer firmwares on few devices.
I have AT&T Galaxy S3 with following detals:
Baseband: I747UCUEMJB
Version: 4.3
I had the device rooted in the past but recently un-rooted it and reset the flash counter as well and did factory reset. Did all that since i wanted to use ISIS and couldn't make it work on a rooted S3. Seems it used to work before till they updated ISIS app to patch it.
Now AT&T got 4.4 update and my phone detects it, downloads it but while installing fails at 32%. I have seen many threads where people faced similar issues due to their phones being rooted. Seems something on my phone didn't reset to default.
I found one post which mentions that i can download UCUEMJB_to_UCUFNE4_Firmware_update.zip and load it to phone using TWRP. As i understand, this will update the baseband but android version still remains at 4.3 (?). Is that the path i should be looking for or i am shooting in wrong direction? I want to stay on default firmware since i like to use ISIS till they keep running those cashback promos
Would appreciate some feedback.
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
DocHoliday77 said:
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
Click to expand...
Click to collapse
Thanks for the reply.
Just to confirm so that i don't mess up, i will apply the following(is modem same as firmware?) and then try OTA.
I747UCUEMJB: modem_CWM_I747UCUEMJB.zip
No. The modem is only one part of the firmware. Firmware includes bootloaders, kernel, system, modem and more.
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
GreatGrizzwald said:
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
Click to expand...
Click to collapse
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
http://www.sammobile.com/
absinthesummer said:
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
Thank you very much for the advice. I am downloading the firmware now. baseband version is showing i317ucama4. Right now the phone is not activated with AT&T, is there a way I could test if I will be able to get cellular data before going to AT&T and activating it?
Click to expand...
Click to collapse
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
absinthesummer said:
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Click to expand...
Click to collapse
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
1425
rangercaptain said:
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
Click to expand...
Click to collapse
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
GreatGrizzwald said:
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
Click to expand...
Click to collapse
It sounds like the phone was updated previously to either 4.3 or 4.4.2, which have Knox and that pesky counter. Technically you can't directly downgrade, so be sure you're downloading firmware that is 4.3 or higher. I didn't realize sammobile only went to MA4 for US AT&T. (In a pinch you can use Canadian firmware, but we have other links for stock firmware). Also, don't worry too much about Kies. It can be helpful, but honestly I could never get my note 2 recognized by kies either.
When I get back from taking my kids to school, I'll gather some links that will help you revive this phone Links below:
@GreatGrizzwald:
More recent links to stock firmware: STOCK PACKAGES TO MK6 This is LJ2 (4.1.2), MK6 (4.3) and up. He's got all the stock firmwares, available for flashing either in recovery on via odin. I've highlighted the one I would use in the attached screenshot (MK6- ODIN)
He also has a thread for NE5 (The latest firmware, 4.4.2) HERE
So if MK6 doesn't work, try NE5. One of those two has to work. You're dad already updated to either 4.3 or 4.4.2, I don't know which so start with 4.3 (MK6) and if it doesn't work try 4.4.2 (NE5)
On those two threads, he has a TON of links that will be helpful to you in getting back to stock also.
And here's a reference page with some useful links: One Stop Shop
This one is dedicated to downgrading back to LJ2 (4.1.2) from 4.3+, it MIGHT come in handy for you: Downgrade Instructions
If you have trouble with the stock firmware, you can also try Chainfire's CF Auto Root. It's stock firmware but it's rooted. Try the other firmwares by Zen Arcade first though CF AUTO ROOT
We'll get it going for you The stock firmware will re-flash the modem and all the configuration files so you're data should work again. Then you can do whatever you want, root, recovery, flash other stuff, or leave it stock. You got this
---------- Post added at 07:51 AM ---------- Previous post was at 07:09 AM ----------
GreatGrizzwald said:
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
Click to expand...
Click to collapse
Also you have to figure out if it's software or hardware. I'm inclined to believe it's software so I think if you get it back to stock you'll be good. If it was hardware, it wouldn't even recognize a sim being inserted (recently repaired an htc one mini with this problem, it needed a new Sim tray, thankfully it was only $20).
But it sounds more like a bad flash corrupted some of those important files and configurations controlling data connections, it's all good, if it's software it can definitely be fixed. If it were hardware it could still be fixed it would just be a bit more time consuming.
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Thank you for all this, I will start working with it today. You have been a huge help.
GreatGrizzwald said:
Thank you for all this, I will start working with it today. You have been a huge help.
Click to expand...
Click to collapse
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
1100
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
GreatGrizzwald said:
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
Click to expand...
Click to collapse
That is great news! I'm so glad it's working for you. Enjoy your (new-to-you) note 2 and keep those files on hand in case you need them in the future!
absinthesummer said:
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
Click to expand...
Click to collapse
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
GreatGrizzwald said:
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
Click to expand...
Click to collapse
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
absinthesummer said:
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
Click to expand...
Click to collapse
Awesome, that makes a lot more sense now. Thanks again.
Hey I forgot you don't have custom recovery. Anyway, I sent you PMs,and you can do a search of this very forum- use the search term "update" or "ota" and you will find a LOT of threads on boot failures after OTA. Most people got their phones back.
If you can't get into DL mode (Vol-, Home, Power), try getting into the stock recovery (Vol+, Home, Power) because you should/could be able to factory reset the device from there. Also hold the button combo longer than usual. If one recovery option (DL mode) isn't working, than theoretically the other should still be accessible, through which you can adb sideload to the device or try factory reset. I know it's frustrating, but you're not the first nor the last to have an OTA go wrong ;/ We'll get ya back up & running.
You're not the only one in trouble after that update: http://forum.xda-developers.com/galaxy-note-2-att/help/todays-update-soft-bricked-phone-t2939649
Q&A for [Baseband] ALL T999, T999L, T999V, T999N Modems! w/ MAP and Data Tweaks!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
modem T999VVLUFNH2
Hi everybody,
I try to find the updated modem for my S3 (videotron SGH-T999v)
I have the modem T999VVLUFNF1 (ROM LS 3.1 stable KK 4.4.4, KT747 kernel)
When I unzip the official ROM of samsung (older like 4.1.2 and the last samsung update from september 2014) , I only find the file NON-HLOS.bin
According to sammobile the last videotron modem is T999VVLUFNH2, but I cannot find the file. This is the first time I try to update the modem because I have a poor reception in my house.
Thank you for your help
I haven't decided if I will post those or not. Too great a risk with the 4.4.2 modems. If you want to try the latest I can only recommend fully updating as a safe way to do so.
If you really want to be the one to test if it's safe, I'll get it uploaded for you, but understand there is a chance it could hard brick the phone beyond repair.
Reason for all of this is because we know if you flash a 4.4.2 modem on 4.3 it'll permanently brick it. I have no idea if flashing an older or newer 4.4.2 modem on 4.4.2 firmware (like you want to do) will result in the same. Normally, I would guess it wouldn't be the case, but it seems a lot has changed in these new builds that no one understands, and there have already been too many bricks for me to be comfortable trying something new like this without exercising great caution.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thank you for your reply and your advise.
As I don't have enought money to take the risk, I will keep my actual modem.
Thank again
Don't blame you a bit! But don't forget, you can still fully update and that may help. (From what I've seen, flashing older modems on 4.4.2 doesn't brick, so i think if you updated, it should be ok to flash the NF1 modem if the newer one doesn't help. It might not work, but I don't think it would cause any harm. Just food for thought, but again, I can't guarantee anything with these latest modems...)
If it's a bad signal issue that you did not have before, call your carrier and ask if there are any tower/network/account issues they are aware of.
Your carrier probably doesn't do this, but Tmobile will sometimes give customers a signal booster for home use only. You can buy them online too, but I'm not sure how my h they are these days. (Just make sure it boosts the frequencies used by your carrier if you look into this.)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Just noticed today that my phone is on T999VVLUFNF1 but that there is a newer 4.4.2 release for the T999V phone that is T99VVLUFNH2. Would it be good to update via Odin to this? Is it just a newer modem?
I have a T mobile T999 that is currently flashed with CyanogenMod 11-20141008-SNAPSHOT-M11-d2lte which is kitkat 4.4.4. The baseband version is T999UVDMD5. I have a Lebara sim card in it now, and I'm in France. I'm not getting any signal and I suspect it is because the baseband version mismatch. Is there anything I can do to make this setup work or do I have to downgrade to a different version of CM? Is there and updated modem I can flash on this device or any way to make it work?
abetterlie said:
I have a T mobile T999 that is currently flashed with CyanogenMod 11-20141008-SNAPSHOT-M11-d2lte which is kitkat 4.4.4. The baseband version is T999UVDMD5. I have a Lebara sim card in it now, and I'm in France. I'm not getting any signal and I suspect it is because the baseband version mismatch. Is there anything I can do to make this setup work or do I have to downgrade to a different version of CM? Is there and updated modem I can flash on this device or any way to make it work?
Click to expand...
Click to collapse
Latest baseband is NC2, flash it, and if the device still does not pick up service flash back to MD5 firmware and see if it will pick it up. If not then it might incompatible with your provider..
Thanks!!!! Also Those using T999 switched to ATT
Just wanted to say thank you!!!
Also just wanted to say for those who have a T999 that switched to AT&T this works (I wasn't sure if this would work since it didn't say anything about AT&T working with it. To be perfectly honest I didn't read everything but again THANKS!!!!!!
Hi Guys,
I got the OTA update ( T999UVUENC2 ) about a month back and since then, my Wifi has stopped working. It stays greyed out when I try to turn it on. Just won't turn on.
The logcat says that the "WiFi driver is unstable".
What I have tried so far (with no success):
1) Flash the same build again (T999UVUENC2).
2) Flash the root666_T999UVUENC2 build. (Currently, I am on this)
3) Flash Cyanogenmod 11.
4) Factory reset.
5) Pull the battery out when the phone is on and put it back again.
6) Modify/delete the wpa_supplicant.conf file.
Can someone please give any directions on how the "Wifi driver can be fixed"? I understand from going through the forums that downgrading from 4.3 to 4.2 can cause a brick. However, can I downgrade to the previous T-Mobile 4.3 build (T999UVUEMJC ) without causing a brick? Do you guys think that can help fix the Wifi?
Any help would be greatly appreciated.
Could you point me to what one exactly i need for T999LUVUBNF4
SGH-T999L Will Not Mount Ext Sd/No root or load file from .zip to root
I always get stuck at the boot screen where I am supposed to Update from Zip, but my phone NEVER lets me Mount the External SD card, I have a 64GB card, failed, 16 GB card, failed, what am I missing. All the good tutorials, ESPECIALLY yours, get me to that point but being unable to load that .zip file from sd just murders me. The Phone is on 4.3 and I believe I loaded your stock 4.3 firmware after failing to get this part done and then trying every single rom possible (didn't realize this had murdered me) until I managed to get back to this stock rom. Why does it not want to load from ext sd? Is it the file system? I've never had any issues with any of these sd cards, and they aren't generic cards, one is a samsung other a sandisk,
Hello,
I tried to flash custom ROM, but something somewhere went terribly wrong.
I did read some guides on flashing before attempting this and did make some precutions as well.
Such as creating ROM backup with CWM and copying efs folder with Root browser.
Unfortunately I didn't succeed with the flash. Now the phone can turn on, but there is no network service, and IMEI number is missing.
I tried to go back to my original ROM, but that didn't fix the problem.
I tried to gather as much information as possible, but it seems that information on this device is a bit outdated. For example, I wanted to try to flash back to stock ROM with odin, but most links with stock ROM are down. The one that isn't down only provides .7z file instead of md5,tar file that is required by odin.
The device works, just can't connect to mobile network.
Is there something I could do?
Before flashing anything else, what baseband and bootloader is on the phone? The imei may be missing because the ROM is too new for the phone's current bootloader/modem combination.
Bootloader version is T999UVDLJA
Baseband version is UKNKOWN
I have finally found stock ROM in tar.md5 format, which is compatible with ODIN.
The t999 is the aws version of the s3 according to this: http://www.gsmarena.com/samsung_galaxy_s_iii_t999-4804.php
This forum is for the i747 and i747m (the AT&T and Rogers) version of the s3.
If the t999 is like the i747, do not flash any ROM via Odin that tries to downgrade the bootloader as this may brick the phone.
This makes just even more complicated.
When I go to settings -> About device, under model number I have SGH-I747.
When I double check this with Samsung phone info app, under model number I have SGH-I747.
In the same Samsung phone info app under PDA version I have I747UCDLK3 and under CSC version I have I747ATTDLK3
t999 only appears when I enter Download mode via volume down + home button + power button.
What does the label under the battery say about the model #?
Label under the phone is SGHT999.
Wow, this phone is weird...
I read on the forums that there is chance to restore firmware of the phone with KIES, so I tried that. At first I entered SGH-I747 model number and serial number of the phone and it failed. But after that I entered SGH-T999 model number and serial number of the phone and KIES started to update the phone.
At the moment I have android V4.3
Bootloader T999UVUENC2
Baseband T999UVUENC2
PDA version T999UVUENC2
CSC version T999MBENC2
Phone seems to be unrooted, IMEI number is visible, I can call again, but the phone's factory mode is on.
It seems that I had a SGH-T999 which somehow was tricked int thinking that it is SGH-I747.
At the moment I would just like to have a stock ROM for this phone without all the T-Mobile apps, would that be possible?
Does everything see to work?
The easiest way to root and remove apps would be to flash a custom recovery, install supersu and titanium backup. Then use titanium backup to remove the apps.
Yes, at the moment everything works.
I can call, receive sms, use wi-fi as well as mobile data.
The only problem is that phone has factory mode on Yellow text on black background. And it is heavily loaded with T-Mobile applications.
So I guess this phone is T999 then, right? How could it be that everywhere it had I747?
By custom recovery you mean custom ROM?
You need a custom recovery such as TWRP: http://forum.xda-developers.com/showthread.php?t=1809313
Download the tar version that can be flashed via Odin.
Download supersu and copy it to the phone. Flash recovery, boot directly into recovery without letting the phone boot the ROM, flash supersu, reboot. Install Titanium Backup from the Play store, remove the apps.
Thank you for sticking with me in this thread!
Could you please explain a little bit more what is TWRP? From the link provided I understand that is is a application that helps with custom rom flashing and backing up roms?
Shouldn't I do this at first - http://forum.xda-developers.com/showthread.php?t=1771687
Boot into download mode. Do you see anything about warranty bit 1? If you do, that means you have already tripped the counter.
Root is not required to flash a custom recovery.
If you are only interested in root, follow the other thread. If you want to be able to flash custom ROMs and backup the rom, you need a custom recovery which will definitely trip the counter.
Do you have any warranty left on the phone?
Yes, there is 1 next to warranty bit. What does it mean for me that I have tripped the counter?
At the moment I would just like to get rid of factory mode and remove those unwanted T-mobile APPS. I think I will be done with Flashing for quite some time
I don't have any warranty on the phone, It has been in the family for quite some time.
It would be 0 if the counter wasn't tripped.
To bring it right back to stock, you could flash one of the prerooted ROMs from the other thread. Just make sure you are flashing a rom that has the same bootloader that is currently on your phone. Hopefully, the stock rom will remove the factory mode.
I understand that the counter is only important if you need warranty, yes?
I actually just found a way how to remove the factory so that is one more thing less to worry about
And I rooted the phone with odin using the link few posts back.
Now for the final question, I understand that this rom is something along the lines that I'm looking for? http://forum.xda-developers.com/showthread.php?t=2501303
The ROM looks nice as long as you are running the correct bootloader and modem.
Installing a custom ROM only requires a custom recovery. There is no need to root or remove apps from the existing ROM since you are going to wipe the existing ROM before installing the new ROM.
I read through the thread and I understand that I have to flash T999UVUEMJC modem before flashing the ROM.
I'm not sure where the bootlaoder of this rom is mentioned. Only place where boot loader of my device T999UVUENC2 is mentioned is in change log "-Rebased to T999UVUENC2".
The official T-mobile firmware is here: http://www.sammobile.com/firmwares/database/SGH-T999/
Notice the last few letters in the firmware PDA?
Based on your post on the first page (post #7) you are on the NC2 bootloader and modem, which are compatible with the rom you are wanting to flash. (See the second line under the Disclaimer banner.) NC2 is the most current firmware for the T999 listed on the page Audit linked to.
(one explanation for how your device was reporting i747)
Is it possible that someone else flashed the i747 rom to this phone? Either someone doing you a favor or a previous owner? I747 roms will work on the T999, I frequently see people commenting on doing so successfully. You just need to have comparable bootloaders and modems. That and if the rom dev didn't accommodate the device in the updater-script the user must edit the script himself. In the unofficial cm12.1 thread for the i747 people were doing this often.
So the bootloader version is always the same as the modem version?
I understand that in my case I don't need to flash T999UVUEMJC modem, since the one I have at the moment is newer?
That is definitely possible, although, how it came to be I will never know, since I personally didn't buy the phone. But this would explain a lot.
Could you please take a look at this thread, I created steps I plan to do in order to flash the above mentioned ROM. It would really put my heart at ease http://forum.xda-developers.com/galaxy-s3-t-mobile/help/one-rom-flashes-please-double-check-t3111443
Hello! Now, I am a new member, And solely for one reason..
I AM UNABLE TO FIND A MODEM FLASH FOR 4.1.1 BASEBAND I317MVLUDNH2
Now, I have searched EVERYWHERE, and, all the Rom's are for the I317, and if it is for the I317M, I am unable to download for some odd reason.
Now, Here are the links i've searched through (Just incase I missed something)
http://forum.xda-developers.com/showthread.php?t=1987541
http://forum.xda-developers.com/showthread.php?t=2005141
http://forum.xda-developers.com/showthread.php?t=2275844
http://forum.xda-developers.com/showthread.php?t=2590452 This may be the answer.. Tho I've heard using a Flash not made for your Modem can brick your phone..
http://forum.xda-developers.com/showthread.php?t=2581321
http://forum.xda-developers.com/galaxy-note-2-att/help/sim-unlock-4-4-2-t2822603/page3
http://android.stackexchange.com/qu...317-att-samsung-galaxy-note-2-on-jelly-bean-4 (links back to first link)
So, I am basically out of ideas. All i want to do is DOWNGRADE to 4.1.1, unlock the phone through the hidden menu, Then go back to 4.4.2. (Since i got the phone from a friend, and am currently using a rogers [Well, More of a Petro-Canada] Sim...)
So, Would I be okay using that Rogers flash? With Phrilz OR TWRP?? Or how would i go about this???
FIGURED IT OUT!!!
Okay, Here is a rundown on how to do it:
1. First download TWRP https://twrp.me/Devices/
2. Download the ROGERS Modem firmware http://d-h.st/rJq
3. Download Odinhttp://androidhost.org/get/PVAIv
4. Enable USB Developer Mode
5. Put the Phone into Odin download mode (Shutdown. Hold down Power+Volume Dwn+home. When the Bootsplash shows, Let go of Power button. Press Volume Up
6. Open Odin on your computer, browse to the TWRP .img (if you haven't already unzipped it, Do so) In the PDA section
7. Hit start, Wait till it is finished
8. Now, Open the phone directory in your windows manager thats built into the OS.
9. Drag the .zip into your main phone directory ( / )
10. Shutdown the phone, Hold power+Volume Up +home. Do it until bootsplash is done. (same as step 5)
11. In TWRP, select backup, then backup the MODEM folder. (I honestly forgot this step, If you have. There is links for the original baseband.)
12. Once that is backed up, You can either upload it to your desktop (i'd recommend doing that) Then, Open install, Browse for the .zip for the MODEM, then flash.
13. The system will reboot back into TWRP, just pull the battery out, and insert it back in, boot up the phone.
14. Type in your dial: *#197328640#, UMTS, DEBUG SCREEN, PHONE CONTROL, NETWORK LOCK, Then select option 4. Reboot phone
The simcard should now work!! Now, You can either install the old firmware you backed up, or just leave it.
New firmware for 4.4.2 Incase anyone Needs it: http://www.sammobile.com/firmwares/database/SGH-I317M/
Hopefully this helps anyone. It took me 5 hours to find out all this info (because the phone is a I317M, Not the non "m" version)
THANKYOU FOR ALL THE WORK OTHERS DID FOR ANY OF THESE PROGRAMS USED!!!!
THIS DOES NOT WORK ON CUSTOM ROM!!! You must have the original Stock rom, or atleast something close with the samsung stock dialer, as the code only works on those.
Thank you for your detail instructions. Recently I got a used a SGH-I317M locked to Rogers. It has firmware 4.4.2. Will it be safe to follow your instructions to flash the 4.1.1 Rogers modem only, do unlock, and then restore to the original 4.4.2 modem with twrp?
Thanks,
Howard
howard30 said:
Thank you for your detail instructions. Recently I got a used a SGH-I317M locked to Rogers. It has firmware 4.4.2. Will it be safe to follow your instructions to flash the 4.1.1 Rogers modem only, do unlock, and then restore to the original 4.4.2 modem with twrp?
Thanks,
Howard
Click to expand...
Click to collapse
Yes that should work (So sorry for the late reply, I haven't been on this site since I made the post) Just make sure to backup before you do anything incase it does happen to screw up Just remember to select that last link (sammobile) and get the firmware FOR YOUR NEW CARRIER, not the old one.
I need to unlock my At&T note 2 but it is now running 5.1.1 Bliss Pop. I tried that code but of course it wont work.
I sent the IMEI number and paid to have it unlocked but the company I sent the money to said they could not unlock it either.
What would I have to do to this phone to unlock it. I am in Cananda this week and want to use this PetroCan sim card I paid for.
Thanks
madpb said:
I need to unlock my At&T note 2 but it is now running 5.1.1 Bliss Pop. I tried that code but of course it wont work.
I sent the IMEI number and paid to have it unlocked but the company I sent the money to said they could not unlock it either.
What would I have to do to this phone to unlock it. I am in Cananda this week and want to use this PetroCan sim card I paid for.
Thanks
Click to expand...
Click to collapse
Okay, this is quite simple, install TWRP as usual, but backup the MODEM you have right now for 5.1.1, Then follow through the instructions, and install the MODEM you backed up after. That shoould work, if not, try to find modems for the phone for 5.1.1, But usually, (if my computer knowledge is correct) a new OS shoould support and older modem, so, you can try 5.1.1 with a 4.4.2 modem.
J.Naw said:
Okay, this is quite simple, install TWRP as usual, but backup the MODEM you have right now for 5.1.1, Then follow through the instructions, and install the MODEM you backed up after. That shoould work, if not, try to find modems for the phone for 5.1.1, But usually, (if my computer knowledge is correct) a new OS shoould support and older modem, so, you can try 5.1.1 with a 4.4.2 modem.
Click to expand...
Click to collapse
I tried the rogers modem and the *#197328640# did not work.
Any other modem files you can suggest?
It appears that I have to the load original stock rom but I also read that is not possible either.
madpb said:
I tried the rogers modem and the *#197328640# did not work.
Any other modem files you can suggest?
It appears that I have to the load original stock rom but I also read that is not possible either.
Click to expand...
Click to collapse
Huh.. Thats honestly really weird, It should work. Did you check the "about" section of your phone to make sure it properly installed the 4.1.1 modem?
w w w.android.gs /flash-android-4-4-2-kitkat-i317mvludnf1-for-canadian-galaxy-note-2-i317m/
(remove the spaces.. XDA forums aren't letting me post outside links -_-)
your second link modem
it has tons of popups and when its not trying to open new windows and ask for browser access etc it downloads a "flash file" your 1.4mb download is a exe and puts up a warning.
since samsung removed the menu entery they left in by mistake on early 4.1x releases there is no way this ork to do anything but install malware and trojans from your site.
Kal Jack said:
it has tons of popups and when its not trying to open new windows and ask for browser access etc it downloads a "flash file" your 1.4mb download is a exe and puts up a warning.
since samsung removed the menu entery they left in by mistake on early 4.1x releases there is no way this ork to do anything but install malware and trojans from your site.
Click to expand...
Click to collapse
You can extract the modem from the stock 4.1.2 ROM or you can flash the entire stock ROM in Odin, unlock, and flash back to the latest stock ROM.