I just joined in the past few days because I decided to try different ROMs on my i747. This is my 1st ever post, and I thought I'd try out this rooting and flashing that I'm missing out on.
First of all, THANKS to EVERYONE that posts here for all of the help given to me and that others have used. Nice to see people helping out other people in such ways.
Second, I have successfully put a few different ROMs on my i747 over the past few days and can't believe how easy it was. I was always scared to do it. I decided since the thing was just sitting in a drawer not being used "What's the risk?"
Third, my actual issue...No matter what ROM I have on the i747, it will not connect to Wi-Fi at my work. FYI, I work (in IT ironically) in a very large company with hundreds of access points around the campus. So I know it is not the network, as we would have others with the same issue. It connects to all other (that I've tried so far) Wi-Fi networks with no issues.
I just don't understand all the terms bootloader, firmware, kernel, modem etc. I read decriptions (on here) trying to explain and I just can't grasp it.
I was on stock with whatever the last OTA update from AT&T was. I updated the boatloader (I believe) from NE4 to NJ1 to NJ2 using this thread. At least, I'm assuming I did it right. Nothing failed and the Phone Info app looks like it worked. https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
Anyone can give me any tips on what I need to do to possible get this working? It's not really a huge deal breaker, it's just bugging me as to why it isn't working.
Thanks in advance!
You upgraded the modem/baseband software when updating the bootloader?
audit13 said:
You upgraded the modem/baseband software when updating the bootloader?
Click to expand...
Click to collapse
I'm guessing no. How do I do that? Don't want to brick it.
I found this link, but what firmware am I on? How do I tell?
https://forum.xda-developers.com/galaxy-s3-att/general/modem-4-4-2-modems-i747-i747m-t2856577
Did you flash the zip or did you flash aboot.mbn? If you flashed the zip, the bootloader and modem would have been updated at the same time.
audit13 said:
Did you flash the zip or did you flash aboot.mbn? If you flashed the zip, the bootloader and modem would have been updated at the same time.
Click to expand...
Click to collapse
I flashed the zip.
So an unrooted stock ROM also refuses to connect?
audit13 said:
So an unrooted stock ROM also refuses to connect?
Click to expand...
Click to collapse
I don't know how to go back to stock.
Related
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
ive tried odin and try reflashing back to stock but odin failed
ImJusDatGuy said:
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
Click to expand...
Click to collapse
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
ImJusDatGuy said:
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
Click to expand...
Click to collapse
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
dawgdoc said:
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
Click to expand...
Click to collapse
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
ImJusDatGuy said:
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
Click to expand...
Click to collapse
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
dawgdoc said:
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
Click to expand...
Click to collapse
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
ImJusDatGuy said:
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
Click to expand...
Click to collapse
thanks man for telling me what was wrong your an amazing human being and i love you (no homo) and thanks again a million thanks bro.
Did that modem fix some of the problems?
If your on 4.1.1 shouldn't you flash the DKL3 version or can't you just flash thru Odin the DLK3 stock ROM thru Odin Amd start all over again
I've been on 4.3 with that bootloader Amd have flashed back to 4.1 back to the baseband version DLK3 firmware. I would think being on 4.1 you should be able to reflash using Odin to fix the issue or flash the modem for 4.1 .
okay so I understand that wifi is the kernel problem
and a lot of people are having problem with the wifi after FNE4 update
but so far I've looked around and couldn't find any fix, or one that does not guarantee on an AOSP rom so please help =)
this is what i did
I was on MJB and flashed this 4.4.2 from http://forum.xda-developers.com/showthread.php?t=2788357
however, it did not update my bootloader to NE4, it stayed MJB, and I noticed Wifi wouldn't turn on on stock rom, so I flashed KT Kernel, but it did not fix the wifi problem.
So i thought it was just the stock rom problem, then i flashed PA 4.4.2 rom, which fixed half of the problem... can turn wifi on and off and there are wifi networks, but can't connect (though some time i got lucky and wifi connect, which is rarely)
so any way to fix?
Bumpz
Can you verify your current firmware build? Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you your current base firmware/bootloader version.
Have you considered updating to the full NE4 firmware?
DocHoliday77 said:
Can you verify your current firmware build? Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you your current base firmware/bootloader version.
Have you considered updating to the full NE4 firmware?
Click to expand...
Click to collapse
the current bootloader is FNE4, i just updated it yesterday and no hope either
currently on dpk kernel, Rom is AOSPA 7/9
Really not sure what could be the problem. Maybe this thread will help:
http://forum.xda-developers.com/showthread.php?t=2808654
Its for updating firmware via recovery, but maybe by refreshing it this way could help. Im thinking maybe something got messed up when you originally updated, and if so rewriting known good firmware could help.
Ask in thst thread before flashing though. I haven't looked at the file myself so im not sure if theres something I dont know about since they say to only flash if you're on MJB. If its a simple firmware flash it should be fine though. But like I said, ask first, just to be safe.
DocHoliday77 said:
Really not sure what could be the problem. Maybe this thread will help:
http://forum.xda-developers.com/showthread.php?t=2808654
Its for updating firmware via recovery, but maybe by refreshing it this way could help. Im thinking maybe something got messed up when you originally updated, and if so rewriting known good firmware could help.
Ask in thst thread before flashing though. I haven't looked at the file myself so im not sure if theres something I dont know about since they say to only flash if you're on MJB. If its a simple firmware flash it should be fine though. But like I said, ask first, just to be safe.
Click to expand...
Click to collapse
I already flashed that yesterday, and other than the bootloader/modem changed from MJB to NE4, nothing else changed
and of course still can't connect to any wifi network
i guess i'll pull the last trick.. back to stock and see
since the last time i flashed, even though the rom is tw4.4.2, but the bootloader remained MJB, so this time i'll go back to stock with NE4 and see how it'll go
Probably the best option at this point. Good luck and let me know if that finally solves it!
DocHoliday77 said:
Probably the best option at this point. Good luck and let me know if that finally solves it!
Click to expand...
Click to collapse
well my last ditch fixed the problem.. so it's all about the bootloader/modem with the incorrect rom
So you just flashed the stock rom, right? Thats still really odd. If you feel like continuing you could try flashing a different rom and whatever kernel is supposed to work for WiFi. Sometimes starting over at the beginning is all it takes...
DocHoliday77 said:
So you just flashed the stock rom, right? Thats still really odd. If you feel like continuing you could try flashing a different rom and whatever kernel is supposed to work for WiFi. Sometimes starting over at the beginning is all it takes...
Click to expand...
Click to collapse
indeed it's really odd.. now i'm back on aosp and for some reason, wifi works but sometimes it wouldn't at all.. so im thinking it's the wifi chip or the driver that is damaged..
These issues started with the upgrade to latest T-Mobile 4.3 software pack at the end of November. Phone operated perfectly before then. After the update, the phone would periodically not receive/place calls/texts/use data. The issue kept worsening daily. It is not related to the SIM card or location, as the card has been replaced and tested in an alternate phone where it performs perfectly.
The T999L was then consequently rooted, KNOX flagged (it's already past warranty, Samsung wouldn't give a rat's ass about it), flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted. Restored to stock 4.1.2, same issues. Did 3 updates OTA to get to latest 4.3, same issues.
Messed around with 4636 menu, 2263 menu, etc. Some changes had a temporary result but nothing permanent. Calls to the phone are redirected to voicemail. When placing a call, it takes 5-10 seconds to either place it or disconnect it (as it can't connect to the network, I guess?). The bars on the phone show 3-4 bars typically, but the phone is rarely able to acquire a data connection. Again, this is not the case with other phones the SIM is tried on.
Any suggestions? I've spent probably close to 10 hours researching this and trying everything out and I am absolutely stumped. This is my mom's phone and a replacement Alcatel OneTouch Fierce 2 just "doesn't look nice", so I'm getting a fair bit of *****ing for trying to help solve this, even though it's not my fault. Would appreciate some help before Christmas.
Have you tried updating the modem?
systemcode said:
Have you tried updating the modem?
Click to expand...
Click to collapse
flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted.
Click to expand...
Click to collapse
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
dwegiel said:
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
Click to expand...
Click to collapse
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
nirogu325 said:
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
Click to expand...
Click to collapse
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
dwegiel said:
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
Click to expand...
Click to collapse
Well, OTA updates can sometimes fail, that's why I gave you the ODIN firmware link. It's the best help I can offer.
Hi all, new comer to the S3 here but not new to flashing etc. I just wanted to get a few things straight before I went ahead.
1. I downloaded and used Mskip unified android toolkit. I rooted and flashed twrp recovery to my S3.
I am on I747UCALG1 4.0.4 and I just wanted to know if I can flash the 4.1.1 build ATT-I747UCDLK3 that I found here straight away in odin. I know some sammy phones are drama queens when it comes to new bootloaders etc. Will the new build update the bootloader or should I do this separately.
Or should I just download a rom from the development section and flash it in twrp or won't that work and I need to flash a new bootloader first then flash the newer roms.
Thanks for any help and yes I did search around but only found questions regarding downgrading.
Bro, remember my strong advice - don't go higher.
Battery life goes worse with every update. I wish I never did it.
But if you want to try something new, try OctOs
The problem I'm having right now is that my wifi keeps on scanning but does not find any networks although I am 2 feel from my router. This phone really was my Gfs that went crazy and I changed out the mainboard so I'm just running it as a back up.
Personally, I would flash stock 4.1.1 from sammobile.com and sim unlock the phone using the free method if the phone is sim locked. Once sim unlocked, I suggest running OTA updates until the phone is running the latest stock ROM. Once it is running the latest stock ROM, flash twrp, take a nandroid backup, and then flash a custom ROM if you want.
Note: once the phone is running the latest bootloader, you cannot downgrade the bootloader.
Would be hard to do an OTA since I cannot connect to any wifi networks.
if youre talking upgrading bootloader/modems , and cannont do as @audit13 suggests , and cannot connect to wifi or use/have enough data ; then i would suggest upgrading incrementally.
"err on the side of kindness"
Is wifi disabled on the phone?
audit13 said:
Is wifi disabled on the phone?
Click to expand...
Click to collapse
No it is on and scans for networks but it does not show any, even if I add a network manually it does not connect. I read somewhere that I need a newer bootloader in order for the wifi to work. Does anyone have the newest bootloader for me to flash and try this out on?
mrrocketdog said:
whats your current bootloader and modem.? if dont know u can download app called "samsung info" from play store that will tell.
heres the xda thread
http://forum.xda-developers.com/showthread.php?t=2609045
"err on the side of kindness"
Click to expand...
Click to collapse
"err on the side of kindness"
Do the last 4 characters of the modem match the last four characters of the bootloader?
For wifi to work properly, it is best to match the bootloader to the modem and vice versa.
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.