Related
I got this phone from ebay, and it worked a few days before I flashed it so I know it's not hardware or a bad flash on their part because it was stock when I got it. Anyway, I flashed the generic fw through flashtool and it was working fine for awhile until one day it froze and nothing was responsive. The battery died, and I recharged it and threw it into flash mode to repair the firmware through SEUS, and it got it working for awhile until it happened again. So instead I went ahead and used flashtool to put AT&T's fw back on the phone. After I did that, the phone now only vibrates when I turn it on and then does nothing. If it does do something, it just continuously vibrates until I pull the battery. I tried using SEUS and Flashtool to flash another fw because I can get it to flash mode, but it says failed everytime no matter what firmware I use. And SEUS fails right up front when trying to repair. Any ideas?
Pull out the battery....plug the usb cable...run latest flash tool...click on flash button..when it is searching for the fone then put back the battery with pressing the return key.
Recheck the latest driver for 2.3.3
Did it work?
Dude are you aware of rooting procedures?
First you should flash the stock rom back in, then you flash some pre-rooted GB rom. Threads on X10 Android Development are full of options.
jeancca said:
Dude are you aware of rooting procedures?
First you should flash the stock rom back in, then you flash some pre-rooted GB rom. Threads on X10 Android Development are full of options.
Click to expand...
Click to collapse
Dude did you even read my post?
I've been a member here for 3 years and have been flashing Android to phones ever since then. I have looked at the troubleshoots but they were all giving a failed flash. Not to mention this has nothing to do with root or GB, I was talking stock firmware, this brick happened before SE pushed out the GB update.
To subhanker.ds, thank you for the input, I'll give it a shot.
EDIT: Just got the same error
Uploaded with ImageShack.us
As per your screen shot, debugging mode is of....but it is not possible to on now as ur phone is dead.
I think somehow jeancca is correct...use rooting process..(no need to flash any rom)..it will automatically turn on debugging mod & then you flash ur rom...
Hope ur prob will be solved dear...
I've tried several rooting methods that and they all state I should turn on Unknown Sources and Debugging. But I cannot do this, is there a way that will force it into usb debugging as you said?
Actually at the time of flashing debugging mode automatically turn on...
Anyway i'm not getting any clue...although you can try to flash only system.sin file.then see what will happen....best of luck...
I've tried everything I can think of and I still can't get it to work. A new symptom has came up though, when I try and connect it to my PC, it will go into flash mode but after awile the LED goes off but is still recognized by the PC as being in flash mode. Same goes for when I plug it into the charging cable.
Bump.
Sorry for doing it, but is there anyone out there that can help me?! I had to think I have a $200 paperweight.
Hi..... I mentioned this on another post but thought I might see if this might help you. Although I didn't mention the use of other Flashtools in the other thread, I did end up trying Flashtool 2.8.0 and 2.9.1 and the latest edition. In the end I ended up going with the 2.8.0 to start fresh and since that was the one that was used for An Android 2.1, I flashed back to 2.1. With a few instances like those you mention I tried this and worked out.
What I did was open my devices and printers (control panel) and noticed the SEMC USB or IDE blah blah......The device pops up when connecting my phone. I would flash my phone and the go to the "Turn on phone and check debug" and ..... Same as you green light (Flash) would go on and then nothing.
What I did was unplug my phone and Uninstall the device used (SEMC USB or IDE, it named itself differently on an occasion or two) and then started my Flashtool then tried again. Goto Flashtool and prepare your Flash and wait for it to load up (took some time once or twice but....) connect your phone and try again.
I have been messing around with a bunch of apps and FW's and ROMS and lately Unlocking the BootLoader.
Some you can just goto Task Manager and Stop the ADB.exe processes but this uninstall worked excellent for me when needed.
Hope this solves your issue. Good Luck. Oh you may not need the other Flashtools but I have them on file just in case because 2.9.1 gave me a problem before when doing something. You might be able to do with whatever Flashtool you are using but just thought I would share my experience.
I have the same problem . i I flashed it with X10i rom but work for while and after 1 or 2 hours hanged and when i remove the battery it's hang in sony ericsson .
After that I flashed it with SEUS and upgrade to official rom 2.3.3
and has the same problem .DO THINK IT IS A HARDWARE PROBLEM
Tingles said:
Hi..... I mentioned this on another post but thought I might see if this might help you. Although I didn't mention the use of other Flashtools in the other thread, I did end up trying Flashtool 2.8.0 and 2.9.1 and the latest edition. In the end I ended up going with the 2.8.0 to start fresh and since that was the one that was used for An Android 2.1, I flashed back to 2.1. With a few instances like those you mention I tried this and worked out.
What I did was open my devices and printers (control panel) and noticed the SEMC USB or IDE blah blah......The device pops up when connecting my phone. I would flash my phone and the go to the "Turn on phone and check debug" and ..... Same as you green light (Flash) would go on and then nothing.
What I did was unplug my phone and Uninstall the device used (SEMC USB or IDE, it named itself differently on an occasion or two) and then started my Flashtool then tried again. Goto Flashtool and prepare your Flash and wait for it to load up (took some time once or twice but....) connect your phone and try again.
I have been messing around with a bunch of apps and FW's and ROMS and lately Unlocking the BootLoader.
Some you can just goto Task Manager and Stop the ADB.exe processes but this uninstall worked excellent for me when needed.
Hope this solves your issue. Good Luck. Oh you may not need the other Flashtools but I have them on file just in case because 2.9.1 gave me a problem before when doing something. You might be able to do with whatever Flashtool you are using but just thought I would share my experience.
Click to expand...
Click to collapse
Thanks a lot, I will give this a shot as soon as I get home. I'll keep my fingers crossed that this may help me and the others having this sort of issue.
Mobark, I don't think it's a hardware issue. For awhile I was thinking it was a dead screen, but from the people I have heard that did indeed have dead screens, they have lines in the center of the screen while my screen just doesn't turn on.
Hi everyone i am having the same problem my phone only vibrates for sec and the green led just flash for sec than nothing but my phone goes into flash mode but the flash aborts i have also made a thread in which i fully listed my progess and software i used http://forum.xda-developers.com/showthread.php?t=1257581
Nope, didn't seem to work. I think my problem is the phone doesn't want to stay in Flash mode for some reason.
I fix this error, i download and flash this, next i updated in SEUS, my phone is Xperia Play
Sorry for my bad english.
Ok, so I upgraded to 3.0.0 and tried flashing the generic fw again to no avail. And as far as above, the firmware isn't for the x10, it's for the Play, Arc, and Neo.
This is what i did
Not sure if this will work for you but this is how I fixed my phone.
When I first changed the rom on my phone i was on baseband 435. I never changed the baseband with the custom rom install.
My friend factory erased the phone and then it would take 45 - 50 mins to finish booting (would turn on i would see se logo and 50 mins later I'd get to a stock "slide to unlock screen" upon doing so i would get a black bg with the custom batt meter and clock at the top. it also dected the sd wasnt plugged in.
While the phone was on, Sony Ericsson pc Companion would say please mount sd card, and that i couldnt do.
While trying to use flashtool 2.9.1 it would say please put the phone in debuggign mode.
At this point, your ss shows you making it further than i did. because mine wouldnt make it past the date/time (yours starts flashing an fails some way through).
I tried 4 roms and none of them worked.
Then i found http://www.multiupload.com/9H20YEXEHR and After updating to flash tool 3.0.0, and using the stock rom that i posted the link to, It worked. but i had to try a few times. At http://forum.xda-developers.com/showthread.php?t=920746 There are 3 different stock roms for x10a (I used the first one in the x10a list)
I used the one that matched my baseband. Try an match yours if you know it.
When i connected usb, the phone would not turn on. The phone would only turn on with batt in. So i connected usb, held back and put batt in.
Doing this worked, I held the back button until the flash completed.
Also as a note, I did not change the bootloader, that could be why it would boot after 50 mins or so.
I hope this helps.
-Mike
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 ...
Even though I (and other members) already posted about the issue, I figured I make another post for everyone to see.
Hopefully this will help you to unbrick your phone, without taking it apart to disconnect the battery.
First of all: what are the symptoms?
In my case I flashed the phone according to the guides found in this forum. Everything worked pretty well until I wanted to revert from CM13 to stock.
I followed the procedures, but after doing so the phone would not turn on. It would not show that a charger is connected, and, of course it would not boot into recovery.
What happened?
While flashing the phone with the official stock ROM ([ROM] Stock ROM Elephone P9000_Android_6.0_20160419) I also flashed the preloader (as it is not explicitly stated to not do so).
That was the cause of my problems. Without the correct preloader, the phone will not work anymore (except for a fallback method to correct that mistake).
Trying to flash it again resulted in the error message "BROM ERROR - STATUS_EXT_RAM_EXCEPTION (-1073414139)".
What to do?
First, connect your phone to your Computer. Open the Windows Device Manager and leave it open. Press VOL+ on your Phone, and you should see a new device popping up (can't remember the name, sorry), and disappear a few seconds later. That device is the fallback for flashing the phone even in a softbricked state. Make sure the driver for that device is installed properly (as long as there is no exclamation mark you should be fine, but this is a possible problem source).
After ensuring that functionality, it is time to find a preloader which will work. You can try the different stock ROMs found on the official elephone forums (in my case Elephone P9000_Android 6.0_20160304 as well as Elephone P9000_Android 6.0_20160608 worked - ymmv).
Disconnect your phone and start sp_flashtool and load the scatter file associated with the firmware. Select only the preloader, leave it on "Download only", click on "Download", connect the phone to your computer and press VOL+.
The download should start and hopefully complete without problems. After the successful flash, Windows should immediately (maybe after reconnection, not sure) recognize your phone as a Mediatek preloader device, the screen should turn on and show the image for being charged, and also the notification LED.
When successful, you should flash the rest of the ROM to the phone, with the exception of the preloader.
If your phone won't turn on after flashing, leave it to charge for a couple of minutes.
That's what helped me. If you do not succeed right away keep trying.
Good luck.
You´re my man!!!
after more than 10 tutorials to unbrick the phone this way was nearly the perfect one.
i totally agree with your steps, but nothing happened in the SP FlashTool after "DA Download" appeared
To continue with the Download i had to "play" with the Powerbutton too, after 2-3sec of pressing, i heard the device is plugged in sound, then it ran through the steps. phone works as smooth as before i deleted the preloader.
After 6hours of trying, testing, mental breakdowns and thinking i have to buy a new one...
maybe someone else will be happy with this additional hint
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
Hello everyone,
This is my first post here, so I would like to say how great is to have such an amazing community!So way to go to all!
Now let's get to the point.I recently bought a asus zenfone 3 pegasus (x008), which was pre-owned and came with the chinese version of firmware.For some reason I realized when I recieved it,that it had invalid IMEI,so I tried to get it rooted and then with the appropriate tools I may had a good chance of making it able to make and recieve some calls (for a change). All were going well,I installed the right drivers,downloaded twrp for my version, so far so good,but on the way I needed to go back to the original recovery,and when I used the sp flash tool for some reason,it stuck and the process was interrupted.The status of the phone currently is as described in the title,TOTALLY BRICKED,except from the charging LED light.
I tried again with SP to do the same process with the original stock firmware for my device,but the strange thing here is that,although the pc reacts to connection with sound,SP flash tool does not respond at all.No red or purple bars like nothing was plugged.It surely is not matter of time because I plugged it and left it many times for about 5-10 minutes.I used all the possible combinations of keys while it is shut down (no other way to be so far) and even the no key.No response for SP flashtool.I checked my device manager and when I plug it in I have the phone as Mediatek DA usb vcom (Android). I WOULD TRULY APPRECIATE IT if you could help me resolve my problem.