Database Users

AT-Commands?

Hi there,
maybe not a XDA specific Question but maybe s.o. could still help me.
I've got a SIEMENS emem ES75 GSM Modem wich I wanted to use as a SMS receiver for my Party next month (receive sms and project them onto a wall )
But I have some trouble controlling it using the AT-Commandset.
For example: the AT+GMM Command which should give me the name of the Manufacturer) Sometimes AT+ Commands are working, sometimes not.
As it works, I printed out the current settings using AT&V:
Code:
ACTIVE PROFILE:
E0 Q0 V1 X4 &C1 &D2 &S0 \Q0 \V1
S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000
+CR: 0
+CRC: 0
+CMGF: 1
+CSDH: 0
+CNMI: 0,0,0,0,1
+ICF: 3
+IFC: 0,0
+ILRR: 0
+IPR: 115200
+CMEE: 0
^SMGO: 0,0
+CSMS: 0,1,1,1
^SACM: 0,"000000","FFFFFF"
^SLCC: 0
^SCKS: 0,1
^SSET: 0
+CREG: 0,1
+CLIP: 0,2
+CAOC: 0
+COPS: "T-MOBILE D"
+CGSMS: 3
Remember: it says "CURRENT PROFILE"
Then I used the AT&V Command when it did not work:
Code:
Current Settings............
E0 H0 Q0 V1
&C0 &D0 &P1 &R0 &S0
S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=000 S07=030
S08=000 S09=000 S10=000 S11=000 S12=050 S13=000 S14=000 S15=000
S16=000 S17=000 S18=000 S19=000 S20=000 S21=000 S22=000 S23=000
S24=000 S25=005 S26=001 S27=000 S28=000 S29=000 S30=000 S31=000
S32=000 S33=001 S34=000 S35=000 S36=000
#0 :
#1 :
#2 :
#3 :
#4 :
#5 :
#6 :
#7 :
#8 :
#9 :
Why does it output the "CURRENT SETTING" instead of the "CURRENT PROFILE"? And why can't I read the SMS? With this Setting it does not accept most of the AT+(..) commands. (AT+GMM, ...)
I sniffed the serial port communication from working applications and used the same commands and init-strings, but nothing
Any advice?

Nothing?

[Script] Collin_ph Battery Tweak [10/23/2010]

This is really a tool for power users
If you don't consider yourself 'comfortable' with messing with your phone, then don't.
This is mostly the work of collin_ph, all the ideas are mostly his and I have only contributed in part to getting some things functioning correctly and some optimizations. We've been enjoying the performance/battery life benefits for about a month now and everyone is, hopefully, enjoying it as well.
Collin, myself and a couple others have decided to turn this script into an app which I hope, and we hope, will be on the market sooner than later.
http://tweaktool.com
The original thread can be found here: http://forum.xda-developers.com/showthread.php?t=762283
This script is more functional and more efficient than applications that constantly run in the background(like setcpu,ocwidget); the reason for this is that it only polls all dependencies every 60 seconds(default) to check for changes. Even the polling interval can be changed.
Why use this?
This script has proven time and time again to not only battery life(on average, about 3-4 hours), but also improve the performance of the device.
Enough of the backstory, into the details:
READ THIS
Original documentation can be found here: http://www.primoweb.com/froyo/battery_tweak_v3.html
The entire 'application' is written in shell code and was first written just to give a performance and battery boost, but since has evolved more and more.
All the tools mentioned will be utilized either through the terminal, or in adb shell.
The Tools
batt.sh
This is the core of the entire script. Don't mess with it.
The one thing you should do after installing the script:
Code:
pidof batt.sh
If theres any number showing up after it, then it's working fine. Don't touch it.
batt-cfg
This is the 'main menu' of sorts, as it gives the user all the options and allows him to toggle tweaks/mods on the fly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Presets
The presets are just default configurations that I have set up that can make your phone more efficient without you, the user, having to manually set everything.
The preset of 806 literally means that 806400 is the scaling_max_freq, or the max frequency, that your phone can achieve after you enable it.
Just typing 1, and then enter, you'll be ready and set to go. Same with 2.
Customize Settings
This is only for the experienced user, and it allows you to manipulate most/ifnotall the configurables on your device.
All the settings explain what each option does, so read them carefully.
Disk Boost
Remounts via noatime and nodiratime. Look up what that means on your own, and why it benefits performance the way it does.
Audio 'Fix'
Disables stagefright for bettery audio quality, though it will hinder your benchmark scores only because it affects the AAC codec and how it behaves.
CFS Tweak
Echos NO_NEW_FAIR_SLEEPERS to sched_features to change CFS into more of a traditional scheduler like BFS, which gives a noticeable benchmark performance boost, but hinders how gps behaves(kind of like the real BFS).
Temperature Management
This new tool allows you to set a temperature(in celsius) at which to override the maximum frequencies to something a bit safer to save your phone battery from melting. It allows you to choose the override max frequency and the override min frequency.
So lets say that you choose the 710 preset.
And you enable the Temperature Management, and set the temperature to 450(45.0 C*) and you set the override max frequency to 537600mhz.
At 45 C*, the tweak will override the preset and echo 5376000 to scaling_max_freq until your battery temperature drops below 45.0 C*, at which point it will resume 710mhz.
Enjoy!
batt-diag
It's a diagnostics utility, allowing you or someone knowledgeable to figure out any issues that you may be having with your device and be able to pinpoint exactly where the problem is.
batt-diag -v gives a more thorough output as you can see here; http://pastie.org/1162034
batt-rm.sh
It's a battery tweak removal script, follow the onscreen prompts and it should remove just about any trace of the battery tweak script.
Prerequisites needed to run this
If you're running a version of CM6, this will work completely fine.
If you're running any other kind of rom, that developer will need to add an 'import' call in the init.rc(in the ramdisk) that imports the init.d script necessary for this application to function at boot. If you don't know how to do this, well, pm me, I might help you, depending on how much I like you.
This script will WORK even if you don't have the import call at boot, but it won't survive on the next reboot.
You can check via:
Code:
adb logcat | grep collin_ph
Code:
pidof batt.sh
NOTE: This script will also prompt you to try to run itself as root if you use it in terminal. Should work fine in CM6 ROMS but may not run fine in other ones.
Credits:
Collin_ph
Myself
Tomatosoup
s0be
Barackisbrown
vinylfreak89 for being so naggy about porting this here
Download Collin_ph BatteryTweak v3 DecaMod v2.2http://dl.dropbox.com/u/9992367/BatteryTweak-ERISv2.2.zip
MD5: 64c40363fdc1f4c5745154a627894850
Last update: Tues 10/26/2010 11:08AM CST.
Download Collin_ph BatteryTweak v3 DecaMod v2(TazzFroyo/KaosFroyo) TAKEN DOWN
MD5: 7ade3a05e20fedc958c714e62ef27bd8
If you flashed this earlier, it breaks wifi, so just reflash your ROM over the top. Tell your ROM cook to fix his CM6 !
Flash via recovery, enjoy!
Why doesn't it work for KaosFroyo/TazzFroyo?
Because they're not built like the CM6 repos, and do not have the init.local.rc import and updated busybox's as well lacking some dependencies found in CM6 itself when its built from source.
ROMs that need to have init.rc patched with import call of init.local.rc(This is necessary for this script to work correctly)
KaosFroyo
TazzFroyo
'start collin_ph' starts the service created in init.local.rc. If init.local.rc isn't imported at boot via the init.rc, then it fails.

