yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
I am going to change this to a how to thread later today. Anyone else try it?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] deadenz:
this may be a stupid question, but if you went through the trouble of rooting after the mf3 update.. why would you want to unroot?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
Warranty replacement in case of a hardware issue, testing purposes, also, some people only want a temp root to remove bloat. After that, they don't want root anymore.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] haremmon:
So to summarize the steps from what I've read on rooting & unrooting MF3:

Root:

Use this guide by jortex: http://xdaforums.com/showthread.php?t=2387577&highlight=mf3

Unroot: http://xdaforums.com/showpost.php?p=44495559&postcount=39

Follow step 1 if not rooted or messed up somewhere during unrooting process.

Just double checking step 2: We can use es file explorer with root explorer option as well correct?

Also I noticed superSU got updated today:

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

Does the new update have something to do with our mf3 baseband like SELinux?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] WezzleD:
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah

I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.

I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.

Going to restart a few times to be sure.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] haremmon:
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] WezzleD:
I'm actually not sure. Didn't look at version numbers.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
4 confirmed. Let's get 5 and I will post a how to.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] supitsronnie:
That method worked for me also. I'm so glad it was discovered. Successfully unrooted.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
5!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Tsuul:
I was able to unlock as well. However my phone stopped showing the custom unlocked symbol at bootup a few days ago (before doing this) and I am at a loss as to why. So I am not sure I can count as a real confirmation.

I did your unroot process, root checker confirms I no longer have root and the unlock symbol has not come back.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
Stay tuned guys. Getting everything ready to quickly make a more organized how to.

Being horribly sick is not helping
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sjhotwings:
confirmed work :)
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] heartspeace:
If you unroot MF3 - will you be able to use ODIN again & get back to starting point?

If you unroot MF3 - will you be able to use ODIN again & get back to starting point?

HP
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
No. Read a little about your phone
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Zephcemi:
So I'm trying out this method...and I only seem to come up with two files. Someone mind listing the three files you're supposed to have left? I don't want to screw this up.

Thanks in advance!

Edit: The two files I have unchecked for deletion are daemonsu and dexdump.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
The other file is the busybox file. It should be in either system/bin/busybox or system/xbin/busybox. It may be in both.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sk337sk337:
I just hit the unroot in SU and restarted and it did all this for me. Boot is on Samsung and root no longer is functional.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Agent:
Adding to confirmation - delete busybox files and use SuperSU to unroot...works like a charm!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] mrthink:
Can't Delete Busybox

On MF3, rooted and using SuperSU. I have a semi-broken fastboot when tried to flash ClockworkMod...it ow takes two reboots to come up okay.

I tried to delete /system/xbin/busybox (the only "busybox" file/folder found) using ES File Explorer with root on, and the delete fails. I get the message "Read only file system". Any ideas?

Thanks, AT&T Galaxy S4 Rooted
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Change its permissions
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sam.balia1012:
u gotta mount as r/w then change permission ---- now u can delete.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] bschemmel:
Is this still the preferred unroot method for MF3? I rooted using Kingo and have not attempted any unroot process yet and am not sure if I will. After checking though, I only have 2 files in xbin. su and daemonsu. Nothing in there about busybox.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] dre_jarboe:
After I unroot how do I restore it back to stock?

After I unroot how do I restore it back to stock?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] DeadlySin9:
I believe so, considering kingo was determined suspicious.

Use the MF3 Odin files in the general section.

Sent from my SGH-I337 running Foxhound 2.0
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] deserthi:
I think I am screwed. When I tried to reroot with the script it won't run because I don't have permissions. I have tried using oden to go back to stock but get a write operation failed. The phone is working like a stock S4 but because I used to have root and now don't I can't run supersu, I can't delete the busybox file because it says I don't have root. It's like I can't do anything and am very frustrated.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] silrosriv:
Unroot

I had kind of the same problem but mine wouldn't re-root through my external sd. It kept telling me it couldn't see it. I ended up just trying something out of desperation. I got a thumb drive and put the root files in there, then re-rooted. After that I was able to delete the busybox files and unroot via su.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] chirpa12:
Does using Odin with the MF3 Tar files remove the root and everything else?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] DeadlySin9:
Yes. It will be as if you just bought the phone with MF3, no root or personal files on it besides external SD.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] chirpa12:
Excellent. I thank you good sir (or ma'am).
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] LiFe_sTyLe:
Hmm.. Is this weird?

I just hit unroot option in superSU and it vanished. Then I checked it via Root Checker and it says it is not rooted. First I just uninstaled BusyBox in menu of it. I restarted my phone and i got samsung galaxy s3 logo.

So basicaly there was no reboot of phone and root was removed? Normal ? And Light Manager app is not working anymore (facebook, viber settings - I cannot select them and i WAS able before unroot).

