FORUMS

OnePlus 2 Forums: Discuss Everything About The OP2!

Now that the OnePlus 2 has been officially unveiled and that we have had close-up … more

Intel & Micron Announce “Revolutionary” Storage Tech

Intel & Micron have announced 3D Xpoint technology—”the … more

Google Now Interfaces With Third-Party Messaging Apps

Google has announced that Ok Google voice commands can now be used to send … more

Make Your Lockscreen More Productive With Widgets

Are you running Android Lollipop? Do you miss the ability to add widgets to your lock … more

[URGENT REQUEST] Spanish (Movistar?) Atrix user needed ASAP

227 posts
Thanks Meter: 335
 
By eval-, Retired Recognized Developer on 14th July 2011, 11:06 AM
Post Reply Subscribe to Thread Email Thread
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.
The Following User Says Thank You to eval- For This Useful Post: [ View ]
 
 
15th July 2011, 11:20 AM |#2  
adlx.xda's Avatar
Recognized Developer
Flag Madrid
Thanks Meter: 1,005
 
Donate to Me
More
Arrow
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
Attached Files
File Type: zip AtrixSpainFiles.zip - [Click for QR Code] (11.8 KB, 53 views)
Last edited by adlx.xda; 15th July 2011 at 11:55 AM.
The Following 2 Users Say Thank You to adlx.xda For This Useful Post: [ View ]
16th July 2011, 04:59 AM |#3  
Pzyduck's Avatar
Senior Member
Flag La Rioja
Thanks Meter: 817
 
More
Thanks adlx, good luck
17th July 2011, 11:13 AM |#4  
OP Retired Recognized Developer
Thanks Meter: 335
 
More
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...
18th July 2011, 12:54 AM |#5  
adlx.xda's Avatar
Recognized Developer
Flag Madrid
Thanks Meter: 1,005
 
Donate to Me
More
Quote:
Originally Posted by eval-

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...

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.
18th July 2011, 01:57 PM |#6  
OP Retired Recognized Developer
Thanks Meter: 335
 
More
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?

Quote:
Originally Posted by adlx.xda

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.

The Following User Says Thank You to eval- For This Useful Post: [ View ]
19th July 2011, 10:53 AM |#7  
adlx.xda's Avatar
Recognized Developer
Flag Madrid
Thanks Meter: 1,005
 
Donate to Me
More
Quote:
Originally Posted by eval-

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?

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...
20th July 2011, 12:06 AM |#8  
adlx.xda's Avatar
Recognized Developer
Flag Madrid
Thanks Meter: 1,005
 
Donate to Me
More
Thumbs down 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.
Last edited by adlx.xda; 20th July 2011 at 12:08 AM.
4th September 2011, 04:41 PM |#9  
Junior Member
Barcelona
Thanks Meter: 5
 
More
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.
4th September 2011, 04:58 PM |#10  
Junior Member
Barcelona
Thanks Meter: 5
 
More
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
4th September 2011, 05:29 PM |#11  
Junior Member
Barcelona
Thanks Meter: 5
 
More
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
root@localhost:/# whoami
whoami
root
root@localhost:/# less /sys/firmware/fuse/ReservedOdm
less /sys/firmware/fuse/ReservedOdm
WARNING: terminal is not fully functional
/sys/firmware/fuse/ReservedOdm  (press RETURN)
20000000200000000
/sys/firmware/fuse/ReservedOdm (END)
/default.prop
Code:
root@localhost:/# 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:
root@localhost:/# 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:
root@localhost:/# 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:
root@localhost:/# 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:
root@localhost:/# 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
The Following 2 Users Say Thank You to malevoli For This Useful Post: [ View ]

Read More
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes