Xolo X900, Xolo X500, Orange Sandiego Official Tool Kit

[Guest karthiknr]

It now seems to be a ICS build by seeing the bild.prop you attached. But someone who is as good as Ricky, or any other alike, could try it out and guide us then it would be helpful. Coz i don't think anyone here wants to risk bricking their device and not knowing how to get it back in working condition. I personally don't wanna risk it. The tool might be very legitimate but it still requires skill. This is my first android phone and I have never flashed Custom ROMs. If this tool really works, it'll be the first for me.

As for the update.zip of 348MB i think it's the ROM after the 59MB update.

Also, I had a look at the tool, it does have some encryption files which is why i'm optimistic that this tool signs the ROM. Also, users facing problems of rooting after the 59MB update can be solved as the tool also allows to push apk and other files in the ROM after flashing the device. This module of the tool can be used to push files required for root.

When you load the files into the tool kit before flashing it asks for a xml file. The xml file with the update.zip contains the instructions as to how to flash the device. But since it boot-loader locked it wont just flash any ROM. This is where the .bin fiiles come in to sign the ROM before flashing. This is what I think. I may be wrong though. I'm no advanced user.

Do we have any ROMs that someone can try on? I'm a little worried about the missing System, Kernel and other files but I might go ahead and try it. But first as you suggested I think I'll try to push the required files for gaining root.

[Guest Hasan217]

Do we have any ROMs that someone can try on? I'm a little worried about the missing System, Kernel and other files but I might go ahead and try it. But first as you suggested I think I'll try to push the required files for gaining root.

Before you go ahead.... Take a BACKUP!! This is the most important step.

Why not try our own ROM first. The 299 Mb update.zip. See how it works for you. And yes if you're successful at pushing files to your device then maybe users can gain root even after the 59Mb update.

Keep us posted on your progress.. ;)

We can't just flash any ROM on our devices coz all the other ROMs are made for devices running ARM, which might not work properly on our devices using x86. I think there's a link somewhere of Intel's own Jelly Bean ROM. Once you're successful you could try that.

Best Of Luck!

[Guest karthiknr]

Before you go ahead.... Take a BACKUP!! This is the most important step.

Why not try our own ROM first. The 299 Mb update.zip. See how it works for you. And yes if you're successful at pushing files to your device then maybe users can gain root even after the 59Mb update.

Keep us posted on your progress.. ;)

We can't just flash any ROM on our devices coz all the other ROMs are made for devices running ARM, which might not work properly on our devices using x86. I think there's a link somewhere of Intel's own Jelly Bean ROM. Once you're successful you could try that.

Best Of Luck!

I'm making a backup right now. As soon as it gets done,i'll flash our ROM to see if it works or not. I loaded the flash.xml from the custom flash section. The only thing that is bothering me is whether to choose blankphone or fastboot type to flash the phone. I think i'll go with the fastboot.

[Guest BlueMoonRising]

I don't know about anyone else but I'm watching with baited breath...

[Guest shuntgenerator]

http://www.modaco.com/topic/362574-solved-problem-of-screen-flashing-different-colors-after-flashing-updatezip-after-installing-37mb-or-12mb-update-on-xolo-ics-rom/

hope you have a hdmi capable tv and proper cables. just in case

[Guest karthiknr]

I don't know about anyone else but I'm watching with baited breath...

:D Let's just be hopeful. I'm backing up using the flash tool itself but even though i unticked the shared storage/sdcard it still seems to be doing a backup of something called com.android.sharedstoragebackup and it's taking ages to complete. Almost 2 GB backed up now.

 

Edit:

 

I'm starting the flash now. It backed up sdcard also btw.

Here's the image for the custom flash screen. I clicked the load file on the right and chose the flash.xml and arrived here. 

 

Edited December 6, 2013 by karthiknr

[Guest Hasan217]

I don't know about anyone else but I'm watching with baited breath...

 

:D Let's just be hopeful. I'm backing up using the flash tool itself but even though i unticked the shared storage/sdcard it still seems to be doing a backup of something called com.android.sharedstoragebackup and it's taking ages to complete. Almost 2 GB backed up now.

Same here... I'm just waiting for a possibility of flashing a custom ROM.

Was just looking for Custom Jelly Bean ROMs over xda and google, but couldn't get anything. I think RAZR i ROMs should work.... Let's see how this goes.

