• Announcements

    • PaulOBrien

      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 software Nintendo 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 author ISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • PaulOBrien

      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.
rickywyatt

[Tool]AIO Tool for San Diego and xolo

1297 posts in this topic

nah not working, let me tell you guys step by step what I've done: 1) I installed any adb/superuser etc. Then ran 'San Diego' from the C drive. 2) The Tool successfully pushed adb insecure on to my phone, but then there was a one line message saying: 'run adb, click box, unplug mobile then replug usb, then press any key to continue' 3) I go into my phone apps, run adb insecure, and it gives me that stupid message about 'superuser access is needed, but could not be acquired. are you rooted and did you give permission?' 4) I ignore it and carry on by pressing any key. 5) I get the full menu and press '7', 6) the shell says pushing busybox, pushing su binary, pushing superuser app, etc I get the restore option, so I hit restore. 7) Shell says 'successful, going to reboot device! Waiting for device to show up again...' 8) THEN I GET THIS MESSAGE:

mount: Operation not permitted

mv: can't create '/system/xbin/su': Read-only file system

mv: can't create '/system/app/Superuser.apk': Read-only file system

cp: can't create '/system/xbin/busybox': Read-only file system

Unable to chmod /system/xbin/su: No such file or directory

Unable to chmod /system/xbin/su: No such file or directory

Unable to chmod /system/app/Superuser.apk: No such file or directory

Unable to chmod /system/xbin/busybox: No such file or directory

rm failed for /data/local.prop, No such file or directory

reboot: Operation not permitted

You can close all open command-prompts now!

After reboot all is done! Have fun!

Bin4ry

Press any key to continue . . .

0

Share this post


Link to post
Share on other sites

In fact here's the full message from start of my process to finish...:

Please make your decision:7

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

=============================================

[ This script will root your Android ]

[ phone with adb restore function Script ]

[ by Bin4ry thanks toGoroh_kun and tkymgr ]

[ for the idea Edited by Ricky wyatt for ]

[ Orange San diego ]

=============================================

New Rooting Your Phone

Press any key to continue . . .

Pushing busybox....

3770 KB/s (1085140 bytes in 0.281s)

Pushing su binary ....

2899 KB/s (23755 bytes in 0.008s)

Pushing Superuser app

3973 KB/s (1468798 bytes in 0.361s)

Making busybox runable ...

Now unlock your device and confirm the restore operation.

Please look at your device and click RESTORE!

If all is successful i will tell you, if not this shell will run forever.

Running ...

Successful, going to reboot your device!

Waiting for device to show up again....

mount: Operation not permitted

mv: can't create '/system/xbin/su': Read-only file system

mv: can't create '/system/app/Superuser.apk': Read-only file system

cp: can't create '/system/xbin/busybox': Read-only file system

Unable to chmod /system/xbin/su: No such file or directory

Unable to chmod /system/xbin/su: No such file or directory

Unable to chmod /system/app/Superuser.apk: No such file or directory

Unable to chmod /system/xbin/busybox: No such file or directory

rm failed for /data/local.prop, No such file or directory

reboot: Operation not permitted

You can close all open command-prompts now!

After reboot all is done! Have fun!

Bin4ry

Press any key to continue . . .

0

Share this post


Link to post
Share on other sites

Maybe it's time to start from scratch by reinstalling the Xolo ICS rom. You may need to clear cache as well, do not install SU from the playstore.

0

Share this post


Link to post
Share on other sites

Uninstall the one you downloaded from the playstore (both if necessary) and run root again. Don't forget to kill any instance of adb first.

^ This.

To root, all you need is on modaco. Try reflashing Xolo ICS, by enabling debugging mode if not enabled, then:


fastboot.exe -i 0x8087 flash update update.zip

Your settings and installed apps will remain unchanged by using this.

Finally, try my root/unroot kit:

0

Share this post


Link to post
Share on other sites

thanks

Edited by vaibhav D
0

