Database Users

Ubuntu can't see my N1

Hi,
I'm trying to unlock my N1's bootloader in order to root it. I downloaded fastboot and enabled USB debugging in the phone doing this:
Settings → applications → development → USB debugging → check.
I power off the phone and reboot while pressing the trackball, then do this on my Ubuntu terminal, once I'm in the directory that contains fastboot-linux, fastboot-mac and fastboot-windows.exe:
[email protected]:~/Android/fastboot$ ./fastboot-linux devices
[email protected]:~/Android/fastboot$
As you see, the phone does not appear even though it's properly connected. Am I leaving something out?
Thanks in advance.

can you copy files to the sdcard when the phone is running?
some other guy here had a broken usb-cable.
do you see anything in dmesg when powering up the phone and entering bootloader?
should look like this:
Code:
Jan 27 10:19:25 distance kernel: [ 481.870100] usb 2-4: new high speed USB device using ehci_hcd and address 5
Jan 27 10:19:25 distance kernel: [ 482.022787] usb 2-4: configuration #1 chosen from 1 choice

xkonni said:
can you copy files to the sdcard when the phone is running?
some other guy here had a broken usb-cable.
Click to expand...
Click to collapse
Yep, it's recognised as a mass storage device and I can copy stuff alright.
xkonni said:
do you see anything in dmesg when powering up the phone and entering bootloader?
should look like this:
Code:
Jan 27 10:19:25 distance kernel: [ 481.870100] usb 2-4: new high speed USB device using ehci_hcd and address 5
Jan 27 10:19:25 distance kernel: [ 482.022787] usb 2-4: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
This is what I get:
Code:
Jan 27 10:25:28 david-laptop kernel: [ 159.700293] usb 2-3: new high speed USB device using ehci_hcd and address 4
Jan 27 10:25:28 david-laptop kernel: [ 159.845496] usb 2-3: configuration #1 chosen from 1 choice
Jan 27 10:25:28 david-laptop kernel: [ 159.848975] scsi6 : SCSI emulation for USB Mass Storage devices
Jan 27 10:25:33 david-laptop kernel: [ 164.857208] scsi 6:0:0:0: Direct-Access Google, Inc.Nexus One PQ: 0 ANSI: 2
Jan 27 10:25:33 david-laptop kernel: [ 164.857836] sd 6:0:0:0: Attached scsi generic sg2 type 0
Jan 27 10:25:33 david-laptop kernel: [ 164.868692] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Everything seems normal, does it?

is that dmesg from booting the phone to bootloader?
it should not be identified as mass storage there.

xkonni said:
is that dmesg from booting the phone to bootloader?
it should not be identified as mass storage there.
Click to expand...
Click to collapse
My fault, that was a normal boot.
This is what booting to bootloader gives:
Code:
Jan 27 10:44:46 david-laptop kernel: [ 1317.564263] usb 2-3: new high speed USB device using ehci_hcd and address 5
Jan 27 10:44:46 david-laptop kernel: [ 1317.703962] usb 2-3: configuration #1 chosen from 1 choice
Yet...
Code:
[email protected]:~/Android/fastboot$ ./fastboot-linux devices
[email protected]:~/Android/fastboot$

strange. what version of ubuntu is it?
could be a permission problem.
try 'sudo fastboot devices' to check.
however this is not the way you're supposed to use fastboot. there was another thread describing how to create an udev rule so your user can access usb properly.

Having the same issue. I don't want to boot a Windows PC just for this. It would be a shame

1. Create a file called "52-android.rules" in /etc/udev/rules.d directory.
Contents for file follows:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Reboot.
3. PROFIT!

http://forum.xda-developers.com/showthread.php?t=613217
the solution is in there
you have to create a file with rules for the specific device, so your regular user is able to use it. but it seems there are different vendorIDs.
so we check which one you have.
remove the phone 'lsusb', plug in the phone 'lsusb'.
check for a new line
for me the entry looks like this
Bus 001 Device 005: ID 18d1:xxxx
so like described in the linked thread,
edit /etc/udev/rules.d/51-android.rules and add this line (with your ID!)
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
after that, plug out the phone again, sudo service udev restart, plug in, should be good to go
edit: damn... going afk while posting is not a good idea ;p

here also is a thread with what you may need.
in addition to the rules file you have to create, there is a ~/.bashrc export path you have to add

