[Completed] Soft Brick Sankey TAB 1010 - XDA Assist

Hello people, even though I'm a frequent user of xda, this is the first time I post an issue, so I'd like to thank in advance for all your help. Now, let's get straight to the point.
I have a Sankey TAB 1010. Unfortunately, this 'brand' doesn't have a site, and I couldn't find any data or ROMs anywhere (I'd say it's an orphan Tablet). Since it began to lag, and somehow Google Play Store suddenly disappeared, I decided to make a full nandroid backup, just in case something else happened. I rooted my device. Then I downloaded and installed CWM (v6.0.2.8) following these instructions: http://forum.xda-developers.com/showthread.php?t=2189640. From cpuinfo, I got my device was an Allwinner A10, with 10 partitions. Hence, I downloaded that version and flashed it via adb.
My tablet booted into CWM and it got stuck there (bootloop). The problem is I can't install/wipe/backup/restore/mount anything. I could only mount my ext sd card and format it. Scripts at the bottom are: E:Can't mount /cache/recovery/command; E: Can't mount /cache/recovery/log; E:Can't open /cache/recovery/log; Error mounting /data, /emmc, /cache, /sdcard, and so on.
I've also tried many flashing tools: Odin, LiveSuit, Phoenix Card with no success. Obviously, since I don't know which ROM is compatible with my Tab, I've tried many generic ROMs (ICS 4.0.3).
I also attach my CWM log.
I know it's and old and cheap tablet, but instead of having a paperweight, and before buying a new tablet, I'd like to give it a last try, besides, while it worked, it performed really well.
Again, I really appreciate all your help.

Hi,
That was an unwise decision unfortunately. Flashing anything not made for your specific device can often destroy your device. The app simply took a best guess at what device you had and decided on Allwinner. But it isn't and surely the hardware is not identical with your device.
So now you're in a bind here. You likely need to reflash your factory firmware. Finding it will be the challenge. I'd contact the manufacturer and see if they have it, along with flashing instructions. And hope you haven't already bricked the device.
Unfortunately I can find nothing at all relevant on XDA, so you can ask here.... But with no mention of your device here, finding help will be hard. Again... Try the manufacturer, it may be your best chance.
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
---------- Post added at 09:38 PM ---------- Previous post was at 09:35 PM ----------
Also, Odin and all those tools are for specific manufacturers devices.... They are not universal. And I don't know what roms and firmware you've tried, but again... Only the firmware for your device will help.
I'm not sure what all you may have partly flashed now, but it doesn't look good.
Please read Read read before doing anything in the future. And no matter what device you have.... Only flash software made for it... Nothing else.
Hopefully you can sort it out.

Darth said:
Hi,
That was an unwise decision unfortunately. Flashing anything not made for your specific device can often destroy your device. The app simply took a best guess at what device you had and decided on Allwinner. But it isn't and surely the hardware is not identical with your device.
So now you're in a bind here. You likely need to reflash your factory firmware. Finding it will be the challenge. I'd contact the manufacturer and see if they have it, along with flashing instructions. And hope you haven't already bricked the device.
Unfortunately I can find nothing at all relevant on XDA, so you can ask here.... But with no mention of your device here, finding help will be hard. Again... Try the manufacturer, it may be your best chance.
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
---------- Post added at 09:38 PM ---------- Previous post was at 09:35 PM ----------
Also, Odin and all those tools are for specific manufacturers devices.... They are not universal. And I don't know what roms and firmware you've tried, but again... Only the firmware for your device will help.
I'm not sure what all you may have partly flashed now, but it doesn't look good.
Please read Read read before doing anything in the future. And no matter what device you have.... Only flash software made for it... Nothing else.
Hopefully you can sort it out.
Click to expand...
Click to collapse
Hey, that was really fast. Thanks. I'll try to contact the manufacturer. As you said, it'll be a hard thing to do since it doesn't have a website and as you might have seen, this brand isn't really known around Internet. I've found a contact e-mail. I'll try to ask for support there (if Sankey still exists). Problem is I bought it in a trip, so going back to the store I bought it will be more expensive than buying a new device, besides, guarantee wasn't valid anymore.
I know it was an unwise decision. I only tried it because I experienced some issues with my tab (even after Factory reset). As I said before, Google Play Store dissapeared, and the OS became unstable and laggy. And since it wasn't the first time I did this stuff (I also have an SE Xperia Play in which I installed Gin2Kitkat rom with Lupus kernel), I decided to install a Custom Recovery and make a nandroid backup. It was an awful decison as you said.