Share this post


Link to post
Share on other sites

the 37 mb update is visible now. should i update my phone ?

Edited by vaibhav D
0

Share this post


Link to post
Share on other sites

I get the same error as firestorm79,

Please make your decision:7

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

=============================================

[ This script will root your Android ]

[ phone with adb restore function Script ]

[ by Bin4ry thanks toGoroh_kun and tkymgr ]

[ for the idea Edited by Ricky wyatt for ]

[ Orange San diego ]

=============================================

New Rooting Your Phone

Press any key to continue . . .

Pushing busybox....

3770 KB/s (1085140 bytes in 0.281s)

Pushing su binary ....

2899 KB/s (23755 bytes in 0.008s)

Pushing Superuser app

3973 KB/s (1468798 bytes in 0.361s)

Making busybox runable ...

Now unlock your device and confirm the restore operation.

Please look at your device and click RESTORE!

If all is successful i will tell you, if not this shell will run forever.

Running ...

Successful, going to reboot your device!

Waiting for device to show up again....

mount: Operation not permitted

mv: can't create '/system/xbin/su': Read-only file system

mv: can't create '/system/app/Superuser.apk': Read-only file system

cp: can't create '/system/xbin/busybox': Read-only file system

Unable to chmod /system/xbin/su: No such file or directory

Unable to chmod /system/xbin/su: No such file or directory

Unable to chmod /system/app/Superuser.apk: No such file or directory

Unable to chmod /system/xbin/busybox: No such file or directory

rm failed for /data/local.prop, No such file or directory

reboot: Operation not permitted

You can close all open command-prompts now!

After reboot all is done! Have fun!

Bin4ry

Press any key to continue . . .

............................................................................................................................

I am not sure if a working fix has been posted,

can someone help me step by step....?

sorry complete n00b,

i've tried glossy's version as well, similar error. During the boot, everything fails and there is no second boot and no root!

I have ICS 4.0.4, did everything with USB debugging enabled and INTEL driver ver 1.1.5

I have no idea what I am doing wrong.

Please help..

0

Share this post


Link to post
Share on other sites

I get the same error as firestorm79,

I have no idea what I am doing wrong.

Please help..

Have you tried killing any instance of adb running and trying the tool again?

Plug the phone out first and reboot(make sure the phone is fully finished booting).

0

Share this post


Link to post
Share on other sites

Looks to me like it has been blocked by the updates that have been pushed out. Did you install any?

0

Share this post


Link to post
Share on other sites

@bluemoonrising

I did, killed adb, tried many times over....

either gets stuck at

If all is successful i will tell you, if not this shell will run forever.

or the usual happens. Tried rebooting as well.

........

@utternoob

I haven't updated anything as far as i know.

........

@glossy

By stock xolo, u mean a factory reset?

Would it delete all my apps and data?

But no I haven't tried this yet

.........

and thank you guys for your response... Should i reset it to factory?

1

Share this post


Link to post
Share on other sites

@bluemoonrising

I did, killed adb, tried many times over....

either gets stuck at

If all is successful i will tell you, if not this shell will run forever.

or the usual happens. Tried rebooting as well.

........

@utternoob

I haven't updated anything as far as i know.

........

@glossy

By stock xolo, u mean a factory reset?

Would it delete all my apps and data?

But no I haven't tried this yet

.........

and thank you guys for your response... Should i reset it to factory?

Hello :)

Your data, settings and apps are safe, unless you intentionally wipe /cache and /data partitions, which you won't when you re-install the Xolo ROM via fastboot :)

0

Share this post


Link to post
Share on other sites

@bluemoonrising

I did, killed adb, tried many times over....

either gets stuck at

If all is successful i will tell you, if not this shell will run forever.

or the usual happens. Tried rebooting as well.

........

@utternoob

I haven't updated anything as far as i know.

........

@glossy

By stock xolo, u mean a factory reset?

Would it delete all my apps and data?