Thanks for all your help guys,
packetlss said:
1. Create a file called "52-android.rules" in /etc/udev/rules.d directory.
Contents for file follows:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Reboot.
3. PROFIT!
Click to expand...
Click to collapse
This definitely solved the issue. It was easy!

I second that you need to either manually create the right devices in /dev or use the udev rules posted above. Works on Fedora 12.
No entries in ~/.bashrc or similar are necessary, you just have to call adb with the full pathname ~/somedirectory/android-sdk-linux_86/tools/adb

`sudo ./fastboot-linux devices`
would have worked (or just su to root)
fastboot requires root, just like the adb server needs to be started as root via `sudo ./adb start-server` then you can run adb as a normal user.

flipp said:
`sudo ./fastboot-linux devices`
would have worked (or just su to root)
fastboot requires root, just like the adb server needs to be started as root via `sudo ./adb start-server` then you can run adb as a normal user.
Click to expand...
Click to collapse
works, not recommended though.
neither 'adb start-server', nor 'fastboot' require root. both just require write permissions on the usb-device (root has these rights, your local user will get them with the right udev-rule)
don't just run everything as root, thats not what linux is about

flipp said:
`sudo ./fastboot-linux devices`
would have worked (or just su to root)
fastboot requires root, just like the adb server needs to be started as root via `sudo ./adb start-server` then you can run adb as a normal user.
Click to expand...
Click to collapse
I see xkonni beat me to it but neither fastboot or adb require root. You should never run things as root without good reason. Really even a mode of 666 is probably not the best setting, but it is a reasonable compromise. If you are on a multi user box or just a little paranoid (like me) you should create a group for this and then set it as the owner and mode of 660
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", GROUP="android", MODE="0660"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", GROUP="android", MODE="0660"
In general though 666 is fine and less error prone on set up.

I am at a total loss. I have tried everything that I have read to try and get fastboot to see my phone and nothing is working.
I'm running Ubuntu 10.10 x64 by the way.
ADB will see and connect to my phone just fine(wired or wireless). I have edited the bash file, I have the rules file created. I know fastboot is installed cause if I just type "fastboot", I get a list of commands, but if I try "./fastboot" or "sudo fastboot", I get a command not found error.
I had this working under Windows 7 just fine, but I'm trying to get switched over to linux, and this is the current hurdle I'm trying to overcome.

Well, obviously, fastboot has to be on your PATH. Did you download it and put it on your PATH via .bash_rc? Type `which fastboot` in your terminal and if you don't get anything that means that your machine has no idea where it is. Alternatively, `cd` into the directory where you put fastboot and run the following command `./fastboot devices`. If you get an error, then try `sudo ./fastboot devices`. It's a PATH issue, not a fastboot issue.
On another note, thanks to everyone who helped in this thread, it worked for me Weird though, since adb and fastboot worked without having to modify any rules in Ubuntu 9.X.

i never was able to get ADB to work in ubuntu 10.04. so i did all the compiling in ubuntu, and just sent the zImages for my kernel over to my windows machine, adb fastboot, and done. not sure what the problem was.

[Q] A500 Boot loop. How I got there, and resolved it [RESOLVED]