Original Source: http://github.com/collinph/battery-tweak-v3
My Source: http://github.com/Decad3nce/battery-tweak-v3
Help us debug!
Before you complain about anything, do this.
Code:
adb shell batt-diag -v > battdiag.txt
and upload that txt file so that we can diagnose your problems more thoroughly.
For ROM Modders
You need 3 things for the script to survive a reboot:
An overclockable kernel(duh)
An 'import' call for init.local.rc in init.rc in the ramdisk.
Just paste this into init.rc after the "Define TCP buffer sizes" setprops
Code:
# Include extra init file so that the battery tweak will function
import /system/etc/init.local.rc
Proper file structuring/permissions(The update script in the update.zip really does all of this for you)

Yay it got ported. Thanks.

im naggy huh... no seriously... great job dude... immediately my CPU usage has gone down and tomorrow we'll see if battery life goes up as well.. i sure hope so... phone is overall... smoother

oh happy day! i had been using the original version of this and am happy to see it ported and enhanced... me and my eris thank you greatly!

I'm assuming that since this sets frequencies on it's own that it would be ill advised to use along with something like SetCPU?

UNCbassbone said:
I'm assuming that since this sets frequencies on it's own that it would be ill advised to use along with something like SetCPU?
Click to expand...
Click to collapse
It' CONFLICTS with setcpu, so no.
Same thing with OC widget.

Thanks checkin it out... see how tomorrow goes..

After choosing option [1] in batt-cfg I noticed it said "/system/bin/batt-cfg: line 467: load_806: command not found". I did the "pidof batt.sh" command before running batt-cfg and no number displayed after inputting the command. I ran it again after saving settings in batt-cfg and it displayed a number.

burndtjamb said:
After choosing option [1] in batt-cfg I noticed it said "/system/bin/batt-cfg: line 467: load_806: command not found". I did the "pidof batt.sh" command before running batt-cfg and no number displayed after inputting the command. I ran it again after saving settings in batt-cfg and it displayed a number.
Click to expand...
Click to collapse
Oops, bug. Thanks. Will fix in a sec
EDIT: Fixed. Same URL, check md5.

Thanks, Decad3nce. Choosing option [1] resulted in an '...integer expression expected' and saved settings. Is it normal for it to show 'Starting batt.sh /system/bin/batt-cfg: line 107: start: command not found' afterwards? The phone just rebooted (no android skateboards) as I was typing this while looking at the terminal prompt.
edit: Had to pull the battery, it froze at the loading animation. Running KaosFroyo V34 + CFSv4, for reference.

burndtjamb said:
Thanks, Decad3nce. Choosing option [1] resulted in an '...integer expression expected' and saved settings. Is it normal for it to show 'Starting batt.sh /system/bin/batt-cfg: line 107: start: command not found' afterwards? The phone just rebooted (no android skateboards) as I was typing this while looking at the terminal prompt.
Click to expand...
Click to collapse
NVM. sec. ...
I'm guessing pidof batt.sh doesn't bring back anything?

Got it flashed, messed with the settings.. looks all good so far!

Decad3nce said:
NVM. sec. ...
I'm guessing pidof batt.sh doesn't bring back anything?
Click to expand...
Click to collapse
Running the 'pidof batt.sh' command does not result in anything.

Thanks and good work.
Sent from my ERIS using XDA App

burndtjamb said:
Running the 'pidof batt.sh' command does not result in anything.
Click to expand...
Click to collapse
Means its not running at all. :S Try reflashing it, also, could you check for the dependencies necessary in batt-diag

Installed for me very smoothly on kaos34 w/CFS. pidof shows a #3
Thanks for bringing this over.
Sent from my FroyoEris using Tapatalk

Decad3nce said:
Means its not running at all. :S Try reflashing it, also, could you check for the dependencies necessary in batt-diag
Click to expand...
Click to collapse
Reflashed again, same result.
Code:
sh-3.2# pidof batt.sh
pidof batt.sh
sh-3.2# batt-diag
batt-diag
Collin_ph Battery diagnostic utility
batt-diag -v for verbose diagnostics
Checking if batt.sh service is running
pidof batt.sh:
Checking dependencies. If any dependency is blank the battery tweak may not func
tion and should be disabled
sleep: /system/xbin/sleep
mount: /system/xbin/mount
expr : /system/xbin/expr
log :
Checking tweak files and permissions
Checking batt.sh service
-rwxr-xr-x 1 root shell 7174 Aug 1 2008 /system/bin/batt.sh
Checking batt.conf configuration file
-rwxr-xr-x 1 root shell 411 Aug 1 2008 /system/etc/batt.conf
Checking batt-cfg configuration utility
-rwxr-xr-x 1 root shell 12241 Aug 1 2008 /system/bin/batt-cfg
Checking batt-rm.sh service
-rwxr-xr-x 1 root shell 889 Aug 1 2008 /system/bin/batt-rm.sh
Checking Configuration
----batt.conf file contents----
audio_fix=0
CFStweaks=0
MOUNToptions=1
enabled=1
LEDfix=0
cpu_limiting_method=1
min_freq_on_battery=245000
max_freq_on_battery=691200
min_freq_on_USBpower=245000
max_freq_on_USBpower=691200
min_freq_on_power=245000
max_freq_on_power=691200
polling_interval_on_battery=60
polling_interval_on_power=15
polling_interval_on_USBpower=15
cpu_max_underclock_perc=33
scaling_governor=interactive
cpu_scheduler=deadline
----end of batt.conf----
----Mount points----
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
/dev/block/mtdblock3 on /system type yaffs2 (rw)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noe
xec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
/proc/mounts/
cat: can't open '/proc/mounts/': Not a directory
Displaying CFS tweaks.----
/sys/kernel/debug/sched_features
NEW_FAIR_SLEEPERS NORMALIZED_SLEEPER WAKEUP_PREEMPT START_DEBIT AFFINE_WAKEUPS C
ACHE_HOT_BUDDY SYNC_WAKEUPS NO_HRTICK NO_DOUBLE_TICK ASYM_GRAN LB_BIAS LB_WAKEUP
_UPDATE ASYM_EFF_LOAD NO_WAKEUP_OVERLAP LAST_BUDDY
/proc/sys/kernel/sched_latency_ns
10000000
/proc/sys/kernel/sched_min_granularity_ns
4000000
/proc/sys/kernel/sched_wakeup_granularity_ns
2000000
Displaying Current CPU scheduler and Scaling Governor
Scaling Governor:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
ondemand
CPU scheduler:
/sys/block/mtdblock3/queue/scheduler
[noop] anticipatory deadline bfq
Displaying Batt.sh tweakables.----
/proc/sys/vm/swappiness
60
/proc/sys/vm/dirty_expire_centisecs
200
/proc/sys/vm/dirty_writeback_centisecs
500
/proc/sys/vm/dirty_background_ratio
5
/proc/sys/vm/dirty_ratio
10
/proc/sys/vm/vfs_cache_pressure
100
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
710400
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
245000
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
80
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias
0
Current charging source: 0=Battery 1=USB 2=AC
/sys/class/power_supply/battery/charging_source
1
Current battery capacity
/sys/class/power_supply/battery/capacity
100
/sys/class/power_supply/battery/health
Good
----Current Battery Temp----
95 F / 35 C
----End of Battery Temp----
----ROM Version----
Linux version 2.6.29-DecaFuctCFS-dirty-2a66c604 ([email protected]) (gcc versio
n 4.4.0 (GCC) ) #2 PREEMPT Mon Sep 6 16:49:41 EDT 2010
----End of ROM Version ----
---CPU Time in each Frequency---
19200 0
122880 0
160000 0
245760 9146
480000 313
528000 24
604800 12
710400 9575
729600 0
748800 0
768000 0
787200 0
806400 0
825600 0
844800 0
864000 0
---End of CPU Time in each Frequency----