One step at a time  :D

[Guest kabirsaini2011]

dont use ifwi and osdnx of the tool :P 

[Guest karthiknr]

Too late. Ended up with this error.

I will try removing the erase data part and will try again.

 

 

After removing the erase data part and after registering flash file again,i went ahead and flashed.

 

After the fastboot continue command,it boots into the recovery where a bunch of errors pop saying it cannot mount/open some folders.

I chose to reboot system. It's still showing the Xolo logo. Hopefully it boots up.

 

Edited December 6, 2013 by karthiknr

[Guest kabirsaini2011]

Try to flash moto razr-i's jb if u pass

[Guest Hasan217]

The link for Moto RAZR i on XDA: http://forum.xda-developers.com/showthread.php?t=2174731

If anybody is just as curious as me. :P

[Guest karthiknr]

Looks like it hasn't worked. :(  It's still stuck on the Xolo logo. I'll go into the recovery and install the update.zip from sdcard. 

 

I'm having serious issues now. It looks like the recovery is not able to mount the sdcard partition at all. Data wipe and cache wipe are still possible though.

Any suggestions to flash stock ROM?

Edited December 6, 2013 by karthiknr

[Guest Hasan217]

Looks like it hasn't worked. :(  It's still stuck on the Xolo logo. I'll go into the recovery and install the update.zip from sdcard. 

You could try without the IFWI and OS DnX option, as Kabir suggested, if you still have the urge to go on.... :P

[Guest Hasan217]

Looks like it hasn't worked. :(  It's still stuck on the Xolo logo. I'll go into the recovery and install the update.zip from sdcard. 

 

I'm having serious issues now. It looks like the recovery is not able to mount the sdcard partition at all. Data wipe and cache wipe are still possible though.

Any suggestions to flash stock ROM?

Use the AIO Tool by Ricky

If it doesn't work then try this: http://www.modaco.com/topic/362367-how-to-manually-fixbrick-with-aio-tool-installed/page-2?hl=%2Bfastboot#entry2128649 . The first post.

I have tried this method and it has worked for me.

Edited December 6, 2013 by Hasan217

[Guest karthiknr]

Use the AIO Tool by Ricky