Tools:
-Android SDK
-USB Drivers from Acer
-Afterota v1_09
-ICS Root 7.1.1
-APX_v0.4A-flashTool-500Manager1.0.2
-V8-UNL-ICS-HC-bootloader-MULTI-cwm
-acer_update_decrypt
1.) Starting with A500 running ICS with USB Debug enabled (Settings, Developer Options, USB debugging)
2.) Get SBK using Afterota v1_09. Export ids to AcerIDs.txt
3.) Root the device using ICS Root 7.1.1.
-ensure "Don't reboot is selected"
-after the root process is completed delete the /system/recover...p file
--Open CMD
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\X>cd "c:\Program Files (x86)\Android\android-sdk"
c:\Program Files (x86)\Android\android-sdk>cd platform-tools
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb.exe shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ mount
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
debugfs /sys/kernel/debug debugfs 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/mmcblk0p3 /system ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /system/vendor ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /mnt/external_sd 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
[email protected]:/ $ su -
su -
[email protected]:/ # cd /system
cd /system
[email protected]:/system # ls -l
ls -l
drwxr-xr-x root root 2012-10-29 08:53 app
drwxr-xr-x root shell 2012-10-29 08:53 bin
-rw-r--r-- root root 1841 2008-08-01 20:00 build.prop
drwxr-xr-x root root 2012-10-29 08:53 etc
drwxr-xr-x root root 2012-10-29 02:29 fonts
drwxr-xr-x root root 2012-10-29 02:29 framework
drwxr-xr-x root root 2012-10-29 02:29 lib
drwxr-xr-x root root 1970-01-01 07:30 lost+found
drwxr-xr-x root root 2012-10-29 02:29 media
-rw-r--r-- root root 595077 2008-08-01 20:00 recovery-from-boot.ICSRootBackup.p
drwxr-xr-x root root 2012-10-29 02:29 tts
drwxr-xr-x root root 2012-10-29 02:29 usr
drwxr-xr-x root root 1970-01-01 07:30 vendor
drwxr-xr-x root shell 2012-10-29 08:53 xbin
[email protected]:/system # rm recovery-from-boot.ICSRootBackup.p
rm recovery-from-boot.ICSRootBackup.p
[email protected]:/system # reboot
Click to expand...
Click to collapse
4.) Open A500Manager from APX_v0.4A-flashTool-500Manager1.0.2
5.) Open a CMD in the expanded V8-UNL-ICS-HC-bootloader-MULTI-cwm folder
- Run a500-hc.bat
- Enter the SBK (step 2) when prompted
- On A500Manager click on "Enter APX mode"
- When the status bar in A500Manager and ICS Root 7.1.1 reads "A500 Detected in APX Mode" press enter in the a500-hc.bat CMD window
Formatting partition 4 please wait.. /
CTRL+C
-v8.bat
c:\Users\X\Downloads\Acer\V8-UNL-ICS-HC-bootloader-MULTI-cwm>v8.bat
****************************************************************
* This will boot your A500/501/G100W into bootloader mode, *
* flash the V8 bootloader *
* and flash recovery of your choise. *
****************************************************************
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXx
**********************************************************
* Make your choise: *
*(1) ICS bootloader V8 with TWRP-2.1.3-ICS cwm(touch cwm)*
*(2) ICS bootloader V8 with PubRecovery-v0.2 (BareBones) *
*(3) ICS bootloader V8 with Thor-1.7cwm (touch cwm) *
*(4) ICS bootloader V8 with Thor-1.7.3 NEW cwm(touch cwm)*
* with its compatible recoveries. *
**********************************************************
(1 2 3 4):1
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0380700143df9217
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
*****************************************************************
* Press any key when your A500/501/G100W is in bootloader mode *
*****************************************************************
Press any key to continue . . .
Flashing bootloader: bootloader_v8.bin ...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. done!
Nvflash started
[resume mode]
sending file: bootloader_v8.bin
| 1191932/1191932 bytes sent
bootloader_v8.bin sent successfully
Flashing recovery: recovery_twrp_2.1.3-ICS.img
Nvflash started
[resume mode]
Formatting partition 6 please wait.. done!
Nvflash started
[resume mode]
sending file: recovery_twrp_2.1.3-ICS.img
/ 5222400/5222400 bytes sent
recovery_twrp_2.1.3-ICS.img sent successfully
Exiting APX mode...
Nvflash started
[resume mode]
**********************************************************
* Press any key when you are done reading nvflash output *
**********************************************************
Press any key to continue . . .
*****************************************************************
* Hold the power button on your A500/501/G100W to power off, *
* then turn it back on normally *
*****************************************************************
Press any key to continue . . .
Click to expand...
Click to collapse
At this point it will read "PASS" in ASCII art on the device
-reboot the device
6.) Download Honeycomb rom from either
http://forum.xda-developers.com/showthread.php?t=1816560
http://forum.xda-developers.com/showthread.php?t=1113878
I ended up with : Acer_A500_0.000.00_1.013.01_EMEA_GEN1_1300336887417_befd43a1.zip
and later tried : Acer_A501_0.000.00_4.017.03_EMEA_CUS7_1313721527367_dc802d69.zip
7.) Decrypt the ROM using acer_update_decrypt
8.) Expand the decrypted zip file
9.) Transfer the content of the decrypted zip file onto the root folder of an SDCARD
10.) Switch the tablet off
11.) Switch the tablet on holding the Volume Up key
12.) Once in TWRP v2.1.3 click WIPE
- WIPE Cache
- WIPE Dalvic Cache
13.) in TWRP click on Mount
- Ensure the SDCard is mounted and "Using external SDCard" is selected
14.) in TWRP click on Install
- Select update.zip
- Swipe to confirm flash. This will take a couple of minutes
15.) Reboot
16.) At this stage I would expect to have honeycomb installed and the option to update to ICS via OTA available to me. However all I get is the Android title flashing from time to time. Also rebooting into the TWRP was no longer working either. All I ended up getting trying to boot into TWRP was a 2D Andoid drawing with a yellow exclamation mark.
17.) Download ICS rom from above link to try and see if flashing with ICS might work
I used : Acer_A500_7.014.14_041.203.01_COM_GEN1_1333444737199_8ec8b991.zip
Any attempt of booting a recovery rom fail with the exclamation mark android. The only functionality I can access at this point is the Power-Down menu. Booting the primary kernel results in boot loop and recovery in exclamation android.