burndtjamb said:
Reflashed again, same result.
Code:
sh-3.2# pidof batt.sh
pidof batt.sh
sh-3.2# batt-diag
batt-diag
Collin_ph Battery diagnostic utility
batt-diag -v for verbose diagnostics
Checking if batt.sh service is running
pidof batt.sh:
Checking dependencies. If any dependency is blank the battery tweak may not func
tion and should be disabled
sleep: /system/xbin/sleep
mount: /system/xbin/mount
expr : /system/xbin/expr
log :
Checking tweak files and permissions
Checking batt.sh service
-rwxr-xr-x 1 root shell 7174 Aug 1 2008 /system/bin/batt.sh
Checking batt.conf configuration file
-rwxr-xr-x 1 root shell 411 Aug 1 2008 /system/etc/batt.conf
Checking batt-cfg configuration utility
-rwxr-xr-x 1 root shell 12241 Aug 1 2008 /system/bin/batt-cfg
Checking batt-rm.sh service
-rwxr-xr-x 1 root shell 889 Aug 1 2008 /system/bin/batt-rm.sh
Checking Configuration
----batt.conf file contents----
audio_fix=0
CFStweaks=0
MOUNToptions=1
enabled=1
LEDfix=0
cpu_limiting_method=1
min_freq_on_battery=245000
max_freq_on_battery=691200
min_freq_on_USBpower=245000
max_freq_on_USBpower=691200
min_freq_on_power=245000
max_freq_on_power=691200
polling_interval_on_battery=60
polling_interval_on_power=15
polling_interval_on_USBpower=15
cpu_max_underclock_perc=33
scaling_governor=interactive
cpu_scheduler=deadline
----end of batt.conf----
----Mount points----
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
/dev/block/mtdblock3 on /system type yaffs2 (rw)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noe
xec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
/proc/mounts/
cat: can't open '/proc/mounts/': Not a directory
Displaying CFS tweaks.----
/sys/kernel/debug/sched_features
NEW_FAIR_SLEEPERS NORMALIZED_SLEEPER WAKEUP_PREEMPT START_DEBIT AFFINE_WAKEUPS C
ACHE_HOT_BUDDY SYNC_WAKEUPS NO_HRTICK NO_DOUBLE_TICK ASYM_GRAN LB_BIAS LB_WAKEUP
_UPDATE ASYM_EFF_LOAD NO_WAKEUP_OVERLAP LAST_BUDDY
/proc/sys/kernel/sched_latency_ns
10000000
/proc/sys/kernel/sched_min_granularity_ns
4000000
/proc/sys/kernel/sched_wakeup_granularity_ns
2000000
Displaying Current CPU scheduler and Scaling Governor
Scaling Governor:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
ondemand
CPU scheduler:
/sys/block/mtdblock3/queue/scheduler
[noop] anticipatory deadline bfq
Displaying Batt.sh tweakables.----
/proc/sys/vm/swappiness
60
/proc/sys/vm/dirty_expire_centisecs
200
/proc/sys/vm/dirty_writeback_centisecs
500
/proc/sys/vm/dirty_background_ratio
5
/proc/sys/vm/dirty_ratio
10
/proc/sys/vm/vfs_cache_pressure
100
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
710400
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
245000
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
80
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias
0
Current charging source: 0=Battery 1=USB 2=AC
/sys/class/power_supply/battery/charging_source
1
Current battery capacity
/sys/class/power_supply/battery/capacity
100
/sys/class/power_supply/battery/health
Good
----Current Battery Temp----
95 F / 35 C
----End of Battery Temp----
----ROM Version----
Linux version 2.6.29-DecaFuctCFS-dirty-2a66c604 ([email protected]) (gcc versio
n 4.4.0 (GCC) ) #2 PREEMPT Mon Sep 6 16:49:41 EDT 2010
----End of ROM Version ----
---CPU Time in each Frequency---
19200 0
122880 0
160000 0
245760 9146
480000 313
528000 24
604800 12
710400 9575
729600 0
748800 0
768000 0
787200 0
806400 0
825600 0
844800 0
864000 0
---End of CPU Time in each Frequency----
Click to expand...
Click to collapse
Strange. run batt-rm.sh, hit y.
reboot.
then flash it again.
If it persists, I'll go bug hunting; but this seems just erroneous.

Decad3nce said:
Strange. run batt-rm.sh, hit y.
reboot.
then flash it again.
If it persists, I'll go bug hunting; but this seems just erroneous.
Click to expand...
Click to collapse
Code:
sh-3.2# batt-rm.sh
batt-rm.sh
This tool will remove almost all traces of the Battery Tweak
Are you sure that you want to go through with this?[y/n]
y
y
/system/bin/batt-rm.sh: line 15: log: command not found

G2 2.3.4 OTA 1-Click temp-root