But no I haven't tried this yet

.........

and thank you guys for your response... Should i reset it to factory?

boot into fastboot then open c:\sandiego\tools then click command prompt and then type:

fastboot -i 0x8087 flash update c:\sandiego\tools\xolo\update.zip

(make sure you have the "xolo uppdate.zip" in c:\sandiego\tools\xolo)

then go into recovery on phone and choose the update.zip

0

Share this post


Link to post
Share on other sites

I dont think i have the update.zip i used with me anymore, so i download a new one or does it come with modaco package?

Edited by Inumanoj
0

Share this post


Link to post
Share on other sites

I dont think i have the update.zip i used with me anymore, so i download a new one or does it come with modaco package?

You can download from here :- http://www.xolo.in/xolocare/xolo-x900-software-upgrade

Do not accept any more updates once you're sorted.

0

Share this post


Link to post
Share on other sites

Thank you! This fixed my problem! I was searching for a solution for quite a while now!

Cheers to guys! :)

0

Share this post


Link to post
Share on other sites

Just a couple more questions guys,

1) Signal booster didn't work for me

fails to copy and is unable to chmod

2) Enable Sd card and Enable Mass storage

aren't they the same?

Which one should I choose, if I want to use a micro sd in my phone? What's the maximum allowed?

0

Share this post


Link to post
Share on other sites

Just a couple more questions guys,

1) Signal booster didn't work for me

fails to copy and is unable to chmod

2) Enable Sd card and Enable Mass storage

aren't they the same?

Which one should I choose, if I want to use a micro sd in my phone? What's the maximum allowed?

For question 1) :-

Signal boost files are here in case you don't have them already :- Download

Copy the SignalBoost folder you downloaded into C:\SanDiego\tools. Then create a new text document and paste the following into it ;-

adb.exe kill-server

adb.exe start-server

adb.exe wait-for-device

adb remount

sleep 5

adb push C:\SanDiego\tools\SignalBoost\app\signalboost.apk /system/app

adb push C:\SanDiego\tools\SignalBoost\etc\rild.conf /system/etc

adb push C:\SanDiego\tools\SignalBoost\lib\libganril.so /system/lib

adb push C:\SanDiego\tools\SignalBoost\lib\libkineto.so /system/lib

adb push C:\SanDiego\tools\SignalBoost\lib\librilswitch.so /system/lib

adb reboot

sleep 5

adb.exe kill-server

save the text file into C:\SanDiego\tools and rename it to a .bat file. Plug your phone in and run the .bat file you just created.

You can of course just copy & paste over the AIO version in the sandiego.bat

As for question 2) I think the mass storage option combines the 2 storage areas(USB & SD card) together. Presumably you need to enable the SD card first before using the mass storage option. Perhaps someone else could confirm?

I think it's possible to use a 64GB micro SD card but given the cost I don't believe anyone has been brave enough to try yet. I'm thinking of getting a 32GB card and enabling it myself, I'm just trying to decide which of the cards on Amazon are actually real class 10 or fake lower spec ones relabeled :angry:

Edit :- reading the manual(something I suggest to other people but didn't do myself, whoops) it says "This will install an application on your phone so you can open it to enable mass storage or mtp". So I'm guessing it's not massively important.

In fact I think Ricky did discover a way(clever sod that he is) to combine the storage areas into one big partition but he wouldn't publish it in public. It was very technical and he didn't want everybody trying it and permanently bricking their phones, and especially didn't want all the inevitable PMs that would result(can't blame him on that). If you fancy trying it you would need to PM him and ask pretty please.

Edited by BlueMoonRising
0

Share this post


Link to post
Share on other sites

i create

For question 1) :-

Signal boost files are here in case you don't have them already :- Download

Copy the SignalBoost folder you downloaded into C:\SanDiego\tools. Then create a new text document and paste the following into it ;-

adb.exe kill-server

adb.exe start-server

adb.exe wait-for-device

