i.t.works TM1008 tablet Bricked: How can I solve this? - General Questions and Answers

Hello everybody,
I hope I don't post this question where I should not post it, if so, I do apologies.
Some times ago, my father-in-law gave me one tablet he didn't use anymore, an i.t.works TM1008 as said on the box and on the back of the tablet.
It was sold by the French shop Darty, youcan have a preview of the specs over here. It's nothing fancy, a chinese tablet with a rebranding from what I could understand. After some search on the net, I found out it also exist with the Kesa name - Kesa TM1008.
After getting the tablet, I've erase everything on it as you normaly do when you want to have a fresh tablet from factory, using the android tools already onbard: long story short, I use the settings of the device as far as I remember, I did not flash it or anything crazy. It didn't worked, I had the setup menu, but I couldn't do much. The only thing I have is the quad core boot image, then the android logo, then nothing at all.
Lately I tried to go a bit further with firmware update, etc. and it worked so well I've bricked the device *facepalm*. I was a bit stupid to say the least, because I tried to put the TM1007 firmware on it. And from what I can see herew, the processor is not the same. It's a MT8127 Quad Cortex A7 but the TM1008 has a MTK MT8163 Quad Core.
So from my understanding of the situation, that what messed everything up. And after browsing for a long long time, I did not find any firmware for the i.t.works or the kesa TM1008. And with the "I.T.Works" name, it makes my researches much harder.
Anyway, still from my understanding, if I find a ROM for the MTK MT8163 Quad Core, I would believe it would work. So first question: Am I right to think such insanity? Or is the tablet fully bricked and dead?
The state actual of the tablet is:
I have no indication if it's charging or not when I put it on charge.
When I plug it to my laptop, it is not recognise. I have a Windows 10 installation, and when I plug it, there is nothing: no sound notification that something has been plugged, nothing in the device manager tool. Nevertheless, if I plug it and keep the power and return buttons, I can sometimes hear a notification that something has been plugged, but that's it.
I can't see it with SP Flash Tools
I can switch the tablet at all: no recovery menu, no android logo, nothing.
I've find the scatter of the MTK MT8163 processor, I wanted to try if it would do something, but there is no way for me to see if it could work. So for my second question: Would a scatter file of something like 10ko would restore a firmware, or substitue a ROM? (I would assume no, but I don't know much about tablets)
How can I restore it when there is nothing on internet regarding that firmware, or brand? I could go to a Darty shop, but I'm living in UK, and the warranty of the tablet is way overdue, so...
Thank you for your help!
EDIT: I tried to follow that guide, but as I don't have the ROM, I don't really think I can go that far.

Related

[Q] I Really Screwed Up This Time....Major Screw Up

