Related
I rooted my phone yesterday using the toolkit from the development forums. I created a backup of my stock ROM before I flashed anything new but apparently I messed that up b.c trying to restore that, the toolkit told me I have no restore files. Anyway I flashed the unofficial cm10 build and I am having some radio issues, so I wanted to go back to stock until a more official build comes out. I have tried doing that through the toolkit a few times but it continues to fail.
Looking around online I found the stock ROM from Google and dl'd it (mysid-imm76k-factory-98d21321.tar is the file) I am pretty noobish when it comes to flashing stuff and i have never seen a .tar but I found that Odin can flash .tar. so my plan was to get the odin app flash that file and hope I did everything okay.
A couple questions: is this going to work okay? Do I need to flash kernels or radios or anything else or is this a complete return to stock? Will this keep me rooted and unlocked?
you dont need ODIN.
use this:
http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
you dont need ODIN.
use this:
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thank you. Don't know why I couldn't find that.
Any chance you could explain what odin is/.tar files are? And how they are different?
unrefine said:
Thank you. Don't know why I couldn't find that.
Any chance you could explain what odin is/.tar files are? And how they are different?
Click to expand...
Click to collapse
ODIN is a firmware restore program for all samsung phones.
here's a decent webpage on what ODIN is/does
http://forum.jakar.co/android-hack/1341254634/
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.
As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?
huz666 said:
As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?
Click to expand...
Click to collapse
If you are getting errors in both odin and cwm, it sounds like it is a root issue. In other words, it sounds like the apps are being denied access to root and therefor cannot flash. Both odin and cwm are able to generate logs so you can tell the reason for the fail. Personally, I would recommend flasing twrp recovery instead of cwm since it seems to simplify alot and is a little better for our device. Without knowing exactly why the flash is failing, i would just recommend to try and re-root the phone again.
Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.
Perseus71 said:
Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.
Click to expand...
Click to collapse
Yes the phone was in downloading mode. I couldn't find any posts that thought that I would brick my phone for sure by downgrading so I thought I would try. Could I go back to the 4.3 Stock ROM with some degree of confidence?
Yes you can go back to 4.3 Stock.
Perseus71 said:
Yes you can go back to 4.3 Stock.
Click to expand...
Click to collapse
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.
huz666 said:
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.
Click to expand...
Click to collapse
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk
serio22 said:
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
.
Thanks for the advice. I think I'll just quit while I'm only slightly behind now and remain on 4.3 Stock. I appreciate everyone's help and suggestions.
Downgrade from CM11 4.4.2 to 4.3 on I747
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747
You seriously need to do some reading
Sent from my SGH-T999 using Tapatalk
nitagro said:
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747
Click to expand...
Click to collapse
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.
Perseus71 said:
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.
Click to expand...
Click to collapse
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.
nitagro said:
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.
Click to expand...
Click to collapse
Please Read through this Thread. For Future Reference, all Odin Files for S3 in general are looked up by unique Keyword Root66. That thread is the right place for you to post errors or issues. If there's no 4.3 image for your phone there, you can post a request as well.
For your immediate Problem, there is a an alternate ATT StockMod Rom by @saranhai Please see this thread. Pay particular attention to the mandatory requirement of flashing a particular modem beforehand.
I think i Have bricked my phone I was on the new 4.4 I flashed back to [ROM][RESTORE][5-12-13]Back to UNROOTED Stock with Auto Flash Count Reset .. And then was taking the OTA back to 4.3. When it rebooted it gets stuck on the Samsung note2 screen and sits there. I can't get intoo any kind of recovery it brings up the connect to kies screen that says Firmware Upgrade encountered an issue connect to kies. I have tried flashing recovery again with odin to no avail I have also tried flashing the unbrick.tar file that is floating aroung here. I cant get anything to flash everything fails. I can get into download mode.. PLEASE HELP!!!!
jyerly said:
I think i Have bricked my phone I was on the new 4.4 I flashed back to [ROM][RESTORE][5-12-13]Back to UNROOTED Stock with Auto Flash Count Reset .. And then was taking the OTA back to 4.3. When it rebooted it gets stuck on the Samsung note2 screen and sits there. I can't get intoo any kind of recovery it brings up the connect to kies screen that says Firmware Upgrade encountered an issue connect to kies. I have tried flashing recovery again with odin to no avail I have also tried flashing the unbrick.tar file that is floating aroung here. I cant get anything to flash everything fails. I can get into download mode.. PLEASE HELP!!!!
Click to expand...
Click to collapse
Looks like your having the same issue I was having. Check the 4.4 update thread about rwilco's modified restore. The one with the sboot or boot.ini in it works. Trust me It works I just got my phone back to 4.3 then back up to 4.4. If u have any questions pm me.
puffyjello said:
Looks like your having the same issue I was having. Check the 4.4 update thread about rwilco's modified restore. The one with the sboot or boot.ini in it works. Trust me It works I just got my phone back to 4.3 then back up to 4.4. If u have any questions pm me.
Click to expand...
Click to collapse
puffyjello,
what version of Odin did you use? reboot checked/unchecked?
ive used three different versions and have been unsuccessful in getting out of the samsung logo screen.
im having the same problems as the OP.
thanks for the help!!!
arichter35 said:
puffyjello,
what version of Odin did you use? reboot checked/unchecked?
ive used three different versions and have been unsuccessful in getting out of the samsung logo screen.
im having the same problems as the OP.
thanks for the help!!!
Click to expand...
Click to collapse
If it's the Samsung screen u need to go into factory recovery and do a factory reset. If u stuck at the note 2 screen u need to use odin and use the modified restore that was posted on the 4.4 update discussion thread. i think i used odin 3.4 or something. Ill turn my computer on to see.
---------- Post added at 04:25 AM ---------- Previous post was at 04:11 AM ----------
arichter35 said:
puffyjello,
what version of Odin did you use? reboot checked/unchecked?
ive used three different versions and have been unsuccessful in getting out of the samsung logo screen.
im having the same problems as the OP.
thanks for the help!!!
Click to expand...
Click to collapse
ok to make things short as possible. i dont want this discussion to get out of hand and i will be as helpful as possible. I was stuck on the samsung note 2 screen. i couldnt get past it. tried everything for like 2 days and then rwilco12 posted his modified 4.3 restore on page 50 of the Note II - the 4.4.2 update - discussion thread. all i did was flash that through Odin3 v3.04. just reboot checked on PDA. nothing else. when it rebooted it took a while but it booted to the samsung screen that changes colors. it stuck there so what i did was reboot into recovery mode and did a factory reset. after that it booted into 4.3 no problems.
---------- Post added at 05:06 AM ---------- Previous post was at 04:25 AM ----------
arichter35 said:
puffyjello,
what version of Odin did you use? reboot checked/unchecked?
ive used three different versions and have been unsuccessful in getting out of the samsung logo screen.
im having the same problems as the OP.
thanks for the help!!!
Click to expand...
Click to collapse
Any progress?
puffyjello said:
Looks like your having the same issue I was having. Check the 4.4 update thread about rwilco's modified restore. The one with the sboot or boot.ini in it works. Trust me It works I just got my phone back to 4.3 then back up to 4.4. If u have any questions pm me.
Click to expand...
Click to collapse
Up and running thank you!
jyerly said:
Up and running thank you!
Click to expand...
Click to collapse
Your welcome. Glad i could help. what about you arichter35??
It worked!
Thank you!!
If I go back to mc2 through billards file to get all the ota's in order will go through the same bs? If so, I will use the other method that was posted using the ota 4.4.2 file on XDA...
I appreciate all the help!
Sent from my SPH-L900 using XDA Free mobile app
arichter35 said:
It worked!
Thank you!!
If I go back to mc2 through billards file to get all the ota's in order will go through the same bs? If so, I will use the other method that was posted using the ota 4.4.2 file on XDA...
I appreciate all the help!
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
Honestly I'm not quite sure. What u could do is use billards mc2 then ota to 4.3 and when u reboot if u soft brick again just use the modified restore again. If u want to try it go ahead no harm in trying. i might try it later but chances are its going to fail anyways. Since downgrading from 4.4 is what caused the problem in the first place.
puffyjello said:
Honestly I'm not quite sure. What u could do is use billards mc2 then ota to 4.3 and when u reboot if u soft brick again just use the modified restore again. If u want to try it go ahead no harm in trying. i might try it later but chances are its going to fail anyways. Since downgrading from 4.4 is what caused the problem in the first place.
Click to expand...
Click to collapse
Puffyjello,
I simply flashed the OTA 4.4.2 in stock recovery and rebooted to the update no problem. No new Odin's of MK4 or anything, just flashed the OTA after i used your method to unbrick.
I then Odin'd Philz, flashed SuperSu and now im rooted and on 4.4.2, no problems.
Again, thanks for the help with the 'unbricking'!
arichter35 said:
Puffyjello,
I simply flashed the OTA 4.4.2 in stock recovery and rebooted to the update no problem. No new Odin's of MK4 or anything, just flashed the OTA after i used your method to unbrick.
I then Odin'd Philz, flashed SuperSu and now im rooted and on 4deeded problems.
Again, thanks for the help with the 'unbricking'!
Click to expand...
Click to collapse
Np. And what I thought u meant was going back to mc2 from 4.4 then ota to 4.3 and see if it bricks again. I wasnt sure if it would. Ne ways I'm glad everything's fixed. And I hope anybody that has this problem follows what fixed our phones. you guys take care. Running stock deodexed ne2 and loving it. Can't wait to try out their s5feat rom when they release it.
Does the LJC_Stock_With_Count_Reset[FINAL].zip still work after ota 4.4.2 ?
This to me is the best back to unrooted stock. It resores the LJC PIT, kernel, and modem. Compared to all the other stock roms; I find this one read and writes easier with QPST & CDMA-ws.
Im currently running stock rooted MC2 with stock LJ1 baseband.
In my opinion so far this is the recipe for this phone. Oldest basebands seem to have better battery life. I'm not really sure if the newer modems are actually faster causing the battery to drain faster, or generate more compression and share more detailed information with big brother which would also cause it to slow down.
I have this theory the manufacturers purposely slow peoples equipment down with the OTA after the first couple years to motivate them to buy the newer model flagships that supports the same software more efficiently. maybe I'm just crazy but can someone please try the back to LJC stock unrooted. and let me know if it works better than the back to stock MC2.
plus it could possibly be better doing all the OTA to 4.4.2 from an older stock rom.
New galaxy user, here its a s3 for ATT 4.4.2 i747CUCFNE4. I have rooted using the Cf Auto-Root method.
Along the lines of trying to flash a new task manager apk, (for I had to factory reset my phone because the original task manager was missing) I came across a thread that had s5 apps (settings apk) and tried flashing this apk(don't laugh I know.) Then I couldn't get my phone to boot through the standard setup wizard. So I tried booting into recovery and factory resetting my phone clearing cache, dalvik, and partition.
My biggest problem arose when I chose to format system from ghe recovery.
I know all this can be fixed with odin but I can't find a 4.4.2 os link, I have read I can't simply downgrade my os. A link to a 4.4.2 stock rom thread would be greatly appreciated. I also have the Ktoonsez kernel installed if that makes any difference.
AT&T never released a full 4.4.2 ROM. AT&T released 4.3 and 4.4.2 via OTA updates only.
Since you are on the NE4 bootloader, do not flash anything that will attempt to downgrade the bootloader or the modem. A mismatched modem/bootloader combination may cause other problems.
Have a look here: http://forum.xda-developers.com/showthread.php?t=2789917
Ok I just reviewed your link in your response but just to be clear I'm starting where it says step 3: stock deodex and root and finishing the walkthrough from there?
And also will this reset me to my factory kernel?? Either or it doesnt matter to me I'm still trying to find one that I find suitable.
And I appreciate the speedy response you've been a huge help.
If you just want to get your phone up and running, I would flash Philz and then CM11. Confirm the bootloader and modem then decide if a stock ROM would be best.
I am always paranoid when it comes to flashing bootloaders on the s3 so I prefer to know exactly whan my phone is running.
I have never used the thread I linked because I no longer have an s3 i747m. Infact, I haven't had my s3 for several months.
Ok and my last question is you can flash Philz and CWM 11 through odin?
Nevermind I see it now greatly appreciated
I hope it all goes well. With CM11, you will also need to flash Gapps via CWM as CM11 does not include certain apps such as the Play store.
Now odin wont recoginize or open any of my rom files. Li see the rom im trying to flash by name but when i click open it only opens the next folder instead of initiating the flash. I really just need someone who has a 4.4.2 stock rom in md5 format.(edited or not.)
As a last effort if i get no answer im going to try to downgrade to another os and reupdate to 4.4.2 right after. Ive been searching for days now all i see are guides from how to upgrade to a different os . If it does include 4.4.2 they only posted the update and not the entire rom.
And when i do find someone posting a full rom for 4.4.2 its either not for 747i or its not a md5 file so someone plz help me.
glyph2 said:
Now odin wont recoginize or open any of my rom files. Li see the rom im trying to flash by name but when i click open it only opens the next folder instead of initiating the flash. I really just need someone who has a 4.4.2 stock rom in md5 format.(edited or not.)
As a last effort if i get no answer im going to try to downgrade to another os and reupdate to 4.4.2 right after. Ive been searching for days now all i see are guides from how to upgrade to a different os . If it does include 4.4.2 they only posted the update and not the entire rom.
And when i do find someone posting a full rom for 4.4.2 its either not for 747i or its not a md5 file so someone plz help me.
Click to expand...
Click to collapse
DO NOT downgrade to a bootloader older than your NE4 -- doing so will cause a hard brick.
You did mean i747 instead of 747i, didn't you?
Odin is designed to not flash any stock rom that would install a bootloader than the one on your phone. this is to save you from hard bricking your phone. Since you are on 4.4.2, any stock rom in a .tar.md5 format has an older bootloader than your NE4. As far as I know, the only stock NE4 rom on the forums is in a .zip format for flashing from recovery, it was posted by enewman17. (The thread audit13 linked.) If you tried to flash an older bootloader and baseband package through recovery you will probably hardbrick the phone.
Otherwise, there are roms based on TW in the forums: S3Rx, TMS3KK, Likewise, and others. Some use the stock kernel, others give you an option from their Aroma install. The iBubbler's kernel in a couple of these roms is reported to be excellent.
I'm guessing you pulled your S5 apk from either the S3Rx or Likewise thread.
I appreciate everyones feedback and guideance. Yeah I meant i747. It gets pretty easy to misread something when all you've been doing was researching roms and guides. And now its back to researching and finding one of the roms you mentioned. Much appreciated everyone I hope u all have a blessed day..
i know this a zip , but maybe could find help in the thread.
http://forum.xda-developers.com/showthread.php?t=2788357
good luck.
"all I can really do, is stay out of my own way and let the will of heaven be done"