Camelia, the Perl 6 bug

IRC log for #motoactv, 2012-03-21

| Channels | #motoactv index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:32 Bdaman80-Iconia joined #motoactv
00:34 Bdaman80-Iconia left #motoactv
05:39 Pau joined #motoactv
05:39 Pau Hello
05:40 Pau bdaman80 do you have a 16gb model?
05:40 Pau ds2
05:51 dproldan joined #motoactv
09:58 christefano joined #motoactv
10:06 christefano joined #motoactv
11:14 bdaman80 left #motoactv
12:14 morten_ joined #motoactv
12:15 morten_ hi - has anyone seen instructions for how to root the motoactv 16gb model?
13:34 datagutt joined #motoactv
13:34 datagutt joined #motoactv
15:14 cmw joined #motoactv
16:20 bASSchica joined #motoactv
16:30 bASSchica Anyone here?
16:34 CEnnis91 whats up
16:42 CEnnis91 bASSchica: ?
17:04 bASSchica Hey, just wondering if anyone might be able to help me troubleshoot my MotoActv.  I get the M splash screen but it doesn't boot beyond that and if I go to Fastboot it doesn't get recognized by my computer as adb device.
17:10 CEnnis91 sounds like system is messed up
17:10 CEnnis91 and adb isnt recognized in fastboot, fastboot is
17:10 CEnnis91 chcek the forum there have been other ppl with that issue
17:12 ds2 which forum is the forum thesedays? the 121+ page thread?
17:14 bASSchica Yeah, I tried searching it and without having a proper forum it's hard to find things.  =|
17:21 CEnnis91 you dont need pre page 100
17:22 CEnnis91 for sure you dont need anything before this http://forum.xda-developers.com/showthread.php​?p=22064190&highlight=utkanos#post22064190
17:23 CEnnis91 but thats still 70 pages
17:23 ds2 blah, that is yet another thread
17:24 CEnnis91 ds2: that just links the recovery its not a big deal
17:24 CEnnis91 ds2: but i had to create another thread for the roms, otherwise they wouldve gotten lost
17:24 CEnnis91 http://forum.xda-developers.​com/showthread.php?t=1534073
17:25 ds2 CEnniis91: 1399692 is the one I been following
17:25 ds2 CEnniis91: is someone working on a Linux version of the root tool? been having to do everything manually since fastboot won't recogonize the device in Windows
17:25 CEnnis91 wait what?
17:26 ds2 http://forum.xda-developers.com/sho​wthread.php?t=1399692&page=126
17:26 ds2 that thread is what I been following but now I learn there are 2 more (at least)
17:27 ds2 having to reverse engineer what the batch files do in the windows version everytime is no fun
17:27 CEnnis91 well the roms thread doesnt really hold any useful information
17:27 CEnnis91 neither does the recovery
17:27 CEnnis91 they just contain the useful files, heh
17:28 CEnnis91 but what about the linux part
17:28 ds2 oh
17:28 ds2 would be nice if there are simple .sh files
17:28 CEnnis91 shrug
17:28 CEnnis91 the commands arent complicated
17:28 CEnnis91 just make ur own =)
17:29 ds2 cuz the way I am doing it is to grab the cleard tool, run it but don't press any buttons, copy out the temp files, then do everything manually
17:29 ds2 I know. I did it once already... the complain is all the releases are in the 'updated' version of the tool and not posted directly
17:29 CEnnis91 oh yea
17:29 CEnnis91 ive bitched at cleard for that too
17:30 ds2 would be nice to flash in 5.6.0 but I been holding off til I get free time and a windows machine around
17:30 CEnnis91 usually i just make him extract it for me
17:30 ds2 heheh
17:30 CEnnis91 well all you need is to push the file to the sdcard and install in recovery
17:30 CEnnis91 you dont really need a tool to install 5.6.0
17:31 ds2 does installing recovery repartition flash or did motorola allocate space for it?
17:31 CEnnis91 you  have to dd it in
17:31 ds2 so I need to reflash everything to allow space for the recovery image?
17:31 ds2 (system.img, etc)
17:31 CEnnis91 no
17:32 CEnnis91 1) Download this file: CWMR5x_F100_recoveryA.img
17:32 CEnnis91 2) adb push CWMR5x_F100_recoveryA.img /data/local/
17:32 CEnnis91 3) adb shell (become root)
17:32 CEnnis91 4) dd if=/data/local/CWMR5x_F100_recoveryA.img of=/dev/block/mmcblk1p13
17:32 CEnnis91 5) exit adb from the device
17:32 CEnnis91 6) adb reboot recovery (you should be in CWMR now)
17:32 CEnnis91 http://rootzwiki.com/topic/17022-recover​y-cwmr-5028-for-moto-f100motoactv-beta/
17:32 ds2 different wiki heh... that is the clearest instructions yet
17:33 CEnnis91 ds2: utkanos and i arent dumb ;)
17:33 ds2 not saying that
17:33 ds2 i usually don't work on recovery images
17:33 CEnnis91 not saying cleard is either, but well make sure the progress is simple
17:33 CEnnis91 ah
17:33 ds2 most android stuff I work on don't even use fastboot
17:34 CEnnis91 samsung/htc?
17:34 ds2 I do custom ports for special hw
17:34 CEnnis91 ah
17:34 ds2 so I use whatever works on the board
17:34 CEnnis91 as a job, or hobby?
17:34 ds2 job
17:34 CEnnis91 (feels like a job)
17:34 CEnnis91 yea
17:35 ds2 I would love to turn this into a gps logging watch
17:35 bASSchica Ok, so I think I've gotten a little further.  I was trying ADB in fastboot instead of fastboot commands.  I tried a fastboot -w and still get the splash screen.  I think I need it to re-image possibly...
17:36 CEnnis91 bASSchica: try reflashing the system.img in fastboot
17:36 bASSchica ds2, that's what I want too :( I  just want runkeeper =|
17:36 CEnnis91 and then reflash the boot.img if it still doesnt work
17:36 ds2 what irks me is not having a read flash command in fastboot on this device
17:37 bASSchica What's the correct syntax for system.img  flashboot flash system.img  ?
17:37 bASSchica yeah, I was thinking that too
17:37 ds2 you need the partition name
17:37 ds2 forgot what fastboot calls the system.img partition
17:41 ds2 fastboot flash system IMGs\%SubDIR%\%SystemIMG%
17:41 ds2 from the fullrestore.bat file
17:41 ds2 modify as needed
17:47 bASSchica If I run the fullrestore.bat it says it found the following dates and then no dates found, then says to enter a date to continue.
17:48 bASSchica In the folder that I have the root tool in I do have several images: boot, recovery, modified_boot
17:49 bASSchica oh and systemt oo
17:49 bASSchica er too
17:50 bASSchica boot, CWMR5x_F100_recoveryA, modified_boot, recovery, system
17:56 bASSchica Ok, return to stock from the gui might have worked.  I've got the water rings around the M showing...
17:57 bASSchica Whew, that got it to boot finally.
17:58 bASSchica So I assume the stock update will fail with the SN issue right?  Or is there a work-around to that?
17:58 CEnnis91 fastboot flash system system.img
18:18 [mbm] bASSchica: fastboot and adb are two entirely different protocols and commands; when in fastboot you are not expected to have adb
18:24 [mbm] ds2: the whole tool method of backing up, restoring and rooting is just silly, you can write almost any partition from fastboot so all you really need to do is flash with something that has adb enabled and ro.secure=0 so adb runs as root
18:24 ds2 [mbm]: *nod* but every vendor has little extensions to fastboot if they use it
18:25 [mbm] there's actually no need for a custom recovery, update.zip files or root exploits
18:25 [mbm] people just do that crap without thinking just because they always did it that way
18:26 [mbm] ds2: it's always 'fastboot flash $name $file'
18:26 ds2 [mbm]: you seem to know this - Am I correct that i cannot brick things as long as I can boot into fastboot?
18:26 [mbm] for any device that has fastboot
18:26 ds2 [mbm]: the kernel sometimes wants -c or other stuff
18:26 [mbm] correct
18:27 ds2 [mbm]: 'k good to know. I am usually a bit paranoid on devices I don't have console on
18:28 [mbm] moto has a size limit on their flash command; some larger flash requests are broken into several smaller ones
18:29 [mbm] I can't remember if that applies to motoactv or not; don't think so
18:29 [mbm] and the flash command is about the only thing other than getvar that's likely to work
18:30 [mbm] and getvar isn't all that useful
18:30 ds2 actually, flash isn't that standard come to think of it...
18:30 ds2 one !@#!@$!@#!@#!@@$!##%#@$*(#@()$@#* vendor has decided to require sign'ed images
18:30 ds2 can't name that vendor :(
18:31 [mbm] oh, several of them require signed images with the flash command
18:31 ds2 bastards :)
18:31 [mbm] pretty much every other moto device will only work with signed images
18:32 ds2 this particular vendor does it on their dev board :(
18:32 [mbm] the trick is to have those images handy so when you brick you can just reflash from fastboot
18:33 ds2 for that sure...  but it is frustrating when doing development
18:33 [mbm] I recommend grabbing copies of /dev/block/mmc* before messing with those partitions
18:34 ds2 as far as people know, the motoactv doesn't have NAND, does it?
18:34 [mbm] emmc
18:34 ds2 I know it has emmc
18:34 ds2 trying to backout the possible sysboot config
18:34 [mbm] if it was nand it'd show up as mtd* and not mmc*
18:34 ds2 I know that. slightly different bit of info I am looking for
18:35 [mbm] and you'd have to deal with the crap of nand oob pages
18:35 ds2 some boards (i.e. the G8 archos) have NAND as the boot and eMMC as the storage
18:35 ds2 yep. nand_write instead of dd to install stuff
18:35 ds2 anyone sounded out which PMIC is on the actv?
18:35 [mbm] oh, moto keeps everything on a single emmc for all theur emmc devices
18:36 ds2 is it the venerable TWL4030?
18:37 [mbm] bootup for omap chipsets pretty much matches the ti trm documemts
18:37 [mbm] just that moto likes to rename the things
18:37 ds2 the goal of this line of questioning is to find out if there is a chance we can USB boot
18:37 [mbm] x-loader becomes mbmloader
18:37 [mbm] the motoactv? sure
18:38 ds2 so the USB port is off of the MUSB block via the TWL4030 phy?
18:38 ds2 so it'd be just a mod to sysboot to get it to scan for it?
18:38 [mbm] but probably only by booting and then setting the omap boot configuration registers
18:38 [mbm] and unfortunately it's an omap hs
18:39 ds2 oh
18:39 [mbm] which means that it requires a signed boot image
18:39 ds2 blah
18:39 [mbm] and usb boot on an omap is limited to 64k
18:40 [mbm] so stuff needs to be loaded in stages
18:40 [mbm] more trouble than it's worth really
18:40 [mbm] especially since we don't have a signed usb payload
18:41 [mbm] boot config is probably set to emmc then usb
18:42 [mbm] so if you wiped the bootloader off the emmc gou'd probably see the asic packet of a usb boot
18:43 [mbm] if there was an sdcard slot there'd also be the option of booting that
18:43 [mbm] which is pretty easy because sd and emmc look the same to the chip
18:44 [mbm] </trivia>
18:45 [mbm] oh, and twl was an older chipset; omap3 on the motoactv, omap4 on newer moto phones
18:46 Okawa__ joined #motoactv
18:48 ds2 yes, I am familiar with that
18:48 ds2 thought signed means I can't even load into SRAM?
18:48 [mbm] not with moto
18:49 ds2 Oh they didn't fully lock it, nice.
18:49 [mbm] fastboot has a few partitions it will refuse to write to
18:49 ds2 you seen this fastboot source?
18:49 [mbm] all others are fair game to write anything
18:50 [mbm] but on bootup the bootloader will walk the cdt and look for partitions which should be signed
18:50 [mbm] and verify the signatures
18:50 ds2 if this is the case, someone should copy out the mbmbootloader and archive it
18:51 [mbm] happens that the bootloader on the motoactv doesn't bother checking siga
18:51 [mbm] *sigs
18:52 [mbm] so, the longer explaination is: secure rom on omap chip has sha1 of a public key
18:52 [mbm] public key is stored in mbmloader
18:52 [mbm] sha1 has verifies the key
18:53 ds2 I thought there is a key that can be burned into the chip for the ROM?
18:53 [mbm] key is used to check signatures of mbmloader/mbm
18:53 ds2 oh nevermind... that is what it is, misread
18:53 [mbm] mbm can then continue the chain of trust checking more sigs as specified by the cdt
18:54 ds2 got it
18:54 ds2 where are you finding docs on the HS parts?
18:54 [mbm] technically it's just the sha1 of the key burned into the chip
18:54 dproldan joined #motoactv
18:54 [mbm] lol, no docs, just a few years of reverse engineering moto devices
18:55 ds2 ah, okay.
18:55 [mbm] key is in emmc as part of mbmloader
18:55 ds2 was trying to find out if - 1. you got it under NDA or 2. there are public docs
18:55 [mbm] mbmloader also has ths other keys used to sign software and such
18:56 ds2 I guess the SHA1 is different btwn HS and non HS devices?
18:56 [mbm] well, the public side used for the verification
18:56 [mbm] hs is high security
18:56 ds2 I know, but there are non HS versions
18:56 [mbm] otherwise it's gp general purpose
18:56 ds2 GP is the name I was looking for
18:57 ds2 GP and HS have different SHA1's in them?
18:57 [mbm] ti has complete docs on the gp free on their website
18:57 ds2 yes, I am familiar with the GP parts
18:57 [mbm] if you try to read the sha1 from a gp device you just get 00's
18:57 ds2 mapping the differences in my mind
18:57 ds2 Ohhhhhhhhhhhhhhhhh okay
18:58 [mbm] shows up in the asic packets that way too
18:58 ds2 these details are good to know
18:59 ds2 do you have a write up on this somewhere?
19:00 [mbm] not really; droid-developers.org has a bunch of useful information though
19:01 [mbm] otherwise feel free to ask me what I know and find a place to write it up
19:01 ds2 heh, thanks.
19:02 ds2 now I have confirmed it is hard to hard-brick it, I can do more experiments
19:04 [mbm] some of my stuff occasionally gets posted to opticaldelusion.org, but I'm usually to lazy or don't want to show my cards too obviously where moto might start making things difficult
19:04 [mbm] yep, pretty much leave mbmloader/mbm alone and keep backups of the rest
19:05 * [mbm] should probably post more stuff to the blog
19:08 bASSchica Whew, ok got myself back to mostly where I had things before.  I was concerned I had a $200 paperweight for awhile.  :)  Have any of you installed MyTracks?  I didn't have luck with that before.
19:09 * [mbm] has mytracks on the phone
19:09 [mbm] for the motoactv I've just been using the walk/run to track
19:10 bASSchica Is there an apk that you used?
19:12 [mbm] huh? app came preinstalled
19:12 [mbm] you never used the motoactv as a motoactv?
19:12 bASSchica for mytracks?
19:13 bASSchica oh, sorry thought you said you had mytracks on it, you said phone
19:13 bASSchica my bad.  I know someone else said they had it on MotoActv
19:19 christefano joined #motoactv
19:22 christefano joined #motoactv
19:23 morten_ joined #motoactv
19:23 morten_ got a rooting question, guys
19:24 [mbm] sup?
19:52 morten_ I've been able to find instructions for how to root the 8gb version, but not the 16. Any hints?
20:11 CEnnis91 the method should be the same
20:12 CEnnis91 i dont think that the 16gb boot.img is any different from the 8gb boot.img
20:12 CEnnis91 but we dont know for sure
20:16 bASSchica I wouldn't risk it if it were me until someone tested though.
20:17 CEnnis91 i believe it was
20:20 CEnnis91 http://blog.8796.jp/8796kanri/20​11/12/motoactv-16gb-rooted.html
20:21 CEnnis91 [mbm]: anything in boot.img that would be different in the 8gb and 16gb models?
20:21 bASSchica Just realized my music is still on mine still, yay.  That's good to see.
20:22 bASSchica I wish I had taken the time to fix it before my 5k last weekend.
20:22 bASSchica ah well
20:27 dproldan joined #motoactv
20:31 morten_ The instructions mention that they won't work for the 16Gb model - and also to make sure the firmware is the right version. Mine is newer
20:32 CEnnis91 thats kind of true
20:32 CEnnis91 newer versions are fine
20:32 CEnnis91 if you dont use the hacky boot.img
20:32 CEnnis91 if you use the right one its fine
20:32 CEnnis91 or if you update
20:32 CEnnis91 then you can use it
20:33 CEnnis91 i would guess that they say it doesnt work on the 16gb because no one tested for sure
20:33 CEnnis91 but im not telling you to do it
20:33 dproldan :-)
20:33 morten_ hehe okay
20:43 [mbm] CEnnis91: expect them to be the same
20:44 CEnnis91 [mbm]: and as for system.img?
20:44 CEnnis91 i see nothing that would matter minus a few build.prop lines
20:44 [mbm] if someone can provide me with the 5.6.0 upgrade zip for a 16g I can confirm
20:45 CEnnis91 one sec i think i can get it
20:45 [mbm] basically just dig out the applypatch line and look at the sha1sums
20:46 CEnnis91 okay, and for the files it doesnt patch?
20:46 CEnnis91 if enough are the same, its likely they will all be?
20:47 [mbm] well, only one I care about is boot.img since after that you can use root to check the rest
20:48 [mbm] and that will be an applypatch
20:48 [mbm] and if I'm right the exact same sha1
20:48 [mbm] thinking the only difference is cdt
20:49 CEnnis91 https://rsdsecure.motorola.com/downl​oad/delta-ota-Blur_Version.4.56.97-5​.6.1.Motorola-F100.Retail.en.US.zip fwiw
20:49 CEnnis91 but im checking
20:50 [mbm] yeah, I'm irc'ing from my phone so I can't check it for myself right now
20:50 CEnnis91 [mbm]: apply_patch("MTD:boot:2957312:7c147eda886​d8883851160cd0627f96ad635be9b:2959360:a49​b7084ec74ab7d60757a18bc4eca41f20c4cca",
20:50 CEnnis91 "-", a49b7084ec74ab7d60757a18bc4eca41f20c4cca, 2959360,
20:50 CEnnis91 7c147eda886d8883851160cd0627f96ad635be9b, package_extract_file("patch/boot.img.p"));
20:50 CEnnis91 which is the sha1sum
20:51 CEnnis91 err
20:51 CEnnis91 nvm
20:51 [mbm] sha1sum boot-5.6.0.img
20:51 [mbm] think I gave you that file already
20:52 CEnnis91 yes
20:52 [mbm] wait .. 5.6.1?
20:52 [mbm] dammit..
20:52 CEnnis91 thats how they are ordering it
20:52 CEnnis91 no
20:52 CEnnis91 5.6.1  "1" = 16gb model
20:52 [mbm] ah
20:52 CEnnis91 horrible versioning
20:53 dproldan heh
20:53 CEnnis91 4.55.97 = 8gb / 4.56.97 = 16gb
20:53 CEnnis91 and then theres an US and EU version
20:53 [mbm] ah
20:54 CEnnis91 [mbm]: theyre not the same
20:54 CEnnis91 a49b7084ec74ab7d60757a18bc4eca41f20c4cca vs e4df6cd302b1a478818d431278df843d2d40dce2
20:55 CEnnis91 the sizes of them are however
20:55 CEnnis91 before and after
20:55 [mbm] hmm, guess we'd need the actual boot.img to figure out what changed and if it mattered
20:56 CEnnis91 of course there is no boot.img in the 16gb otas
20:56 CEnnis91 ive checked
20:56 [mbm] you're looking at the non-rooted boot-5.6.0?
20:57 CEnnis91 yes
20:57 CEnnis91 the sha1sum command was the same from the applypatch in the ota aswell
20:57 CEnnis91 so im sure thats correct
20:57 [mbm] next idea - assume rooted boot.img works, dump recovery.img and reverse the recovery-from-boot patch to get a stock boot
20:58 CEnnis91 how does reverse patching work?
21:00 [mbm] iirc applypatch had a commandline switch
21:00 CEnnis91 -c -s -l are the
21:01 CEnnis91 parameters
21:02 [mbm] hmm
21:02 CEnnis91 -l is useless
21:02 CEnnis91 applypatch -s <bytes> so not sure what that would do
21:03 [mbm] if there was a way to boot recovery I'd just mess with that and let the install-recoverh.sh clean up
21:04 [mbm] but don't think theres a way to boot to recovery
21:06 CEnnis91 well done moto
21:06 CEnnis91 [mbm]: what about the factory cable stuff?
21:07 CEnnis91 they have that prop that allows adb over it right?
21:07 CEnnis91 on a stock device
21:09 CEnnis91 hmmm interesting
21:10 CEnnis91 [mbm]: i went back one official version: not only are the sha1sums different but the initial size is different between the 8gb/16gb
21:10 CEnnis91 so there is definitely something worthwhile missing early on
21:11 CEnnis91 2048 bytes smaller, interesting
21:12 CEnnis91 er, kb
21:12 CEnnis91 nope, right the first time
21:12 * CEnnis91 goes to school
21:18 [mbm] CEnnis91: iirc, plugging in my factory cable didn't do a damn thing other than externally powering it
21:18 [mbm] as for the prop, yeah look at my modified boot.img
21:43 CEnnis91|Mobile joined #motoactv
22:33 cmw joined #motoactv
22:59 Snoothy joined #motoactv

| Channels | #motoactv index | Today | | Search | Google Search | Plain-Text | summary