It happens. It's how we learn too! ?
Good luck again!

Thank you. Thread closed.

Related

CWM 5.0.2.7 restore issue

CWM Backup and Restore: It backs up fine. But it won't restore. I can't remember the error message...something about rfs and can't mount. I know that's not much help. I was wondering if anyone besides me has had problems restoring with this version of CWM, and has a fix for this problem. I have presently done several backups of my stock rooted GB 2.3.6. And I can't restore any of them. As a noob to the Samsung Charge, I have very little knowledge to work with on this. But it seems to me that I read something somewhere that said I needed to use ADB to do something. Darned if I can remember where I saw it. Any help here would be appreciated. Thanks in advance.
The last version that I know of that had Backup/Restore working properly in was the 0817 version but hell if I know where you can get it.
I have it on my hard drive for my own personal reasons but imnuts has said that I can't upload it or redistribute it in any way. I personally can use the file if I so choose to keep it but I can't upload it to anywhere.
Perhaps you can IM imnuts to send you a copy of the 0817 version.
trparky said:
The last version that I know of that had Backup/Restore working properly in was the 0817 version but hell if I know where you can get it.
I have it on my hard drive for my own personal reasons but imnuts has said that I can't upload it or redistribute it in any way. I personally can use the file if I so choose to keep it but I can't upload it to anywhere.
Perhaps you can IM imnuts to send you a copy of the 0817 version.
Click to expand...
Click to collapse
if you don't mind my asking why is it banned from being posted now? that's the orange 4.0.1.4 version that was up publicly for months and had few issues besides the voodoo menu being removed/disabled... I guess if imnuts ok's it I'll post or pm a link to anyone who needs it
He got pissed at me for having a link to it, that's all. If you want to attach it to your reply, be my guest. I just don't know what will happen.
trparky said:
He got pissed at me for having a link to it, that's all. If you want to attach it to your reply, be my guest. I just don't know what will happen.
Click to expand...
Click to collapse
ah yes I remember, something about imnuts himself wanted to host it to keep track of support and downloads.. nevermind then I won't post publicly but if anyone wants it just pm me
blazing through on my Acer A500 via XDA app
I have found that CWM 5.0.2.7 has removed "Voodoo" from the menu. Anyone know why? I'm just trying to figure out why my nandroid restore function does not restore. Being a noob to the Samsung phone, I can only guess that it has something to do with the existing partition format when restore begins. IOW, is it the same as the backup? If not, it will fail. Am I getting close, or am I still clueless?
Lexus One said:
I have found that CWM 5.0.2.7 has removed "Voodoo" from the menu. Anyone know why? I'm just trying to figure out why my nandroid restore function does not restore. Being a noob to the Samsung phone, I can only guess that it has something to do with the existing partition format when restore begins. IOW, is it the same as the backup? If not, it will fail. Am I getting close, or am I still clueless?
Click to expand...
Click to collapse
backups may or may not work with the new 5.x CWM, some people say they can do it and doesn't work for others so I'd just stick with the 4.x CWM... voodoo options were removed from CWM due to them not working right or not working at all sometimes when trying to disable lagfix which caused bootloops and softbricks
Same problem on Samsung Epic 4G. Backed up rooted stock FC09 & flashed to CM9 Beta 3. Attempted to restore the stock FC09 & error message popped up. I tried this with & without data/cache/dalvic cache etc., etc. wipes. Same problem either way. I also noticed the time stamp on the backup was dated 2005. Wayyy offf ! ! ! Did you have the same incorrect date stamp? I wonder if changing the date on the backup will fix the issue.
---------- Post added at 07:52 PM ---------- Previous post was at 07:14 PM ----------
Just Reposting To Give Further Detailed Info
I'm sure you already know of this issue but, I'll re-post here as from my understanding, this is updated most often & I'm really amped about this project.
Major stock Samsung Epic 4G Gingerbread FC09 restore issue.
I did this exactly:
1) Started stock FC09
2) Odin to cwm-5.0.2.7-epic4g.tar.md5
3) Flashed cm-9-20120507-SNAPSHOT-epicmtd-beta3-pre9.zip using CWM 5.0.2.7 recovery mode (volume down, camera button & power button combo)
4) Backed up rooted stock
5) Attempted to restore the stock FC09 to make sure it works before I got too into the new release
6) Error message popped up
7) I tried this with & without data/cache/dalvic cache etc., etc. wipes. Same problem either way. I also noticed the time stamp on the backup was dated 2005. Wayyy offf ! ! ! Did you have the same incorrect date stamp? I wonder if changing the date on the backup will fix the issue.
Again, my deepest apologies but, right now, I'm like the kid who missed the ice-cream truck. I'm not new to flashing but, am new to trying to run a restore. I only wanted the stock FC09 back because Swype wasn't included in the CM9 Beta 3 release & the text messaging background is white (kinda thwarts the sleek, stealthy black color scheme). Will there be a black text messaging background soon? Let me know if I can install Swype using Titanium Backup or any app backup app. If I can at least have Skype, I'll be good as my Beta 2 Bluetooth issue has been corrected.
---------- Post added at 08:03 PM ---------- Previous post was at 07:52 PM ----------
Sorry. I meant to say I flashed Deodexed-FC09-BML.zip before I flashed cm-9-20120507-SNAPSHOT-epicmtd-beta3-pre9.zip
---------- Post added at 08:23 PM ---------- Previous post was at 08:03 PM ----------
Brain farts today >.< I also ran a CM9 Beta 3 backup before I attempted the stock FC09 restore. After the FC09 restore failed, I tried the CM9 Beta 3 restore & that worked perfectly so, again, my suspicions lye in the wrong date stamp factor. At some point tonight, I'll test this theory and post the results. If anyone beats me to the punch, awesomeness.
So you bumped a 5 month old thread in the Charge forum to say you had a similar issue with an Epic 4G?
Well
Whatever the case may be, the rules of the site are to post similar questions/concerns in a relevant thread that has already been started. I had no idea this was the "charge" forum as nothing above clearly states that. And instead of just saying the generic, "same problem", I opted to give as much detail as possible considering we're dealing with later released software.
Casey Stellar said:
Whatever the case may be, the rules of the site are to post similar questions/concerns in a relevant thread that has already been started. I had no idea this was the "charge" forum as nothing above clearly states that. And instead of just saying the generic, "same problem", I opted to give as much detail as possible considering we're dealing with later released software.
Click to expand...
Click to collapse
You can clearly see at the top of the screen what forum your in. CWM is individually built for each phone, and not every phone is going to support the same features in the same way. Chances are, no one here is going to know anything about the Epic unless someone here just happens to own one.
Wow
Man that thing's tiny. But, as I stated, I didn't notice that & I only posted because the rules say try not to start a new thread concerning a topic that's already been posted. I'm aware each CWM is custom to every phone. I posted the exact details in case someone does notice this thread & has a solution or a definite no it can't be done. I have read on other posts that CWM will restore other custom non-stock ROMs just fine. One source claims people have been able to restore stock back-ups just fine while others have not. But, there were no definite solutions or enough details to go on. Still waiting for a return on that.
XDA (and others) are built around the idea of device specific forums as there are many differences between devices, even in the same family, that prevent anything for one device from working on another. The Droid Charge, as an example, is in the Galaxy S family, but none of the Galaxy S stuff will work directly on it. Even further, the Galaxy S Aviator and the Droid Charge are the same hardware for different carriers, and nothing for the Charge will work on the Aviator. Don't hesitate to make a thread in one device forum just because a thread exists in a different device forum. There's a "Search this forum" button at the top of every subforum. Use it for your device, and post in that forum if you can't find anything.
O.O
Well now I know I've been up to long. I didn't even realize the fact he said "Samsung Charge" nor was I aware there is a Samsung phone called Charge. But, in my defense, I attempted to start a new thread but, as I was typing out a title for the post, the site showed suggestions of other posts that may have my issue already resolved or at least discussed and this one seemed to be the closest. Had I known the Charge was a phone, it may have stuck out more & I would've known I was in the wrong place -_- Silly me. I am glad to announce however that after a little tinkering, I think I have found the solution to my issue. I'll post any results and details in the proper forum. Sorry for any inconveniences.

