Database Users

Atrix Touch Screen way off after SPF flash

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

Help with executing commands in adb; stuck at ".../bin/sh...No such file..." error

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 .

Crashing Nook

Well, my Nook appears to be in trouble.
The long and the short of it is that it got wet. Not too wet, but wet.
It boots but whatever I boot to crashes. This includes sdcard installs. The ROM completes the boot, and I can sometimes even open the app drawer, but it crashes before I can interact with it in any meaningful way.
All ROMs complain of "System process" and Wireless issues, with FCs.
I cannot get adb to recognize the device anymore. lsusb does find the Google Inc. entry, though. When I try and run adb devices (ubuntu), it returns ?????? and says insufficient permissions. I have, in response, set up the 99-android.rules in etc/udev/rules.d but it still cannot connect. I have also tried to quickly access the android terminal in the brief period I am allowed before the device crashes with no luck. My goal with this was to try fdisk -l.
The sdcard never mounts while in the ROM, and the emmc storage appears completely wiped.
However, I was able to see I had the correct files in /rom once, so those are there.
Thinking that the wireless chip might be the problem (as when even when I return to stock the set-up fails there, well, until it crashes again...) I tried to just turn off Wifi in 7.2. But as I unchecked the box, right under the setting just displayed "error"
CWM appears to be working EXACTLY as it should, including mounting the sdcard and allowing me to choose update zips.
The uboot and the uboot menu work as well.
I have tried flashing CM7, 9 and stock, as well as booting from sdcard in CM9. All flash and boot normally, but crash.
I have done the 8x reboots, succesully, but when the B&N set-up begins, I cannot connect to wireless. Which would be okay, in the long run, but it then crashes, which is not okay.
I was hesitant to reveal that it got wet, because I can see this being written off as a hardware issue (which it may be, don't get me wrong). But the fact that CWM works and the ROMs boot sure look like software problems to me.
I have tried flashing just about everything that looked promising. I have not dd any images, because I cannot get adb to work, and don't have any idea which partitions are in what shape.
Any suggestions?

Position the unit upside down with the SD flap open. Blowdry it from the bottom up on medium several times over a couple of days. If it's still doing it after that you can probably eliminate moisture as a cause.

old cell phone trick
Fill a bowl with rice (uncooked).....the rice will draw the moisture out.

you can also submerge it in ispropol rubbing alcohol... is what we use to clean electronic components... it will combine with the water... also used for water in gas on a car

Whoa, isopropyl alcohol. I feel like that would take some stones...
I have already put it through a 30 or so hour rice regimen (if that is true, even. It makes some kind of weird intuitive sense, which is usually the kiss of death...)
I have it standing up now and will see about a little air dry method while I investigate where to find the alcohol.
It didn't get submerged, it was lying on a counter and a glass got knocked over. I grabbed it right up, and then left it off like I said.
It boots, CWM works, but since it has been set all the way back to stock and all iterations have the same issue I am fearing the worst...
Thanks for the ideas...any and all welcome!

You can take the back off. I have not done it, but somebody just said they did it to disconnect the battery to reset. Look at that recent thread in q/a. Maybe he can tell you how he did it.

Attempt at your own risk, no support will be provided.
I'm not the battery guy leapinlar was talking about but,
Open the battery flap, remove SD card, remove the tape dots from the T-5 torque screws then remove the screws. Slowly and carefully so as not to break any of the hooky thingies that are holding the back on pry the cover up from that point moving slowly around the unit.
I've only done this once, it was a while back and I ended up breaking two of the little hooky thingies. That's why I suggested providing points for evaporation to escape and attempting to accelerate evaporation. Heck we don't even know if moisture is the issue anymore.

Thanks for the extra suggestions.
I tend to think at this point that whatever water got in there is gone. It's been four days, and it wasn't soaking. I may just go ahead and try and take out the battery, I don't know exactly why that would help, but what have I got to lose?
If I had to guess, I would think that the wifi chip might be shorted, as that is the only thing that doesn't seem to work at least for some period of time.
The FC's sure do look software related though. I fail to see how CWM could read and mount the sdcard while the ROM cannot as being anything other than sotware. Unless they use wildly different methods to do the same thing.
This nagging feeling that I should be able to at least fix that with some software methods keeps me thinking the same or the other problems. I'd be okay with an non-networked tablet, if it came to that. But maybe the thing has to have wifi as an option to work right. I don't know...

Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.

Malave said:
Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.
Click to expand...
Click to collapse
Considering that this is basically what is happening to me (but with some additional Wifi setting crashes) this gives me hope.
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
Anyway, of interest (before I shut it down 2 days ago):
internal sd card is not wiped, it can be explored in CWM.
The /ROM partition is at least somewhat functional, as battery stats can be wiped
When I request a log, I get:
Code:
Battery Stats
Block Groups: 3
reserved block group size: 23
Created filesystem with 11/22608 inodes
and 2883/90357 blocks
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure. Maybe that is why I am having trouble with ADB. It just kept saying insufficient permissions and ???????????. I tried setting up android-rules for udev with no luck.
Unless I hear anything else promising, I will go get the proper screwdriver and try the battery thing. It has been sitting off for a couple days now...
Thanks for all the ideas, people.

I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Try your edits to /rom... and if you have to try: mount /dev/block/mmcblk0p2 /rom

DizzyDen said:
I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Click to expand...
Click to collapse
I actually didn't try to do anything. I just wiped system, cache, davlik, battery stats and asked for a log prior to flashing a new zip in the hopes that the rom would work if provided a blank slate.
I wiped battery stats since the .bin that holds them is in /rom. The log was something I had never done before.
The notes from above were just the CWM output from the log.
edit: I just saw your second paragraph. Don't know how I missed it.
But I don't know what you mean by edits. I haven't been able to get ADB working. I have been able to mount and unmount through CWM that's it. Unless you might know anther way to resolve insufficient permissions with beaucoup question marks instead of device number?

Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.

DizzyDen said:
Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.
Click to expand...
Click to collapse
Which I was. I got it from Leapinlar, and was under the impression, since I had seen him warn that roms flashed from that recovery would go to emmc, that it would work.
I did make a regular 3.2.0.1 bootable, and tried again, but with the same result, so I don't know if that made a difference. But it did seem hopeful, so thanks for the response.
I am going to finally go get the torque screwdriver and take this battery off and give it some days. It's been almost a week already, but you never know.
Thanks a bunch for the reponses, Diz.

mateorod said:
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)[/CODE]
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure.
Click to expand...
Click to collapse
Mateorod, if you got that log using my CWM boot SD version 5.5.0.4, the recovery.fstab lists /dev/block/mmcblk1p2 as SD-EXT, which for some devices is the extended partition on SD for storing additional apps to supplement /data. Our implementation of CM does not use that. So when recovery tries to do some wiping, formating, backing up, etc, it always fails when it looks for that partition. It has nothing to do with /system or /rom.
If you told it to do a factory reset, it tries to wipe /SD-EXT as part of that and it fails to wipe that because it cannot find that partition.
Edit: That CWM SD does do its modifications to emmc. It only referenced mmcblk1p2 because of sd-ext.
Here is the filesystem table from my log using it on SD:
0 /tmp ramdisk (null) (null) 0
1 /boot vfat /dev/block/mmcblk0p1 (null) 0
2 /system ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /emmc vfat /dev/block/mmcblk0p8 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /sd-ext ext4 /dev/block/mmcblk1p2 (null) 0

