• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

Xolo Software update Available

169 posts in this topic

Posted (edited) · Report post

Dam why would they do that :angry:

I uploaded it take a look: http://www.mediafire...63zvw7dzuzm3zgp

And yes it is a system patch as well, but not full.

Only real change I see is an arm lib and google chrome x86.

Edited by jikobutsu
0

Share this post


Link to post
Share on other sites

Posted · Report post

Looks like a trip back to orange for me, phone now stuck in a boot loop, can't fix it, using the ai0 tool to fix brick doesn't work, can't get recovery to work either, wondering if that update did something ? phone was fine before that update failed.

Is the update for the xolo or both ? least I can use that when I go for a new phone, along the lines of phone wanted to install an update and now it doesn't work ...

0

Share this post


Link to post
Share on other sites

Posted · Report post

if you can boot into android I can help

0

Share this post


Link to post
Share on other sites

Posted · Report post

if you can boot into android I can help

I can get into recovery, but that's it, can't get android to boot as in getting to the home screen and actually having a working phone.

0

Share this post


Link to post
Share on other sites

Posted · Report post

do you have stock logo eg Intel one

0

Share this post


Link to post
Share on other sites

Posted · Report post

do you have stock logo eg Intel one

Not on the phone, which is a worry as they may well ask what the hell I've done to it.

0

Share this post


Link to post
Share on other sites

Posted · Report post

do you no adb?

0

Share this post


Link to post
Share on other sites

Posted · Report post

do you have my tool if you do go to c:/sandiego/tool/ then open the black icon named command prompt

then connect phone and type

adb shell

keep typing it will kick in once you get $ or #

then type stop

let me no

0

Share this post


Link to post
Share on other sites

Posted · Report post

okay got $ (terminal says - shell@android:/ $ )

0

Share this post


Link to post
Share on other sites

Posted · Report post

typ su

it should change to

#

then type stop

0

Share this post


Link to post
Share on other sites

Posted · Report post

did it change to #

0

Share this post


Link to post
Share on other sites

Posted · Report post

okay.

typed su

output was -

Error type 2

android.util.AndroidException: Can't connect to activity manager; is the system running?

at com.android.commands.am.Am.run(Am.java:99)

at com.android.commands.am.Am.main(Am.java:80)

at com.android.internal.os.RuntimeInit.finishInit(Native Method)

at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:238)

at dalvik.system.NativeStart.main(Native Method)

Then I typed stop.

0

Share this post


Link to post
Share on other sites

Posted · Report post

did it change to #

Yes terminal now reads - shell@android:/ #

0

Share this post


Link to post
Share on other sites

Posted · Report post

good now your going to have to open a new command prompt so click the black icon again but make sure you keep the first window open then copy exactly this

adb push flashtool data/local/tmp/

then

adb shell chmod 755 data/local/tmp/flashtool

0

Share this post


Link to post
Share on other sites

Posted · Report post

Okay done that (thanks for the help by the way)

0

Share this post


Link to post
Share on other sites

Posted · Report post

if adb shell chmod 755 data/local/tmp/flashtool don't work goto first command prompt Window and type

chmod 755 data/local/tmp/flashtool

0

Share this post


Link to post
Share on other sites

Posted · Report post

now open the full xolo update the 299mb one found in c:/sandiego/xolo with winrar or 7zip and extract fastboot.img and recovery.img to c:/sandiego/tools

tell once done

0

Share this post


Link to post
Share on other sites

Posted · Report post

then with the second command prompt window and type

adb push fastboot.img /data/local/tmp/

and then type

adb push recovery.img /data/local/tmp/

tell once done

0

Share this post


Link to post
Share on other sites

Posted · Report post

Okay, done that, no errors.

0

Share this post


Link to post
Share on other sites

Posted · Report post

now you must copy exactly what I write here to first command prompt window

cd data/local/tmp

then

./flashtool -i recovery -w ./reccovery.img

copy past command prompt output here

0

Share this post


Link to post
Share on other sites

Posted · Report post

Here's the output from the commands you got me to run.


shell@android:/ # cd data/local/tmp

cd data/local/tmp

shell@android:/data/local/tmp # ./flashtool -i recovery -w ./recovery.img

./flashtool -i recovery -w ./recovery.img

flashing './recovery.img' to 'recovery' osip[1]

Writing 10486784 byte image to osip[1]

slot 0 used by osip 2

slot 1 used by osip 1

slot 2 used by osip 3

shell@android:/data/local/tmp #

0

Share this post


Link to post
Share on other sites

Posted · Report post

good now type

./flashtool -i fastboot -w ./fastboot.img

type output here

0

Share this post


Link to post
Share on other sites

Posted · Report post

Here you go.


shell@android:/data/local/tmp # ./flashtool -i fastboot -w ./fastboot.img

./flashtool -i fastboot -w ./fastboot.img

flashing './fastboot.img' to 'fastboot' osip[2]

Writing 10486784 byte image to osip[2]

slot 0 used by osip 2

shell@android:/data/local/tmp #

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.