The tool says Device not found. :(

Even if im into droidboot,it says the same.

[Guest Hasan217]

The tool says Device not found. :(

Even if im into droidboot,it says the same.

I thought so... Continue to the next step. It sometimes shows device not connected but still goes further for flashing.

If that also doesn't work go directly to flashing. Hope it works mate!

Edited December 6, 2013 by Hasan217

[Guest kabirsaini2011]

try to flash with osdnx and ifwi of x900

[Guest karthiknr]

Looks like i bricked it or something. The problem according to google and xda is that my partition table is probably messed up. It isn't able to mount the /cache itself. Fastboot works,adb doesn't. The partitions are all messed up.

 

 

After using fastboot to flash update.zip,the android with the gears(or something) turning shows up and then directly goes into recovery with the following messages-

 

E:Can't mount /cache/recovery/command

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

 

And a few more lines like this about /logs as well.

 

Anybody has the slightest idea how to proceed from here?

Edited December 6, 2013 by karthiknr

[Guest BlueMoonRising]

Can you restore the backup? Got to go to work now but I'll try and keep up while there.

[Guest shuntgenerator]

Just sharing something i observed.

with this new piece of tool i can find 4 different connection statuses.

MOS - switched on device connected

POS - Device in droid boot connected

COS - Switched off device connected while keeping volume down pressed

SOC (SOC serial number is displayed)- Simultaneously pressing power and camera briefly while in droidboot all the while keeping the device connected on USB (this mode persists for just 1 min). When entering this mode for the first time a driver gets installed and device manager shows a new device named Medfield under intel group.

Edited December 6, 2013 by shuntgenerator

[Guest karthiknr]

Can you restore the backup? Got to go to work now but I'll try and keep up while there.

No,backup wont work.

 

I had issues with adb,i sorted them and it started working again. This is what i come up with for the filesystem tree.

 

 

 

So basically upon adb ls /system or adb ls /sdcard,i get nothing at all.

It's like it's empty. And there is no /cache,hence the errors of it not being able to mount it.

[Guest BlueMoonRising]

I don't know what stage you're at but would this help http://forum.xda-developers.com/showthread.php?t=1507876&page=5 post 42

Edited December 6, 2013 by BlueMoonRising

[Guest karthiknr]

I don't know what stage you're at but would this help http://forum.xda-developers.com/showthread.php?t=1507876&page=5 post 42

Being a little optimistic,i think that would help ;)  I was going through the flash.xml again and i noticed the "fastboot erase factory". I'm still not sure what that line does,the rest of the flash process seemed pretty normal for me.

 

Also from your link,the order to make it alright would be to flash userdata,cache,boot and system and finally the recovery images again. Do we have a factory image from which i can maybe extract the userdata and the cache images(Considering the boot image is the boot.img from within the update.zip?)? And how would i go about making these images?

 

I really can't thank you enough if this works! :D

 

Edit: I have the boot.img and the recovery.img but i don't have the userdata.img or the cache.img or the system.img, Once i have these images i will use the following commands to make it alright:

fastboot flash userdata userdata.img

fastboot flash cache cache.img

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash recovery recovery.img

 

Correct me if i'm wrong.

 

 

 

 

EDIT:

 

It's fixed now! I did the following things to fix it:

 

1.Boot into the droidboot screen to enable fastboot

2.fastboot erase userdata(It will most likely give you an error)

3.fastboot erase cache

4.fastboot erase system

5.fastboot erase boot

6.fastboot flash boot boot.img(This is the boot.img from within the update.zip)

7.fastboot flash update update.zip

 

After this,it rebooted by itself. There was a flash of the Xolo logo and then the screen went blank. Adb access was there at this point. To make sure i did adb ls /system and all the folders were there.

So now because the update.zip was the 299MB one,i used the HDMI method to do an OTA update and it's all sorted now. 

 

I will check the folders again to see if any memory is missing or has ocupied extra space. 

 

 

Thanks a lot guys!

BlueMoonRising,that link you posted had the right flash/erase order,like i said,can't thank you enough! 

:D 

Edited December 7, 2013 by karthiknr

[Guest darkvicious]

Being a little optimistic,i think that would help ;)  I was going through the flash.xml again and i noticed the "fastboot erase factory". I'm still not sure what that line does,the rest of the flash process seemed pretty normal for me.

 

Also from your link,the order to make it alright would be to flash userdata,cache,boot and system and finally the recovery images again. Do we have a factory image from which i can maybe extract the userdata and the cache images(Considering the boot image is the boot.img from within the update.zip?)? And how would i go about making these images?

 

I really can't thank you enough if this works! :D

 

Edit: I have the boot.img and the recovery.img but i don't have the userdata.img or the cache.img or the system.img, Once i have these images i will use the following commands to make it alright:

fastboot flash userdata userdata.img

fastboot flash cache cache.img

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash recovery recovery.img

 

Correct me if i'm wrong.

 

 

 

 

EDIT:

 

It's fixed now! I did the following things to fix it:

 

1.Boot into the droidboot screen to enable fastboot

2.fastboot erase userdata(It will most likely give you an error)

3.fastboot erase cache

4.fastboot erase system

5.fastboot erase boot

6.fastboot flash boot boot.img(This is the boot.img from within the update.zip)

7.fastboot flash update update.zip

 

After this,it rebooted by itself. There was a flash of the Xolo logo and then the screen went blank. Adb access was there at this point. To make sure i did adb ls /system and all the folders were there.

So now because the update.zip was the 299MB one,i used the HDMI method to do an OTA update and it's all sorted now. 

 

I will check the folders again to see if any memory is missing or has ocupied extra space. 

 

 

Thanks a lot guys!

BlueMoonRising,that link you posted had the right flash/erase order,like i said,can't thank you enough! 

 

you can share the zip update of 299Mb

:D 

Edited December 7, 2013 by darkvicious

[Guest BlueMoonRising]

@karthiknr, glad you got it sorted although you do know I was winging it don't you? I'm no developer I'm afraid. I don't know if I should ask but are you going to try again :) ? If so maybe use the 299MB zip first?

 

@darkvicious, I think you managed to put your question within the quote but if you're looking for the 299MB zip it's here :- https://www.dropbox.com/s/1a7vtezns1l49a0/update.zip