The alcohol trick does work, I did it on my old HTC Kaiser. I disassemble it as much as I was comfortable, and then completely submerged it in alcohol until It stopped throwing up air bubbles; Thus showing there was no air left in the unit. I then removed the pieces from the alcohol and put them in a bowl of rice. I let it stand for about a week. Once the time was up a reassembled and turned it on like nothing had happened.
Little note: I was in the possession of a AT&T Go Phone for use as a back up in case this destroyed the unit. If you feel that there might be another way to repair it, I would suggest you explore that option first as I do not know what a significant time in alcohol will do to the inner workings of the Nook. However if you are at the point of already replacing or upgrading to a different tablet, than you have nothing to lose and can only gain a working Tablet or fancy Paper-weight from this.

Okay, a little update.
I had taken apart the Nook and let it sit for almost a week. But upon reconnecting the battery and clearing system/cache/davlik and reflashing anything, it still wouldn't allow in-ROM mounting of sdcard or adb or wireless and I would still get some version of "process System not responding" and "Setting Wireless not responding" toasts and then a crash, either in CM7, CM9 or Stock. Unusable.
What I think I have is a totally borked wifi chip. Which is okay, in the long run, but the Nook kept crashing and I would have liked to use it in some capacity.
What I decided (which was difficult to diagnose with no terminal or no ADB) was that the Nook was crashing upon trying to access the network and the saved network info. (which I know is mad persistent, as the wifi network I used to originally register the device still shows up in the stats, even after many many system wipes and 8x reboots and so forth.)
I had never reset to factory from stock settings and I couldn't now completely erase and deregister because you need wifi to do so.
However, I found this (which I had never heard of, sounds like a boon to thieves everywhere). After skipping out-of-box experience I could boot into stock recovery and finally erase the wireless settings.
Now I have a stable (albeit un-registered) stock nook, where I can at least read the books I have on sdcard.
I will eventually reflash a CM build now that the network settings have been forgotten and see if that is usable, even if there is no wifi.
But I am pretty happy to have some semblance of the Nook back, even if it is just a neutered (literally) stock.
I'll let you know how CM goes one day soon.
Thanks for the help!