Thanks for the move orb3000
EDIT:
Apparently I can't post links either... what gives??? Going to have to do this the ghetto way I guess..
Anyway, I made a nice little .bat to temp-root the 2.3.4 OTA for the T-Mobile G2 (HTC Vision) for all you lazy people out there, or the people who are just tired of playing with the cmd (like myself).
It's on media fire... www(dot)mediafire(dot)com/?xwurdlpcw61oxiz
Just unzip and run "rootg2.bat"
It uses fre3vo, as it is the only method that currently works. If this for some reason does NOT work for you, edit rootg2.bat and change the address set to one of the following after a reboot
FAA90000 -end FFFFFFFF
10000000 -end 1FFFFFFF
20000000 -end 2FFFFFFF
30000000 -end 3FFFFFFF
F0000000 -end FFFFFFFF
E0000000 -end EFFFFFFF
Find one that works?? Great! Now you have a bat juuuuuust for you.
Long time lurker, first time poster, micro sized developer.

how to install
hi, i'm not very good with this. can you let me know how to install the g2root file on my g2? by the way, is this a permanent root? thx

tntx said:
hi, i'm not very good with this. can you let me know how to install the g2root file on my g2? by the way, is this a permanent root? thx
Click to expand...
Click to collapse
It says in the title this is a temporary root, not permanent. Check the [REF] Sticky is either General or Development for guides that will help you through the proces. DO NOT attempt root until you are sure you know what you are doing. READ and SEARCH!

Does anyone know of a way to temp-root on-device, without having to hook up to a PC?

After the message "daemon started successfully" the adb just hangs at that line, no crash, just doesn't advance any further. I can't input any commands either. I waited for over an hour to see if it would proceed, but not as such. Any ideas?

RebelScum75 said:
Does anyone know of a way to temp-root on-device, without having to hook up to a PC?
Click to expand...
Click to collapse
Hi!
I know that there is none
Have fun - Guhl

will this also work for the desire z ?

no dude ive been looking forever "finally had a reason to root the darn thing but i dont think there is one at least not that i have found--i work for verizon now anyways left my tmo--lol-----

dianlb50 said:
will this also work for the desire z ?
Click to expand...
Click to collapse
yes, basically same phone

Did this work for anyone?
Sent from my T-Mobile G2 using XDA App

I'm having issues getting this to work. I have tried the various addresses with no solid confirmation of whether it worked or not, aside from running the app "Root Check" or attempting to use an app that requires root, and finding that the phone is indeed, not rooted.
The results vary however at best, the process appears to have gone through smoothly. Daemon was successful, it successfully locates the region, and finally successfully dismounts and and remounts, which leaves us at the stage where it says press any key to continue.
Are there additional steps? What conditions must be met in order for this to work other than turning on debugging mode? Must the usb cord remain connected? Does the temp root end once the cord is unplugged? The guide above didn't exactly give any clear cut step-by-step directions and so I am feeling as if I'm not doing something because the guide doesn't mention it.
Can someone who has successfully temp-rooted their G2 v2.3.4 post a list of steps needed from start to finish? Example:
1) Enable USB debugging on phone.
2) Plug phone into computer via USB cord.
3) Unzip g2root.zip into a folder of your choice.
4) Run g2root.bat.
5) If successful, you will see (fill in the blank)
6) If successful, go to step 7, if unsuccessful, reboot computer/phone and retry step 1
Something like the above direct would be extremely useful to a few of us. Thanks!
-HobbesG2

Hello, I think this is my first post over here.
enable usb debugging on the phone
Plug phone into computer via USB
kill adb if it is already running:
Code:
./adb kill-server
start adb server as root:
Code:
sudo ./adb start-server
sample output:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Code:
./adb wait-for-device
and wait for this command to exit
Code:
./adb push /PUT/PATH/TO/G2ROOT/HERE/fre3vo /data/local/tmp
sample output:
Code:
218 KB/s (9796 bytes in 0.043s)
Code:
./adb -d shell chmod 777 /data/local/tmp/fre3vo
Code:
./adb -d shell /data/local/tmp/fre3vo -debug -start fb040000 -end FFFFFFFF
sample output:
Code:
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 2fd00000
smem_len: 300000
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Frame Buffer handle: 4
Buffer offset: 002ee000
Buffer size: 8192
Scanning region fb040000...
Scanning region fb130000...
Scanning region fb220000...
Scanning region fb310000...
Scanning region fb400000...
Scanning region fb4f0000...
Scanning region fb5e0000...
Scanning region fb6d0000...
Scanning region fb7c0000...
Scanning region fb8b0000...
Scanning region fb9a0000...
Scanning region fba90000...
Potential exploit area found at address fbb54e00:1200.
Exploiting device...
Code:
adb wait-for-device
Code:
./adb -d remount
sample output:
Code:
remount succeeded
verify you have root:
Code:
./adb -d shell id
output:
Code:
uid=0(root) gid=0(root)

