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.
Related
So, I took my microSD card out of my phone, put it into my digital camera, and my digital camera formatted the card. So, I lost all my pics I had taken with my phone. One of the pics, I have saved as the screen lock on my phone. Id love to get this pic off my phone, and onto my computer. can anyone suggest the best way to do this? Any responses are greatly appreciated! Thanks!
plug your phone into your computer via the usb cable and mount the sdcard via your phone
You could try this free deleted recovery software called Recuva. It works with removable media. I've attached it to this message for you.
where on the phone is the pic that is my current lock screensaver at? that pic is the pic I want, and I was unable to get it off the SD card (although other things I could get off there, thanks so much for that!). just curious, I would love to salvage this one pic.
/data/misc/lockscreen/
flipzmode said:
/data/misc/lockscreen/
Click to expand...
Click to collapse
alright, so... just to prove my noob status with android... how would I go about getting that off my phone from there?
jtmercutio said:
alright, so... just to prove my noob status with android... how would I go about getting that off my phone from there?
Click to expand...
Click to collapse
*makes mental note to add "pull any file" to my kitchen. heh*
Do you have the sdk / adb installed on your comp? Or are you a totally nubile noob? heh
If you do, from a command prompt it would be:
Code:
adb pull /data/misc/lockscreen c:\temp\
and make sure that c:\temp\ exists before you do it. If you don't have adb installed then download my kitchen (link is in my signature). Open a command prompt (on your computer) and then do this instead:
Code:
cd c:\folder-where-you-extracted-kitchen\adb\
adb-windows pull /data/misc/lockscreen c:\temp\
If you have any problems or errors then copy/paste them to me.
whew, got it. thank you guys sooo sooo much!
I use my Nook Touch for reading only. I do not need it to access the internet or download apps. From my understanding, these are the main reasons to root one's Nook.
What I am interested in is gaining access to that 1.5 GB or so of internal memory. As the majority of my books are side loaded, it makes much more sense to have 1.5 GB available to me and only 240 MB for B&N downloadable content.
My first question is, if I am going to try to re-size some partitions and I have no interest in apps, which rooter is the simplest for v1.1? SalsichaNooter or TouchNooter?
And finally, I have searched the forum and there are a couple of threads about re-sizing partitions, but they all involve linux terminal work. I think I might be able to figure it out, but could a linux disk partition program (like gparted) be used instead?
Ok, I found a thread posted by ros87 here that details how to go about resizing the partitions. It was very helpful, however, after rebooting back into my Nook, I am no longer able to connect to the internet.
I am not sure if either the sdb6, sdb7, or sdb8 partitions have any connection to wireless internet, but I noticed during the step of:
#mount /dev/sdb8 tmpdata
Click to expand...
Click to collapse
I got some socket warnings relating to a wireless file. ros87 says to ignore the socket warnings, which I did. Then at this step:
#tar xf tmpdata.tar tmpdata
Click to expand...
Click to collapse
I got a whole bunch of errors about unable to write files. But when I checked the drive, it seemed that all the folders copied over okay, so I continued on through the steps.
I probably should have copied the error output, but after discovering that wireless isn't working (it says "Unable to Connect"), I'm thinking maybe something didn't copy over correctly.
Should I try deleting and copying over the tmpdata.tar again?
Go trough dmesg and logcat (in adb shell) to see if you can find any troubles about your wifi connectivity, then post it here, but not the complete logs please!
As for my posted setup, I ran it for several weeks, with wifi enabled, without any troubles at all.
The socket errors is not the problem. A socket cannot be copied, and it is recreated whenever the socket service is started.
-R
Can I use adb if my Nook isn't rooted? As in, would I be fine just using noogie? I won't be able to try this until I get home.
Edit: Found this. I'm not interested in apps and such, so this seems the best option for me. Will post the dmesg and logcat later.
Okay, so I restored my backup image and checked the wi-fi. That is coming up as "Unsuccessfull", too. So maybe the problem is my wifi setup? My ipod connects fine, so I'm not sure what the problem is.
Just for future knowledge, is it safe to erase and de-register the device with different sized partitions?
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 .
Hi all,
I tried yesterday this mod, messing with swap and stuff at the sd card and installed swapper2 from market, but after hitting "on" at the app and tried to reboot, my phone died... and by that I mean completely died...
It doesn't power up, it doesn't boot at CWM neither at bootloader (pink screen).
When I plug it to the charger nothing happens and it doesn't get recognised by the PC also.
I tried booting without the sd card, i tried reformatting it (with swap or without swap) but again... nothing.
I tried to flash the stock firmware (dload folder at sdcard and stuff) but again it doesn't start the bootloader...
Any suggestions before I through it off the window much appreciated
EDIT: I was on latest Aurora...
You may have better luck accessing it through Linux.
If you can get access then you can restore a dd backup from someone.
That program uses root, right? And you put swap partition as mmcblk0p2?
If so, then it simply replaced your main bootloader with the swap file and you have to take it to repair service.
The correct way would've been to use mmcblk1p2, as external SD uses mmcblk1.
m!xal!s said:
You may have better luck accessing it through Linux.
If you can get access then you can restore a dd backup from someone.
Click to expand...
Click to collapse
All the above where done with Linux.
Blefish said:
That program uses root, right? And you put swap partition as mmcblk0p2?
If so, then it simply replaced your main bootloader with the swap file and you have to take it to repair service.
The correct way would've been to use mmcblk1p2, as external SD uses mmcblk1.
Click to expand...
Click to collapse
That is exactly what it did... I will sent it to service then ... I hope my 1 year warranty covers this... Thanks
If anyone knows a way to change the bootloader manually I would love him forever...
spirosbond said:
If anyone knows a way to change the bootloader manually I would love him forever...
Click to expand...
Click to collapse
You have to get phone boot from USB and then use USB JIG which contains bootloader to boot phone and then use some flash tool to flash bootloader to phone. It's very hard and I have no idea how get it boot from USB. Another solution is write bootloader directly to internal sd. I can't help you more.
Sent from my U8800 using Tapatalk 2
Can someone upload the mmcblk0p2 file? I think is inside /dev/block/ folder.
Does anyone knows how to boot something from the sd card? I don't know what... another ROM, another OS...
Thanks a lot.
http://db.tt/Qb32A8Z0
I know how to boot my galaxy tab from USB but I don't know about u8800.
Sent from my U8800 using Tapatalk 2
Qqqxxxzzz said:
http://db.tt/Qb32A8Z0
I know how to boot my galaxy tab from USB but I don't know about u8800.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
Can you post here what do you do to boot your tab from USB, and then I may find something based on that... who knows...
I just can't think of a way of booting it up. I tried to make the sdcard bootable disk with cm7 but again I cannot start the phone (or make it boot from sdcard). Copying mannually the bootloader seems easy but again I have no idea who I can acces that partition of the phone....
Thank you all for the help/tips
spirosbond said:
Can you post here what do you do to boot your tab from USB, and then I may find something based on that... who knows...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1312391
I think it will not work in u8800 because I don't believe that u8800 has iROM and OM pins.
Sent from my U8800 using Tapatalk 2
spirosbond said:
Can you post here what do you do to boot your tab from USB, and then I may find something based on that... who knows...
I just can't think of a way of booting it up. I tried to make the sdcard bootable disk with cm7 but again I cannot start the phone (or make it boot from sdcard). Copying mannually the bootloader seems easy but again I have no idea who I can acces that partition of the phone....
Thank you all for the help/tips
Click to expand...
Click to collapse
Can you try to make a partition on your sd card and dd the bootloader to that partition? After that, give the partition a bootable flag with fdisk and insert to phone. Try to start in many different variations, press the volume keys etc. If the soc bootloader has enabled a function to boot from sd card, somehow it would boot.
The emmc is soldered onto the motherboard. I don't think there are any ways to desolder it or replace.
Of course there must be another way to boot directly from sd card by using some pins, but I have not taken my phone apart to seek on that. Might do it someday though.
JTAG is the thing that would help you definately, but I don't think you have that and the box is pretty expensive too.
-EDIT-
I found this link, it says the phone should go in emergency download mode if loading flash disk fails, do you get any messages in Windows or by listing lsusb in Ubuntu do you get any result when connected with USB? There has to be a way to boot that emergency mode.
Blefish said:
Can you try to make a partition on your sd card and dd the bootloader to that partition? After that, give the partition a bootable flag with fdisk and insert to phone. Try to start in many different variations, press the volume keys etc. If the soc bootloader has enabled a function to boot from sd card, somehow it would boot.
Click to expand...
Click to collapse
I 've tried some things like that but it didn't work. I will try with the bootloader. Should I dd the bootloader.bin from here? I was using this mod since I f***** things up.
fdisk is something I'm not familiar with. Can you let me know how to "give the partition a bootable flag" please? Thanks !
Blefish said:
The emmc is soldered onto the motherboard. I don't think there are any ways to desolder it or replace.
Of course there must be another way to boot directly from sd card by using some pins, but I have not taken my phone apart to seek on that. Might do it someday though.
Click to expand...
Click to collapse
That would be so cool but I don't want to risk any chance of loosing my warranty (if I haven't already) .
Blefish said:
JTAG is the thing that would help you definately, but I don't think you have that and the box is pretty expensive too.
Click to expand...
Click to collapse
Ohh I wish I had one of these things...
Blefish said:
-EDIT-
I found this link, it says the phone should go in emergency download mode if loading flash disk fails, do you get any messages in Windows or by listing lsusb in Ubuntu do you get any result when connected with USB? There has to be a way to boot that emergency mode.
Click to expand...
Click to collapse
I don't get any indication when I connect the phone to any OS. I will send it to service tommorow and if nothing happens I will give it a try then, because it seems little complicated.
I will try the first thing you suggested (with the bootable bootloader) today. If you could answer the above question of mine it would be great
I can't thank you enough... We are lucky having you at our community.
Cheers man
I'm currently learning how to use Fdisk in unbutu to fix my own problem: http://forum.xda-developers.com/showthread.php?t=1694914
Here's something that may help you out:
https://help.ubuntu.com/community/InstallingANewHardDrive
1) Initiate fdisk with the following command:
sudo fdisk /dev/sdX
2) Fdisk will display the following menu:
Command (m for help): m <enter>
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help):
For: sudo fdisk /dev/sdX, where sdX is the disk or partition you want to modify.
If you don't know the disk or partition name, "ls /dev/sd*" should list all drives attached to the system.
From there, just use:
Command action
a toggle a bootable flag
I have not tried this, because I don't need to, but it seems to be what you're looking for. Hope it works for you.
If someone has better information, then please add to this. I just started learning unbuntu yesterday, and may not be completely correct.
If I come across anything that may help you, I'll let you know, and hope you'll do the same for me.
UPDATE: Also try disk utility in ubuntu. It's a lot easier and it has a gui.
Another UPDATE: http://www.thegeekstuff.com/2010/09/linux-fdisk/
Look for "6. Toggle the Boot Flag of a Partition Using fdisk Command a"
Thank you all. My phone has been fixed under warranty. They said that they changed the main board... Who knows... All good for now.
Thanks again!
spirosbond said:
Thank you all. My phone has been fixed under warranty. They said that they changed the main board... Who knows... All good for now.
Thanks again!
Click to expand...
Click to collapse
So there's no way for me to fix this myself without resorting to warranty?
S3nd41 said:
So there's no way for me to fix this myself without resorting to warranty?
Click to expand...
Click to collapse
Did you try the above solutions? If you did but no hope, then all you can do is send your phone to warranty.
Hi all,
First thread here .
So, on with it. I've been a member on this forum for quite some time, but never felt like posting or anything as I didn't have anything interesting to share and all the questions I might've got at some point got already answered...
Anyway, about a year a go I bought a Samsung Galaxy S III. Cute little 'monster', powerful and all... and I got hit by MTP. I'm a Linux user, so getting MTP to work was a huge pain. So I started reading, digging, found out that some guys already implemented some scripts for mounting the external SD as UMS... the problem was that they didn't work on my end.
So I developed my own little app. Nothin' fancy, two buttons to switch from MTP to UMS and back.
In the meanwhile, I changed my phone to a Note 2 LTE and did some more tweaking on my app and now I'm kinda ready to share it with you guys:laugh:.
You need to have a rooted phone equipped with busybox (my app will prompt warnings telling you you're not rooted or you don't have busybox, but I thought it was nice to tell you here the requirements).
One small thing, besides the usual "I'm not responsible to any damages brought to your phone and all": after transferring to / from your SD card, please use the eject command (or the safety remove feature on Windows) to unbind the card from your operating system before changing back to UMS. That way you ensure no harm is brought to you SD card or to the data on it.
All that being said, you can download the app from here: devver.ro/ums-mounter/ (I don't have enough posts to give an external link, so you'll have to enter the text manually in your browser). The text on that page is written both in Romanian (my native language) and English so there shouldn't be any problems .
This app should work on every device that has an SD card and runs Android 4.3+. Oh yeah, there might be some glitches on devices with Samsung's official releases (bummer, I know), but that's related to some screw-ups on their end, 'cause they're random from ROM to ROM.
Anyway, hope you'll like it (if you test it). If you have and problems, comment here and attach a logcat and I'll see if I'm smart enough to help you.
== 2014-06-10 ==
Version 1.1
Changes:
- please uninstall the previous version, as I've changed the signature on the file ;
- added a small sanity check which will force you to unplug your phone from the computer before switching between modes (hopefully this will also force you to safely remove the external sd card );
- fixed (i hope at least) the situation where the card is not mounted as usb on Touchwizz related ROMs;
As usual, the app can be downloaded from devver.ro/ums-mounter. Thanks again for testing .
sleepwalker123 said:
This app should work on every device that has an SD card and runs Android 4.3+.
Click to expand...
Click to collapse
It mounts the card slots (although it needs a reboot sometimes), but the PC shows up two empty usb slots and the sd card is not mounted.
Im running DN3 V5+.
I do hope you can fix it.
Thank you.
@erljayp: that's one ROM which is based on a stock ROM and, as I mentioned in my OP, there might be glitches woth 'em.
I'll setup my phone into dual booting so that's gonna be a bit easier to test these ROMs and hopefully sort them out.
Thanks for testing my little app
your app said that i haven't installed busybox yet. then i tried to install busybox from play store and it said the same. what problem?
ectv96 said:
your app said that i haven't installed busybox yet. then i tried to install busybox from play store and it said the same. what problem?
Click to expand...
Click to collapse
I've used play.google.com/store/apps/details?id=stericson.busybox to install busybox. Basically, after you install the app from the play store, you need to open it in order for it to actually download and install the busybox binaries. If you just downloaded the app from play store but didn't actually open it, that may be the problem
sleepwalker123 said:
I've used play.google.com/store/apps/details?id=stericson.busybox to install busybox. Basically, after you install the app from the play store, you need to open it in order for it to actually download and install the busybox binaries. If you just downloaded the app from play store but didn't actually open it, that may be the problem
Click to expand...
Click to collapse
oh yes, it works. thankyou :good::laugh:
New version, please check OP. Should resolve the DN3 related issues (this should apply to all ROMs which are based on stock Samsung). 'Njoy!
sleepwalker123 said:
there might be glitches woth 'em.
Click to expand...
Click to collapse
I thought you were talking about the "stock" rom. haha.
sleepwalker123 said:
Should resolve the DN3 related issues.
Click to expand...
Click to collapse
Now working in DN3 V5+, but I have fluctuating transfer rates. What is the average transfer rate you have?
Thank you.
@erljayp: i get about a maximum of 2 MB/s transferring a file bigger than 50-100 MB, which I find quite satisfying. Also, if I'm not mistaking, the transfer rates are influences by a lot of factors: the card's class, if you're transferring a lot of small files (mp3's, for example) etc.
Anyway, glad that sorted your problem. Like I said before, my app should now work not only on the DN3, but on all ROMs (CM11 based, AOSP, AOKP, ROM's based on the stock Samsung release). If you find a ROM that won't work, Iemme know and I'll see what's to be done about it .
sleepwalker123 said:
@erljayp: i get about a maximum of 2 MB/s transferring a file bigger than 50-100 MB, which I find quite satisfying. Also, if I'm not mistaking, the transfer rates are influences by a lot of factors.
Click to expand...
Click to collapse
I guess mine is normal.
Well, thank you very much for this great app and goodluck in your future projects.
sleepwalker123 said:
Hi all,
First thread here .
So--------.
Click to expand...
Click to collapse
The App crashes when trying to switch the pages.
Is this working on 4.4.2 TW roms ?
aukhan said:
The App crashes when trying to switch the pages.
Is this working on 4.4.2 TW roms ?
Click to expand...
Click to collapse
Don't try and switch pages All you need to do is "play" with the 2 buttons. I think the "page" you're referring to is something i use for debugging.. will remove it in a future release
sleepwalker123 said:
Don't try and switch pages All you need to do is "play" with the 2 buttons. I think the "page" you're referring to is something i use for debugging.. will remove it in a future release
Click to expand...
Click to collapse
I use Switch UMS and connect USB is that right any requirements to run the app apart from Root and busybox ?
aukhan said:
I use Switch UMS and connect USB is that right any requirements to run the app apart from Root and busybox ?
Click to expand...
Click to collapse
Nope. Those are the only requirements. Could you please give me a link to your ROM's thread?
sleepwalker123 said:
Nope. Those are the only requirements. Could you please give me a link to your ROM's thread?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=36202763#post36202763
Does this support windows or only linux??
aukhan said:
http://forum.xda-developers.com/showthread.php?p=36202763#post36202763
Does this support windows or only linux??
Click to expand...
Click to collapse
Grr... can't test that one...
Could you please connect your phone to your, connect into an adb shell, run mount and give me the output? Or if you have the Terminal Emulator app installed, do it from there and gimme the output.
sleepwalker123 said:
Grr... can't test that one...
Could you please connect your phone to your, connect into an adb shell, run mount and give me the output? Or if you have the Terminal Emulator app installed, do it from there and gimme the output.
Click to expand...
Click to collapse
You want me to run this # mount in terminal emulator and give you the results ?
Should i be connected to PC or not ?
aukhan said:
You want me to run this # mount in terminal emulator and give you the results ?
Should i be connected to PC or not ?
Click to expand...
Click to collapse
You don't have to be connected to the computer. Try and run the following in the terminal emulator:
- su (if you didn't);
- mount > /sdcard/mount.log
And after that, on your internal storage you shall find a file called mount.log. Give me the contents of that file, please.
sleepwalker123 said:
You don't have to be connected to the computer. Try and run the following in the terminal emulator:
- su (if you didn't);
- mount > /sdcard/mount.log
And after that, on your internal storage you shall find a file called mount.log. Give me the contents of that file, please.
Click to expand...
Click to collapse
Usage: mount [-r] [-w] [-o options] [-t type] device directory.
aukhan said:
Usage: mount [-r] [-w] [-o options] [-t type] device directory.
Click to expand...
Click to collapse
I think you ran the command including the dash ("-" sign).
Perhaps i didn't express myself well enough, sorry...
1). su (for gaining root access, no matter if you're doing this from the terminal emulator or from your pc);
2). mount > /sdcard/mount.log
Again, sorry for the confusion.