Issues with USB connectivity etc. and root / A2SD

[Guest jeckyllhavok]

ok

im trying to find a way to acces the recovery menu without adb

when phone boots in recovery it is looking for /cache/recovery/command

i am trying to find a way to copy the recovery files from for example /data/local/files

or any other writable area

any help would be welcome on how to do that without /system/bin/sh

everytime the phone boots in recovery it is looking for that file and after reboot its deleted again so the command file needs to be placed there again for a new recovery

greetings from a vastloper

Man, if i can help you in any way, please tell me, will test what's needed

[Guest ZiCoN]

Would it be possible for a ROOTED usb-bricked phone in a terminal emulator to do a:

sudo mkdir /cache/recovery/command/ (or just the mkdir) or is this in the locked down part of the system?

[Guest vastloper]

Would it be possible for a ROOTED usb-bricked phone in a terminal emulator to do a:

sudo mkdir /cache/recovery/command/ (or just the mkdir) or is this in the locked down part of the system?

That is possible but i need to know the commands that can be used in the command file so when it is executed in recoverymode it'wil create the directory's and copy the recovery files to the correct place

the filename is command and should be placed in the folder /cache/recovery

[Guest jeckyllhavok]

Would it be possible for a ROOTED usb-bricked phone in a terminal emulator to do a:

sudo mkdir /cache/recovery/command/ (or just the mkdir) or is this in the locked down part of the system?

i got a no such file or directory

[Guest jeckyllhavok]

i got a no such file or directory

in cache folder there is no recovery

+++++++++++edit

okay i created the folder, in /cache

mkdir recovery

cd recovery

mkdir command

cd command

no not allowed messages, command folder is created

Edited May 15, 2010 by jeckyllhavok

[Guest vastloper]

in cache folder there is no recovery

i know

but you can create that folder there

#mkdir /cache/recovery

for now im interested in what commands can be used in the command file

[Guest jeckyllhavok]

i know

but you can create that folder there

#mkdir /cache/recovery

for now im interested in what commands can be used in the command file

edited above post,

what commands should i add?

Edited May 15, 2010 by jeckyllhavok

[Guest ZiCoN]

Could a non-bricked try going into recovery, would it then be possible to #cat it out?

[Guest vastloper]

Could a non-bricked try going into recovery, would it then be possible to #cat it out?

i am non bricked

there is no command file

we need to create something that is doing about the same as the recovery in windows is doing

in other words

create a command file that is able to copy some files to /syste/bin and to /system/lib and some more

[Guest jeckyllhavok]

i am non bricked

there is no command file

we need to create something that is doing about the same as the recovery in windows is doing

in other words

create a command file that is able to copy some files to /syste/bin and to /system/lib and some more

which name should the command file have?

[Guest jeckyllhavok]

which name should the command file have?

Whats with that:

cp /sdcard/files/ /

busybox --install /sbin

/sbin/recovery &

basicly the same as the recovery script from r4 root

Edited May 15, 2010 by jeckyllhavok

[Guest eViL D:]

i am non bricked

there is no command file

we need to create something that is doing about the same as the recovery in windows is doing

in other words

create a command file that is able to copy some files to /syste/bin and to /system/lib and some more

How about looking at logcat while booting to recovery. See if we can emulate that in a script, and then execute recovery/pushfiles.

Come to think of it. Root Boot (and maybe others) can boot directly to recovery, maybe a script can be added after that initial script. Like an if recovery mode, then push/execute.

[Guest ZiCoN]

Modified kernel... tunnel loaded on boot...

http://android.modaco.com/content/htc-desi...-ext4-tun-cifs/

If he can make the system eat something during boot, would it be possible to make a script that could make the system eat the board_bravo commands also?

[Guest ZiCoN]

Paul... Not to a pain in the ¤ , but any news from your sources that could help us end our suffering?

[Guest Kali-]

Modified kernel... tunnel loaded on boot...

http://android.modaco.com/content/htc-desi...-ext4-tun-cifs/

If he can make the system eat something during boot, would it be possible to make a script that could make the system eat the board_bravo commands also?

for what i have understood, the option board_bravo... is not kernel command line options, but this command sames to disabling or modify the hw configuration before kernel start, also Richard Trip script load modules during the OS startup but after the kernel is loaded

probably kernel source didn't help much to fix this problem

[Guest ZiCoN]

hey guys, something really random - if your battery is being sucked 3x faster than before your usb-brick, try this

http://www.technipages.com/htc-hero-start-in-safe-mode.html

I know it says Hero, but it works on Desire too.

My battery lasts forever now. 14+ hours and 73% left. Stoked :)

Last 7 hours was WiFi enabled in background, Gmail checks every hour etc.

I have a feeling 3G data will still suck the life out of it, but from memory it did that anyway the first week I had this phone (before rootedupdate.zip)

To be honest... I think it have actually done a huge difference... My Desire have been running 7 hours+ after I did this... At that point I had approx 90% battery. Since then I have had wi-fi enabled and used it HEAVILY... I'm at 60% ;)

[Guest mardox]

i have just got this problem aswell and seen that the sdcard portion of the problem has been fixed with some quick fastboot commands, i am just wondering where i use these commands? in the normal command prompt while having the device in fastboot usb mode?

[Guest xhemp]

i have just got this problem aswell and seen that the sdcard portion of the problem has been fixed with some quick fastboot commands, i am just wondering where i use these commands? in the normal command prompt while having the device in fastboot usb mode?

Yes, just go to fastboot mode and do:

fastboot oem enableqxdm 0

fastboot reboot

You will get your SD and celullar network back.

[Guest ZiCoN]

i have just got this problem aswell and seen that the sdcard portion of the problem has been fixed with some quick fastboot commands, i am just wondering where i use these commands? in the normal command prompt while having the device in fastboot usb mode?

Fastboot... hold 'back key' on press power... go into your favorite adb\tools directory via command prompt and enter: fastboot oem enableqxdm 0

Edited May 15, 2010 by ZiCoN

[Guest ZiCoN]

Yes, just go to fastboot mode and do:

fastboot oem enableqxdm 0

fastboot reboot

You will get your SD and celullar network back.

;) we've done this a few too many times :)

[Guest xhemp]

:D we've done this a few too many times ;)

indeed :)

I ran out of ideas for our issue though, unfortunately...

[Guest ZiCoN]

Any of this useable?

http://shadowmite.com/wiki/index.php/The_T...Hidden_Commands

gettoken, settoken... never came across this before...

[Guest mardox]

ok i opened a command prompt to the tools directory in android sdk and typed fastboot oem enableqxdm 0 , but no luck, when i hit enter 3 dots came up in command promt like it is working but nothing has happened past five minutes. i cant type anything new in cmd.

or maybe it should take this long?

[Guest xhemp]

ok i opened a command prompt to the tools directory in android sdk and typed fastboot oem enableqxdm 0 , but no luck, when i hit enter 3 dots came up in command promt like it is working but nothing has happened past five minutes. i cant type anything new in cmd.

or maybe it should take this long?

Ok, 3 dots and then it went back to the cmd prompt or is it still stuck?

Also, are you on fastboot mode?

If everything is alright, you should be able to get your sd/cellular working when you switch your phone back on.

[Guest ZiCoN]

ok i opened a command prompt to the tools directory in android sdk and typed fastboot oem enableqxdm 0 , but no luck, when i hit enter 3 dots came up in command promt like it is working but nothing has happened past five minutes. i cant type anything new in cmd.

or maybe it should take this long?

try "fastboot devices" This should show you the connected devices...

It should give an output sort of like: OKAY...