Guest Posted November 21, 2012 Report Share Posted November 21, 2012 (edited) 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 November 21, 2012 by Guest Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 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 ... Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 if you can boot into android I can help Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 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. Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 do you have stock logo eg Intel one Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 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. Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 do you no adb? Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 No, afraid not. Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 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 Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 okay got $ (terminal says - shell@android:/ $ ) Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 typ su it should change to # then type stop Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 did it change to # Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 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. Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 did it change to # Yes terminal now reads - shell@android:/ # Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 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 Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 Okay done that (thanks for the help by the way) Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 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 Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 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 Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 okay done that. Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 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 Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 Okay, done that, no errors. Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 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 Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 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 # Link to comment Share on other sites More sharing options...
Guest rickywyatt Posted November 21, 2012 Report Share Posted November 21, 2012 good now type ./flashtool -i fastboot -w ./fastboot.img type output here Link to comment Share on other sites More sharing options...
Guest technomole Posted November 21, 2012 Report Share Posted November 21, 2012 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 # Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now