Or you could verify it worked by executing 'adb shell' and if you have a # prompt rather than $, it worked.
This will stick until you reboot. Unplugging the cable will not affect it (unless you're currently running the commands)
This is not exactly a true temp-root, as it just gives adb root access, but you should be able to remount /system as rw and push su and SuperUser.apk to the right places to get a proper temp-root.
-Nipqer

Nipqer said:
you should be able to remount /system as rw and push su and SuperUser.apk to the right places to get a proper temp-root.
Click to expand...
Click to collapse
could you please describe how to do that? where do i get these packages from?

Getting closer but still not quite there. The reason why I was not having confirmations before was because I was running the rootg2.bat file directly rather than doing it through the cmd prompt, aka Start --> Run --> [type cmd]. After having ran the .bat file via the cmd prompt, I was able to apply, and confirm via the steps that were mentioned.
Problem is, I'm still not exactly truly temp-rooted, as none of my apps that require root or are designed to check root, show me as rooted. Is this because superuser and/or busybox are not operating as if they are rooted due to something I'm not aware of?
I already have the latest Superuser/Elite and BusyBox installed onto my phone via the Market. Do I have to push them into a specific folder that simply installing them from market wont do automatically?
Any thoughts?
After I get this nailed down, I will write a comprehensive explaination for others to do this as well.

Here is a true temp-root which works with fre3vo.
Just read the readme file.
-Nipqer

any update on this one?
i hope this makes rooting easier...

Nipqer said:
Here is a true temp-root which works with fre3vo.
Just read the readme file.
-Nipqer
Click to expand...
Click to collapse
I see this method listed for the Sensation, has it been proven to work for G2, stock OTA 2.3.4?

Wondering the same.

If you are running 2.3.x, and use fre3vo, then run that zip I posted, you will have proper temp-root.
It will stick until a reboot, but then you can just redo everything.
Yes it's proven to work.
-Nipqer

CM7 MAC Address Fix

I could not post directly in the development thread as I joined simply to share my solution. If anyone can confirm and prepare a better guide please post to CM7 thread by whistelstop.
You will need your factory mac address.
MAC Addresses all being the same is due to the nvs_map.bin file required by the tiwlan driver. dmseg driver will tell you it is looking for it and defaulting mac address.
I am running CM7 mileage will vary in stock rom.
http://www.omappedia.org/wiki/Porting_MCP_WLAN_to_Android#TxBiP_Calibration
I used the calibration instructions in terminal emulator on cm7 Kindle as "su"
#wlan_cu –b
# / w p 1 l 2 f 2
# / t b v 21
# / t b t 1 0 0 0 0 0 0 0
#/ q
New nvs_map.bin file will be ceated in /data/misc/wifi/
#cp /data/misc/wifi/nvs_map.bin to /sdcard/nvs_map.bin
connect to linux/windows host copy file to pc
open with hex editor I used xvi32 for windows.
link to my source for instruction for byte order and editing.
http://processors.wiki.ti.com/index...ce_(CLI)_User's_Guide#Editing_the_MAC_Address
Short instructions:
Editing the MAC Address
After the TX BIP runs, there is a new file called nvs_map.bin in Linux that contains the MAC address and the calibration data. The document SWAA044_NVS_INI_File_Functions_AN.pdf contains the format of the NVS file. If MAC address fields are manually edited with a hex editor, the byte order should be low byte first, followed by the high byte:
MAC address low register (offset 0x01 to 0x02)
MAC address LSB (offset 0x3 to 0x06)
MAC address high register (offset 0x08 to 0x09)
MAC address MSB (offset 0x0A to 0x0D)
The MAC address LSB and MAC address MSB, respectively, are shown in bold in the
following code for 08:00:28:12:34:56:
0000: 01 6d 54 56 34 12 28 01 71 54 00 08
For 11:22:33:44:55:66:
0000: 01 6d 54 66 55 44 33 01 71 54 22 11 00 00
Using a hex editor, you should change the bold numbers to the MAC address you
want to use.
Be careful about byte order and look closely at examples.
Good Luck
Please confirm instructions yourself and use at your own risk

Just tried that and it worked beautifully!
Thanks for that - great find!

TheKid2 said:
I could not post directly in the development thread as I joined simply to share my solution. If anyone can confirm and prepare a better guide please post to CM7 thread by whistelstop.
You will need your factory mac address.
MAC Addresses all being the same is due to the nvs_map.bin file required by the tiwlan driver. dmseg driver will tell you it is looking for it and defaulting mac address.
I am running CM7 mileage will vary in stock rom.
As I can not post links you will need to google my text and find correct link (noob)
maybe a moderator can fix for me.
######.omappedia.org/wiki/Porting_MCP_WLAN_to_Android#TxBiP_Calibration
I used the calibration instructions in terminal as "su"
#wlan_cu –b
# / w p 1 l 2 f 2
# / t b v 21
# / t b t 1 0 0 0 0 0 0 0
#/ q
New nvs_map.bin file will be ceated in /data/misc/wifi/
#cp /data/misc/wifi/nvs_map.bin to /sdcard/nvs_map.bin
connect to linux/windows host copy file to pc
open with hex editor I used xvi32 for windows.
link to my source for instruction for byte order and editing.
##processors.wiki.ti.com/index.php/OMAP35x_Wireless_Connectivity_WL1271_Command_Line_Interface_(CLI)_User%27s_Guide#Editing_the_MAC_Address
Short instructions:
Editing the MAC Address
After the TX BIP runs, there is a new file called nvs_map.bin in Linux that contains the MAC address and the calibration data. The document SWAA044_NVS_INI_File_Functions_AN.pdf contains the format of the NVS file. If MAC address fields are manually edited with a hex editor, the byte order should be low byte first, followed by the high byte:
MAC address low register (offset 0x01 to 0x02)
MAC address LSB (offset 0x3 to 0x06)
MAC address high register (offset 0x08 to 0x09)
MAC address MSB (offset 0x0A to 0x0D)
The MAC address LSB and MAC address MSB, respectively, are shown in bold in the
following code for 08:00:28:12:34:56:
0000: 01 6d 54 56 34 12 28 01 71 54 00 08
For 11:22:33:44:55:66:
0000: 01 6d 54 66 55 44 33 01 71 54 22 11 00 00
Using a hex editor, you should change the bold numbers to the MAC address you
want to use.
Be careful about byte order and look closely at examples.
Good Luck
Please confirm instructions yourself and use at your own risk
Click to expand...
Click to collapse
I'll verify tomorrow. Thanks for taking the time to help run this to ground and get a workaround.

** Deleted **
For new driver only ....

so next cm7 build will get the fix
right?

As it was my first post forum would not allow me to post links I am hoping someone will clean up solution and add to development thread.

whistlestop said:
I'll verify tomorrow. Thanks for taking the time to help run this to ground and get a workaround.
Click to expand...
Click to collapse
love this rom , I have four of these running on my router now with original factory mac addresses, Thank You for your work. I know from personal experience hours and hours can just disappear when you get involved with a project of this type.

Is there a way to get the factory MAC address while still in CM7 or do I have to load the stock ROM to get it and then go back to CM7?

I have not found am method other than loading stock software back on device.
If you only have one kindle on your network you most likely will never have a problem.
If you had more than one running cm7 you could have router issues as they all were reporting same mac address. You will not have any issues unless another cm7 kindle shows up on the same wireless access point as yours.

Unless you have a router log or something with your former mac address, I think you have to reload stock to find it. Thats what I did anyway.
Thanks to the OP for posting this; worked like a charm!

direct editing
could we use a hex editor to change the local file on the kindle?
I spotted one at the market place, and combined with SU privileges it might get the job done.

jfb9301 said:
could we use a hex editor to change the local file on the kindle?
I spotted one at the market place, and combined with SU privileges it might get the job done.
Click to expand...
Click to collapse
any hex editor should work. I am so use to using laptop still adjusting to touch keyboard.

Hopefully better instructions
having just stumbled through to OPs instructions (hats off to the OP for finding this). Successfully I might add, I thought I'd write up a hopefully more clear method of achieving this.
As I have had difficulty with the adb.exe command (connection issues, probably from a dodgy connection if I have too many USB devices plugged in) I chose to use applications local to my Kindle itself for as much as I could.
Apps:
adb.exe (the one that came with Kindle_Fire_Utility worked for me) grab a copy of this useful tool here kindle fire utility thread
Root explorer from the android market android market link
HexEditor android market link
Kindle fire
Computer
Data:
Your original MAC address - this might suck to get, as you will have to get it from your Kindle booted to stock Kindle Fire Firmware. I had installed CM7 using TWRP, so I booted to TWRP did a backup of my current CM7 OS, did a restore to the KF OS, booted to stock(rooted) opened up settings/device and nabbed that pesky MAC address, rebooted to TWRP, restored CM7.
Instructions:
connect KF to computer
open the computers start menu and select run, type CMD in the box
navigate to kindle_fire_utility/tools
type command: adb shell
adb should open and start communication with you Kindle
within the shell you have to type the following (be mindful of the spaces as they are important, ignore the #s as they are to make this post put the spaces in):
#wlan_cu –b
# / w p 1 l 2 f 2
# / t b v 21
# / t b t 1 0 0 0 0 0 0 0
#/ q
now use ctrl-c to end ADB, and command:
exit
to close cmd, you are done with windows.
now the kindle part...
open root explorer
/data/misc/wifi
select nvs_map.bin and copy to the sdcard, I made two copies and named the second nvs_map.bin.bak just in case things got screwed from this point on.
exit root explorer
open HexEditor
open /sdcard/nvs_map.bin and change the digits in the very first line of the file
(example from OPs post)
following code for 08:00:28:12:34:56:
0000: 01 6d 54 56 34 12 28 01 71 54 00 08 00 00
For 11:22:33:44:55:66:
0000: 01 6d 54 66 55 44 33 01 71 54 22 11 00 00
save the file
use root explorer to copy it back to /data/misc/wifi
long press the file and set permissions to RW-RW-RW-
Reboot.....
Done
---------- Post added at 04:09 PM ---------- Previous post was at 03:11 PM ----------
I confimed MAC address using my wifi router (DDWRT) is awesome.
Does anyone know a way to get CM7 to cough up the kindles MAC address?

I'm having some difficulties with these instructions. I've tried with the WiFi setting from CM7 on and off, and also with the full instructions from the omappedia.org site, and it's still not working. A quick Google didn't come up with anything.
This is my output (from an ADB shell, obviously):
Code:
# insmod /system/etc/wifi/tiwlan_drv.ko
# start wlan_loader
# ifconfig tiwlan0 up
# wlan_cu –b
ERROR - IpcWpa_Sockets_Open - can't connect the socket
******************************************************
Connection to supplicant failed
******************************************************
ERROR - IPC_STA_Private_Send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 800003, res = -1, errno = 19)
ERROR - driver is not in RUNNING state!
user_main, start
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
/ D S
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Driver> Start, sTop, stAtus
ERROR - IPC_STA_Private_Send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8000001, res = -1, errno = 19)
ERROR - Failed to start driver!
I have tried it with and without the first three lines (going straight to wlan_cu -b), and the / D S line is an unsuccessful attempt to start the driver. An attempt to just push through all the commands gives an error message with every line, and does not create the nvs_map.bin file.
Anyone have any ideas?

