yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] fenix71230:
(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.14.3250.13

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.1020.2

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__247

(bootloader) battery-status: good

(bootloader) battery-voltage: 3625mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))

finished. total time: 0.051s

I was with Anroid Revolution HD 30.0

I wiped all with CWM with format system, cache, data
[One (M7) Q&A, Help & Troubleshooting] nkk71:
OK, no problem. A couple of notes:

1- ARHD 30/31 is based on Android 4.3; and Android 4.3 is known to have (sometimes) connectivity issues (MTP and adb), these are usually solved by a combination of updated HTC drivers and/or updated firmware.

2- You are still on firmware 1.29.1020.2 and S-On, so you cannot flash unsigned firmware.... Are you interested/willing/able to getting S-Off (what's the date of you hboot)?

3- to get a ROM to your phone, you should enter CWM recovery, "adb" would work from there, you can either

------ "adb push <name of rom>.zip /sdcard/"

------ adb sideload

------ OR if you have an OTG cable, you can use that
[One (M7) Q&A, Help & Troubleshooting] fenix71230:
Yes I am interested by installing S-Off but how can I do without OS and in CWM adb doesn't detect my phone.

My hboot date is 11 March 2013.

I don't have an OTG cable yet but I have order one.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
adb should work in CWM (I had one version that didnt, but the rest should), so just because it works for me, can you download the following one:

recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)

https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc

MD5: 1c6afb14db3f305b0ad7d85d5af80bef

Once you've downloaded and verified MD5:

fastboot erase cache

fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img

fastboot erase cache

fastboot reboot-bootloader

-> enter RECOVERY

and confirm "adb devices" now shows you are connected. we'll proceed from there.

BTW: hboot 11 March 2013 is good for revone, I'll PM you a link for a ROM that works for that when you confirm adb is working.

EDIT: can you copy/paste you command prompt as you do the above mentioned fastboot commands.
[One (M7) Q&A, Help & Troubleshooting] fenix71230:
All done but when I launch CWM it shows :

E: can't mount /cache/recovery/command

E: can't mount /cache/recovery/log

E: can't open /cache/recovery/log

E: can't mount /cache/recovery/last_log

E: can't open /cache/recovery/last_log

Pc has well installed USB composite device, Mass storage USB device, won't install Android Phone : device disconnected, well installed HTC Android Phone USb Device

When I type adb devices it detect nothing I fear a hardware failure?

C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot erase cache

erasing 'cache'...

OKAY [ 0.063s]

finished. total time: 0.064s

C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot flash recovery recov

ery.img

sending 'recovery' (7422 KB)...

OKAY [ 1.143s]

writing 'recovery'...

OKAY [ 0.649s]

finished. total time: 1.794s

C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot erase cache

erasing 'cache'...

OKAY [ 0.053s]

finished. total time: 0.053s

C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.046s]

finished. total time: 0.048s

C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>adb devices

adb server is out of date. killing...

* daemon started successfully *

List of devices attached

C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
I had pretty much the same problem as you for a long time and did the following:

Uninstalled everything to do with HTC - drivers, sync etc

Downloaded a program called USBDEVIEW (google it) and then install it. Make sure you run it as administrator. It will load all the drivers installed. At this point make sure the phone is not connected. Select all the HTC drivers and delete - anything that says android usb, htc, mtp device etc

Once thats done I went to C:\windows\system32\driverstore and theres a file there I think called info cache. Right clich and change the security so that you can edit the file and then delete. Restart the computer

Try then inserting the phone to a USB 2.0 port and allow the drivers to install. Make sure you are using the HTC cable!

This is how I fixed it anyways, hope it works for you!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
This is normal.

Did you enter Recovery after that? Can you see CWM recovery screen? adb will not work in bootloader.
[One (M7) Q&A, Help & Troubleshooting] fenix71230:
Yes i can enter and see CWM, that's when my PC have detected it but won't install Android phone
[One (M7) Q&A, Help & Troubleshooting] fenix71230:
I've done all that and after my PC won't install : USB MTP device, Android Phone
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Ok, that's either a driver version and/or adb version problem. get the latest HTC drivers and adb sdk. Are you on Win 8 or 8.1 by any chance? Maybe try a different PC.

Search the threads (or google), there are plenty of answers for that. Here's one, but I can't confirm it as I havent tried it:

http://xdaforums.com/showthread.php?p=45415030#post45415030

http://xdaforums.com/showthread.php?t=2256359