This is so simple!? lol ? :)
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] root_unrooot:
I know this is a little late, but this worked for me as well
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] strikeone:
Another late confirmation, worked great for me.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] matthewpapa:
Has anyone successfully applied system updates after deleting the busybox files and unrooting?

I hear the recent updates are less stable, but I am more concerned about the well documented security holes in MF3.

Sucks that Samsung had to lock the bootloader. Software wise the SGS4 was a big disappointment compared to my SGS2 (which I could install CyanogenMod, tinker to no end, etc). If I could just go back in time and not apply the MF3 update.... I will be purchasing a non bootloader locked phone next time around which means I will not be buying Samsung again.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] cjimmy:
Root a full unrooted phone

Hi, is there a way to root an SuperSu fully-unrouted phone ?

I547C with 4.2.1 on it, I'm with Telus (Canada)

Tried something with ADB but seem not working when I reboot in download mode

Thank you
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] PhatMunch:
Hey can you help me unroot my mf3? Im currently running a GPE rom on it with SS. I have no clue where to start. Ii would greatly appreciate it if someone could help me?
[T-Mobile myTouch 4G Slide] stroh.ed:
Did some searching about this beforehand but couldn't come up with a solid answer. Really hoping someone can help me out.

I very recently changed my friend's MT4GS from the latest stock ROM to CM 10.1. The ROM works fine for the most part. The issue is that she seems to be missing the vast majority of her contacts which is extremely upsetting to her as I'm sure you can understand. The few that were retained were the only ones she had synced to her Google account. The really odd thing is that she has had this phone replaced on four different occasions (same model) and her contacts would always sync effortlessly going from one to the next (all of them being on the stock ROM until now).

I've tried enabling sync in the People app through Gmail, Facebook, and even adding her Hotmail account to the AOSP email app and syncing that as well. The latter did add plenty of contacts but not the ones she was used to seeing, just email contacts exclusive to that account, no phone numbers as such.

So basically there are a few questions that arise from all of this:

1: Is there a simple way to get the contacts back while still on AOSP?

2: If we were to revert back to the stock ROM would the contacts come back as they have in the past?

3: Why would the contacts sync on the stock ROM but not AOSP?

Any and all help is greatly appreciated. Thank you for your time.
[T-Mobile myTouch 4G Slide] demkantor:
She was probably syncing contacts with T-Mobile and not Google, go back to at least a stock based ROM, sync contacts, then transfer them to gmail, then you can flash any ROM you want as they will be tied to gmail
[T-Mobile myTouch 4G Slide] stroh.ed:
Thanks for the info and the tip. I'll give a shot and report back.
[T-Mobile myTouch 4G Slide] Vauvenal7:
Its the most annoying thing for me with AOSP ROMs

The contacts she has "lost" are on her SIM card only right? Yet for some reason all AOSP and CM and AOKP

ROMs can't read those contacts...just the ones on the Google account

So best way is, return to stock as said above...i am sure all contacts are now available again, then sync them all to Google by just copying to Google account and flash back to your AOSP ROM and you are done

Was shocked the first time I rooted my desire z and missing some contacts too...but with time I got it why they where missing xD (still don't know why AOSP can't read SIM card contacts though)

Greets Vauvenal7

Sent from my SGS i9000
[T-Mobile myTouch 4G Slide] PsychoPhreak:
If you login to my-tmobile (assuming she was backing up to t-mo) go to mobile life-> contacts, then you can do an export of all the contacts that are there to something like VCF and then import to the phone. If they're out there, they're certainly not lost!
[T-Mobile myTouch 4G Slide] stroh.ed:
Success! Thanks everyone for the information and advice. You were all very helpful.

What I ended up doing was reverting back to a stock ROM, had T-Mobile automatically restore the contacts and exported them. Then simply imported them once back on AOSP. No biggy. :]

Thanks again! You can consider this thread solved!
[Galaxy S 4 Q&A, Help & Troubleshooting] casper0k:
Hi guys...

I need help. Trying to install another ROm to my Galaxy S IV - GT-I9505, but always have an Error "Signature verification failure".. I tried install 4 different ROMs, but always have this error... Trying do that in Recovery mode, because do not any other ways. Of course I did wipe/factory reset, new Rom what I want to install located on external SD card.

Thanx for yours advices...
[Galaxy S 4 Q&A, Help & Troubleshooting] HS™:
Try changing Recovery to Philz if you have some other
[Galaxy S 4 Q&A, Help & Troubleshooting] casper0k:
If be exactly wish to install CyagonoMod..
[Galaxy S 4 Q&A, Help & Troubleshooting] HS™:
U mean u wanna install cyanagen rom??

I m saying flash philz recovery mostly u won't have error while flashing