I had wifi on, and did not run the first 3 commands. No thoughts beyond that.
For reference, I am on the latest CM7 with the updated video stuff by wistlestop (I think)

csyria6919 & jfb9301,
I can confirm, you'll get the errors csyria6919 gets with WiFi OFF - turn on Wifi on the KF and then the ADB commands work without errors.
VERY NICE Fix - +1 thanks to TheKid2!
~J

csyria6919 said:
I'm having some difficulties with these instructions. I've tried with the WiFi setting from CM7 on and off, and also with the full instructions from the omappedia.org site, and it's still not working. A quick Google didn't come up with anything.
This is my output (from an ADB shell, obviously):
Code:
# insmod /system/etc/wifi/tiwlan_drv.ko
# start wlan_loader
# ifconfig tiwlan0 up
# wlan_cu –b
ERROR - IpcWpa_Sockets_Open - can't connect the socket
******************************************************
Connection to supplicant failed
******************************************************
ERROR - IPC_STA_Private_Send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 800003, res = -1, errno = 19)
ERROR - driver is not in RUNNING state!
user_main, start
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
/ D S
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Driver> Start, sTop, stAtus
ERROR - IPC_STA_Private_Send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8000001, res = -1, errno = 19)
ERROR - Failed to start driver!
I have tried it with and without the first three lines (going straight to wlan_cu -b), and the / D S line is an unsuccessful attempt to start the driver. An attempt to just push through all the commands gives an error message with every line, and does not create the nvs_map.bin file.
Anyone have any ideas?
Click to expand...
Click to collapse
Hi,
I only used docs as reference. Wifi should be turned on on Kindle. I issued all command from terminal emulator running on Kindle. Hope you have found solution that works for you. Also there are spaces in between just about every letter in the commands.
Let us know if you were successful.

