I installed my bought and paid for DroidSSHPro which works flawlessly on my OG DROID onto my new rooted Nexus Galaxy (stock ICS)...
The app installed and starts when I'm on wifi. My computer can ping the IP that the phone has, but when attempting to ssh to the phone, I get the following:
Bryans-MacBook-Pro:~ bbrake9764$ ssh -vvv [email protected]
OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.1.46 [192.168.1.46] port 22.
*pauses for about 45 seconds*
debug1: connect to address 192.168.1.46 port 22: Operation timed out
ssh: connect to host 192.168.1.46 port 22: Operation timed out
I tried installing DroidWall to attempt to make rules that allow traffic, but Droidwall fails to do anything.
Has anyone had this issue? I'm using MAC OS X Lion, and have tried it with OpenBSD -current. OpenSSH 5.6p1 on the OSX and OpenSSH 6.0-beta on the OpenBSD laptop...
I'm having the same problem and found this thread by searching the Gnex forum for "ssh".
Mine also ends with at the same time as yours, 4th line in the debug output, so it's not connecting for some reason.
netstat doesn't show the port open on the phone. iptables seems to be set up to accept any connections, but I don't know for sure if iptables is really in charge on Android.
I also can't seem to ssh out from the phone. It just hangs. It does identify my computer's ssh version so at least there is some connection happening, but it gets hung right after that.
update: I'm sitting at restaurant and can ssh into my home computer over 4g. I dont know why it didn't work at home, I know the router is set up properly. I'll work on it tonight and see if I figure anything out.
I also saw a comment in the market page for quicksshd where someone said it worked on the galaxy nexus, so dont give up hope
Sent from my Galaxy Nexus using Tapatalk
yea, nothing is working... i installed droidwall to try and allow ssh in, but that did not work either... still hoping it work soon
Yeah, I can still ssh from the phone to the computer perfectly over the cell network, but it doesn't work in either direction over wifi. I've checked and rechecked all the router settings and even rebooted the router, but it won't work.
I'm no expert but I can't live without ssh so if I stumble across anything I'll let you know.
I cannot live without ssh too... and here is the kicker... if you PuTTY, it works QuickSSHD... don' t ask me why...
Just installed firebind, and was able to test and it says that port22 is open inbound and outbound... that only means the port is open... if droidssh and quicksshd are busted in any way, that may be the case...
I downloaded Firebind and it says the same. If I turn off Quicksshd and try to connect, it immediately says "connection refused", but when I turn it on, it just hangs, so it is obviously trying harder when Quicksshd is enabled. I'm going to try a different kernel if I find one. It looks like the kernels are only for 4.03 so I'll have to get a 4.03 rom and there's not much to pick from yet.
I can SSH from my linux box into my GNex. Quick question, doesn't SSHDroid default to listen on port 2222 instead of 22 ? I thought that is the case. If it is, you are trying to connect to the wrong port.
rubik said:
I can SSH from my linux box into my GNex. Quick question, doesn't SSHDroid default to listen on port 2222 instead of 22 ? I thought that is the case. If it is, you are trying to connect to the wrong port.
Click to expand...
Click to collapse
What's your phone setup? I'm trying from Linux too but I borrowed a windows box and tried putty, tried quicksshd and ssh droid, everything. What bugs me is that SSH phone to comp works, but only when not on wifi. The same setup and commands work on my Nexus One on wifi.
Sent from my Galaxy Nexus using Tapatalk
I don't know if it is related but my phone has a bigger problem... the MAC address changes on every reboot.
On the router, I had set the IP address I wanted the phone to connect to 3-4 times over the past few days. I thought I must have kept forgetting to hit "apply" until I looked a little closer tonight and realized I had set it for a different MAC address yesterday. I found it changes to a new MAC address every boot.
I found this thread where someone had that problem and Samsung replaced it. I called Verizon and after some head scratching (in which they didn't rule out a "hidden setting") they decided to swap it. I'll go to the store tomorrow instead of waiting for one to ship.
I'll report is ssh works after the swap.
fubaya said:
What's your phone setup? I'm trying from Linux too but I borrowed a windows box and tried putty, tried quicksshd and ssh droid, everything. What bugs me is that SSH phone to comp works, but only when not on wifi. The same setup and commands work on my Nexus One on wifi.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Stock 4.0.1 , locked & not rooted.
Well, I got a new phone because of the MAC address problem and while it fixed a lot of issues (crashes, lockups, battery drain etc that I had attributed to non ICS compatible apps) I still can't ssh while connected to the router from the command line or ssh to the phone with QuickSSHD, but I can connect to the computer through ConnectBot. That's not really useful to me, but at least some sshing does work.
rubik said:
I can SSH from my linux box into my GNex. Quick question, doesn't SSHDroid default to listen on port 2222 instead of 22 ? I thought that is the case. If it is, you are trying to connect to the wrong port.
Click to expand...
Click to collapse
No, I changed it to port 22. and have tried on port 2222 as well... no change.
The weird thing for me is... When I set up wireless tethering and connect my laptop to the phone, I can then SSH with no issues. Also, if my phone is connected to my wireless network, and I use PuTTY, then it works, but OpenSSH based SSH connections fail miserably. I can ping on Windows, OpenBSD, and Mac OS Lion, but OpenSSH-based SSH connections fail.
Is PuTTY OpenSSH based? I'd imagine not, considering that it connects to the phone.
I keep trying to get logcat output but I have no place to send them to. The developers of both QuickSSHd and SSHDroidPro seem out of contact. Don't know if it's because of the holidays...
I got a new router, a cheap DLink, and ssh works perfectly now. I can't understand why it didn't work with my old one, but everything was set up right and worked remotely, just not when connected to the router.
Howdy guys,
I've had the same issues with my Nexus as well, cannot ssh/sftp to the phone when on my home wifi or 3G. using QuickSSHd to open a port and I can ping the phone from my command line but apart from that I get nothing.
I think something has been blocked to prevent access to the phone.
I'm running a Peter Alfonso 4.0.3 ROM
Frustrating when I used to be able to ssh to my jailbroken iphone from practically anywhere with anything!
well..
After seeing so many people having issues with something so trivial to me (i use ssh everyday much like yourselves), i decided to give it a go (i use good old fashioned usb cable and adb when i'm at home to get a prompt, i normally ssh from the phone not to it).
installed *checks phone notification bar again to see the name of the app* SSHDroid (free on the market), fired up xterm, 'ssh -p 22 [email protected]', it says admin is the password for root, oh really, now that's great! typed it, even missed first login, typed again, logged in, works. i assume the rest also works.
Code:
valhalla% ssh -p 22 [email protected]
SSHDroid
Use 'root' on rooted devices otherwise any username works
Default password is 'admin'[email protected]'s password:
Permission denied, please try again.
[email protected]'s password:
[email protected]:/data/data/berserker.android.apps.sshdroid/home # uname -a
Linux localhost 3.0.8-cyanogenmod-25569-gc0a1566 #1 SMP PREEMPT Sat Jan 28 07:11:24 CET 2012 armv7l GNU/Linux
[email protected]:/data/data/berserker.android.apps.sshdroid/home # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/data/data/berserker.android.apps.sshdroid/home # mount -o rw,remount /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
[email protected]:/data/data/berserker.android.apps.sshdroid/home # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/data/data/berserker.android.apps.sshdroid/home #
root over ssh achieved quite easily.
you can see running kernel is 3.0.8, rom is cm9 self built kang.
edit: oh yeah, host os is linux 3.2.2
edit2: for those who are stating openssh is the problem, well maybe it's just your current installed version of openssh that has some issues. that's what i use, and it sure works.
Code:
valhalla% pacman -Qs openssh
local/openssh 5.9p1-5
Free version of the SSH connectivity tools
I just leaned that to make this work on a Fresh installed ICS 4.0.3 in my case (Pixel ROM) on my Nexus S, I had to jump in to ther terminal emulator once and execute su - and then grant it superuser rights. Then after that SSHDroid now finish initialization, and you can SSH to it....
Related
I just downloaded this after finding it online. it says im missing the runtime. how do i fix this
Make sure you use the most recent version which can be found in the Android dev section on these forums.
DirkGently1 said:
Make sure you use the most recent version which can be found in the Android dev section on these forums.
Click to expand...
Click to collapse
I was on the SuperOneClick Android dev. page but it would not allow me to post as I am a horrible underling and have no privileges.
So if anyone can post it there or answer it here then this is the failure error I get for the device (A coby Kyros MID8024)
I have everything set up and the tablet is running android 2.2 all drivers and other files needed are installed.
Installed terminal emulator confirms NO SU allowed.
Getting mount path...
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /proc/bus/usb type usbfs (rw,relatime,devmode=666)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p3 on /data type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/vold/179:1 on /mnt/nand type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=utf8,shortname=
FAILED
Thanks if anyone can assist.
I used the super 1click method to root. It failed the first time but I rebooted my tablet and ran the super1click a second time and it sucessfully rooty my tablet...now looking for instructon for installing market.
Vernox701 said:
I used the super 1click method to root. It failed the first time but I rebooted my tablet and ran the super1click a second time and it sucessfully rooty my tablet...now looking for instructon for installing market.
Click to expand...
Click to collapse
Why not just flash google apps? That should install the market or you could download the apk for the market directly. See this thread: http://forum.xda-developers.com/showthread.php?t=1231290 .
I have installed CM7 RC1 on top of a brand new SBF179 (did a factory reset after the flashing of that one). While the market initially downloaded all the old apps, it now fails to install or update any apps from the market with a download unsuccessful message. To resolve this, I was looking at s0be's fix which supposedly works:
Here is the s0be's fix
1. adb shell
2. su
3. mkdir /cache/download
4. chown system:cache /cache/download
5. chmod ug+rwx /cache/download
6. chmod a+x /cache/download
I can su but my /cache dir is read only, which presumably is because there is not really a cache partition:
Code:
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p21 on /system type ext3 (ro,noatime,nodiratime,barrier=1,data
=ordered)
/dev/block/userdata on /data type ext3 (rw,nosuid,nodev,noatime,nodiratime,error
s=continue,data=ordered)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
tmpfs on /data/tmp type tmpfs (rw,relatime,size=2048k)
/dev/block/pds on /pds type ext3 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,d data=ordered)
Can anyone shed some light on this? Is there something wrong with the setup here? And why is the cache folder read only?
Market "Download paused" over WiFi
i also had market issue after downgrade cm7 rc1 to froyo rom somebody plz help ......
Market "Download paused" over WiFi
I had the same issue. I found this, and the "fix" worked.
http://www.androidpolice.com/2011/0...on-usb-storage-or-sd-card-problem-on-android/
That does not seem to be my issue - in any case that file does not exist in either locations. In my case I dont even get an error pop up just a silent, quick note in the download bar that the download was unsuccessful.
I still think its weird that my /cache folder is entirely empty and on a read only filesystem to boot?
in my case there is no download folder on /cache
i can able to download file from 2g/2g but download pause if i do it from WiFi ...
did u try flashing google apps again?
it works normally..
how to do it on stock froyo ?
ankit360 said:
how to do it on stock froyo ?
Click to expand...
Click to collapse
well u need to root it and install 2ndInit Recovey and then u can flash anything u like from custom recovery
I just reflashed gapps-2011-03-XX from stable recovery, no change.
nupi said:
I just reflashed gapps-2011-03-XX from stable recovery, no change.
Click to expand...
Click to collapse
i even try gapps-gb-20110613-signed.zip not working
I think I may just go back to RC0 tomorrow, that seemed to be more stable after all
So wiped data and cache on RC1V2, still same issue. Going back to RC0 now
Ok so I did reinstall 177 Nordic, flashed CM7.1RC0 and it STILL does not work.
However, I am still thinking there is something wrong with my partioning of the Defy as custom recovery gave me the following errors:
Can't mount /dev/block/memblk1p24
Can't mount /cache
Can't mount cache:recovery/log
Similarly, stock recovery upon starting also gives me:
Can't mount CACHE:recovery/command
Can't mount CACHE:recovery/caller
Can't mount CACHE:recovery/log
Last vain hope of going back to 177-Nordic and not installing CM7 for now, let's see what happens there.
where apk get save ? /cache/download or /cache ?
when i create download folder in cache it get deleted automatically and downloadfile.apk is get created is this normal plz help me ....
On vanilla 177-NORDIC it works. Confuses the hell out of me.
But also, I get a much different filesystem hierarchy - now I actually get /cache, android secure etc!
$mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk1p21 /system ext3 ro,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/userdata /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/cache /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
tmpfs /tmp tmpfs rw,relatime,size=2048k 0 0
/dev/block/pds /pds ext3 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.trueaxis.jetcarstuntslite-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
Click to expand...
Click to collapse
I still think there is something wrong with the CM7 mount points I get!
I had the problem at rc0. Also got the mounting error. What worked for me was to unmount the cache and than mount again via recovery.
Sent from my MB525 using XDA App
How do I unmount/mount stuff in recovery? Also, did that fix market issues?
For me it fixed the problem. I had also this problem on RC0 and got the error of cant mount cache.
You can unmount and mount it in custom recovery. It do not exactly know where it is in recovery. Thought it was at the advanced menu.
Sent from my MB525 using XDA App
This explains why this happens and how to fix it:
http://forum.cyanogenmod.com/topic/19100-cm7-rc3-market-fails-to-download-big-apps/
Give me thanks for this if it helps, it took me hours to find this fix! thanks
Hello. I need help with backing up my /efs folder. I tried different methods and none seemed to work.
Phone: GT-S5660 Gio
Network Lock [OFF]
Network Subset Lock [OFF]
SP Lock [OFF]
CP Lock [OFF]
Android: 2.3.3
PDA : S5660XXKPO
PHONE : S5660XXKPA
CSC : S5660OXFKP5
Lurking the forums I tried different methods with no luck:
C:\sdk>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# tar zcvf /sdcard/efs-backup.tar.gz /efs
tar zcvf /sdcard/efs-backup.tar.gz /efs
tar: not found
# exit
exit
$ exit
exit
=======================
C:\sdk>adb shell
$ su
su
# busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
tar: /efs: No such file or directory
tar: error exit delayed from previous errors
# cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
/dev/block/stl3: Invalid argument
# exit
exit
$ exit
exit
This method creates efs_dev-block-stl3.img (0 bytes) and efs-backup.tar.gz (29 bytes)
=======================
EFS Pro
Checking Device Connection... Device Connected!
Restarting ADB Server... Okay!
Checking ROOT Access... Device Has ROOT Permissions!
Backing Up Device's '/efs' Folder, Please Wait...
Creating EFS Backup TAR Archive... EFS Backup Failed!
Operation Finished!
With the ISO option the program freezes.
=======================
C:\sdk>adb shell
$ su
su
# dd if=/dev/block/stl4 of=/sdcard/efs.rfs
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
/dev/block/stl4: cannot open for read: Invalid argument
# exit
exit
$ exit
exit
=======================
I also tried this:
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=u
tf8 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.sportstracklive.stopwatch-1 vfat ro,dirsync,nosuid
,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859
-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
=======================
With Root Explorer I am unable to find the /efs
Sorry for the long post, but what am I missing?
Best regards, V a L y O.
STOP!
The first rule with the Gio is not to mess with the EFS partition if you don't know what you're doing.
It is located in stl5, but you very much risk corrupting it solely by mounting and reading it.
Corruption in this case means a bricked phone or a blank IMEI, which means no phone service.
Either backup bml5, or work in recovery mode.
Thank you for the replay.
I know that messing with the stl5 can brick the phone. Well, that already happened once when I used Odin to flash a wrong 2.3.5 version. Lucky for me, It was repaired under warranty.
That's why I want to make a backup to the system files.
bml5 is backed up. Is it enough to fix the phone in case I brick it again?
Best regards, V a L y O.
now my phone have blank imei
but, i still can use it for sms, call & internet
is anyone here know how to restore it?
lucky, in indonesian imei is not requirement for gettiong mobile service service
phiexz said:
now my phone have blank imei
but, i still can use it for sms, call & internet
is anyone here know how to restore it?
lucky, in indonesian imei is not requirement for gettiong mobile service service
Click to expand...
Click to collapse
Same here! I live in the Netherlands and also have a blank IMEI(IMEI is 000000000000) but still evrything works except swype install because it requires an IMEI number. Somebody know how to fix it? maybe to use somebody elses IMEI? with /efs restore or is there an way to import my own IMEI in somebody elses /efs backup?
i've tried help to root and s-off my DHD friend..but found very strange trouble on his device..never found this trouble before..
the trouble is when i've tried to downgrade and s-off used AAHK 2 by phiber 2000..at the process of downgrade first..i confirm "y"..then when process step on setup tacoroot and automatic make phone rebooted to stock recovery..the phone stop and stuck at HTC logo..and can't setup tacoroot on stock recovery..
i've tried manual process temp root with tacoroot too but the result still the same as before..when phone reboot just suck at HTC logo..and can't go to stock recovery..
then i tried to check boot to bootloader with volume down + power then choice recovery..i've success go to stock recovery..but when i've used adb command like "adb reboot recovery"..the phone always stuck at HTC logo...
cause of that..i can't used AAHK 2 or manual process to downgrade and s-off the phone..this is really strange trouble for me..
i've already tried too to unlock through HTCdev unlock but can't get token from the phone it say.."command error" and i know i must update the hboot first to version 2.00.0029
but i've already tried to update ruu too from the site it self for update hboot to 2.00.0029.. but result error190..
what i've already done :
1. tried AAHK2 to downgrade and s-off..but stop process on tacoroot setup
2. tried manual downgrade process with installing tacooroot first..result still the same can't setup tacoroot to in stock recovery
3. tried unlock with HTCdev unlock..result can't update hboot already tried with a various ways
4. tried factory reset first but result still the same..just stuck at htc logo
5. tried re flash RUU with the same version of firmware..but the result still the same
6. tried flashing hboot 2.00.0029 of the various ways..some with error result..some with success completed flashing but after reboot the phone..the hboot version still the same as before..nothing change
Update :
7. tried flashing different RUU with goldcard..result is success and completed flashing it..but the strange is..after reboot..nothing any change..the bootloader and the rom still the same like before..
8. tried check and looking partition on eMMC..then compared to my DHD (the normal mine DHD) and turns it like this :
my normal DHD :
adb shell mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.2/by-num/p25 /system ext4 ro,relatime,barrier=1,dat
a=ordered 0 0
/dev/block/platform/msm_sdcc.2/by-num/p26 /data ext4 rw,nosuid,nodev,relatime,ba
rrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/msm_sdcc.2/by-num/p27 /cache ext4 rw,nosuid,nodev,relatime,b
arrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/msm_sdcc.2/by-num/p28 /devlog ext4 rw,nosuid,nodev,relatime,
barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:65 /storage/primary/legacy vfat rw,dirsync,nosuid,nodev,noex
ec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp
437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/primary/legacy/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
Click to expand...
Click to collapse
my friend DHD that's had troubled :
adb shell mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext3 ro,relatime,errors=continue,barrier=0,data=or
dered 0 0
/dev/block/mmcblk0p28 /system/lib ext3 ro,relatime,errors=continue,barrier=0,dat
a=ordered 0 0
/dev/block/mmcblk0p26 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrie
r=0,data=ordered 0 0
/dev/block/mmcblk0p27 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barri
er=0,data=ordered 0 0
/dev/block/mmcblk0p30 /devlog ext3 rw,nosuid,nodev,relatime,errors=continue,barr
ier=0,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /data/secure/data tmpfs rw,relatime,mode=771,uid=1000,gid=1000 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/data/d /data/d debugfs rw,relatime 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow
_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Click to expand...
Click to collapse
is that possible this trouble come from the partition of that in my friend DHD itself..?
note : the phone always troubled reboot normally..always stuck at htc logo..then success reboot normally after a couple of time must pull out the battery first..
and always back to the state like before even when i've already change disabled the Fast boot in Settings..there's always back enable again while back after reboot the rom..
really need someone help me to go out from this trouble..please..
thanks b4..
If u wanna unlock via htcdev you have the wrong hboot you need the one that ends with 29 there a way to flash it ( google it ) if u try the ruu u wil get a error, that's way u need to look for a way to flash it via fastboot.
lexuz said:
If u wanna unlock via htcdev you have the wrong hboot you need the one that ends with 29 there a way to flash it ( google it ) if u try the ruu u wil get a error, that's way u need to look for a way to flash it via fastboot.
Click to expand...
Click to collapse
i know..and i've already done it..but when i've success completed flashing a hboot 2.00.0029 from bootloader then reboot the phone..the hboot still the same as before..nothing change in there..when i've tried flashing through running utility from the RUU update hboot 2.00.0029 from HTC itself..the result is "error 190 : blah blah i forget".."you must update your phone to 3.13.707.3 first via OTA..blah blah blah..i forget too" this is so silly..because the DHD is already had RUU 3.13.707.4 with hboot 2.00.0027.. and i've already flashing from fastboot reboot oem-78 too..but the result is stop.. fail read <too many link>..blah blah..
then like what i say above..i've already tried too to replaced my RUU with the same version as already had it in the phone and even different version (of course higher not lower version) and different carrier of the RUU too with goldcard and the flashing process is completed all..but the result after reboot the phone is..the hboot and the room still the same as before..nothing change in there..
another solution maybe..??
anyway thanks for trying to help me..
JJeamy said:
i know..and i've already done it..but when i've success completed flashing a hboot 2.00.0029 from bootloader then reboot the phone..the hboot still the same as before..nothing change in there..when i've tried flashing through running utility from the RUU update hboot 2.00.0029 from HTC itself..the result is "error 190 : blah blah i forget".."you must update your phone to 3.13.707.3 first via OTA..blah blah blah..i forget too" this is so silly..because the DHD is already had RUU 3.13.707.4 with hboot 2.00.0027.. and i've already flashing from fastboot reboot oem-78 too..but the result is stop.. fail read <too many link>..blah blah..
then like what i say above..i've already tried too to replaced my RUU with the same version as already had it in the phone and even different version (of course higher not lower version) and different carrier of the RUU too with goldcard and the flashing process is completed all..but the result after reboot the phone is..the hboot and the room still the same as before..nothing change in there..
another solution maybe..??
anyway thanks for trying to help me..
Click to expand...
Click to collapse
I'm also new at this but I know that a week ago I downloaded a mini-adb package with the hboot inside (the ....29) connected the phone via USB and the flash process was shrines after that.
lexuz said:
I'm also new at this but I know that a week ago I downloaded a mini-adb package with the hboot inside (the ....29) connected the phone via USB and the flash process was shrines after that.
Click to expand...
Click to collapse
yap i know..that's the package like behtash had.. that i've already tried too.. but the result is like i said before..just stop fail read <too many links>>
even i tried manual without behtash script too..with "adb reboot oem-78" then "fastboot flash zip rom.zip"..but result still the same..
i think this is the problem come from the partition table that i show in the first post..because of info from my friend itself..this DHD is ever brought to HTC service center for repair dead pixel of lcd before..after that..the lcd is fix..but..some of other hw doesn't seems perfect like before..
ANYONE CAN HELP ME...HOW I CAN REPARTITION THIS DHD WITH DEFAULT LAYOUT WITHOUT USING RIFF BOX JTAG TOOLS..??
THX B4..
I don't know what happened, my battery died, I plugged it in, turned the phone back on, and boom, my phone is throwing errors out left and right, and ES File Explorer is saying '/sdcard/' is not found. I've tried going to storage/emulated/0 & legacy, but I get the same not found message.
Storage in System Settings shows that the storage is still being used, and the file browser in TWRP shows all the files are still there. It just seems like the mount points or bindings got all screwy.
My phone is on the BOF5 firmware, it's stock rooted. I've had no problems restarting my phone, usually have to atleast twice a week. Nothing funky installed, atleast nothing that would mess with the SD card. No SW was uninstalled, just frozen, and it wasn't much [Voicemail, Internet (Browser), Hangouts]
I'm really just hoping that someone, somewhere knows a way to help me fix this so I don't have to restore!
krakerx said:
I don't know what happened, my battery died, I plugged it in, turned the phone back on, and boom, my phone is throwing errors out left and right, and ES File Explorer is saying '/sdcard/' is not found. I've tried going to storage/emulated/0 & legacy, but I get the same not found message.
Storage in System Settings shows that the storage is still being used, and the file browser in TWRP shows all the files are still there. It just seems like the mount points or bindings got all screwy.
My phone is on the BOF5 firmware, it's stock rooted. I've had no problems restarting my phone, usually have to atleast twice a week. Nothing funky installed, atleast nothing that would mess with the SD card. No SW was uninstalled, just frozen, and it wasn't much [Voicemail, Internet (Browser), Hangouts]
I'm really just hoping that someone, somewhere knows a way to help me fix this so I don't have to restore!
Click to expand...
Click to collapse
Youre taking all the fun out of it. Backing up and restoring from scratch is half the fun with android phones. If youre gonna root to have fun, be prepared to do the dirty work as well. JMHO
xxSTARBUCKSxx said:
Youre taking all the fun out of it. Backing up and restoring from scratch is half the fun with android phones. If youre gonna root to have fun, be prepared to do the dirty work as well. JMHO
Click to expand...
Click to collapse
Well, I'm looking to do the dirty work, otherwise I would have just restored the phone from my backup weeks ago. But I don't want to do that, because, honestly, there has got to be a way to see this data. With that said, here is the output from running 'mount' in TWRP and Terminal Emulator:
C:\MiniADB\adb shell
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1418352k,nr_inodes=154938,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=1418352k,nr_inodes=154938)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p27 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p27 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p25 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
===========================================================================================================
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1414720k,nr_inodes=153121,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=755,gid=1000 0 0
/dev/block/bootdevice/by-name/modem /firmware-modem vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/apnhlos /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,norecovery 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/carrier /carrier ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persdata /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=1414720k,nr_inodes=153121,mode=050,gid=1028 0 0
tmpfs /storage/emulated/legacy tmpfs rw,seclabel,nosuid,nodev,relatime,size=1414720k,nr_inodes=153121,mode=050,gid=1028 0 0
[email protected]:/ #
Hopefully someone with BOF5 rooted stock can take a look at their mount points and see if they lineup with what I'm getting
krakerx said:
Well, I'm looking to do the dirty work, otherwise I would have just restored the phone from my backup weeks ago. But I don't want to do that, because, honestly, there has got to be a way to see this data. With that said, here is the output from running 'mount' in TWRP and Terminal Emulator:
Click to expand...
Click to collapse
Thanks for posting this.
Hopefully someone who is still on OF5 can match and compare/contrast whats there or not there. Maybe unrooting and OG5 is the way to go or simply trying it in your laptop(if it has a SD cardslot reader and see if it functions properly there) Might be time to get a new card
SD card is fine, internal memory is fine... Found the issue was a corrupted sdcard pointer, once fixed, phone runs like it should