PS: don't forget to hit the thanks button if someone helped!
[One (M7) Q&A, Help & Troubleshooting] fenix71230:
I have tried with 3-4 different PC, using WIndows 7 64, WIndows 8, 8.1, always the same end (adb won't detect it)

Here on my PC I am on Windows 7 x64.

Maybe it's a phone hardware problem, I don't know what to do please help :crying:
[One (M7) Q&A, Help & Troubleshooting] fenix71230:
That worked ouff thanhs for all :

I have uninstall all HTC driver and HTCF Sync Manager, downloaded the latest HTC Sync Manger, installed it then uninstalled it, just remain new HTC drivers.

Then I took adb from HTC all_in_one kit 1.2, redo the commands and I pushed my rom on my sdcard.

Thanks a lot !!! :good:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
:good::good:, glad everything worked out. Could I ask you to update the main thread title to include [SOLVED] so that others know is solved when they refer to it.
[One (M7) Q&A, Help & Troubleshooting] fenix71230:
How can I update the title ?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
go to your first post and EDIT it, at the bottom of the edit window there's GO ADVANCED, once you click that you can see the main thread title and change it to include [SOLVED]
[One (M7) Q&A, Help & Troubleshooting] 911jason:
THANK YOU THANK YOU THANK YOU!

Fixed finally!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Shockndrop:
I had another thread for this, but I figured it would be good to repost it since I didn't know what I had stumbled upon at first.

For all of those who have soft bricked their phones, I present to you to the MF3 TAR files to flash it back to stock via ODIN.

https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE

And for those that aren't sure as to where to put the files when flashing via ODIN, while it should be obvious, I have attached a picture that [MENTION=5443584]xrandallx[/MENTION] posted to help those that need it.

I[/IMG]
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] rayburne:
Sticky???? ;););)
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] XCnathan32:
The Mega site isnt working, the download keeps on stopping randomly.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] NighthawkXL:
It's known issue with MEGA, it works best if your using Firefox or Chrome. If the download keeps freezing keep reloading it will eventually work...

Once somebody can grab the files I suggest they be uploaded to several locations, and perhaps a torrent file.

---Edit---

Maybe a mod can edit the title to include something like [Release]? As is stands now people might miss the thread by thinking it's a question being asked.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] FrozenDragoon:
AWESOME, simply fantastic! It seems that the picture has been moved, however. Any chance we can get a re-up?

EDIT: The only reason I'm asking is because I have been on MF3 since I purchased my phone. I assume, that if anything happens, I can use the existing guides for MDL, and just replace the files with MF3, right...?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jball:
Yes firefox and try the mega mobile app if you don't have it already.use in combo
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] xrandallx:
attached is the picture
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
The files are pretty self explanatory. Platform in PDA, modem in Phone, csc in csc, bootloader in bootloader. Only have auto-reboot checked. Ignore the dll file.

Edit, even better ^^^, haha posted while I was typing :good:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] NighthawkXL:
No, if you on MF3 and attempt to load any firmware below it such as MDL you'll end up with a brick (which this will fix, grant it). This has more use for people brick their MF3 devices using MF3-based firmwares.

Don't mind me, I misread your post... - Thanks for clearing that up @jd1639.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
You won't end up with a brick and the Odin guide for mdl firmware will work just fine. It's a guide. If you don't know what you're talking about don't post
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] deadenz:
worked perfectly. trading this phone for an lg. I'm on windows 8.1 pro 64bit and used odin v1.85
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] steven2k7:
This worked great for me as well. The only issue I have is when I first boot up my phone, it hangs in the middle of the AT&T logo until I pull the battery then it boots fine. That only happened in the first boot after odin and first boot after doing a factory restore.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Deamonicone:
recovery

so, with this MF3 image, are we that much closer to a custom CWM or TWRP for i337 MF3s?

wasting away in safestrap land :P
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] NighthawkXL:
Hate to burst your bubble, but this doesn't seem like the case. Although we have access to the TAR files now the fact is the MF3 bootloader remains locked. Unless we can convince AT&T or Samsung to hand over the keys it's going to be a long wait (if ever) before we find a means to circumvent it's encryption.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Randallel:
What about us Mac users. Will Heimdall work with this?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] The X-Ray Tech:
mf3 tars