[Completed] [Q] Installing Android Lollipop on a unknown tablet.

Hello! This is my first post on this forum, but I'll try to be helpful.
Well, I got my hands on a tablet. Which tablet? I have no idea. The "About page" on the settings only says that the Model number is M1706. And nothing else. (Besides that it's running on Android 4.2.2)
Since Android Lollipop is out, I've been dying to try it. Unfortunately, I don't have a device that supports it, so I though I'd try to install it on this random tablet that I have.
And here's where the problems start.
I tried flashing a AOSP Lollipop build to the tablet, but it always aborted. (From this thread)
Then I tried to install a custom recovery to see if that would help.
Managed to find the TWRP apk and install it. Unfortunately the app crashes when I open it.
So I tried downloading it from the App Store. The thing is that my tablet doesn't have the App Store app.
I tried many different versions, but none of them were able to be opened. It's like a process was killing the app, I think. I have no idea, though.
I then installed Clockworkmod ROM Manager to see if that would work.
It installed and opened, but it can't flash ROMS unless my tabled is rooted.
Since this is a mistery tablet, I don't think there are any root methods for it.
That's my situation right now.
Any suggestions on what I can do to achieve my goal of installing Android Lollipop on my tablet?
Hi,
I have to say, you're swimming in dangerous waters here.... And so far you've been extremely lucky. You can't flash anything to just about any device, unless it's made specifically for your device. Many times trying to do so can brick (destroy) your device.
So you'd be best to stop trying to install things made for other devices.
As far as your device getting Lollipop, that seems doubtful. I say that because it's on Jelly Bean.... Not even kit Kat. Of course that's an educated guess though. And until you find out what actual device you have, There's not much we can do for you. Also, you won't know if there's anything out there for your device... Cause you don't know what device you have.
I'd work on solving that mystery... And go from there. ?
Good luck.
Darth said:
Hi,
I have to say, you're swimming in dangerous waters here.... And so far you've been extremely lucky. You can't flash anything to just about any device, unless it's made specifically for your device. Many times trying to do so can brick (destroy) your device.
So you'd be best to stop trying to install things made for other devices.
As far as your device getting Lollipop, that seems doubtful. I say that because it's on Jelly Bean.... Not even kit Kat. Of course that's an educated guess though. And until you find out what actual device you have, There's not much we can do for you. Also, you won't know if there's anything out there for your device... Cause you don't know what device you have.
I'd work on solving that mystery... And go from there. ?
Good luck.
Click to expand...
Click to collapse
Eyyup. I know what I'm doing is very dangerous, but this tablet is basically useless without any form of Google apps. Besides, I think it's a prototype tablet, so even if I brick it, I won't be sad. I got it for free, after all.
I'm trying my best to figure out which device it is. Usually when you have Google apps in a device, Google Play store shows its type when you install an app using Google Play Store on a desktop. Since I can't get Google Play Store in it, though, it may be a lot harder. I still need to try installing Google+ to see if it works. Will come back with the results in a bit.
Hi,
If you want to post about this further, please post here...
[Ask Any Question][Newbie Friendly]
XDA Assist is here to help members navigate the site, not for support.... So this is not the place to discuss your progress unfortunately.
Good luck! Thread closed.

[Completed] [Q] Could we please start a forum specifically for ZTE Supreme/Vital/Quantum/N9810?

I've been searching for info specifically for rooting/CWM'ing/ROM'ing this phone for a couple of weeks now and this device seems to be the bastard child of the Android world. If I owned a ZTE Blade I would be fine already. I know that help for this device exists somewhere, but using the XDA search tool doesn't pull up anything. I've searched for "Supreme", "Vital", "Quantum", ZTE in general, etc, etc, and the only thing that comes up is the LG Quantum which is obviously no help at all. And it seems that none of the other Android "help" sites have any better luck with specific information for this device (it's always a "this works for most devices, but your mileage may vary" kind of thing).
Basically I broke my phone from Virgin Mobile, bought a cheap used one in good condition off of eBay, but unfortunately the new one is tied to Sprint. Doing an ADB backup/restore from one device to the other does not copy over any of the carrier information so that was no help. It appears that this info would be copied over with a Nandriod backup, but I can't do this until I install CWM. I can't use ROM Manager to flash in a CWM image because this is not a "supported" device. I've tried using fastboot but it just waits forever for the device to connect whether I have the ZTE or Google USB drivers installed. I've tried flash_image but it throws an error saying the recovery partition was not found. I've tried just about every solution I can find any hint of anywhere online and I'm at the end of my rope. The only good news is that I was at least able to root my device using KingRoot! It's everything after that which has been the problem... I'm hoping somebody here can point out a link to a GOOD source for exactly how to at least load CWM for this specific device so I can get Nandroid going. Ordinarily I wouldn't mind experimenting with building this from source myself, and I'm sorry for taking the lazy approach and asking for somebody else to do the grunt work, but I work 12-16 hours a day and just don't have the brainpower available to deal with this right now. I just want my phone back!
As a second item, I would very much like at some point to play with loading Lollipop on this device. I've found a link which on the surface seems to have good info, but then when you try to download the image they hold the data hostage and expect you to "complete these dozen offers". NO, I'm not going to give them all of my personal info, and I'm also not going to jump through their bs marketing hoops. But anyway, this is entirely secondary to getting my replacement phone up and running. The link to this info I found is:
cwm-twrp-recovery.org/2015/03/zte-vital-n9810-5511.html
Copious thanks in advance for helping me to keep my sanity!
Hi
Thanks for writing to us at XDA Assist. I can't find anything relating to your question on XDA, please ask your question here:
Android Q&A, Help & Troubleshooting
If you wish to request a device forum for this phone you can do so in this thread:
*** New Device Forum Requests ***
Good luck!
No response in two days, thread closed.

