So my ATT S3 has completely lost sound. I updated the bootloader to the latest 4.3 leak, the modem, and then I installed a 4.4.2 rom (currently on OMNI, but I've gone flash happy the past few days trying to fix the sound, no chance).
I can't downgrade my bootloader, and for some reason ODIN is not working for me. Am I missing something?
Related
Hello all,
So, I've been doing some reading in regards to some problems I ran into when installing KK on my device (even though it's currently running CM11 nightly without any noticeable issues ) and I noticed that my device has something that for my understanding should not have worked: I'm still on the I747MVLDLK4 bootloader and was able of getting the latest CM11 nightly running without issues on the device.
Granted that the device's modem is updated to the latest version, but for what I've read that it should have never boot up onto any KK ROM. I've been able of getting SlimKat, AOKP and CM11 running on it, even though CM11 was the only one that didn't give me any FC's or any unwanted behavior. I must admit that getting any of these ROM installed required quite a bit of messing around in TWRP and had to do complete wipes between installing versions, but still, it worked. I also had JB 4.3 installed ( AOKP ) since around October/2013 and upgraded to KK about 1 month ago.
I have a couple of questions in regards to this:
- If the KK ROM's are not supposed to boot up on such an old bootloader, what did I do that would've overrun this?
- Since I'm still on I747MVLDLK4 bootloader, would I be able of downgrading to 4.1.1? ( I want to perform the device unlock for free, which only is available on that version)
I've added screenshots of the bootloader info on the console emulator and the system info...
Thanks in advance!
The 4.3 requirement is only for touchwiz kk roms.
So to start I went from my s3 to the Z2 when it first came out. I am with bell and for some reason they are not supporting updates and my Z2 is ridiculously glitchy, i'm looking to update the firmware and expect to take sometime to do this and i dont like downtime. Due to some legal reasons my old s3 was confiscated... so i picked up an S3 off kijiji. Unknown carrier but still I747M. I rooted, unlocked and ran cm on my old s3 so i figured i would give this one a rip and see what had come out.
Without thinking i found slimkat and rooted and updated to 4.4.4. Great rom, kind of glitchy, but smooth.
And then i through my sim in... didn't work. So i started trying to unlock it. And my quest begins
I have CM11 boot
I tried the easy modem dialer fix. didnt work
I tried the sim generator, couldn't find my nv data bin file
I then tried downgrading to 4.3 and 4.1.1 stock roms and also mod roms didn't work. Got them off of sammobile and also xda as the sammoblie one didn't work.
What are my options? should i just put this s3 back into the realm of kijiji?
Any help would be appreciated
I picked up a used AT&T S3 here in NY because I just installed an Alpine ICS-X7HD in my car. The S3 had the latest NJ1 installed. I was able to root the phone OK. My research has lead me to believe that I won't be able to get any version of Drive Link running on Android 4.4 without FCing when connecting to the Alpine Unit. Research also seems to suggest that I can't go back to the LK3 version either due to boot loader changes made from Samsung and AT&T with the 4.3 update. So I'm looking for advice from the forum experts on what I can do, if anything to get the phone downgraded to a Jelly Bean firmware. I am hoping to hear from someone who has been able to do this before. Can I go from 4.4.2 to 4.3? If so does Drive link still work for you?
I am comfortable using Odin and adb. Let me know if you need any other specific information.
The solution was so incredibly simple. I flashed the AT&T+UCMG2.ZIP through TWRP and rebooted. Now I am on 4.1.2. Drive Link working! So To Recap...I went from 4.4.2 NJ1 back to 4.1.2 and stayed on NJ1 baseband.
Dbeayon said:
I picked up a used AT&T S3 here in NY because I just installed an Alpine ICS-X7HD in my car. The S3 had the latest NJ1 installed. I was able to root the phone OK. My research has lead me to believe that I won't be able to get any version of Drive Link running on Android 4.4 without FCing when connecting to the Alpine Unit. Research also seems to suggest that I can't go back to the LK3 version either due to boot loader changes made from Samsung and AT&T with the 4.3 update. So I'm looking for advice from the forum experts on what I can do, if anything to get the phone downgraded to a Jelly Bean firmware. I am hoping to hear from someone who has been able to do this before. Can I go from 4.4.2 to 4.3? If so does Drive link still work for you?
I am comfortable using Odin and adb. Let me know if you need any other specific information.
Click to expand...
Click to collapse
How did you root on Nj1??!
To get to jelly bean, you do the hack like method above by flashing a zip in TWRP or Clockwork mod or boot a custom rom based off 4.1.x. Once you are on 4.3 or 4.4, there is no going back to a previous version, attempts result in bricking.
It's been a while since I flashed a rom. I thought I would play around with some ROM's today, but I'm getting overwhelmed by the contradictory information out there, regarding bootloaders,wifi patches, kernel flashes etc. Not that it's misinformation, but I just don't know if it's implied that the bootloader on the install instructions have been updated to 4.1.2 or higher before moving forward with flash.
I'm on a rooted T-mo/T889 Galaxy Note 2 with stock 4.1.1 and UVALL4. I flashed TWRP on it a few months ago, when I was looking into installing DN3 rom.
It seems to me that the instructions for installing DN4 (which is what I'm looking at today) might assume my device is updated to latest firmware.
So I'm wondering where to start. Do I need to update bootloader, or can I just move forward with electronteam's install instructions flash DN4 with addon patch? Or even more broader terms, can I flash a 4.4.4 + rom from a 4.1.1 firmware?
lyinelriche said:
It's been a while since I flashed a rom. I thought I would play around with some ROM's today, but I'm getting overwhelmed by the contradictory information out there, regarding bootloaders,wifi patches, kernel flashes etc. Not that it's misinformation, but I just don't know if it's implied that the bootloader on the install instructions have been updated to 4.1.2 or higher before moving forward with flash.
I'm on a rooted T-mo/T889 Galaxy Note 2 with stock 4.1.1 and UVALL4. I flashed TWRP on it a few months ago, when I was looking into installing DN3 rom.
It seems to me that the instructions for installing DN4 (which is what I'm looking at today) might assume my device is updated to latest firmware.
So I'm wondering where to start. Do I need to update bootloader, or can I just move forward with electronteam's install instructions flash DN4 with addon patch? Or even more broader terms, can I flash a 4.4.4 + rom from a 4.1.1 firmware?
Click to expand...
Click to collapse
You're good to go with DN4... just flash Dn4 and addon. The only thing is, Dn4 has issues with GPS. So, if you need/use this often, you may want to stick with DN3. Oh yeah, update your TWRP to newest (2.8.5.0) since it's been a few months since you installed it. And after you get it set up, update to the newest Agni kernel... http://forum.xda-developers.com/showthread.php?t=2602053
Thanks.
I went ahead with DN4, and sure enough, I have no GPS.
A more troubling issue I'm having is that my data/phone signal just randomly gone. I live in a city with LTE , and have no coverage issues here. Sometimes a restart will remedy it, but only for a short while. I'm going to flash this Latest Agni, Maybe that will fix it. EDIT: Nope, still happening. Changing Network Mode back and forth between LTE and WCDMA/GSM seems to be easier than rebooting though.
I was happily using 4.4.2 stock on my rooted SGH-i747M, however rooting it tripped the warranty bit, then I had the phone unlocked and changed carriers from Rogers to Bell and because of either of those my device is blacklisted from getting OTA updates.
I decided to try CM and was advised on the CM IRC channel to update the modem firmware first. I updated (or perhaps downgraded?) to I747MUMUEND3 per this thread (http://forum.xda-developers.com/showthread.php?t=1831898) and rebooted but found that I no longer had sound or WIFI and the SIM card wasn't detected. I tried other versions from that same thread with no luck.
I went ahead and flashed CM 12.1 nightly for D2ATT which worked well, however still no sound or SIM. WIFI works but slowly. I also tried 11.2 for D2LTE but got the same result, and flashing 10.1 for D2ATT gave me an assert error. In 12.1 I experimented with other modem firmware versions (I747MVLUEMK5, I747MUMUEND3, I747MVLUEND2) but it made no difference.
I'm not quite sure where to go from here. According to a CM12.1 debug log my boot loader is I747MVLUFNF2. Do I need to match the modem firmware version with this, and if so, where can I get this version? Would flashing stock from sammobile do it, would I lose root while doing so, and how can I get root back? I forget how I rooted it originally but soft bricked it but fixed it with chainfire.
Anything else I can try at this point? I might just be happy back on stock with cellular connectivity.
The latest modem for the i747m is FOB1. The END2 modem is about a year behind the FOB1.
The assert error occurred because d2lte or d2can ROMs are to be flashed to the i747m.
Fixed
I flashed the stock ROM that matched up with my current bootloader version. Inside the stock ROM everything worked as normal. I then installed TWRP and flashed 12.1 and everything worked in there as well.