I have to say u are a life saver! I thought my phone was bricked for sure. thanks
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] kyrumo71:
Can someone please re upload this, MEGA keeps stopping in middle of downloading.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] RockRatt:
I will try uploading it to dev-host and then let Shockndrop add it to his OP if he wants. It may take a long time to upload as I an being throttled on my data right now and my WiFi is not much better. Plus I couldn't get dev-host to upload yesterday. Will let everyone know once it is uploaded.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] FrozenDragoon:
To everyone using Mega, I thought it was crapping out in the middle too, until I realize that Chrome wanted to ask permission to download large files. After I allowed that permission, everything works fine.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] f0b:
Works perfectly! Thanks a lot! Had been waiting for this from long time! :good:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] contact.ace:
Mega taking forever

It is taking for ever to download from Mega.

Does anyone have a mirror?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Deamonicone:
Thanks for clarifying. damn AT&T ><
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] STLWaffles:
I joined just to say that you saved me from having to hit my phone with a hammer and pay my insurance deductible. Thank you X100
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] haremmon:
Confirming it works!

Thank you for the files. I used ODIN 1.85 on my Win7 x64 to wipe my s4 back to default without any issue :D

Also, I wanted to remind you guys that ODIN'ing your phone will erase your internal storage (not your sd card storage). That was my mistake for not backing up but thankfully there weren't anything important haha.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] lboyce72:
Worked perfectly, thank you OP!!

Returned rooted MF3 back to stock.

LB
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] goldenzeus:
Tar MF3 files

I took the liberty and unloaded the files to another file sharing service

http://www.fileconvoy.com/dfl.php?id=ge2c8e0d344e706b399940583906a3d902b897641c
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] ronnie498:
Here's a mirror that I had posted in another thread.

MF3 Tar

Sent from my SGH-I337 using Forum Runner
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] gage0727:
can someone tell me what is the best version of odin to use with the s4 i337 thanks a bunch,
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] haremmon:
I noticed a lot of people successfully ODIN their s4 1337 with version 1.85 so I went with that and with no surprise, it worked on my end.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] intika:
Thanks for the files at least we have now a real way to step back.

thanks !
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sharpehenry:
So now we can unroot without a trip to the best buy? Awesome!

Sent from my SAMSUNG-SGH-I337
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] AxAtAx:
Good job ronnie....:good:

This is a must if you have att.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Sigil42:
What would happen if you took this MF3 firmware and used Oden to flash it with CWM recovery all together? Would that work?

Im a newb by they way :confused:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
It wouldn't work. Not even sure how you'd do that
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jherring002:
So basically, If i mess with my phone a bit - end up in a boot loop or something - I will be able to come back to stock with this?

Last time Kies bricked my phone (mostly my fault as i didnt notice it was trying to take me back to MDL from MF3) and even best buy couldn't flash it back...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] dre_jarboe:
Where do you put the files I cant see the img

Where do you put the files I cant see the img
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] gadget069:
Here you go.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] cswann1:
Thank you sooooo much. I knew my phone was only soft-bricked but still it was fairly stressful. I am stress free now thanks to this thread!:victory:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] cswann1:
Yes. I was trying to flash a custom ROM from CWM and soft-bricked my phone. Using Odin and the tar files in the OP, I connected my AT&T i337 to my PC booted into Download Mode (home+vol down+power), once I saw my phone register in Odin, I just hit "start" and 6:59 later I was back to factory fresh.

I think the cause of my woes with flashing a custom rom stemmed from a failed MD3 update (this was weeks ago). I downloaded it before I knew what exactly it was but the download failed. After I saw the failure message I started researching what this big-ass download was. When I read about it I decided I didn't want it and left it at that.

Any of you Android pros have any thoughts on this?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] giler123:
your a fu*** life saver!!!

thanx man , i flash it with odin 1.85 windows 7 64 bit and it worked great!!!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] troybklyn:
U... Are... The... Mannnnn!!!!!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] LightningGA:
Thanks for this.

Kies soft bricked my phone.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] stealthily:
Im trying to get back to 4.2.2 using these files and odin 1.85 however it keeps failing after NAND write complete. I have it in download mode (vol down + home + power) tried 2 different computers and odin 3.04 and all fails at the same spot. I rooted the phone using vroot after the ota 4.3 and havent unroot it. Am i doing something wrong here?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] scott14719:
Yes you are doing something wrong...you aren't reading and learning about your device. It has been mentioned dozens of times already throughout several threads (that are very important) that you can not go back to a previous firmware once you allow an OTA. In other words, if you took the 4.3 update (MJ6 or MJ9) you CANNOT go back to 4.2.2 (MF3, AMDL, etc...) Search for information about q-fuses and read the "pinned" threads in the General and Q & A sections before you permanently brick your phone. Good luck.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] darinalleman:
I'm still trying to understand the implications now of the MF3, so bear with me.