Or pls specify what u Have runng Rom recovery etc etc
[Android Q&A, Help & Troubleshooting] giannoug:
I'm working on a CM port and currently facing issues with vold. For some weird reason, vold isn't mounting storage devices as it should. Here is my current vold.fstab file:

dev_mount flash /storage/sdcard0 auto /devices/platform/mtd/mtd8/media nonremovable
dev_mount sdcard /storage/sdcard1 auto /devices/platform/AMLOGIC_CARD/card_host/memorycard0

Using adb I can confirm that everything is mounted correctly and also I can browse the files. Using applications (even MediaScanner) fails with permission errors. This is how I'm creating the storage folders, for user/permissions reference:

# Create mountpoints
mkdir /mnt 0775 root system
export EXTERNAL_STORAGE /storage/sdcard0
export SECONDARY_STORAGE /storage/sdcard1
mkdir /storage 0550 system sdcard_r
mkdir /storage/sdcard0 0000 system system
mkdir /storage/sdcard1 0000 system system
mkdir /storage/usbdisk0 0000 system system
symlink /storage/sdcard0 /sdcard
symlink /storage/sdcard0 /mnt/sdcard
symlink /storage/sdcard1 /mnt/external_sdcard

I have also noticed that the system reports different owner/group/permissions through adb and Terminal Emulator. Here are the outputs:

adb:

root@android:/ # ls -la /storage/
d---rwxr-x system sdcard_rw 1970-01-01 02:00 sdcard0
d---rwxr-x system sdcard_rw 1970-01-01 02:00 sdcard1
d--------- system system 2013-09-05 02:29 usbdisk0

Terminal Emulator:

ls -la /storage/
d--------- system system 2013-09-05 02:29 sdcard0
d--------- system system 2013-09-05 02:29 sdcard1
d--------- system system 2013-09-05 02:29 usbdisk0

Why does this happen? I'm suspecting storage_list.xml, but I checked mine and seems correct. Also, it doesn't define permissions, so I excluded that.

I'm out of ideas. What else should I check? How can I further debug this? Logcat doesn't show anything useful, everything seems fine with vold.
[Android Q&A, Help & Troubleshooting] shimp208:
Have you tried extracting the stock vold.fstab from your devices stock boot.img file to use as a reference point? You can then modify that if need be.
[Android Q&A, Help & Troubleshooting] giannoug:
Yes I did! Stock files are 4.1 though, so I made the appropriate changes (/mnt -> /storage) for example. It's really weird, because apps and adb show different permissions. Should I check anything in the Android framework?
[Android Q&A, Help & Troubleshooting] shimp208:
What I would recommend doing is setting the same permissions adb shows and seeing if that fixes any problems.
[Android Q&A, Help & Troubleshooting] giannoug:
I created an init.d script that chowns storage0 and storage1 to system:sdcard_rw. Same results, but I can see from Terminal Emulator the new values. I also added a chmod to change those folder permissions to 775, but again, no luck.

From the Terminal Emulator, even if I become root, I still can't see sdcard0/1 contents. From adb, I can! Really weird... That's why I'm suspecting the framework and not vold. By the way, here is the output of mount, just in case you spot something wrong.

rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/system /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/data /data ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/cache /cache ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
none /proc/bus/usb usbfs rw,relatime 0 0
/dev/block/vold/253:1 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/250:32 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/250:32 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

Maybe those fmask/dmask values?

Thanks!
[Android Q&A, Help & Troubleshooting] Christian Troy:
you need an updated /init binary because starting with 4.2 and its (useless) multiuser thing mount mechanisms have changed. You can use this for example.
[Android Q&A, Help & Troubleshooting] giannoug:
Thanks for the binary, unfortunately it still doesn't work. I also tried with the Elf II init binary from your repo and the device's stock binary. All binaries show the same error, no difference at all. What else can I try?

Storage is the only thing left to fix and I'm really stuck. No errors, no starting point :(
[Android Q&A, Help & Troubleshooting] giannoug:
Did some further testing with the new init, this is what I'm getting now:

W/dalvikvm( 2523): Failed to mount /storage as MS_SLAVE: Invalid argument
[Android Q&A, Help & Troubleshooting] Lt1streconbn:
Im having a few issues also. It seems to be rooted only 4.1.2 and later... Has specifically been vzw. I have my phone running a ported multicarrier on sgs3 and it's based on vzw. I'm running a d2att kernel though. I had to assign umask=0755 with busybox in a .sh in /system/xbin and remount sdcard0. It does work but I'd like a solution... not a patch lol. I've made several attempts to fix this, but with initramfs jamming errors at us and carriers crippling the roms to barely functional... I don't know to do but continue with a patch. Reply if you need the script, but you look as qualified as I am to write a fast one up. The weird thing is what happens trying to view a pic and it has no permissions. Smanager fixes it with another .sh script, scripts are powerful but it's not fixed... patched only. Good luck.
[Android Q&A, Help & Troubleshooting] shutt1e:
i'm in a middle of a nightmare with sdcard implementation in android, i'm compiling a cm10.2 android 4.3.1 based. as for the google guides for the sdcard i have used a fstab.xxxx and a storage_list.xml. i don't get it working, i can browse the sdcard(s) using adb but they never show as available on settings and on all apps. there is something obscure to me due the ridicolous documentation about the whole thing.

