Database Develop

Help with Autostart please.

I'd like to run adblock.sh and Nimbuzz after the phone has booted and connected to the internet. So far I've been able to write code that launches nimbuzz via a shell script like this:
Code:
am start -n com.nimbuzz/com.nimbuzz.InitScreen
but nothing happens when I save that to a file called autostart.sh in /data/opt/
However, issuing that command via adb or a terminal session does launch the app. I looked at other .sh files (userinit.sh etc) and saw that the PATH variable was defined so I added that but still nothing.
I figure running adblock.sh should be easy enough but have no idea how to make the script check for an internet connection. I figure I'd have to wait about 120 seconds for the phone to boot and acquire net connectivity (either 3g or wifi), so I could use something like sleep 120 to pause the script for two minutes before attempting to continue.
Could someone help me build an autostart.sh file? I'd really appreciate the help.

well... could someone please point me to a tutorial on shell scripts for android then? I've applied fu but have yet to come up with anything functional.

Hey bud,
Try saving the script in /system/sd, and naming it userinit.sh
If there already is a userinit.sh, just add the line to the very end of the file. You'll need to edit it in the computer
adb pull /system/sd/userinit.sh "C:/userinit.sh"
open the file in wordpad, make your addition,
adb push "C:/userinit.sh" /system/sd/userinit.sh
PM me if that doesn't work.

Help is appreciated.

Ok so this all started 7 hours ago.
I did a factory reset and I couldn't get passed the gmail account login. I tried multiple times, and tried resetting. Didn't work.
So I looked online to see if I can use wifi, and I could.
http://modmygphone.com/forums/showth...1891#post51891
I updated my drivers, downloaded Android SDK.
I got up to the part where I type " adb shell "
It says no devices found. Please help. Thanks in advance :]
Currently I am in stock ROM RC29.
I am trying to do this on the site above:
"6. Now type this on your G1 keyboard..
<enter>setprop persist.service.adb.enable 1<enter>
7. Now.. Open the command prompt on your PC ( Start > Programs > Accessories > Command Prompt )
8. Type "adb shell" without the quotes.
(Just in case typing that doesn't do anything.. Navigate to the folder you've unzipped the ADB Files and type there instead)
9. Then when the '$' comes out .. type this:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
9. Take a look at your G1 and now it'll be in the WiFi settings section. Configure it.. Connect to your network.. And done!"

I find this guide:http://forum.xda-developers.com/showthread.php?t=532719 much easier to follow
the code
cd C:\android-sdk-windows\tools needs to be typed in the cmd before typing in adb shell.

thanks for the guide, but I followed what you said/the guide said, still the same result =/

TmobileDash12 said:
thanks for the guide, but I followed what you said/the guide said, still the same result =/
Click to expand...
Click to collapse
Do you have the android-sdk-windows file on the root of your C drive?

Debugging
Did you make sure to add a path for adb in the environmental variables tab on the pc, and also make sure that usb debugging is checked off in the settings>applications>development tab.

It is in my C drive or root folder.
I can't access settings because my phone's stuck on the login screen.

Need help with METROPCS FLASH. Talk Text and Web but...

