1672 replies to this topic

[gwebb]

Intel badly need some developer support for x86 Android, and what do we get? Locked down phones running Gingerbread.

From everything I've read it sounds like a decent phone, the price is right, but they've dropped the ball on the software side.

Hardware wise this could be THE phone for hacking right now; a fast CPU, NFC, state-of-the-art image processor, HDMI, good screen, lots of RAM, and potentially very interesting x86 Linux/Android software (Intel has done a lot of Linux work).

Anyway, good luck to those of you working to prize it open.

[spences10]

PaulOBrien, on 13 June 2012 - 08:16 PM, said:

It's an extremely old package that doesn't flash.

P

bawls

[.thalamus]

Hmmm, the first post is grim reading. I was going to buy one of these last week, but something told me to hold off, and I'm glad I did.

I also found that they use an obscure format for the boot / recovery / fastboot images which are probably created by some obscure proprietary Intel tool, so that'll cause problems I imagine. I might be wrong though.

[PaulOBrien]

I did a 'fastboot erase userdata' today - it worked and I was able to boot OK. Not that useful, but just FYI.

P

[PaulOBrien]

'fastboot flash userdata' fails, same for cache.

Quote

'writing 'userdata'... FAILED (remote: flash command failed)'

P

[PaulOBrien]

OK!

I was brave / stupid enough to 'fastboot flash' a boot image. The device isn't bricked per se, but I can only load recovery / fastboot, the device won't boot normally. So, hopefully, it should be recoverable when an Orange update zip surfaces...

P

[PaulOBrien]

I conclude from this that the boot images are signed...

P

[PaulOBrien]

Hmmm, resurrected by dead device by flashing the boot.bin from the Lava Xolo update. So they must share the same boot image signature.

P

[Rem1x]

So are we pretty much s*** out of luck for root/custom recoveries?

[spences10]

I noticed the images were called .bin in the factory download

Are you still able to unpack them in this format? Probably why nothing is booting with the .img extension, all stuff I'm sure you're aware of Paul

[PaulOBrien]

Yes, we can unpack (i've unpacked a bunch of them) but not repack as they're signed.

We really could do with a bootloader unlock.

P

[PaulOBrien]

The .bin and .img files seem to be the same format AFAICT.

P

[.thalamus]

PaulOBrien, on 14 June 2012 - 09:24 AM, said:

I conclude from this that the boot images are signed...

P

I would expect so. From the info that I have found the trusted boot requires verification of signed images. I would hope that there would be a way to disable that though, aka 'unlocking' the bootloader.

Edited by .thalamus, 14 June 2012 - 10:10 AM.

[hecatae]

has anyone got the xolo retail rom?

[PaulOBrien]

I think we should be able to get the (unbranded) Xolo ROM onto the device if we can find the full release in update zip format...

P

[spences10]

PaulOBrien, on 14 June 2012 - 09:54 AM, said:

Yes, we can unpack (i've unpacked a bunch of them) but not repack as they're signed.

We really could do with a bootloader unlock.

P

lol, I did try oem unlock, just says waiting for device

actually when i use the correct id! -i 0x8087 it says FAILED (remote: unknown OEM command)

Edited by spences10, 14 June 2012 - 11:18 AM.

[Spooke]

Is this of any use?

http://www.xolo.in/x...oftware-upgrade

Edit - the file is only 10mb Didn't realise it was only a update, not the full rom, my bad.

Could you maybe contact them by email or have you already tried?

Edited by Spooke, 14 June 2012 - 11:35 AM.

[PaulOBrien]

The SD appears to have a switch so it can tell when the back cover is off.

Unfortunately, this doesn't seem to have any effect on what you can do in bootloader etc.

P

[PaulOBrien]

My device shows up as a Xolo X900 in USB settings now.

P

[spences10]

PaulOBrien, on 14 June 2012 - 03:42 PM, said:

My device shows up as a Xolo X900 in USB settings now. data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAMAAAC6V+0/AAAABGdBTUEAANbY1E9YMgAAAdRQTFRFV0AI////V0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIW0IIV0AIW0IIW0QJW0IIV0AIV0AIV0AIQzQQa0oJbEwJbVELbk4Kb0wJb1QMcVILc1cMlF8Ll2oNmXEQnn8Vo2gLpGgLpGoMpW8NpXEOp3YQq4MUrH0Rro0Xr4QUsI4XsZAYuXQNwIkSwI0VyIAOyocQyqcdy4QQzosS1Kod1rIf3ZMS3ZUT3a8c3o4Q3rcf4ZER5JUR5ZYS5ZgS5aIW55wT554U6KkZ6qQV6qUW6qYW6qcX66gW7Lsf7a0X7a0Y7a8Z7bEb7rAY7rEY7rMa7rMb77Ma77cd77oc8bob8b4f8cUh8skh870c88If88kk89Im9Mwl9cch9scf9skh9swi9swk98og988k99Mm+dMk+dYm+9cl+9gl+9kn+9on+9oo+9op+9so/Ngl/Non/Nso/N0o/N0p/eAp/eEp/uAn/uIq/uMp/uMq/uQq/+An/+En/+Eo/+Io/+Ip/+Mo/+Mp/+Mq/+Qp/+Qq/+Qr/+Uq/+Ur////QENjqgAAACd0Uk5TAAABCQoLHCYnMDY4OjuCg4WHiImKm56fx8jJys3P1Ofp6enq7/DyAdnyKAAAASJJREFUGNNjYMQCGBgZgICZi09CRUWCj4sZxIMIsgnr2ngW5HlYaQmzQQWZOOWM8xvaWuurSmOM5DiZwILsSq4NHb2zZvS015ZnOsmzgwRZxewbu9TVZ82cqa5eW5JmKcoCFOTRr2hXB4pMV582Sb0yN0ybGygoZFfXPX369GlTpkyZ3FldmGAhABSU8WuZChaZOHHihKbiFHdJoKBKdrO6OkhkYn9/n7p6srcCUFA1q0Z9tjoUzFaP9wIJyvpUqs+GA/UoN2mgoIhtMbJgqJkgUJBXL70MLqoe6a/DA3K8uHVGEVRUPTrQVIwV5E0OZcfUHIg94YEOiuywADEMjktKjI0I8TWABQgo6DTNXYICnE004EEHDmR+KTU1KX54IGMBAGd3XCYdIc62AAAAAElFTkSuQmCC

P

From flashing that 10mb update?

Is that where the logo.img came from?