Well, I'm sure you've probably guessed by the tone of the title, I bricked my 3G Xoom MZ600. Don't really wanna get too much in depth on how I did so.​ But I will say this: I rooted my Xoom a few weeks back, and everything was cool. For some reason, tonight, I decided I wanted to revert back to stock. This way I could do all OTA updates, and get myself off of Honeycomb, and back to ICS, and then see what I wanted to do from then on. Well, my dumbass, DID NOT have my battery fully charged, and I had this wild ass idea that if I had my charging cable plugged in, everything would be ok as far as being able to flash all necessary *.img files to revert back to Stock. So I flash the first *.img file which was the boot.img This went completely fine, which led me to believe that continuing on would be fine as well....Not the case. I proceeded to flash the system.img file, and that's where things took a turn for the worse. For some reason the system.img file would not flash to my Xoom through ADB (kept saying FAILED). So what do I do? I panic. I try several ADB Commands thinking that the Xoom had come Unmounted from my PC. After trying different commands, and reading a few things, I was somehow able to get the Xoom to respond, but not in a good way. I apparently hit a button combo that reset my Xoom, and then all it would do is stay stuck on the Motorola M Dual Core Boot Screen. So then I panic again. I then press Volume Up + Power and then Volume Down + Power to get back into Fastboot protocol. I then try to flash the *.img files again, thinking surely it had been enough time on the charger, so I should be able to flash all files now. Not the case. I honestly can't remember what happened exactly next, but my Xoom started saying RSD MODE 3. At this point I stopped panicking and started completely tripping (I've heard of the elusive RSD MODE, Never actually saw it though, until now). I do some research (Google is my Best Friend), but hey, I'm a dumbass, and I start trying to boot into recovery and what not (didn't happen by the way). Got the Xoom to reboot again, back into fastboot protocol again, thinking to myself, I'll try flashing the files one more time. It's GOT to work this time. So I flash the boot.img, success! I try to flash the system.img, FAILED! So now I'm thinking, well maybe I don't necessarily need to flash the System.img file, and instead I just continue on flashing the other *.img files (recovery.img, and userdata.img). By the way, not sure if I made this clear, I'm a F**KING dumbass!) Well, I then get the files flashed, minus the system.img, I then for some reason, think it is acceptable to go ahead and Lock the F**KING BOOTLOADER(before having successfully flashed the system.img file. Yea, I know what you're ALL thinking (What the HELL is WRONG with YOU!?!?!?!) So, guess what happens next? Can you guess? My Xoom stays stuck on the Moto Dual Core Boot Logo Screen, I reset once more using Volume Up + Power, then try to go into Recovery, only to be told (In Red Letters):
Failed to boot LNX 0x0004
Starting RSD mode 2
OneWire: Charger is connected...
Battery Charge Level: 60%
Danny Xoom by DannyShane, on Flickr
So now I'm not really sure what the hell to do. I keep giggling a little bit to myself, but that could just be the liquor I'm now consuming because I am completely devastated that I could actually be so F**KING STUPID to go and do this to myself. I am at a total loss for words to be spoken out loud, for I feel as though a person as dumb as I should not be allowed to talk for a significant amount of time.​
ANY, and I MEAN ANY, HELP would be GREATLY APPRECIATED. I have been looking at random stuff about RSD Mode and so on, on Google since this has happened, which was about 25 minutes ago now (currently 2:08am Sunday April 14th 2013). All I have seen so far, are some posts, and other random things about Soldering a USB cable (which I have no idea how to do BTW) And a person with as little brain power as myself, definitely does not need to be screwing around with a Handheld Metal Melting Device, to "FIX" his electronics. Someone please Help! PLEASE HELP PLEASE HELP. I am going to go drown my sorrows in a bottle of rum. We'll see what tomorrow has in store for DannyShane and his beloved Stingray Xoom, See you tomorrow XDA.
For the love of all that is holy.....Please HELP!:crying::laugh::silly:
there ya go
1:Type "Fastboot oem unlock" and Enter: It will say "Waiting for device"
3: Immediately press'n hold "Vol- and power", when the Dual core logo appears. You will need to hold them down for 10-20 sec
2:Reset the Xoom (Power and Vol+)
4: After 10-20 sec you will see that the fastboot command gets through and you can unlock the xoom with fastboot oem unlock (MZ604 US)
As I know the only way to get out of this is with a "Factory Cable" or something, I never ran to RSD 2 to tell you what it is. I found this cable on ebay, not sure but looks it can work for you http://www.ebay.com/itm/150CM-5-ft-...014771?pt=PDA_Accessories&hash=item3a7b234f33
@Extremetempz, first let me say THANK YOU for such a quick response. I did have a question though, about the order of which you put the instructions:
1:Type "Fastboot oem unlock" and Enter: It will say "Waiting for device"
3: Immediately press'n hold "Vol- and power", when the Dual core logo appears. You will need to hold them down for 10-20 sec
2:Reset the Xoom (Power and Vol+)
4: After 10-20 sec you will see that the fastboot command gets through and you can unlock the xoom with fastboot oem unlock (MZ604 US)
The question I have is, am I supposed to do step 3 before step 2? Or was the step that is labeled as step 3 actually supposed to be labeled step 2? I just want to make sure I have it correct. Thanks again.
@XxLordsxX, hello again! Let me also say THANK YOU for such a quick response as well. I too have been looking at the Pre-Made Brick Fix Cables, because I honestly think I would end up screwing something else up by trying to make one myself. Not really sure that it is possible to do any more screwing up to my Beloved Xoom, but I'm sure I could find a way, ha.
Anyway once again thank you for the Shared Link, if I can't my Xoom to do anything based upon what Extremetempz explained how to do, then I will definitely bee looking at purchasing the Pre-Made Brick Fix Cable. I just hope it doesn't come down to that. Wish me luck.
DannyShane said:
@Extremetempz, first let me say THANK YOU for such a quick response. I did have a question though, about the order of which you put the instructions:
1:Type "Fastboot oem unlock" and Enter: It will say "Waiting for device"
3: Immediately press'n hold "Vol- and power", when the Dual core logo appears. You will need to hold them down for 10-20 sec
2:Reset the Xoom (Power and Vol+)
4: After 10-20 sec you will see that the fastboot command gets through and you can unlock the xoom with fastboot oem unlock (MZ604 US)
The question I have is, am I supposed to do step 3 before step 2? Or was the step that is labeled as step 3 actually supposed to be labeled step 2? I just want to make sure I have it correct. Thanks again.
Click to expand...
Click to collapse
yeah do the 3rd before second I've had this problem before
If you come to have the RSD Mode 3 problem again, you can check the FAQ (which points to my solution to solve it) or the link on my signature . RSD Mode 3 is quite a common things to happen, and to not cause further problems remember to download another system.img, because it's clear that yours is corrupted!
Thanks goes to both
First, I wanna say Thanks to both of y'all
Now, to update y'all: Unfortunately XxLordxX the cable that you spoke of was not really an option for me, simply because, A.) I can't wait for the whole shipping time and such. B.) I don't have the $$$ to buy one if that was an option for me either. C.) I know that there has to be an easier/alternative way to go about fixing a completely Bricked Xoom. So as much as I do thank you for the input, these were not really feasible options for me seeing as how I use my Xoom on a constant daily basis, and I needed it back up and running immediately
And Extremetempz, I want to thank you for your input as well, because even though I couldn't get your method to actually do anything for me, it did get me to rethink my situation, take a deep breath, sit down, and start going back through everything I have learned, and everything I have taught myself about my Xoom, ADB, Fastboot, Android, and Patience. I would have to say that patience was the big factor in all of this. After trying your method with no success, unfortunately , I tried a few other things, button combos and what not. Unfortunately at this point the Xoom was completely unresponsive when it came to having it connected to my PC through USB. I kept getting a blank list of attached devices in ADB/Fastboot. I know it would seem that this would have to be a case of Drivers not being installed on my PC, but this was not the case. So after moving the folder that ADB/Fastboot was installed to around I was finally able to get my Xoom to register through Command Prompt(ADB/Fastboot). I wasn't ever able to get it to give me anything other than blank list of devices. So I took a shot in the dark, and decided to try and flash the *.img files......And so it worked!!!! Success! And I didn't even have to download any new *.img files. Because despite what XxLordxX recommended (about me needing to re-download the *.img files) they were actually all working files, and Ta-Da!!! I now have my Xoom back to Stock, and fully OTA'd and back on ICS (@ the moment ). We'll see how long it takes me to get something else going on it.
Once again, I wanna thank the both of you for helping me as much as y'all tried to. I will be keeping XDA posted on any new news that may happen in my Android Journey.
Thank you, and goodbye.

