Hello.
I have the SGH-M919 with the following details:
Android version: 4.2.2
Baseband version: M919UVUEMK2
Kernel version: 3.4.0
Build number: M919UVUAMDB
This is after using various guides to rooting, getting rid of the SIM lock, changing the baseband version and reverting it.
Right now the phone works, I can make calls and the sound is fine. However, I can't turn Wi-Fi on. Thus, I have a few questions:
Is there a way to fix Wi-Fi on my phone?
Will upgrading to 4.3 be worth it, or will there be any risks?
Will upgrading/flashing a new (stock) rom bring back the SIM lock, or am I done with that?
Thanks.
1) there are several ways. You can start by downgrading your modem to its original since you are still on older firmware and see if that works
2) not very risky, just make sure you know about Knox and all that
3) Nope, unlocked for good
Thanks!
I'm so happy to know that it's gone for good. That means I could probably just flash a stock 4.3 rom and get the matching modem with it, and hopefully have wi-fi working, right?
Or-L said:
Thanks!
I'm so happy to know that it's gone for good. That means I could probably just flash a stock 4.3 rom and get the matching modem with it, and hopefully have wi-fi working, right?
Click to expand...
Click to collapse
Yup!
Sim unlock
Hello everyone, I m from India and i recently got a samsung sgh m919 from my ajnt and got it unlocked. The person who did it, rooted my device in order to unlock. Now i want to know if 1) Can unrooting remove sim unlock? 2) can i install any custom rom without loosing sim unlock? Thank you
I want to say
1) no
2) yes
but since we don't know what method they used, can't say for sure
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.
Hello,
I just bought my first Galaxy device (had a CDMA LG for a while, and I have a Nexus Tablet), and I am looking at how to get this new phone set up right. I bought my i747 retail, so I was unable to unlock it. However, now I'm struggling with finding the right method for upgrading, rooting, etc. I know nothing about knox or any of these Samsung intricacies. Could someone please give me a little guidance on how to go about getting to the OS and status that I'm looking for? This is what I've done so far:
Came unrooted with 4.1.2 stock rom
Unlocked using legit unlock code
Tried OTA updates, but none were available (must be because of unlock)
Rooted w/ ODIN using 4.1.1 file based of MrRobinson method. (http://forum.xda-developers.com/showthread.php?t=1739426)
Now I keep getting popups like process. ... .acore,media, etc. stopped.
I'm looking to ideally get a custom recovery (either CWM or TWRP, whichever is better) and either kitkat Touchwiz or possibly kitkat nexus stock (I read somewhere that it was possible). Also, i just bought it, and have the code still, so I don't mind deleting everything if needed. Regardless, I'd like the ability to get it back to pure stock with no flash counter (I have a manufacturer's warranty I want to use if need be).
Could someone please just give me a little guidance? I'm pretty capable with rooting, etc., so you'd only need to lead me to other threads, etc. that will take me where I want to go. Thank you very much.
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
audit13 said:
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
Click to expand...
Click to collapse
Well, the bad news is I already flashed using MrRobinson's instructions, and now my phone is barely workable, as things like process.android.media and Touchwiz keep crashing. I was able to install the info app though, and my bootloader is listed as I747UCDLK3. Thanks again though, and let me know what else you need from me.
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
audit13 said:
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
Click to expand...
Click to collapse
Thank you, but wouldn't OTA updates install Knox, which would basically void my warranty if I tried to flash anything after that? And, I've checked for OTA updates twice, once on 4.1.2 and on 4.1.1, and both times it said my software was up to date.
I spoke with StoneyJSG about my situation, and he suggested that I go to stock 4.1, root w/ saferoot, then flash a kitkat custom rom without Knox through TWRP. That way, I could use triangle away and flash stock unrooted if I needed to send it in.
Although, I'm not sure if I should do that, as I thought I read that you need to update the radio and bootloader first before you can install a custom kitkat rom from jelly bean, but I'm still not entirely sure how that works.
The most recent release of many custom ROMs will not work but you may not have a signal without an updated modem and you should not be running updated modems on an older bootloader. Doing this could brick your phone.
With a rooted system, OTA updates will not work.
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
jateed said:
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
Click to expand...
Click to collapse
What is your cell service? If not AT&T, you will never get OTA.
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
audit13 said:
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
Click to expand...
Click to collapse
Well, I have an AT&T model which I unlocked and will be putting on Cricket at the end of the week (when my plan month is set to end). Right now there's no SIM in it, and I've been doing everything over wifi. I looked up whether the carrier had something to do with the OTAs, and I was told that Samsung sent the updates out, not AT&T, so I figured that the carrier info was irrelevant. I now wonder what my options are.
Can I manually flash 4.3 stock without tripping the knox warranty void?
Does Towelroot/Xposed framework trip the Knox void flag?
If I can update to 4.3/4.4 and root without tripping the knox flag, I might just manually update and just run towelroot and xposed to modify my OS the best I can until my warranty runs out.
If I can't root it at all once I'm on 4.3+, then I'll just sit on 4.1.1 for a few months until I can't stand it anymore and just void the warranty anyway.
Thanks again everyone. This whole knox/binary counter thing is not something I dealt with on my CDMA LG or Nexus, so I was totally in the dark about how it all worked. This is also my first GSM phone, so all those intricacies are new to me too. Once I know about manually flashing stock and running towelroot/xposed, I think I'll be in good shape.
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
audit13 said:
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
Click to expand...
Click to collapse
Excellent. If I did flash stock, i would just use ODIN, then factory reset to wipe the caches. And that's good to know about the KK rom, as I would probably update straight to 4.4 if at all (I've read a lot of bad things about 4.3 on the S3), but not if it means I cannot root safely and cleanly.
I'll check out the custom roms for 4.1.1. I know that flashing the rom and/or a custom recovery will trip the binary counter, but I can just use triangle away to clean that up. Do you know if there is a list of custom 4.1.1/4.1.2 roms somewhere, or do I need to scour the older threads here?
Thank you very much audit13 (thanks to StoneyJSG and pre4speed as well). You have been immensely helpful and really brought me up to speed on everything surrounding S3 customization. Needless to say it's way more complicated than what I've dealt with from LG and Google/Asus. (I mean, i could root my nexus with a single click using Wugfresh's toolkit)
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
audit13 said:
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
Click to expand...
Click to collapse
Oh, so what other way can you flash a stock rom, if not through ODIN or a custom recovery? Regardless, it seems as though I really should not dive into 4.3+ until I'm ready to concede that my warranty is over. There are just too many potential pitfalls and headaches.
On the lighter side, I've found a few 4.1.2 based custom roms that have some promise. I'm going to post them here in case anyone has opinions on them, or if someone else in my situation sees this thread and wants to go custom 4.1 too:
Hyperdrive RLS16
http://forum.xda-developers.com/showthread.php?t=2176793
Slim Bean-d2
http://forum.xda-developers.com/showthread.php?t=1865262
Jedi Academy
http://www.teamandroid.com/2013/12/...oid-412-jedi-academy-jelly-bean-custom-rom/2/
Jelly ‘Beans’
http://www.teamandroid.com/2013/04/...ndroid-412-att-galaxy-s3-sgh-i747-custom-rom/
I was also torn when I got my s3 that was running 4.1.2. I downgraded to 4.1.1, sim unlocked the phone, used it on stock 4.1.2 for about a week to make sure everything was working, hardware wise, upgraded to stock 4.4.2, installed a custom recovery and a custom ROM. I wasn't too concerned about the warranty since I got the phone as a free upgrade and had no intention of using the s3 as my daily phone. I kept it as a backup until my niece needed and phone and then it went to her. It's been over a year and there are still no problems with the phone.
How to downgrade from 4.4.1 OEM to 4.3? OEM, no rooting really needed, I tried to go to 4.1.1 first and then flash to 4.3 but it keeps the 4.4.1 bootloader so the charging does not work when the phone is off...
There were no responses for almost 3.5 months however I keep hoping!
I know Note 2 is almost antique, however need to downgrade 4.4.1 bootloader UCUCNJ1 to original 4.1.2 LJ2 or 4.3 as the latest. I was able to go down to 4.1.1 but bootloader remained the same new one. It's an older phone, so there should be a way to get this done.
Maybe there is a way to make bootloader UCUCNJ1 work properly with 4.1 or 4.3?
I believe the bootloader on the i317 is locked and cannot be downgraded unlike the i317m.
Thanks!
All I need is 4.1 or 4.3 even with late NJ1 bootloader I have, as long as the phone would charge while being off
Need SOME advise, there must be a way of doing this.
I know of no way to unlock the bootloader to downgrade it to 4.1 or 4.3.
This is the picture of the real phone, OS 4.1.2 with NE5, correct?
I'd be fine with late NJ1 bootloader working properly with OS 4.1....
I was able to go down to 4.1.1 using this method http://forum.xda-developers.com/showthread.php?t=2618447 sadly NJ1 bootloader did not allow the phone to charge properly while off...
The phone can have a rom and bootloader that don't match but it is unlikely that an older rom will work properly with a newer bootloader.
Have you tried flashing the latest rom to see if that solves the issue? I don't have the 317, I have the 317m and I'm not sure if nj1 is the latest rom for the 317.
audit13 said:
The phone can have a rom and bootloader that don't match but it is unlikely that an older rom will work properly with a newer bootloader.
Have you tried flashing the latest rom to see if that solves the issue?
Click to expand...
Click to collapse
Yes I'm back to 4.4.1 everything works as it should (charges while the phone is off without locking the phone up), but I NEED to downgrade to 4.1 or 4.3 as the latest. Getting down from 4.4 to 4.1 or 4.3 is the whole point. The phone is so old, it's hard to believe that my question does not have a positive answer
I see people downgrade from 4.3 bootloader down to 4.1 no problem http://forum.xda-developers.com/showthread.php?t=2502464
I understand your frustration but 4.3 to 4.1 was possible, but 4.4.2 to 4.1 is not.
audit13 said:
I understand your frustration but 4.3 to 4.1 was possible, but 4.4.2 to 4.1 is not.
Click to expand...
Click to collapse
4.4.2->4.3 would work for me - is it possible?
Downgrading the bootloader to 4.3 from 4.4.2 is not possible based on my everything I have read and heard. I have never come across a post to indicate that the downgrade was successful.
Being in Canada, the phone I had was the i317m which, if I recall correctly, did have a downgradable bootloader. It's been a couple of years since I had a Note 2.
So we can make it official: on AT&T SGH-I317 there is no way to downgrade Android 4.4.1 to any earlier version.
As far as I am aware, once the AT&T Note 2 is on stock 4.4.2, there is no way to downgrade everything to 4.3, although there may be ways to downgrade parts of ROM/modem to 4.3 but not the bootloader.
Hello I'm currently running 4.4.2 with root and I've been thinking about upgrading to marshmallow. I just wanted to know whats the best way going about it. I'm assuming that I'm going to have to re-enable the software updating app that I disabled for I didn't get OEM updates then upgrade to marshmallow and re-root using one of the guides or would a root keeping app or Survival mode on superSU possibly work? I also believe I have TWRP installed from when I rooted my phone before, I'm not sure if that's important info. Also side note, would their be a way to keep the 4.4.2 touch buttons on the bottom of the screen? They make more sense to me then the new ones. Device info below
AT&T
android 4.4.2
software version D85010d
Model number LG-D850
You can't root on marshmallow so if you want root DO NOT update with that app. the easiest way is to just flash a rom. i have the verizon version (vs985) and all i have to do to flash a custom stock rom, is to flash the right modem before flashing the rom, then flashing modem again after the rom and bam, i just flashed a marshmallow rom from kitkat 4.4.2. you can also downgrade that way just flashing the appropriate modem before and after and bam.! but i dont know about your version, you should definitely check the att&t G3 subforum. you need to be careful and read thoroughly so you don't brick. the thing with vs985 is that there are modems out there that can hardbrick the device, however, it may not be the same for others but, just in case you should read.
Thank you I'll look into that. So far I found this https://forum.xda-developers.com/att-lg-g3/development/rom-stock-bumped-marshmallow-v30a-t3661194 but I still got more research to do since I'm unfamiliar with flashing modems and whatever "bumped" is exactly. Hopefully this weekend I'll have more time to look into this.