I've recently picked up this phone (A2017U), and following the guide from DrakenFX (don't think I can post links yet), the phone was bootloader unlocked and rooted on B20. I then decided to update it to B29 using an additional guide.
Ok, I'm pretty sure I did something stupid here, as I opted to wipe system during the above steps, and there was an error (E: failed to mount..., I think it was). I then flashed SuperSU from TWRP as noted in the above post, but after rebooting, I lost root, and I'm back to the stock recovery. Now, my PC can see the phone fine in regular mode with ADB, but as soon as I do 'adb reboot edl' or 'adb reboot bootloader', I get USB error 43 (device descriptor request failed). I have two integrated USB 3.0 ports on this PC and have tried both, and I've also tried this on another PC (Surface Pro 4) multiple times and with two different cables, with the same result. Both are Windows 10 post anniversary update. I've also reinstalled and tried it pre-anniversary update. I've tried using the Google ADB drivers (version 9.00) to no avail. I can manually add 'Android Bootloader Interface' when error 43 happens, but it gives me error 10 and no amount of uninstalling/reinstalling does the trick. I've also tried FTM, which gives me ADB access and a COM port, but it's right back to error 43 with 'adb reboot edl/adb reboot bootloader'.
Am I missing something, or am I stuck? Is there no way to get it recognized in fastboot mode so I can flash TWRP again?
Check in drakenfx thread on the b29 update, I think i saw note about it in OP
Have you tried going back to b20 using the zte factory firmware image?
When you get to a point you can't recover from, go back to square one and start over.
Since you said you unlocked your bootloader, what happens when you reboot your device? Do you get a weirdly formatted black screen for a few seconds that says something along the lines of "Warning - your device is unlockrr", before booting into the OS? If so, press VolUp or VolDown during that screen, it'll give you booting options. Select Fastboot and it'll reboot into bootloader.
All: thanks for the tips so far. I did manage to go back to B20 stock using ZTE's factory update.zip. Unfortunately, that's as far as I can seem to get. The bootloader is still unlocked (as it indicates when I do 'adb reboot bootloader') but since going back to B20 I no longer get the startup message that tells you so (device can't be trusted). OEM unlocking is still set to 'on' in developer options. I've done the 'update driver software' trick on the USB 3 host controllers but that didn't work. I've also pulled the battery from my motherboard and left it off for a few minutes. That didn't help either, as I still get error 43 when entering fastboot mode. I have a backup of fbop.img prior to unlocking, and a full TWRP backup from B20, but since I don't have root or fastboot I can't flash anything.
Hi all,
Unfortunately, I still can't get any pc to recognize my phone in fastboot mode via any of the above suggestions. I tried this thread titled: "[RESOLVED] fastboot not recognizing phone in bootloader mode" (I can't post links yet), but it didn't work. Neither Kingroot or Kingoroot work either (although some requests have been made in Kingroot). Am I stuck? I don't know of any other way to get my pc or my Surface Pro 4 to recognize the phone in fastboot mode or even to get root.
Knight1314 said:
Hi all,
Unfortunately, I still can't get any pc to recognize my phone in fastboot mode via any of the above suggestions. I tried this thread titled: "[RESOLVED] fastboot not recognizing phone in bootloader mode" (I can't post links yet), but it didn't work. Neither Kingroot or Kingoroot work either (although some requests have been made in Kingroot). Am I stuck? I don't know of any other way to get my pc or my Surface Pro 4 to recognize the phone in fastboot mode or even to get root.
Click to expand...
Click to collapse
You need to revert back to the old drivers in device manager,
When you boot to fastboot the device install the newest drivers and those drivers are a NO GO,
Boot to fastboot and look in Windows device manager , you'll see Android something forgot the name and go to update drivers and manually revert / install driver from 2014, I'm not at home at the moment so can't tell you exactly how.
As soon I get home I'll update this post.
EDIT : CHECK IMAGE about HOW TO Revert to Old drivers.
NOTE : YOU MUST BE IN BOOTLOADER / FASTBOOT MODE.
<snip>
NOTE : YOU MUST BE IN BOOTLOADER / FASTBOOT MODE.[/QUOTE]
Hi DrakenFX,
Thank you for the response. I did try the above, but unfortunately, it didn't work. I tried this on my Surface Pro 4, and when I enter fastboot mode, I get error 43 (device descriptor request failed). I can manually install the drivers from 2014, but if I do, I get error 10. I can uninstall the drivers and reinstall them, but to no avail. I tried this on my PC also, and I don't get error 43. Instead, there is no indication at all when entering fastboot mode. On my PC, I updated the BIOS and the USB 3.0 firmware thinking that would help, but it didn't. This is an Asus 970 Pro Gaming/Aura motherboard. I've tried it in multiple USB ports, both 2.0 and 3.0. Previously I reinstalled Windows (Windows 10) several times on my PC and that didn't help, either. I had drivers from another phone installed (HTC One M9) and thought that might be conflicting, and removed them, but that didn't do anything either.
I know I've got to be missing something totally obvious but I can't for the life of me figure out what that is. The phone is recognized just fine normally, but as soon as I enter fastboot mode, it's no longer recognized. Is it a problem the fastboot partition itself? I've done cat/proc/partitions and it shows a size of 512 for sde6 (which, I believe, is the fastboot partition), so there does appear to be data in it.
Here is the output of cat/proc/mounts:
1|[email protected]_ii:/ $ cat /proc/mounts
rootfs / rootfs ro,seclabel,size=1824140k,nr_inodes=456035 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1893300k,nr_inodes=473325,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,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1893300k,nr_inodes=473325,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=1893300k,nr_inodes=473325,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/dm-0 /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
tmpfs /data tmpfs rw,seclabel,nosuid,nodev,noatime,size=262144k,nr_inodes=473325,mode=771,uid=1000,gid=1000 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/bluetooth /bt_firmware vfat ro,context=ubject_r:bt_firmware_file:s0,relatime,uid=1002,gid=3002,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=1893300k,nr_inodes=473325,mode=755,gid=1000 0 0
/dev/block/dm-1 /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,resuid=1000,resgid=9990,data=ordered 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I also wanted to do ls -al /dev/block/platform/*/by-name but it returns 'permission denied', which means it needs root, which I don't have.
What do you recommend I should do next?
Edit: for what it's worth, I have a backup of fbop.img prior to unlocking the bootloader, even though I can't do anything with it at this time. The bootloader is still unlocked and 'OEM unlocking' has been left in the on position on each attempt I've made. I've also been able to flash back to B20 using the stock update and that didn't help either.
Find an old PC, with Windows 7, start from scratch. Do not waste your time in the new ones.
I'm trying to find one this week. Found one already, but unfortunately it had too many problems to be of any use. I may have to wait for the weekend for another shot.
Related
EDIT: NEVERMIND EVERYONE, I took the plunge and flashed with odin. Good a time as any to try out froyo JP3 optimism lol
As per title, I had an android noob moment...
I was going to try and copt over the feeds widget with vibrant version (cause it's black from a video i saw), and i figured i could prob copy over apk + odex into system/app and theyd work... but my phone froze and now it wont go past the boot screen...
Is there some way i can delete the system files i copied over from PC (adb?) or update.zip?
Nooooo X_X
Hope someone can help this noob!
EDIT: did some research and downloadiing the sdk now, hope i can fix this T_T. Advice still appreciated!
I had a similar issue trying to get a wildfire app working on my galaxy. I just used adb to push clockworkrecovery and then once booted into clockwork used adb shell and su to remove the files that I shouldn't have installed and it boots fine
how to push clockworkrecovery using adb? ive got adb up and running...
I would so much appreciate some more details on what you did please!
I tried standard adb rm -r, but it says permission denied. no doubt because su is needed...
i have su and root explorer installed before this happened, but how do I use it from recovery or .....?
I'd think you need to get the recovery .zip from Koush's site, rename it update.zip, do adb push update.zip /sdcard . Apply the update.zip in the standard recovery to get to ClockworkMod.
Thanks Mithent, but I've been trying that for the last 10 mins... and it keeps saying "permission denied"
I know my phone isn't bricked.. but i don't wanna have to lose data by reflash etc >_<
Somehow i just need to get permission... and undo my mistakes >_<
desperately want my phone back! lol
Hmm, seems like I can see the two drives in My computer (windows 7). I guess I might be able to mount them via adb? Im trying to find commands to do that now >_<
EDIT: KILL ME! still can't manage mount sd or do anything. please save me XDA!?
EDIT2: I can't even list /sdcard/!!!!
The only thing i've managed to do is "adb shell ls' to list the root directory. anything else just doesnt do anything 0_0
I used a card reader to get update.zip onto my external sd, but i can't even move it to the internal using adb "mv" wtf?
xfile087 seems like you might be my best hope!!! hope you reply again tomorrow :S
Can't mount anything either. the only thing that seems to give me a response is adb shell mount
C:\Users\Nirro\Desktop\sdk\tools>adb shell mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
nodev /tmp tmpfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
C:\Users\Nirro\Desktop\sdk\tools>
Alright so I am trying to help out and get a backup of /system from my GF's samsung intercept. A dev over on SDX managed to flash a custom recovery to the phone. There are no issues from what I can find with the recovery accept for the fact that I cannot backup /system....or atleast I cannot find where it backs it up.
The recovery says it backs up successfully but it should be on the SD card in a folder named sdx but there is no folder. The dev told me to open up a terminal emulator and type mount. This is what it spit out:
ootfs / rootfs ro 0 0
mpfs /dev tmpfs rw,mode=755 0 0
evpts /dev/pts devpts rw,mode=600 0
roc /proc proc rw 0 0
ysfs /sys sysfs rw 0 0
mpfs /sqlite_stmt_journals tmpfs rw,
dev/stl5 /system rfs ro,codepage=utf
check=no 0 0
dev/stl6 /data rfs rw,nosuid,nodev,c
=128,xattr,check=no 0 0
dev/stl7 /cache rfs rw,nosuid,nodev,
)=128,xattr,check=no 0 0
mpfs /sdx tmpfs rw,size=152k 0 0
Can I get any help on how to find this backup?
Spectral8x said:
Alright so I am trying to help out and get a backup of /system from my GF's samsung intercept. A dev over on SDX managed to flash a custom recovery to the phone. There are no issues from what I can find with the recovery accept for the fact that I cannot backup /system....or atleast I cannot find where it backs it up.
The recovery says it backs up successfully but it should be on the SD card in a folder named sdx but there is no folder. The dev told me to open up a terminal emulator and type mount. This is what it spit out:
ootfs / rootfs ro 0 0
mpfs /dev tmpfs rw,mode=755 0 0
evpts /dev/pts devpts rw,mode=600 0
roc /proc proc rw 0 0
ysfs /sys sysfs rw 0 0
mpfs /sqlite_stmt_journals tmpfs rw,
dev/stl5 /system rfs ro,codepage=utf
check=no 0 0
dev/stl6 /data rfs rw,nosuid,nodev,c
=128,xattr,check=no 0 0
dev/stl7 /cache rfs rw,nosuid,nodev,
)=128,xattr,check=no 0 0
mpfs /sdx tmpfs rw,size=152k 0 0
Can I get any help on how to find this backup?
Click to expand...
Click to collapse
Ok I did see this issue as well rooted and custom kernel on intercept but does not create the folders
go to the root of your sdcard and create the following folders
/sdx
and inside that folder create 2 folders /backup and /zip
reboot the phone and let it come back up, then reboot into recovery and choose the option for backup and then backup both /system and /data, then when you go back to the sdcard, the .tar file will be in the backup folder
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
Hello guys,
after flashing ICS on my Kindle Fire I can't see my internal storage files via terminal or file explorer. When I connect the kindle via usb to the computer, I can see files, folders and stuff I put there, but I couldn't find any way to see them from the kindle. Any ideas?
If I try to mount the second internal storage unit via settings -> storage it just tries for half a second and then goes back to where it was.
my mount output is this one:
127|[email protected]:/mnt # mount
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
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,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
[email protected]:/mnt #
I had similar problem with ICS but in my case a simple restart did the trick. You probably tried that already
I am in the same boat as OP. I finally took the plunge in rooting and installing ICS ROM on my Kindle Fire, been waiting for a good ICS Build. Unable to access internal storage. Rebooted several times. Clicked "Mount SD Card" and it shows for about a second and goes back to showing "Mount SD Card." Any help is appreciated.
FIXED!!! Booted into recovery, unmounted, remounted sd card, rebooted and was able to see internal storage. Hope this helps.
dragonsoul84 said:
I am in the same boat as OP. I finally took the plunge in rooting and installing ICS ROM on my Kindle Fire, been waiting for a good ICS Build. Unable to access internal storage. Rebooted several times. Clicked "Mount SD Card" and it shows for about a second and goes back to showing "Mount SD Card." Any help is appreciated.
FIXED!!! Booted into recovery, unmounted, remounted sd card, rebooted and was able to see internal storage. Hope this helps.
Click to expand...
Click to collapse
After installing droidwall and blocking the 1000 internal kf sync app, and after that unblocking it and uninstalling the droidwall I cannt understand why but it has "woken up" the kindle with wispersync app that it had install being rooted and it asked for regitration (an up that that didnt work before), and from then on I cannot se everything that I put in the "books" and "documents" folders! Have you any idea why?
dragonsoul84 said:
I am in the same boat as OP. I finally took the plunge in rooting and installing ICS ROM on my Kindle Fire, been waiting for a good ICS Build. Unable to access internal storage. Rebooted several times. Clicked "Mount SD Card" and it shows for about a second and goes back to showing "Mount SD Card." Any help is appreciated.
FIXED!!! Booted into recovery, unmounted, remounted sd card, rebooted and was able to see internal storage. Hope this helps.
Click to expand...
Click to collapse
Hey this happended on my LG Optimus 2X when I flashed ICS, I tried more or less all the file managers and the storage settings but they didn't work, then I tried this and it worked...thanks a lot
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.