Star 9500 soft bricked problem

Greetings all,
This is probably in the wrong section, so apologies for that.
I had a working Star 9500 china clone phone mtk 6589 1.2 with a gig of ram and with a 1280 x 720 5'' display it was a totally usable jelly bean phone.
However I rooted it and put CMW recovery on it, and I was using an old sd card that had previously been used in a tablet which also had a clockwork mod folder and I have inadvertently recovered that tablet image to my phone, no big deal, but I can not get to recovery with any button pushing sequence. (probably as the tablets recovery wiped over my CWM).
The phones boots to a silly android man which normally the eyes light up and he takes off, but then the phones displays a red screen bar down the middle of the display and then powers off and back to the red display, I have the scatter file and flash exe but the phone will not hold at any boot level to get a win 7 driver to recognize it, so I guess a lesson learned, new phone - always format your sd card. Will probably see if any smashed screen units appear on eBay and swop out the mobo. This was really if any one had a miracle cure and would a usb jig work on this to hold some kind of bootloader state. Great site been reading since buying a magic in 2008.

[Completed] Help with Hannspree 1281 unresponsive

If it ain't broke...see if it'll go faster. That's what I tried, BUT ended up
If it ain't broke...fix it 'til it is!
Android 4.2.2
It's rooted with Vroot, has SuperSU and Titanium Backup Pro, shows rooted.
Had ADB working, tablet taking commands.
I first tried to put in CWM recovery for the HSG1279, supposed to be the same tablet, just bigger screen. I don't even know now whether THAT'S true or not.
Started in recovery mode, but was just stock, so I tried arctools to put in a generic Rockchip CWM 6.0.3.1. That's when things started going sideways. The install hung (imagine that!). The arctools had a forced restart of some kind, so I used that. When I got back to my home screen (whew!), I used Titanium backup to see what recovery mode looked like. The tablet went dark, and would not power on. I did the paper clip trick, which got it started, but did NOT wipe anything out, so not a hard reset. Any time after that when I tried to restart in recovery mode, the hard shutdown with the clip was required. Yesterday afternoon, I went off to work for about 3 hours, leaving the tablet on, but in standby. When I came back, the tablet was dark and no amount of paper clipping would help. It would not recognize a charge. Not being one to duck a fight, I opened the case and unsoldered the black (-) wire at the PC board. The battery measured some voltage, but I didn't notice how much, about 1/4 on the 25v. scale. I soldered it back on, put it back together without any further incident. It sill does just what it was doing...nothing. I have noticed that when it's plugged into my PC's USB port, and I reset with the clip, Unknown Device shows up in my PC's Devices And Printers list. When I unplug the cable, I get the stock Windows "be-boop" USB removal sound. When I plug it back in, I get a short "boo-boo-boop" sound. That's where it is now. Anyone have any ideas on getting it going again? For me, no more trying files that aren't made specifically for this oddball tablet. This has been a fairly expensive lesson in that.
Thanks for any help.
~Bob~
Hi,
Honestly, I think you've made a mess for yourself. Lol
And flashing things made for anything but your specific device is a bad idea. Almost always it will lead to big trouble.
And the hardware tinkering is high risk too.
Anyway, we are entitled to do what we please with our devices, so not judging. Just advice.
There is nothing useful on XDA for your device that I can find, so you would need to ask for help... But you may have passed that point already....
>Android Development and Hacking>Android Q&A, Help & Troubleshooting.
Good luck!
Any use posting this to the General Discussion?
..