Hey guys I basically did everything that the Cricket how to said, but with the Metropcs logins and passwords. I have flashed several phones before, but not an Android OS. The phone works with internet and picture text coming in, but the apps. like Youtube and Google maps will only work on WIFI and not on the network and MMS out will also not work.
My assumption is that it has to do with this whole autostart file thing. I am so new to this programming stuff that I am not sure what to do when it comes to this.
So I used QPST and CDMAW to program the back end so that is probably why the Internet works. APN and Proxy settings are all correct, but here is the only place I have an error.
These are the directions:
Before starting the next step make sure you have the u2nl file and autostart.sh in this folder c:/android/tools
"Now go to the command prompt on your pc and type the following commands:
cd c:\android\tools
adb remount
adb push c:\android\tools\u2nl /system/bin/u2nl
adb push c:\ android\tools\autostart.sh /data/opt/autostart.sh
Now:
adb shell
chmod 0755 /system/bin/u2nl
chmod 0755 /data/opt/autostart.sh
reboot"
My error begins when I type the adb remount.... it states unable to find device or something like that.
I plugged phone to computer not in Diag mode or any mode, just turned it off then back on and plugged it in. Is there a setting on the phone I need to check?
Then I go ahead and do those push commands just for the hell of it, it just scrolls through this whole display of things.. not sure what its doing.
The adb shell part works and so do those other commands after....
When I am done with the last line that has the autostart.sh and hit enter...
The phone doesn't reboot, I just unplug and then turn off and then back on. I would have thought there would be a script to reboot phone or something...
So what am I missing or is it not even possible to get Google maps and youtube to work on Metroweb... has to be on wifi??? I have seen people say they have done it...
Any help would be appreciated..

[FIX] Phone Bootlooping?

CONFIRMED WORKING ON LINUX.. waiting to hear for windows, mac...
NOTE: Please keep track of what your doing, because if you DON'T know what you broke, your going to have a hard time fixing it.
I'd recommend NOT wiping DATA/factory restore unless you literally have NO other choice (see post 11)
That being said...
Assuming you know what change(s) you made before your bootloop, you are saying to yourself "If i could only boot up so i can UNDO it" ... this IS for you!
Directions:
Battery Pull
Put Battery Back
Hold M button on keyboard then power
Use vol - button to go to BP TOOLS (don't select yet)
Connect via USB to computer with ADB
In terminal on computer...
Code:
adb wait-for-device shell
On phone use vol + button to select BP Tools.. then wait for your terminal to get you into shell (this will happen while the phone is continuously bootlooping)
according to djrbliss root method...
Code:
mv /data/local/12m /data/local/12m.bak
ln -s /data /data/local/12m
exit
9.
Code:
adb reboot
10. wait for the power off then repeat steps 1-7
11. again thanks to djrbliss...
Code:
rm /data/local/12m
mv /data/local/12m.bak /data/local/12m
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
exit
12. then again, repeat steps 1-7
13. You should have root, now go ahead and fix whatever needs fixing and reboot 1 final time
ENJOY
-KrazyKrivda

I followed this exactly but could never get an adb connection. My drivers are good and my adb setup works just fine (I was using it earlier). And idea what I could be doing wrong?
Thank you so much for posting this btw!

one more reason why I choose linux over winblows. Just a personal opinion.

Darksurf said:
one more reason why I choose linux over winblows. Just a personal opinion.
Click to expand...
Click to collapse
I tried both Windows and Linux. Are there any special steps in Linux I may be missing to get adb to work in this mode? I tried my OG Droid to test the adb setup and it worked fine.

you need to be in the android group and have adb properly installed and preferrably the current version. I use a gentoo based linux system so this stuff isn't an issue for me.
Ubuntu and debian based systems are a little different. I really dislike the package management system and Ubuntu separates users from the actual "linux" part of linux. its like linux for n00bs. Not saying its a bad distro, its just not my distro of choice.
But, if you are booting up your device correctly, you should be able to do adb start-server and then do a adb remount (if rooted) then push the files to /system/app/
if you have just ran updates, reboot your computer. If you aren't picking up the device, try using other ports (usb ports can go into a suspend mode to save power and sometimes don't like to wake up, it also happens in windows)

Jonny9797 said:
I followed this exactly but could never get an adb connection. My drivers are good and my adb setup works just fine (I was using it earlier). And idea what I could be doing wrong?
Thank you so much for posting this btw!
Click to expand...
Click to collapse
Join us in IRC and I will try to talk you through it

