Hi,
I'm a new member here.
8 months ago, I purchased two "Samkimoke T710 LA-I" Android phones. It has Spreadtrum SC6820, Mail 300 GPU, 256 MB RAM, MTK6517, Camera (idk spec needed for driver? I guess).
(I know the above from an App I installed in another T710 mobile.)
The OS was said to be "4.0.2" in 'About Device', i personally think it's Android GingerBread though.
Today, I got a miss call, and after that I just pushed the Power button (to turn the display off), it did so. Now the thing does NOT start, no display while charging.
I've googled a LOT, I tried other batteries, connected mobile to USB and then inserted battery, as was said online, nothing came, I also tried Volume buttons + Power button, and also charge to Power Outlet trick. Nothing worked.
After that I went to a local repair shop, after checking it he said the phone does boot, but is not starting (i think he was referring to it's ROM), he said "he would try to re-install a software", from what I understood, he wanted to flash it or something.
So the questions are:
1. Was my phone "dead" or "hard brick" with OUT any problem/s (just out of nowhere) ?
2. Can i flash it (or even any "hard brick" Android device) myself, and expect it to work? If yes, how?
3. Where can i find a custom ROM this manufacturer used (or it's alternative)? What tool should i use to Flash?
(i guess, personally, driver issue will arise in these cases) I checked the Samkimoke DOT com website, their service is available in China only, and NO Email given for me to ask question about their custom ROM)
Thank you ...
(You can say I'm too greedy to forget that .. i can't throw a device that was working in the morning, and that's just 8 months old )
What's happening here?
I left it for the shop to flash (I've never flashed an Android before), and also since it's Chinese Android - I was unsure of the ROM. So he said he tried to flash it (or flashed it) but it still isn't booting!
Back home, I pressed the Power Button, and I noticed this.
http:\\i.share.pho.to/e7653bef_o.png
1. Before Pressing Power Button
2. After Pressing Power Button (the display starts, as if trying to display something)
3. The display fading away (back to off state -- state 1)
4. Back to State 1
All this happens within a second. Is the phone trying to launch the ROM and not finding it or something? Does the above mean it's not the Hardware issue?
I downloaded the MTK Droid Tool and it does NOT show any info, it doesn't detect it at all.
What should I do in such cases?
Thanks ....
Umm.. Am I posting this in the wrong forum section or something?
stream13 said:
I left it for the shop to flash (I've never flashed an Android before), and also since it's Chinese Android - I was unsure of the ROM. So he said he tried to flash it (or flashed it) but it still isn't booting!
Back home, I pressed the Power Button, and I noticed this.
http:\\i.share.pho.to/e7653bef_o.png
1. Before Pressing Power Button
2. After Pressing Power Button (the display starts, as if trying to display something)
3. The display fading away (back to off state -- state 1)
4. Back to State 1
All this happens within a second. Is the phone trying to launch the ROM and not finding it or something? Does the above mean it's not the Hardware issue?
I downloaded the MTK Droid Tool and it does NOT show any info, it doesn't detect it at all.
What should I do in such cases?
Thanks ....
Umm.. Am I posting this in the wrong forum section or something?
Click to expand...
Click to collapse
i don't think this is your fault, its just the faulty Chinese firmware is terribly developed and half of the time this happens to all Chinese phones. they decide not to work anymore or the usb drivers decide to not like your computer anymore. if there is not life from the device (no boot, no recovery) then its hard bricked. the only why you could fix it is using a jtag and finding the firmware online for your specific device and using that to write the Firmware back onto your device. but that can cost lots of moola $.
stream13 said:
I left it for the shop to flash (I've never flashed an Android before), and also since it's Chinese Android - I was unsure of the ROM. So he said he tried to flash it (or flashed it) but it still isn't booting!
Back home, I pressed the Power Button, and I noticed this.
http:\\i.share.pho.to/e7653bef_o.png
1. Before Pressing Power Button
2. After Pressing Power Button (the display starts, as if trying to display something)
3. The display fading away (back to off state -- state 1)
4. Back to State 1
All this happens within a second. Is the phone trying to launch the ROM and not finding it or something? Does the above mean it's not the Hardware issue?
I downloaded the MTK Droid Tool and it does NOT show any info, it doesn't detect it at all.
What should I do in such cases?
Thanks ....
Umm.. Am I posting this in the wrong forum section or something?
Click to expand...
Click to collapse
Sounds like a hard brick to me, too. Since you didn't "tweak" the phone in any way, it's not your fault. You can do only 2 things: either go to another service shop and ask for repair, or find a toolkit and the necessary firmware files to flash it on your own. From what you're describing, it seems like the firmware is all messed up.
Okay, thank you .. and I didn't tweak it, it just simply stopped working.
the only why you could fix it is using a jtag and finding the firmware online for your specific device and using that to write the Firmware back onto your device. but that can cost lots of moola $
Click to expand...
Click to collapse
find a toolkit and the necessary firmware files to flash it on your own.
Click to expand...
Click to collapse
Where can I find/buy this thing called jtag? Or is it simply the same thing as "jig"? If not, How much would it cost?
Since I bought two of them, I have another T710 mobile (same manufacturer) working with me. I'm kinda scared for it too, should I use CWM or something and back it up right now?
Back to the topic, the working mobile has MTK6515 (as opposed to MTK6517 that the damaged one has), can I still backup/extract the image of one to use in the damaged Android phone?
Thank you ...
So, i was inserting and ejecting this device back and forth, and this time, the device decided to show up in the Device Manager, At 1st, it showed up in the Other Devices, then under the "USB Controllers" as "Unknown Device":
http:\\i.share.pho.to/80f316eb_o.png
It was still not showing up in the MTK Droid Tools, although i had installed already MTK65xx drivers. Then i installed the SpreadTrum Phone Driver, and after connecting the device, i pressed Power + Volume [+] button, and it showed up under USB Controllers as "SPRD COM Enumerator".
http:\\i.share.pho.to/3001fb77_o.png
At first, it said "The device is working properly":
http:\\i.share.pho.to/1ad975d3_o.png
And then it refreshed again and said "The device cannot start":
http:\\i.share.pho.to/dd9ee409_o.png
So this means my phone is SpreadTrum phone so maybe that's why it did not show up in MTK Droid Tools?
Which Programs are available to backup and flash Spreadtrum phones?
Thank you. .....
EDIT: I pressed the Power button in my other t710 phone, and it also does the same blinking as the damaged one does. So that means the phone was, i guess, testing if it's "on" and should display or something, and since it has no contents or has, as a member pointed out, a damaged firmware, it's not working properly..
stream13 said:
Okay, thank you .. and I didn't tweak it, it just simply stopped working.
Where can I find/buy this thing called jtag? Or is it simply the same thing as "jig"? If not, How much would it cost?
Since I bought two of them, I have another T710 mobile (same manufacturer) working with me. I'm kinda scared for it too, should I use CWM or something and back it up right now?
Back to the topic, the working mobile has MTK6515 (as opposed to MTK6517 that the damaged one has), can I still backup/extract the image of one to use in the damaged Android phone?
Thank you ...
Click to expand...
Click to collapse
a Usb jig and a JTag/Riff box are a little different. usb jigs are used for only samsung to force the device into download mode, otherwise known as a easy way to get into download mode. the Jtag and riff box's attach pins to Certain parts of a phone or another device and it Write firmware onto that device since its corrupt or does not want to turn on. these can cost up from $100-200, i would just get another phone my friend .
So, although it shows under Device Manager, I'm already screwed with this device? Can I not flash it by using a Computer?
Thank you ..
stream13 said:
So, although it shows under Device Manager, I'm already screwed with this device? Can I not flash it by using a Computer?
Thank you ..
Click to expand...
Click to collapse
Nope, from what i understand when a device is hard bricked or you have nothing showing, the OS is corrupt and that means the USB drivers are Screwed up so it wont recognize your device.
Hmm ... I have flashed it a couple of times, and it's not starting because I don't have the right ROM It gives the usual short vibration when I press power button to start it. The screen is not displaying anything, as expected. and there is no light.
The device is SpreadTrum and the screen size is 4.3 inch, the roms I downloaded either seem to be that for 3.5 inch or 5 inch
1. Is there something like Custom Barebone ROM which will "work on any device"? OR at least compatible ROM?
[ I purchased the phone for 5860, "repairing" it will cost me 1500 So I'm trying to not go to the repair shop. ]
--------------------------------------------
2. I rooted my working phone with vroot, and used adb to backup the images, the total size is 309 MB, trying to flash it in my device, it's giving me "Failed: Download size is over it's partition" error or "Failed: Operation Failed" error.
Regardless of which FDL.bin file I use, my PAC always gives errors. And those that I download from the web flash fine.
(I'm using ResearchDownload -> Packet option, it makes the PAC file, but the flashing process always results in errors.)
Is there some proper Guide to make the PAC file?
Thanks ...
Hi
Lets get straight to the point
I was running Dev ROM 6.4.14 and wanted to upgrade to 6.4.21. I did the worst possible thing i could, by accident. I flashed ROM not for Redmi Note 3 PRO, but for Redmi 3 PRO. Totally different device. Now my phone is dead. When i connect it to PC only red blinking light apears on phone.
So basicly what can i do in this situation ?
1. Tear down (test point method) ?
2. Throw it away
?
Had the same... Mine was doing nothing anymore.
To be honest I did the teardown method which was doable with the right tools.
However afterwards I believe i didn't have to do this.
Just relax, take a deep breath and take your time!!
I believe this is the best guide to move forward.
http://en.miui.com/thread-235865-1-1.html
I cant follow this guide because my phone is DEAD. Its not beind deteced in task manager in windows. I cant do anything with it in this state
adb devices shows "no device found", so how to move forward from that ?
blinking red might be edl mode, have you checked ports on device manager?
Hello,
Have the flashed succesfull ? I failed flashing sometimes ago and result in the red flash an no screen on. I try to hold the power very long, then it reseted to previous flash. and boot up.
Good day guys.. I just recently started facing a problem with my phone and I need help urgently. At first I forgot my mobile anti-theft password and locked myself out when changed my SIM card. I eventually found a solution by flashing my stock rom using sp flash tool (every option was checked). after this was done successfully , I noticed that whenever I force my phone to 3G only (did this using *#*#3646633#*#*> Network selecting) it never shows a single signal bar. But before this, after flashed my phone I had invalid imei so i solved this by using *#*#3646633#*#*( you probably know the rest). Ok let me continue, during this my problem with the 3G only feature, I began to think that this had something to do with my initial invalid imei, so I decided to do a little research and this is when I stumbled upon SN write tool. In order to use this, i thought it was best to return to the invalid imei stage and so I flashed my ROM again with all the options checked. After this my phone would not come on no matter how many times i pressed my buttons, so i just abandoned my phone for like 6 hours and it eventually came on. So i proceeded to changing my imei using SN writ tool, I installed all the drivers the tutorials i saw said said were necessary eg CDC driver, VCOM driver, etc. And this when I noticed my BIG problem which are:
1. I could complete the task
2. My phone could not charge when switched off.
3. My PC can't detect my phone when switched off.
so far I have tried flashing my phone with sp flash tool to no avail and I have uninstalled all the drivers that I installed....
Sorry about the long story please, I need help, I can't get to my care centre exert as a last resort as it is very far from where I stay. I use a Malata N455 (also known officially as Malata M6 in my country). It runs on Android 5.1 lollipop and Mt6580 chipset. THANK YOU. PS: I can't enter recovery mode cuz no button combination has ever worked for me.
I'm still a big fan of 1-800#s and that's why I always sign an at&t contract even though I don't need to. I'm sure you took out battery not that I know what this will do.I do miss uscellular!No sim card but I did manage to mess that up being curious wondering fee what's A band and B band and found out real fast It said if you want to make a collect call when I opened it.
Sent from my 9020A using Tapatalk
I need help with unbricking my Ulefone Power 2.
First, a few words about how the issue came to be: I bought the phone two days ago and after bringing it back home, and powering it on, I noticed that the icons were not the same as the ones that were on the displayed phone's screen (although I found the new ones to be an improvement, I thought that maybe I have to install "the official ROM" no matter how unattractive it was, as the phone would probably work better with it).
So I went to the official ulefone site, saw the instructions for installing the drivers for windows 10 as being fairly easy to do myself, and downloaded the sp flash tool provided on the site and then, of course, downloaded the official stock rom from the ulefone site.
After installing the drivers, I tried to flash the phone and then the first error happened. Naturally, I sought the answers on Google, as any proper boy scout should, and learned in the process that I should hold volume up while connecting the phone.
And it worked!
Alas, my happiness wouldn't last long as another error decided to stand in my way. BROM Error: sec imghdr type mismatch. Of course, I took another trip to Google's search bar.
Then I tried many different solutions, those being:
Downloading Sp flash tool v3 instead of v5 and trying to flash with that one - this one asks something like if I'm sure that my scatter file is legal (how it cannot be, I don't know as it was downloaded from theanufacturer's site). Regardless, i clicked download but it couldn't recognize my phone I guess as nothing was happening when I plugged it in)
Afterwards I tried to format the phone using the sp flash tool v5 and then flash the ROM onto my phone but that also did not work (with the exact same error as last time - imghdr type mismatch).
Now I have a phone that cannot power up and when plugged in it constantly connects/disconnects regardless of me holding down the volume up button (could be that I'm holding down the wrong button).
Please, is there anyone who can help me unbrick my phone? I just want to flash the stock ROM onto it, that's all
Dear community, my Redmi Note 4 had its battery dying, so I ordered a new BN41 battery on ebay. After receiving it, I followed a video tutorial on youtube in order to replace the old battery with the new one. After that, I started the phone and since then it's in bootloop mode. The only thing I get is the Mi splashscreen without the android message at the bottom, and it keeps looping like that if I dont hold the power button in order to shut down the device. If I press volume down and power button I can enter fastboot mode. I also managed to unlock my phone with the official xiaomi unlock tool. I tried to use SP Tools with the fastboot rom "Redmi Note 4 MTK Latest Global Stable Version Fastboot File Download" ( nikel_global_images_V10.1.1.0.MBFMIFI_20181206.0000.00_6.0_global_b73ca18a6f.tgz) from en.miui.com a-234.html
I use SP Tools version 5.1648 with replacing the cust.img with a cust global I found on different forums.
In SP Tools I leave all checked and "Download only" mode, when I plug the phone all the process runs successfully until the end, but then when I unplug the phone and start it it's still in bootloop (no android message at the bottom of the screen, only the "Mi" logo in the middle of the screen ).
I haven't tried anything else, and not sure what else should I try, any suggestions would be appreciated.
Thanks in advance for your help. Let me know if you need any additional information that could help to resolve the issue. Before changing the battery everything was working fine, official rom, just the battery was not holding anymore.
Best regards,
Even though bootloops are generally a software issue, I would carefully consider the fact that it occurred after you physically opened your phone and replaced the battery.
I would open the phone again and examine it for the possibility that a connector inside has been disturbed and maybe not re-seated correctly.
It may also be beneficial to temporarily put back in the original battery just to rule out the possibility that the replacement battery is not causing an issue, (though I can't see how it could).
Once you have been able to rule out any physical problems then look into reflashing the rom etc.
Sent from my Redmi Note 4 using Tapatalk
Hi, Thanks for the feedback.
Actually, I have proceeded to physical checks, tried previous battery, connectors, but unfortunately still the same...
I have tried several fastboot images using SP Flash tool, always the process ends successfully from the tool side, but phone remains in bootloop after turning it on.
Could installing TWRP be any sort of help ? I am not an expert so trying to figure out the possibilities. I have not able to install TWRP anyway so far, there is a lot of information out there but I'm having trouble to figure out what is the right information. As I don't have access to android to set the phone in debug mode I am trying to install TWRP with SP Flash tools, but haven't been successful so far.
Any additional thoughts ?
Best,
Hi, after further inspection I noticed that I damaged the main board flex for my redmi note 4 while replacing the battery.
My Redmi Note 4 is MTK processor (not Snapdragon) The flex on my phone says :
CM885_MAIN_FPC_V2.0
FWSZ 42 16
I find on aliexpress , ebay, replacement flex cables but with other references.
Are the cables for SD & MTK different ? From the pictures they look pretty the same, but apparently they are different can someone confirm ?
For MTK version of the phone, I find replacements, but with other references than mine. I did not found any with the FWSZ 42 16 reference ; but they all have the CM885_MAIN_FPC_V2.0 reference
Does anyone knows which reference of cable I can order, knowing that my phone is an MTK version of the redmi note 4.
Thanks.
Quick update, I ordered a new CM885_MAIN_FPC_V2.0 cable flex for my Redmi Note 4.
Now I'm waiting to receive it, replace it and see if my phone boots normally.
Good luck. I hope it works.
Sent from my Redmi Note 4 using Tapatalk