Related
Noticed this morning, when I power up holding HOME the phone lockes on the 'HERO' first screen and I can not get into RA...
Anyone got any ideas ?
somebody ? anybody ? this is a disaster, i can not get into my boot menu to install or flash or anything. the phone boots normally if i dont hold the HOME button, but when i power on with the home button held, it locks..... please help me...
Ian_4614 said:
somebody ? anybody ? this is a disaster, i can not get into my boot menu to install or flash or anything. the phone boots normally if i dont hold the HOME button, but when i power on with the home button held, it locks..... please help me...
Click to expand...
Click to collapse
Happened to me too.. no worries..
Re-flash AR through fastboot and it will work again..
adb shell reboot bootloader
adb shell mount /sdcard
adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb shell reboot
that's it .. you can rename recovery-RA-hero-v1.6.2.img to something shorter so you don't have to type so much
inertiax3 said:
Happened to me too.. no worries..
Re-flash AR through fastboot and it will work again..
adb shell reboot bootloader
adb shell mount /sdcard
adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb shell reboot
that's it .. you can rename recovery-RA-hero-v1.6.2.img to something shorter so you don't have to type so much
Click to expand...
Click to collapse
thanks, but i do not understand, how do i access fastboot ? i am keen to learn but this is new to me...
I'm pretty sure that this is the process, got this from the RA-heroc-v1.6.2.img thread:
adb shell reboot bootloader
fastboot boot recovery-RA-heroc-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell reboot
Click to expand...
Click to collapse
muzz3256 said:
I'm pretty sure that this is the process, got this from the RA-heroc-v1.6.2.img thread:
Click to expand...
Click to collapse
Appreciate that,, but i am sorry to say it does not make any sense to me. How to i get into FastBoot,, what do I press etc,, and once I am there,, what do I do ?
Ian_4614 said:
Appreciate that,, but i am sorry to say it does not make any sense to me. How to i get into FastBoot,, what do I press etc,, and once I am there,, what do I do ?
Click to expand...
Click to collapse
I NEVER DONE THIS BEFORE...
back + power button will take you to fastboot...
BUT, I believe "adb shell reboot bootloader" will take you to the right place instead of trying button combinations. So, you can run these commands from normal boot itself.
so when you say, run from normal boot itself, you mean from a file manager etc ?
Ian_4614 said:
so when you say, run from normal boot itself, you mean from a file manager etc ?
Click to expand...
Click to collapse
No!
Do you have adb setup? If not set it up using this link:
http : // theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Check this link as well: http://forum.xda-developers.com/showthread.php?t=502010
no, you start your phone up normal, go to settings and make sure usb debugging is enabled, then connect your usb-cabel, go to your sdk-directory and type adb shell reboot bootloader, then your phone will reboot into fastboot
Not sure,, this is what I added when I flashed the phone..
boot up the hero, plug in the usb, execute the commands that were given to you on the pc. that is all. you need adb on the pc for that.
right, i dod not know i had to have a programe on the PC,,, I will look for adb and see where I can find it. Is this an app I need to install on the PC ? where do I get it ?
Ian_4614 said:
right, i dod not know i had to have a programe on the PC,,, I will look for adb and see where I can find it. Is this an app I need to install on the PC ? where do I get it ?
Click to expand...
Click to collapse
cracked it, downloaded ROM MANAGER app and this enabled me to flash alternative RA Recovery,, and all now working,
Im starting this new thread because I was not able to find a solution for my problem for about 2 weeks now.
Issue : Unable to install recovery. Im trying to install recovery by following this thread : http://forum.xda-developers.com/showthread.php?t=2221102 - in the 3rd step when i flash the recovery i get this error "command write failed - unknown error"
- tried almost all the different types of steps available in xda and also outside xda.
My Environment:
Win8 Pro 32bit
LG optimus L9 flashed and rooted by lelus method - Current ROM - P76020c
Installed all LG drivers - PC suite is installed
Have SDK manager installed
Device is recognized when I run the "adb devices" command keeping phone switched on.
Device is recognized when I run the "fastboot devices" command when phone is in fastboot mode.
So I guess this is not a driver issue.
Im also attaching screenshots of the error and the commands that I have ran ....
SOOOOOOOOOOOO ... whats the prob here .... ... anyone faced this same prob ???? HELPPPP
rkn989 said:
Im starting this new thread because I was not able to find a solution for my problem for about 2 weeks now.
Issue : Unable to install recovery. Im trying to install recovery by following this thread : http://forum.xda-developers.com/showthread.php?t=2221102 - in the 3rd step when i flash the recovery i get this error "command write failed - unknown error"
- tried almost all the different types of steps available in xda and also outside xda.
My Environment:
Win8 Pro 32bit
LG optimus L9 flashed and rooted by lelus method - Current ROM - P76020c
Installed all LG drivers - PC suite is installed
Have SDK manager installed
Device is recognized when I run the "adb devices" command keeping phone switched on.
Device is recognized when I run the "fastboot devices" command when phone is in fastboot mode.
So I guess this is not a driver issue.
Im also attaching screenshots of the error and the commands that I have ran ....
SOOOOOOOOOOOO ... whats the prob here .... ... anyone faced this same prob ???? HELPPPP
Click to expand...
Click to collapse
As always, use at your own risk.
Upload recovery image to sdcard and change the file name to recovery.img if that helps
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
or terminal emulator straight from the phone
Code:
su
busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
Lelus said:
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
[/QUOTE]
is this the exact code that we should type into the cmd after getting to fastboot mode ??? or shud this be ran while phone is switched on ???
Click to expand...
Click to collapse
rkn989 said:
is this the exact code that we should type into the cmd after getting to fastboot mode ??? or shud this be ran while phone is switched on ???
Click to expand...
Click to collapse
phone switched on, usb mode: camera or lg software
btw, you have unlocked the bootloader , right ?
Lelus said:
phone switched on, usb mode: camera or lg software
btw, you have unlocked the bootloader , right ?
Click to expand...
Click to collapse
yess .... my bootloader is unlocked ....
tried this and get an error - su not found - check screenshot
im not getting the command that we tried :
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
"su" stands for ???
and where should i copy the .img file to ?? (i copied it to the root of the ext sd card)
anyone any suggestions ?????
May be your file is corrupt. Just give it a try.
Download latest version of CWM Touch and Non-touch version from http://www.clockworkmod.com/rommanager and try again.
cmahendra said:
May be your file is corrupt. Just give it a try.
Download latest version of CWM Touch and Non-touch version from http://www.clockworkmod.com/rommanager and try again.
Click to expand...
Click to collapse
Ive already tried that ... have tried downloading the files many times .. already have 4-5 copies of both the normal and touch recoveries ...
Its the same error !!!!!!
And yu want me to try by the fastboot method rite ?? not the method lelus juzz said ???
Lelus said:
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
or terminal emulator straight from the phone
Code:
su
busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
Can yu explain this in more detail. ????
Sent from my LG-P760 using xda app-developers app
rkn989 said:
Ive already tried that ... have tried downloading the files many times .. already have 4-5 copies of both the normal and touch recoveries ...
Its the same error !!!!!!
And yu want me to try by the fastboot method rite ?? not the method lelus juzz said ???
Click to expand...
Click to collapse
Lelus is explaining you in details and he is expert here. I am just confirming that if you have tried the basic things or not. By the way, your fastboot drivers seem working as device responds to "fastboot devices" command properly.
The fastboot screen should show the phone is unlocked or not, exactly like this....does it show like this screenshot?
SW Upgrade mode also should show unlocked like this screnshot.
If not, you may not be yet Unlocked and fastboot will not work.
cmahendra said:
Lelus is explaining you in details and he is expert here. I am just confirming that if you have tried the basic things or not. By the way, your fastboot drivers seem working as device responds to "fastboot devices" command properly.
The fastboot screen should show the phone is unlocked or not, exactly like this....does it show like this screenshot?
SW Upgrade mode also should show unlocked like this screnshot.
If not, you may not be yet Unlocked and fastboot will not work.
Click to expand...
Click to collapse
I din know where exactly to run those commands, so asked detailed steps
And the my bootloader is unlocked, I get the fastboot boot mode when I run the adb reboot command to unlock bootloader, yday when I flashed my phone with v20c, I gt the second screenshot as yu mentioned, also i tried running that *# command from inside the phone and it showed bootloader status- unlock.
So I hope it is unlocked! !!
Sent from my LG-P760 using xda app-developers app
ATLASTTT !!!!!!!!!!!!! I have succeeded in flashing my recovery .....
but the resolution is strange .... it just worked fine in WIN7 .... isn't that strange ???????????
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Dexter885 said:
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Click to expand...
Click to collapse
Look here: http://forum.xda-developers.com/showthread.php?t=2439949.
It seems that the bootloader is locked.
tylerr55 said:
Look here: http://forum.xda-developers.com/showthread.php?t=2439949.
It seems that the bootloader is locked.
Click to expand...
Click to collapse
If overwriting / dev/block/mmcblk0p5 with emmc_appsboot.bin, the phone will not boot up. It must be restored with an image kdz.
Any news? I've been waiting for cwm for long
Hey,
The correct comand on adb to unlock bootloader on Lg devices is:
adb reboot oem-unlock
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
reffer to http://forum.xda-developers.com/showthread.php?t=2224020
pedrocel85 said:
Hey,
The correct comand on adb to unlock bootloader on Lg devices is:
adb reboot oem-unlock
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
reffer to http://forum.xda-developers.com/showthread.php?t=2224020
Click to expand...
Click to collapse
Someone try this method on P710?
try, it will do no harm
maxx_hr said:
Someone try this method on P710?
Click to expand...
Click to collapse
Did you try it?
Did it work?
======================
OP:
Dexter885 said:
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Click to expand...
Click to collapse
Any news about the recovery?
Vagelis1608 said:
Did you try it?
Did it work?
======================
OP:
Any news about the recovery?
Click to expand...
Click to collapse
Tried, does not work!, Googling I found this guide,
Code:
://translate.googleusercontent.com/translate_c?depth=1&hl=it&rurl=translate.google.it&sl=ru&tl=en&u=http://4pda.ru/forum/index.php%3Fshowtopic%3D466295%26st%3D0&usg=ALkJrhhM8yja33NUhK__pNP0aLRznOSGhg#entry22312158
But it not work well on the P710. I found this bug: when you disconnect and reconnect the battery the phone will not turn over and go into an infinite loop!
Necessary to crack the bootloader, but I nn I know these ...
The cwm start on my lg p710 but the same problem with battery,if i go in cwm(volum down+home+power)and rebot from there the phone start.
Sorry for my bad english.
I try CWM from this thread:
http://forum.xda-developers.com/show...2700579&page=3
on my P710, and it works-no upside down problem, no bootloops.
But I dont install gscript, just put APPSSBL.bin and recovery.img on their places.
After that, i perform backup with one warning message-no file_contexts, but on second backup it dissapears...:good:
nobody here still unlocked L7 II bootloader ?
please take look at this
http://forum.xda-developers.com/showthread.php?t=2212092&page=4
since page 4 there are users talking about unlocking bootloader and it seems some of them did unlock bootloader and installed succesfully CWM.
RenatoNismo said:
nobody here still unlocked L7 II bootloader ?
please take look at this
http://forum.xda-developers.com/showthread.php?t=2212092&page=4
since page 4 there are users talking about unlocking bootloader and it seems some of them did unlock bootloader and installed succesfully CWM.
Click to expand...
Click to collapse
Just see link from my post, this is newer version of your, taken from same russian site.
With this bootloader and CWM, i just flash some P713 mod (deodexed, with kit-kat look), but i can confirm some problem with restoring-everything works, but restoring data (maby because i have more than 500 files in one folder ) failed. I must try restoring without that amount of data.
Anyway, backup in my case, is success, because restoration of sistem/boot gives me result like factory reset of original (but some data, before error is restored). After restoring, i just reset/clean dalvik to clean garbage, and phone works like new one, and even stay rooted.
Sorry for bad english...
Is the way to make logcat at boot? My computer doesn't detect phone.
Xerdox said:
Is the way to make logcat at boot? My computer doesn't detect phone.
Click to expand...
Click to collapse
Hi Xerdox, I don't know why, but my L9 P760 with stock rom is only detected by ADB when in Charge Only mode.
If that mode works for you too,
you could try
Code:
adb wait-for-device && adb logcat > logcat.txt
Then reboot your L9.
Cheers. Good luck.
Never actually got it done, But see the last post for a workable solution.
Hi all.
The basics:
Device Samsung Galaxy Tab A SM-T295 android 9 PC WIN 7 PRO
Trying to do this >> https://www.xda-developers.com/change-sms-limit-android/
Started this >>> https://www.xda-developers.com/install-adb-windows-macos-linux/
Got this:
I have the USB DEBUGGUNG turned on.
I get the COMMAND WINDOW open
I enter "adb devices" and I get a result
list of devices attached
Enter again and it doesn't show a serial number.
If command
Code:
adb devices
doesn't bring up any device, then an USB connection isn't successfully established. Read here how to fix it.
If device got successfully connected you get its serial-number entering command
Code:
adb shell getprop ^| grep ro.boot.serialno
jwoegerbauer said:
If command
Code:
adb devices
doesn't bring up any device, then an USB connection isn't successfully established. Read here how to fix it.
If device got successfully connected you get its serial-number entering command
Code:
adb shell getprop ^| grep ro.boot.serialno
Click to expand...
Click to collapse
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
But as a test I will do the following from the other thread:
Type in cmd
adb kill-server
adb start-server
Click to expand...
Click to collapse
A lot of that other thread seems to be directed at LINUX users and the thread starter was working on a rooted device which I do not have.
Going to do this
run cmd as Administrator
Click to expand...
Click to collapse
too.
This looks promising so after the above I will try it:
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
Click to expand...
Click to collapse
Back later
Cut_Right_Sharpening said:
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
But as a test I will do the following from the other thread
Back later
Click to expand...
Click to collapse
OK.
Got this from everything except going into recovery mode.
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb kill-server
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb server
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb shell getprop ^| grep ro.boot.serialno
error: no devices/emulators found
Click to expand...
Click to collapse
Cut_Right_Sharpening said:
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
This looks promising so after the above I will try it:
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
Back later
Click to expand...
Click to collapse
Ok this is what I got in recovery mode on the Tab A
https://drive.google.com/open?id=1SCYtbrZKnnfrkNVP34S-H9Jq0SQHSYqj
Still getting this from the CMD WINDOW
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb shell getprop ^| ro.boot.serialno
error: no devices/emulators found
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>
Click to expand...
Click to collapse
@Cut_Right_Sharpening
Is the device shown with a yellow exclamation mark in the Windows device manager when in recovery mode? If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
BTW:
Wondering why the hell you started the device in recovery mode to access it via ADB? Noone does so, me included.
jwoegerbauer said:
@Cut_Right_Sharpening
Is the device shown with a yellow exclamation mark in the Windows device manager when in recovery mode? If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
BTW:
#1 Wondering why the hell you started the device in recovery mode to access it via ADB? Noone does so, me included.
Click to expand...
Click to collapse
#1 Because that was one of the suggestions by this guy https://forum.xda-developers.com/member.php?u=5498377 in the thread I was sent to by the first poster.
Yes, The SM-T295 has the exclamation mark.
If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
Click to expand...
Click to collapse
With WHAT????
@Cut_Right_Sharpening
This is my last post here: Honestly, I have no lust telling you how to successfully run ADB - this may do others here.
What you should know:
1.
Especially for Samsung devices a device-relevant USB driver for Windows OS provided by Samsung Co.Ltd. exists. Hint: Install the one that matches your device, don't further on make use of the obscure one you've already installed.
2.
ADB needs neither the device to be rooted ( unless you want to perform system relevant operations such as modifying system properties ) nor to be run as Administrator nor something else.
3.
Running Android in recovery mode only is useful if you want to perform system maintenance operations, such as
a) reboot system
b) apply update from SD card
c) apply update from cache
d) wipe data/factory reset
e) backup user data
f) restore user data
Note that on stock recovery the ADB utility only registers that the device is connected. When you try applying adb shell or any other thing you'll get an error: it only accepts adb push commands to the device.
Good luck.
jwoegerbauer said:
@Cut_Right_Sharpening
This is my last post here: Honestly, I have no lust telling you how to successfully run ADB - this may do others here.
Good luck.
Click to expand...
Click to collapse
Well, The link to the Drivers may someday be very useful.
I am going to change the thread line to indicate I have given up. There may be people that have the knowledge to do this, but I suspect Google has been working overtime to make it nearly impossible without rooting and I am not ready to go that far.
Should someone else stumble on this thread, it looks like my solution is going to be HitEmUp APP . Not exactly a fully automatic Bulk mailer, but I think it will work for what I want as long as I stay under the 30 SMS/30Minute limit.