Vold mount the sdcards and it only mount them at the path written in the fstab, directories must be created on the init.hardware.rc and indeed the vold mount the volumes, but, it mount on storage/sdcard0 (assuming this is the path) and mouth them with own permissions so system.sdcard_rw 0075

guides says to use a fuse_sdcard service to remap the mounted sdcards with right permissions for the system so a "service sdcard /system/bin/sdcard source_path dest_path 1023 1023" is needed, where 1023 is the right user/group

but

i need to use as the dest_path the same path i used on storage_list.xml and as source_path the path vold has created, but how the src and dst can be the same?

what i tried so far:

using a different path on storage_list.xml= the sdcards are not mounted at all

using a different path on fstab.xxxx= vold don't mount the sdcards

using no sdcard service= vold mount the cards and they are working but they cannot be used on android,just with adb

i never ran so much troubles compiling kitkat, maybe android 4.3.1 has some obscure problems?

edit- post edited, maybe can help someone.

i got the problem solved, it was a init executable which was in my build tree by mistake (wrong device.mk)

once i used the init compiled i got the sdcard working.
[Android Q&A, Help & Troubleshooting] Lt1streconbn:
Have you tried mounting with umask=0 ? It should mount them correctly in default properties... Or umask=0000 as android and RH can be distinct at the worst times and then I'm unaware of where I might have goofed ;) I'm not positive I'm understanding the question either. If your issue with your fstab or is it with the actual boot process getting prop errors? I'm a bit confused, but if its the actual boot, my suggestion may be of assistance. If its in creating an fstab, well the command I gave you will actually be referencing the fstab to assign properties in boot and that will use your defaults in fstab. I forget where it actually retrieves it from though after the fact. Lol anyway, perhaps of help. You could also get the info from proc/mounts, but with emulated storages that's tricky. I can't recall if 10.2 was the emulated or not tho.
[HTC Typhoon] s4czech:
Has anyone figured out why www.orb.com does work with WM5?

Orb doesn’t seem to work with WM5.

Orb worked perfect on the Typhoon with Windows Mobile 2003SE

I confirmed it WONT work on the WM5 Himalaya as well.

http://forums.orb.com/community/viewtopic.php?t=294

http://forums.orb.com/community/viewtopic.php?p=3112#3112

-Please wait while Orb measures the network speed. (success)

-I see my favorites and play a tv station (looks good at first)

-Windows Media opens with error:

"Cannot play the file. The file is either corrupted or the Player does not suport the format you are trying to play"

more info.........

WM5 Windows Meida plays my local MP3's just fine

WM5 Windows Media plays http://www.xstreamxm.com/mobile/ just fine

WM5 Windows Media plays various .WMV videos perfect
[HTC Typhoon] s4czech:
ORB: My Support Request response........

Reply from Administrator	Submitted on Sep 02, 2005 04:14 PM

"Windows Mobile 5.0 is not yet supported and we are currenlty in the process of testing. It will most likely be supported by the time Windows Mobile 5.0 is officially released."
[HTC Typhoon] dny238:
Anyone figure this out yet? Before I install Real...

Thanks,

Rob
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dantexaiver:
Hey guys

Any news on if Tegra 2 will be updated to work with Jeallybean and allow video playback that does not stutter on the P7510?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] gordonx10i:
use MX player I don't find any stutter
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dantexaiver:
You mean to tell me Netflix and video streaming from network works with out issues no stutter or lag? I had to downgrade to a earlier version of Cyangenmod 9 to be able to play videos again because when i instead 10.1 no video play back would work with out lag or stuttering. I was told this had to do with the fact the Tegra 2 drivers were not updated to support jeallybean and that is why video playback wouldn't work. I tried MX player in the past but still had the same issue.
[Android General] Lindsay02:
:good::good::good:
[Android General] manhgioiandroid:
:good: like
[Android General] onikage31:
Thanks for share ! I really loved the way you open your postal gift :good: :highfive:
[Android General] fnxbaby:
thanks for the review
[Android General] marcomaccio:
Total agree

Just got an MI 2S and I had the same nice experience you had.

I agree about the tricky back cover.

Really satisfied and great customer service ever !