Alright, I own a TCT Alcatel One Touch 918/Alcatel OT-918/T-Mobile Move 2 android device. Now, I have rooted it before, after a while it went into the startup loop, I sent it to repair, and now apparently they upgraded software and it's working fine, however when I try to use scatter.txt and recovery.img that I used before to root it with FlashTool, I get an error "Can not find USB port...", now, I am trying to find a specific scatter for my phone, I have all the drivers installed, although when I tried to install with alternative methods I get "Device tree not found" error, anyway, I need a scatter file, so could someone provide me with ways of getting them for a certain device, please?
Thanks!
Hello,
I was asked to forward my problem here so here it goes:
Not a long time ago I bought Asus ME302C FHD 10 and tried to root it. I followed a guide but I can't paste link just now.
Anyhow, the guide told me to flash rooted system image. I did every step correctly except that after i rebooted it, my device got stuck on logo screen, sometimes saying "no command".
I would like to undo that by getting unrooted system image for my device or rather get a working rooted system image. I am not sure about other possibilities as I am not experienced in android rooting or anything related. I do have fastboot up and working.
Thank you a lot in advance.
Edit: I figured out that Asus website has factory system images, however I don't really know which one to use because they all are for different countries and I am not sure what device is mine. Is there a way to check parameters of your device without booting it?
Edit2: I messed with the device more and found out that adb doesn't recognize device, as in, running 'adb devices' nothing gets listed. However, 'fastboot devices' does output my device, not sure where the problem is. Also, firmwares listed on asus website are zipped files and I don't know how to flash them. I tried 'fastboot flash system zippedfile.zip' but it would give me an error.
Solved
After few sleepless nights and loads of browser tabs opened I finally managed to fix my device.
All I needed was to use a different SKU firmware from Asus website. Now I can finally boot it thanks to XDA developers team and their useful information on the forums.
So, here is the firmware flash guide for B15Q. It assumes either a Win7 x86 machine or a x64 with driver signature verification disabled (but Win8/8.1 in any variant or W7x64 is NOT RECOMMENDED).
I assume no warranty for bricked devices, especially not if you manage to kill your PRELOADER or DSP_BL. Double and triple check before downloading.
0) Driver and toolkit setup
Get the driver set, scatter file and spFlashTool from this thread: http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774
Remove back shell from phone, remove battery (!)
Attach phone via USB. Windows should now, approx. once every 2-3s, make a sound similar as if you put in a USB stick and then pull it out again.
Start=>Run=>devmgmt.msc, in the View menu choose "Devices by connection"
Click yourself through the tree until you find an unknown device (MT65xx Preloader or similar)
Rightclick on the device and press "Install drivers"; you shall find the drivers in "MTKUsbAll_0.9.2\New inst. win 7&8x64" folder.
Launch "SP Flash Tool v5.1352.01\flash_tool.exe"
In the tab "Download", click on the "Scatter loading" button and select the downloaded file "MT6582_Android_scatter.txt". spFlashTool usually remembers this across restarts.
Unplug the phone at the computer side if you want to work with it later (the MicroUSB ports don't like too many inserts, they wear out physically).
A) ReadBack for backup of existing firmware/userdata
This will involve a ****load of typing for the first readback.
Open the scatterfile using Notepad++ or any editor capable of handling UNIX line endings, NOT notepad
You will see a lot of blocks like
Code:
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0xC00000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
In spFlashTool, select the "Readback" tab.
For all the blocks you see in the scatterfile (IDs 0-23), repeat the following:
Click "Add"
Double-click on the newly appeared row
Choose a filename (e.g. preloader.bin for the first block; some blocks will have name = NONE, use the partition_name here for the filename) and click SAVE
A window "Readback block start address" will appear
Choose Type = "hex". Copy (Ctrl+C,Ctrl+V, and take care to exactly select the hex value! Do NOT type the hex values by hand!) the value from linear_start_address (with the 0x) into the "Start address" box and the partition_size value in the "Length" box, press OK.
Unless you are at the SYS23 partition BMTPOOL, proceed to the next block, repeat from above.
The SYS23 partition can not be backed up, because it has invalid lengths. Do not enter it into spFlashTool.
CHECK THE VALUES FOR START ADDRESS AND LENGTH IN THE TABLE. CHECK THEM ANOTHER TIME.
Press "Read back" button at the top.
Plug in the phone with the battery removed(!) and wait. This process will take time and consume approx. 3-4GB of disk space.
Archive the files you created somewhere safe. Do NOT distribute anything to other people except the BOOTIMG, RECOVERY and ANDROID partitions, because the other partitions contain data that is hardcoded to your board (e.g. IMEI/MAC addresses, sensor calibrations,...) or your private data and app data (SYS22/USRDATA).
If you want a full backup to disassemble by hand lateron (aka you trust in nothing going wrong and don't want to do the hard work except when you need it), just create one readback section with start=0x0 and length=0xE5720000 - this backups everything in one file.
B) Download for flashing new firmware
In spFlashTool, select the "Download" tab
In the dropdown box below the scatter file, keep it at "Download only" or set it if this is not the case
Uncheck all the boxes in the table
Double click on the "Location" column of the BOOTIMG, RECOVERY, ANDROID or USRDATA rows which you want to flash, select the appropriate image file.
Check that you selected the correct images for the correct partitions!
CHECK THAT ONLY THE ROWS WHICH YOU WANT TO FLASH ARE CHECKED. ESPECIALLY, NEVER EVER CHECK THE PRELOADER, MBR AND EBR PARTITIONS. YOU HAVE BEEN WARNED.
Press Download
Plug in the phone with the battery removed and wait. spFlashTool will tell you when it's done.
Unplug phone from computer (!) and put in the battery.
If you get an error "PMT changed for the ROM; it must be downloaded", reboot your machine.
When you have a running ROM on it, you may also try to keep the battery in the phone during flashing; just press Download on the PC, then select Shutdown in the Android menu that appears after holding Power pressed. Once the phone has shut down, it will vibrate shortly and then be detected by spFlashTool. I also recommend using a high-quality USB cable and not a worn out one because USB cables with worn out plugs may lead to issues during transmission.
NAND reflush?
Excellent stuff you wrote here - thank you.
Any hints on how to resurrect dead B15Q that has damaged/erased NAND or a Preloader?
In this link http: // forum . xda-developers . com/ showthread.php?t=1943442 a forum member
claims that mt65xx have META mode even if they appear dead - like mine B15Q is right now - and could be
revived with SPFT and proper W7 drivers.
Does under those circumstances PRELOADER might be reflashed?
I read just afterwards that one should not do fully ticked Memory Test as it silently reformats NAND.
I guess this is what happened in my case.
Also, a reason to do this test was that reflashing the phone with 1.010 BOOTIMG, ANDROID and RECOVERY, having it back for a brief moment and then upgrading it via OTA to 1.019 that had bricked it in a reboot loop.
Any clue would be welcome.
uhuru-meditation said:
Excellent stuff you wrote here - thank you.
Any hints on how to resurrect dead B15Q that has damaged/erased NAND or a Preloader?
In this link http: // forum . xda-developers . com/ showthread.php?t=1943442 a forum member
claims that mt65xx have META mode even if they appear dead - like mine B15Q is right now - and could be
revived with SPFT and proper W7 drivers.
Does under those circumstances PRELOADER might be reflashed?
I read just afterwards that one should not do fully ticked Memory Test as it silently reformats NAND.
I guess this is what happened in my case.
Also, a reason to do this test was that reflashing the phone with 1.010 BOOTIMG, ANDROID and RECOVERY, having it back for a brief moment and then upgrading it via OTA to 1.019 that had bricked it in a reboot loop.
Any clue would be welcome.
Click to expand...
Click to collapse
Bigal1337's image should also contain a preloader, but I guess in your total-dead state it'd be better to send in the device for warranty... after all no one can prove what exactly zeroed out your NAND.
harddisk_wp said:
.....but I guess in your total-dead state it'd be better to send in the device for warranty... after all no one can prove what exactly zeroed out your NAND.
Click to expand...
Click to collapse
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
The other thing is my bad clicking around and "checking memory" while not really knowing what I am doing.
As well as Windows x64 drivers, admin rights and all the other voodoo lurking in there.
What troubles me more is how come that CAT ppl. allowed "bricking" device upon system update, while root or no root shouldn't really matter there?
They sell it unlocked, so they should sell it, as well, with an easy option to root it. As Nexus One from Google had this "build-in" option.
I still hope that future updates will not have the same behaviour and also that there will be an alternate option for some other flavour of Android.
uhuru-meditation said:
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
The other thing is my bad clicking around and "checking memory" while not really knowing what I am doing.
As well as Windows x64 drivers, admin rights and all the other voodoo lurking in there.
What troubles me more is how come that CAT ppl. allowed "bricking" device upon system update, while root or no root shouldn't really matter there?
They sell it unlocked, so they should sell it, as well, with an easy option to root it. As Nexus One from Google had this "build-in" option.
I still hope that future updates will not have the same behaviour and also that there will be an alternate option for some other flavour of Android.
Click to expand...
Click to collapse
I think I have found something... this chinese rooter apparently messed with internal symlinks, and the firmware update broke as it assumed "stock" contents...
Another reason not to trust rooters where one can't even read the description because its chinese...
harddisk_wp said:
Another reason not to trust rooters where one can't even read the description because its chinese...
Click to expand...
Click to collapse
I agree there. I gave up on rooting B15Q.
On the side note: lately I had 2 spontaneous reboots after this reflash and resurrect.
It happened after I used "official" messaging app more precisely after I send a message and close the app..
.
Did anyone noticed this? - it is 1022 I have up and running.
Other than that it works fine.
Hello,
I tried your workaround but haven't succeeded yet. And yes my phone also is bricked, unfortunately.
My phone halts where you have to choose a language after a factory reset. At that moment I get some messages that some services had stopped. Like Google keyboard, Youtube and some more. I can click OK but this doesn't get me passed these messages and they reappear. I only can switch off the phone.
I tried your workaround on a x64 machine (and got the PMT message) because that's what I have. I am preparing a x86 machine which has XP on it but on launching SP Flash Tools I get the message the configuration of the computer is not correct. Will W7 32-bits do the trick?
Also two more questions.
The downloaded images are : boot.img, recovery.img, system.img and uboot.img.
In your explanation you're mentioning : BOOTIMG, RECOVERY, ANDROID or USRDATA.
I presume that in SP Flash Tool I have to use the system.img in the row ANDROID?
Or should it be in the row USRDATA?
You don't use uboot.img. What's the reason for that? For what purpose is this image?
Update 19 april 2015.
I managed bringing back my phone to life. I did another attempt by rebooting my 64-bits computer (as you wrote in the beginning) because at that moment I didn't had a 32-bits machine. It worked wonderwell. So, I'm using my phone again. Like uhuru-meditation I give up rooting for the moment. Nevertheless Android 4.4.2 I still like this phone. Hope it won't let me down after this major reset. Keep fingers crossed.
harddisk_wp many thanks for your hard working in making this workaround. It sure has cost you more then an hour's work.
I hope you read my questions and can or will answer them.
CAT B15 help
Hi guys, i'm sorry i have to ask this in this forum but i've been asking for a couple of months now, and got no answer. I have a CAT B15 (not the B15Q). It is single sim version (IMEI write on the back) and i managed to do plenty of things in it. I swapped memory and worked fine, and even i installed a Dual Sim android rom and i managed to use the secondary Sim bay in it (that was tapped with a plastic fake sim) and used the phone with 2 sims for like 2 weeks. Then i started to play with deodex and build.prop and softbricked the phone, but it was piece of cake since it is easy to unbrick. The problem was that i wrongly flashed the phone with scatter file, and flashed all partitions in it, EBR1, MBR, UBOOT, etc, etc. The result was a non-working dual SIM phone. Everything works, but the SIMS, it does not detect any SIMs in it, in any of the SIM bays, and the IMEIs are wrong numbered. I did no buckup of the phone so i'm pretty screwed. I've been asking for someone to upload the EMEA_SS or US_SS ROM for the CAT B15, but nobody responded. I thaught maybe the CAT B15Q has a similar software/bands flashing partitions, but that i leave to you for answer. Anyway, if any of you has the possibility of taking the images of a single sim CAT B15 it would save me this awesome phone for me. I'm also willing to give a 20GB account of ownCloud server for 1-year free of charge if storage space is needed, no problem. This are the links i've been searching and asking.
All About CAT B15: http://forum.xda-developers.com/show....php?t=2430904
Root for Catterpillar B15: http://forum.xda-developers.com/show....php?t=2263455
Best regards,
2 Questions
Good day
I have the same questions as a previous user, but I cannot find any answer to it:
"Also two more questions.
The downloaded images are : boot.img, recovery.img, system.img and uboot.img.
In your explanation you're mentioning : BOOTIMG, RECOVERY, ANDROID or USRDATA.
I presume that in SP Flash Tool I have to use the system.img in the row ANDROID?
Or should it be in the row USRDATA?
You don't use uboot.img. What's the reason for that? For what purpose is this image?"
Could you please help with these? Should I use uboot.img as well? And does system.img go to the Android row?
I added this 3d question later: is it safe to flash SS phone with the DS file?
Kind regards
"PMT changed for the ROM" and SP Flash Tool version
Hello,
I'd like to say big thanks and report that my B15Q was saved thanks to this thread, after a failed upgrade to the 1.016.00 firmware (due to the Chinese root app).
Moreover, I would like to point out that the procedure worked only with the v5.1352.01 version of SP Flash Tool. All other versions I've tried bailed out with the "PMT changed for the ROM; it must be downloaded" message. Unfortunately, the thread which is listed in the instructions refers to a version of SP Flash Tool more recent than v5.1352.01. A link to the said version can be found in this post: http://forum.xda-developers.com/showpost.php?p=58810386&postcount=4
Regards,
Aurél
harddisk_wp said:
0) Driver and toolkit setup
Get the driver set, scatter file and spFlashTool from this thread: http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774
Remove back shell from phone, remove battery (!)
Attach phone via USB. Windows should now, approx. once every 2-3s, make a sound similar as if you put in a USB stick and then pull it out again.
Start=>Run=>devmgmt.msc, in the View menu choose "Devices by connection"
Click yourself through the tree until you find an unknown device (MT65xx Preloader or similar)
Rightclick on the device and press "Install drivers"; you shall find the drivers in "MTKUsbAll_0.9.2\New inst. win 7&8x64" folder.
Launch "SP Flash Tool v5.1352.01\flash_tool.exe"
...
...
If you get an error "PMT changed for the ROM; it must be downloaded", reboot your machine.
Click to expand...
Click to collapse
my b15 loopboot
Hello such greetings from Venezuela have a cat b15q dual sim to load the firmware with sp flashtool v3 makes the whole process but remains frozen on the logo even doing a wipe and there no moves have the rom that is posted here I can I am doing wrong excuse my English but I use a translator
Thanks on advanced . Worked fine on my b15q cat . Really much apreciated .
Hello, I'd like to say big thanks and report that my B15Q was saved thanks .Thanks this rom launch perfect
uhuru-meditation said:
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
...
Click to expand...
Click to collapse
Would you please care to share how you achieved that?
(Following some guide which said that upon ""PMT changed for the ROM..." error one should format the device before downloading, we did that (after reading back everything) but unfortunately, spFlashTool doesn't like the readback PRELOADER partition we extracted.)
goodnight I hope will help me have a cat b15q and remained in recovery mode and I need to flash it revive hope help me thank you .. I'm from Venezuela and one who does not get that software. Excuse my English but q use the translator
CAT B15Q - My Rear Camera doesn't work anymore
Good evening everyone.
After a bad update, my rear camera on CAT B15Q doesn't work anymore. I read all the posts here and I'm using Windows Vista Home Premium 32 bits. I downloaded all the necessary files and when I open the SP Flash Tool, I think it didn't recognize my smartphone and when I try to download any file to the phone the status bar on SPFT still stopped, like if anything is going on. I buy this B15Q on Paraguay. Could this fact be my problem? Anyone could help me, please???
This post was closed and i was told to ask it here. I posted it in the wrong area and im sorry about that.
I really need some serious help and advice. Could anybody who is experienced it this filed please help me, or even put me in the right direction.
I am stuck in the qualcomm download mode with my device as QHSUSB_Dloader9008.
Yes it is a hard brick and 99% of the google searches have just confused me.
So here is the story.
I was developing for the Lg Vista D631, and trying to port a rom from the v10lte tablet due to the exact same architecture. The only main difference was the screen size.
Anyhow i was using fastboot to mess arount with the LG Security Error but nothing worked.
I didnt find out that much. So i just flashed back stock and then restored from cwm.
Well i went back to fastboot to try some more and i typed fastboot erase aboot, all went well. Then as i was in the middle of typing fastboot flash aboot my dang phone battery fell out my phone. And this is what i recieved... It Took it off my cmd prompt screen, i now have a nice crack in the screen, and a wonderful bricked phone....
It read up as Android Net USB, and it also came up as a removable disk with 64mb free on it. so i looked and i looked for something just to flash the aboot partiton back to the phone. But nothing came up. I even tried win32 imager.
I googled jtag and read that there are test points which would i could short to reset the devices bootloader to the wualcomm safe bootloader to flash the emmc chip and partition table back to stock. Which would thus repair the partition and open up recovery and or download mode.
I attempted to trace the circut to find out what point to short' and yea i even tried a few which only reset the phone. So i said screw it and formatted the removable disk....... And bam my pc detected a new device and installed the qhsusb dload9008 driver.
So now im in qpst fail safe download mode, i have it set to com41, and qpst detects it too.
And now th issue and question at hand.. I need the files to flash an msm8296. As the mbn, hex, and what nots are all not working with me. Do
When i try to use eMMC downloader I just kept getting the same response from qpst 4.0.2.
"Download failed could not communicate with flash programmer"
then in software download i keep recieving that the hex file is invalid, and could not detect the hex scrambling method. The file is invalid.
I have the lg d631 and have many unofficial kdz files i compiled. I could use the vs88010b for any other ones needed too. As i found out which ones are compatible through my testing phase.
When thia gets fixed though, the development for this phone will skyrocket, as anything will be possible.
So i am stuck. I messed up. And need to fix my mistake.
Phone bricked stuck on Android screen,access to adb & fastboot logs provided [Solved]
Hello,
I recently messed up my phone. Long story short, I snatched an OTA, modified it and tried to force it on my phone. The vanilla OTA always failed in the check process because I modified some /system files on my phone. In result of that, a couple of files has been wrongly patched ( /system/app/OpenWnn/OpenWnn.apk ; /system/bin/debuggerd ; /system/bin/install-recovery.sh ; /system/priv-app/ApeCloudFileManager/ApeCloudFileManager.apk ; and maybe others indirectly ). I can provide more informations about my slip up if you wish.
Since then when I start my phone I'm stuck at the "Wiko, powered by Android" screen. I can access the stock recovery menu, and the factory mode. I also have access to my phone throught adb, adbd, and fastboot.
My phone is a Wiko Rainbow Lite 4G ( http://world.wikomobile.com/m745-rainbow-lite-4g ), the actual manfacturer is Tinno so the phone is probably sold under different names around the world, Wiko being only a "middle-man".
With that said, I can't flash the ROM using the utility given to me by Wiko. They do not provide "stock rom" with scatter file, but instead use their own software, a sole .exe file ready-to-use, you hook your phone to your pc, restart the phone by pressing random combination of buttons, and voila. However, I managed to extract the system.img, boot.img, etc files from the .exe . So I figured out I could try to use "fastboot flash system system.img" command to restore whatever files are messed up. Might as well not touch /recovery and /boot because I can access the recovery the phone seems to boot correctly ( from what I understand /boot is just a bootloader, so me being a pc-guy I wouldn't see the point of reinstalling GRUB if windows was missing a dll or something like that ) .
But the phone is locked .... Here's the "fastboot oem device-info" result
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
And I when I try to "fastboot oem unblock" :
Code:
FAILED (remote: oem unlock is not allowed)
So yeah .... I'm stuck there. If anyone got an idea, even a vague one of what I could try next to unbrick my phone that would be very kind of you. There's no wrong answers. So please if you got a couple minutes to spare (you already made it through my laïus which is already something ) I would be very grateful.
I'm thinking about extracting files from system.img and copy them on my /system partitions throught adbd with a script .... But I'm not sure if that would help or make it worse.
If you need informations here's the logcat I got under "factory mode" ; part1 : http://pastebin.com/nx7BC8K5 , part2 : http://pastebin.com/eU94B9VE
the pstree (because come on, if a phone can launch all of that, certainly there's something we can do to repair it) : http://pastebin.com/ZWd6vC9q
dmesg : http://pastebin.com/RYfbF0ub
prop : http://pastebin.com/k6T4bYnu
cpuinfo : http://pastebin.com/a6eMQTmd
PS : Yes I'm still a noob when it comes to Android, but please if you have any questions, need more informations, ask and I shall provide.
PPS : @moderators, I apologize if I posted in the wrong section, please redirect me
Since you extracted them, they now have a different signature and can therefore not be flashed onto the device because your bootloader only allows ROMs with their signature to be flashed successfully. Also, to clear things out, boot == kernel, boot =/ bootloader. Also, why exactly can't you flash it using their provided tools? If you are going to flash stock ROM you might as well reflash recovery and boot.
Thanks for answering.
I can't flash using their provided tool because the tools fails at 1% progression with a generic message error "oops something wrong happened, good luck with that kido, kisses".
Why do I don't want to flash recovery and boot ? Because these seems to work now, and I'm scared that if I break those I won't even be able to access my phone through adb,fastboot or get to recovery.
About the signature, I've seen plenty of topic/tool/stuff around the internet about how to unpack RUU images (is that what they're called or is RUU specific to htc ?) to update.zip files (eg: http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/ ; http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/) . Problem being they're always wayyy outdated and approximative.
Honestly it would help me a lot in my research if I know what is even wrong with my phone.... I can't make sense of the logcat.
EDIT :
Ok I finally managed to reflash it using a more generic flashtool (designed for qualcomm based phone) named QFIL.exe, found it in this archive http://www.mediafire.com/download/4rgr02wi542n4sw/Qualcomm_tools_and_guidance.rar . Then I simply used the file found in the .exe files to populate the form and yabadabadou !
However my flash screen is now completly black .... I do not even have a prompt when selecting between recovery ("Power"+"vol-" then "vol+") and factory mode ("Power"+"vol-" then "vol-")...
Anyway, now that I know how to safely unbrick it. I can mess with it even more. But I probably should port CWM to it and do a backup pretty quick.....
Aramir said:
Thanks for answering.
I can't flash using their provided tool because the tools fails at 1% progression with a generic message error "oops something wrong happened, good luck with that kido, kisses".
Why do I don't want to flash recovery and boot ? Because these seems to work now, and I'm scared that if I break those I won't even be able to access my phone through adb,fastboot or get to recovery.
About the signature, I've seen plenty of topic/tool/stuff around the internet about how to unpack RUU images (is that what they're called or is RUU specific to htc ?) to update.zip files (eg: http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/ ; http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/) . Problem being they're always wayyy outdated and approximative.
Honestly it would help me a lot in my research if I know what is even wrong with my phone.... I can't make sense of the logcat.
EDIT :
Ok I finally managed to reflash it using a more generic flashtool (designed for qualcomm based phone) named QFIL.exe, found it in this archive http://www.mediafire.com/download/4rgr02wi542n4sw/Qualcomm_tools_and_guidance.rar . Then I simply used the file found in the .exe files to populate the form and yabadabadou !
However my flash screen is now completly black .... I do not even have a prompt when selecting between recovery ("Power"+"vol-" then "vol+") and factory mode ("Power"+"vol-" then "vol-")...
Anyway, now that I know how to safely unbrick it. I can mess with it even more. But I probably should port CWM to it and do a backup pretty quick.....
Click to expand...
Click to collapse
YaY, you can now put [SOLVED] in the title to help other in the same issue you had!