[Completed] Can Clockwork or another recovery program find and backup your truly stock ROM?

My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Duende101 said:
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Click to expand...
Click to collapse
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Sam Nakamura said:
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Click to expand...
Click to collapse
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Duende101 said:
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Click to expand...
Click to collapse
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Totally cool. It's a tough question.
The OG firmware thing is the toughest part to understand. Just wanted to make sure I was clear in my explanation and question.

Homtom HT17PRO MTK6737M HardBricked

I need help with my mtk6737m phone which i bricked in a really dumb way
I need help flashing it with SP Flash Tool which gives an error that says:
S_FT_ENABLE_DRAM_FAIL (0xFC0)
Here is how i bricked it.
Today i decided that i want to flash a custom recovery on my phone, so i did and it didnt work.
For some reason when i tried to boot to the custom recovery it didnt work, it went to the stock one
For some reason i got stuck in a boot animation too...
So then decided that it was a good idea to flash to complete stock rom back to my phone,
but chose the format all + download option, so that the changes the custom recovery made
were deleted. Well, so i thought...
Is there any way to fix my bricked phone? Its the only one I have :crying::crying::crying::crying:
dekannomad said:
I need help with my mtk6737m phone which i bricked in a really dumb way...
Click to expand...
Click to collapse
I don't have this device but, you may be able to obtain some member guidance within the following thread.
https://forum.xda-developers.com/showthread.php?t=3385527
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, you may be able to obtain some member guidance within the following thread.
https://forum.xda-developers.com/showthread.php?t=3385527
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Hello, I know how to use the flashtool, my phone is completlely bricked and doesnt turn on, thats what I dont know how to fix. I got a response from another user saying i lost imei and completlely removed everything inside my phone and said maybe i can get help here, so far nothing
dekannomad said:
Hello, I know how to use the flashtool, my phone is completlely bricked and doesnt turn on, thats what I dont know how to fix. I got a response from another user saying i lost imei and completlely removed everything inside my phone and said maybe i can get help here, so far nothing
Click to expand...
Click to collapse
This wasn't extremely clear...
There's really not much of anything on the forum regarding a Bricked H17.
The following links are probably the best you're going to be able to locate via a Google search.
The following is just a few guides (with downloads) for installing the Stock Firmware back to your device.
https://www.getdroidtips.com/stock-rom-on-homtom-ht17/
https://www.getdroidtips.com/install-official-stock-rom-on-homtom-ht17-pro/
https://romprovider.com/2018/02/install-official-firmware-homtom-ht17/
The following is just the download firmware from the HomTom website.
https://www.homtom.cc/DownFile
If your device is completely unresponsive (aka dead) then the only real option for you is either to return the item for a repair/replacement where you had purchased it or just to contact HomTom.
https://www.homtom.cc/about-us/
I'm sorry that I can't help you out any further than this...
I do wish you the best of luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
This wasn't extremely clear...
There's really not much of anything on the forum regarding a Bricked H17.
The following links are probably the best you're going to be able to locate via a Google search.
The following is just a few guides (with downloads) for installing the Stock Firmware back to your device.
https://www.getdroidtips.com/stock-rom-on-homtom-ht17/
https://www.getdroidtips.com/install-official-stock-rom-on-homtom-ht17-pro/
https://romprovider.com/2018/02/install-official-firmware-homtom-ht17/
The following is just the download firmware from the HomTom website.
https://www.homtom.cc/DownFile
If your device is completely unresponsive (aka dead) then the only real option for you is either to return the item for a repair/replacement where you had purchased it or just to contact HomTom.
https://www.homtom.cc/about-us/
I'm sorry that I can't help you out any further than this...
I do wish you the best of luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Sorry, english is not my main language, its actually portuguese
I'll do my best to explain what happened from the beggining:
My homtom had some issues like, when you used the camera in any app it was dark, and on instagram stories, there were glitches on the screen, green and purple stuff started appearing in the screen and you couldnt see what was happening, so i decided to change my rom to a custom one.
I saw some tutorials..... and after watching them i tried to install TWRP so i could flash the custom rom..
After installing TWRP it wasnt working, when i tried "volume up + power" it went to the stock recovery.
So i thought it was a good idea to select format + download on SPFlashtool so it formatted the phone reseted all the changes i made...
After clicking, the phone immediately shut off and SpFlashtool said: S_FT_ENABLE_DRAM_FAIL (0xFC0).
I dont know what i did but somehow i am not able to do anything on my phone, I tried new drivers, older firmware, stock firmware, different cable, different port, charging, but the phone doesnt even light up.
I think there must be a way to access the phone's storage and install android all over again but, what i dont know is how to do that. So thats why im seeking help, but no one seems to understand or know how to do that....
I hope you understand me now and know of a solution, if not, I appreciate that you tried to help me
if your phone have removable bettey, try only format option after remove bettery and after formate complet, download only rom with bettery..
---------- Post added at 04:39 PM ---------- Previous post was at 04:31 PM ----------
dekannomad said:
I need help with my mtk6737m phone which i bricked in a really dumb way
I need help flashing it with SP Flash Tool which gives an error that says:
S_FT_ENABLE_DRAM_FAIL (0xFC0)
Here is how i bricked it.
Today i decided that i want to flash a custom recovery on my phone, so i did and it didnt work.
For some reason when i tried to boot to the custom recovery it didnt work, it went to the stock one
For some reason i got stuck in a boot animation too...
So then decided that it was a good idea to flash to complete stock rom back to my phone,
but chose the format all + download option, so that the changes the custom recovery made
were deleted. Well, so i thought...
Is there any way to fix my bricked phone? Its the only one I have :crying::crying::crying::crying:
Click to expand...
Click to collapse
Sorry bro try format device without bettery and after format download rom with better...

Categories

Resources