Related
I soft brick my phone tried to downgrade to 4.1.1 using odin it fails. any help guys!!!!
i was using stock 4.3 rooted before the brick
can anyone provide me with the at&t 4.3 tar file so i can use it in odin. I can't find one
please help guys
abcd8496 said:
I soft brick my phone tried to downgrade to 4.1.1 using odin it fails. any help guys!!!!
i was using stock 4.3 rooted before the brick
can anyone provide me with the at&t 4.3 tar file so i can use it in odin. I can't find one
please help guys
Click to expand...
Click to collapse
You'll need JTAG service repair.
polobunny said:
You'll need JTAG service repair.
Click to expand...
Click to collapse
He may not if it is a soft brick. As long as when he says softbrick he means that it is not loading past the Samsung log or the ATT logo for example. I was on stock rooted 4.3 as well and tried flashing other roms as well and soft bricked my phone in the process.
I ended up with two choices, load only 4.3 (The STOCK MOD v4 install worked for me just fine - but I was trying to get out of 4.3 tbh) Tried several other roms and all would end in a soft brick.
Finally landed on a stock 4.1.2 UCMG2 rom http://forum.xda-developers.com/showthread.php?t=2388065
After clearing my internal SD and formatting it I flashed it and it worked (took a long time on the Samsung logo but worked!) the wifi is a little flaky at times but it always was on 4.1.2 for me anyways... the key I believe was that this rom did not have a bootloader and modem updated, which was required to properly downgrade after having had previously installed 4.3.
OP try it out and see how that works? Unfortunately I could not find a TAR of this, but luckily I was able to use a microSD adapter to move the needed files onto the SD card so that I could flash in TWRP.
werds said:
He may not if it is a soft brick. As long as when he says softbrick he means that it is not loading past the Samsung log or the ATT logo for example. I was on stock rooted 4.3 as well and tried flashing other roms as well and soft bricked my phone in the process.
I ended up with two choices, load only 4.3 (The STOCK MOD v4 install worked for me just fine - but I was trying to get out of 4.3 tbh) Tried several other roms and all would end in a soft brick.
Finally landed on a stock 4.1.2 UCMG2 rom http://forum.xda-developers.com/showthread.php?t=2388065
After clearing my internal SD and formatting it I flashed it and it worked (took a long time on the Samsung logo but worked!) the wifi is a little flaky at times but it always was on 4.1.2 for me anyways... the key I believe was that this rom did not have a bootloader and modem updated, which was required to properly downgrade after having had previously installed 4.3.
OP try it out and see how that works? Unfortunately I could not find a TAR of this, but luckily I was able to use a microSD adapter to move the needed files onto the SD card so that I could flash in TWRP.
Click to expand...
Click to collapse
If he was on stock 4.3 and tried to ODIN to stock 4.1.1, then he's gonna need a JTAG.
If he had tried to flash something via TWRP/CWM then it wouldn't have been an issue.
polobunny said:
If he was on stock 4.3 and tried to ODIN to stock 4.1.1, then he's gonna need a JTAG.
If he had tried to flash something via TWRP/CWM then it wouldn't have been an issue.
Click to expand...
Click to collapse
Aaaah OK! Thanks for the clarification on why
You do not need a JTAG service. There is a way to unbrick it of you accidentally downgraded your bootloader from 4.3 OTA.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have i747 and update is only possible through ota that's what written on official website kies is not updating my phone as it is showing 4.1.1 is the latest firmware.
Please help me how can i update my Sgh-i747 manually or any other method.
I don't wanna root my phone.. I have also downloaded leaked 4.3 ROM I747UCUEMJ2.7z and after extracting i get different files.I didn't get any .md5 or .tar file which odin recognizes. So i can't update my phone maually to 4.3 by odin
Please help me how can i update my sgh-i747.
I have official samsung firmware 4.1.1.
samoudwfr said:
I have i747 and update is only possible through ota that's what written on official website kies is not updating my phone as it is showing 4.1.1 is the latest firmware.
Please help me how can i update my Sgh-i747 manually or any other method.
I don't wanna root my phone.. I have also downloaded leaked 4.3 ROM I747UCUEMJ2.7z and after extracting i get different files.I didn't get any .md5 or .tar file which odin recognizes. So i can't update my phone maually to 4.3 by odin
Please help me how can i update my sgh-i747.
I have official samsung firmware 4.1.1.
Click to expand...
Click to collapse
The update IS possible OTA. It does not show up in KIES for some reason.
A couple of things before you do this.
Be aware that once you have the MJB bootloader that comes with the 4.3 update, you cannot go back to anything lower without bricking the phone. Plenty of articles here about it. Until someone here finds a way, it's a one way trip, and there is no stock firmware available yet to flash via Odin. I'm also not sure if you can load one of the other 4.3 versions found here without bricking it after the OTA 4.3.
Some new features are added in 4.3, and some are broken. For me, after the update, s-voice no longer works via Bluetooth, and I'm pretty sure it is an S-voice and not BT issue. Others are reporting battery life issues, constant updates, etc. Research research research. (I wish I had)
Go to settings - about device - software update and follow the prompts to get an OTA. I don't think AT&T is pushing it, but is available. Probably not a bad idea to boot to recovery first and wipe the cache before you do.
You have to be running a stock recovery for it to install and its about a 1gig download, so be on wireless and have a fully charged battery.
In my case, I had the phone rooted with a toggles mod. The update went partially and broke some things. I had to flash to an unmodded unrooted 4.1.1 via Odin to get the update to go.
I made the mistake of trying to flash MJ2 bootloader after having the MJB bootloader. It boots now with the "unbrick" sd card. Would it be possible to ODIN stock 4.1 and still boot with the SD card so it could take the 4.3 OTA again?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
RichMD said:
I made the mistake of trying to flash MJ2 bootloader after having the MJB bootloader. It boots now with the "unbrick" sd card. Would it be possible to ODIN stock 4.1 and still boot with the SD card so it could take the 4.3 OTA again?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
I don't know. I've never bricked a phone. As I understand it, 4.3 BL blows e-fuses making it impossible to downgrade. If that is in fact an accurate description, then even if you were to get it to boot via SD card and installed 4.1.1, it would brick it again (double brick?)
Considering the dangers involved, I'm afraid to even sideload a different MJB 4.3 on mine.
You might just have to suck it up and send it off for a J-tag service. I've never done it, but I think others here have.
here's the link I've seen most.
http://www.ebay.com/itm/Unbrick-AT-T-SGH-I747-S3-SGH-T999-JTAG-service-I747-T999-Hard-Brick-Fix-USA-/160896407164
Sorry for your loss.
Michael503 said:
I don't know. I've never bricked a phone. As I understand it, 4.3 BL blows e-fuses making it impossible to downgrade. If that is in fact an accurate description, then even if you were to get it to boot via SD card and installed 4.1.1, it would brick it again (double brick?)
Considering the dangers involved, I'm afraid to even sideload a different MJB 4.3 on mine.
You might just have to suck it up and send it off for a J-tag service. I've never done it, but I think others here have.
here's the link I've seen most.
http://www.ebay.com/itm/Unbrick-AT-T-SGH-I747-S3-SGH-T999-JTAG-service-I747-T999-Hard-Brick-Fix-USA-/160896407164
Sorry for your loss.
Click to expand...
Click to collapse
I am trying to learn more about it but my "initial" understanding is that the "blown efuse" thing is that you can no longer boot from an earlier bootloader but it doesn't "damage" anything else. Therefore, since I already have a phone in that state but it can boot off the SD card I'm wondering if it doesn't make things worse to flash a 4.1 stock image. It would still fail to boot via EMMC but then boot off SD? Then the OTA could "possibly" happen? I doubt it is possible or someone would have posted about it but I haven't seen that you definitely CAN'T do it so I am continuing to look.
Hello, I know there are many threads on restoring a bricked S3, some of them for hard bricks, and some for soft bricks. None of the guides I found by scouring these forums provided all of the answers I needed.
INFO PLEASE READ ALL
Here I hope to outline how I restored my T999 Tmobile S3 to stock firmware after the 4.3 MJC update, and after bootloader bricking the phone. I do assume you are capable of using ADB, ODIN and TWRP. I believe this method will work for other S3 models, but I have no ability to test it. If it will work, firmware and debrick IMGs will have to be found for the specific device. The T999 firmware and IMGs will NOT work with other devices. This will restore to stock UVUEMJC 4.3 firmware. Will not be rooted, but existing 4.3 roots for the device should work.
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE. THE TOOLS USED IN THIS GUIDE HAVE THE POTENTIAL TO BRICK, OR OTHERWISE DAMAGE YOUR DEVICE. USE AT YOUR OWN RISK
So as context, I had been flashing different ROMS; then I updated to stock 4.3 UVUEMJC Firmware. This updated the bootloader, and installed the Samsung KNOX security upgrade. Both the bootloader and the KNOX are problems regarding rooting, rom installation, and downgrading (which I still have not achieved)
After upgrading, I installed a vanilla rootbox. I then attempted to flash the UVDMD5 bootloader at mnasledov's thread here: http://forum.xda-developers.com/showthread.php?t=2282603
Lacking my present understanding, of the 4.3/KNOX problems, I managed to brick my phone by effectively attempting to downgrade the bootloader. Phone appeared to be hard bricked.
I tried many things to fix the phone, these are what worked:
GUIDE:
1. Get a Class 10 MicroSD card and follow KAsp3rd's guide to boot from the SD card: http://forum.xda-developers.com/showthread.php?t=2439367
You should now be able to boot to download mode, recover, and system if it was undamaged when you bricked your phone.
2. Boot into download mode and install TWRP via ODIN
3. Boot into your new TWRP recovery. Do an ADB sideload of the KNOX removal script found in Kaito95's thread here: http://forum.xda-developers.com/showthread.php?t=2507931 Check the clear cache and clear dalvik recovery boxes. You have to do an ADB sideload, because your SD card is in use as a bootloader.
4. Use ODIN with Download Mode to Re-Partion by flashing the PIT file found in invisiblek's downloads here: http://forum.xda-developers.com/showthread.php?t=1848267
The Re-Partition box will have to be checked, and the PIT file loaded under Re-Partition. This is what I believe corrected the download mod fails I had been getting.
5. Use ODIN and Download mode to flash the original UVUEMJC firmware found in DocHoliday77's thread here: http://forum.xda-developers.com/showthread.php?t=1949687
6. In TWRP do a factory reset, and a fix permissions. Reboot into system, (without the SD card)
If all went well you should be in business!
If you see any error in my guide, or have another correction, please let me know. If I have posted this in the wrong section I'll be happy to move it.
I hope this helps you.
ROOTING:
So after fixing my phone via the steps above, I still wanted to root it. To root it I simply ODIN flashed mrRobinson's rooted/deKNOXED 4.3 stock rom from here: http://forum.xda-developers.com/showthread.php?t=1771687
It seemed very stable to me.
I then decided to use TWRP to install the CyanogenMod 10.2. If you choose to install CM, I believe you must use the 10.2 branch, because it is 4.3 based. Prior versions are not 4.3, and won't work with the 4.3 bootloaders. You can find the appropriate CM download by selecting your device here: http://download.cyanogenmod.org/ The T999 is d2tmo.
EDIT: YOU CAN RUN OLDER VERSIONS AFTER UPDATING TO 4.3.
This was pointed out to me by Adreaver. I personally am using rootbox 4.2.2 after having done the 4.3 official update. Any rom for the device should work, but certain lines may need be removed form the updater script. I am still looking into this.
NOTES
This has been confirmed to work on the T999L, but you need a different PIT file, and different firmware for the model. See @mrspock08 's post on page 2 of this thread for more info on the T999L
THANKS
I could not have debricked my phone or created this guide without referencing and using the work of several fine members of this forum. Particular thanks to:
@mnasledov for providing a thread with information about bootloaders.
@KAsp3rd for providing a way to boot from the SD card, enabling the entire rest of the debrick.
@Kaito95 for the deKNOX script.
@invisiblek for the PIT file for correctly repartitioning the phone.
@DocHoliday77 for the MJC 4.3 Stock Firmware mirror.
@mrRobinson for the rooted MJC Stock firmware
@Adreaver for correcting me that you can run an older version of android
And the threads of many many others who's work I read through while learning about how all of this works.
Nice guide. I think @DocHoliday77 could use this method because I believe he bricked his phone the same way.
Oh, and I believe you might have made a typo SDB is actually ADB Android debug bridge.
sswb27 said:
Nice guide. I think @DocHoliday77 could use this method because I believe he bricked his phone the same way.
Oh, and I believe you you might have made a typo SDB is actually ADB Android debug bridge.
Click to expand...
Click to collapse
Of course! You're right, a typo on my part. Thanks for pointing that out!
TronMinecraft said:
Of course! You're right, a typo on my part. Thanks for pointing that out!
Click to expand...
Click to collapse
No problem, I made more then 1 mistake when I made my first page. So your doing good with only 1.
TronMinecraft said:
Hello, I know there are many threads on restoring a bricked S3, some of them for hard bricks, and some for soft bricks. None of the guides I found by scouring these forums provided all of the answers I needed.
Click to expand...
Click to collapse
Cool guide! Thanks for the write-up!
Thanks for guide and explaining very clearly
Surely if it worked for you then it is going to help others too
Thanks once again
Sent from my SGH-T999 using Tapatalk
Nice writeup. I assumed that a bootloader brick was the point of no return, thanks for proving me wrong.
Worth noting that you can flash any d2tmo ROM on the new bootloaders, even cm9 or 4.0.4 tw, but you may need to remove asserts from the updater-script.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Great tutorial. An extreme amount of time went into this I can see. Hopefully it'll be able to get @DocHoliday77 back up and running tho. I miss that guy!
Sent from my Nexus 5 using Tapatalk
TheLastSidekick said:
Great tutorial. An extreme amount of time went into this I can see. Hopefully it'll be able to get @DocHoliday77 back up and running tho. I miss that guy!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I spent a few days on it, I hope it helps people. I hope it gets Him back up and running, his MJC mirror was instrumental in my fix.
Adreaver said:
Nice writeup. I assumed that a bootloader brick was the point of no return, thanks for proving me wrong.
Worth noting that you can flash any d2tmo ROM on the new bootloaders, even cm9 or 4.0.4 tw, but you may need to remove asserts from the updater-script.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For most phones the bootloader brick would require JTAG; fortunately several of the Samsungs have the SD as default boot.
And you can flash older ROMs? I was unaware of this; every attempt I've made to run something older has resulted in a getprop(ro.bootloader) error. But that updater script assert makes sense. Thank's for letting me know. I'll check that out and add it to the OP
so what?
i want to update my phone to T999UVUEMJC 4.3 firmware
currently i'm on T999UVDMD5 4.1.2
is it safe to update using Odin?
sorry for noob question
Restoring bootloader to bricked S3 T999L
TronMinecraft said:
Here I hope to outline how I restored my T999 Tmobile S3 to stock firmware after the 4.3 MJC update, and after bootloader bricking the phone. I do assume you are capable of using ADB, ODIN and TWRP. I believe this method will work for other S3 models, but I have no ability to test it. If it will work, firmware and debrick IMGs will have to be found for the specific device. The T999 firmware and IMGs will NOT work with other devices. This will restore to stock UVUEMJC 4.3 firmware. Will not be rooted, but existing 4.3 roots for the device should work.
Click to expand...
Click to collapse
Great guide, thanks a ton to @TronMinecraft for this writeup! I've been lucky and haven't bricked my S3 T999L (the T-Mobile LTE variant), but a relative wasn't so lucky. She took the OTA upgrade and when she wasn't happy with the result tried to just restore to her old 4.1.2 backup. Needless to say she bricked her phone.
So, I can confirm that this method DOES work on a T999L. However, there are a couple of things to note (these should be no-brainers, but in the interest of saving questions from the newbies out there...) Of course like Tron said, I take no responsibility for damage to your device should you try this. I can only tell you that it worked fine for me. Here's the things to watch out for, listed by the steps in the OP:
4. Make certain that you use the correct PIT file for the T999L. The proper PIT file for the T999L is the one DocHoliday uploaded here http://forum.xda-developers.com/showthread.php?t=1848267&page=3. Do not use the regular T999 PIT file from @invisiblek's first post in that thread, which is what was linked to in the OP.
5. Make sure you use the correct firmware for the T999L, NOT the T999. If you're trying to recover from a brick then most likely you're going to want the Original UVAMB7 firmware (JB 4.1.2), since it seems most bricks lately are caused by trying to downgrade after flashing the 4.3 update. Of course if you want to you can also flash the UVUBMK4 (4.3) firmware and get the complete stock 4.3 system, including the bootloader, KNOX, etc.
However, if you're just recovering from a brick and want 4.3 I would recommend not just flashing the UVUBMK4 firmware directly. Rather, I would flash the older UVAMB7 firmware, and then once your phone is back up and running flash DocHoliday77's UVUBMK4 4.3 Rooted, deodexed_KnoxFREE ROM from http://forum.xda-developers.com/showthread.php?t=2370981&page=58. Once you've done that, just flash the updated modem from http://forum.xda-developers.com/showthread.php?t=1880987 as needed. This way you end up with the full rooted version of the 4.3 firmware but without the 4.3 bootloader which includes KNOX and causes so many problems with downgrading.
Of course that's just my two cents. I've been running my S3 with DocHoliday's stock UVUBMK4, KnoxFree, rooted ROM with the UVAMB7 bootloader and UVUBMK4 radio for over a month now and haven't had any problems. As always, your mileage may vary.
mrspock08 said:
Great guide, thanks a ton to @TronMinecraft for this writeup! I've been lucky and haven't bricked my S3 T999L (the T-Mobile LTE variant), but a relative wasn't so lucky. She took the OTA upgrade and when she wasn't happy with the result tried to just restore to her old 4.1.2 backup. Needless to say she bricked her phone.
So, I can confirm that this method DOES work on a T999L. However, there are a couple of things to note....
Click to expand...
Click to collapse
Thank you for confirming this worked for somebody else. I'm working on a slightly re-factored version of this based on input, and I'll be sure to note your findings about the T999L. Thanks!
SignalX said:
so what?
i want to update my phone to T999UVUEMJC 4.3 firmware
currently i'm on T999UVDMD5 4.1.2
is it safe to update using Odin?
sorry for noob question
Click to expand...
Click to collapse
This really isn't quite the right place for such a question. A search will yield you great results.
But yes, there's no reason you couldn't if you're sure you have the right firmware for your GS3 model. However if you simply want a stock update, I'd just use the OTA update function, or kies. Its a bit safer than manually messing with Odin, and won't void your warranty.
Very useful thread. Bricking is actually a lot easier than I thought.
hi does this guide help downgrade a 4.3 without loosing imei ? thank you
hope to receive a answer to this noob question
Sent from my SGH-T999 using XDA Premium 4 mobile app
FINNIX1996K said:
hi does this guide help downgrade a 4.3 without loosing imei ? thank you
hope to receive a answer to this noob question
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You CAN NOT DOWNGRADE 4.3.
This guide is to unbrick you and return you to 4.3 if you tried to downgrade (which won't work, ever).
Sent from my SGH-T999 using XDA Premium 4 mobile app
Actually, from my own experimentation you were right, you can in fact downgrade from 4.3. You just can't flash a rom that tries to change the bootloader. You cannot downgrade the 4.3 bootloader; but there isn't any reason why you can't run an earlier version of android.
I am currently running 4.2.2 rootbox AFTER having having done the official 4.3 update.
I did this with TWRP, and a rootbox flashable zip.
TronMinecraft said:
Actually, from my own experimentation you were right, you can in fact downgrade from 4.3. You just can't flash a rom that tries to change the bootloader. You cannot downgrade the 4.3 bootloader; but there isn't any reason why you can't run an earlier version of android.
I am currently running 4.2.2 rootbox AFTER having having done the official 4.3 update.
I did this with TWRP, and a rootbox flashable zip.
Click to expand...
Click to collapse
You did not downgrade. You flashed a custom ROM.
An example of downgrading would be a user on md5 flashing ljc with Odin. This puts bootloader, ROM, kernel, and baseband exactly as Samsung intended when LJC was released.
Sent from my Cleared Out T999L on CM11
Should be pinned. Very useful indeed
Adreaver said:
You did not downgrade. You flashed a custom ROM.
An example of downgrading would be a user on md5 flashing ljc with Odin. This puts bootloader, ROM, kernel, and baseband exactly as Samsung intended when LJC was released.
Sent from my Cleared Out T999L on CM11
Click to expand...
Click to collapse
Okay, thank you for the clarification. I was incorrectly applying the term downgrade.
Hey guys,
I got a I747 I want to give to my mother as a gift.
I downgraded 4.1.2 to 4.1.1 and ran the secret menu unlock to unlock the sim card, that worked perfectly.
Now I want to update this out of 4.1.1 to 4.4.2 but I cannot find a stock firmware to run on odin anywhere.
Do I need to go to 4.3 first? Is there a stock firmware for that?
SamMobile stops at 4.1.2... OTA obviously doesn't work.
How Can I get this done..
Iz3man said:
Hey guys,
I got a I747 I want to give to my mother as a gift.
I downgraded 4.1.2 to 4.1.1 and ran the secret menu unlock to unlock the sim card, that worked perfectly.
Now I want to update this out of 4.1.1 to 4.4.2 but I cannot find a stock firmware to run on odin anywhere.
SamMobile stops at 4.1.2... OTA obviously doesn't work.
How Can I get this done..
Click to expand...
Click to collapse
You can just flash stock 4.1.2 firmware from sammobile and then run OTA updates.
I also found this on sammobile: Canada (Bell Mobile) (Black Edition), Version: Android 4.4.2, PDA: I747MVLUFNE6
CSC: I747MOYCFNE6, MODEM: I747MVLUFNE6
audit13 said:
You can just flash stock 4.1.2 firmware from sammobile and then run OTA updates.
I also found this on sammobile: Canada (Bell Mobile) (Black Edition), Version: Android 4.4.2, PDA: I747MVLUFNE6
CSC: I747MOYCFNE6, MODEM: I747MVLUFNE6
Click to expand...
Click to collapse
Will it work though.
I have it already on my pc, I updated my wife's with it.
If I update to 4.1.2 will OTA come? Even with the I747(not the I747m) on the Bell network?
Iz3man said:
Will it work though.
I have it already on my pc, I updated my wife's with it.
If I update to 4.1.2 will OTA come? Even with the I747(not the I747m) on the Bell network?
Click to expand...
Click to collapse
I have a Motorola Atrix from Bell. I flashed it with stock ATT firmware and received OTA updates from ATT over wi-fi.
Since you have the i747, start with stock pre-rooted ATT 4.1.1. This will flash the stock recovery, radio, and bootloader. Run triangle away, flash a stock unrooted ATT stock 4.1.1 ROM, and take the OTA updates.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=135374642
audit13 said:
I have a Motorola Atrix from Bell. I flashed it with stock ATT firmware and received OTA updates from ATT over wi-fi.
Since you have the i747, start with stock pre-rooted ATT 4.1.1. This will flash the stock recovery, radio, and bootloader. Run triangle away, flash a stock unrooted ATT stock 4.1.1 ROM, and take the OTA updates.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=135374642
Click to expand...
Click to collapse
Ok, so I guess it wasn't clear, my bad.
I have 4.1.1 stock firmware on my att 1747. It has never been rooted.
I run the Ota and I got an error, now it tells me "Your software is up to date".
Can I flash a bell i747m 4.4.2 image onto this i747 or will it brick?
Iz3man said:
Ok, so I guess it wasn't clear, my bad.
I have 4.1.1 stock firmware on my att 1747. It has never been rooted.
I run the Ota and I got an error, now it tells me "Your software is up to date".
Can I flash a bell i747m 4.4.2 image onto this i747 or will it brick?
Click to expand...
Click to collapse
You can flash i747m firmware on your phone but DO NOT flash the radios or bootloader from an i747m to an i747 and vice versa. Bricking is a really possibility if you do that.
Do you have a custom recovery? If you do, you will need to install a stock recovery.
Try resetting the phone (wiping cache, data) in recovery or through the ROM itself.
audit13 said:
You can flash i747m firmware on your phone but DO NOT flash the radios or bootloader from an i747m to an i747 and vice versa. Bricking is a really possibility if you do that.
Do you have a custom recovery? If you do, you will need to install a stock recovery.
Try resetting the phone (wiping cache, data) in recovery or through the ROM itself.
Click to expand...
Click to collapse
Alright, I have the stock recovery. How do I not flash the radio and boatloads when using the firmware from sammobile?
You cant. You cannot flash another devices firmware. Odin wont let it happen and if it did youd end up hard bricked due to mixed firmware. For example your sbl1, modemst and param partitions (plus others) would be i747 and youd be flashing sbl2, sbl3, rpm, etc from an I747M.
The only thing you could use are the system partition and kernel, nothing else. There are two ways to accomplish this, one is to build a rom from the firmware and flash that. The other is to flash with mobile odin, but that requires root and youd still have to be very careful.
Another priblem I see you encountering is you cannot run 4.4.2 without 4.3 or newer firmware. It will not boot otherwise.
You need to go to the General section and follow one of enewman17's tutorials to get to either 4.3 or 4.4.2. Personally, I dont see any other way you will be able to accomplish it.
audit13 said:
You can flash i747m firmware on your phone but DO NOT flash the radios or bootloader from an i747m to an i747 and vice versa. Bricking is a really possibility if you do that.
Do you have a custom recovery? If you do, you will need to install a stock recovery.
Try resetting the phone (wiping cache, data) in recovery or through the ROM itself.
Click to expand...
Click to collapse
Alright, based on Doc holiday, and others they say It cannot be done and from my experience I beleive them.
Thank you,
It's very difficult to do this when others are giving bad advice.
So for the record, cannot flash i747m firmware to i747.
Thanks!
The annoying part here is I can do it with my m7, I just flashed the Dev edition onto my Bell m7 with no problems.
All devices are different in many ways. What is perfectly safe to do with one brand or model can brick another.
And I wouldnt call it "bad" advice... I've seen audit13 and others helping lots of folks with very good advice. We all make mistakes and we all have more we can learn about these devices. No one knows everything about this stuff and shouldnt let that prevent them from trying to help.
Those who are trying to help are doing so with the best of intentions and tell people what they think could be the best way to solve a given problem. In cases like this one, its easy to see how anyone would think its ok to flash different firmware between similar models based on being able to do so on other devices they are familiar with. (If I had gone into those forums I wouldve been telling people the opposite and ended up being wrong there.)
All I can say is chalk it up as a new lesson on a different device, and I hope you still appreciate that someone was trying to help.
@audit13 I hope none of this discourages you from helping. Ive seen plenty of threads where your advice was sound and appreciated, and I am glad you have been around to help so many people out!
Now, back on the problem at hand... if you want to be running the latest 4.4.2 kk, you will have the option to use the OS (/system and kernel) from either the I747 or I747M firmware. But first you must fully update to a minimum of the 4.3 MJB firmware for the I747. Once you have this running for your base firmware/bootloader, you can then run the Bell or AT&T (4.3 or 4.4.2) system. (I hope this is making sense!)
So first, update the full 4.3, MJB, firmware via Odin. (Theres a thread in General with the file, ill post the link in a min).
If you want to update to 4.4.2 firmware, you can then follow enewman17's tutorial to do so via OTA.
You can then either stay with that, or use Mobile Odin to flash ONLY the system and kernel from the Bell firmware.
Let me know if any of that needs better clarification! Also let us know what your ultimate goal is. From the options you have, where do you want to end up?
---------- Post added at 10:32 AM ---------- Previous post was at 10:26 AM ----------
Ok, here are some links.
Stock MJB firmware (flash in Odin)
http://forum.xda-developers.com/showthread.php?t=2722660
enewman17's thread for updating to 4.4.2 (high success rate)
http://forum.xda-developers.com/showthread.php?t=2789917
Official, unmodified 4.4.2 OTA
http://forum.xda-developers.com/showthread.php?t=2788012
After updating with the 4.3 firmware, you can first try using the official ota to update. Then, if that fails you can go to enewman17's thread and try his method.
DocHoliday77 said:
All devices are different in many ways. What is perfectly safe to do with one brand or model can brick another.
And I wouldnt call it "bad" advice... I've seen audit13 and others helping lots of folks with very good advice. We all make mistakes and we all have more we can learn about these devices. No one knows everything about this stuff and shouldnt let that prevent them from trying to help.
Those who are trying to help are doing so with the best of intentions and tell people what they think could be the best way to solve a given problem. In cases like this one, its easy to see how anyone would think its ok to flash different firmware between similar models based on being able to do so on other devices they are familiar with. (If I had gone into those forums I wouldve been telling people the opposite and ended up being wrong there.)
All I can say is chalk it up as a new lesson on a different device, and I hope you still appreciate that someone was trying to help.
@audit13 I hope none of this discourages you from helping. Ive seen plenty of threads where your advice was sound and appreciated, and I am glad you have been around to help so many people out! ]
:thumbup::beer::sly:
err on the side of kindness
Click to expand...
Click to collapse
i747 from at&t rooted and twrp installed . Flashed CM12 5.1.1 no signals from t-mobile.To make it work on T-Mobile from att stock i had to flash QCN(t999) via QPST by code *#7284# to change into diag. . But now after flashing cm12 ,it is not giving me signals .No calls no DATA . Now i can not flash T999 QCN again because secret codes are hidden . Is there something i can do, to get signals on CM12 . I want to enjoy 5.1.1 !:silly:. . I already tried all of the (i747)lollipop roms same results. can i flash tmobile rom on att is it possible (radios are different ) will that work ?. I forgot there was an apk that could bring up secret codes window forgot the name. If anyone knows or have a link .
You can flash the T999 roms, just not the firmware.
Sent from my SGH-T999 using Tapatalk
You never stated what bootloader and modem was on your device before you flashed any of the Lollipop Roms. On the i747 you need at least the NE4 bootloader and modem to get signal on 5.x.x.
dawgdoc said:
You never stated what bootloader and modem was on your device before you flashed any of the Lollipop Roms. On the i747 you need at least the NE4 bootloader and modem to get signal on 5.x.x.
Click to expand...
Click to collapse
with NE4 , i can not downgrade ? I was on LK3 . Let me know if i can downgrade please from NE4 that is needed in case of ER accidents..( as i have already turned previous device into paper weight ) . If so i will upgrade then try to flash again . Thanks
DocHoliday77 said:
You can flash the T999 roms, just not the firmware.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks Doc i am going to give a shot .
rns416 said:
with NE4 , i can not downgrade ? I was on LK3 . Let me know if i can downgrade please from NE4 that is needed in case of ER accidents..( as i have already turned previous device into paper weight ) . If so i will upgrade then try to flash again . Thanks
Click to expand...
Click to collapse
Correct with the NE4 bootloader you can not downgrade without bricking your phone. Downgrades went out the window with MJB (Jellybean 4.3) and have not returned. Meaning you can never downgrade on MJB, NE4, NJ1, or NJ2.
With LK3 you could go upto MG2 (JB 4.1.2) or MJ2 (the leaked release of 4.3) and still be able to downgrade. I have downgraded while on MJ2 with no issues. I went down to LK3 from MJ2 in order to utilize the free sim unlock, I think DocHoliday mentioned it earlier. Since then I have gone back up to MJB and then to NE4, so I can no longer downgrade.
dawgdoc said:
Correct with the NE4 bootloader you can not downgrade without bricking your phone. Downgrades went out the window with MJB (Jellybean 4.3) and have not returned. Meaning you can never downgrade on MJB, NE4, NJ1, or NJ2.
With LK3 you could go upto MG2 (JB 4.1.2) or MJ2 (the leaked release of 4.3) and still be able to downgrade. I have downgraded while on MJ2 with no issues. I went down to LK3 from MJ2 in order to utilize the free sim unlock, I think DocHoliday mentioned it earlier. Since then I have gone back up to MJB and then to NE4, so I can no longer downgrade.
Click to expand...
Click to collapse
Hey dawgdoc ,
I just turned another device into paper weight man .It had LK3 and i tried to flash MJB via odin stock firm from company but end of odin it f**king hard bricked the phone is there something i messed up . The bootloader were from DLK3 (rooted and twrp) but if i was just flashing new firm from odin it was not supposed to brick it just wondering what am i missing throwing my 500 for 2 phones into garbage !
Do you get any response from the device at all?
Plug into the computer and open device manager. Does it show connected as QHSUSB_DLOAD, or something else?
Did odin complete the flash and say PASS when it was done?
Sent from my SGH-T999 using Tapatalk
Where did you get an Odin flashable 4.3 stock rom? As far as I know AT&T never released an official one, nor have I ever seen one on sammobile. There may have been one put together by either loserskater or enewman17, but that one is rather hard to find.
Going from LK3 to MJB should cause no problems, I have done so myself. Going from NE4 to MJB is risking bricking your phone. I have read of some who have recovered from the bricking caused by the NE4 to MJB downgrade. Those used a debrick image on an external sdcard, the image was based on the bootloader that was running before the phone/device was bricked. There may be in the forums, but I'm not sure of that.
---------- Post added at 07:49 PM ---------- Previous post was at 07:25 PM ----------
dawgdoc said:
Where did you get an Odin flashable 4.3 stock rom? As far as I know AT&T never released an official one, nor have I ever seen one on sammobile. There may have been one put together by either loserskater or enewman17, but that one is rather hard to find.
Going from LK3 to MJB should cause no problems, I have done so myself. Going from NE4 to MJB is risking bricking your phone. I have read of some who have recovered from the bricking caused by the NE4 to MJB downgrade. Those used a debrick image on an external sdcard, the image was based on the bootloader that was running before the phone/device was bricked. There may be in the forums, but I'm not sure of that.
Click to expand...
Click to collapse
This person tells how he used a debrick image on a device he bricked flashing NE4 and provides some links. And the post following that one has links to NE4 debrick images.
Thanks guys for helping me out, i tried debrick with 64 gb class 10 sd and it worked now trying to flash firmware again .If any tips will be great, just read DocHoliday77 post that you need to remove sd before odin back to firmware. So after that, i wont have to boot with sd card is that right. Thanks for saving my eyes burning through frames by frame .. ( I still didn't get it why it's got bricked i was coming from lk3 4.1.1 to mjb 4.3 !)
rns416 said:
Thanks guys for helping me out, i tried debrick with 64 gb class 10 sd and it worked now trying to flash firmware again .If any tips will be great, just read DocHoliday77 post that you need to remove sd before odin back to firmware. So after that, i wont have to boot with sd card is that right. Thanks for saving my eyes burning through frames by frame .. ( I still didn't get it why it's got bricked i was coming from lk3 4.1.1 to mjb 4.3 !)
Click to expand...
Click to collapse
I need a Quick help please i tried flashing mjb but phone still wont boot without sd card . Now download mode does not stay it comes and go the only option is i can get to recover from stock . So i need to flash bootloaders and modem only right from stock recovery i can not flash cwm or twrp .
After Debrick force phone to to boot from internal storage
Thanks DocHoliday77 and Larry2999 , I followed direction from Larry and used DocHoliday files . After debrick i was unable to boot without Debrick image from sdcard. Even after i flashed MJB with odin it was not working . All you have to do is to flash bootloader and modem to make it boot from internal storage . I add all the files in the link below.
I followed this direction http://forum.xda-developers.com/showthread.php?t=2608260&page=2 . And files were uploaded by DocHoliday77 in one of the posts that i can not remember the actual link . I used philz_touch_6.48.4-d2lte.tar.md5 for recovery that worked for me twrp for some reason was not working.
dawgdoc said:
Where did you get an Odin flashable 4.3 stock rom? As far as I know AT&T never released an official one, nor have I ever seen one on sammobile. There may have been one put together by either loserskater or enewman17, but that one is rather hard to find.
Going from LK3 to MJB should cause no problems, I have done so myself. Going from NE4 to MJB is risking bricking your phone. I have read of some who have recovered from the bricking caused by the NE4 to MJB downgrade. Those used a debrick image on an external sdcard, the image was based on the bootloader that was running before the phone/device was bricked. There may be in the forums, but I'm not sure of that.
---------- Post added at 07:49 PM ---------- Previous post was at 07:25 PM ----------
This person tells how he used a debrick image on a device he bricked flashing NE4 and provides some links. And the post following that one has links to NE4 debrick images.
Click to expand...
Click to collapse
Thanks alot dawgdoc that link saved me from ......
Now that i am back again i really want to enjoy lollipop i have MJB how can i get it please . Any help do not want to brick it again . !
rns416 said:
Thanks alot dawgdoc that link saved me from ......
Now that i am back again i really want to enjoy lollipop i have MJB how can i get it please . Any help do not want to brick it again . !
Click to expand...
Click to collapse
To run a Lollipop ROM you will need to be on at least the NE4 bootloader and modem. You can find them in his NJ1 or NJ2 threads. It is not necessary to flash the ROMs, just the bootloader and modem. If you don't flash some KitKat or LP rom after updating the bootloader and modem, you may have issues running the MJB ROM. If you want newer than the NE4 bootloader and modem, be sure you flash them each in order, don't skip NE4 or NJ1 if you are going all of the way to NJ2. All of the mentioned bootloader/modem files can be found on enewman17's AFH profile.
dawgdoc said:
To run a Lollipop ROM you will need to be on at least the NE4 bootloader and modem. You can find them in his NJ1 or NJ2 threads. It is not necessary to flash the ROMs, just the bootloader and modem. If you don't flash some KitKat or LP rom after updating the bootloader and modem, you may have issues running the MJB ROM. If you want newer than the NE4 bootloader and modem, be sure you flash them each in order, don't skip NE4 or NJ1 if you are going all of the way to NJ2. All of the mentioned bootloader/modem files can be found on enewman17's AFH profile.
Click to expand...
Click to collapse
I will try DirtyUnicorn seems good or give me any suggestion . So you said just update NE4 bootloader and modem in recovery then flash LP rom (without rebooting) thats it without installing whole NE4 .
rns416 said:
I will try DirtyUnicorn seems good or give me any suggestion . So you said just update NE4 bootloader and modem in recovery then flash LP rom (without rebooting) thats it without installing whole NE4 .
Click to expand...
Click to collapse
I haven't tried any LP roms, so the best I could do is parrot back what I read in the threads. Correct on the flashing instructions, I have read of many doing so to go to LP. Others flashed the ROM first and then booted. They had issues with wifi, bluetooth, data, calls, etc until they went back and flashed the bootloader and modem.