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:
My cousin got me this phone from China. According to him, the phone model is Coolpad 7296.
The first problem seems to be that the phone is actually different from the official Coolpad 7296, which is shown in the first attached image. But my phone looks more like the second attached image. I have the link for both phones the official site and a online seller selling a phone 99% like mine while claiming it to be a Coolpad 7296. I can't post the links due to the forum policy requiring me to have a least 10 posts. In other words, there is a very good possibility that my phone is not a legit Coolpad or it may be a variation of the Coolpad 7296.
When i first wanted to unlock the bootloader to root my phone, it was impossible. After booting to fastboot mode, any fastboot command would get stuck. For example, if i did the following:
Code:
fastboot oem unlock
It would get stuck and only show:
Code:
...
Click to expand...
Click to collapse
Or if i tried erasing the user data:
Code:
fastboot erase userdata
It would get stuck and only show:
Code:
erasing...
Click to expand...
Click to collapse
Later, I was able to root the phone via a Chinese app which literately translate to "Baidu One Click ROOT". After some playing, i tried to flash the phone via fastboot, then i literally broke the recovery mode. Most likely, the recovery partition was damaged. After more playing around, i broke the system image. I was still able to boot to fastboot mode back then. Afterwards, i broke fastboot mode as well.
After some time, i was able to install the VCOM Preloader USB Drivers by disabling the digital signatures required for installing the drivers in Windows 8. Then, I flashed the phone using the SP Flash Tool and an official ROM of Coolpad 7296 manufacturer. I am able to turn on the phone and the screen would light up in a black blank screen. The computer is able to recognize the phone via USB and i am able to use ADB commands as well as ADB Shell on it. In addition, i downloaded a program called 刷机精灵, which is a ROM flash tool for Chinese phones. This program is able to show exactly what was supposed to be showing on my phone screen. If i press the Power Button, it shows the phone's pop up window asking for if i want to power-off, reboot or put in airplane-mode. The screenshot is shown in the third attached image.
Sorry for the long post but i thought it would help if i told the whole process. Now are the real questions:
1) I never backed up my phone. So, i can't get it back to the original ROM i had. I wonder if it is possible that the screen doesn't work because the phone doesn't have the right radio image with the proper drivers. I mean, I could assume that the phone is a variation of the current official Coolpad 7296, and it is not compatible with the current official ROM.
2) Or, what are the chances that i burned my screen by charging the phone when the recovery and system images were dead. At that time, the phone could only work on fastboot mode and i left it charging overnight. Next day, the phone camera was extremely hot. And i am not sure if fastboot mode was dead first or the screen stopped showing stuff first.
3) Right now, the phone cannot reboot to neither recovery or fastboot mode (no matter how much i try with the ADB reboot or power & vol key press methods). I believe that the possibility of a somewhat incompatible phone radio, recovery and fastboot images are the cause of my current problem. So, i wonder if anybody have the same phone and know a compatible ROM.
Edit: I also want to mention, that i tried to flash the phone with other official Coolpad ROMs too. The only one that were flashable ere Coolpad 7295 and 7296. When i flash it with Coolpad 7295, i have the same problem plus the phone cannot see my SD Card. On the other hand, when i flash it with Coolpad 7296, i recognizes my SD Card. I have confirmed this via ADB shell and i can see my old files in the SD Card too.
Edit2: Another things i wanted to mention was that when i entered to fastboot mode in the past, the device id was mt6589_phone_720pv2 which means the cpu must have been a mt6589 chipset. However, i remember that when i ran a phone hardware app, it showed that the CPU was a 2.0Ghz mt6592 which was weird. And when i check online, mt6589 the CPU freequency is 1.2Ghz. On the other hand, documents online show that mt6592 has 2.0Ghz frequency but it is a octa core. My phone is definitively a quadcore.
I found a working ROM. It says it is for Coolpad 8750 but it is identical to my original ROM. The irony is that when i download the ROM of Coolpad 8750 from the official site, it doesn't work with my phone.
Code:
pan.baidu.com/share/link?shareid=1988426388&uk=2802944333
Click to expand...
Click to collapse
I bricked my MT6577-based phone. I ran an app which re-partitions the drive, and this stopped the phone from booting -- the initial boot splash screen appears (in this case an Android icon), but it doesn't get to the point where it loads the OS (which would be represented by an Android icon where the droid's eyes and 'jetpack' light up).
I have placed the phone in recovery mode (power+vol up), and connected this to my PC (Windows 7). The PC does not recognise the phone and flags up an "unknown device" (code 43), so I cannot do anything with the flash tool or MTK tools.
I'm assuming that the original ROM is still intact, but can anyone confirm: is this phone recoverable? I should point out that it appears not to be possible to get a copy of the stock ROM for this device, I have searched at length with no success.
If it's dead without the ROM, a single line to the effect will put my mind at rest at least
Reinstall the drivers and then connect your phone in recovery mode
Use yuweng's ctr recovery porting tool and get the custom recovery
Then in wipe menu, wipe data and emmc partition then try
Otherwise you'll need the stock rom to he flashed by flashtool
Press thanks :good: if I've helped :highfive:
Hello Ive got a bit of a problem actualy a few with my pipo U1 Pro
I installed CWM V6.o.3.1 and rebooted fine, pipo boot image was normal, then i installed from ext SD card Decontaminat V3.1
after install the screen was Split at 2/3 and touch orintation was off with buttons in wrong corners
so i read alot found change in build.prop (ro.sf.hwrotation=270) from 270 to 0 and reinstalled form ext sd card
all it fixed was position of touch screen the image of ui was still split 2/3 and out of rotation.
i reinstalled CWM fron ext sd card reboot ant the cwm recovery is straigt on the vertical and the android shows in center of screen, but ther is a fine line showing where the screen was split in the os.
after reboot the os is still split 2/3 image i have to us the show touch function to navigat the touch field to make thins work
i had TNT pipo u1 pro.img installed before and was rooted worked fine but latly had a few minor problems with it so i desided to chand up a bit.
second problem is i cant get ADB , android studio or rkbatch tools to find my tablet, usb debugging is on, tried the load from adb sideload function in cwm
im running linux mint 17 added udev.rules rebooted every thing many time s swapped usb plugs cords you name it.
as it is the tablet works but the ui is buggered up and touch is off
any help would be verry appricated
mike
May be bricked now ?
I have the pipo stuck in what might be a boot loop?
just says decontaminate with a split screen on bootup shows pipo image then goes to decontaminate screen and nothing.
lsusb shows device { Bus 002 Device 009: ID 2207:0006 }
shows Android device in file manager But Error unable to mount android unable to open mtp device
pushing the buttons '' esc, +vol then power gets nothing.
pushing +vol, power gets nothing
incerting usb and pushing +vol gets nothing
only thing gets anything is push and hold power, CWM is not working cant boot to cwm
tried a bootable sdcard still no boot
was a nice Tablet till decontaminat screwd the screen up
got recovery yeah !!!!
found a way into the cwm recovery through adb.
i added a line into the file here.
/yourusername/.android/adb_usb.ini
its a hidden file added a simple line as root user
0x2207
saved file and rebooted computer.
will post again if i can recover the pipo.
buggered
had total access to the pipo.
i used flash_image to install freaktbs ryley rom for the pipo u1 pro.
now im stuck in a worse position. the kernal.img was not for the pipo.
he was playing with a another tablet and left its kernel.img as kernel.img and had pipo kernel as 1kernel.img
so im stuck with no touch support on the screen and its not defaulted to usb debug mode.
i can see the button acking to allow debug when i connect to usb on linux but no access to touch.
also the rom didnt have any tools for adb installed in recovery /system/bin.
no adb shell support.
only access is adb ls /
to read files and push pull commands.
any ideas on how to edit the default.prob make it stick through reboot and get it to debugg after reboot ?
this sucks MR.RYLEY built a bad rom I was almost into my pipo again.
my guess is the decontaminat rom was using a similar kernel to ryley to get the screen all buggered up.