Related
I used RSD lite to flash to 4.1.2.6 and when it boots up the touch screen is way off and i can even go back or click the buttons on the bottom row. Anyone else have this happen? I reflashed twice already to see if it would fix it.
I've been toiling day and night for the last few days with the exact problem!!!
Tenfar is trying to help me via PM.
Because I partitioned internal SD this happened. I figure we need to do following command:
adb shell mkfs.vfat /dev/block/mmc0p18
And then
#newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18
But I'm getting random daemon errors now because my PC is a piece of ****!! Trying to fix that problem to run the first command. Second command goes through okay but I'm still having touch screen issues.
Waiting for him to PM back. I'm in Canada with an AT&T Atrix and although the seller can send me proof of purchase, to send it to Motorola would take super long and would cost lots in shipping.
If you find anything, please post it here. I'll do the same!
lol
lol yup thats what i did. I realized it wouldnt let me install from internal sd and i didnt have a external sd at the time so is figured let me format it.. whats the harm. Well the harm is the whole bottom row of buttons doesnt work and the bottom of the screen is a half inch off lol. Been driving me crazy, let me know if u get anywhere with tenfar
Getting stupid daemon errors I can't fix. Going to try on another machine and will let you know if there's any progress. Seems simple enough in concept but I'm no Linux genius.
I'll keep you posted.
Have u tried booting into the recovery and partitioning the internal sd another way?
fallchild said:
Have u tried booting into the recovery and partitioning the internal sd another way?
Click to expand...
Click to collapse
Yep. I've tried it all. Has to be manual now from what I gather... didn't get the chance to try on a new computer last night but will after work. I'll send you the commands if it works.
Dear lord, I hope it works!
Any Luck? I use my phone heavily for work and i had to use bluetooth all day with voice commands just to use the phone half way decently lol.
I had the same issue. I wasn't able to boot into my custom recovery and repartition. I ended up taking it back to AT&T and getting it exchanged. Can always pass it off as a bad device.
No luck. Same error. I tried mounting SD but I think I must be doing something wrong..
Still giving it another few tries. What a bummer. Gotta rip through the Atrix dump to see if I can find something else useful.
Can't unmount my SD card and successfully run the other command. Not sure what the heck I'm doing wrong. Now I'm uncertain what state my phone should be in when I run these commands.
I'm going to keep tinkering around but I'm waiting for the proof of purchase because I think I'll need to send it in. Damn. Wish I had someone in person that knew how to use shell commands properly. I'm not the greatest at this. Using an Xperia X10 in the meanwhile and dying to use my Atrix again. :'(
Hopefully someone will be kind enough to do a Nandroid backup of a fresh install and post it. I'm not sure but I think it could possibly help. It's worth a shot. Would pay someone $10 via Paypal if they could upload it to their Dropbox or something.
Hey OP, any luck?
If you have a new Atrix. Could you do a Nandroid backup and upload it to Dropbox by any chance???
I've exactly the same problem! (And when you are in some menu, you can't go back, so you have to reboot!!)
I did the same thing (Root, put recovery and so...)
I partitioned internal SD... And now, it's like touchscreen completly disturbed.
When you click on home - back or search, the screen select the bottom of the android interface!
I need to know if someone has a correct issue for that... I'm not at home, I will test the commands in adb from the second post later...
Also, I don't understand how a nandroid backup could resolve the problem... A backup will resize and fix the internal memory?
Thanks
Good evening everyone.
To start with, yes I've read all the similar topics and none of them helped me
To my problem now. My phone has been flashed with a custom ROM for 1-2 months now (I don't remember exactly) and this morning I woke up to find my phone turned off. While trying to turn it on, no matter how much time has passed, it's stuck on the splash screen refusing to load the home screen
Is there any suggestion that does not involve me losing all my data because I have no backup of them?
Waiting for any suggestions.
See if you can connect with usb, and adb can communicate with device.
If yes, you can save the /data/data folder(in which are all configurations) + /data/app folder(in which are all apps except these on sdcard if any).
You can also run adb logcat from command prompt and see if you can find what app causes the error and the bootloop, and if maybe you can uninstall/reinstall this app, or delete the folder of that app on /data/data folder, to hopefully solve the error.
Try to install a program like QtADB, droid explorer or Android manager to avoid use command line and simplify some of above operations as copy/delete folders or install/uninstall apps.
If you need more help, PM me to speak in greek(it' s better)
I've just installed QtADB and connected the phone while being inside ClockwordMod v4.0.0.5.
The truth is that from here I don't get almost any useful information (don't know why). One positive aspect is that I can copy data from/to the phone.
While stuck in the splash screen I can't connect through adb though.
You mean not at all? Usually when appears IDEOS screen you can connect via adb, after some time and when the error start maybe the device freezes and then adb probably disconects, but until then you can take some useful logcat info for the error.
You can also have some more functions with QtADB on recovery mode if you mount the partitions first.
Maybe and the app manager work then(I haven't tested though).
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
gkaran said:
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
Click to expand...
Click to collapse
By reading your log i think the problem is permissions. Try to fix permissions with recovery tool.
Help with executing commands in adb; stuck at ".../bin/sh...No such file..." error
I am out of all tricks now for reviving my Note which boots into download and recovery mode. I conclude that from what I have experienced, that factoryfs is the partition which fails to take any write commands when I odin a ROM, as it gets stuck at the factoryfs message. I have tried all the flashing of kernels and ROMs with no luck.
Working with adb seems to be the only option, to configure the partitions on my device manually. The big issue is that I am not able to execute "adb shell" command using Forest1971's guide.
So far, I have had no luck going beyond the "exec -/system/bin/sh...:No such file or directory...(2)" error message, when I type the "adb shell" command.
Can someone with the know-how of how to work through adb help with this? This is my last effort of trying to recover my Note, and if it fails, I will have no choice but to sent the device out of the US. I dread sending my phone out of the country for repairs, as I don't know just how long it will be before it gets fixed and is shipped back to me.
Please do not suggest any flash options, because as I said, I have tried all there is to do with flashing - nothing has helped.
First see if you have a /system filesystem. Looks to me that it doesn't exist. See if you can type
Code:
$ cd /system
or
Code:
$ cd /system/bin
If it complains then there's your problem - you don't have a functioning /system. Maybe type mount and show your filesystems.
I know you asked for no flash suggestions, but have you tried making the device do a hard reset - when powered off hold down home, volume up while holding down power on then release power button when screen shows life. May be worth a shot, but looking like another ICS firmware/emmc issue from here... good luck.
[edit]
should have read your post more closely. Looks like you have no /system/bin/sh at all so can't fire up a shell, so you can ignore my initial suggestion.
paulshields said:
First see if you have a /system filesystem. Looks to me that it doesn't exist. See if you can type
Code:
$ cd /system
or
Code:
$ cd /system/bin
If it complains then there's your problem - you don't have a functioning /system. Maybe type mount and show your filesystems.
I know you asked for no flash suggestions, but have you tried making the device do a hard reset - when powered off hold down home, volume up while holding down power on then release power button when screen shows life. May be worth a shot, but looking like another ICS firmware/emmc issue from here... good luck.
[edit]
should have read your post more closely. Looks like you have no /system/bin/sh at all so can't fire up a shell, so you can ignore my initial suggestion.
Click to expand...
Click to collapse
Suggestion ignored. Any more?
Get an iPhone?
Look at this thread
http://forum.xda-developers.com/showthread.php?p=26279833
Sent from my GT-N7000 using Tapatalk
paulshields said:
Get an iPhone?
Click to expand...
Click to collapse
I won't go the route of laughing and mocking you for saying that. I do think it's a very well put together device, but it just doesn't serve my needs of a big screen, the ability to be free...etc. By the way, you asked me to ignore your suggestion, so I did - FYI.
zviki said:
Look at this thread
http://forum.xda-developers.com/showthread.php?p=26279833
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
I was in that thread, and the suggestions didn't help as it is too complex a process. I was hoping to pick up from scratch, so I created this thread.
incisivekeith said:
I won't go the route of laughing and mocking you for saying that. I do think it's a very well put together device, but it just doesn't serve my needs of a big screen, the ability to be free...etc. By the way, you asked me to ignore your suggestion, so I did - FYI.
I was in that thread, and the suggestions didn't help as it is too complex a process. I was hoping to pick up from scratch, so I created this thread.
Click to expand...
Click to collapse
Hi, please take a look to my post. http://forum.xda-developers.com/showthread.php?p=26350317#post26350317
Just flash that kernel from cmw, and you should be able to run commands on adb shell.
matiasg85 said:
Hi, please take a look to my post. http://forum.xda-developers.com/showthread.php?p=26350317#post26350317
Just flash that kernel from cmw, and you should be able to run commands on adb shell.
Click to expand...
Click to collapse
Thanks for the kernel, but it seems you didn't have much luck solving the issue, even after doing everything in adb correctly. Is that the case?
incisivekeith said:
Thanks for the kernel, but it seems you didn't have much luck solving the issue, even after doing everything in adb correctly. Is that the case?
Click to expand...
Click to collapse
Yes, unfortunatelly i did everything as stated on adb, but had no luck. If ssc don't replace it, i will try using the memory blocks used by the "internal sd card".
You must try it anyway, there were some users that succesfully unbricked the phone.
Did anyone try this mk2efs command with -c option ON ??
Sorry Incesivekeith
I was out of connection for past 2 days.
We have to pull Mr Forest1971 for doing this.
Let me sum up :
parted is not able to solve your issue.
mk2efs is another formating tool that comes with CWM
You are stuck up in executing commands.
Now the idea of flashing the cwm kernel is fine. Did u try that ??
Mr Forest1971 :
Did you see Dr Sumralls comments for this bug.
''He says that we have to go for a full wipe. I have a tool but I dont know I couldnt share it.''
incisivekeith said:
I won't go the route of laughing and mocking you for saying that. I do think it's a very well put together device, but it just doesn't serve my needs of a big screen, the ability to be free...etc. By the way, you asked me to ignore your suggestion, so I did - FYI.
Click to expand...
Click to collapse
I asked you to ignore the initial suggestion as you've obviously not got any functioning recovery. You've not provided much info about how you got to this position, but in my similar situation I got out of it by successfully flashing a FULL WIPE factoryfs (LA4 in my case) and doing the factory reset as I mentioned in my first response. I lost a few GB of my eMMC storage but got a working device. May not help you, but may be useful info for others. Share and share alike. Good luck dude .
Hello to all you developers out there.
For quit some while now is recieve a consistent warning pop-up whenever i reboot my phone. It only occourse when i'v installed a TW rom. When i'm running any other rom like a GPE for example, the warning does not appear.
Currently i'm on Goldeneye 49.2. My phone is a GT-I9505 on baseband-version: I9505XXUGNK4
I'm not a developer, but a true flashjunky. I would not now how many times is flashed one of your roms and so i do not now specific when this problem started. I'v spend much time browsing the internet in search of this problem and how to fix it. But my effords where not succesfull. The only thing i might have picked up about it, is that is could be related to a corrupt EFS. I hope some of you out there can give me a headsup about this.
Plus! I want to thank all you devoted developers out there. Your hard work and effords are much apreciated.
I have made a picture of the warning.
Thank you for taking your time reading this and i hope someone knows how to fix this.
Greatings,
Peter
From the Netherlands
peterd689 said:
Hello to all you developers out there.
For quit some while now is recieve a consistent warning pop-up whenever i reboot my phone. It only occourse when i'v installed a TW rom. When i'm running any other rom like a GPE for example, the warning does not appear.
Currently i'm on Goldeneye 49.2. My phone is a GT-I9505 on baseband-version: I9505XXUGNK4
I'm not a developer, but a true flashjunky. I would not now how many times is flashed one of your roms and so i do not now specific when this problem started. I'v spend much time browsing the internet in search of this problem and how to fix it. But my effords where not succesfull. The only thing i might have picked up about it, is that is could be related to a corrupt EFS. I hope some of you out there can give me a headsup about this.
Plus! I want to thank all you devoted developers out there. Your hard work and effords are much apreciated.
I have made a picture of the warning.
Thank you for taking your time reading this and i hope someone knows how to fix this.
Greatings,
Peter
From the Netherlands
Click to expand...
Click to collapse
Hi mate,
Indeed it could be related to an EFS problem......It would help us to help you if you tell us what you tried so far to fix it
MAX 404 said:
Hi mate,
Indeed it could be related to an EFS problem......It would help us to help you if you tell us what you tried so far to fix it
Click to expand...
Click to collapse
Hi There,
Thanks for your quick reply. As soon as i read about the EFS, i also read about the backup of the EFS. But i didn't have on.
I made a backup and tried to restore. But i gues a corruption would also be backuped. I also tried to manualy adjust the EFS. Neither workt. Following that i tried holding down the power button for more then 10 seconds till it rebooted (read that somewere between de lines). I also tried various other roms, kernels and basebands. I full despiration i tried returning to fully stock rom. Nothing worked.
Now it has been about a month and a half i left this issieu. So ik can not be very specific about mij tries to resolve.
Is this in any way helpfull?
that is one of the saddest thing that will happen to your phone. My sister has s2 and s3 and she was a flashaholic with different roms and now both phones have no signal/baseband unknown.. She never back up her efs so she cant fix it. I tried my very best to search for an answer, i saw some but it never solve it anyways. Im using my s4 and i backed up my efs every flash that i do. Try to flash official rom, latest modem and pray that it will fix it.
peterd689 said:
Hi There,
Thanks for your quick reply. As soon as i read about the EFS, i also read about the backup of the EFS. But i didn't have on.
I made a backup and tried to restore. But i gues a corruption would also be backuped. I also tried to manualy adjust the EFS. Neither workt. Following that i tried holding down the power button for more then 10 seconds till it rebooted (read that somewere between de lines). I also tried various other roms, kernels and basebands. I full despiration i tried returning to fully stock rom. Nothing worked.
Now it has been about a month and a half i left this issieu. So ik can not be very specific about mij tries to resolve.
Is this in any way helpfull?
Click to expand...
Click to collapse
Hi
Well let me tell you about a few things you can try , with some luck they may be enough if not you may have to take it to a local repair shop with a Z3X box of similar they may be able to rebuilt the EFS folder
Check if the EFS folder is mounted correctly
Install / use Terminal Emulator
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
mke2fs /dev/block/mmcblk0p10
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
Reboot
With a root explorer go to EFS/factoryApp/factorymode and open it if it says off change it to on
In case none of the above worked check this great thread about EFS and Factory Mode for further help…..
http://forum.xda-developers.com/showthread.php?t=2392632
If those points do not work and without an working EFS backup you may have to look for professional help ( with a Z3X box or similar )
MAX 404 said:
Hi
Well let me tell you about a few things you can try , with some luck they may be enough if not you may have to take it to a local repair shop with a Z3X box of similar they may be able to rebuilt the EFS folder
Check if the EFS folder is mounted correctly
Install / use Terminal Emulator
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
mke2fs /dev/block/mmcblk0p10
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
Reboot
With a root explorer go to EFS/factoryApp/factorymode and open it if it says off change it to on
In case none of the above worked check this great thread about EFS and Factory Mode for further help…..
http://forum.xda-developers.com/showthread.php?t=2392632
If those points do not work and without an working EFS backup you may have to look for professional help ( with a Z3X box or similar )
Click to expand...
Click to collapse
Thank you very much for your help. I did tried to fix the EFS with the guides in the site you mentioned repeatedly. But none were succesfull. The strings you mention in your post, do not look formiliar and i tried them just now. After the second string i get the following in the Emulator:
" can't format mounted filesystem"
Could this be the issieu? Both de FactoryApp and Keystr are on ' ON ' when i open them in a rootexplorer.
And i'm starting to think this problem will, despite all your help, not be resolved.
@MAX 404 try to go to the nearest cellphone repair shop they have this cable that can fix that issue. Its around 4-5$ depends on your country.
shthppns said:
that is one of the saddest thing that will happen to your phone. My sister has s2 and s3 and she was a flashaholic with different roms and now both phones have no signal/baseband unknown.. She never back up her efs so she cant fix it. I tried my very best to search for an answer, i saw some but it never solve it anyways. Im using my s4 and i backed up my efs every flash that i do. Try to flash official rom, latest modem and pray that it will fix it.
Click to expand...
Click to collapse
I did a full restore to official rom, but did not do the trick. This problem is a real pain in the ...
Maybe in a little while, when i can get the Note 4, i need to think about controlling my flashfrenzy. My wife would certanly like that
peterd689 said:
I did a full restore to official rom, but did not do the trick. This problem is a real pain in the ...
Maybe in a little while, when i can get the Note 4, i need to think about controlling my flashfrenzy. My wife would certanly like that
Click to expand...
Click to collapse
GL peter! Going to switch with s6 edge soon though my s4 still a beast.
peterd689 said:
Thank you very much for your help. I did tried to fix the EFS with the guides in the site you mentioned repeatedly. But none were succesfull. The strings you mention in your post, do not look formiliar and i tried them just now. After the second string i get the following in the Emulator:
" can't format mounted filesystem"
Could this be the issieu? Both de FactoryApp and Keystr are on ' ON ' when i open them in a rootexplorer.
And i'm starting to think this problem will, despite all your help, not be resolved.
Click to expand...
Click to collapse
Hi
Regarding the string , Are you root at the moment , maybe that is the problem , i have not tried in while but they should work...did you check in the thread i gave you?
regarding your other point , ON is the normal , ON is not factory mode...strange but is like that..
MAX 404 said:
Hi
Regarding the string , Are you root at the moment , maybe that is the problem , i have not tried in while but they should work...did you check in the thread i gave you?
regarding your other point , ON is the normal , ON is not factory mode...strange but is like that..
Click to expand...
Click to collapse
I found a wrong reverence in the string. In your string you refer to mmcblk0p10. Except voor the S4 it's ...0p3. Found that out after you let me check the thread again. Although the factory mode is still on after inserting your three strings.
Second thing i noticed was that with the first two string, i get a repley string and info that i can't understand. With the third string, i get no reply string in the emulator. Do you think this can be part of the problem?
I also included a screenshot from the emulator.
peterd689 said:
I found a wrong reverence in the string. In your string you refer to mmcblk0p10. Except voor the S4 it's ...0p3. Found that out after you let me check the thread again. Although the factory mode is still on after inserting your three strings.
Second thing i noticed was that with the first two string, i get a repley string and info that i can't understand. With the third string, i get no reply string in the emulator. Do you think this can be part of the problem?
I also included a screenshot from the emulator.
Click to expand...
Click to collapse
Hi
Try this
http://forum.xda-developers.com/showpost.php?p=44315069&postcount=21
Hey guys,
Quick newbie question for you. I followed the procedure in this thread ([ROM][5.1.1][LMY47V] 21 May- Stock Flashable Rom/Factory Image) to a T and have 5.1.1 on the Nexus 4 but for some reason my internal SD card paths are all messed up. I couldn't use my camera to take a photo - it wouldn't save anywhere.
I used Terminal to run the restorecon -FR command for /data/media/0/* and then I restarted the phone and I could use my camera, so that was a good step.
Now I'm in WhatsApp and I can't see any media that people are sending me. The photos stay blurry. Is WhatsApp pointing to a directory that doesn't exist? How can I solve that? Or is my internal SD card ****ed?
I am using TWRP so if you have any solutions I can fully utilize that to fix the path errors or re-flash system img or whatever you think will work! My brother is trying to send me photos through WhatsApp and I can't see 'em!
Any help is appreciated!
--Mike
Did usie the script included with the stock ROMs to flash back to stock?
audit13 said:
Did usie the script included with the stock ROMs to flash back to stock?
Click to expand...
Click to collapse
You mean the flash_all.bat? Nah - I manually flashed as per the forum thread I linked to. I installed through TWRP, not fastboot. My Nexus 4 only connects as an AC source so I can't even get it communicating with my PC to unroot and flash stock.
So the phone is not recognized in OS X, window, or Linux? Tried different USB cables and USB ports?
audit13 said:
So the phone is not recognized in OS X, window, or Linux? Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yeah I've pretty much tried everything to get it communicating with the computer again. I think it's a hardware issue - I had my screen replaced and I think some part of the battery assembly wasn't re-installed properly and thus communication ceased. I thought flashing to 5.1.1 would fix what could have been a 4.4.4 issue, as I had USB fast charge enabled with various kernels, but alas this was not to be.
Any ideas about the internal paths?
A screen replacement does involve moving the USB charging port to the new screen and it is possible that this part was damaged and vertical seems to be the case. I assume you don't have access to another phone to test the port.
audit13 said:
A screen replacement does involve moving the USB charging port to the new screen and it is possible that this part was damaged and vertical seems to be the case. I assume you don't have access to another phone to test the port.
Click to expand...
Click to collapse
Yeah no other phone to test the port. I just got an X Play and am using the same cable I was using with my Nexus 4 and communication is flawless - adb, fastboot, all the goodies. I thnk I'll need to take the Nexus to a shop or open it up myself.
Thanks for paying attention to this thread, audit.
Try opening the phone yourself as it is pretty easy but that choice is yours. Good luck!.
Hi Mike, just a hint... did you check the partition status on your device ? To check if it's a logical or hardware issue, here's a reference: http://forum.xda-developers.com/moto-x-play/general/partition-layout-t3196367
You can analyze yours with something like: https://play.google.com/store/apps/details?id=com.cls.partition
and eventually mount manually the missing mounts.
dev>null;5160773 said:
Hi Mike, just a hint... did you check the partition status on your device ? To check if it's a logical or hardware issue, here's a reference: http://forum.xda-developers.com/moto-x-play/general/partition-layout-t3196367
You can analyze yours with something like: https://play.google.com/store/apps/details?id=com.cls.partition
and eventually mount manually the missing mounts.
Click to expand...
Click to collapse
Great idea, dev. How do I go about manually mounting? Do I need to use Terminal or something similar?
Thanks for your reply.
mounts & partitions
@XxMikeMasterxX Yes! In terminal emulator.
Code:
su
cat /proc/mounts
- or -
mount
- or -
df
- or -
cat /proc/partitions
to list all partitions/devices/... a bit messy output
The mount command is also what you'll need after you find the problem.
It can mount a partition, remount read-write...in case it's a permission problem, or bind a folder to another, in case it's looking for a specific folder, but your system named it in a different way.
Not sure if this applies to your case...just an idea Did your partitions check return any anomaly ?
dev>null;5160773 said:
@XxMikeMasterxX Yes! In terminal emulator.
to list all partitions/devices/... a bit messy output
The mount command is also what you'll need after you find the problem.
It can mount a partition, remount read-write...in case it's a permission problem, or bind a folder to another, in case it's looking for a specific folder, but your system named it in a different way.
Not sure if this applies to your case...just an idea Did your partitions check return any anomaly ?
Click to expand...
Click to collapse
Not that I can see. I'm a bit of a noob with Terminal so I'll even have difficulty identifying the erroneous file paths. It's too bad my adb and fastboot don't work. Or else I'd just revert to stock and re-flash everything.
@XxMikeMasterxX If you don't want to mess with terminal, try using the app linked in my first message then (or others that show mount points and partition details), and please use this as a reference. I posted the MXP one by mistake !!!
dev>null;5160773 said:
@XxMikeMasterxX If you don't want to mess with terminal, try using the app linked in my first message then (or others that show mount points and partition details), and please use this as a reference. I posted the MXP one by mistake !!!
Click to expand...
Click to collapse
@dev>null Eeeek! Scared! I'll try the app and see what I can see. I guess from there it's a simple remount.
So hypothetically let's say that sdcard is mounted somewhere else by mistake and some app folders end up on the wrong partition/location, do I use a remount to remount that particular folder/location to the proper sdcard path?
Whoa I think I just got it.
@XxMikeMasterxX Exactly! There used to be a bug in CM with wrong sdcard mount point. Take a look at this, I'm sure it will address you to the right direction
And also give you examples for command syntax...
dev>null;5160773 said:
@XxMikeMasterxX Exactly! There used to be a bug in CM with wrong sdcard mount point. Take a look at this, I'm sure it will address you to the right direction
And also give you examples for command syntax...
Click to expand...
Click to collapse
You're the man. I'll try it soon. My brother has the phone now so it could be a bit.
XxMikeMasterxX said:
You're the man. I'll try it soon. My brother has the phone now so it could be a bit.
Click to expand...
Click to collapse
@dev>null
My brother tried the Terminal commands but after he entered su and tried the other 4 commands Term returned "nothing found" each time. What does that mean?
Also, it appears that he needs to remlunt his entire SD card somewhere. What's the folder? Root/sfcard
@XxMikeMasterxX Nexus 4 does not have a physical sdcard, so I guess it's just a missing symbolic link.
Try:
Code:
su
mount -o bind /data/media /sdcard
and see if Whatsapp can save the images now.
Also you may want to check this guide: http://forum.xda-developers.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447
dev>null;5160773 said:
Also you may want to check this guide: http://forum.xda-developers.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447
Click to expand...
Click to collapse
@dev>null
Thanks for your recommendations. Yet again, though, the command you provided didn't work. I tried to get him to bind different locations to sdcard but that didn't help either.
A funny thing he told me is that under Settings>Storage he can't open the Internal storage section. He said it just doesn't open.
It's almost like Android installed to a really weird location and isn't recognizing anything. I am really baffled.
I checked out the guide - the o ly problem.is that the phone doesn't connect as a USB device (broken link...battery maybe?) and as such he can't run the adb commands.
I wish it did connect USB though - I'd just have him return to stock and then this would all be erased. Any other ideas, dev? I really don't know what to do next... Thanks for your ideas so far - you've been a great help.