My phone it's bricked, I rooted my w100 yesterday and to celebrate I installed the ifont app from the market, but at the third change didn't reboot any more, I have searched for the rom but seems to be very new... Neither the recovery or something help me out, I was looking for the preloader or somethin ... I'm just desperate.
Some help will be very appreciated!
How did you root it?
Uri997 said:
How did you root it?
Click to expand...
Click to collapse
its pretty easy, you can use the motochopper tool, instal the mtk6589 driver and connect your phone to the pc, then hit the runme.bat file and follow the instructions, very easy!
Here you have a very simple and good post that surely will help you.
http://forum.xda-developers.com/showthread.php?t=2247537
Best wishes!
josepbennet said:
My phone it's bricked, I rooted my w100 yesterday and to celebrate I installed the ifont app from the market, but at the third change didn't reboot any more, I have searched for the rom but seems to be very new... Neither the recovery or something help me out, I was looking for the preloader or somethin ... I'm just desperate.
Some help will be very appreciated!
Click to expand...
Click to collapse
here u go:
kokuo81 said:
Here you have it
THL W100 rooted ROM:
https://mega.co.nz/#!SEYFlbxT!LYK3Rw231-M6eA0O75ccZRgEQ7JLvBrZDm_MDqdLvBU
(credits to josemdg90 on htcmania)
Originally taken from:
http://4pda.ru/forum/index.php?showtopic=462368&st=200
Hope it helps
Cheers
kok
Click to expand...
Click to collapse
josepbennet said:
My phone it's bricked, I rooted my w100 yesterday and to celebrate I installed the ifont app from the market, but at the third change didn't reboot any more, I have searched for the rom but seems to be very new... Neither the recovery or something help me out, I was looking for the preloader or somethin ... I'm just desperate.
Some help will be very appreciated!
Click to expand...
Click to collapse
You must be the absolute first to brick your w100.
Did you succeed installation of kok's rom ?
I bricked my phone too...
First I installed a partitioning app to my device, my plan was to merge the two inner partition into one.
Then i become frozen boot.
After that I tried reflash with sp Flash Tool, I made a "format" and a reflash, and now the W100 is in boot loop.
When I try to do a factory reset in recovery it says: "Mount /data error"
Could you guys help me please? What the hell can I do now...?
I've succesfully unbricked my THL W100
josepbennet said:
My phone it's bricked, I rooted my w100 yesterday and to celebrate I installed the ifont app from the market, but at the third change didn't reboot any more, I have searched for the rom but seems to be very new... Neither the recovery or something help me out, I was looking for the preloader or somethin ... I'm just desperate.
Some help will be very appreciated!
Click to expand...
Click to collapse
salaksalak said:
I bricked my phone too...
First I installed a partitioning app to my device, my plan was to merge the two inner partition into one.
Then i become frozen boot.
After that I tried reflash with sp Flash Tool, I made a "format" and a reflash, and now the W100 is in boot loop.
When I try to do a factory reset in recovery it says: "Mount /data error"
Could you guys help me please? What the hell can I do now...?
Click to expand...
Click to collapse
Hi everyone,
Few days ago, I've also bricked my THL W100... My mistake was one of the most stupid one: instead of click on Download in SP Flash Tool, I click on Format and accept the operation without reading the warning message. Result: first boot I got the white THL logo in bootloop, and second attempt give me only a black screen with only a faint red light on the front LED.
I've read many threads about unbricking MediaTek based devices, made many manipulations without success. I've even disassemble my device in search of a secret 'test point' dedicated to full memory flash.
Unbricking THL W100 in far more simple than all this. You'll need one of the 'THL W100 original ROM'. I've choosen the May 16th edition (130516) on NeedRom (http://www.needrom.com/phone-roms/thl/thl-w100/). And off course, you'll need SP Flash Tool, also available on NeedRom.
Unpack the Rom files, launch SP Flash Tool, and load Scatter file, and press 'Download' button
The 'deep memory flash mode' require activation of the 'MTK DA USB VCOM' driver. To activate this mode, you'll have to:
1) disconnect the battery
2) keep the Vol+ down and connect the USB cable (without battery)
These are the main operations...
For my problem, I've tried to flash:
- the whole Rom except Preloader... but it fails,
- the whole Rom including Preloader... but it fails too,
The solution came by using first 'Format' function, and select 'Format whole flash' option, before flashing Rom as previously described. But, I used this format function with classic flash connection, e.g.: connecting the THL W100 to the PC via USB cable without the battery, and inserting the battery (and no use of Vol+ button, off course).
Be carreful: before trying this kamikaze procedure, try to unbrick your device by simply flashing the Rom without/with Preloader.
hi
Who have THL W100 firmware upgrade, please send a link to me, thank you
Lindsay02 said:
hi
Who have THL W100 firmware upgrade, please send a link to me, thank you
Click to expand...
Click to collapse
here it is : http://www.needrom.com/mobile/thl-w100-official/
pigot said:
The solution came by using first 'Format' function, and select 'Format whole flash' option, before flashing Rom as previously described. But, I used this format function with classic flash connection, e.g.: connecting the THL W100 to the PC via USB cable without the battery, and inserting the battery (and no use of Vol+ button, off course).
Click to expand...
Click to collapse
Afraid I don't understand...
The format is what you had done to brick it in the first place isn't it ?
So you needed to format again using 'Format whole flash' option ?
Is that correct ?
ch-vox said:
here it is : http://www.needrom.com/mobile/thl-w100-official/
Click to expand...
Click to collapse
Thank you
Lindsay02 said:
Thank you
Click to expand...
Click to collapse
you're welcome
intrax said:
Afraid I don't understand...
The format is what you had done to brick it in the first place isn't it ?
So you needed to format again using 'Format whole flash' option ?
Is that correct ?
Click to expand...
Click to collapse
True: I've bricked my device by using 'Format' with the option 'Format whole flash except Bootloader". At the first reboot, I got a THL white logo bootloop. After second reboot, nothing but a black screen and a faint red light from the front Led. I've tried 'Download' and 'Upgrade' SP Flash Tool functions to reinstall ROM(s) with or without 'Preloader' partition: got lots of sybilin error messages, and correct download.upgrade achievements, but my device remains bricked.
I've also tried 'Format whole flash except Bootloader' function + immediate Rom download, but it fails... until I use 'Format whole flash' function (USB cable connected + battery insertion) and immediately after whole ROM (130529) 'Download' (no battery inserted + Vol+ pushed + USB cable). First boot took about 4 minutes... but everithing works after that.
Need help please
please help me !!! I THINK MY DEVICE IS BRICK I NEED THE OFFICIAL ROM
please help me i BOUGHT THL W300 befor 5 days ago ...i try to update the recovery but the divice is died and black screen it is no work and no start up no charging . now i want for your help
it is new divce but no support here in saudi arabia..
when I conict the computer there is no logo no show any thing gust black screen gust I heard some sound when I plunge with computer . I try to flashing ROM(thl w100) it is show message error 4023 in flashtools.
now I need file to flashing ROM also file for bootloader.or any help to start up agin
iam sorry my english languge is not ok
I can't do it!!
pigot said:
True: I've bricked my device by using 'Format' with the option 'Format whole flash except Bootloader". At the first reboot, I got a THL white logo bootloop. After second reboot, nothing but a black screen and a faint red light from the front Led. I've tried 'Download' and 'Upgrade' SP Flash Tool functions to reinstall ROM(s) with or without 'Preloader' partition: got lots of sybilin error messages, and correct download.upgrade achievements, but my device remains bricked.
I've also tried 'Format whole flash except Bootloader' function + immediate Rom download, but it fails... until I use 'Format whole flash' function (USB cable connected + battery insertion) and immediately after whole ROM (130529) 'Download' (no battery inserted + Vol+ pushed + USB cable). First boot took about 4 minutes... but everithing works after that.
Click to expand...
Click to collapse
Hi everyone!
When I got my w100 I tried to put an other ROM with sp flash tool, flash tool process completed perfectly but when I tried to boot my phone, the pone it started up but the screen only showed white lines. I even heard the sound of the boot.. But screen remained black with white and other colours lines.
I tried to flash it again with diferents many ROMs..W100_130912_backup_131001-214504, W100_130504_ForFlashtoolFromReadBack_130605-170952, ThL.W100.130701.JBV2.HD.EN.COM.8P32_MT6589.
Even though the process got complete, the perfomance of the phone was the same as I said.
As I got tired of flash it once and again, then I followed your advice, so I did a "Format whole flash", I got it, but after I tried the "Download" I always get the same error, after first red bar it's 100% sp flash tool always shows the same message:
BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
HINT:
Please check your load matches to your target which is to be downloaded.
Now when I tried to do whole format or download, I got the same error.
I tried by vol+ pushed + cable usb and cable usb conected without battery then I put de battery. But still the same result.
I'm starting to think that can be a motherboard damage or samthing!!
Can anyone help me please!!?
I found the solution!!
I did it by using Windows xp!!! Then the error message disappeared!! And i've got my phone working!!
---------- Post added at 07:38 PM ---------- Previous post was at 07:02 PM ----------
I found the solution!!
I did it by using Windows xp!!! Then the error message disappeared!! And i've got my phone working!!
pigot said:
True: I've bricked my device by using 'Format' with the option 'Format whole flash except Bootloader". At the first reboot, I got a THL white logo bootloop. After second reboot, nothing but a black screen and a faint red light from the front Led. I've tried 'Download' and 'Upgrade' SP Flash Tool functions to reinstall ROM(s) with or without 'Preloader' partition: got lots of sybilin error messages, and correct download.upgrade achievements, but my device remains bricked.
I've also tried 'Format whole flash except Bootloader' function + immediate Rom download, but it fails... until I use 'Format whole flash' function (USB cable connected + battery insertion) and immediately after whole ROM (130529) 'Download' (no battery inserted + Vol+ pushed + USB cable). First boot took about 4 minutes... but everithing works after that.
Click to expand...
Click to collapse
Great! That work for my friend phone after a lot of trying , Thank you.
Sent from my GT-I9000 using Tapatalk
Brom error: S_ft_enable_dram_fail (4032)
Hello,
my THL W100 arrived yesterday and i was immediatelly interested in some custom rom so i began flashing it not knowing properly, what i was doing, so firstly i ended up in boot loop, then completely bricked with device refusing to boot (black screen).
I tried recovering using SP Flash Tool these builds, but nothing worked for me:
thl.w100.130529.jbv2.hd.en.com.8p32_mt65
ThL.W100.130701.JBV2.HD.EN.COM.8P32_MT65
ThL.W100.130802.JBV2_.HD_.EN_.COM_.8P32_MT65892
W100_130504_ForFlashtoolFromReadBack_130605-170952
I also tried using different versions of SP Flash Tool (.119, .139 .150), but all showed error BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032)
As said here before, tried on Win XP and Win 7 64bit and it showed same error.
So then being despred for several hours I actually dig up a lot on internet and found up some information:
1) There are apparently some hardware revisions, according to beginning of serial code:
BFYSG94W - Rev. 1
BFYSG9410 - Rev. 2
But my phone has CFYSGM4W - maybe its a new Rev. 3?
2) Based on many other mtk6589 phones having the same problem, you should look for firmware released by date of manufacture. It should be written somewhere, but I didn't find any information on device no package, so I decide to look for latest.
3) The phone shows up in device manager as "alcatel RNDIS" under network cards, I had to manually update the driver selecting "Preloader for Flash SP.Flash" .ini file manually from a disk. It may tell that the device may not work or something, but don't worry, reconnecting it shows up as MTK USB Port under COM and LPT ports and it should be fine.
4) I also had to disassemble to device and short LCOLO test pin to ground - here is the original post with image http://forum.xda-developers.com/showthread.php?p=44208574#post44208574 I soldered a single wire of hdd ribbon cable to lcolo, the other side being wrapper around USB cable. I flashed without battery, shorted all the time. The Flash Tool immediatelly discovered the device, when the lcolo pin is shorted, then when progress bar turned from red to violet the MTK USB Port device changed to 'MediaTek Preloader USB VCOM Port' so the preloader was owerwrited and phone successfully flashed back to factory state.
(before you lose your warranty try connecting usb > inserting battery or connecting usb without battery + holding volume up, it does practically the same job)
5) There are lot of stock roms here - http://www.needrom.com/phone-roms/thl/thl-w100/
So finally the version that worked for me was: ThL.W100.130912.JBV2.QHD.EN.COM.V01.8P32-kol
I even managed to get CWM working, (used same scatter, checked only recovery and doble clicked and selected recovery-cwm-6037-w100-130912).
To make it easier for people having the same problem I put up the things that worked for me and uploaded it, includes:
ThL.W100.130912.JBV2.QHD.EN.COM.V01.8P32-kol
SP_Flash_Tool_v3.1316.0.150
recovery-cwm-6037-w100-130912
and drivers for ADB and Preloader for Flash with SP.Flash
http://www.4shared.com/archive/FjP0asvJ/thl_w100_rev3.html
I hope you will find my first post useful, sorry for my bad english
Regards,
Umakarton
I also received a THL W100 with a CFYSGM4W serial today.
I flashed a different stock rom to it and it refused to boot (just showed some black and white lines). Google led me here and your package worked great . I tried a few different roms but the one you provided seems to be the only one to work.
Thanks
Snippo said:
I also received a THL W100 with a CFYSGM4W serial today.
I flashed a different stock rom to it and it refused to boot (just showed some black and white lines). Google led me here and your package worked great . I tried a few different roms but the one you provided seems to be the only one to work.
Thanks
Click to expand...
Click to collapse
I am glad it worked for you too, I don't found any complete info in one place so i decided to write this essay. It feels nice to help other people! :good:
Hi,
i have bricked my P780 after flashing with new firmware. Now the Phone is dead with black screen and doesn't start after pressing Power button. After a few trials with SPflash (3.x) i recognized that SPflash had a problem with reading the Scatter-file i.e. the adress mapping. The adresses were set for all areas from 0x0000 to 0x0000. When flashing the phone i didn't see that and i think this is the reason for the dead phone (stupid old man
With Spflash 5.x the Scatterfile was read correctly.
Anyway: Now the phone was detected by the Win7 device manager as Mediatek USB Modem but it works not correctly with SPflash (3.x or 5.x).
I could neither download new firmware nor format the flash. I get always the error: "BROM error DA download to Baseband SRAM failed".
Sometimes i get the message that the power up sequence was problay to short and the bootmonitor sequence didn't work.
Both states are reached after pressing the reset button on the backside when the phone is connected to the PC.
Is there any chance to get the phone working with SPflash again or do i have to use a JTAG-Tool ( if there is one for Mediatek-chips)?
Mattes12345 said:
Hi,
i have bricked my P780 after flashing with new firmware. Now the Phone is dead with black screen and doesn't start after pressing Power button. After a few trials with SPflash (3.x) i recognized that SPflash had a problem with reading the Scatter-file i.e. the adress mapping. The adresses were set for all areas from 0x0000 to 0x0000. When flashing the phone i didn't see that and i think this is the reason for the dead phone (stupid old man
With Spflash 5.x the Scatterfile was read correctly.
Anyway: Now the phone was detected by the Win7 device manager as Mediatek USB Modem but it works not correctly with SPflash (3.x or 5.x).
I could neither download new firmware nor format the flash. I get always the error: "BROM error DA download to Baseband SRAM failed".
Sometimes i get the message that the power up sequence was problay to short and the bootmonitor sequence didn't work.
Both states are reached after pressing the reset button on the backside when the phone is connected to the PC.
Is there any chance to get the phone working with SPflash again or do i have to use a JTAG-Tool ( if there is one for Mediatek-chips)?
Click to expand...
Click to collapse
Hi. First look on the box of the phone. Iff there is something with a date that is something like 03.2014 or more like 09.2014 look what you must do:
1. download SPFlash Tool from here. This are the correct tools for Lenovo P780. DO NOT USE OTHERS.
2. now download the preloader file from here and the drivers from here. And yes, you must reinstall the drivers because your preloader is messed up.
3. unzip preloader file, go to target_bin folder and delete existing preloader(preloader_prada_row.bin), and add the preloader you downloaded, and delete any file from target_bin directory with the name Checksum.ini.
4. now load scatter file from ROM directory(should be target_bin directory)
5. check DA,DL WITH CHECKSUM (NOT OPTIONAL)
6. press Firmware Upgrade button (NOT DOWNLOAD BUTTON)
7. now just now plug usb cable to your phone.
8. firmware flash should start.(some red and other color lines should appear)
9. iff the firmware is not starting remove the back case of your phone and hold pressed the little red button from the right side, for about 20 seconds then release. All this must be done with cable pluged in to your phone.
10. after flash is done a green circle should appear
11. disconect your phone and power on your phone
12. lenovo logo should appear. then you should be pacient because it will took some time before android boots for the first time.
13. Good luck. Hope This Helps You. If not post here again.
Hi stympy,
sorry for the delayed feedback but i had no time to test it until now.
But you where completely right! It was the wrong preloader and the wrong drivers.
Now the phone is running again! Thanks a lot!
Best regards!
So i installed TWRP and flashed a xiaomi android one
It worked ok, some apps were weird
Tried to do the latest update for flyme with TWRP
It installed ok, but after restart it would boot to logo screen and turn off
Fastboot or recovery do not work
All phone does is turn on on 10 sec pwr button press and nothing else
Meizu M6 Note M721H is the version, tried qualcom but gives all bunch of errors and i cannot seem to find a way out
Requesting assistance please
Thankyou in advance
+1
Same problem here.
Folks, "a bunch of errors" is not exactly an accurate description that allows anyone to help you out.
However. Today, after I've tried to restore the TWRP backup of my "devinfo" partition with the intention of relocking my bootloader, I've bricked my Meizu M6 Note (unable to boot OS or the recovery) and subsequently spent about 3 hours googling for a working solution, I've tried reflashing the stock firmware using QFIL (also QPST and a few other tools), but I either got the infamous "Switch to EDL" errors:
Switch To EDL
Code:
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
This was due to the fact that my device was recognized as the Qualcomm (...) 900E device, so I had to go to Device Manager and "Update driver", then manually select the correct one from the list, which was "Qualcomm HS-USB QDLoader 9008" (version 2.1.2.2, but older ones might work as well). After that, QFIL gave me the also infamous "Sahara protocol" errors:
Code:
ERROR: function: is_ack_successful:1121 SAHARA_NAK_MEMORY_DEBUG_NOT_SUPPORTED
ERROR: function: sahara_start:895 Exiting abruptly
ERROR: function: sahara_main:924 Sahara protocol error
ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
However when this error occured, I was able to go to fastboot mode, by pressing the Volume down (-) key and trying to flash the stock firmware again. After this, my phone displayed "fastboot mode" at the bottom of the screen in green. However because bootloader was locked again, I wasn't able to run or flash a TWRP recovery. At this point I was out of ideas.
Thankfully, I've ended up finding an excellent Russian guide by VladimirVVK of 4PDA fame (thanks Vladimir!):
Code:
hxxps://4pda.ru/forum/index.php?showtopic=843179&st=5620#entry69341915
...where a certain UnbreakM6NoteMinimum.rar was uploaded, that included everything I needed to get out of the boot loop. I've reuploaded the file, so hopefully you'll be able to download it, and follow the instructions inside INSTRUCTIONS.TXT (there's a Russian and English version as well):
Code:
hxxps://mega.nz/#!N5ZEFaAb!ez3F4pCJPPs9jFODI2a9_QH8tiGD3GQfDtOP4xkEuDo
My only tip is, that if you find it difficult to put your device into "download mode" (which is NOT fastboot mode) because you're not able to turn it off properly and you can't get into the "Partition manager", do this:
1. Start QFIL
2. Choose Flat Build under "Select build type"
3. Click browse under "Select programmer", select prog_emmc_firehose_8953_ddr.mbn (you can use the file from UnbreakM6NoteMinimum.rar)
4. Connect your device, wait until it shows up as "9008"
5. Start pressing Volume up (+) and Volume down (-) at the same time
6. In upper menu go to "Tools" - "Partition manager", confirm the dialog.
7. Repeat process 5 and 6 until you see the partition manager.
8. Continue the guide in INSTRUCTIONS.TXT (steps 5 and 6 there).
After that, my device was out of the bootloop, however the OS still didn't boot completely (I was running crDroid before the whole kerfuffle), the boot animation started and continued for a couple of minutes then I saw a blank screen. However, now that the original Meizu recovery was restored and I was able to boot into it by holding down Volume up and the Power button. The Meizu recovery mounted an empty 2GB partition on my PC, I was able to copy the stock Flyme 7.0.1.0G stock ROM update.zip on it and flash it after that. My phone is now working again.
Good luck everyone!
Sorry about the "hxxp" links, but I'm not (yet) allowed to link external URLs per xda-developers policy.
meizu m6 note stuck on fast boot
plz help me
I fouund the solution
The 8953ddrmbn file not worked for me so i tried another mbn file from this pack and it worked fine :
mega.nz/#!5cwEWbTa!JQtI1mQslzUMNOgJd13DpxpmLjXTdA6V6tWWp5I0kng
My phone Not Showing 9008 in QFIL
i have connected and followd all instruction but My phone Not Showing 9008 in QFIL its showing 900E its not happening plzz help me
Tinyhafij001 said:
i have connected and followd all instruction but My phone Not Showing 9008 in QFIL its showing 900E its not happening plzz help me
Click to expand...
Click to collapse
Hi,
When it shows 900E in the windows device manager you must force the installation of the 9008 driver.
Choose "update driver" and "select a driver from a list" and select the 9008 driver even if Windows warns you that this driver is not signed.
Then you will be able to connect to QFIL again and restore the "devinfo" partition.
TWRP SHOULD NEVER BE INSTALLED ON THE "DEVINFO" PARTITION BUT RATHER ON THE "RECOVERY" PARTITION.
I saved some of my partitions of my phone (Meizu M6 Note M721H global firmware)
the files contains "_original" in their filename are the original ones from Meizu (FlymeOS)
https://drive.google.com/drive/folders/1Fc8s5khlz95cXIT0m2kLhqzZXn8yoBdG?usp=sharing
geekborg said:
Hi,
When it shows 900E in the windows device manager you must force the installation of the 9008 driver.
Choose "update driver" and "select a driver from a list" and select the 9008 driver even if Windows warns you that this driver is not signed.
Then you will be able to connect to QFIL again and restore the "devinfo" partition.
TWRP SHOULD NEVER BE INSTALLED ON THE "DEVINFO" PARTITION BUT RATHER ON THE "RECOVERY" PARTITION.
I saved some of my partitions of my phone (Meizu M6 Note M721H global firmware)
the files contains "_original" in their filename are the original ones from Meizu (FlymeOS)
https://drive.google.com/drive/folders/1Fc8s5khlz95cXIT0m2kLhqzZXn8yoBdG?usp=sharing
Click to expand...
Click to collapse
Unfortunately I replaced devcfg with devinfo and after that i cant start my device again or switch it to edl 9008
any help ????plz
Hello.
I'm struggling with this for days now without any result, so I decided to ask for some help.
I had this phone staying in my closet for a few months. A couple of days ago when I tried to charge it, I got the logo saying "Powered by Android" and get stuck there. (the phone was working perfectly before)
Interesting thing was, that most of the time I was not able to power it up at all.
Sometimes I managed to got it into Fastboot Mode TA, but not always.
Reading post here, I tried to reflash with stock ROM using YGDP.
It went smoothly, but now the bootloader is completely corrupted. Not able to get into Fastboot Mode anymore. Doesn't respond to any key at all.
It is recognised as Qualcomm hs-usb qdloader 9008.
After reading some more, I tried to get yhe bootloader back using QFIL without success.
No matter what I try, I get:
13: C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn
14:37:07: Requested ID 13, file: "C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn"
14:37:07: ERROR: function: is_ack_successful:988 SAHARA_NAK_INVALID_DEST_ADDR
14:37:07: ERROR: function: sahara_start:825 Exiting abruptly
14:37:07: ERROR: function: sahara_main:854 Sahara protocol error
14:37:07: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Same errors with prog_emmc_firehose_8936.mbn
It doesn't even get any acknowledge back from the phone?
Any help is highly appreciated.
Thanks.
Hi , I think you need a full emmc backup.img from working device in order to put your device in fastboot mode and be able to normaly flash stock firmware ....
https://forum.xda-developers.com/general/general/guide-unbrick-coolpad-dazen1-qualcomm-t3362253
Where to get an eMMC dump from?
I've tried with that dump in that post, but absolutely no change at all.
Will the phone read the SD card while it's off? At least that's what that post is telling me to do.
• After successful completion of writing eMMC backup image to SD card, insert the MicroSD card in your device and remove all sim cards. Insert battery into your device now. Do not power it on yet.
• Now you can boot to fastboot mode with the eMMC image on SDCARD.
Click to expand...
Click to collapse
I don't really get this part...
Hi you can't use backup from another device so you need to have the same working device it need to be rooted in order to do make debrick.img which you will make it bootable on micro sd card with Win32DiskImager tool . So then you should put your device in fastboot mode and flash normaly official stock firmware with YGDP tool ... If you don't know someone who can do that for you , check on the internet or YouTube who has device like your to make full emmc dump .
But it you don't have it then you can try Qualfast flash tool , but it required device to be into fastboot mode also you need to extract CPB firmware
Qualfast flash tool
https://androiddatahost.com/asaew
Download firmware from here :
http://www.mediafire.com/file/b3xdr59s6roj0jz/Coolpad_7576U_4.4.230.33.T3.140715.7576U.zip
Example how to extract CBP firmware files .
https://www.youtube.com/watch?v=OEbWKkzfiSA
Example how to use Qualfast flash tool :
https://www.youtube.com/watch?v=R4Bvy0Sax6Q
Just select path from extracted firmware for example C:/Users/SZabio/Desktop/Coolpad 7576U estracted firmware/ , wait all bars to be colored ....
Another option what you can try is one chinese app called COOLPAD DOWNLOAD ASSISTANT SETUP :
Download from here :
English language:
https://drive.google.com/file/d/0B5vyMGZJJmcnclVJb2Y2cHNNQkU/view
Chinese language
http://www.mediafire.com/file/e28degd1vjvevh3/Coolpad+Download+Assistant+Setup+V1.89_141231.rar
add path of CPB firmware (4.4.230.33.T3.140715.7576U.vf_ro.CPB) on number 2 ( browse) and click on green button ( Check Rom) , from up will be 100% loaded , now connect your device without the battery once the app detect your tool it will start writing files to your device .
Example how it should be :
https://www.youtube.com/watch?v=ZhWtvNVlqzE
Good Luck my friend , I hope you will finally get him to work again .
Thank you for trying to help, but as I said, the phone cannot be put into FastBoot mode.
It is completely dead, does not react to any button presses, does not even charge the battery anymore.
It is detected by the PC as "Qualcomm hs-usb qdloader 9008".
That's all.
I know nobody to get a full eMMC dump from unfortunately.
I've found out, that the phone's CPU is a Qualcomm MSM8210 Snapdragon 200, so I tried prog_emmc_firehose_8x10.mbn programming file.
Now QFIL is able to communicate with the phone, but all I'm getting is a bunch of errors, because the configuration .xml files are wrong.
I need rawprogram0.xml patch0.xml and partition.xml for this phone.
I don't understand why the bootloader was not blocked, so it could not have been overwritten by mistake.
Does anyone have some info on how the partitions are organised? Would be enough to write the bootloader in correctly, to get fast boot mode working again?
Hello all good souls over here.
Could you please help me out with flashing back the original stock ROM to Mediatek MT6737M phone?
UMAX VisionBook P50 LTE, Mediatek MT6737M, 2GB RAM, 16GB internal memory.
What happened:
Before I was trying Oukitel P5 Pro ROM as well as Lineage OS and flashing with SP Flash Tool was working just perfectly.
But then I tried to flash Oukitel P5 Pro Andorid 7 stock ROM. (Oukitel P5 Pro and UMAX VisionBook P50 LTE are completely the same phones. Just different branding)
(And from now on I am not sure if I remember correctly)
When I loaded in scatter file, SP Flash Tool said something about something .... and recommended to do "Format all + Download" and I have done so.
Clicked on the Download button, flashing started instntly when I connected the phone while holding Volume - button.
Flashing stopped in maybe one second with the error which I do not remember as I closed the error window way too quickly. :-(
Later on I noticed that the preloader file is different in this Android 7 ROM then Android 6 ROM.
What is the current behavior:
When the phone is connected (with the battery inside) to the computer phone keeps connecting and disconnecting (appearing in Device manager as Mediatek USB Port) if I click Download button it starts doing "something" instantly which stops at Download DA 100% and after the while ERROR: S_FT_ENABLE_DRAM_FAIL (4032) pop up windows shows up.
The same error happens if I try to Format it and all other combinations in Download tab (Firmware upgrade, Format All + Download)
If I plug in the phone to the computer while pressing Volume - button phone will show up in the Device manager after about 20 seconds.
(Just to note - When the phone was working OK, I started flashing instantly when I plug the phone into the computer while pressing the Volume - button
So that kind of leads me that if nothing will show up in Device manager when I plug the phone to the computer while pressing Volume - button, then there might be the issue with the phone not switching into META mode? Not sure, just what I have read. But I cannot move any forward at this point.)
What I have tried:
- Correct stock ROM and Oukitel stock ROM (both Android 6 and both I was able to flash correctly and was able to boot them, until I tried Android 7 ROM)
- various SP Flash Tools 5.xxxx (and 3.xxxx too, but version 3 does not accept scatter file at all)
- USBDeview and removing all related USB devices from Windows and re-install them back again.
- Various VCOM drivers I have found on the Internet
- Flashing with SP Flash Tools on Linux (ends up with the exact same result - 4032)
- I tried shorting test point to ground on the phone main board. (The result was the same like when I plug the phone in while holding the Volume - button - Phone would not show up in Device manager for about 20 seconds)
- Tried flashing with the battery inside and outside the phone. (When the battery is outside flashing would not start, but the error about incorrect chip type will show up)
- Read many articles about this error all over the Internet
Do any of you think there is a change to bring the phone back to live? Or do you know what actually might happen to the phone? It does not seems to be completele bricked, but I cannot say in what state the phone is.
Thank you very much for your help and have a nice day.
Hi. I need this rom for this phone. I have umax p50 lte too . Please give me link if you can. Thx
@oukitel654
Look inside here:
Common SP Flash Tools error and Solutions - ROM-Provider
Common SP Flash Tools error and Solutions: Hello guys if you are facing a SP Flash tools error code issue then this page is for you where we share solutions for for almost all SP Flash tools error. Common SP Flash Tools error Code: Error 5054, 4032, 8038, 5069, 4001, 4008, 3149, 3168, 2004, 1013, …
romprovider.com