Excellent, (and powerful), link.
And by virtue of that link I will find a way to proclaim my absolute geekitude within the company by dropping Kate's name. :good:

Well, I finally tried flashing Cyanogen 7 and 9 to the thing, but as it crashes when it tries to access wifi, I can't get it stable.
Unless anyone knows a code edit (smali maybe? I know there are a bunch of boolean settings in the SystemUI.apk, maybe there) where I can change the default wifi setting, I may just be stuck with stock.
Which is way better than nothing, at least it has use. Skipping OOBE was a life-saver for getting to a place where I could erase the WiFi info.

Okay, here's another shot in the dark, still trying to get this thing to successfully boot in CM...
I am working on a little project for the Nook, which will be infinitely easier to debug if I can actually boot into CM.
Does anyone familiar with the source code know how to modify it so that WiFi is set to off by default? I am thinking about changing the 'true' to 'false' in the /device/bn/encore/overlay/frameworks/base/core/res/res/values/config.xml entry for wifi found here...
Code:
<!-- This string array should be overridden by the device to present a list of network
attributes. This is used by the connectivity manager to decide which networks can coexist
based on the hardware -->
<!-- An Array of "[Connection name],[ConnectivityManager connection type],
[associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] -->
<!-- the 5th element "resore-time" indicates the number of milliseconds to delay
before automatically restore the default connection. Set -1 if the connection
does not require auto-restore. -->
<!-- the 6th element indicates boot-time dependency-met value. -->
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,1,-1,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<!-- item>"ethernet,9,9,2,-1,true"</item -->
</string-array>
This looks like I am on the right track (this will eventually end up being compiled into the res folder of framework-res.apk) but I may need to track down the ConnectivityManager. Although the cursory look I have given this seems like I may be close to on the right track...
(The wifi being on at boot always crashes my CM installs due to shorted wifi chip, for those of you who may be new to the thread.)
I am asking here just in case someone knows, I may just go ahead and try it if no one chimes in. But better to ask than to blindly shoot in the dark, I figure...
Update: Success. I am back on CM9 (well, a hybrid, actually...HINT), without wifi.
Update 2: Due to the fact that this nook is now in a Cyanogen-usable state, a new rom will be posted in development tomorrow from eyeballer and I. Thanks for the suggestions, everyone. I wish I had dipped it in isopropyl alcohol, just so I could say I did it...

Internal SD Card Paths

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.

I can't get /system to mount a re-writable?

I'm attempting to edit /system/etc/permissions/handheld_core_hardware.xml and upon trying to save I get an error "read-only filesystem"...
I'm rooted, s-off, with twrp.... running bad boys rom...
I've attempted to mount /system as rw using twrp...still get the error...
I've attempted using terminal/busybox to mount as rw...
I'm at a loss at this point...but I also feel like I'm fairly novice at this so maybe there's something I'm missing...
(for the record I'm trying to trick Google Daydream into running....I was able to on my S7 before switching to the bolt....if I can get this figured out and everything works I'll make up a guide to get daydream working on the bolt)

I finally got it working and GOT DAYDREAM HOME WORKING 100%...Used an old S4 as the controller and a modified samsung gear VR as the headset!
Guide coming soon!

rw mount on HTC Bolt.
I was wondering how you mounted your Bolt RW. I have also tried all of the different things you have listed trying to mount this puppy, but I have rolled 7's on all of it. Which leads me here and your post. Please tell me you figured it out and hook me up with the process. Thanks.