[Q]4.3 I747 Root Help!!!! - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Tonight I tried to root my ATT Galaxy S3 I747UCUEMJB which is running on 4.3.
I rooted with Odin3 v1.85 and CF-AutoRoot-d2att-dtuc-samsungsghi747.tar.md5
After is rebooted I was greeted with the friendly images attached below. Any ideas on what to do?
I have been looking on this forum and others with no success. Someone please help!

u need to update Supersu in Playstore..

fr3d0x said:
u need to update Supersu in Playstore..
Click to expand...
Click to collapse
Thank you. I feel stupid for not checking that...

Hey Chris. I have the same phone. And just in case you have issues with flashing any roms I made this http://forum.xda-developers.com/showthread.php?t=2552952
It differently helped and now I'm able to flash. Long story short that UCUEMJB bootloader is new and some roms even though are for 4.3 may not flash because the Dev hasn't updated the bootloaders. You may come across some people telling you to update your bootloader which you have to careful. I made the mistake of flashing the loader and it hard bricked my phone and that linked helped me and theramsey3 was very helpful to get me back and running. It can be confusing about what loader to update. My advice if you flash any rom either post or as the Dev if they updated to the UCUEMJB bootloader. But just in case If you mess up and hard brick your phone that link will save your phone.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Can someone direct me to a tutorial on how to root my Galaxy S3 AT&T (SGH-I747) running Android 4.3. All I want is to root it and have SU so that I can remove bloatware and use wifi teather.
I'm very worried about rooting and having my bootloader or Knox do something and brick my phone. (this will be my first time rooting) I just want to make sure I do everything right the first time.

flash it with CFAutoroot on Odin.. make sure you check your model and the file you are downloading.. if SuperSU crash after rooting update it via playstore and it will ask you to disable the knox then tap yes to disable...

when im on odin an doing the update for SuperUS do I put the update under Phone or PDA?

Related

[Q] Rooting SGH-T889v