[Q] Motorola RAZR HD XT925 Doesn't Start (Blinking Green LED)

Hello. I have problems with my device, a Motorola Razr xt925 HD. It doesn't start, it just keeps the green led blinking when connected to wall charger, and when I plug the USB, makes a sound of a new device detected but only for a few seconds then it makes a sound of an unplugged device, and so on. It doesn't respond to any combination of buttons. I let it charging overnight, even though the battery was nearly full before this happened. Don't know if this is relevant but before this happened, I was going to flash stock Retail Brazil firmware by fastboot and got a flash failure. I turned it off and then it wouldn't turn on again. I never had this happened, I had problems but I always solved them all. Not this time hopefully you guys can help me or tell me what it could be, because I doubt it was the battery. I leave you a video showing my case.
i dont know for certain but the only time i see that green light is when battery is ou and i put it to chrge. Could your phone be in apfastboot and can t charge. It is a bit of a tough situation to troubleshoot.
Did you try keys combo to put it in fastboot, and test it by flashing
or maybe use rsd lite see if it shows you device connected? maybe then you can flash stock
i am sure there are other possibilities, let s hear from you
There's no way to enter in Fastboot by key combos and RSD lite doesn't show my device :/ maybe I need a factory cable, just in case that the battery is empty. I need more suggestions please
me paso lo mismo
did you find any solution?
im having this problem after i start using KK 4.4.2 seems like the phone go to sleeping mood by it self while my screen is locked so i have to keep clicking at power and volume up and down to restart the device now im looking for an update or a fix for this problem, another problem is the device WIFI do not catch my house signal while im away 10 feet from the house the software have bugs
I've been using CM 11 (KK 4.4.4) with no issues. This is a flash problem or maybe the battery. My phone is still dead btw I see that two more people are having the same problem here... we need a solution please.
chuYxP said:
I've been using CM 11 (KK 4.4.4) with no issues. This is a flash problem or maybe the battery. My phone is still dead btw I see that two more people are having the same problem here... we need a solution please.
Click to expand...
Click to collapse
i think your your device is dead.
this exact thing happened to me.
it happened on september, i was forced to get a new device.
i love this phone but it was dead.
i hope a fix comes through i would like to have it back
I ll take one of your hand, I need parts if interested
Any update with this? Did you try with a factory cable?
I'm going through the same thing , I read the other day that and the driver installed and nothing more .
keep trying to revive my device.
I'm going through the same thing. When I plug it into my pc , under device manager it shows "Human Interface Device" then it unmounts itself then remounts itself then unmounts. Over and over..... I've even replaced the battery.
I was running stock rom with just root, phone was working great. phone rebooted, screen never came back on but when i connect it to my computer it sees it in adb..........
Any advice would be great.
Thank you
kilroy1stcav said:
I was running stock rom with just root, phone was working great. phone rebooted, screen never came back on but when i connect it to my computer it sees it in adb..........
Any advice would be great.
Thank you
Click to expand...
Click to collapse
This thread for the droid Ultra might interest you: http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
There is some discussion of the Razr HD in this thread. It looks like someone with an unlocked device would need to dd their bootloader partition for this method to work.
A few years later .... Any solution? rsrsrs
any update on this scenario?
i have this situation too and the time could give us an answer, i am searching again, i took my device to some 'phone repair stores' and in less than 5 minutes they told me that the phone was dead, but i have my last doubts
Just to add an update here
I ended up with the Green light only and blank screen after trying to fix a battery issue, despite getting a number of batteries my phone wasn't accepting the batteries.
I remembered a battery issue a long while back, so went to reflash my phone to see if it resolved it.
I ended up with the green light and blank screen and no matter what buttons, it would just make a noise then keep rebooting.
I ended up using the Unbrick bat file.
RSD Lite was briefly showing a Medfield device of something starting with Med, but since the phone kept rebooting I couldn't reflash it again.
I did the Pwr and Vol down and as soon as I saw the device, I clicked the UnBrick bat and it managed to get my Moto logo up.
I then booted to Fastboot mode and reflashed and my phone is back,
See this link for the UnBrick, but when you do it, you have to be fast to catch it while the device is seen, otherwise the phone reboots after 4s or soo.
Softely Unbrick XT890 Razr i - Really Unbrick the Zombie
Well do not think that this thread is one among others. It's my experience when i messed up with my Razri. I wish I had this before, so I'm sharing it with you ! Every has his experience and a way to do it, so this is mine First I searched...
forum.xda-developers.com

