Related
I have had nothing but issues trying to use this software to update the firmware on my ATT S3. I'm new to Android (From Apple) and I'm still a noob but I have rooted and I have been trying all kinds of different ROMS. I cannot update my phone because I am getting the dreaded "Communication failed" error that more than a few people are getting.
One fix is to install latest update through Kies - but I can't seem to accomplish that. Am I able to update my firmware using Odin? I really haven't figured out much about Odin, I only rooted my phone with it once and that was easy and I din't learn a lot about Odin.
Can I use Odin to update firmware? If so how do I go about getting firmware file and whats the quick of it?
Thanks! :good:
jackryan57 said:
I have had nothing but issues trying to use this software to update the firmware on my ATT S3. I'm new to Android (From Apple) and I'm still a noob but I have rooted and I have been trying all kinds of different ROMS. I cannot update my phone because I am getting the dreaded "Communication failed" error that more than a few people are getting.
One fix is to install latest update through Kies - but I can't seem to accomplish that. Am I able to update my firmware using Odin? I really haven't figured out much about Odin, I only rooted my phone with it once and that was easy and I din't learn a lot about Odin.
Can I use Odin to update firmware? If so how do I go about getting firmware file and whats the quick of it?
Thanks! :good:
Click to expand...
Click to collapse
What firmware are you trying to update to? Once your phone is rooted and your "trying all kinds of different ROMS" I question your need for Odin. Unless your trying to go back to a bone stock ROM I'd think that you would want to use whatever custom recovery that you've installed (CWM or TWRP) to install a ROM. I'm not going to link to it but I can guarantee that if you search for it here or on Google you'll find several guides to Odin.
rcook55 said:
What firmware are you trying to update to? Once your phone is rooted and your "trying all kinds of different ROMS" I question your need for Odin. Unless your trying to go back to a bone stock ROM I'd think that you would want to use whatever custom recovery that you've installed (CWM or TWRP) to install a ROM. I'm not going to link to it but I can guarantee that if you search for it here or on Google you'll find several guides to Odin.
Click to expand...
Click to collapse
Well, here's the thing. ATT has pushed out updates and I'm not getting them. I know some updates improve things - like call quality etc. Since I am not getting these I'm worried that I am missing out. I have uninstalled EVERY SINGLE ROM I have tried because of one issue: everyone I talk to on my phone hears an echo of their voice, it's so bad they tell me they have to hang up. It only does this on custom ROMs. So, I would like to be able to get these updates...not sure if I am making sense or not. Since Kies is such an incredibly horrible piece of software, I was hoping there was another way I could update my phone?????
Got ya, you should be able to use Odin to install the stock ROM. I think it's Sam Mobile? that you can register at and get the latest stock firmware. Again, search for the best way but it's doable.
I'm sure this has been asked many times before, but I just wanted to make absolutely sure I'm ready before I flash, so I don't brick my phone. I have been reading the forums for a few days now. I have an S3 (i747M) with Fido. I'm not totally sure which ROM to go with. From what I understand so far, I'm thinking StockMOD or Dandroid. I want a fairly minimalistic OS, latest version (4.3 vs 4.4?), so I can play the occasion game on it and get good idle battery life. I believe I have rooted my stock rom and I have disabled some of the bloat through the "Application Management" option under settings. Any advice on flashing? I have spent many years building, modding and generally tinkering with windows pcs but I haven't done anything with phones, android or linux. Any advice? Obviously do the backup of my current phone with the app mentioned on the related ROM installation page. I assume I can restore my phone back to this stock ROM is the new one fails? After the backup, do a full phone wipe and default restore. Then hook the phone to my PC via USB and use the related program to flash the phone? Thank you for any and all replies in advance. :good:
Kwijybow said:
I'm sure this has been asked many times before, but I just wanted to make absolutely sure I'm ready before I flash, so I don't brick my phone. I have been reading the forums for a few days now. I have an S3 (i747M) with Fido. I'm not totally sure which ROM to go with. From what I understand so far, I'm thinking StockMOD or Dandroid. I want a fairly minimalistic OS, latest version (4.3 vs 4.4?), so I can play the occasion game on it and get good idle battery life. I believe I have rooted my stock rom and I have disabled some of the bloat through the "Application Management" option under settings. Any advice on flashing? I have spent many years building, modding and generally tinkering with windows pcs but I haven't done anything with phones, android or linux. Any advice? Obviously do the backup of my current phone with the app mentioned on the related ROM installation page. I assume I can restore my phone back to this stock ROM is the new one fails? After the backup, do a full phone wipe and default restore. Then hook the phone to my PC via USB and use the related program to flash the phone? Thank you for any and all replies in advance. :good:
Click to expand...
Click to collapse
in my opinion or anyone will say that 4.3 is the most stable right now, and 4.4 is only available for CM based roms.....Samsung Touchwiz will always be the last to update their devices to 4.4 while custom roms AOKP, SLIM BEAM, PAC ROM, BEAN STALK, CM, PARANOID, ETC they will always have nightlies on latest the Android version but will take sometime for stable roms to be released
1st before you think of flashing please research and know what you're getting into
2nd read all the info. ROOT your i747m with cf-auto root (i recommend it cuz its the simplest, easiest, safest way to root)
3rd install custom recovery there are two that i know of but am confident and comfortable with clockworkmod recovery....u can try TWRP
4th yu can either wish to stay stock touchwiz, 2types of stock
-one that comes from samsung all bloated and no tweaks and
-the one that is taken by devs debloated, modded, customized, xposed mod, minimalistic, faster and better.
--OR you can go completely Android vanilla stock, which has nothing but the normal google staff (ITS LIKE A NEXUS DEVICE from Google) you dont have any bloatware, or features/addons just plain stock
5th Once yu know the basic, the universe is yours, with Android comes endless customization and possibilities just like Microsoft Windows, Linux, ubuntu or even OSX
6th wish to become a DEV its your choice, wish to modify, play with the filesystem its your choice but without knowledge of what you're doing bricking is easy as just deleting a file yu think its not important
7th help the rest with android as you do with PC
PS am learning to code now but one thing at a time so am starting with Web design, plan to learn some computer languages, hacking, etc computer science :laugh: maybe yu can help me out
everything you need to know about what i said or root http://forum.xda-developers.com/showthread.php?t=1725839
Thanks for the reply. It's been a while since I originally posted this. I decided to hold off on a custom ROM at that time but I find myself back again, still wanting to customize my phone (especially now that my contract is about to expire). I figure that if I do brick my phone beyond repair, I'll just get another phone anyways so not so worried about it now.
Anyways, one concern I have about flashing a custom ROM on my S3 is can I go backwards in Android versions? I can confirm that I am running the stock (Rogers / Fido) Android 4.4.2 which I believe is Kitkat? I am very interested in going either StockMOD or Dandroid, which as far as I can tell are 4.3 Jellybean? Can I do that?
Yes, you can run a 4.3 rom on your phone as long as you do not try to downgrade the bootloader.
You can go back to completely stock Rogers by using Odin to flash as stock kk rom from sammobile.com.
audit13 said:
Yes, you can run a 4.3 rom on your phone as long as you do not try to downgrade the bootloader.
You can go back to completely stock Rogers by using Odin to flash as stock kk rom from sammobile.com.
Click to expand...
Click to collapse
Thanks for the reply. Regarding the bootloader, the versions of Android I'm looking to install say they need the 4.3 bootloader. How can I check which bootloader I am running on my phone?
If you're phone is running stock Rogers kit kit, you have a kit kat bootloader which you can't downgrade.
If the rom needs a 4.3 bootloader and since you have a newer bootloader, you can probably load the rom.
Kwijybow said:
I'm not totally sure which ROM to go with.
Click to expand...
Click to collapse
Using the most recent build of the most popular ROM has it's advantages.
cm-12.1-20150807-NIGHTLY-d2att.zip
fast, light, stable, secure, supported
Hey guys! This might sound noobish, but i really never flashed, rooted, or anything on a droid/etc before. So atm I bought a galaxy s4 for my dad, and tried unlocking this stupid phone, but unlocking thru the dialer didnt work(couldnt even get *#27663368378# to work, when using *#0011#, still couldnt do anything.) All i know about it, is that it recognizes the European sim card, but the simple mobile(usa) sim card doesnt recognize, can't make calls, etc, as when you try to make a call it says "cant register to network" or w.e. So i was wondering what should I do? Do i need to flash the modem? rom? Root it? I want it to be able to work in global, in usa and euro.
On another note, I got my other phone that's on ver 4.2.2. Should i try upgrading my modem/baseband from mdl to nb4? Anything new with the new modem or anything i should update? Since i cant update OTA anymore on my 4.2.2. lol. Any suggestions would be awesome Tell me from your point of you, is it better to stay at 4.2.2? or just get the 4.4.2, and should i root my phone? Any vernabilities/security problems if done?
I found this: http://forum.xda-developers.com/showthread.php?t=2780006
Samsung Galaxy S4 M919 T-mobile
ROM: M919UVUFNB4
4.4.2 kitkat
Den Den said:
Hey guys! This might sound noobish, but i really never flashed, rooted, or anything on a droid/etc before. So atm I bought a galaxy s4 for my dad, and tried unlocking this stupid phone, but unlocking thru the dialer didnt work(couldnt even get *#27663368378# to work, when using *#0011#, still couldnt do anything.) All i know about it, is that it recognizes the European sim card, but the simple mobile(usa) sim card doesnt recognize, can't make calls, etc, as when you try to make a call it says "cant register to network" or w.e. So i was wondering what should I do? Do i need to flash the modem? rom? Root it? I want it to be able to work in global, in usa and euro.
On another note, I got my other phone that's on ver 4.2.2. Should i try upgrading my modem/baseband from mdl to nb4? Anything new with the new modem or anything i should update? Since i cant update OTA anymore on my 4.2.2. lol. Any suggestions would be awesome Tell me from your point of you, is it better to stay at 4.2.2? or just get the 4.4.2, and should i root my phone? Any vernabilities/security problems if done?
I found this: http://forum.xda-developers.com/showthread.php?t=2780006
Samsung Galaxy S4 M919 T-mobile
ROM: M919UVUFNB4
4.4.2 kitkat
Click to expand...
Click to collapse
To unlock your dad's phone the guide you linked to should do what you need done.
As far as your phone still on MDL, you should be able to use the old method through the service menu to unlock if that's what you wanted to do. You can update your modem/baseband if you desire, although if you're staying on stock 4.2.2 TouchWiz there is really no need to. It's only when you flash ROMs based on 4.3 and above that you run into issues using the MDL modem/baseband.
To add to lordcheeto's post, there's a difference between MDL bootloader and the MDL modem. When the S4 was released with Android 4.2 it had an unlocked bootloader (MDL), but with Android 4.3 and 4.4 Samsung included new security software called Knox. Knox doesn't prevent rooting, but if you flash a custom recovery such as CWMR, TWRP, or Philz Touch then a security flag will be irreversibly tripped which voids your warranty. Because this Knox software is tied into the bootloader, developers found a way around it by extracting the modems from 4.3 (MK2) and 4.4 (NB4) firmwares which allows us to keep our MDL bootloader and still use 4.2, 4.3, and 4.4 roms. The advantages are that we keep our warranty and we're able to use any 4.2+ rom. We can downgrade and upgrade easily while Knox phones can't.
lordcheeto03 said:
To unlock your dad's phone the guide you linked to should do what you need done.
As far as your phone still on MDL, you should be able to use the old method through the service menu to unlock if that's what you wanted to do. You can update your modem/baseband if you desire, although if you're staying on stock 4.2.2 TouchWiz there is really no need to. It's only when you flash ROMs based on 4.3 and above that you run into issues using the MDL modem/baseband.
Click to expand...
Click to collapse
Should i keep the 4.4.2 kitkat thats not working with my usa sim card atm? Or should i flash it to 4.2.2. ADL? If having 4.2.2 is better doing that guide i put link to above, then give me a good tut on doing it, need to do it today xD THanks in Advance!
HampTheToker said:
To add to lordcheeto's post, there's a difference between MDL bootloader and the MDL modem. When the S4 was released with Android 4.2 it had an unlocked bootloader (MDL), but with Android 4.3 and 4.4 Samsung included new security software called Knox. Knox doesn't prevent rooting, but if you flash a custom recovery such as CWMR, TWRP, or Philz Touch then a security flag will be irreversibly tripped which voids your warranty. Because this Knox software is tied into the bootloader, developers found a way around it by extracting the modems from 4.3 (MK2) and 4.4 (NB4) firmwares which allows us to keep our MDL bootloader and still use 4.2, 4.3, and 4.4 roms. The advantages are that we keep our warranty and we're able to use any 4.2+ rom. We can downgrade and upgrade easily while Knox phones can't.
Click to expand...
Click to collapse
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Den Den said:
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Click to expand...
Click to collapse
I thought the answers given were pretty clear... I'm actually confused about what phone you're asking about, and if there are, in fact, 2 different phones in question... My answer will be a bit lengthy, but I hope that you can put 1 and 2 together and apply the information I am about to type to your particular situation: Also, I'm not trying to be a ****, just concise.
In reference to the S4 that is on 4.4.2 (NB4) firmware: The unlock method which you posted SHOULD enable the device to use different SIM cards and function in "euro" and "usa." That includes making calls and using "date" (data?) as you mentioned. As far as your question on reverting that particular device: There is no way whatsoever to downgrade the firmware on a device running either stock 4.3 (MK2) or stock 4.4.2 (NB4) obtained by flashing via Odin, Kies, or OTA; so that idea can be forgotten about. The unlock method, from what I gather, simply reverts the modem and allows you to use the old unlock method. then returns the modem to NB4. It does not touch the firmware, bootloader, or anything other than the modem/baseband.
For whichever device this applies to: there should be no need to root either to accomplish either goal. If you wish to root, then I can point you in the right direction; otherwise, if you haven't needed it so far and don't foresee needing it in the future, I say don't worry about it.
As for the device running 4.2.2: if you have had no troubles with reception, then there is no need to update your modem/baseband. There are really only 2 times that updating your modem would come in handy. 1: If you are having reception problems, or 2: If you plan on keeping your bootloader at MDL AND using custom ROMs 4.3 and above. The benefit of this scenario is that keeping your bootloader on MDL means that your device does not have the KNOX-implemented bootloader and can easily be reverted to a completely stock state for warranty purposes yet you still get to have the most up-to-date version of Android. If neither of those conditions apply to you, then there is really no real need to update your modem.
Den Den said:
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Click to expand...
Click to collapse
The guide you posted should work just fine. Just follow the instructions.
Also, I left out one of the most important parts of having the modems extracted from the 4.3 and 4.4 firmwares. The reason for extracting the modems is so that we can flash them separately from the official firmware which would upgrade us to a Knox bootloader. Using the 4.2 modem with 4.3 and 4.4 roms causes data and sound issues that make the phone pretty much unusable. The same goes for using the 4.3 modem with a 4.4 rom. With the extracted modems we can flash them separately for whatever Android version we're using and have full functionality and retain the MDL bootloader and all it's perks.
If you use a 4.2 rom, you'll need to make sure to flash the MDL modem with it.
For 4.3 roms, you'll need to be on MK2 modem.
4.4 roms require NB4 modem.
As long as you don't update to official 4.3 or 4.4, you'll be able to use any version rom you want according to your preference. Personally, I use 4.4 roms, but it's nice to have the option to go back to 4.2 if I want to. Once you SIM unlock, it should stick between all versions. You should be able to flash any rom that you want without having to worry about going through that process again.
lordcheeto03 said:
I thought the answers given were pretty clear... I'm actually confused about what phone you're asking about, and if there are, in fact, 2 different phones in question... My answer will be a bit lengthy, but I hope that you can put 1 and 2 together and apply the information I am about to type to your particular situation: Also, I'm not trying to be a ****, just concise.
In reference to the S4 that is on 4.4.2 (NB4) firmware: The unlock method which you posted SHOULD enable the device to use different SIM cards and function in "euro" and "usa." That includes making calls and using "date" (data?) as you mentioned. As far as your question on reverting that particular device: There is no way whatsoever to downgrade the firmware on a device running either stock 4.3 (MK2) or stock 4.4.2 (NB4) obtained by flashing via Odin, Kies, or OTA; so that idea can be forgotten about. The unlock method, from what I gather, simply reverts the modem and allows you to use the old unlock method. then returns the modem to NB4. It does not touch the firmware, bootloader, or anything other than the modem/baseband.
For whichever device this applies to: there should be no need to root either to accomplish either goal. If you wish to root, then I can point you in the right direction; otherwise, if you haven't needed it so far and don't foresee needing it in the future, I say don't worry about it.
As for the device running 4.2.2: if you have had no troubles with reception, then there is no need to update your modem/baseband. There are really only 2 times that updating your modem would come in handy. 1: If you are having reception problems, or 2: If you plan on keeping your bootloader at MDL AND using custom ROMs 4.3 and above. The benefit of this scenario is that keeping your bootloader on MDL means that your device does not have the KNOX-implemented bootloader and can easily be reverted to a completely stock state for warranty purposes yet you still get to have the most up-to-date version of Android. If neither of those conditions apply to you, then there is really no real need to update your modem.
Click to expand...
Click to collapse
That Makes sense...just trying to grasp info. on everything so it's more clearer ;p and thanks for correcting me, yea it was data lol.
HampTheToker said:
The guide you posted should work just fine. Just follow the instructions.
Also, I left out one of the most important parts of having the modems extracted from the 4.3 and 4.4 firmwares. The reason for extracting the modems is so that we can flash them separately from the official firmware which would upgrade us to a Knox bootloader. Using the 4.2 modem with 4.3 and 4.4 roms causes data and sound issues that make the phone pretty much unusable. The same goes for using the 4.3 modem with a 4.4 rom. With the extracted modems we can flash them separately for whatever Android version we're using and have full functionality and retain the MDL bootloader and all it's perks.
If you use a 4.2 rom, you'll need to make sure to flash the MDL modem with it.
For 4.3 roms, you'll need to be on MK2 modem.
4.4 roms require NB4 modem.
As long as you don't update to official 4.3 or 4.4, you'll be able to use any version rom you want according to your preference. Personally, I use 4.4 roms, but it's nice to have the option to go back to 4.2 if I want to. Once you SIM unlock, it should stick between all versions. You should be able to flash any rom that you want without having to worry about going through that process again.
Click to expand...
Click to collapse
So If i was on 4.3, and it updated to 4.4.2 kitkat, means it went to the official update eh? As "lordcheeto03" said that once u go to 4.3 or 4.4.2 you cant go back to 4.2, the menu options and w.e go updated, the "about me" is now yellow, the top border of the phone is grey, etc. The new security is enforcing, I guess I'll try the guide i found, hope i don't do anything stupid or skip a step(usually doesn't happen) but feels kinda weird doing things the first time.
On another note, if a phone bricks or in a loop, etc can it be solved? So i still have hope if something goes wrong xD
edit: The guide i link that i found, it works for all m919 models? Since i got t-mobile, not sure if all models(tmobile, att, etc) have the same modem, wouldnt want to brick cuz of not flashing the correct file, w.e(disregard this, i forgot i posted in the t-mobile section, man sometimes i feel like an idiot because i dont double check xD)
Den Den said:
So If i was on 4.3, and it updated to 4.4.2 kitkat, means it went to the official update eh? As "lordcheeto03" said that once u go to 4.3 or 4.4.2 you cant go back to 4.2, the menu options and w.e go updated, the "about me" is now yellow, the top border of the phone is grey, etc. The new security is enforcing, I guess I'll try the guide i found, hope i don't do anything stupid or skip a step(usually doesn't happen) but feels kinda weird doing things the first time.
On another note, if a phone bricks or in a loop, etc can it be solved? So i still have hope if something goes wrong xD
edit: The guide i link that i found, it works for all m919 models? Since i got t-mobile, not sure if all models(tmobile, att, etc) have the same modem, wouldnt want to brick cuz of not flashing the correct file, w.e(disregard this, i forgot i posted in the t-mobile section, man sometimes i feel like an idiot because i dont double check xD)
Click to expand...
Click to collapse
Once you hit 4.3, you lost your ability to downgrade. You can upgrade, but you can't go back. Rest easy, as long as you can get into download mode, you can recover your device. Bootloop, soft brick, whatever; as long as Power + volume down brings you to download mode everything is still OK. Just read the directions a few times.. get used to the idea of what's going on, double check and make sure you have the right software and files, and jump in. You'll do fine. Even after years of jailbreaking iphones and rooting Droids, I still get nervous whenever I have to fire up Odin; but just remember... many many others (more than have posted in that thread for sure) have done the same thing you're about to do, so as long as you follow the directions you will be fine!
lordcheeto03 said:
Once you hit 4.3, you lost your ability to downgrade. You can upgrade, but you can't go back. Rest easy, as long as you can get into download mode, you can recover your device. Bootloop, soft brick, whatever; as long as Power + volume down brings you to download mode everything is still OK. Just read the directions a few times.. get used to the idea of what's going on, double check and make sure you have the right software and files, and jump in. You'll do fine. Even after years of jailbreaking iphones and rooting Droids, I still get nervous whenever I have to fire up Odin; but just remember... many many others (more than have posted in that thread for sure) have done the same thing you're about to do, so as long as you follow the directions you will be fine!
Click to expand...
Click to collapse
Thanks for the reply, now I'm all fired up and ready to do this I'll post back here when i'm done and see how it went xD
Edit: Can i ask you a favor? Could you get me the "M919UVUFNB4_M919TMBFNB4_TMB.zip" modem file and "M919UVUAMDL_M919TMBAMDL_TMB.zip", i think that's what the tutorial link i posted is asking for. But the files r huge, 1.6gb, etc, would take me 3hrs+ each for each file to download just to extract the modem =/ If that's the only thing i need.
found these links: http://rapidgator.net/file/59487dc515500a0430ddaddc780fa555/TMB-M919UVUFNB4-20140314115123.zip.html
and : http://terafile.co/32d149264215/M919UVUAMDL_M919TMBAMDL_TMB.zip
Not sure if they are safe to use or not, not everything on the net is...plus they r huge files =/
Den Den said:
Thanks for the reply, now I'm all fired up and ready to do this I'll post back here when i'm done and see how it went xD
Edit: Can i ask you a favor? Could you get me the "M919UVUFNB4_M919TMBFNB4_TMB.zip" modem file and "M919UVUAMDL_M919TMBAMDL_TMB.zip", i think that's what the tutorial link i posted is asking for. But the files r huge, 1.6gb, etc, would take me 3hrs+ each for each file to download just to extract the modem =/ If that's the only thing i need.
found these links: http://rapidgator.net/file/59487dc515500a0430ddaddc780fa555/TMB-M919UVUFNB4-20140314115123.zip.html
and : http://terafile.co/32d149264215/M919UVUAMDL_M919TMBAMDL_TMB.zip
Not sure if they are safe to use or not, not everything on the net is...plus they r huge files =/
Click to expand...
Click to collapse
These files include modem.bin that is required... I'm not sure why the OP linked to the entire firmware instead of just those links, but anywho...
The NB4 modem can be found in this thread. It's only ~20MB.
The MDL modem is in this thread. It is ~25MB.
Also, quote me instead of just replying to the thread. I'll respond quicker
lordcheeto03 said:
These files include modem.bin that is required... I'm not sure why the OP linked to the entire firmware instead of just those links, but anywho...
The NB4 modem can be found in this thread. It's only ~20MB.
The MDL modem is in this thread. It is ~25MB.
Also, quote me instead of just replying to the thread. I'll respond quicker
Click to expand...
Click to collapse
Flashed ADL using odin, somehow got the menu to work(couldnt budge for some reason to umts), went thru all the steps, it rebooted, put it back to download mode, and flashed it back to nb4. Put my simplemobile simcard in, still nothing, am I supposed to put a different sim card in like ATT or something for it to work? Confused why it didnt work, yet it still detects the MTC european version simcard(not in service, but it had a pin set on it, so it always asks you to unlock the sim with the sim pin u put on it to view ur files on it, etc). Am i doing something wrong? I could give you more info on the phone...
Edit: Just checked on Swappa.com of my imei and got this =/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nvm, Looks like i think its blocked on Tmobiles network, but i put in the H2O sim and it worked.(under ATT) phew....
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
I know that a lot of people are gonna say to read several other similar threads, but having gone through all of that I still don't get it.
THE SITUATION:
My Samsung Galaxy Note 2 GT-n7100 is :
1) Stock Android 4.1.2 Rooted
2) Modified with Xposed
3) TWRP (Latest, updated regularly)
4) Never been updated ever. Like never ever.
THE A-HOLE PROBLEM:
I honestly never bothered to flash anything on my note 2, since I have all the stuffs working perfectly as it is. Until the god-damn son of a gun WIFI started acting like a sissy she-dog. The problem is that the WIFI keeps on disconnecting itself and reconnecting itself automatically, wierdly enough, only when an app tries to access it. I hope everyone can understand how horrible it is, especially when you are talking dirty to your girlfriend over a whatsapp call and it keeps dropping, just like my errection.
All jokes aside, this has been driving me mad. In-case you need the details, here is what I did to solve my annoying problem :
1) Factory reset.
2) Reboot.
3) Phone works fine. Wifi works fine. Does not disconnect or reconnect. Seems like problem solved.
Then, the camel-crap happens.
4) Open Google play store, it updates. Play services updated. Need it to access the google services.
5) Open any internet enabled app.
6) Wifi switches on/off automatcally.
7) I tear my gonads off.
Side-Note : I also turned off the wifi power saving mode using *#0011#. I also made all the necessary changes in the wifi settings menu.
THE QUESTION:
Since I have never updated, my bootloader, etc are still stock. I read a thread that if I dont update the bootloader, future flashing will not work. I have no earthly clue so as to what the heck am I supposed to do.
I need some simple directions, to the point if possible. I have taken a full nandroid backup, just to be safe.
I think only a CFW now can solve this weird problem of mine. So, any help will be appreciated.
Newer roms require up-to-date bootloaders and modems. The easiest way to update both would be to flash the latest stock ROM from sammobile.com in Odin. Make sure you back up your data before flashing.
audit13 said:
Newer roms require up-to-date bootloaders and modems. The easiest way to update both would be to flash the latest stock ROM from sammobile.com in Odin. Make sure you back up your data before flashing.
Click to expand...
Click to collapse
Okay. But, what about the filthy Knox ? Also, what about my root? Also, what about Knox ? Hmm, I wrote knox twice. Now, thrice.
Simply put, knox is poo. I dont want that. So, how do I get the latest knick-knacks without knox. Is it possible to flash the latest bootloader, modem etc.
Sorry for using "noobish". I hate that language too, but when it comes to 40k phones, I get a bit nervous. Hope you can help. Or someone else.
Regards,
TheBasterd.
If you flash the latest bootloader, you'll get Knox.
Personally, I have never found Knox to interfere with flashing custom ROMs.
audit13 said:
If you flash the latest bootloader, you'll get Knox.
Personally, I have never found Knox to interfere with flashing custom ROMs.
Click to expand...
Click to collapse
So, here is the thing. If I go here : http://forum.xda-developers.com/galaxy-note-2/development/rom-resurrection-remix-5-6-0-t3278709 and downloaded the ROM, did all the stuff the ROM maker says and flash it.
Without the latest bootloader and other poo, you are saying that my flash will be unsuccessful ?
That ROM will probably need an updated bootloader and modem to connect to a cell network, detect a sim, and wifi.
If you want to, you can flash the ROM and see what happens.
audit13 said:
That ROM will probably need an updated bootloader and modem to connect to a cell network, detect a sim, and wifi.
If you want to, you can flash the ROM and see what happens.
Click to expand...
Click to collapse
Hey audit, thanks for sticking around and helping me bro. I really appreciate that.
So, I took your advice and have put the ROM from Sammobile.com for the latest bootloader and the modem stuffs.
Hope that will work. Also, when I flash the ROm, wont I loose my root ?
Yes, you'll lose root but it doesn't matter if you don't intend to use a stock ROM.
audit13 said:
Yes, you'll lose root but it doesn't matter if you don't intend to use a stock ROM.
Click to expand...
Click to collapse
Allright ! That was easy. Done and done. Thanks audit. (Thanks hitted)
Now, I will ensure a painless future for all noobs like me by making a tutorial. This thread can be marked as fixed. Thanks audiot bro.
It's great that you resolved the issue.
We're all here to help and learn from each other.