I hate starting new threads cause, well, everyone else hates it lol.
But my hand is forced. I want the multi-window feature on my phone and like the impatient people we are, I want it now. Well the only problem is that the only way of getting said feature is too root your phone and install a custom ROM. Which is perfectly fine, I have no quarrels with custom roms, in fact I love them, I think the developers are amazing and truly unlock the full potential of the phone when they do make custom ROMS. However, one thing I do notice is that sometimes the roms become buggy and laggy after a while. Anyway's I digress...
My true reason too create this thread is that I need help in rooting my phone as its new and I paid full price for it, the last thing I want to do is brick it. By all means I am no noob, I've been rooting all my phones. Its just that I see that there is no direct root method for the t889v, I would assume it to be similar to t889 and with an addition to flashing the t889v modem/radio.
But if there is someone out there, who could assist me in successfully doing so I will be mighty grateful to them. I would prefer it be a person who has rooted their t889v.
Did you successfully get this resolved? Just got the Canadian version of T889V note2. I'd love to control my privacy a bit more, such as feeding malicious apps a fake contact list instead of letting then steal everything
Sent from my SGH-T889V using xda app-developers app
If by direct root you mean exploit, there isn't any I'm aware of. However rooting with Odin and either a stock injected ROM (if you want to avoid tripping your counter) or Chainfire's AutoRoot, or CWM and flashing a superuser zip as usual works just fine.
MCRHAZ said:
I hate starting new threads cause, well, everyone else hates it lol.
But my hand is forced. I want the multi-window feature on my phone and like the impatient people we are, I want it now. Well the only problem is that the only way of getting said feature is too root your phone and install a custom ROM. Which is perfectly fine, I have no quarrels with custom roms, in fact I love them, I think the developers are amazing and truly unlock the full potential of the phone when they do make custom ROMS. However, one thing I do notice is that sometimes the roms become buggy and laggy after a while. Anyway's I digress...
My true reason too create this thread is that I need help in rooting my phone as its new and I paid full price for it, the last thing I want to do is brick it. By all means I am no noob, I've been rooting all my phones. Its just that I see that there is no direct root method for the t889v, I would assume it to be similar to t889 and with an addition to flashing the t889v modem/radio.
But if there is someone out there, who could assist me in successfully doing so I will be mighty grateful to them. I would prefer it be a person who has rooted their t889v.
Click to expand...
Click to collapse
Hey i messed up my wind note flashed the t889v modem and it screwed it up, is it possible you can link me with a nandroid backup of your phone,
Thanks in advance
How to root Windmobile T889v on Android 4.3
Darkshado said:
If by direct root you mean exploit, there isn't any I'm aware of. However rooting with Odin and either a stock injected ROM (if you want to avoid tripping your counter) or Chainfire's AutoRoot, or CWM and flashing a superuser zip as usual works just fine.
Click to expand...
Click to collapse
Anyway confirmed step by step to root T889v on 4.3? The firmware ends in MK4, if that matters. Thanks for any help in advance.
subaron said:
Anyway confirmed step by step to root T889v on 4.3? The firmware ends in MK4, if that matters. Thanks for any help in advance.
Click to expand...
Click to collapse
Will CF-Autoroot work with the T889v?
I don't know if CF-Autoroot will work on 4.3, but since you're going to trip the KNOX e-fuse anyway, you might as well:
Get Odin3 3.09 (the latest available version AFAIK)
Download the latest SuperSU zip update file and put it on your SD card
Flash the latest t0tle Odin flashable image. (Other HSPA t0lte variants like t0lteatt and t0ltetmo should also work)
Or, if you've got a tar binary (like Cygwin's if you're on Windows) available on your computer, the latest Clockworkmod image, which you'll rename to recovery.img and put in a tar file with the command: tar -H ustar -cf clockworkmod.tar recovery.img
Reboot to recovery
Backup your current ROM and data, just in case.
Install the SuperSU zip.
Reboot.
The stock, unmodified ROM might throw error messages about KNOX having been tripped. I haven't touched the 4.3 bootloaders because I haven't needed them yet. I'll leave figuring how to deal with those up to you, there's a few threads on that topic.
I did root my T889v(updated WindMobile stock ROM 4.3+TMobile radio) using CF-Autoroot. Downloaded the one for N7100(the one I searched on web for T889 actually doesn't work, this N7100 one from CF-Autoroot official web site worked without problem) and rooted. Then went to market to install SuperU, then it asked whether to disable Knox, I clicked yes and root was done.
The Knox counter is tripped anyway, but I don't care.
Dont work for me ...
cr2069 said:
I did root my T889v(updated WindMobile stock ROM 4.3+TMobile radio) using CF-Autoroot. Downloaded the one for N7100(the one I searched on web for T889 actually doesn't work, this N7100 one from CF-Autoroot official web site worked without problem) and rooted. Then went to market to install SuperU, then it asked whether to disable Knox, I clicked yes and root was done.
The Knox counter is tripped anyway, but I don't care.
Click to expand...
Click to collapse
I tried with to root with odin 3.09 and cf-auto-root (sgh-t889) & (gt-n7100) and bolth dont work... My phone model is (sgh-t889v) canadian . Can help me ?

[Q] i317 lost root after 4.1.2 update

I'm running a rooted stock I317M with nothing modified except for root. I used mrRobinson's thread h t t p :/ / forum.xda-developers.com/showthread.php?t=2004650 as a guide which worked perfectly to keep everything stock (and thus avoid tripping the flash counter) but gave me root. This morning the Canadian carriers began rolling out the 4.1.2 update OTA which failed a few times on my device so I used (GASP!) Kies to do the update. Not sure if it would have mattered OTA or Kies but I have now lost root. Has anyone managed to inject root into a stock image for the I317m yet? It looks like I could go with a custom AT&T I317 build or ADB in and manually install a custom recovery, root etc. but if possible I'm hoping to keep normal device status and not trip the flash counter.
Are you planning on turning your phone in for warranty anytime soon or do you just like the look of "Official" instead of "Modified" on your About Phone settings?
Exact same thing happened for mine, stock rooted Canadian OTA to 4.1.2 failed repeatedly, Had to use Kies as well and lost root. The main reason I wanted root was to switch off fast dormancy since my Canadian carrier doesn't support it and was killing battery. Good news is it stayed switched off.
[email protected] said:
Are you planning on turning your phone in for warranty anytime soon or do you just like the look of "Official" instead of "Modified" on your About Phone settings?
Click to expand...
Click to collapse
Not really. Originally it was just to make sure I'd get the update without issue when it was released. My understanding is that I can always reflash with the stock firmware I have from Sammobile and it will reset the flash counter + set the status back to normal if the need arose but also thought it easier to just unroot, reboot and uninstall SU if possible.
chris19000 said:
Not really. Originally it was just to make sure I'd get the update without issue when it was released. My understanding is that I can always reflash with the stock firmware I have from Sammobile and it will reset the flash counter + set the status back to normal if the need arose but also thought it easier to just unroot, reboot and uninstall SU if possible.
Click to expand...
Click to collapse
Cool.... Honestly, I never worry about tripping the counter unless I need to turn in for replacement/warranty repair. Apparently, this seems to work just fine: http://forum.xda-developers.com/showthread.php?t=2073141&highlight=lost+root
m4runner said:
Exact same thing happened for mine, stock rooted Canadian OTA to 4.1.2 failed repeatedly, Had to use Kies as well and lost root. The main reason I wanted root was to switch off fast dormancy since my Canadian carrier doesn't support it and was killing battery. Good news is it stayed switched off.
Click to expand...
Click to collapse
First time I've actually heard of fast dormancy. My battery life has actually been pretty good and that with fairly varied, heavy use. Have to look more into it. I rooted primarily for backing up (TB), remote file sharing and just plain messing around.
[email protected] said:
Cool.... Honestly, I never worry about tripping the counter unless I need to turn in for replacement/warranty repair. Apparently, this seems to work just fine: http://forum.xda-developers.com/showthread.php?t=2073141&highlight=lost+root
Click to expand...
Click to collapse
Thanks R1K, I looked at that earlier and still might try it after a little more in depth reading if nothing else presents itself. I use the camera fairly extensively and although it looks like the camera is only affected when patching the exploit I have to be a little cautious since I use it for work. Plus the easy unroot/stock return part :good:
m4runner said:
Exact same thing happened for mine, stock rooted Canadian OTA to 4.1.2 failed repeatedly, Had to use Kies as well and lost root. The main reason I wanted root was to switch off fast dormancy since my Canadian carrier doesn't support it and was killing battery. Good news is it stayed switched off.
Click to expand...
Click to collapse
One option which is what I did, was to download the 4.1.2 update from sammobile.
I then used mobile odin to flash it which has the ability to protect root.
So now I am stock rooted on latest firmware device status is normal
---------- Post added at 04:54 PM ---------- Previous post was at 04:42 PM ----------
[email protected] said:
Cool.... Honestly, I never worry about tripping the counter unless I need to turn in for replacement/warranty repair. Apparently, this seems to work just fine: http://forum.xda-developers.com/showthread.php?t=2073141&highlight=lost+root
Click to expand...
Click to collapse
Doubt this will work.
The whole way this gained root was via the exynos exploit.
This firmware I am pretty sure has patched it.
Exynos abuse says no but voodoo app says yes.
I can confirm the exploit is patched in this new firmware so I suspect this will close any holes used by exynos abuse app to root phone.
Canadoc said:
One option which is what I did, was to download the 4.1.2 update from sammobile.
I then used mobile odin to flash it which has the ability to protect root.
So now I am stock rooted on latest firmware device status is normal
---------- Post added at 04:54 PM ---------- Previous post was at 04:42 PM ----------
Doubt this will work.
The whole way this gained root was via the exynos exploit.
This firmware I am pretty sure has patched it.
Exynos abuse says no but voodoo app says yes.
I can confirm the exploit is patched in this new firmware so I suspect this will close any holes used by exynos abuse app to root phone.
Click to expand...
Click to collapse
Thank you Canadoc. Might be the best bet for me too. I did a TB backup just prior to the update so maybe I'll flash back to 4.1.1 with the root injected ROM in odin and then flash the 4.1.2 update from sammobile from mobile odin. Otherwise looks like it might be a custom i317 build for me. CWM sure sounds nice right now
For those trying to get multiveiw update and are rooted.... it is much much easier ti go get the firmware from sammobile.com then flash it with mobile odin with the ever root option.. all done :thumbup:
Sent from my SGH-I317 using xda premium
twanskys204 said:
For those trying to get multiveiw update and are rooted.... it is much much easier ti go get the firmware from sammobile.com then flash it with mobile odin with the ever root option.. all done :thumbup:
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
That's for sure. I'm going to go back to root injected stock 4.1.1 and start from scratch.
chris19000 said:
That's for sure. I'm going to go back to root injected stock 4.1.1 and start from scratch.
Click to expand...
Click to collapse
Worked as planned... more or less. Had to do a factory reset and flash twice to get 4.1.1 to boot but from there installed mobile odin, extracted and flashed from 4.1.2 (from sammobile and copied to external SD) and good to go. Now, if you want to go stock with root and for whatever reason don't want to/can't use mobile odin, head over to this thread http://forum.xda-developers.com/showthread.php?t=2004650&page=26 mrRobinson is working on injecting root into the stock builds.
Cheers.
Which is the better way ?
chris19000 said:
Worked as planned... more or less. Had to do a factory reset and flash twice to get 4.1.1 to boot but from there installed mobile odin, extracted and flashed from 4.1.2 (from sammobile and copied to external SD) and good to go. Now, if you want to go stock with root and for whatever reason don't want to/can't use mobile odin, head over to this thread http://forum.xda-developers.com/showthread.php?t=2004650&page=26 mrRobinson is working on injecting root into the stock builds.
Cheers.
Click to expand...
Click to collapse
I use the Mr. Robinsons thread to stock my device to 4.1.1 but when i did . it always stuck on the Samsung logo after rebooting.
so i have to put my phone in recovery mode and factory restore.
this wasy right now i have root on 4.1.1 .
but i wanna know the best way to update my phone to 4.1.2
becasue i know .. with OTA i will loose my root.
please help.
prashant19p said:
I use the Mr. Robinsons thread to stock my device to 4.1.1 but when i did . it always stuck on the Samsung logo after rebooting.
so i have to put my phone in recovery mode and factory restore.
this wasy right now i have root on 4.1.1 .
but i wanna know the best way to update my phone to 4.1.2
becasue i know .. with OTA i will loose my root.
please help.
Click to expand...
Click to collapse
Hi prashant there are a number of ways you can update OTA without losing root but of the easy ones I can only speak personally about one of them - Mobile Odin - which is what I used. It's a paid app but it gives you the option for EverRoot which maintains root across roms and automatically installs itself and SU in the new rom. Hate to ask, but are you sure you flashed the right rom? He has it listed as the new! Bell rom under January. If you flash that with his directions it should work - that being said though I did have to flash it twice myself to get it to work. One flash with odin, stuck on logo, back to regular recovery, wipe cache, download mode and reflash with odin, worked that time around. By that time I had mobile odin and flashed the regular update without root that way but mobile odin kept my root.
If you're looking to retain or regain root after ota, this is the easiest way imo. Just answered it in this thread.
http://forum.xda-developers.com/showthread.php?t=2156741
Froid said:
If you're looking to retain or regain root after ota, this is the easiest way imo. Just answered it in this thread.
http://forum.xda-developers.com/showthread.php?t=2156741
Click to expand...
Click to collapse
Thanks Froid. SuperSU seemed to work for some folks too if they dropped the dime for the PRO version. I did see some instances where neither worked too though, but not enough details to say why.
all you need to do is just reflash with odin rooted 4.1.1 stock rom then once that is done goto play store and get voodoo ota rootkeeper make backup then temp unroot then get the ota 4.1.2 update when finished goto to ota rootkeeper and restore root works just fine and u keep root.

[GUIDE] Restore Bootloader Bricked S3 to Stock Firmware AFTER 4.3 update. No Jtag

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.

[Q] Samsung galaxy s3 i747M unroot on 4.3

Hi, im new on XDA but have quite a lot experience whit phone.
I tryed to root my samsaung galaxy s3 from Rogers (same as att) i747M whit CF-Auto root (im on android 4.3 jellybean).
I did it my phone is still working. I didnt flash a new recovery or anything.
Now i woudlike to remove root finally.
*the counter of the new Knox is set now to 0X1 but personnally i dont really mind.
The problem is that i woudlike to remove the root. I dont whant to downgrade i like 4.3 jellybean. (Anyway Att s3 cant be downgraded it will result to a soft brick)
I dont know how to remove the root and i woudlike to learn how to do it on my Samsung galaxy s3.
Thanks
(i was wondering about if i download the 4.3 stock Rom and i flash it will odin will it brick even if its on the same bootloader? because thats not downgrading...)
Thank you in advance for helping me out fast!
killer0123 said:
Hi, im new on XDA but have quite a lot experience whit phone.
I tryed to root my samsaung galaxy s3 from Rogers (same as att) i747M whit CF-Auto root ( su in the app itself4.3 jellybean).
I did it my phone is still working. I didnt flash a new recovery or anything.
Now i woudlike to remove root finally.
*the counter of the new Knox is set now to 0X1 but personnally i dont really mind.
The problem is that i woudlike to remove the root. I dont whant to downgrade i like 4.3 jellybean. (Anyway Att s3 cant be downgraded it will result to a soft brick)
I dont know how to remove the root and i woudlike to learn how to do it on my Samsung galaxy s3.
Thanks
(i was wondering about if i download the 4.3 stock Rom and i flash it will odin will it brick even if its on the same bootloader? because thats not downgrading...)
Thank you in advance for helping me out fast!
Click to expand...
Click to collapse
Im having the same problem. Cant downgrade to any version. Can't unroot phone, I have yhe the s3 i747 also on 4.3. Im kind.of.sad nobody has.replied to this. I tried unrooting removing.supersu via inapp permanent unroot option, then using rootbrowser to delete su files from system/bin and system/xbin. ( there wasnt any), root checker said my phone didny have root access.all I wanna do is upgrade to thr newest version lol then root that. Why does it.habe ti be so hard?
Nico de Pontiac said:
Im having the same problem. Cant downgrade to any version. Can't unroot phone, I have yhe the s3 i747 also on 4.3. Im kind.of.sad nobody has.replied to this. I tried unrooting removing.supersu via inapp permanent unroot option, then using rootbrowser to delete su files from system/bin and system/xbin. ( there wasnt any), root checker said my phone didny have root access.all I wanna do is upgrade to thr newest version lol then root that. Why does it.habe ti be so hard?
Click to expand...
Click to collapse
This will get you to the 4.4.2 stock update: http://forum.xda-developers.com/showthread.php?t=2789917
It depends on you having a custom recovery. It does provide a way to go back to the stock recovery once you are updated. I believe the same devolper has also posted the most recent update to NJ1 in a separate thread.
wifi not working now, and didnt update.
dawgdoc said:
This will get you to the 4.4.2 stock update: http://forum.xda-developers.com/showthread.php?t=2789917
It depends on you having a custom recovery. It does provide a way to go back to the stock recovery once you are updated. I believe the same devolper has also posted the most recent update to NJ1 in a separate thread.
Click to expand...
Click to collapse
it let me flash from mjb or whatever to the ne4. all that did was **** up my wifi. switch it to on and it just goes right back off. plus the files for the stock recoveries were spam.
Nico de Pontiac said:
it let me flash from mjb or whatever to the ne4. all that did was **** up my wifi. switch it to on and it just goes right back off. plus the files for the stock recoveries were spam.
Click to expand...
Click to collapse
Check that your bootloader and modem/baseband are matching in version number, this seems to be important in some of the newer kernels. If they do not match, flash the modem to correspond to the bootloader. If they are matching you may want to reinstall the modem on the off chance that it flashed incorrectly the first time.
Since you didn't mention any issues with calling or data I take it that the correct APNs are installed.
I don't understand why you call the stock recovery files spam. The link at 4. leads directly to the androidfilehost page to download the file. The other is an attachment to directly download the file from xda. To each his own.

questions about knox

So i have some questions about knox. I'm new to it and sadly had the 4.3 bootloader thrust upon me.
1. Is there a way to remove it/return to a different bootloader? Not just hide it like Billards thing does
2. One way I restore my phone if it freaks out is to run a 1 click stock rooted ljc program. I was reading in a Verizon forum flashing a stock version will brick my phone does this apply for sprint? They said mk3 not mk4
3.if I no longer can use that and need to fix say a soft Brick with no recovery what should I use/do
4. What are the main things i need to be aware or with knox?
I've been reading around and all I'm finding is its security. I know that it's bootloader related but every time I odin a tar file I didn't know that affected a the bootloader. This knox cap has me not even wanting to touch my phone.
Any help would be appreciated and you will get your thanks
Anyone?
I thought all this to but I took the plunge to root and did so with kingo root it went flawless and upon boring l booting just open super su and it will ask you if you want to disable knox just click Yea and you're done and to flash roms flash philz touch recovery with odin and make sure to make a backup is stock and flash away
Sent from my SPH-L900 using xda app-developers app

Categories

Resources