please help me!
i am having the same problem. i can get into recovery, fastboot, AP, and BP modes, and my device manager sees the ADB interface, but i cannot execute commands. I get this error "C:\Program Files\Android\android-sdk\platform-tools>adb remount error: device not found". i have the latest SDK and moto drivers installed... is there anyway i can install an update.zip from recovery to get me out of the bootloop?

I've updated the OP.. there is no longer a "remount" part... so I'm not sure what you are doing.. again if you can join IRC ( webchat.freenode.com ... #krazyk is the chan ) i'd be more than happy to assist

guys, i need urgent help...
i did some **** by replacing the SystemUI.apk in RootExplorer and it started force closing. i rebooted and i started bootlooping i backed up the apk in a file on my sdcard called 'import'. now i tried BP tools but it wont recognize my device..i had adb working perfectly fine before. what should i do?

Krivda, even in VM ubuntu it still doesn't see my phone... i have jdk, sdk installed... windows and ubuntu both see my xoom but the D3 is not being seen...

if the bootloop is caused due to an issue created in /data then then a factory reset will be fine (if you don't mind losing data).
HOWEVER, if the change it made is in /system.. the factory reset may reset your adb debugging option... which in turn will mean.. you will be stuck in a bootloop without the ability to access adb at all, in which case you are SOL until sbf or a way to run update.zip from recovery.

Yep that's me! I need an sbf lol

royalpunk, let me know if you find a way out... im in the same situation...

yeah, I'm the same as royol and highcee... i guess it just gives us a double incentive to find an sbf

i am also in the same situation ugh

I haven't started to fiddle yet but fear not ill be with yus tomorrow lol
-smc

I know its tempting to foolnaround with files. But no one should be messing with anything till we get an sbf.

suzook said:
I know its tempting to foolnaround with files. But no one should be messing with anything till we get an sbf.
Click to expand...
Click to collapse
SHUTUP lol you're making me feel bad

a little clarification.. OP UPDATED

I wanted to say THANK YOU to krazykrivda.
Because of your how-to I have successfully unbricked my Droid3 )) THANKS

ADB access

Hey everyone,
I am not sure if this is the correct place to put this forum anyways, I was having an issue trying to use ADB. I read all the forums and nothing would help connect it but I finally found a site that helped.
If any of you are having an issue with ADB with the Nook HD+, run this command in terminal,
mkdir -p ~/.android && echo 0x2080 > ~/.android/adb_usb.ini && adb kill-server && adb devices
after doing this, I finally got my laptop to detect my nook.
I got this from:
nookdevs [dot] com at the adb over usb section
so all credit goes to them.
They also have some other useful troubleshooting tips if any issues.
I hope this can help someone out.

Thank you for the tip. If you have cyanogenmod installed, another option is to enable "ADB over network" in Settings--Developer Options (this option might be available in non-CM ROMs, as well). Then you can use the command "adb connect" followed by the IP address and port displayed by your tablet. A message should pop up on the device, and once you select 'allow', you should be able to open up an adb shell.
Here's a screenshot I took yesterday while struggling to identify my eMMC version over USB. I finally had success using ADB over network.

elskankinloco said:
Hey everyone,
I am not sure if this is the correct place to put this forum anyways, I was having an issue trying to use ADB. I read all the forums and nothing would help connect it but I finally found a site that helped.
If any of you are having an issue with ADB with the Nook HD+, run this command in terminal,
mkdir -p ~/.android && echo 0x2080 > ~/.android/adb_usb.ini && adb kill-server && adb devices
after doing this, I finally got my laptop to detect my nook.
I got this from:
nookdevs [dot] com at the adb over usb section
so all credit goes to them.
They also have some other useful troubleshooting tips if any issues.
I hope this can help someone out.
Click to expand...
Click to collapse
If you had check it on ArchWiki: h t tps://wiki.archlinux.org/index.php/NOOK_HD%2B (Sorry I cannot post a url)

You rule! lol. I was pulling my hair out and then poof! you're like rogaine!