adb remount

sleep 5

adb push C:\SanDiego\tools\SignalBoost\app\signalboost.apk /system/app

adb push C:\SanDiego\tools\SignalBoost\etc\rild.conf /system/etc

adb push C:\SanDiego\tools\SignalBoost\lib\libganril.so /system/lib

adb push C:\SanDiego\tools\SignalBoost\lib\libkineto.so /system/lib

adb push C:\SanDiego\tools\SignalBoost\lib\librilswitch.so /system/lib

adb reboot

sleep 5

adb.exe kill-server

save the text file into C:\SanDiego\tools and rename it to a .bat file. Plug your phone in and run the .bat file you just created.

You can of course just copy & paste over the AIO version in the sandiego.bat

As for question 2) I think the mass storage option combines the 2 storage areas(USB & SD card) together. Presumably you need to enable the SD card first before using the mass storage option. Perhaps someone else could confirm?

I think it's possible to use a 64GB micro SD card but given the cost I don't believe anyone has been brave enough to try yet. I'm thinking of getting a 32GB card and enabling it myself, I'm just trying to decide which of the cards on Amazon are actually real class 10 or fake lower spec ones relabeled :angry:

Edit :- reading the manual(something I suggest to other people but didn't do myself, whoops) it says "This will install an application on your phone so you can open it to enable mass storage or mtp". So I'm guessing it's not massively important.

In fact I think Ricky did discover a way(clever sod that he is) to combine the storage areas into one big partition but he wouldn't publish it in public. It was very technical and he didn't want everybody trying it and permanently bricking their phones, and especially didn't want all the inevitable PMs that would result(can't blame him on that). If you fancy trying it you would need to PM him and ask pretty please.

i rename the text document file and rename it to a .bat file. Plug my phone but when i open the file he open in text document nothing is happening .........
0

Share this post


Link to post
Share on other sites

You are double clicking the bat file and not just editing are you? Don't take this as sarcasm as I don't know your level of understanding.

Have you got the files listed in the bat file in the folders noted? Increase the sleep time (the second to last line) to 20 from 5 to give you a bit more time to see what messages you're getting.

0

Share this post


Link to post
Share on other sites

I managed to root my phone using this tool, but some other things will not work. For instance the Kernel mods and flibblesan's tweaks. Oddly, the GL drivers worked fine.

I am wondering if the 27MB update had something to do with this. I downgraded by using the update.zip and the stock recovery, but perhaps the downgrade didn't remove all the changes?

0

Share this post


Link to post
Share on other sites

I managed to root my phone using this tool, but some other things will not work. For instance the Kernel mods and flibblesan's tweaks. Oddly, the GL drivers worked fine.

I am wondering if the 27MB update had something to do with this. I downgraded by using the update.zip and the stock recovery, but perhaps the downgrade didn't remove all the changes?

If you managed to get Xolo ICS on to it, the next thing after rooting would be to add flibblesans mods. They SHOULD install fine normally(ensure adb is dead first), did you do anything else in between?
0

Share this post


Link to post
Share on other sites

If you managed to get Xolo ICS on to it, the next thing after rooting would be to add flibblesans mods. They SHOULD install fine normally(ensure adb is dead first), did you do anything else in between?

Flibblesan's mod bricks it and I have to reinstall ICS from recovery. So the thing I should be doing is making sure adb insecure is dead before I install the other mods?

0

Share this post


Link to post
Share on other sites

Flibblesan's mod bricks it and I have to reinstall ICS from recovery. So the thing I should be doing is making sure adb insecure is dead before I install the other mods?

OK I think it's working now. I installed Flibble before the OpenGL drivers. Still have to see about the kernel tweaks.

0

Share this post


Link to post
Share on other sites

Couldn't help you with the kernel tweaks as not only have I never used them I don't even know what they're for. :blush:

What are they exactly(or even roughly)?

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-2016. MoDaCo uses IntelliTxt technology.