Related
Hi all,
I have an issue with my HTC Magic (Rogers' 32A), I am pretty pessimistic about being able to fix it, but if I don't ask I will never know
So here's the problem:
My phone fell in the water.
I took it out, removed the battery, let it dry.
Now everything is working fine except the USB connection, when I plug it to a PC via USB there is no notification, but the phone charges fine.
Basically I don't see the USB device and the can't browse the sd card, I have to take it out and use a card reader.
Also I can't adb, fastboot etc...
Other weird thing happening, when the phone is off the screen is always on, I have to remove the battery for the screen to completely shut off.
When the system is running, when I press the END/Hang Up key, the screen shuts off normally
It seems like a Hardware issue, that's why I don't think there is a (easy) way to fix it.
But I am asking here just in case.
Thank you.
sounds like a hardware issue...
Thank you, that's what I tought...
I ordered a screwdriver for the phone... gonna try to clean up the inside...
Anyone knows if there's a tutorial on how to take the phone appart and putting it back together with out breaking anything ?
check out this thread for service manuals with full tear down info, page 2 specifically for the download link (phandroid), the links on page 1 are dead now
http://forum.xda-developers.com/showthread.php?t=490774
also you can google magic service manual and find tons of links..
good luck, hope you can get your magic fixed
Go into terminal and see if you can manually mount it
$su
#mount /sdcard
___________________________
If that doesnt work, you might want to search for the /dev/block
that enables it internally.. Its around here, but im too lazy to look and link.
x) hope that helps you..
I got the PDF, that's exactly what i was looking for, I shall try it when I get the tools.
I tried the mount technique but it failed:
Code:
mount: mouting /dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy
Thanks guys for all your help.
no, just
$su
#mount /sdcard
thats it lol no dev
jamsk8er1994 said:
no, just
$su
#mount /sdcard
thats it lol no dev
Click to expand...
Click to collapse
yes, that's what I did.
I just pasted the result.
sorry should have been more specific.
like this :
Code:
$su
#mount /sdcard
mount: mouting /dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy
#
Ok, I finally got to disassemble the phone, clean up and blow away the dust/dirt.
And it seems like it fixed the USB issue, I am able to see the usb drive, adb, fastboot, etc...
But the screen is still back lit when the phone is turned off...
Anyways
Thanks for all you help guys.
Cant figure out for the life of me how to reroot after doing the 340 ota. I came from 2.2 ota.
I tried z4root multiple times, no dice.
Tried the DoRoot Automatic script. Didnt fully work.
Tried the manual method on the phone with term emu.
Tried the manual method...and im getting stuck here...
Factory Reset and did it all AGAIN... So annoyed
Mod note from Sleuth
Wispirer figured this out further down in the thread. It has to do with different versions of the superuser apk file confusing z4root. His post is here
nicely done btw
end mod note
[*] Searching for adb ...
[+] Found adb as PID 6025[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] [email protected] so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb kill-server
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb.exe devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A9D7E1303301A device
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb shell
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
$
z4root sat for 5-10 minutes on "running exploit" when I ran it. Others have also reported this.
I experiened that ONCE too, but i pulled the battery after a few minutes since it went through the full process so many times before.
anyone any ideas?
same problem here...can't get root back yet
Just to make sure, when you guys are rooting you have USB debugging on, yeah?
Also, does 1click root work? Several DX flavors. Check the Wiki. Link in DX android development.
Some questions:
What precisely happens when you try to use z4root? Give me the step by step.
Can you get temporary root with z4?
Sleuth255 said:
Also, does 1click root work? Several DX flavors. Check the Wiki. Link in DX android development.
Some questions:
What precisely happens when you try to use z4root? Give me the step by step.
Can you get temporary root with z4?
Click to expand...
Click to collapse
It goes through the whole process, says its rooting, getting shell, etc, goes white for a second, says rebooting, come back up and no root. And nope, tried both options.
Same here. The main thread about the update says it can take as many as 10 tires. I'm on about #5. we'll see.
That doesnt quite make any sense to me....
Same thing is happening to me, z4root says using exploit, acquiring root shell, goes to white screen then goes back and says rebooting. After it reboots still no root.
Tried 1 click method and it hangs at performing the rage command. Manually tried rooting and after applying the ./rage it kicks me off like its supposed to then says my device isn't found when I do adb devices command.
Yup, Same. I even factory reset twice.
Interesting. I have both copies of the update.zip. I did notice that they were slightly different in size. I used the very first one that was posted. I'm gonna do a quick hex compare to see if they're the same...
edit: uh oh, the two update files are totally different. The original one is slightly larger and HexCMP finds no similarities after the first 1K or so. The one I used had a size of 26,358. The other, more recent one has a size of 26,259.
So whats that mean exactly? Two versions of OTA were pushed out? One rootable and one not?
It sure looks like there's two different sizes and a hex compare shows significant differences. Take a look at your update.zip. What is the precise size? If everybody who can't root has a size of 26,259 then the validity of your thought is supported.
Remember, the original update only went out to a special beta test group and then was quickly pulled. The one I used was that update.
Where do i find the update.zip file? I did the ota update
Review the Droid X 2.3.340 Update thread in this forum. Good history about this update there including the information you seek.
I tried to root with Sil3ntK1ll Root X 2.2 and it looked like it was taking until about 3/4 of the way it said waiting for device. I left it for 5 min and it was then locked up solid. I had to pull the battery and reboot. No ill effects after the reboot but I am not rooted.
So I assume the root authors are already hard at work on fixing this issue?
same story as everyone else, had root, did update, cant get it back
Found this method, hxxp://forum.androidcentral.com/motorola-droid-2/40283-how-root-droid-2-without-computer.html (note: change x's to t's) and lo and behold it worked! Did from top to bottom and now back to being rooted. Hopefully this method works for you guys.
Hi all,
Have any of you been able to get a Cifs share mounted under android 4.3 on the N10.
I've tried various kernels and managers like Cifs manager but with no joy, they complain of invalid argument.
It seems like there has been success on the N7 according to this thread http://forum.xda-developers.com/showthread.php?t=2107224&page=7 but I can't see anything for the N10.
If it does work for you could you let me know what ROM / Kernel combo you use?
Not only 4.3. I haven't managed to make it work on 4.2.2 either
Sent from my GT-I9505 using Tapatalk 4
http://forum.xda-developers.com/showthread.php?t=2430056
^^^^^^^ What zod said. Working fine for me
I tried several combinations to mount CIFS shares with mountmanager:
Trinity + Carbon Rom, Sentinel, CM10.2 = works without problems
Flaming Monkey + Carbon Rom, Sentinel, CM10.2 = works - but without UTF-8 (for special characters like öäü...)
KTManta + Carbon Rom, Sentinel, CM10.2 = doesnt work.
Any Kernel + Purity Rom, AOKP, PA = doesn't work.
Could someone please confirm if CIFS is finally dead on Android? I haven't seen a single user manage to make it work. I even asked kernel developers to patch their kernel with this only solution provided here and even though they were happy in the beginning they never wanted to talk about it later which makes me think it was a hell or them.
I'd really like to know if I should just uninstall all CIFS related staff and just forget about it.
Edit:
Sorry I think it's wrong threat
andreasy said:
Could someone please confirm if CIFS is finally dead on Android? I haven't seen a single user manage to make it work. I even asked kernel developers to patch their kernel with this only solution provided here and even though they were happy in the beginning they never wanted to talk about it later which makes me think it was a hell or them.
I'd really like to know if I should just uninstall all CIFS related staff and just forget about it.
Edit:
Sorry I think it's wrong threat
Click to expand...
Click to collapse
Google sure seems to be trying really hard to kill CIFS (and any network filesystems for that matter) on Android. As it stands now (in 4.3) there is no possible way to get CIFS working properly on the stock ROMs with a stock kernel. This is because the geniuses at Google removed loadable module support from the stock kernel and because of the way they implemented the multi-user stuff (using filesystem namespaces). The thing that kills me is that there is absolutely no reason for Google to make this so difficult. They could have simply compiled support for network filesystems into the kernel if they wanted to remove modules for "security". It would also be trivial for them to add a mount point which propagates to the user namespaces. They did this crap on purpose. And that is exactly the reason why my next tablet will not be an Android one. You shouldn't have to hack your tablet to get basic functionality that should just work out of the box. I'm done being scroogled.
Anyhow, I did manage to get CIFS working on my Nexus 7 which is running 4.3. See my post here for details. Now, I don't think my kernel will work on your Nexus 10. But, if you flash someone else's custom kernel (or compile your own) for the Nexus 10 which does have CIFS support/modules you should be able to use my update.zip which does not contain the kernel. I don't have a Nexus 10 to test on, so I can't promise anything but I don't see why it wouldn't work.
With new 4.3.1 Rom Versions I have troubles with CIFS Mount.
I can mount my NAS without problems with Terminal command, and I can see all mounted Files and Folders in Terminal.
But any App (like ES Fileexplorer, Solidexplorer, Power-Amp....) can't see any files. The Folder always keeps empty.
I have tried several mount points: /sdcard/cifs, storage/emulated/legacy/cifs, /data/media/cifs. Always the mount is visible in Terminal but not in all apps.
I have tried many mount options like: noperm, rw, file_mode, dir_mod, gid.....
cien12 said:
With new 4.3.1 Rom Versions I have troubles with CIFS Mount.
I can mount my NAS without problems with Terminal command, and I can see all mounted Files and Folders in Terminal.
But any App (like ES Fileexplorer, Solidexplorer, Power-Amp....) can't see any files. The Folder always keeps empty.
I have tried several mount points: /sdcard/cifs, storage/emulated/legacy/cifs, /data/media/cifs. Always the mount is visible in Terminal but not in all apps.
I have tried many mount options like: noperm, rw, file_mode, dir_mod, gid.....
Click to expand...
Click to collapse
Hi there, could you post the command line you use to mount your NAS drive ? I keep getting "Invalid argument", this is what I've tried
Code:
mount -t cifs //192.168.1.3/music /mnt/music
pkfox said:
Hi there, could you post the command line you use to mount your NAS drive ? I keep getting "Invalid argument", this is what I've tried
Code:
mount -t cifs //192.168.1.3/music /mnt/music
Click to expand...
Click to collapse
You have to get su access first with "su"
mount -r -o noperm,rw,file_mode=0777,dir_mode=0777,uid=1000,gid=1000,unc=\\\\192.168.0.10\\music,username=***,password=*** -t cifs none /sdcard/cifs
Thanks that worked, do you know of a way to mount automatically at boot time on Android ? I notice there is no /etc/fstab
Thanks again.
Hi all, if your goal is simply to play music and video from your NAS to your android device, you can use Kodi (xbmc) that can access cifs path directly!
I'm currently running an OMNI build for everest, which is working delightfully well. The only thing I can't seem to achieve is to mount a CIFS directory. Actually, it can be mounted, but its contents are only visible to root.
While doing some research I found this thread. For what the description says, I assume this fix has been applied in CM, since I was able to mount CIFS (outside of /storage) before switching from CM to OMNI.
Would these patches be applicable for OMNI? If so, I would try to ask the everest ROM creator to apply them, or even try myself. But I'm afraid I may be lacking the knowledge to judge whether it'd just be a waste of time.
Thanks in advance for any tips on this matter.
Any update on the topic? I've tried Omni on my Nexus 10 and it runs perfectly well but this is the last thing that stops me from using the ROM. After mounting the data from my CIFS or NFS share the data is only available from the app performing the mount. The patches in the link from the previous post seems to work around this issue, is there any chance it could be applied to OmniROM?
Try to mount your folders manually (or by GScript) with Superusers --mount-master switch to make the mounts available to all processes. Something like this.
The su binary now also has a "--mount-master" option that connects you to a su session in the main mount namespace. Mount commands in this session should affect all processes. This is still a bit experimental, and getting it working requires a reboot after upgrading the binaries from a pre-1.93 version. This feature has been asked for a lot by devs, and it escapes the need to hijack system services to affect system-wide mounts, which is becoming more complicated with every Android release. A new version of StickMount will be released in a few days as well, taking advantage of this feature, and thus avoiding a number of issues some are seeing.
https://plus.google.com/+Chainfire/posts/hLKytCwUm6k
Click to expand...
Click to collapse
Alternatively, there is still the possibility to hijack a system service (like SSH one) to point to a script instead that will bring up your mounts. I'm personally using this so i haven't checked the SU method yet.
Good Luck!
DualJoe said:
Try to mount your folders manually (or by GScript) with Superusers --mount-master switch to make the mounts available to all processes. Something like this.
Alternatively, there is still the possibility to hijack a system service (like SSH one) to point to a script instead that will bring up your mounts. I'm personally using this so i haven't checked the SU method yet.
Good Luck!
Click to expand...
Click to collapse
Thanks, --mount-master works like a charm!
Hi all
As the title says, i want to mount a networkpath to my nexus 10 for using "normal" musicplayer like Mort player to play the music stored in the network.
I searched a little around but only found solutions for JB. (Cifs and stuff)
I already tried myself to mount it with Mount manager from the playstore but always get a "failed to mount"
I am using an usb-stick on my Router (Asus RT-N56U). I have access to it with my fileexplorer.
Used ROM and kernel are shown in my signature.
Hopefully someone can give me a hint.
Greetings
Cua.
A little brainstorming:
An user in our german forum found out, that for the moment mounting seems only to work with thunderkat-kernel. But the folder is empty when trying to access. Maybe a problem with the correct rights.
Still in hope someone can help solving this problem.