Progress
I managed to boot the tablet into fastboot mode and to delete the user data. Once that was done I managed to boot into 3.2. However since I picked the EMEA version it was all in German. For some reason I picked an image for an A501. So now my tablet runs 3.2 in German and thinks it is a A501. Also there are no OTA updates available, presumably because the device (A500) does not match the ROM (A501).
I tried to update to various other images using the recovery option, but all just end up on the yellow exclamation.
Any suggestions on how to recover from this. I am guess I need to root my device and re-install TWRP. Any pointers on rooting 3.2 ?

lostinspace2011 said:
I managed to boot the tablet into fastboot mode and to delete the user data. Once that was done I managed to boot into 3.2. However since I picked the EMEA version it was all in German. For some reason I picked an image for an A501. So now my tablet runs 3.2 in German and thinks it is a A501. Also there are no OTA updates available, presumably because the device (A500) does not match the ROM (A501).
I tried to update to various other images using the recovery option, but all just end up on the yellow exclamation.
Any suggestions on how to recover from this. I am guess I need to root my device and re-install TWRP. Any pointers on rooting 3.2 ?
Click to expand...
Click to collapse
Sent from my A500 using Tapatalk 2
Thanks for all the info, makes it a lot easier to help!!!
You were doing fine until Step 6 - flashing an HC 3.2 Rom
The patched bl is for ics roms.!
3.2 is locked down, theres never been a way to root it without installing a pre-rooted stock 3.2 like timmydeans v4 or ezterry's one
When u flashed it, it also flashed the stock recovery and wiped yr twrp.
I'd suggest u start over again with the patched boot loader flash, get a recovery back on there and flash any of the ics roms OR
You could try running the update.zip from jdgM3NT4L's thread if u want to try an OTA to ICS - only thing there is u need to do
a full wipe otherwise you'll get stuck booting.
tdv4 will give u a rooted 3.2 with cwm - this should OTA you as well - this method will wipe your tab clean and you'll need yr cpuid.
Once you have yr rom flashed id be tempted to full wipe it again and beforehand, just to get rid of anything that shouldn't be there
Good luck with it and let us know how u get on
rgds dibb

And so my journey continues. I am now back on an English version of 3.2 after using V8-UNL-ICS-HC-bootloader-MULTI-cwm to update the bootloader and restore the recovery function. So small progress.
However now I was hoping to be able to OTA to stock ICS, yet it tells me that I am already on the latest version. Currently I am on:
Model : A500 (rather than 501)
Android Version : 3.2
Kernel Version : 2.6.32.3+
Build Number : Acer_A500_7.006.01_COM_GEN2
Any suggestion on how I can get OTA to work ?

I followed the steps from : http://forum.xda-developers.com/showthread.php?t=1839313 and updated to
Model : A500
Android Version : 3.1
Kernel Version : 2.6.36.3
Build Number : Acer_A500_4.010.38_COM_GEN1
I also installed "Iconia tab update enhancements" but still not getting any OTA updates.
Any thoughts on what is preventing me from getting the OTA updates ?
thanks