Stuck in "nothing" (not bootloop) cannot enter into recovery or fastboot

Dear all,
On my redmi 6, I was on android 8.1 (10.3.6.0 cereus precisely) and I prepared myself to try android 9
I had exactly this recovery recovery-TWRP-3.3.0-0423-REDMI6-CN-wzsx150.img and I did the necessary (backup everything) to be ready for the worse
Don't ask me why but I +/- remembered that recovery was tricky with android pie and I stupdly decided to flash the latest recovery I found on TWRP: twrp-3.5.1_9-0-cereus.img
Just after the flash I said reboot to recovery but: I'm in a "bootloop" not the one people have when booting in android, it's before!
Whatever the power or vol+ / vol- combination, long press power etc. , the screen is black it vibrates every 5 sec and I cannot enter neither recovery (i can understand...) NOR fastboot!
First time it happened to me to be stuck at this level. I do not know what to do, I tried desperate physical manipulations and crawl the internet meanwhile, but I do not see any trick, only solution is for an android bootloop, but not "early phone boot" (the 1 second before recovery or fastboot)
Can someone save me?
Hi, you've got your phone hard bricked, which means, that it coould be fixed, but it takes a lot of time to find a solution or you'll spend days trying to fix it, but its just gonna be a waste of time.
You can try methods that other people did, and maybe you'll get lucky, and unbrick your phone.
Other fix, is that you're gonna take your phone to an authoried Xiaomi store and hope for the best.
There are 10s of threads on hard bricks on Redmi 6 (for example: removing your battery for a couple of minues and putting it back, using SP flash (but you must have an authorized Xiaomi account, ...)).
If none of my solutions worked, I suggest buying a new phone. Redmi 6 is old and unstable after all (it didnt get MIUI 12 because of "performace issues"), so I guess thats the best you can do.
Im not really an expert for this kinda stuff.
I hope this will help you, but Im not saying that I could solve the brick.
Hi Sucharek,
I put the phone to the back of a drawer one week ago, because the vibrations every 30s where annoying. This afternoon I just "found" it again, likely out of power (no screen no vibration), and I charged it. Hopefully, it rebooted, not too far, as expected, but at least in fastboot mode and I was able to flash the TWRP and everything was fine!
With much more time and tools, I could have maybe follow one of your advice like removing battery, but I saw your replay 'too" late.
Strange and funny thing, I couln'd pass the pattern at the system lock screen. I can't forget it: it's the same I use on many phones. As this remdi was rooted, it was a piece of cake to remove the lock
So, in this story, I learnt that the fastboot is not a kind of secure sanctuary where you can go that easily...
edwin_r said:
Hi Sucharek,
I put the phone to the back of a drawer one week ago, because the vibrations every 30s where annoying. This afternoon I just "found" it again, likely out of power (no screen no vibration), and I charged it. Hopefully, it rebooted, not too far, as expected, but at least in fastboot mode and I was able to flash the TWRP and everything was fine!
With much more time and tools, I could have maybe follow one of your advice like removing battery, but I saw your replay 'too" late.
Strange and funny thing, I couln'd pass the pattern at the system lock screen. I can't forget it: it's the same I use on many phones. As this remdi was rooted, it was a piece of cake to remove the lock
So, in this story, I learnt that the fastboot is not a kind of secure sanctuary where you can go that easily...
Click to expand...
Click to collapse
Hi Edwin, Im glad to hear that your phone is back and running
For any of you other people that have this problem, I would recommend removing and replugging the battery, but remmember, there are more solutions you can find on XDA, that could fix the hard brick.
Also, for those of you that are willing to wait days, weeks, or even months and dont have the tools to open your phone and removing and replugging the battery, I would recommend checking out other solutions or just buying a new phone. Like I said before, Redmi 6 is old and unstable and theres a high change that you might get a hard brick, so if you want to install a custom ROM or a custom recovery, think twice before you do it and always have a backup phone.
I wish you all the best in solving your hard brick

Categories

Resources