Hello,
I am hearing about cpu utilization issue in another thread. http://forum.xda-developers.com/showthread.php?t=1411895
Can anyone running cm7 and using nvs_map file check utilization connected to secure network. My installation is not exhibiting cpu behavior stuck at 1008 that is being described. Wondering if using calibration file is actually improving performance.
As a side not same file can be used in the current build of ics they are developing in that thread.
cpu scaling issue does not show up on unsecured net. Need a few people to sound off here to determine if my kindles are the only ones not having scaling issue.
Thanks

Is there somewhere in cm7 to check cpu utilization, I looked everywhere ended up downloading task manager from market. Seems like task manager, and performance monitor should be in there somewhere. I am sure I am overlooking something simple.
Thanks

TheKid2 said:
Is there somewhere in cm7 to check cpu utilization, I looked everywhere ended up downloading task manager from market. Seems like task manager, and performance monitor should be in there somewhere. I am sure I am overlooking something simple.
Thanks
Click to expand...
Click to collapse
I used your guide, got CM7 on my device and will check that once I get home.
To check CPU utilization I'd recommend CPU Spy https://market.android.com/details?id=com.bvalosek.cpuspy

Tcpdump

Does anyone know how to disable tcpdump on the latest MIUI 11 rom with out root? It creates quite large log files quite quickly.

The other day, noticed that this guy is doing it:
Code:
system 10516 2161 0 21:58:31 ? 00:00:00 com.huaqin.diaglogger
root 10541 1 1 21:58:31 ? 00:00:05 tcpdump -i any -W 2 -C 2 -s 134 -w /sdcard/MIUI/debug_log/common/tcpdump.pcap
try to disable/uninstall that app and see if that resolves it. In my case made phone run faster..

stormy1777 said:
The other day, noticed that this guy is doing it:
Code:
system 10516 2161 0 21:58:31 ? 00:00:00 com.huaqin.diaglogger
root 10541 1 1 21:58:31 ? 00:00:05 tcpdump -i any -W 2 -C 2 -s 134 -w /sdcard/MIUI/debug_log/common/tcpdump.pcap
try to disable/uninstall that app and see if that resolves it. In my case made phone run faster..
Click to expand...
Click to collapse
Thanks man, I got rid of that but can't shift the finddevice logs and unfortunately you can't uninstall it or the device goes into a bootloop.

not sure what you mean 'shift' the logs, on my device, the com.xiaomi.finddevice is in DISABLED state, and no bootloop, maybe if you UNINSTALL it goes into that loop, then managed to delete the files in that location..