Hi Guys,
I'm in a bit of a problem. I bricked my phone and nothing seem to help.
Let me tell whats happened
1. I updated my TWRP in LeTV X500
2. This kinda made my phone to in soft brick mode every time I restarted it went to TWRP
3. I than installed new ROM from TWRP (i think it might be too high for my phone)
4. Phone endup bricked, not switching on, off nothing - redl light only
5. I tried here to install new rom from Windows and Linux via SP Flash Tools - phone is not recognised.
6. I disassembled the phone and detached battery
- now this is actually helped in a way that windows now recognises the phone, but the connection is not continous
- it recognises MediaTek Pre launcher ... few seconds pass
- it disconnets the MT Pre Launcher
- It recognises VCOM USB Port ... few seconds pass
- It disconnets again
- loop like this goes on and on
7. I tried holding any of the buttons (up, down, power and combination) - not helping
8. I believe my last option is to try and bridge some of the points on the motherboard to try and reset the system ... is this correct?
I have no idea what should I bridge with what ... there are no labels on the MB, i'm not even sure where the GND is.
Any ideas fellas?
Here is front of the MB:
Code:
imgur.com/a/b4oWI
Here is back of MB
Code:
imgur.com/a/XgZiV
help will be appreciated
Have you found a solution?
Related
Hi!
I had a problem yesterday with my Amoi N828 cell phone. During a contact list or messages searching, my phone was automaticly restarted. My idea was to make a system restore using option available on the power on/off button. After that I saw chinesse menu which is not understoded for me I pressed some button and after that such process was started and stopped during 15 min. My decision was to a phone restart. And right now, during system initialization I'm seeing only Amoi logo and phone is stoped.
My next step was to flash system again. I found some drivers MT6589, additionally firmware and "SP flash tool"
When I'm connecting phone without battery by USB cable to the system (Win7 32 and 64 bit) is detected and looking the drivers. And now is a problem. my device is visible for the moment and after that is disappears and again - see link below:
youtube.com/watch?v=Wg47gdlB7YU
the question is why? When the drivers are installed, the problem is still same like before - nothing changed
PLEASE HELP ME! I'm woeful ((((
I stupidly formated the memory of my Cubot One mt6589t without backup, i can install firmware V0.8 with flashtool,but the screen has issues, the screen is black with the backlight on, the phone works i could restore even the IMEI's, rooted the equipment via MTKdroid tools, i pushed the build.prop to enable usb debugging, i can see the screen via androidscreencast, even the phone can make calls and connect to wi-fi, but the screen stills black. Can some charity soul, post the g800_cubot_d1_v1.3_2014_03_28_mjk firmware for SP_flashtool, or a backup made in MTKdroid tools of the NVRAM?
Help Please....
:crying:
The process I followed was:
1. Disconnect the Cubot One if connected and installed mtk win7 drivers.
2. Open SP_flashtools v5.1343.01
3. Load the scatter file for V0.8 firmware (obtained from needrom webpage)
4. Remove Battery from cubot one
5. Selected "Format all + download"
6. Click download.
7. Connected Cubot One via USB cable.
8. The flashtool went normally, green indication.
9. Disconnected Cubot, i put the battery.
10. I powered phone (black screen, backlight on)
11. Removed battery
12. Turned on phone with pressing vol minus (-) at the same time with power button.
13. Still black screen, I connected to PC.
14. Loader detected.
15. Open MTKdroid tool, the phone is detected, no baseband visible.
16. Rooted device, installed superSU, succesfull.
17. Open an adb shell, then injected to the build.prop the instruction persist.service.adb.enable=1
18. Rebooted in normal mode.
19. The phone makes the boot sound as normally, still black screen with backlight on.
20. MTKdroid tool detects normally, granted superuser permits.
21. Change IMEI's with MTKdroid tool, rebooted.
22. Phone restarts normally, still black screen.
23. MTKdroid detects phone.
24. Opened on PC androidscreencast and can see the device screen on the PC.
25. Tested making a call and connecting to wi-fi, no problem, screen stills black.
So i think i made a mistake formatting the NVRAM of the device. I suppose with a newer stock firmware i can get back to normal the phone, in the other hand the phone is almost new with no physical damage.
Hello there!!
bump!
Up
Up. help please!
I'll bump it because I need help too, with something related, I lost the recovery mode and I had the same version the 1.3
Need help wit this too. Can anyone post link to this rom .Cant be found anywhere.g800_cubot_d1_v1.3_2014_03_28_mjk firmware
Hello Forum,
Since last week I've been searching how to recover Alcatel OT900 (AV 2.3.4) which is now stuck (i assume semi brick) phone after hard reset.
Below is the status of the phone
*FIRST ///PHONE IS NOT DEAD :angel:
* have no recovery but recently rooted (cannot go to recovery mode)
* when going setup (after boot)
error the setup wizard
(process com.jrdcom.jrdsetupwizard) has stopped unexpectedly.
FORCE CLOSE
* OTU upgrade fail (network connection error)
* by pressing vol - & power & home keys computer (Win7) detects
ALCATEL HS-USB QsBLoader 9002 (comm port)
*When OTU loads and tries to connect to the server then the above driver details vanish from the device manager.
* When powering on as normal Computer tries to install driver but soon shows disconnected
* On Fastboot - vibrates only
Tried several tools but no result there any proper solution for this ? I mean through Windows ? Your step wise guide is highly appreciated.
PS Same problem as : http://forum.xda-developers.com/showthread.php?t=1597847
But can't access fastboot. I came to know that SP flash tool can address this, but what to use in scatterloading? Since there is no scatter .txt files for factory FW or most of the custom FW. I have tried to create the scatter file from MTKDroid tools. but device not connected. I figure out that device is connected only through comm.port but not as usb device (while booting normal startup and pluging in usb the phone is blank /OFF) Did anybody else having same problem? Any alternate solution?
I solved this problem by downloading Firmware ALCATEL OT-990 OS 2.3 (Gingerbread).rar i am new so i cant post link so i will separate some parts. dfiles . eu/files/qqc5kjy05 and following Instructions.txt from inside that archive. I had EXACTLY same problem. I managed to do first step by removing battery for 2 minutes, then insert it and then do first step right away.
Hi guys, I recently purchased a Homtom HT3 for my mother, when it arrived to me I charged it and checked it out a bit just to make sure everything was fine which it was.
She collected it from me the next day and told me she'd start to use it the day after, she calls me up the next day and tells me there's some problems with it and a few people at her workplace tried to fix it for her to no avail. I pick the phone back up and I notice that everytime I power it on, it gets stuck on the "homtom" logo.
As I don't know too much about fixing phones I only took the following steps before asking for advice here; I went into recovery mode by holding up volume and power button, the android guy with the red triangle appeared so I tapped up + power button to get into the recovery(?) menu. I wiped the phone to factory settings and deleted the cache in there but it hasn't fixed the problem.
I assume I need to flash a firmware or something to potentially fix this, but I'm unable to find an official firmware from doogee/homtom's site for the HT3. I've found a firmware that I downloaded from "chinagadgetsreviews" but I'm a bit weary to try and flash with that rom because it isn't from the manufacturer. (even if I knew how to - the only experience I have is rooting my own phone but that's when I actually had access to a working phone, not one thats stuck on a boot logo).
Sorry for the long post but could anyone guide me in the right direction here? TIA
I'm not opposed to not using official firmware, I think I use cyanogen mod(?) on my own phone. I'd just like the problem fixed in the easiest way possible.
Trying to fix it myself by flashing a rom via SP flash tools but I've ran into another problem which is stopping any kind of progress - the phone isn't detected in Windows, I can't enable usb debugging because I can't get passed the boot loop, I've tried installing the ADB driver manually which didn't seem to work (just said it didn't install correctly and left me with a yellow exclamation mark) and I tried to install it automatically via ADB driver installer but it just throws up an error that the device isn't detected.
Any help would be greatly appreciated.
Hello. I bought a Homtom HT3 and next day a done an update with sp flash tool. all gone ok, but phone now wont to turn on. I contact homtom and got all drivers and room to fix it. Now i have a problem , i hit download on flash tool , take off battery + pres volume down + conect phone on usb cable. My computer detect it as USB MTK PORT sp flash tool load only the first red line but not detecting phone info, then after 1 minute i get
s_ft_da_no_response(4001) da didn't send response data to flash tool.
I changed drivers port even to MTK preloader, but i get same error.
NOTE....... All drivers and rom i got original from HOMTOM.
Thanks to all who can help me.
I can show a screenshot if need.
Same here - any solution for this problem?
Kleos89 said:
Hello. I bought a Homtom HT3 and next day a done an update with sp flash tool. all gone ok, but phone now wont to turn on. I contact homtom and got all drivers and room to fix it. Now i have a problem , i hit download on flash tool , take off battery + pres volume down + conect phone on usb cable. My computer detect it as USB MTK PORT sp flash tool load only the first red line but not detecting phone info, then after 1 minute i get
s_ft_da_no_response(4001) da didn't send response data to flash tool.
I changed drivers port even to MTK preloader, but i get same error.
NOTE....... All drivers and rom i got original from HOMTOM.
Thanks to all who can help me.
I can show a screenshot if need.
Click to expand...
Click to collapse
Hello everyone,
Recently I tried to flash my Freer X9 Tablet (aka U89) with Android 7. In the beginning the SP flash tool was not able to detect the tablet, maybe because of a driver clash. Then the flash process started very very slow and stopped in the middle for some unknown reason. I had to exit the SP flash tool.
After that, the tablet seems to be hard bricked. It does not start, it does not respond at all. On the other hand, when I connect it to my laptop, the laptop is able to detect it as Mediatek USB VCOM device.
I came across some threads which mention Meta mode which can make the device start working again but for it to work, I must physically open the device to disconnect the battery since the battery in this device is not removable. I do not really want to do that fearing that the tablet could be damaged while I open it (locks, paint and stuff).
Can it be unbricked in any way without physically opening it? Any help is highly appreciated.
Thank you in advance.
Solved!
Well, I waited for a day and guess what, the battery got discharged. I don't know how. I put the SP tool to download mode (clicked the download button). Connected the tablet to the laptop while keeping the volume up key pressed. I did not release the volume key for 10 seconds even after connecting it to the laptop.
And... boom! it started to flash!!! the tablet works now!