lostinspace2011 said:
I followed the steps from : http://forum.xda-developers.com/showthread.php?t=1839313 and updated to
Model : A500
Android Version : 3.1
Kernel Version : 2.6.36.3
Build Number : Acer_A500_4.010.38_COM_GEN1
I also installed "Iconia tab update enhancements" but still not getting any OTA updates.
Any thoughts on what is preventing me from getting the OTA updates ?
thanks
Click to expand...
Click to collapse
I'll reply to this thread m8 rather than the other one....
some reasons for not being able to ota.
the enhancement app is for the ics ota, so won't help from 3.1
if yr tab was GEN1 u won't be able to update using GEN2 and vice versa, this applies to HC only.
Acer don't roll out updates automatically, there appears to be some sort of cycle, that has no sort of rhyme or reason.....go figure!
you must be completely stock and unrooted
you mentioned a bug you were trying to isolate as the reason for returning to stock.
all I can tell you is there was a big difference between the OTA ICS and the pre-rooted
stock ICS roms posted by our much respected dev, civato but of course even those roms
do not compare in the slightest to his custom reFlexxx roms -
also a full wipe and format and rom reflash can work wonders too in keeping u bug-less!
off hand I cannot remember if u need the patched boot loader for his stock roms, I don't think
you do....you can try flashing one of those - as always full instructions are in the OP
as far as OTA'ing - if you've tried a gen1 give a gen2 a go, blackthund3r has a stock rom thread, you may find something suitable in that....whatever u end up doing please keep us posted, its always nice to have some sort of resolution for others reading who may be in a similar situation
rgds dibb

Third time lucky. I installed :
Model : A500
Android Version : 3.2
Kernel Version : 2.6.36.3+
Build Number : Acer_A500_7.006.03_COM_GEN1
And got a 7MB update. Not quite sure where this will take me though.

Now I am on :
Model : A500
Android Version : 3.2.1
Kernel Version : 2.6.36.3+
Build Number : Acer_A500_7.014.03_COM_GEN1
The next available OTA update was
Acer_A500_7.014.15_com_gen1 (7.51MB)
And then the big one
Acer_A500_041.203.01_COM_GEN1 (391MB)

lostinspace2011 said:
Now I am on :
Model : A500
Android Version : 3.2.1
Kernel Version : 2.6.36.3+
Build Number : Acer_A500_7.014.03_COM_GEN1
The next available OTA update was
Acer_A500_7.014.15_com_gen1 (7.51MB)
And then the big one
Acer_A500_041.203.01_COM_GEN1 (391MB)
Click to expand...
Click to collapse
sooooo.....you're all good now??
u may have wifi issues if so, do a complete wipe/factory data reset - probably best to do one anyway....

Thanks, done that. All good now. Hopefully this thread will help others.

[Q] Flashing HD2 without touch screen

Hy.
I have a HTC HD2 with a dead touch screen (I can read, but touch is not reactive). I could reset it to factory settings via buttons. So I have a Windows Welcome screen.
I can also enter HSPL.
Is it possible to flash the device, and install Android without working screen ?
Once I have Android, I can do stuff with the device, and use it as VNC client, and manage remotly via ssh. My problem is to install Android on it. Most tutos say at one step or an other to activate ActiveSync in Windows, what is not possible for me.
I am used to HTC Sensation, and to all classic Android tools (adb, fastboot). I have Windows and Linux hosts.
Classic tutos are not usable for me.
Otherwise, the device will go for sale, for peaces. 10€.
Thanks.

voldown + power --> bootloader,
fhlash hspl
flash radio 2.15.50
flash magldr
use toolkit to apply partition size and cwm
into cwm
flash rom from zip
no touchscreen necessary
the instruction about activesync is a red herring, , it doesn't refer to the app on the PC, and it doesn't require winmo to be running on the phone either, it just means get a usb connection.
however if you have trouble flashing hspl, then manually updating windowsmobiledevicecenter (find it on microsoft website) will help fix driver errors, and later, when you get into magldr and start using 'usb flasher' you may wanna install 'myphoneexplorer' for the android drivers it comes with.

