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
Related
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 ...
Hey guys, please forgive me for any bad etiquette or lack of information (any information I can provide is available upon request if I leave anything out). I am new to forums in general and especially to XDA, which seems like a good place to get help.
I recently purchased a Sony Xperia Z2 Tablet from Craigslist under the assumption it was a fully unlocked tablet not associated to a carrier. Turns out it was a Verizon Z2 tablet. I dislike Verizon with a firey passion and without getting into too many details, I'm fairly certain they won't help me because a) this tablet wasn't purchased through them as a customer and b) Verizon and I have bad history (unauthorized account modification, shady charges, etc.)
So I thought I'd do my best to make the tablet mine since the asshole who sold it to me has ceased all contact and I don't know how to get a hold of him anymore. No receipt and a data-less tablet.
Anyway, I successfully rooted the tablet and began installing apps that I installed for my G4 when I rooted it (SuperSU, Adaway, Greenify, etc.)
Things were going well but I realised I wanted anything that had to do with Verizon removed from the tablet so I was going to flash Cyanogenmod onto it with a guide I found online. Now rooting and installing custom recoveries was familiar territory and I did these flawlessly. It had TWRP and I made a backup of the system -no Nandroid, sadly-and I began the flashing process. The process said it completed without issue and I went to reboot my device. Enter my current situation:
The device, when I attempted to turn it on, all it did was vibrate constantly until I let go of the power button. Attempting to enter recovery mode (green LED, power + vol down) it showed me, instead of TWRP, a very basic recovery mode with basic options. "Continue booting up", "enter safe mode", "system recovery", and "power down". I tried entering safe mode and it just shut back down, I tried doing a system recovery and it shut down. The only time I ever see the "SONY" logo is if I'm entering this mode. I can enter what I assume is "fastboot mode" (power + vol up and plugging the device into a PC). Nothing on the screen but the LED is blue. I am trying to find guides to restore it if I can and it all looks promising but the only things I know how to really do are root and install custom recovery. I know there are PC tools I can use to send commands to it while it's in fastboot, or send commands in general I just don't know where to begin.
Does anyone know how to fix this? I know it was from Verizon, which sucks, and I know the problem most likely occurred with the attempted flashing of Cyanogenmod. I think I read somewhere I might have done something regarding mismatching kernal numbers. I couldn't find a way to unlock the bootloader so I assume that had something to do with it too.
If someone could give me a guide to restore it to at least its stock ROM where I can begin rooting and installing a custom recovery again, that would be great. Even better would be just flashing a ROM on there that doesn't need Verizon or being able to take it to a stage where it's unlocked and the only evidence it was ever with a carrier is the Verizon logo on the back. I'd really hate to think I wasted money on this and now I'm at a dead end because of a mistake I made. This was supposed to be a gift for my mom on her birthday which is coming up soon. So if anyone knows anything, or has a guide where we can at least get the thing bootable again and I'll just try and deal with a rooted locked device, that would be great.
Thanks for considerations,
Marmalade_Shaws
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Ez-go said:
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Click to expand...
Click to collapse
Sorry if this is late... But where can I find the stock? I've searched everywhere and I would need to do it from a flash tool on my PC? I could use all the help I can get.
I just had a very similar experience to the OP, seemingly identical in every way, and am curious if anyone has a solution.
ADB won't function at all, and the bootloader has blocked any sort of flashing via fastboot. Can't boot into TWRP, it goes into a very minimal "recovery," which I imagine is the stock tool, and the Factory Restore option there does absolutely nothing. Flashtool would work great if ADB / Flashmode was at all functional (device blinks and vibrates in a fashion typical of something bricked, and no connection is picked up).
Verizon Z2 Tablets are 561s.
This thing dead or is there some way to push back onto it?
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
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
iamnekro said:
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
Click to expand...
Click to collapse
What you read in the internet means re-flashing your stock rom (system), that is the fix for your problem, the way to do it is to download and install Samsung USB drivers if you hadn't done that already, and Download stock rom from here or here search your model number in the search box and choose the stock rom based on your country, and flash with Odin, it's pretty much the same way you tried to root using CF-ROOT method:
1-you boot into download mode (volume down + home button + power button)
2-and then connect your phone to PC.
3-open Odin and uncheck everything except "auto reboot" and "F. Reset Time" (you should find it like that already), make sure your phone is recognized by Odin, you will see a blue box with a message saying "0:[COMX]" where X is a number.
4-press AP (or PDA in some versions) locate your stock rom which should be in .md5 format, and choose it, then 5-press start.
6-wait for the process to finish (takes a while) and then the phone should reboot itself and you will get a message in Odin saying "Reset!"
PS: you must register on the sites to download..bad thing i know but it's obligation.
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
iamnekro said:
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
Click to expand...
Click to collapse
Give me your model number.
Sorry found it in the thread title
@iamnekro
That is the link from the first site:
SM-T337T latest firmware android 5.1.1
That is the link from the second site:
SM-T337T latest firmware android 5.1.1
Obviously you didn't search at all...LOL
PS: It's called Stock Firmware or Stock ROM.... not Drivers
Register on any of the sites first to download.
And press the thanks button please
Regards Migo
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
iamnekro said:
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
Click to expand...
Click to collapse
It doesn't need any advanced computer and only the size of the stock rom and Odin, it's no big deal.
I only want my Wogiz WX40 to work properly again. It somehow got into a booting loop and I spent many hours figuring out how to flash it due to drivers acting unexpectedly, incorrect instructions for my device and so on.
I finally got it to flash with stock software I got from needrom using SP Flash Tool. However 1) none of the bottom keys work now and 2) it looks as if the resolution is set too high for the device and I think there is also some slowness when using the phone. I have tried clicking upgrade firmware and formatting the entire flash and using different versions of the software and the result is always the same - the bottom keys not working in particular makes it unusable. I tried downloading the stock rom from another location but after downloading it said I needed a password.
So what is the next thing I can try? I'm at my wit's end here and just want it to work again. Thanks for all help.
Anyone know what I should try? For example what custom RAM + firmware might I want to try? At this point I don't care what it is as long as it works. It's a MT6580 device if that helps.
God, I FINALLY got it working.
In case there's anyone else that runs into this: My mistake was getting the stockrom from needrom, every one of those roms for this phone is bad. Get the rom from shareas.us and use SP Flash Tool to flash it, and even then you have to try to get the one that isn't password protected with no password. Leave the battery in, turn the phone off, use option "format + download" in the software and click download BEFORE you connect the phone, NOW connect the phone and after a little while it will start downloading. Disconnect the phone when it's done and switch it on, it will take a REALLY long time to boot up the first time but it should then work.
That's what came from hours of trying to get it to work. The tutorials etc. online are so confusing, even some incorrect instructions like saying I should take out the battery that are completely false and I would never have gotten it to work if I paid more attention to them. I don't ever want to go through something like that again. I finally have my phone back.