168 replies to this topic

[technomole]

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

[rickywyatt]

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

[rickywyatt]

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

[technomole]

okay done that.

[rickywyatt]

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

[technomole]

Okay, done that, no errors.

[rickywyatt]

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

[technomole]

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 #

[rickywyatt]

good now type

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


type output here

[technomole]

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 #

[rickywyatt]

good now type

reboot bootloader

then open aio tool and select bricked opinion let it flash then let me no if it worked

[technomole]

I'm not sure why but when I opened the ai0 tool the system couldn't find the phone, so as yet no luck, I'm trying to go through the steps again but seem to be having trouble with the system not knowing what the phone is.

[rickywyatt]

try to shut fone down by holding the power button then turn back on see if it starts boot looping again

[technomole]

It still boot loops, not sure why but when I try and run adb push flashtool data/local/tmp/

I get daemon not running. starting it now on port 5038 *
daemon started successfully *
error: device not found

even if the phone is plugged in.

Also noticed that the ai0 tool does the same, but is using port 5037

Could be this part of the problem ?

[rickywyatt]

can you get into recovery

[technomole]

yes, but using the recovery option results in the red triangle, and everything else takes me back to the boot loop.

[rickywyatt]

have you tried since I made you flash the old xolo recovery

[technomole]

Yes, when I couldn't do fix brick I tried using recovery, still failed though, and now every time I plug the phone into the pc it wants to install the intel mtp driver, which it then tries to do and that fails as well.

[rickywyatt]

put phone in fastboot and connect to pc open device manager and see if you see adb

[technomole]

In device manager the first entry is Android Phone, and under that Android ADB Interface. (windows 7 ultimate)

If I open the command prompt and type adb shell I get device not found, even though it's plugged in.

Edited by technomole, 21 November 2012 - 02:47 PM.