^That's true, but you might have a problem with Aroma installer. I think it may work with the volume keys too, but if it doesn't then you'll have to find a ROM which doesn't use Aroma (most relatively old ROMs don't) and flash that instead.

Nigeldg said:
^That's true, but you might have a problem with Aroma installer. I think it may work with the volume keys too, but if it doesn't then you'll have to find a ROM which doesn't use Aroma (most relatively old ROMs don't) and flash that instead.
Click to expand...
Click to collapse
Aroma does work without touchscreen, buttons can be used to select the default choices, (can't recall if volume buttons can used to change selected option, so may need to edit ROM zip so the defaults are what you want). The issue I'd see is how you go about issuing commands and starting apps; it's possible of course - there are commands to simulate screen presses (monkeyrunner) and command to start apps/processes but those commands can get complicated.
If you get a VNC system set up without touchscreen then could you add your procedure?

I am stuck at almost last step: pushing CWM: I have downloaded Recovery-400 from http://www.filecrop.com/Clockworkmod-Recovery-hd2.html , but I get the RSPL error message. I have Windows XP SP3 with .NET3 SP1, so i am admin, i have EnterBootloader.exe and rapidtool.exe, and I have unticked the USB stuff in ActiveSync ... but i am still stuck at the RSPL error :/
About going further: if I have ADB access from CWM, I will just install Armel by copying from my Sensation (Debian Armel have been installed using LinuxInstaller by Galoula). If i don't have adb, I will have to pre-install it in the zip, and reflash. In short, I push a chrootable env, and find an init script that will run sshd after boot. Once I have ssh, i'm done.

I had to install RAPI.dll, and CEUTIL.dll (found in google), re-install ActiveSync, and use a very specific ROM. HD2toolkit did not work at all for me. I forgot how I installed MAGDLR, but it was PITA to install it. And once installed, I spent 2 days on trying to use it. Putting ROMs on uSD does not allow to install the from SD.
After viewing http://cdn.youtubeavi.com/view-video/0TpYHpfHW-8 (confirmed by reading http://resetguide.com/2012/05/how-to-install-android-on-hd2-nand/ ), I saw that amongst my 1GB of data downloaded in the last days, I did not have the file ANDR_install.exe; I downloaded all possible ROMs until I find one having this magic file: http://forum.xda-developers.com/showthread.php?t=893637 . Only this ROM has andr_install.exe . And when I ran it, it worked on the first time (while of course having HD with MAGLDR on option 5: USB flash).
Now, my HD2 started Android. I still can not use it at all for now, but at least, I have made a step.
adb works, so it will probably be very easy for me. From ADB, I can do almost anything: install APKs(pm install), getprop, remount /system rw, install Debian manually ... the hardest part may be to click on buttons, but I can find a WA for this: create minimal apps on my other Android phone, using Tasker with AppFactory, apps which will be able to send keystrokes, and start them as required. Long way, but should work (if I don't have CPU uncompat issues). Anyway, without touch pad, it's not gonna stay a "phone"; it will mostly be a VNC-viewer for other devices (like my RaspberryPi).
Hell I am lucky: both HTD HD2 and HTC Sensation use the exact same CPU: "ARMv7 Processor rev 2 (v7l)" . Gonna be trivial to have fun around An example to install a VNC-client:
Code:
[email protected] /tmp $ adb -s SH169V80XXXX pull /data/app/android.androidVNC-1.apk
1703 KB/s (245795 bytes in 0.140s)
[email protected] /tmp $
[email protected] /tmp $ adb -s 0123456789ABCDEF install android.androidVNC-1.apk
2015 KB/s (245795 bytes in 0.119s)
pkg: /data/local/tmp/android.androidVNC-1.apk
Success
[email protected] /tmp $
Same for server.
Like in my Sensation (definitly, I am lucky), I have a free folder in the default PATH :
Code:
localhost / # echo $PATH
/sbin:/system/sbin:/system/xbin:/system/bin
localhost / # ls /system/
app dmesg.txt framework lost+found lost+found xbin
bin etc lib lost+found media
build.prop fonts lost+found lost+found usr
localhost / #
so, let's populate it
Code:
localhost / # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 205.9M 0 205.9M 0% /dev
tmpfs 205.9M 0 205.9M 0% /mnt/asec
/dev/block/mtdblock1 127.3M 118.8M 8.5M 93% /system
/dev/block/mtdblock3 248.8M 65.2M 183.5M 26% /data
/dev/block/mtdblock2 40.0M 1.1M 38.9M 3% /cache
/dev/block/vold/179:1
3.7G 2.3G 1.4G 63% /mnt/sdcard
/dev/block/vold/179:1
3.7G 2.3G 1.4G 63% /mnt/secure/asec
localhost / # mount -o remount,rw /dev/block/mtdblock1 /system
localhost / # cd /system/
localhost system # ln -s /data/local/bin/ sbin
localhost system #
Now add my personal boot script:
Code:
localhost system # cd /etc/init.d/
localhost init.d # ls -l
-rwxrwxrwx 1 root root 365 Feb 29 2008 00banner
-rwxrwxrwx 1 root root 27 Oct 9 2010 01sysctl
-rwxrwxrwx 1 root root 229 Feb 29 2008 03firstboot
-rwxrwxrwx 1 root root 105 Feb 29 2008 04modules
-rwxrwxrwx 1 root root 1593 Feb 29 2008 05mountsd
-rwxrwxrwx 1 root root 794 Feb 29 2008 20userinit
localhost init.d # ln -s /data/local/bin/rc.local 99doublehp
localhost init.d #
and populate /data as required:
Code:
bash-3.2# tar -czf bin.tgz /data/local/bin/
tar: removing leading '/' from member names
bash-3.2#
[email protected] /tmp $ adb -s SH169V80XXXX pull /data/app/bin.tgz
3660 KB/s (411734 bytes in 0.109s)
[email protected] /tmp $
[email protected] /tmp $ adb -s 0123456789ABCDEF push bin.tgz /data/local/tmp/
1972 KB/s (411734 bytes in 0.203s)
[email protected] /tmp $
localhost / # tar -xvzf /data/local/tmp/bin.tgz
data/local/bin/
data/local/bin/cpu
data/local/bin/rc.local
data/local/bin/psa
[...]
ah ... at last, ONE difference:
Code:
localhost / # head -n1 /system/sbin/psa
#!/system/bin/bash
localhost / # which bash
/system/xbin/bash
localhost / #
localhost / # cd /system/bin/
localhost bin # ln -s ../xbin/bash .
localhost bin #
No way to edit each and every script ^^
Most important one for debugging:
Code:
localhost ~ # vibrate 100
Voltage not provided. Using default 3100 mV.
/system/sbin/vibrate: line 37: /sys/devices/virtual/timed_output/vibrator/voltage_level: No such file or directory
localhost ~ # vibrate 500
Voltage not provided. Using default 3100 mV.
/system/sbin/vibrate: line 37: /sys/devices/virtual/timed_output/vibrator/voltage_level: No such file or directory
localhost ~ #
Let's prepare the SDcard for Debian use; since CM6 does not have mkfs.ext3, I did that on my workstation.
Code:
localhost / # mkdir -p /data/local/mnt/sdcard_ext
localhost / # mount /dev/block/mmcblk0p1 /data/local/mnt/sdcard_ext/
localhost / #
I should have started by this (to help understand these logs), but it's never too late:
on HD: vi /etc/bash/bashrc
PS1='\[\033[01;31m\][email protected]\[\033[01;34m\]:\w\[\033[00m\] '
on Sensation: vi $HOME/.bashrc
PS1='\[\033[01;31m\][email protected]\[\033[01;34m\]:\w\[\033[00m\] '
This prompt is handy so that I can do copy-paste of the prompt itself for use with scp and rsync: if I am at one place in ssh, I can copy the prompt to scp a file there from an other machine.
So ... I was about to copy my Debian: I put both SDcards in the workstation.
Code:
[email protected]:~ cp -a /media/uSD_ext3/Linux /media/Hmmm/
Remove sshd keys to force regen ( /etc/ssh/ssh_host_*). Update hostname (it never properly worked in Armel).
... I'll continue overnight.

doublehp said:
I
After viewing http://cdn.youtubeavi.com/view-video/0TpYHpfHW-8 (confirmed by reading http://resetguide.com/2012/05/how-to-install-android-on-hd2-nand/ ), I saw that amongst my 1GB of data downloaded in the last days, I did not have the file ANDR_install.exe; I downloaded all possible ROMs until I find one having this magic file: http://forum.xda-developers.com/showthread.php?t=893637 . Only this ROM has andr_install.exe . And when I ran it, it worked on the first time (while of course having HD with MAGLDR on option 5: USB flash).
Click to expand...
Click to collapse
...because thats the old, outdated way of installing android,, pre-nand recovery, , and those are old, outdated android roms which is why only they have the 'magic' (now obsolete) file.

samsamuel they may be outdated, but I love CM6 (after 1h of use, I find it very good), and no other method worked (4 or 5 other different methods all ended up in the RSPL.cpp issue).
To take control of my new Android, a friend told me to try AndroidScreenCast. It's some kind of VNC, specially written for Android.

Once Android is installed, you can have fun with it, without touchpad, by using http://code.google.com/p/androidscreencast/ . I am lucky that on CM6, adb was enabled by default. Download http://androidscreencast.googlecode.com/svn/trunk/AndroidScreencast/dist/androidscreencast.jnlp and run it with
Code:
javaws androidscreencast.jnlp
I will try to not use it at all. I tried it, just so that I can tell "it works", and discard all welcome menus. Did not even configure Wifi.

invalid rsync error - rsync not found in path

[Thread edited and changed, because partially solved]
Device: asus Nexus 7
Android Version: 4.2.2
Build: JDQ39
rooted
I have installed SSHDroidPro (v1.9.6) - https://play.google.com/store/apps/details?id=berserker.android.apps.sshdroidpro and Terminal IDE (v2.02) - https://play.google.com/store/apps/details?id=com.spartacusrex.spartacuside
Code:
/storage/emulated/legacy # which rsync
/storage/emulated/legacy # which mkdir
/data/data/berserker.android.apps.sshdroidpro/home/bin/mkdir
Code:
-rwx------ 1 u0_a86 u0_a86 1012309 Dec 5 2011 /data/data/com.spartacusrex.spartacuside/files/system/bin/rsync
What do I have to do, that _this_ rsync is used by SSHDroidPro? I would like to use all shell.commands from Terminal IDE with SSHDroidPro.
It helped to copy rsync set the permissions to 755 and link it:
Code:
cp /data/data/com.spartacusrex.spartacuside/files/system/bin/rsync /data/data/berserker.android.apps.sshdroidpro/dropbear
ls -l /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
-rwxr-xr-x 1 root root 1012309 Mar 10 01:37 /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
ls -l /data/data/berserker.android.apps.sshdroidpro/home/bin/rsync
lrwxrwxrwx 1 root root 60 Mar 10 01:38 /data/data/berserker.android.apps.sshdroidpro/home/bin/rsync -> /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
And then:
Code:
/storage/emulated/legacy # which rsync
/data/data/berserker.android.apps.sshdroidpro/home/bin/rsync
The rest of the posting was deleted, because it was a bug in my script. But what can I do, so the ssh-server can use the commands ot the IDE-Terminal?

SuperSU not autostarting

Hello, I hope someone has seen this before. I am not sure how I managed to break S7, as it was working, initially. I am running PE1 firmware, and factory reset before following the root guide, in the verizon guide forums. But now I have the problem where supersu will not auto start on bootup. I have to connect the usb cable to my pc, and use adb and manually start it. Root and Supersu are loaded. The only thing I have to run is:
C:\adb\adb.exe shell /system/etc/launch_daemonsu.sh
Then disconnect the usb cable, and all is well. Everything seems to be correct. What am I missing? I really do not want to start completely over. I have run the verizon debloat v2 and v8. I had to manually start supersu to flashfire the v8 script. Also in the same guide. All the root checker apps will see that you have root, but they say you are missing a super user app.
C:\adb\adb.exe shell /system/etc/launch_daemonsu.sh
mkdir: '/su': File exists
cp: /cache/stock_boot_*: No such file or directory
cp: bad '/cache/stock_boot_*': No such file or directory
/data/su.img: recovering journal
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: clean, 25/2048 files, 1399/8192 blocks
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
mount: No such file or directory
mount: No such file or directory
supolicy v2.74 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Patching policy ...
(Android M policy compatibility mode)
- Success
<Then disconnect the usb cable, supersu will work fine now.>
C:\adb>adb shell cat /system/etc/init.sec.boot.sh
#!/system/bin/sh
echo "init.sec.boot.sh: start" > /dev/kmsg
# start deferred initcalls
cat /proc/deferred_initcalls
## strace for system_server
#str=""
#while [ "$str" = "" ]; do
# str=`ps | grep system_server`
# sleep 0.1
#done
#
#pid=${str:10:4}
#echo "init.sec.boot.sh: strace -tt -T -o /data/log/strace.txt -p ${pid}" > /dev/kmsg
#strace -tt -T -o /data/log/strace.txt -p ${pid}
/system/etc/launch_daemonsu.sh
/data/s7startup/startupscript.sh
C:\adb>adb shell ls -la /system/etc/launch_daemonsu.sh
-rwx------ root root 4686 2016-07-03 13:32 launch_daemonsu.sh
Thanks again.

Did you push the supersu app to you device?

Is that to say uve got supersu installed but it won't start? If that's so I would check the box for start supersu during bootup. Unless im just completely missing your issue and im sorry if I am.