So my uncle gave me a brand new Galaxy Tab 4. I have used it for 3 weeks already and suddenly the wi-fi turned off. Now it won't turn on (also the bluetooth). I have tried rebooting and factory reset but it doesn't resolve the problem. I went to the Samsung customer service but they said they couldn't repair it beacuse the parts on our country are "not compatible" with the parts where the Tab 4 was bought. They advised me to give it back to my uncle, outside the country, to get it fixed. Can somebody please help?
Please help
Please help T_T
help
Sometimes it's not hardware failure,* software problem.. like missing driver.. leading to the same problem.. have you try reinstall your tab to the latest firmware?
Prepare carefully !!* if you choose to reflash your tab with odin.
google.. and you can find how to flash your tab.
*if you can't find firmware exactly match with your tab, then forget about flashing.
jokowi said:
Sometimes it's not hardware failure,* software problem.. like missing driver.. leading to the same problem.. have you try reinstall your tab to the latest firmware?
Prepare carefully !!* if you choose to reflash your tab with odin.
google.. and you can find how to flash your tab.
*if you can't find firmware exactly match with your tab, then forget about flashing.
Click to expand...
Click to collapse
My MAC address is "Unavailable". It says I have the latest firmware, but I still downloaded and installed the latest firmware via kies. Problem still persists. :<
What your Mac address is missing? Check your tab IMEI is still there? I'm afraid something wrong with your EFS partition brother*.. if you never backup your good EFS... it hard to fix it.. or almost impossible
Same problem Wifi Bluetooth SM-T231
I have same problem... I reinstall Rom on Odin. Factory reset wipe data , and is same...
Please see the Video , SM-T231 My Samsung Galaxy Tab 4 With problem Wifi BT youtu.be/q4zWr2ZAF2g
I also have the same problem SAMSUNG GALAXY TAB 4 SM-T230NU . Do we have any update about this? Tried soft reset, factory reset and hard reset. It's still the same.
kleinski23 said:
I also have the same problem SAMSUNG GALAXY TAB 4 SM-T230NU . Do we have any update about this? Tried soft reset, factory reset and hard reset. It's still the same.
Click to expand...
Click to collapse
please give me a:
# mount|grep persist && mount|grep efs
# ls -al /efs/wifi
# ls -al /persist
# mount
Here you go
[email protected]:/ # mount|grep persist && mount|grep efs
mount|grep persist && mount|grep efs
1|[email protected]:/ # ls -al /efs/wifi
ls -al /efs/wifi
-rw------- system system 17 2000-01-01 00:19 .mac.cob
-rw-rw---- system wifi 17 2000-01-01 00:19 .mac.info
[email protected]:/ # ls -al /persist
ls -al /persist
/persist: No such file or directory
1|[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/soc.2/by-name/SYSTEM /system ext4 ro,seclabel,relatime,data=
ordered 0 0
/dev/block/platform/soc.2/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noa
time,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered
0 0
/dev/block/platform/soc.2/by-name/USER /data ext4 rw,seclabel,nosuid,nodev,noati
me,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0
0
/dev/block/platform/soc.2/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,noatime
,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/soc.2/by-name/NVM /NVM ext4 rw,seclabel,nosuid,nodev,relatim
e,nodelalloc,noauto_da_alloc,data=ordered 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,mode=775,uid=1000,gid=1000 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1
023,derive=legacy,reserved=20MB 0 0
[email protected]:/ #
I fixed it!!!
digz4 said:
So my uncle gave me a brand new Galaxy Tab 4. I have used it for 3 weeks already and suddenly the wi-fi turned off. Now it won't turn on (also the bluetooth). I have tried rebooting and factory reset but it doesn't resolve the problem. I went to the Samsung customer service but they said they couldn't repair it beacuse the parts on our country are "not compatible" with the parts where the Tab 4 was bought. They advised me to give it back to my uncle, outside the country, to get it fixed. Can somebody please help?
Click to expand...
Click to collapse
Go to general settings. go to application manager. got to running applications and STOP everything. Then go back to connection settings and click advance settings for Wifi. You will have new option on of which is restart WiFi. Click that which will force power of restart the device. When it me back, you'll be able to turn on wifi.
Related
Galaxy Tab 10.1 GT-P7510 32GB, stock, not yet rooted
kernel: #1 SMP PREEMPT Mon Jun 6 08:59:10 KST 2011
PDA: KF3, phone: KF3; CSC: KF3 (XAB)
Starting down the path to root the phone, I encounter an issue that I haven't seen on the fora.
If I boot to recovery, I get to menu about "reboot system now", "apply update from /sdcard" and so on, but if I pick "apply update from /sdcard" it can't find what I've put in /sdcard. I get an error "E: unknown volume for path [/sdcard]".
While in this recovery state, if I adb shell, do "mount", I see that nothing is mounted on /mnt/sdcard:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/mmcblk0p4 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
In normal running state, if I adb shell "mount" I get:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs 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/mmcblk0p4 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I'm quite surprised that /mnt/sdcard is not mounted in a mode where it's supposed to be able to do update.zip things from there.
Am I being stupid? (No surprise if that turns out to be the case.)
--bogoid
I am having the exact same issue with my Galaxy Tab 10.1. Anyone help would be greatly appreciated.
Adam
Ditto - have you guys found a fix yet?
Good Day. This is a known issue with the Retail Boatloaders.
If and only if your Devices is Unlocked (padlock at the bottom of the screen during regular boot up is evidence of an unlocked device) you can use the attached thread to flash a IO boatloader then a CWM compatible one and then root.
http://forum.xda-developers.com/showthread.php?t=1130574
For other questions take a walk over to the Development thread.
PLEASE READ COMPLETELY BEFORE TRYING ANYTHING
msm903 said:
Good Day. This is a known issue with the Retail Boatloaders.
If and only if your Devices is Unlocked (padlock at the bottom of the screen during regular boot up is evidence of an unlocked device) you can use the attached thread to flash a IO boatloader then a CWM compatible one and then root.
http://forum.xda-developers.com/showthread.php?t=1130574
For other questions take a walk over to the Development thread.
PLEASE READ COMPLETELY BEFORE TRYING ANYTHING
Click to expand...
Click to collapse
That did the trick! Thank you!
Hey everyone,
This is pretty embarrassing... I successfully ran the following:
Code:
mount -w -t vfat /dev/block/mmcblk0p12 /mnt/sdcard
But now I cannot revert back to the original mount point of "/sdcard"
I've even tried umount-ing with the force-flag and still no luck
I'd appreciate any help at all, thanks
It *might* revert when you reboot unless you overwrote something.
Why are you screwing with this anyways?
Thanks for the quick reply.
Rebooting didn't change it.
Edit: Below is fixed, no longer relevant
Except, now I'm noticing I have to root with SuperOneClick each time I reboot to get su access.
The only thing I did after running the mount command, was install BusyBox
Wait, what? Since when does Kindle Fire have an SD Card? I'm so confused
jasongw said:
Wait, what? Since when does Kindle Fire have an SD Card? I'm so confused
Click to expand...
Click to collapse
There's an "sdcard" partition. It's whats mounted when you attach your KF to your PC... But no, there's no removable SD Card
Not sure 100% what the correct command to remount the sdcard partition is so can't say much right now.
check under /proc/mounts and also under /proc/emmc (open them as a text file) and paste what it says.
Didn't see a /proc/emmc but here's what I found
Contents of /proc/mounts:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/splash /dropbox ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:12[B][COLOR="Red"] /mnt/sdcard[/COLOR][/B] 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/179:12 /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[B][COLOR="Red"] /mnt/sdcard/[/COLOR][/B].android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.angrymobgames.muffinknight3rdparty-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I hope you can solve your problem,good luck
looks like you need to mount /dev/block/vold/179:12 so rerun the command you were doing with that instead.
I installed Astro File Manager, through which I can view the sdcard partition's contents in "/sdcard" as well as "/mnt/sdcard"
I only seem to have issues viewing contents of location "/sdcard" in adb shell.
At this point I'm not too terribly concerned about it. Maybe I'm making a deal out of nothing...
I do appreciate your help though.
And if anyone knows the exact solution, then please speak up
EDIT:
Returns nothing:
Code:
ls /sdcard
Returns contents:
Code:
cd /sdcard
ls
I guess nothing was ever wrong after all.. Now I feel extra-dumb
Hi everybody,
i have a galaxy S4 korean version E300L, i been trying to install on it a custom rom of a korean gs4 i9500 through CWM, everything went smooth till i came to discover that there's no signal and the baseband is unknown and the IMEI is blank! and before doing so i made sure to backup my rom and also the efs partition with a dd command using the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/efs and here's the 20mb efs backup if anybody can tell me how to use it:
http://www.4shared.com/file/Ajc7gjXB/efs.html
because trying to restore that backup using dd command like that:
[email protected]:/ # dd if=/sdcard/efs of=/dev/block/mmcblk0p3
dd if=/sdcard/efs of=/dev/block/mmcblk0p3
40960+0 records in
40960+0 records out
20971520 bytes transferred in 4.253 secs (4930994 bytes/sec)
[email protected]:/ # reboot
reboot
as you can see everything goes well but when i check /efs using root explorer the partition would be the same, a blank folder with few recreated files by the system with no nv-data.bin files., so please can you suggest anything to restore my wiped efs partition? i tried to restore the cwm backup many times but it didn't work, and here's the partition table:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,
data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,errors=panic,data=ordere
d 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_
checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journ
al_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journa
l_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p14 /tombstones ext4 rw,seclabel,nosuid,nodev,noatime,data=ord
ered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /dev/memcgrp cgroup rw,relatime,memory 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1
023 0 0
[email protected]:/ #
yakie47 said:
Hi everybody,
i have a galaxy S4 korean version E300L, i been trying to install on it a custom rom of a korean gs4 i9500 through CWM, everything went smooth till i came to discover that there's no signal and the baseband is unknown and the IMEI is blank! and before doing so i made sure to backup my rom and also the efs partition with a dd command using the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/efs and here's the 20mb efs backup if anybody can tell me how to use it:
http://www.4shared.com/file/Ajc7gjXB/efs.html
because trying to restore that backup using dd command like that:
[email protected]:/ # dd if=/sdcard/efs of=/dev/block/mmcblk0p3
dd if=/sdcard/efs of=/dev/block/mmcblk0p3
40960+0 records in
40960+0 records out
20971520 bytes transferred in 4.253 secs (4930994 bytes/sec)
[email protected]:/ # reboot
reboot
as you can see everything goes well but when i check /efs using root explorer the partition would be the same, a blank folder with few recreated files by the system with no nv-data.bin files., so please can you suggest anything to restore my wiped efs partition? i tried to restore the cwm backup many times but it didn't work, and here's the partition table:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,
data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,errors=panic,data=ordere
d 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_
checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journ
al_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journa
l_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p14 /tombstones ext4 rw,seclabel,nosuid,nodev,noatime,data=ord
ered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /dev/memcgrp cgroup rw,relatime,memory 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1
023 0 0
[email protected]:/ #
Click to expand...
Click to collapse
Wrong forum.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
First: Questions go in Q&A
Second: make sure you are in the correct forum for your device
Moved to International S4 and Q&A
FNM
sir, it is not enough to backup only efs partition in s4, you must backup also m9kefs1, 2 and 3 partitions
http://forum.xda-developers.com/showthread.php?t=2284357
samersh72 said:
sir, it is not enough to backup only efs partition in s4, you must backup also m9kefs1, 2 and 3 partitions
http://forum.xda-developers.com/showthread.php?t=2284357
Click to expand...
Click to collapse
what about the CWM back up i have? is there any chance to extract those hidden partitions from it? if my Korean version has that same divided into 4 efs partition?
yakie47 said:
what about the CWM back up i have? is there any chance to extract those hidden partitions from it? if my Korean version has that same divided into 4 efs partition?
Click to expand...
Click to collapse
efs and m9kefs partitions are not a part of the firmware, they are not flashed with it
samersh72 said:
efs and m9kefs partitions are not a part of the firmware, they are not flashed with it
Click to expand...
Click to collapse
you mean that those m9kefs blocks are not part of the system so cwm would never back'em up then..?
and what's the size of each one of those m9kefs blocks in your gs4, for me after making those m9kefs partitions backups i got 4mb size in each one of them as for the main one: /dev/block/mmcblk0p3 partition, it was 20mb, and cheking them with an hex editor they don't seem like an efs partition similar to the gs2 or the gs3 only the 20mb /dev/block/mmcblk0p3 partition that contains some information that seem to have something to do with the efs partition data, and here's a link to one of those partitions check it out yourself:
http://www.mediafire.com/download.php?cwrbz26cdowowuk
yakie47 said:
you mean that those m9kefs partitions are not part of the system so cwm would never backed'em up then..?
and what's the size of each one of those m9kefs partitions in your gs4, for me after making those m9kefs partitions backups i got 4mb size in each one of them as for the main one: /dev/block/mmcblk0p3 partition, it was 20mb, and cheking them with an hex editor they don't seem like an efs partition similar to the gs2 or the gs3 only the 20mb /dev/block/mmcblk0p3 partition that contains some information that seem to have something to do with the efs partition data, and here's a link to one of those partitions check it out yourself:
http://www.mediafire.com/download.php?cwrbz26cdowowuk
Click to expand...
Click to collapse
yes
right size.
those EFS partitions that need to be secured for the S4.
m9kefs contain NV_DATA files
EDIT: in S2 & S3 all are included in efs partition
samersh72 said:
efs and m9kefs partitions are not a part of the firmware, they are not flashed with it
Click to expand...
Click to collapse
samersh72 said:
yes
right size.
those EFS partitions that need to be secured for the S4.
m9kefs contain NV_DATA files
EDIT: in S2 & S3 all are included in efs partition
Click to expand...
Click to collapse
well.. good to know that even though it's too late!
Hi,
May I ask you a link to your efs partition? I might have an idea to fix your device (and in the same time, getting access to an exynos s4 efs might help me adding support to galaxsim unlock)
I believe the link is above, hope you could find a way to restore that efs.bin file.
Sent from my SHV-E300L using xda premium
I try root with motochopper, tool work , icon Superuser appearance, but when i setup Root Explorer, it not work, please help me root my phone.Thank so much.
Wait this isnt an S4 right ? Try posting in the right fourm.
Sent from my HTC One X using xda premium
mhoss48 said:
Wait this isnt an S4 right ? Try posting in the right fourm.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
there isnt a S4 mini GT-I9195 (and I9190, I9192) Forum yet.
m4kl4 said:
there isnt a S4 mini GT-I9195 (and I9190, I9192) Forum yet.
Click to expand...
Click to collapse
Hi,maybe it can help you root your i9195. I have no device to test. So think about it before you do.
Steps:
extract this zip file, open "Eroot.exe" , click the button "root"，maybe it's in Chinese "一键ROOT"。 Remember to enable the usb debug mode and install the drivers for your I9195.
m4kl4 said:
there isnt a S4 mini GT-I9195 (and I9190, I9192) Forum yet.
Click to expand...
Click to collapse
Hi, attachfiles are the tool. After downloading the two files, you need to change "I9195-Eroot.z01.zip" name to " I9195-Eroot.z01" . Then extract "I9195-Eroot.zip" ,it will be ok.
monokoo said:
Hi, attachfiles are the tool. After downloading the two files, you need to change "I9195-Eroot.z01.zip" name to " I9195-Eroot.z01" . Then extract "I9195-Eroot.zip" ,it will be ok.
Click to expand...
Click to collapse
files are BROKEN, can someone reupload new ones?
DustEater said:
files are BROKEN, can someone reupload new ones?
Click to expand...
Click to collapse
Have you modify the file extension of "I9195-Eroot.z01.zip" to I9195-Eroot.z01? it's a compression volume.
yes I did. they are broken
Eroot Screen
I tryed your Programm. Eroot finds the i9195 and starts the process.
In the end i get this Screen and I'm not shure what to do. Hope someone can help
No Superuser installed and i can't proceed. All on the Phone seems unchanged
Anyone that knows Chinese please provide some help.
Google translate mówi:
1. Wpisz model telefonu
2. Wpisz numer telefonu
3. Komentarz
goodneo said:
I tryed your Programm. Eroot finds the i9195 and starts the process.
In the end i get this Screen and I'm not shure what to do. Hope someone can help
No Superuser installed and i can't proceed. All on the Phone seems unchanged
Click to expand...
Click to collapse
Here is the translation
Only for feedback?
Did this program root the device or not?
Where is Chainfire when we need him we need cf-auto-root for i9195...
Here is my ADB shell info
s4 mini i9195
united kingdom
Hope this helps someone to root it
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p20 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_c hecksum,journal_async_commit,noauto_da_alloc,data= ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_c hecksum,journal_async_commit,noauto_da_alloc,data= ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_c hecksum,journal_async_commit,noauto_da_alloc,data= ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_c hecksum,journal_async_commit,noauto_da_alloc,data= ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=ubject_r:firmware:s0,relatime,gid=100 0,fmask=0006,dmask=0006,allow_utime=0020,codepage= cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/data/container /mnt/shell/container sdcardfs rw,nosuid,nodev,relatime,uid=1000,gid=1000 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/dev/block/vold/179:33 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime, uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime, uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/extSdCard/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.distractionware.superhexagon-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
in case you get the same error message I got, I attached a translation....
Did the root work using eroot?
Sent from my GT-I9195 using xda app-developers app
arco68 said:
Hello all.
I will probably release ClockworkMod recovery and an insecure kernel for the GT-I9195 this weekend. With those installed, root can easily be achieved by using the built in root function in recovery.
Click to expand...
Click to collapse
Hi. As far as I know, the developer @arco68 is releasing CWM and insecure kernel for rooting within this week. You can wait for this
i think we definatelly need a section for 9190 and 9195.....otherwise we are gonna be lost in the sub forums for good..
Eroot doesn't work
Eroot doesn't work for our device.
You should wait for the insecure kernel.
In case you haven't seen it yet:
[RECOVERY][ROOT] Samsung Galaxy S4 Mini (GT-I9195)
http://forum.xda-developers.com/showthread.php?t=2364980
Hello, since yesterday I can't write anything om my external memory-card (sdcard0) anymore. No idea what caused this
CM: nightly 24.11.2014 (happens also on older builds until 16.11.)
Mounts (recorded with the mount command via terminal):
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data_root ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkHD-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/ginlemon.flowerpro-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/vold/179:27 /mnt/media_rw/sdcard0 ext4 ro,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,data=ordered 0 0
/dev/block/vold/179:27 /mnt/secure/asec ext4 ro,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-2 /mnt/asec/com.sonny.lpi.frost2-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
Hmmm - I hope I did provide enough information ...
I'm wondering whether it is possible to unmount /mnt/media_rw/sdcard0 in a terminal and mount it again with read-write enabled?
Not sure how to proceed and a bit anxious about it as well since I don't know enough about Android despite working with Linux since 20 years
I guess your filesystem is corrupted. Please post dmesg logs.
Here's the dmesg.log -> https://gist.github.com/wimstefan/7af22e19b6ff408a7c22
Thanks for looking into it!
If needed I also can provide the logcat I took this afternoon ...
yep ur filesystem is corrupted. The weird thing is, that errors should be fixed on each boot.
you could reboot to recovery and run "e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system" from a shell.
m11kkaa said:
yep ur filesystem is corrupted. The weird thing is, that errors should be fixed on each boot.
you could reboot to recovery and run "e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system" from a shell.
Click to expand...
Click to collapse
Oh I see
Well running the command above seems not to do that much:
Code:
# e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/msm_sdcc.1/by-name/system: 1944/32768 files (0.5% non-contiguous), 106443/131072 blocks
Same happens with system1 ... but that's not where the errors in dmesg are listed or am I completely wrong now? I see some fs errors passing dmesg regarding device mmcblk0p27 which is /dev/block/platform/msm_sdcc.1/by-name/storage. Running the e2fsck command on that device was a completely different story! A lot of errors and corrections ... the filesystem was modified at the end and after a reboot it is mounted writable again!
So THANK YOU VERY MUCH for pushing me in the right direction !!! :highfive: :victory:
Hopefully everything is alright again and I can continue to enjoy my MI2S
yeah sorry I meant storage. stupid copy&paste errors