Last night I tried flashing one of the new KitKat roms, and by accident wiped data using TWRP. Apparently that's bugged and forces you to do a factory restore using Odin. Anyways, long story short, I Odin'd these TAR files and now I'm on MF3. Is there any way to get back to a point where I can reflash my recovery, or even restore a nandroid backup that I have?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Your on mf3 now. You could have flashed mdl but it's too late now. There's no going back. You're stuck with safestrap. No recovery like you're familiar with and I don't think your nandroid will be any good either. Sorry bud, should have done some more homework before you flashed mf3.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] darinalleman:
Welp. Alright, that's fine. Thanks for your help!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] adambombz:
HELP!

Someone please help I'm not sure what's going on with this, I soft bricked my phone doing something with safestrap and when I try to run this in odin 3.07 and 1.85 I get:

<ID:0/003> Removed!!

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> sbl1.mbn

<ID:0/003> NAND Write Start!!

<ID:0/003> sbl2.mbn

<ID:0/003> sbl3.mbn

<ID:0/003> rpm.mbn

<ID:0/003> aboot.mbn

<ID:0/003> tz.mbn

<ID:0/003> boot.img

<ID:0/003> recovery.img

<ID:0/003> persdata.img.ext4

<ID:0/003> system.img.ext4

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] lionhart_1912:
I try to make it work with odin v3 1.85 but doesnt work so i decide to use odin v 3.07 and it works!!

thanks for make this happen
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] collins2275:
thank you

you are a savior I was scared
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] tevil:
This phone simply sucks because of this. What's the point of having android if you can't root and rom ?

Luckily in a few weeks this is going in a drawer and I'll have my nexus 5.

I can't complain since it was free but if I paid for this it would be going back.

I can root it fine but from there then what.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] kip1332:
Thanks

This helped me out a lot. I tried with odin 1.85 four or five times before I saw your post. Odin 3.07 worked first try!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] blanco613:
So I'm currently rooted on MF3, i stupidly tried to flash twrp and messed up my recovery. now i cannot boot into recovery, only system and odin mode. If i odin this package it will return everything to factory stock but does that include the recovery? i really want to fix the recovery so i could possibly do an ota. Also what version of odin should i use because i've heard 1.85 and 3.07 and idk which to use. Thanks for any help in advance :)
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Flashing with odin will put the stock recovery back on. I've mainly used odin 1.85 and have not had any problems with it. I've also been successful with 3.07 but my recommendation is 1.85. I have had to flash with odin more than once for it to take on a couple occasions. So don't give up on the first try if it doesn't work. Make sure you use the usb ports on the back of your pc, not the front.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] ngharo:
Does anyone know if this will revert the AWS/TMobile radio mods?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] bigube:
Just update the PDA with the stock TAR MF3 on ODIN 3.07 and your radio should not change.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] bitscience:
Works Great, Replaces EVERYTHING. (?)

After messing up the tethering patch to the point the phone read "network error", trying "factory reset" in recovery mode, failing to recover root in the so-called "factory" reset ROM, and discovering just what sorts of information the "factory reset" does NOT repair or replace, I tried this handy stock ROM from Post #1.

Surprise! It worked! Everything I can see in Titanium Backup, Root Explorer, App Quarantine, Settings, Root Uninstaller, and every other Root-needing app I can find to muck around in my phone--has all been replaced with out-of-the-box versions and settings.

Is there REALLY anything on the phone besides /mnt/extSdCard that this ROM doesn't replace? I'd like to know so I can stay away from there until I can find stock images for them.

Edit: Probably there isn't anything worth worrying about that the ROM won't replace. Question: If MF3 has some sort of "code signing"/ROM verification in place---and this really IS the stock MF3 ROM--what is now stopping us from creating a Knox- and "code signing"-free ROM that will pass inspection? It seems to me that doing so would effectively replace the current encumbered bootloader with one that does not have those "features" in working order, thus allowing us to proceed with flashing, well....anything.

P.S. noobs (like me!) may find it handy to have a link to the Odin thread posted so they can get the tool needed to flash this ROM:

http://xdaforums.com/attachment.php?attachmentid=581913&d=1304094576