Help!!
I just insalled the latest xubuntu on one of my pcs (gutsy gibbon)
trying to get it to connect to the internet thru my uni's wmodem app by usb.
ran
sudo -i
modprobe usbserial vendor=0xbb4 product=0x0cf
already did mkdev for ttyUSB0
dmesg shows device connected to ttyUSB0
echo "ATDT*99#" > /dev/ttyUSB0
causes connection light to go on in wmodem app on uni
but...
when I run wvdialconf I get:
ttyUSB0<*1> ATQ0 V1 E1 .. failed with 2400 baud, next try;9600 baud
ttyUSB0<*1> ATQ0 V1 E1 .. failed with 9600 baud, next try;115200 baud
ttyUSB0<*1> ATQ0 V1 E1 .. failed with 2400 baud, giving up.
Sorry, no modem detected! Is it in use by another program?
Did you configure it properly with setserial?
what do I have 2 do?
oh yeah, tried making 'tmobile' in /etc/ppp/peers
contains:
----
hide-password
noauth
connect "usr/sbin/chat -v -f /etc/chatscripts/tmobile"
debug
ttyUSB0
115200
defaultroute
noipdefault
user "tmobile"
remotename tmobile
ipparam tmobile
usepeerdns
---
and in /etc/chatscripts/tmobile
---
# ispauth PAP
# abortstring
ABORT BUSY 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED
# modeminit
'' "ATDT*99#"
# ispnumber
# OK-AT-OK "ATDT*99#"
# ispconnect
CONNECT \d\c
# prelogin
# ispname
# isppassword
# postlogin
-----
with
----
"tmobile" * "one2one"
----
in my chap-secrets
then tried using
pon tmobile
but light does not come on
running plog gives
last 2 lines as
chat[4923]: send (ATDT*99#^m)
chat[4923]: expect (CONNECT)
please can someone help as I'm not a linux xpert and the only way I have of using the internet is thru my uni.
ps uni works fine with my gf's laptop under XP
Similar problems for me
I have tried a very similar config with my Vario II (Hermes) with no avail. I have this working fine in XP & Vista x32 & x64.
I am also running Ubuntu 7.10 Gutsy. It would be great if someone could help on this issue as I suspect many people are trying to do this at the minute.
Dz
ok, was just being a luser
for some reason u have to use 'modprobe ipaq' instead of 'modprobe usbserial' then it works
Yipeeeeeeeeeeeeeeeeeeeeeeee!!!!
Hi
I've got a question. How to connect blade (on 2.2 froyo) to ad-hoc wirless?
Probably must change a "wpa_supplicant" file (and probably other's simmilar), but i don't know how
This is my "wpa_supplicant" (viewed by normal notepad) :
Code:
# Note: All file paths in this configuration file should use full (absolute,
# not relative to working directory) path in order to allow working directory
# to be changed. This can happen if wpa_supplicant is run in the background.
# Whether to allow wpa_supplicant to update (overwrite) configuration
#
# This option can be used to allow wpa_supplicant to overwrite configuration
# file whenever configuration is changed (e.g., new network block is added with
# wpa_cli or wpa_gui, or a password is changed). This is required for
# wpa_cli/wpa_gui to be able to store the configuration changes permanently.
# Please note that overwriting configuration file will remove the comments from
# it.
update_config=1
# global configuration (shared by all network blocks)
#
# Parameters for the control interface. If this is specified, wpa_supplicant
# will open a control interface that is available for external programs to
# manage wpa_supplicant. The meaning of this string depends on which control
# interface mechanism is used. For all cases, the existance of this parameter
# in configuration is used to determine whether the control interface is
# enabled.
#
# For UNIX domain sockets (default on Linux and BSD): This is a directory that
# will be created for UNIX domain sockets for listening to requests from
# external programs (CLI/GUI, etc.) for status information and configuration.
# The socket file will be named based on the interface name, so multiple
# wpa_supplicant processes can be run at the same time if more than one
# interface is used.
# /var/run/wpa_supplicant is the recommended directory for sockets and by
# default, wpa_cli will use it when trying to connect with wpa_supplicant.
#
# Access control for the control interface can be configured by setting the
# directory to allow only members of a group to use sockets. This way, it is
# possible to run wpa_supplicant as root (since it needs to change network
# configuration and open raw sockets) and still allow GUI/CLI components to be
# run as non-root users. However, since the control interface can be used to
# change the network configuration, this access needs to be protected in many
# cases. By default, wpa_supplicant is configured to use gid 0 (root). If you
# want to allow non-root users to use the control interface, add a new group
# and change this value to match with that group. Add users that should have
# control interface access to this group. If this variable is commented out or
# not included in the configuration file, group will not be changed from the
# value it got by default when the directory or socket was created.
#
# When configuring both the directory and group, use following format:
# DIR=/var/run/wpa_supplicant GROUP=wheel
# DIR=/var/run/wpa_supplicant GROUP=0
# (group can be either group name or gid)
#
ctrl_interface=DIR=/data/misc/wifi/wpa_supplicant GROUP=wifi
# IEEE 802.1X/EAPOL version
# wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines
# EAPOL version 2. However, there are many APs that do not handle the new
# version number correctly (they seem to drop the frames completely). In order
# to make wpa_supplicant interoperate with these APs, the version number is set
# to 1 by default. This configuration value can be used to set it to the new
# version (2).
# eapol_version=1
# AP scanning/selection
# By default, wpa_supplicant requests driver to perform AP scanning and then
# uses the scan results to select a suitable AP. Another alternative is to
# allow the driver to take care of AP scanning and selection and use
# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
# information from the driver.
# 1: wpa_supplicant initiates scanning and AP selection
# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
# parameters (e.g., WPA IE generation); this mode can also be used with
# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
# APs (i.e., external program needs to control association). This mode must
# also be used when using wired Ethernet drivers.
# 2: like 0, but associate with APs using security policy and SSID (but not
# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
# enable operation with hidden SSIDs and optimized roaming; in this mode,
# the network blocks in the configuration file are tried one by one until
# the driver reports successful association; each network block should have
# explicit security policy (i.e., only one option in the lists) for
# key_mgmt, pairwise, group, proto variables
# ap_scan=1
# EAP fast re-authentication
# By default, fast re-authentication is enabled for all EAP methods that
# support it. This variable can be used to disable fast re-authentication.
# Normally, there is no need to disable this.
# fast_reauth=1
# Driver interface parameters
# This field can be used to configure arbitrary driver interace parameters. The
# format is specific to the selected driver interface. This field is not used
# in most cases.
#driver_param="field=value"
# Maximum lifetime for PMKSA in seconds; default 43200
#dot11RSNAConfigPMKLifetime=43200
# Threshold for reauthentication (percentage of PMK lifetime); default 70
#dot11RSNAConfigPMKReauthThreshold=70
# Timeout for security association negotiation in seconds; default 60
#dot11RSNAConfigSATimeout=60
Sorry for my bad english.
I very needed internet in ad-hoc mode. So, anybody help me ?
wifi ad hoc is not supported by zte blade official rom even by changing wpa_supplicant this will crash your wifi.............
maybe the modded supplicant is not compatible with stock rom..........
change your rom to any cm7 and than change its wpa_supplicant to /system/bin than only the wifi adhoc will work
We are trying to determine whether IHOP international edition might brick Spanish (Movistar?) users. NO, please DO NOT flash the new unlockable bootloader yet.
First, I need you to root, as described here or using Gingerbreak or any other method.
Second, we need to know the contents of the
Code:
/sys/firmware/fuse/ReservedOdm
fuse, which you can "cat" in adb shell (after 'su') or open with Root Explorer.
Third, the following files would also be very useful:
/default.prop
/system/default.prop
/system/build.prop
/osh/etc/oshwt-version.txt
Finally, we need to know the signing keys from your build. AS root:
Code:
busybox strings /dev/block/mmcblk0p11 | busybox grep Motorola
(If you get a busybox error, PM me immediately and I will provide a better busybox and update the instructions appropriately.)
PS. It would also help to know your memory layout. If you could turn off your phone and adb this command:
Code:
adb wait-for-device shell "dmesg | /usr/bin/head -100"
Then, turn on your phone, wait, and pastie.org or attach the result in your zip on this post, that would be great.
Use the preinstall method to root. FYI, the Gingrebreak method wouldn't work on mine (Movistar Spain Atrix).
Btw, I've got a full system dump I made before the brick (except data & cache).
So I'll extract the requested files later and share them here with you.
FYI, Pzyduck from M3 managed to obtain the stock sbf for Retail ES, it's published in the Atrix firmware superthread just in case you want to inspect some more files. See here
Here's the info from my phone, dumped by MSU (MST.txt):
07/13/11 09:13:28 Technology: UMTS 3G
07/13/11 09:13:28 Flex File: UCAOLYPB1B8EU049.0R
07/13/11 09:13:28 Software: OLYEM_U4_4.3.3
07/13/11 09:13:28 PRI:
07/13/11 09:13:28 Kjava:
07/13/11 09:13:28 BootLoader: 0007
07/13/11 09:13:28 LangPack:
07/13/11 09:13:28 Internal Carrier Name: N / A
07/13/11 09:13:28 Carrier Name: N / A
07/13/11 09:13:28 Model Number: N / A
07/13/11 09:13:28 AP Setup Flex:
07/13/11 09:13:28 AP Resource Flex:
07/13/11 09:13:28 AP Logo Flex:
07/13/11 09:13:28 AP Secure Setup Flex:
07/13/11 09:13:28 AP ROFS:
07/13/11 09:13:28 AP ROFSExtension:
07/13/11 09:13:28 AP Flex: GAS_EMEA_USAOLYPRTES_P029
Is the BootLoader: 0007 relevant here?
EDIT: I've attached the files I could get.
webtop version is : OSHWT_U1_6.61.18
Thanks adlx, good luck
Big thanks to both of you!
I looked at the signing keys in that SBF but they looked the same as the other international ones =/ And if your ReservedOdm WAS different than all the other internationals, (and in such a way that could brick you by using their bootloader) I would expect Spanish Movistar users to have (big) problems flashing a LOT of .sbf files!
So, quick question: had you flashed any other, non-Movistar .sbf successfully, before your brick? If so, it is probably not worth bothering nothize to disassemble the bootloader in the Movistar .sbf. But then it is even more a mystery how you bricked =( Let us know if you find another Movistar Atrix...
eval- said:
So, quick question: had you flashed any other, non-Movistar .sbf successfully, before your brick? If so, it is probably not worth bothering nothize to disassemble the bootloader in the Movistar .sbf. But then it is even more a mystery how you bricked =( Let us know if you find another Movistar Atrix...
Click to expand...
Click to collapse
Nop, I didn't flash any sbf before the IHOP one.
This is not the first sbf I flash (as I owe 5 Motorola phones, and one, the Defy I have had to reflash it quite a lot), but after updating the Motorola drivers and updating also RSD to 5.3.1 yes, it was the first sbf I flashed on a phone...
Actually to me it is a mistery too how it could have bricked. I have never seen that in RSD lite before. Now I'm pretty much afraid to flash any sbf on any phone, would the problem be in my computer (rsd, drivers,...). Don't want to screw another phone! And I don't know how I could safely "test" my setup, without risking another brick.
Well, ideal is you have a person with an Atrix from Movistar so we can look at the ReservedOdm fuse. If it is different, we check out the Movistar bootloader. If not, then I would say we still want to try IHOP on another Movistar before declaring it impossible. Using a PC which has successfully flashed the normal Movistar .sbf to the phone. Hopefully this friend would already have an insurance policy on their phone... wish I had more ideas but yes, it's a mystery. First time I hear of no screen output at all especially if the LED still lights up. Do you have the RSD logs from the day of flash? Though I suspect they say everything went OK, it is still worth to check... Probably in AppData/Local, or?
adlx.xda said:
Nop, I didn't flash any sbf before the IHOP one.
Actually to me it is a mistery too how it could have bricked. I have never seen that in RSD lite before. Now I'm pretty much afraid to flash any sbf on any phone, would the problem be in my computer (rsd, drivers,...). Don't want to screw another phone! And I don't know how I could safely "test" my setup, without risking another brick.
Click to expand...
Click to collapse
eval- said:
Well, ideal is you have a person with an Atrix from Movistar so we can look at the ReservedOdm fuse. If it is different, we check out the Movistar bootloader. If not, then I would say we still want to try IHOP on another Movistar before declaring it impossible. Using a PC which has successfully flashed the normal Movistar .sbf to the phone. Hopefully this friend would already have an insurance policy on their phone... wish I had more ideas but yes, it's a mystery. First time I hear of no screen output at all especially if the LED still lights up. Do you have the RSD logs from the day of flash? Though I suspect they say everything went OK, it is still worth to check... Probably in AppData/Local, or?
Click to expand...
Click to collapse
Hopefully I will get another one, so at least I should be able to get the commands output on it . Don't know yet if I'll have the b*lls to flash it again LOL.
I don't think it's just the screen that isn't working, because I tried to place it in RSD Mode (power + vol up IIRC), and RSD wouldn't see it.
Actually I can get the led light green in very rare conditions, like half-plugging the power-outlet usb cord in the Atrix. By half plugging I mean if I don't plug it totally inside, but I just "start" to plug it. IIRC, it's when I have the battery pulled. The green led lights up, then when I finish to plug the usb cord the led turns off again. That's not much...
RSD log of the failed flash
Here is the log of my failed flash:
Code:
11:00:54, July 14, 2011
Line: 2085
ERROR: Phone[0000]: Error switching phone to BP Pass through mode
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
11:01:05, July 14, 2011
Line: 768
ERROR: Phone[0000]: The "Motorola_Flash" Interface could not be found.
The super-file is not secure and for re-flash;
the phone needs a super-file that is not secure and for reflash.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 0
11:01:05, July 14, 2011
Line: 610
ERROR: Flash failure: Phone[0000]: Error switching phone to BP Pass through mode (Error Code: be),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=257
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
I've also uploaded two screnshots of RSD Lite at the time of the error, here.
Hi there!
On August 13th I received my Atrix 4G from Movistar and went out on holidays, I'd just arrived now and I would like to help.
I have a brand new movistar atrix 4G
System version: 4.4.33.MB860.Retail.en.ES
Android version: 2.2.2
Base band version: N_01.95.00R
Webtop version: OSHWT_U1_6.61.18
I'd read I must be root so I'm going to root the phone and please tell me if you still need my help, since the date of this post its a bit old...
PS: Im going to use OneClick Method to root the phone, it seems pretty easy and fast.
Bah, SuperOneClick fails, but this other method works like a charm!!
briefmobile.com/motorola-atrix-4g-root
I'm going to backup my apps with Titanium Backup and make the test you specified on post #1
I use /preinstall/dosu to get root access in adb, if you think I'm doing bad, please tell me how to get root (su doen't seems to work)
Content of /sys/firmware/fuse/ReservedOdm
Code:
c:\Root>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# whoami
whoami
root
[email protected]:/# less /sys/firmware/fuse/ReservedOdm
less /sys/firmware/fuse/ReservedOdm
WARNING: terminal is not fully functional
/sys/firmware/fuse/ReservedOdm (press RETURN)
[B]20000000200000000[/B]
/sys/firmware/fuse/ReservedOdm (END)
/default.prop
Code:
[email protected]:/# cat /default.prop
cat /default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
EXTERNAL_STORAGE_MOUNT=/mnt/sdcard
/system/default.prop
Code:
[email protected]:/# cat /system/default.prop
cat /system/default.prop
ro.build.config.version.app=GAS_EMEA_USAOLYPRTES_A002
ro.build.config.version.media=GAS_EMEA_USAOLYPRTEU_M001
ro.mot.vvm_enable=1
ro.mot.datamanager.34568=true
ro.mot.nat_roaming_enable=1
umts.apn_authentication.enable=ALL
ro.product.drm.sd.enable=1
persist.sys.timezone=Europe/Madrid
ro.product.drm.fl.enable=1
ro.fota.enable=1
ro.product.drm.cd.enable=1
ro.build.config.version=GAS_EMEA_USAOLYPRTES_P029
ro.build.bp.config.version=
/system/build.prop
Code:
[email protected]:/# cat /system/build.prop
cat /system/build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=OLYEM_U4_4.3.3
ro.build.display.id=OLYEM_U4_4.3.3
ro.build.version.incremental=7977139
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.2
ro.build.date=Mon Jun 13 22:02:19 CST 2011
ro.build.date.utc=1307973739
ro.build.type=user
ro.build.user=xphk86
ro.build.host=zch68lnxdroid45
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=MB860
ro.product.model.internal=MB860
ro.product.brand=MOTO
ro.product.name=MB860_RTES
ro.product.device=olympus
ro.product.board=olympus
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=es
ro.product.locale.region=ES
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=olyem
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=olympus-user 2.2.2 OLYEM_U4_4.3.3 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/MB860_RTES/olympus/olympus:2.2.2/OLYEM_U4_4.3.3/797713
9:user/ota-rel-keys,release-keys
# end build properties
#BEGIN ikolympus-145 ndkj78 04/29/10 add properties for RIL
rild.libpath=/system/lib/libmoto_ril.so
#ikolymp-874 increment channels to support EFEM
persist.ril.mux.noofchannels=9
persist.ril.mux.ttydevice=/dev/ttyHS3
#Begin IKOLYMP-2372 jqc837 31.aug.10 Short music file set as ringtone does not play in loop when receiving incoming call
#Begin IKOLYMP-425 jqc837 31.aug.10 ro.cdma.home.operator.numeric should not be set
ro.telephony.call_ring.multiple=false
#End IKOLYMP-2372 IKOLYMP-425
#added property for modem ikolympus-203
persist.ril.modem.ttydevice=/dev/ttySPI0
#added property for default RIL mode to be UMTS ikolymp2180
persist.ril.modem.mode=2
#IKOLYMP-4257 add feature GENERIC_OEM_HOOK flag
#IKOLYMP-4894 add feature MUX_PANIC_NOTIF flag
#IKOLYMP-5747 add feature BDTSE_FOR_DTMF flag
#IKOLYMP-7714 Remove feature BDTSE_FOR_DTMF. Revert to DTSE for DTMF
#IKOLYMP-8033 Restore BDTSE_FOR_DTMF. Remove GENERIC_OEM_HOOK (no longer used)
persist.ril.features=0x24
#IKOLYMP-9894 Increase the PPP max failure threshold to 12
#IKOLYMP-10006 Increase the PPP max failure threshold to 16
persist.ril.pppd.start.fail.max=16
#end
#IKOLYMP-9157 libgps send_rds retry number+1
persist.libgps.send.rds.retry=4
ro.hdmi.mirror.enable=false
ro.hdmi.default.app=
hw.overlay.path.config=
# temporary enable AT&T NSUI feature from system prop.
# This should be removed once Flex is enabled in Olympus.
ro.mot.FTR.NSUI=false
# for larger screen support
# 3.75" WVGA == 248dpi
# 4.0" qHD == 275dpi
ro.sf.lcd_density=240
dalvik.vm.heapsize=32m
# Enable FP sensor
ro.mot.hw.fingerprint.enable=1
# required for UDD backup tcmd
ro.mot.hw.calibratedImager=1
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
#For enabling Wispr Feature
#disable att wifi hotspot, IKOLYEM-254
ro.mot.wifi.hotspot=0
# To enable Google Froyo Tethering (USB & WIFI hotspot)
ro.tether.denied=false
# To set wifi (AP) driver's firmware path
ro.wifi-ap.fw-path=/system/etc/firmware/wifi/sdio-g-cdc-roml-reclaim-wme-apsta-i
dsup-idauth.bin
# Enabling EONS feature IKOLYMP-1962
persist.cust.tel.eons=1
ro.opengles.version = 131072
# For docked touchpad keyboard map
android.keylayout.evfwd=/system/usr/keylayout/evfwd.kl
android.keychar.evfwd=/system/usr/keychars/evfwd.kcm.bin
# To send 70 touch events per second
windowsmgr.max_events_per_sec = 70
debug.mot.extwmlog=0
debug.mot.extamlog=0
#proximit sensor screen off delay
mot.proximity.delay=450
#proximit sensor disable touch distance
mot.proximity.distance=60
# Enable HAC support
ro.mot.hw.HAC=1
# BEGIN Motorola, w30250, 4-Nov-2010, IKOLYMP-6198 turn on entitlement check
# BEGIN Motorola, e13085, 9-Dec-2010, IKOLYHKTW-1 turn off entitlement check
ro.mot.entitlement_check=false
# END
# END
# The property "ro.camera.sound.forced" is defined by google.
# Use this property to decide whether camera shutter tone is forced: 1 forced; 0
not-forced.
# BEGIN Motorola, e7482c, 1-Dec-2010, IKOLYEM-76
ro.camera.sound.forced=1
# BEGIN Motorola, w30495 IKOLYMP-9553, add property to control maximum number of
hidden apps
ro.MAX_HIDDEN_APPS=50
# END
# BEGIN Motorola, e7482c IKOLYEM-486, add property to control if disable backgro
und data when making call
ro.mot.background_data.disabled=false
# BEGIN Motorola, w20919 IKOLYEM-993, add property to control if email auto conf
ig after skip the blur setting
ro.mot.auto.email=true
# END
# Enable APN authentication for a specific MCCMNC, "ALL" for all MCCMNC
umts.apn_authentication.enable=ALL
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=false
ro.default_usb_mode=0
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.2_r10
ro.config.sync=no
ro.browser.useragent=0
gsm.sim.mot.simswap=1
ro.config.sync=no
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.aud.hz=44100
ro.media.enc.hprof.aud.ch=2
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.aud.bps=128000
ro.media.enc.hprof.vid.bps=4000000
ro.media.enc.hprof.vid.width=1280
ro.media.enc.hprof.vid.height=720
ro.media.enc.hprof.codec.vid=h264
ro.media.enc.hprof.vid.fps=30
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientid=android-motorola
ro.url.legal=google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=google.com/intl/%s/mobile/android/basic/
privacy.html
ro.mot.hw.uaprof=uaprof.motorola.com/phoneconfig/motomb860/Profile/motomb
860emara.rdf
ro.build.version.full=Blur_Version.4.4.33.MB860.Retail.en.ES
ro.config.ringtone=Piano.ogg
ro.config.notification_sound=Kinetic_Bell.ogg
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.locationfeatures=1
ro.com.google.clientidbase.ms=android-motorola
/osh/etc/oshwt-version.txt (as I posted before)
Code:
[email protected]:/# cat /osh/etc/oshwt-version.txt
cat /osh/etc/oshwt-version.txt
OSHWT_U1_6.61.18
Finally, signing keys seems to fail. Right now I will PM eval-
Code:
[email protected]:/# busybox strings /dev/block/mmcblk0p11 | busybox grep Motorola
<trings /dev/block/mmcblk0p11 | busybox grep Motorola
strings: applet not found
Hope this helps, I'm afraid to brick my shinny new gadget and I'm anxious to replace webtop with a fully featured debian
Thanks man for your help giving us that info. I'll email Eval- and see if he can conclude something about it :-D
You're welcome! I hope this can help someway
I've PMed myself eval- several times but my sentbox appears empty and I don't know if I am spamming him or if he is receiving anything from me... :S
anyway, if I can do anything else, please, let me know.
Hey, sorry for the late reply I've been away for a bit...
malevoli said:
I use /preinstall/dosu to get root access in adb, if you think I'm doing bad, please tell me how to get root (su doen't seems to work)
Click to expand...
Click to collapse
Hmm I know this method (its my preinstall.img ) You have to /bin/mount -o remount,rw /system and then "cp /preinstall/su /system/bin/" in order to have 'su' AND you have to install Superuser.apk from the market or /preinstall...
malevoli said:
Finally, signing keys seems to fail. Right now I will PM eval-
Code:
[email protected]:/# busybox strings /dev/block/mmcblk0p11 | busybox grep Motorola
<trings /dev/block/mmcblk0p11 | busybox grep Motorola
strings: applet not found
Hope this helps, I'm afraid to brick my shinny new gadget and I'm anxious to replace webtop with a fully featured debian
Click to expand...
Click to collapse
This is not so important, it seems default busybox sucks and doesn't have strings, but I have seen the sigs in the ES .sbf and they look the same as other internationals.
malevoli said:
Content of /sys/firmware/fuse/ReservedOdm
Code:
[B]20000000200000000[/B]
/sys/firmware/fuse/ReservedOdm (END)
Click to expand...
Click to collapse
Interesting. This is perhaps the first international phone's ReservedOdm* I've seen that did not have 20002000200000000 or 30003000300000000 (pre-unlock, with the last 00000000 turned to 00004000 after unlock.) Would be cool to get some confirmation whether any other internationals have 20000000200000000 before doing any flashing or OTAs (as some AT&T Atrix did have 10000000100000000 from the factory.)
But, 'IHOP' Pudding should replace your previous bootloader, and IHOP shouldn't care if that fuse is blown (representing the second '2') and in fact will probably blow it if it's not blown. However, there *is* a 'backup' copy of fastboot on the device (in the space pre-mbr, alongside the primary copy) and I suppose by some means it could called during/after the flash?? This would seem a strange catch-22 (loading a backup bootloader that doesn't accept the current state) but perhaps it's possible.
We could potentially disassemble the Spanish .sbf fastboot and check whether it expects no fuse burned at the lower word of Odm1 (this is the same fuse word that bricked all the AT&T downgraders and users of Chinese .sbfs BTW.) So, not only would the fuse have to be burned (by the new bootloader being run as AFAIK flashing doesn't do this) you'd somehow have to run the old bootloader (meaning that backup and current are not the same? seems unlikely... and its doubtful that the old one expects a '0' but we should check) AND it would be crashing in a way that gives you no screen output (instead of 0x1000.) So I still suspect this was a freak mistake, and that not all Spanish users will brick from unlock. But I would still strongly recommend getting device insurance first!
*OK, some mainland china phones have 100010001... this is why their .sbf bricks all other international phones... as fastboot freaks out when it finds a '2' (let's say, it's really a blown fuse in the wrong position) on the phone it's been flashed to and drops to nvflash 0x1000...
Hi eval-
Now I am who is sorry for the late response
Almost everything you said sounds like chinese to me
So what's your advice? To assure the device and try to flash?
I don't know anyone who owns a atrix to make more tests...
Regards,
Angel
There is no solution?
I tried to assure my device, but when I tried was too late, spanish ppl have only 15 days after the adquisition of the mobile phone to make an assurance....
It's a true pity since in movistar webpage there is no link to any update. Shame on that company....
Requested data from Atrix 4G Movistar, Argentina :
I have Froyo 2.2.2 Stock rom, but rooted by gingerbreak. Movistar Argentina not have intention to upgrade to 2.3.x or 2.4 (or 4.0 ) for now.
Thanks in advance.
Code:
/ # cat /sys/firmware/fuse/ReservedOdm
20000000200000000
Code:
/ # cat /default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
EXTERNAL_STORAGE_MOUNT=/mnt/sdcard
Code:
/ # cat /system/default.prop
ro.build.config.version.app=GAS_LA_USAOLYPMOVLALA_A016
ro.build.config.date=Mon Jul 04 15:42:54 -0300 2011
ro.build.config.version.media=GAS_LA_USAOLYPMOVLALA_M001
ro.mot.carrier.ecc=0x390x310x310x000x310x310x320x00
ro.mot.vvm_enable=0
ro.gsm.sms.tp-vpf=2
ro.gsm.sms.tp-vp=255
ro.product.drm.fl.enable=1
ro.mot.force.tp.dcs.bits=1
ro.mot.wifi.hotspot2g=0
ro.build.config.version=GAS_LA_USAOLYPMOVLALA_P014
Code:
/ # cat /system/build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=OLYLA_U4_0.54.0_R05
ro.build.display.id=OLYLA_U4_0.54.0_R05
ro.build.version.incremental=7473195
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.2
ro.build.date=Thu Jun 8 13:24:51 BRT 2011
ro.build.date.utc=1307031891
ro.build.type=user
ro.build.user=wmb050
ro.build.host=zbr05lnxdroid07
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=MB860
ro.product.model.internal=MB860
ro.product.brand=MOTO
ro.product.name=MSTLA
ro.product.device=olympus
ro.product.board=olympus
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=es
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=olympus
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=olympus-user 2.2.2 OLYLA_U4_0.54.0_R05 7473195 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/MSTLA/olympus/olympus:2.2.2/OLYLA_U4_0.54.0_R05/7473195:user/ota-rel-keys,release-keys
# end build properties
#BEGIN ikolympus-145 ndkj78 04/29/10 add properties for RIL
rild.libpath=/system/lib/libmoto_ril.so
#ikolymp-874 increment channels to support EFEM
persist.ril.mux.noofchannels=9
persist.ril.mux.ttydevice=/dev/ttyHS3
#Begin IKOLYMP-2372 jqc837 31.aug.10 Short music file set as ringtone does not play in loop when receiving incoming call
#Begin IKOLYMP-425 jqc837 31.aug.10 ro.cdma.home.operator.numeric should not be set
ro.telephony.call_ring.multiple=false
#End IKOLYMP-2372 IKOLYMP-425
#added property for modem ikolympus-203
persist.ril.modem.ttydevice=/dev/ttySPI0
#added property for default RIL mode to be UMTS ikolymp2180
persist.ril.modem.mode=2
#IKOLYMP-4257 add feature GENERIC_OEM_HOOK flag
#IKOLYMP-4894 add feature MUX_PANIC_NOTIF flag
#IKOLYMP-5747 add feature BDTSE_FOR_DTMF flag
#IKOLYMP-7714 Remove feature BDTSE_FOR_DTMF. Revert to DTSE for DTMF
#IKOLYMP-8033 Restore BDTSE_FOR_DTMF. Remove GENERIC_OEM_HOOK (no longer used)
persist.ril.features=0x24
#IKOLYMP-9894 Increase the PPP max failure threshold to 12
#IKOLYMP-10006 Increase the PPP max failure threshold to 16
persist.ril.pppd.start.fail.max=16
#end
ro.hdmi.mirror.enable=false
ro.hdmi.default.app=
hw.overlay.path.config=
# temporary enable AT&T NSUI feature from system prop.
# This should be removed once Flex is enabled in Olympus.
ro.mot.FTR.NSUI=true
# for larger screen support
# 3.75" WVGA == 248dpi
# 4.0" qHD == 275dpi
ro.sf.lcd_density=240
dalvik.vm.heapsize=32m
# Enable FP sensor
ro.mot.hw.fingerprint.enable=1
# required for UDD backup tcmd
ro.mot.hw.calibratedImager=1
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
#For enabling Wispr Feature
ro.mot.wifi.hotspot=0
# To enable Google Froyo Tethering (USB & WIFI hotspot)
ro.tether.denied=false
# To set wifi (AP) driver's firmware path
ro.wifi-ap.fw-path=/system/etc/firmware/wifi/sdio-g-cdc-roml-reclaim-wme-apsta-idsup-idauth.bin
# Enabling EONS feature IKOLYMP-1962
persist.cust.tel.eons=1
ro.opengles.version = 131072
# For docked touchpad keyboard map
android.keylayout.evfwd=/system/usr/keylayout/evfwd.kl
android.keychar.evfwd=/system/usr/keychars/evfwd.kcm.bin
# To send 70 touch events per second
windowsmgr.max_events_per_sec = 70
debug.mot.extwmlog=0
debug.mot.extamlog=0
#proximit sensor screen off delay
mot.proximity.delay=450
#proximit sensor disable touch distance
mot.proximity.distance=60
# Enable HAC support
ro.mot.hw.HAC=1
# BEGIN Motorola, a17262, 8-Dec-2010, IKXOLYMPLA-93 turn off entitlement check
ro.mot.entitlement_check=false
# END
# BEGIN Motorola, w30495 IKOLYMP-9553, add property to control maximum number of hidden apps
ro.MAX_HIDDEN_APPS=50
# END
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=false
ro.default_usb_mode=2
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.2_r10
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.ms=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.config.sync=no
ro.browser.useragent=0
ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal/?model=MB860
gsm.sim.mot.simswap=1
ro.config.sync=no
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.aud.hz=44100
ro.media.enc.hprof.aud.ch=2
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.aud.bps=128000
ro.media.enc.hprof.vid.bps=4000000
ro.media.enc.hprof.vid.width=1280
ro.media.enc.hprof.vid.height=720
ro.media.enc.hprof.codec.vid=h264
ro.media.enc.hprof.vid.fps=30
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB860/profile/MotoMB860.rdf
ro.build.version.full=Blur_Version.0.54.5.MB860.Movistar.en.01
Code:
/ # cat /osh/etc/oshwt-version.txt
OSHWT_U1_6.71.0
Two questions :
1) I can't get adb shell on mi atrix, so i entered by ssh ( sshdroid ). Adb tellme
Code:
./adb shell
error: insufficient permissions for device
2) How to i see these version you mentioned in most th like 1.5.7 & 1.8.3 ? What is this, version of ...
Perdona SidViciOus
Try http://briefmobile.com/motorola-atrix-4g-root to fully access via adb shell to your device. It worked for me.
I didn't understand your second question... ¿me la haces en castellano?
eval-, It seems that not only spanish guys have these ReservedOdm, but movistar's clients...
People, sorry for the bilingualism....
Well, I'm going to follow these instructions
http://www.grupoandroid.com/topic/23784-liberar-bootloader-del-atrix-fuego/
This user on htcmania assures he did on that way
http://www.htcmania.com/showpost.php?p=3414695&postcount=3
Wish me luck!
malevoli said:
Well, I'm going to follow these instructions
http://www.grupoandroid.com/topic/23784-liberar-bootloader-del-atrix-fuego/
This user on htcmania assures he did on that way
http://www.htcmania.com/showpost.php?p=3414695&postcount=3
Wish me luck!
Click to expand...
Click to collapse
Does that user have a Movistar Atrix?
Anyway, good luck. I'm really liking forward to know if I screw mine because of some stranger circumstance, or it was due to the device itself... So please report here ;-) Gravitas