Guest mohit.2 Posted December 26, 2013 Report Share Posted December 26, 2013 well, My mate has some little upgrade. He figured out the stuff and flashed gingerbread back. Now, he is preparing for jellybean. i also want to flash gb back help me please Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 4, 2014 Report Share Posted January 4, 2014 Yes, but not enough ; When I open the phone, vibrate 5 , then saw the intel logo, then there is no screen.HDMI connection TV Show and pictures. well there's a problem with the ifwi file, maybe its not for x900 or did u notice the intel logo its different i have other ifwi file but they are not working too but i vibrate 2 times if i flash my phone from those file but dont boot up Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 4, 2014 Report Share Posted January 4, 2014 i think the files in the x500 & x900 flasher zip is the files for x500 as two filename start with lexug which i think stand for the intel processer code name present in xolo x500 Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 4, 2014 Report Share Posted January 4, 2014 i have flash.xml file and all the bin files and i think they are for xolo x900 as they are named blb..... which i think means blackbay codename intel processer but they are not working for me any body want to try please ask :unsure: :unsure: :huh: Link to comment Share on other sites More sharing options...
Guest shuntgenerator Posted January 19, 2014 Report Share Posted January 19, 2014 Disclaimer : Total n00b here! Some insights... "An SOC's Boot ROM is responsible for setting up the SOC to a very basic level (using the BCT), setting up SDRAM and figuring out where the boot loader is. This is typically capable of loading the boot loader from USB, SPI flash, UART, eMMC / SD card and NAND flash. The Boot ROM is part of the SOC and cannot be changed other than by making a new chip. Some Boot ROMs include security features which require that boot code be signed by a special tool. Typically, Boot ROM consists of 16-32 KB of code." Trying to load an unlocked 'boot loader' from SD card might work? http://www.chromium.org/chromium-os/firmware-update Our SoC mode is similar to their emergency mode? http://forums.wpcentral.com/huawei-ascend-w1/229445-those-who-get-their-w1-market-locked-china.html There are multiple ways of booting up an SoC? http://www.design-reuse.com/articles/21308/serial-boot-soc.html Link to comment Share on other sites More sharing options...
Guest Hasan217 Posted January 29, 2014 Report Share Posted January 29, 2014 I came across this pdf file by intel which describes more features of the chipset in our devices. I found this page in the pdf file. This means there are more than one tool required to flash the device. The one we have here is I think the 'Mfg. Phone Flashing Tool' as shown in the screenshot. This is the link to the pdf file: https://www.dropbox.com/s/eax0luedqdoynvj/IA%20based%20smartphone%20platforms.pdf Link to comment Share on other sites More sharing options...
Guest BlueMoonRising Posted January 29, 2014 Report Share Posted January 29, 2014 (edited) I came across this pdf file by intel which describes more features of the chipset in our devices. I found this page in the pdf file. This means there are more than one tool required to flash the device. The one we have here is I think the 'Mfg. Phone Flashing Tool' as shown in the screenshot. This is the link to the pdf file: https://www.dropbox.com/s/eax0luedqdoynvj/IA%20based%20smartphone%20platforms.pdf I do believe you're correct, we need the 2nd one "Firmware Stitching and Flashing Tools" to possibly access the bootloader. Any suggestions? Who first posted the 'Mfg. Phone Flashing Tool'? Could they get access? Edit :- well spotted by the way ;) Edited January 29, 2014 by BlueMoonRising Link to comment Share on other sites More sharing options...
Guest Hasan217 Posted January 29, 2014 Report Share Posted January 29, 2014 I do believe you're correct, we need the 2nd one "Firmware Stitching and Flashing Tools" to possibly access the bootloader. Any suggestions? Who first posted the 'Mfg. Phone Flashing Tool'? Could they get access? Edit :- well spotted by the way ;) Well I did a google search by the tool name and I get this: http://phone-flash-tool.software.informer.com/versions/ The version we have is actually an older version. Version 4.1 is the latest. I guess Intel and Lava are holding back these tools from the users. We can get our hands on these tools only if they are leaked from these 2 sources. If Kabir Saini, the creator of the thread can get these tools and share it with us then, maybe we can have a chance of unlocking the boot-loader. Link to comment Share on other sites More sharing options...
Guest Jul655 Posted January 29, 2014 Report Share Posted January 29, 2014 here is MFG flash tool : https://mega.co.nz/#F!0UlDnLLR!IuQdqFqT-oIXtvRlQNtLBw But it seems like quite the same as phone flash tool. I will try ... Otherwise I have the same problem as mohit.2 5 Vibration that boot, IFWI with 2 vibrations that doesn't boot unfortunatly Link to comment Share on other sites More sharing options...
Guest Hasan217 Posted January 29, 2014 Report Share Posted January 29, 2014 here is MFG flash tool : https://mega.co.nz/#F!0UlDnLLR!IuQdqFqT-oIXtvRlQNtLBw But it seems like quite the same as phone flash tool. I will try ... Otherwise I have the same problem as mohit.2 5 Vibration that boot, IFWI with 2 vibrations that doesn't boot unfortunatly No your tool is different. Might be the right tool actually. The main setup file 'ManufacturingFlashTool' is of 5MB whereas the file uploaded in the first pot is of 10MB. The difference can be known by the size itself. But i believe you will need some files from the first post of this thread to flash your device. Like: 'IFWI_GI_DV1.0_v0E.BB_CAAB_PPD', 'LEXUG-droidboot_ota-CAAK-POS', 'CAAB-Signed_PNW_D1_FWR_DnX.FD.07', 'CAAB-Signed_PNW_D1_OSR_DnX.0D.08' and 'LEXUG-recovery_ota' Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 29, 2014 Report Share Posted January 29, 2014 some people 3 months ago hacked into ftp server of xolo and released the password and username in public which has changed no i downloaded the most of the file to my google drive and they have the same phone flash tool. ican share my drive files if anyone want to see i visited xolo servive centre and those assholes dont know how to repair it they says its dead nowbut niw i have given it to a private service center auth. by xolo hope that they can repair iti think the problem is with the gf codes we are using with the flasher there is a post where rick tried flasher with different codes Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 29, 2014 Report Share Posted January 29, 2014 www.modaco.com/topic/355005-the-san-diego-hacking-topic-root-progress-etc/page-33read this topic Link to comment Share on other sites More sharing options...
Guest BlueMoonRising Posted January 29, 2014 Report Share Posted January 29, 2014 www.modaco.com/topic/355005-the-san-diego-hacking-topic-root-progress-etc/page-33 read this topic I never realised Ricky had access to an official flasher. That was before my time on here. Link to comment Share on other sites More sharing options...
Guest Jul655 Posted January 29, 2014 Report Share Posted January 29, 2014 (edited) i think the problem is with the gf codes we are using with the flasher there is a post where rick tried flasher with different codes For sure, when I try to flash "IFWI_GI_DV1.0_v0E.BB_CAAB_PPD" with the following GP flag : "0x80000094" that does not work. There are 5 vibrations and that is all. However with "0x80000005" that works. So for the IFWI with 2 vibrations .... Edited January 29, 2014 by Jul655 Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 29, 2014 Report Share Posted January 29, 2014 For sure, when I try to flash "IFWI_GI_DV1.0_v0E.BB_CAAB_PPD" with the following GP flag : "0x80000094" that does not work. There are 5 vibrations and that is all. However with "0x80000005 " that works. So for the IFWI with 2 vibrations .... try using gt code 0x80000023, 0x80000080, 0x80000041 Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 29, 2014 Report Share Posted January 29, 2014 i think different ifwi need different gt codes i asked intel guys for the problem but they are not helping and some people at xda have done the same thing and they know more about this but are not replying now Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 29, 2014 Report Share Posted January 29, 2014 if anyone having different ifwi and droidboot pls post Link to comment Share on other sites More sharing options...
Guest Jul655 Posted January 29, 2014 Report Share Posted January 29, 2014 (edited) http://support.moulnisky.com/index.php?dir=Xolo/Xolo%20X900/ Each are delivered with a different update.zip X900: Update.zip = 329 009 Ko IFWI: IFWI_PR3.3_v05.A5_CAAK_PPD_ARB.bin FW_DNX: CAAK_SIGNED_PNW_D1_FWR_DnX.FD.05.bin OS_DNX: CAAK-SIGNED_PNW_D1_OSR_DnX.0D.07.bin RECOVERY: BKB4ATI-recovery_ota.img KBOOT: BKB4ATI-droidboot_ota-CAAK-POS.bin X900new: Update.zip = 323 653 Ko IFWI: IFWI_PR3.3_v05.B1_CAAK_PPD.bin FW_DNX: CAAK-Signed_PNW_D1_FWR_DnX.FD.07.bin OS_DNX: CAAK-Signed_PNW_D1_OSR_DnX.0D.08.bin RECOVERY: BKB4ATI-recovery_ota.img KBOOT: BKB4ATI-droidboot_ota-CAAK-POS.bin I put in green colour, the difference of name, however the size is same. I tried with these different packages and : 0x80000023 : 12% INFO : Port 0/1/5 #0: IFW flash started - SN : AA30B98FAB484785 01/29/14 18:43:55.838 INFO : Disabling xFSTK wipe out ifwi option 01/29/14 18:43:55.838 INFO : Disabling xFSTK Misc DnX 01/29/14 18:43:56.043 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 Error Code: 0 - Success 01/29/14 18:43:56.043 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 PASS 01/29/14 18:43:56.043 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 Firmware download skipped. Continuing to OS... 01/29/14 18:44:14.158 WARNING: Port 0/1/5 #0: Retry IFW Flashing - Serial: AA30B98FAB484785 01/29/14 18:44:15.158 WARNING: Port 0/1/5 #0: Retry IFW Flashing - Serial: AA30B98FAB484785 01/29/14 18:44:16.158 ERROR : Port 0/1/5 #0: IFW flash failed - SN : AA30B98FAB484785 0x80000041 : 12% Port 0/1/5 #0: IFW flash started - SN : AA30B98FAB484785 01/29/14 18:42:21.205 INFO : Disabling xFSTK wipe out ifwi option 01/29/14 18:42:21.205 INFO : Disabling xFSTK Misc DnX 01/29/14 18:42:21.410 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 FW download is in progress ... 01/29/14 18:42:21.419 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 4 01/29/14 18:42:23.461 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 Battery power is okay, continue FW download ... 01/29/14 18:42:23.463 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 8 01/29/14 18:42:23.465 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 12 01/29/14 18:42:23.580 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 16 01/29/14 18:42:24.083 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 20 01/29/14 18:42:24.141 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 24 01/29/14 18:42:24.198 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 28 01/29/14 18:42:24.256 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 32 01/29/14 18:42:24.314 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 36 01/29/14 18:42:24.364 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 40 01/29/14 18:42:24.511 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 44 01/29/14 18:42:24.645 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 48 01/29/14 18:42:24.783 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 52 01/29/14 18:42:24.809 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 56 01/29/14 18:42:25.274 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 60 01/29/14 18:42:25.331 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 64 01/29/14 18:42:25.389 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 68 01/29/14 18:42:25.447 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 72 01/29/14 18:42:25.505 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 76 01/29/14 18:42:25.554 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 80 01/29/14 18:42:25.703 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 84 01/29/14 18:42:25.838 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 88 01/29/14 18:42:25.977 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 92 01/29/14 18:42:25.995 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 100 01/29/14 18:42:25.995 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 Error Code: 0 - Success 01/29/14 18:42:25.996 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 PASS 01/29/14 18:42:25.996 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 Firmware download completed. Continuing to OS... 01/29/14 18:42:44.097 WARNING: Port 0/1/5 #0: Retry IFW Flashing - Serial: AA30B98FAB484785 01/29/14 18:42:45.098 WARNING: Port 0/1/5 #0: Retry IFW Flashing - Serial: AA30B98FAB484785 01/29/14 18:42:46.098 ERROR : Port 0/1/5 #0: IFW flash failed - SN : AA30B98FAB484785 0x80000080 : 25%, Port 0/1/5 #0: IFW flash started - SN : AA30B98FAB484785 01/29/14 18:44:50.797 INFO : Disabling xFSTK wipe out ifwi option 01/29/14 18:44:50.797 INFO : Disabling xFSTK Misc DnX 01/29/14 18:44:51.003 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 FW download is in progress ... 01/29/14 18:44:51.012 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 4 01/29/14 18:44:53.054 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 Battery power is okay, continue FW download ... 01/29/14 18:44:53.056 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 8 01/29/14 18:44:53.058 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 12 01/29/14 18:44:53.173 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 16 01/29/14 18:44:53.677 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 20 01/29/14 18:44:53.734 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 24 01/29/14 18:44:53.793 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 28 01/29/14 18:44:53.851 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 32 01/29/14 18:44:53.908 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 36 01/29/14 18:44:53.958 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 40 01/29/14 18:44:54.105 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 44 01/29/14 18:44:54.244 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 48 01/29/14 18:44:54.383 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 52 01/29/14 18:44:54.410 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 56 01/29/14 18:44:54.873 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 60 01/29/14 18:44:54.931 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 64 01/29/14 18:44:54.988 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 68 01/29/14 18:44:55.046 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 72 01/29/14 18:44:55.104 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 76 01/29/14 18:44:55.154 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 80 01/29/14 18:44:55.301 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 84 01/29/14 18:44:55.436 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 88 01/29/14 18:44:55.574 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 92 01/29/14 18:44:55.592 INFO : Port 0/1/5 #0: XFSTK-PROGRESS SN: AA30B98FAB484785 100 01/29/14 18:44:55.592 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 Error Code: 0 - Success 01/29/14 18:44:55.592 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 PASS 01/29/14 18:44:55.593 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 Firmware only download completed. 01/29/14 18:44:56.693 INFO : Port 0/1/5 #0: IFW flash success - SN : AA30B98FAB484785 01/29/14 18:47:55.833 ERROR : Port 0/1/5 #0: Device on port 0/1/5 #0 timeout to enum adb (TIMEOUT = 180) I got same results for these 2 packages. Edited January 29, 2014 by Jul655 Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 29, 2014 Report Share Posted January 29, 2014 try using gt code 0x80000023, 0x80000080, 0x80000041 http://support.moulnisky.com/index.php?dir=Xolo/Xolo%20X900/ Each are delivered with a different update.zip X900: Update.zip = 329 009 Ko IFWI: IFWI_PR3.3_v05.A5_CAAK_PPD_ARB.bin FW_DNX: CAAK_SIGNED_PNW_D1_FWR_DnX.FD.05.bin OS_DNX: CAAK-SIGNED_PNW_D1_OSR_DnX.0D.07.bin RECOVERY: BKB4ATI-recovery_ota.img KBOOT: BKB4ATI-droidboot_ota-CAAK-POS.bin X900new: Update.zip = 323 653 Ko IFWI: IFWI_PR3.3_v05.B1_CAAK_PPD.bin FW_DNX: CAAK-Signed_PNW_D1_FWR_DnX.FD.07.bin OS_DNX: CAAK-Signed_PNW_D1_OSR_DnX.0D.08.bin RECOVERY: BKB4ATI-recovery_ota.img KBOOT: BKB4ATI-droidboot_ota-CAAK-POS.bin I put in green colour, the difference of name, however the size is same. I tried with these different packages and : 0x00000023 : 12% 0x00000041 : 12% 0x00000080 : 25%, I got same results for these 2 packages. i said gt flag 0x80000023 check yourself and try again :(:blink::(:(:(:(:lol::D:D:D:lol::( Link to comment Share on other sites More sharing options...
Guest Jul655 Posted January 29, 2014 Report Share Posted January 29, 2014 Message edited, I made mistakes Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 29, 2014 Report Share Posted January 29, 2014 I never realised Ricky had access to an official flasher. That was before my time on here. www.modaco.com/topic/355005-the-san-diego-hacking-topic-root-progress-etc/page-45 Link to comment Share on other sites More sharing options...
Guest BlueMoonRising Posted January 29, 2014 Report Share Posted January 29, 2014 http://support.moulnisky.com/index.php?dir=Xolo/Xolo%20X900/ Each are delivered with a different update.zip X900: Update.zip = 329 009 Ko IFWI: IFWI_PR3.3_v05.A5_CAAK_PPD_ARB.bin FW_DNX: CAAK_SIGNED_PNW_D1_FWR_DnX.FD.05.bin OS_DNX: CAAK-SIGNED_PNW_D1_OSR_DnX.0D.07.bin RECOVERY: BKB4ATI-recovery_ota.img KBOOT: BKB4ATI-droidboot_ota-CAAK-POS.bin X900new: Update.zip = 323 653 Ko IFWI: IFWI_PR3.3_v05.B1_CAAK_PPD.bin FW_DNX: CAAK-Signed_PNW_D1_FWR_DnX.FD.07.bin OS_DNX: CAAK-Signed_PNW_D1_OSR_DnX.0D.08.bin RECOVERY: BKB4ATI-recovery_ota.img KBOOT: BKB4ATI-droidboot_ota-CAAK-POS.bin I put in green colour, the difference of name, however the size is same. 01/29/14 18:44:55.593 INFO : Port 0/1/5 #0: XFSTK-STATUS SN: AA30B98FAB484785 Firmware only download completed. 01/29/14 18:44:56.693 INFO : Port 0/1/5 #0: IFW flash success - SN : AA30B98FAB484785 01/29/14 18:47:55.833 ERROR : Port 0/1/5 #0: Device on port 0/1/5 #0 timeout to enum adb (TIMEOUT = 180) Doesn't that last line in red just indicate that it can't find adb? Link to comment Share on other sites More sharing options...
Guest Hasan217 Posted January 30, 2014 Report Share Posted January 30, 2014 Has anybody tried installing CWM or TWRP on our devices? I think the tab called 'Provision' can be used to install custom recovery on the device. I am not sure if that will Brick the device though. Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted January 30, 2014 Report Share Posted January 30, 2014 Has anybody tried installing CWM or TWRP on our devices? I think the tab called 'Provision' can be used to install custom recovery on the device. I am not sure if that will Brick the device though. i dnt think it will work Link to comment Share on other sites More sharing options...
Guest mohit.2 Posted February 2, 2014 Report Share Posted February 2, 2014 i thin we all should contact intel 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