I recently upgraded my BMC S3 from a rooted 4.3 to 4.4.2 - FNK2
I then realized there doesn't seem to be a good process for rooting that version.
It looks like I can root 4.4.2 - FNH2 though.
Is it possible to downgrade without bricking the phone?
Downgrading will brick the phone.
If you want root, just flash Philz d2lte recovery and flash supersu from recovery.
audit13 said:
Downgrading will brick the phone.
If you want root, just flash Philz d2lte recovery and flash supersu from recovery.
Click to expand...
Click to collapse
So...i need to use d2lte for the d2can phone then?
Before the s3 builds were unified, there was separate software for the d2can (i747m) and d2att (i747). Since unification, ROMs for the s3 are interchangeable, thus the change to the d2lte moniker.
I pulled the trigger and installed it...it was surprisingly simple...thanks a bunch!
Related
I have a Canadian Telus provided GalaxyIII SGH-I747M, it is rooted, twrp recovery installed and I am confused when it comes looking for compatible roms. I get conflicting information everywhere but have narrowed it down to I can use ATT roms on my Telus phone, please confirm this. My question is, my twrp recovery downloaded the d2can build but ATT is d2att, do I need to change this in my recovery (if possible), or just leave it at d2can to install ATT roms. If my terminology is off I apologize (noob).
Thanks for your time.
Look at the bootloaders in the updater-script of the custom ROM you want to install. If you see your bootloader, you should be fine.
The latest version of TWRP for your phone can flash a ROM designed for the d2att.
I had problems with TWRP so I switched to the latest version of Philz Touch which can be flashed via Odin or from TWRP.
I rooted my dad's phone a while back ago so he can use tethering in case of emergencies etc. He recently got a smart watch and I wanted to updated it so that he can use it. But it has not been touched since that day. I essentially want rooted stock rom, I'm unaware of where to find that the closest I can find is StockMod kitkat. Which seems to not work on ATT phones? I just want to make sure that I don't brick his only phone on christmas. So is there something I should be aware of?
His model is SGH-i747
Baseband
i747UCDLK3
Build number
jro03
So how do I go about upgrading it? Can I just flash TWRP and flash any rom using TWRP?
I found this, so I should install new TWRP, then flash a specified kernel then flash rom? would this be safe route?
Some of the latest ROMs require a 4.4.2 bootloader and modem.
The simplest and safest way to get the latest bootloader may be to flash back to unrooted stock 4.1.1 and run OTA updates until the phone is running the latest KK ROM. You can then flash TWRP or CWM and a custom ROM.
audit13 said:
Some of the latest ROMs require a 4.4.2 bootloader and modem.
The simplest and safest way to get the latest bootloader may be to flash back to unrooted stock 4.1.1 and run OTA updates until the phone is running the latest KK ROM. You can then flash TWRP or CWM and a custom ROM.
Click to expand...
Click to collapse
Would this require flashing with ODIN? I just want it so that it works with root is not required anymore.
Yes, you would flash the 4.1.1 stock ATT ROM via Odin. I prefer Odin 3.07.
You cannot install OTA updates with root.
You can try flashing just the bootloader and modem but I prefer the long slow route of OTA updates.
I rather do it this way, manually so my dad can enjoy it today. I was wondering how can I update it's TWRP? it's at 2.3 but the TWRP manager keeps crashing when I update it.
I highly recommend the latest d2lte version of Philz Touch for recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Ok I ****ed up, flash that kernel and did whatever and bam ****ed up. Not working... ****, I still ahve download mode and Recovery but it will not boot into the OS. I get a flash of samsung and then nothing else happends...****
I decided to flash stock DLK3 in odin. Then let the updates take it course (my dad doesn't need root) Where Can I find the file?
The stock ATT firmware is on sammobile.com.
If you want root, OTA to the latest 4.4.2, install Philz, flash supersu via recovery.
Background: I attempted to update from SlimKat 7.0 stable to 9.0 stable and discovered my apn's were missing and when I try to add them manually it fails to save. I have also found others with this same issue but none have an easy fix. I'm on UCDLK3 firmware, after restoring to previous state using nandroid backup apn's are present. If I try to flash any ROM (even other than Slim) my apn's are missing, even a dirty flash of 7.0 over 7.0. I know I can fix this by flashing stock UCDLK3 and root/twrp/flash slim 9 and everything will likely work fine. I plan to do just that but want to make sure I'm doing things as smart and clean as possible. There is a lot of info out there and I'm finding it hard to sift through old stuff and find the current state of things.
Question: Is there an actual advantage if I upgrade the firmware from UCDLK3 to UCUEMJB while still planning to use SlimKat 9 Stable with BMS kernel and TWRP recovery? Are there any disadvantages? Either way what is the shortest path to get back to stock (either LK3 or MJB) and flash SlimKat?
Thanks
Your APN may not be sticking because your modem and bootloader may be too outdated.
Some of the latest CM11 and AOSP ROMs require a KK bootloader and modem.
And then there are some roms that require at least a 4.3 bootloader and modem, either the MJ2 (leaked) or MJB (official) bootlaoder/modem combos. I have seen mention of these working in some OPs and in the body of other threads. In some of the later TW ROMs you may have to use a custom kernel like kt747 or iBuddler's. I don't know if any kernel other than the stock in SlimKat and AOSP ROMs would be needed with the MJ2/MJB firmware and modem.
I don't know of any advantages other than some of the ROMs require firmware newer than DLK3 to properly boot, receive data, or have a working wifi. As far as disadvantages, KNOX was introduced with the MJB firmware and stock ROMs, once going to MJB or newer firmware you can not make firmware downgrades without a very real risk of hardbricking your phone. Also you will need to insure your baseband and modem versions match. If they do not you risk hardbricking of another variety.
I had not yet realized that the newer AOSP and CM11 required you to go all of the way to NE4, thank Audit.
Just wanted to close the loop on this thread and say thanks for the assistance!
I now have my phone working properly on SlimKat 9; it really was just the firmware not being compatible with newer ROMs as many have suggested. Here is the sequence I followed to do it but really it probably only needed a twrp flash of the mjb firmware and the ROM install:
1. Used odin to restore to stock LK3 (only because I had messed with things so much and wanted a clean slate)
2. Used odin to install TWRP 2.7.1.0 recovery
3. Rooted with SuperSU 2.40 using TWRP
4. Flashed combined MJB modem & bootloader using TWRP
5. Flashed SlimKat 9 using TWRP
6. Flashed Slim GApps using TWRP
7. Rooted with SuperSU 2.40 using TWRP (Lost root after flashing ROM)
thanks for posting fix. am sure it will help others. audit13 and dawgdoc , thank you for continued help with the awesome Slll. :good:
"all i can really do , is stay out of my own way and let the will of heaven be done"
jeff.leonard said:
Just wanted to close the loop on this thread and say thanks for the assistance!
I now have my phone working properly on SlimKat 9; it really was just the firmware not being compatible with newer ROMs as many have suggested. Here is the sequence I followed to do it but really it probably only needed a twrp flash of the mjb firmware and the ROM install:
1. Used odin to restore to stock LK3 (only because I had messed with things so much and wanted a clean slate)
2. Used odin to install TWRP 2.7.1.0 recovery
3. Rooted with SuperSU 2.40 using TWRP
4. Flashed combined MJB modem & bootloader using TWRP
5. Flashed SlimKat 9 using TWRP
6. Flashed Slim GApps using TWRP
7. Rooted with SuperSU 2.40 using TWRP (Lost root after flashing ROM)
Click to expand...
Click to collapse
When you restored to LK3, what Firmware version were you coming from? I'm looking to go to LK3 from the NJ1. However there seems to be cautionary red flags all over the place due to bootloader changes that were made in 4.3.
The OP was already on LK3 with a custom ROM.
Since you are on NJ1, you cannot downgrade the bootloader.
Hey i jus got a s3 i747m. And its been updated to latest firmware I747MVLUFNK2 and i want to root it and get rid of KNOX how would i go about this i know cf-root (d2can since it a Canadian Bell mobility (BMC) Model should work but apparently it does not for this firmware i also need a twrp recovery
Sent from my SGH-I747M using Tapatalk
Never mind i got it will post exactly how even with new i747mvlufnk2 and how to get cwmr6.0.4.7 everything works fine stock tochwiz 4.4.2
Easiest way for me to to accomplish this was to flash Philz Touch recovery for the d2lte using the latest tar.md5 and Odin. Once Philz was flashed, I flashed supersu from Philz, rebooted, updated supersu binaries, and allowed supersu to disable knox.
I used c.f. root and it worked fine for me with the i747mvlufnk2 modem so i uploaded a stock rooted Rom to my Google drive incase anyone wants it StockBLOATED-i747m-02.22.2015.tar.gz
https://docs.google.com/file/d/0B0ijBQSXOnQsRVA1bTNPeFlZOWc/edit?usp=docslist_api
Where can i find latest Philz recovery and the Knox removal flash zip
Latest Philz can be downloaded from here:
Just install the latest supersu via recovery, Once you reboot the phone, supersu should ask to disable knox.
audit13 said:
Latest Philz can be downloaded from here:
Just install the latest supersu via recovery, Once you reboot the phone, supersu should ask to disable knox.
Click to expand...
Click to collapse
There is no link to click i have philz 6.48 d2lte and from what i read d2lte is all variants is this correctly and sad to use on my i747m d2can
Roms and recoveries made for the d2lte are fine on the d2can and d2att.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
I have a Canadian Galaxy S3, on 4.1.1 DLK4 Official. I rooted it, and have TWRP.
I want to upgrade my rom to a CM12/13 but of course with root and custom recovery, OTA updates are blocked.
I need newer bootloaders and modem to run the newer android versions.
Should I install them now, while on 4.1.1, and then flash CM12, or should I sequentially update each of the AT&T firmwares until I get up to 4.4.2?
Do official roms have the bootloaders and modems in them and install them automatically?
Should I use the Kies restore method?
The Canadian and att s3 phones are not the same model number. Don't flash an att bootloader to your Canadian phone as this may brick the phone.
Flash latest stock rom from Sammobile.com, flash twrp, flash cm.
audit13 said:
The Canadian and att s3 phones are not the same model number. Don't flash an att bootloader to your Canadian phone as this may brick the phone.
Flash latest stock rom from Sammobile.com, flash twrp, flash cm.
Click to expand...
Click to collapse
Okay, but i can use AT&T roms tho?
The i747m will work with d2can, d2lte, and d2att Roms.
Is it safe to flash straight from 4.1.1 to 4.4.2 using a sammobile rom? will i brick due to Knox bootloader and modem?
Can I flash it using TWRP?
If someone could link a tutorial that would be very helpful.
I keep reading stuff that says to flash the newer bootloader before flashing a 4.3 firmware, and some that say the opposite. Others say that people should incrementally update.
I want to go from 4.1.1 original with Root and TWRP, to CM13.
Thank you.
Yes, you can flash the latest stock 4.4.2 rom from Sammobile.com directly to your phone. No need to do anything other than backing up your data.
audit13 said:
Yes, you can flash the latest stock 4.4.2 rom from Sammobile.com directly to your phone. No need to do anything other than backing up your data.
Click to expand...
Click to collapse
Thank you!
Now I just need to get the balls again to use odin. Flashing the custom recovery using the Universal Tool Kit that had step by step walkthrough was adrenaline rush enough LOL.
I could also use Kies, as that has 4.4.2 OB3 (telus), and also has "emergency firmware recovery" feature if a brick ever happens. Though ideally the only time boot.img gets flashed is only with Full Stock Firmware files.
I find kies to be unreliable when I have tried to restore firmware so I always stuck with Odin.