1245 replies to this topic

[BlueMoonRising]

It's possible there's a corrupted file somewhere in the download, I don't have the original(or previous?) files to confirm.

[Biohead]

Double check the Orange Dump has unpacked in the correct place. It should be C:\SanDiego\System. If it's not, open up Dump.zip, and extract it manually to C:\SanDiego\System (not System2!!).

Took me some time but I sorted it in the end.

Edited by Biohead, 07 January 2013 - 07:35 PM.

[FullXon]

Yeah, same, it hadn't extracted to the correct directory (if anywhere at all). Now, i have another problem though, When i attempt to flash Orange ICS i always end up with an error partway through saying there is not enough space on the device to copy a file, and then proceeding to push the update.zip.

I had a good 3gb of space available and had installed no apps, so i dont understand where this error is coming from, is it perhaps referring to the system partition?
and if so, is ther any reason why it's not working for me?
Thanks,
-FullXon

[rickywyatt]

the problem is dropbox keeps changing the download files names and thay wont extract and  i cant keep up with them the error is because orange put a patch in there rom and it checks the system partition if the file dont match the orange ics update will stop

[Biohead]

First, make sure the Dump.zip isn't in that system folder, as it will push everything in there to the phone.

Two, and this is the issue I had (Post #614):

In the script (at the Orange ICS section), theres a line that says:

adb shell rm -r system/app/*

For some reason, it returns an error with this code so I've replaced it with:

adb shell rm -r system/app
adb shell mkdir system/app

If run the orange ics section line by line in a separate command prompt, you'll be able to identify if thats the issue.

[FullXon]

 Biohead, on 07 January 2013 - 08:25 PM, said:

First, make sure the Dump.zip isn't in that system folder, as it will push everything in there to the phone.

Two, and this is the issue I had (Post #614):

In the script (at the Orange ICS section), theres a line that says:

adb shell rm -r system/app/*

For some reason, it returns an error with this code so I've replaced it with:

adb shell rm -r system/app
adb shell mkdir system/app

If run the orange ics section line by line in a separate command prompt, you'll be able to identify if thats the issue.

This sounds suspicously similar to my problem, in that i feel like the system/app folder is not deleted, and thus there is not enough space (although the files might be overwritten when pushed and i might be talking crap )

EDIT: I'd like to confirm that indeed, this was my problem, as after editing the script all the files copied no problem (Windows 7 x64), however installing Orange ICS still ended up an error: status 7

Edited by FullXon, 07 January 2013 - 09:03 PM.

[rickywyatt]

ill look at the script and see is i have the same problem

[utternoob]

Updated to 6/1, downloaded all files. Ran tool, daemon starts, then error: device not detected. Think I should have re-installed Intel drivers, but I'm not sure. Device was in debug mode, plugged in and everything

[BlueMoonRising]

 utternoob, on 07 January 2013 - 08:52 PM, said:

Updated to 6/1, downloaded all files. Ran tool, daemon starts, then error: device not detected. Think I should have re-installed Intel drivers, but I'm not sure. Device was in debug mode, plugged in and everything

You don't need to re-install the Intel drivers, try plugging the phone out and back in again.

[FullXon]

Heres a bit more info on my status 7 error, it was due to libc_orig.so, apparently, in the system/lib/arm folder.
Hope that helps

[utternoob]

 BlueMoonRising, on 07 January 2013 - 09:02 PM, said:

You don't need to re-install the Intel drivers, try plugging the phone out and back in again.

I'll try tomorrow, but I'm not sure

[Misadgror]

 BlueMoonRising, on 07 January 2013 - 07:10 PM, said:

Have you installed the small (27MB?) Xolo update? If so remove it first using the tool.

Nope,  haven't  installed that update.  I'm able to root without any problem.

[rickywyatt]

 FullXon, on 07 January 2013 - 09:05 PM, said:

Heres a bit more info on my status 7 error, it was due to libc_orig.so, apparently, in the system/lib/arm folder.
Hope that helps

I'm getting the same error to lol


ill don't no why but ill try and fix it asap

[Tanay Mondal]

plz someone help me.
I tried this app on play, name: [root] Chainfire3D . After restarting it stucked on XOLO logo. Then i tried Fix Bricked. But It's show RED triangle at the time of update & then restarts & again stucked on XOLO logo.

So i tried command prompt, typed "adb shell" , but it's everytime showing device not found.
Plz help.

[rickywyatt]

ok first you need adb so keep typing adb shell once it changes from device not found to $ then open aio to and select downgrade as you have upgraded with the 27mb once you have done that you can then brick fix


please remember if you install the 27mb you have to downgrade before brick fixing

[BlueMoonRising]

 Tanay Mondal, on 08 January 2013 - 01:18 PM, said:

plz someone help me.
I tried this app on play, name: [root] Chainfire3D . After restarting it stucked on XOLO logo. Then i tried Fix Bricked. But It's show RED triangle at the time of update & then restarts & again stucked on XOLO logo.

So i tried command prompt, typed "adb shell" , but it's everytime showing device not found.
Plz help.

Presuming you are rooted, if not have you installed the small Xolo update?

"For Froyo and Gingerbread ONLY. NOT COMPATIBLE with Honeycomb/Ice Cream Sandwich/Jelly Bean !!" this is from the description in the Play Store, do read first before installing apps.

Edit :- damn, Ricky typed faster than me...

Edited by BlueMoonRising, 08 January 2013 - 03:51 PM.

[Tanay Mondal]

yes, my devices is rooted already. i tried that [root] Chainfire3D app. i have not installed the 27 mb update.

[Tanay Mondal]

i tried adb shell many many times, but everytime its showing device not found

[rickywyatt]

did you try to factory rest by any chance?

[Tanay Mondal]

sorry, i am totally noob. after that problem i tried fix bricked only, but at the time of flashing a RED triangle logo appeared & restarted & again stucked on xolo