Hi everyone. I'm trying to fix my aunt's Toshiba Jorn.e touch Windows CE (tablet?) (umpc?) (shi*?) from Groupon. When I hold the power button, the "Toshiba Leading Innovation" screen appears, and.. the nothing happens. I've tried update firmware to reset system, but the update doesn't start. Can you help me?
Sorry for my English, but i have to fix it.
When i connect tablet to PC with a miniUSB cable, the system detects device as "SEC S3C6410X Test B/D".
noobah said:
When i connect tablet to PC with a miniUSB cable, the system detects device as "SEC S3C6410X Test B/D".
Click to expand...
Click to collapse
It looks like your Journ.e is in test mode .
It's stuck at Toshiba "Leading Innovation" ? Feels like "Dead Obsolescence" to me
Forever living in my Galaxy Ace using XDA App
noobah said:
Hi everyone. I'm trying to fix my aunt's Toshiba Jorn.e touch Windows CE (tablet?) (umpc?) (shi*?) from Groupon. When I hold the power button, the "Toshiba Leading Innovation" screen appears, and.. the nothing happens. I've tried update firmware to reset system, but the update doesn't start. Can you help me?
Sorry for my English, but i have to fix it.
Click to expand...
Click to collapse
Well, in this device there is a reset sliding button, you can find it hidden below the device, slide this to the left and then back to the right, the device now should shutdown. now press the power button for at least 3 seconds and you will have your device back to life. hope it works for you as it did for me.
Moved
mmthabet said:
Well, in this device there is a reset sliding button, you can find it hidden below the device, slide this to the left and then back to the right, the device now should shutdown. now press the power button for at least 3 seconds and you will have your device back to life. hope it works for you as it did for me.
Click to expand...
Click to collapse
When you plug the tablet into the pc via USB and you restart , the device just freezes... You cannot restart it anymore, you cannot fix it with the hard reset mini button... You have can do is wait for the battery to go off and hope the soft will start run normal.
I hope i can install any other ROM like android or something - this tablet soft is hilarious...
Maybe a little late, but for me it worked
There is a method of reflashing the Firmware of the device via SD-Card.
Just run the exe in the zip-file and direct it to copy all files to your SD.
Then insert ist into your device and slide the mini hardware switch from right to left and back. Now turn on the Device it schould now display Toshiba-splash with the little message saying "Updating..." it take some time, but then after a restart you are good to go.
Beware the Update is DELETING all yout Data on the Device even if it is not stored in the Windows part of the flash!
Just remove the " "
The File is located here:
h t t p://aps2.toshiba-tro.de
/kb0/OPT0502VS0000R01_E1100-060510.ZIP
Complete Instruction in German:
h t t p://aps2.toshiba-tro.de/kb0/OPT0502VS0000R01de.htm
Hi all,
I've a Samsung Nexus S here from a friend of me.
The phone was rooted and flashed with Cyanogenmod 10.1. Without any special action the phone doesn't power on again after a reboot (during a software update CM10.1). There's nothing. Only a black screen. No lights! Nothing...
I've tried to power on it for several times. I've tried to start it into the download mode and the fastboot mode. But only a black screen. My computers Mac, Linux, Windows are detecting nothing when I'm connecting them to the phone.
Do you've any ideas for unbrick this nexus s?
regards
Marco
MarcMarin said:
Hi all,
I've a Samsung Nexus S here from a friend of me.
The phone was rooted and flashed with Cyanogenmod 10.1. Without any special action the phone doesn't power on again after a reboot (during a software update CM10.1). There's nothing. Only a black screen. No lights! Nothing...
I've tried to power on it for several times. I've tried to start it into the download mode and the fastboot mode. But only a black screen. My computers Mac, Linux, Windows are detecting nothing when I'm connecting them to the phone.
Do you've any ideas for unbrick this nexus s?
regards
Marco
Click to expand...
Click to collapse
That's exactly what I'm working on right now.. Let's start with the basics.. Do you have a good cable (tested with other micro-usb devices?)? If so, on Linux, under terminal, does the lsusb command show any Samsung devices while connected?
Hi,
I have a similar problem.
My Nexus S suffers from the power button bug with the power button occasionally not working. When I turned it off today (using the terminal as I always do) it shut down as normal. However, when I tried to start it again it, it would not boot. When I press the power button (it usually works to start the phone, it just does not work within the recovery / OS), the backlight turns on but there is no vibration and it does not proceed to the Google logo. Similarly if I try to start it using the charger, the backlight turns on but it does not proceed from there.
Linux does not recognise the device, i.e. neither dmesg nor lsusb show any output. Therefore I cannot use the Unbrickable Resurrection tool.
Would doing that be helpful?
http://forum.xda-developers.com/nexus-s/development/i9020t-nexus-s-development-platform-aka-t1566475
I cannot enter Fastboot or Download mode. Again, only the backlight turns on.
Is it a hardware fault?
Has anyone had similar problems?
Thanks.
Yes, it will if yours is a i9020a or t. BUT you need a VERY steady hand and PROPER soldering equipment.. I had mine in Dev mode but it wasn't flashing anything, so I thought I didn't do something right, took it all back apart, and 20 mins and a popped micro resistor (from too much heat from the soldering wand) later, I had a completely dead phone.. So if you attempt it, be very careful.. If you don't feel comfortable you can do it, I would definitely find someone who can..
A co worker had her surface rt crash on updating and now its stuck at the booting surface screen.
I tried the steps I could find fiddling with the volume button and power button but it gets no where.
Honestly I have zero experience with these and normally use android.
Is there a way to connect this thing to a PC and push recovery files to it as it doesnt seem to want to see the recovery USB at all. It does know its there cause the power/reading light on the USB drive lights up.
Im trying another attempt at downloading and remaking the recovery USB just to see if I got a bad download but honestly wondering if this thing is toast. Just really trying to help them out cause it just ran out of warranty and MS wants to charge them 200$ to repair it.
Thanks
Hello there,
I would like to propose again this question, I summarize the problem of a Surface,
in my case a Surface 2 with Windows 8.1 RT stuck at the 'Surface Screen' and looping
in reboots alternating with the screen of 'preparing automatic repair', and then stuck.
If I reboot by holding down power button for 10 or 30 seconds, nothing changes and
the loop restarts by telling 'there is a problem screen', automatic reboot, 'Surface screen' and stuck.
I've tryed with 2 versions of the recovery image, an old one and one new, with two different
usb sticks. I've booted with "volume down" etc, the usb light flashes a couple of times but
the loop described above does not change.
Seems that many people out there suffer from the same problem, with almost all versions of the Surface, up to the Pro 4.
Many of them solved it with the usb recovery, but also a lot of them still have the same problem. Maybe we do something wrong
with the recovery files?
Any help is welcome, thanks for reading.
Try to keep the device on charge and leave it running for some hours, does it still stay stuck?
Hello Kephax,
I tried several times many strategies, even the one you suggested, nothing to do, always the same loop.
Hence I contacted Microsoft on 15th december, the support was very polite and efficient, in a week I was able to pack my device and give the pack to UPS. After 3 days, they returned me a new Surface2 for free.
I must say mine was only 6 months old, so warranty was still valid. On 24th december I was playing with the new device, so the whole procedure took 9 days. I am very happy.
However, I cannot say what was the fault of my Surface, a hardware problem or some updated went wrong? that's the question, I'm frightened that it was an update problem and that it can happen again to the new device. I can only guess it was a hardware problem because of the experience with the new device, less laggy, more fluid for graphics animations. Also the battery lasts longer.
I hope that this experience can help other user with same problem.
Best wishes for a happy new year,
dott_mat
Create a surface rt 8.1 bootable usb and boot from usb device.
If USB Device bootable, then first connect usb device, then press and hold vol down button, then press and release power button, when surface logo appears then release vol down button.
If all successful then surface will boot into recovery or directly boot from usb drive.
Hello,
So I have a bricked KGL MTCD unit. During the update process with Malaysk's most recent FUSE 5.1 ROM, the ignition was turned on, causing the screen to briefly go black, then back to the Android robot with the update status bar, and a second later the unit died.
I read in another thread that I started regarding this that it is possible to debrick an Android headunit using drivers and the RK Batch Tool. I downloaded everything from the Rockchip.nl site.
When the unit is hooked up to power only the button lights light up and that's it. No response whatsoever.
I tried hooking it up with a male-male USB cord to my Lenovo T410 laptop but there is no response from Windows regarding recognizing a USB device.
I have tried every USB port. I've tried both ports on the device and still nothing.
I have tried USB only and external power too. Nothing works.
I have also tried connecting a different, 100% working KGL unit. I hooked it up to power, then tried both USB ports and the computer doesn't recognize any.
Can anybody please tell me how to restore this thing?
Do I need to install the drivers into Windows first? I thought my PC would surely recognize the device and THEN ask for drivers. How do I go about installing them?
Thanks in advance
EDIT!!!!!!!!!!
DEBIRCKED THE UNIT WITH MALAYSK'S METHOD FROM THIS POST http://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
Unbricking MTCD GS
My MTCD GS RK3188 800x1024 Android 5.1.1 radio in my W220 Benz is also bricked.
It came with ROM v. 1.34 I think. So I flashed the most recent OEM ROM I could find (I think v. 1.73) through Settings/About/System Upgrade, hoping to be able to root the radio so I could use Titanium Backup.
Everything went swimmingly and all was good with the world.
Except I still couldn't root through recovery. So I tried to flash Malaysk's most recent GS pre-rooted ROM.
About half way through the process, the screen unceremoniously went black.
Now the radio is bricked. Only the button lights illuminate.
I tried several methods of rebooting into recovery, but nothing happened.
I read the HuiFei page, searched the XDA forums and the Internets generally and still could not find a solution.
I connect the radio to my computer via USB and tried to use the RKTools program, and still no luck.
I hope I missed something somewhere in my searching, so I beg of you: If anyone out there knows how to unbrick this unit, please, PLEASE share your knowledge with me.
Thanks in advance.
I just tried to update my Xtrons unit from a firmware on their site. Update finished 100% and upon reboot the screen was just black!!! There has to be a way to unbrick these. No way am i tossing out a $400 unit! I have a PF73AA4A which i believe is a RK3188 quad core 16g. Please help!
Solved! Mtcd unbricked!
@NaviPR, @shawndak and anyone else suffering the same fate:
I quite accidentally figured it out! Here's what I did (sorry, I tend to over-include information)
It started when I found a link on the Android TV Box forum about debricking RK3188 TV boxes. There was a process where the NAND was reset and then set to Mask Mode by shorting pins and pressing buttons; then the firmware was flashed with RK Batch Tool.
So I loaded RK Batch Tool and driver onto my Windows 10 computer, brought the head unit in and removed the bezel to expose the SoM.
Sadly, this SoM used a different NAND chip that did not have visible pins. So I started messing around.
At first, I couldn't get the PC to recognize the HU after trying the standard recovery process. Finally, out of frustration and without expecting any results, I tried one last thing. These are the steps:
1. Download Rockchip DriverAssistan v.4.4 and RockChip Batch Tool 1.4 zip files.
2. Extract files from each into separate directories.
3. Run Driverinstall.exe.
4. When done, run RKBatchTool.exe
5. Load your desired firmware into RK Batch Tool by pressing the dots button after the "FW Path" field.
6. Power the HU by connecting the 12V (yellow), ACC (Red) and ILL (orange) wires with 12 volts with a benchtop power supply. (Orange isn't really necessary, but it made me feel better to see the lights on.)
7. Connect the HU to the computer with a USB cable.
8. Press and release reset and wait 10 seconds.
9. Press and hold the power button for 10-15 seconds as if you were turning it off normally.
10. Release the power button and within 1 or 2 seconds press and hold it again for another 10-15 seconds until you hear your PC indicate it's loading a driver. At this point RK Batch Tool should show a connected device and the number 1 will light up blue.
11. Press the "Restore" button on RK Batch Tool. The number 1 will flash yellow while it uploads the firmware.
12. When done, repeat steps 8 and 9. The splash screen and logo screen should show up after a short while.
13. After unsuccessfully waiting a long time for it start the launcher, press reset.
14. Wait for HU to boot up and go into whatever flavor launcher you are using.
Two things to note:
1. It was helpful using a power supply with a current meter so you can actually see the current drop that indicates it's ok to release the power button and press it again.
2. When the firmwareI sideloading completed, RK Batch Tool showed a red error message "<Layer 2-6> Download Firmware Fail." Do not worry. Disregard the error message and continue with the steps.
I hope this works as well for you as it did for me.
Let me know and feel free to contact me if you're having trouble. Good luck! :laugh: :laugh:
@ibdegen
Thanks for the help, I followed your guide to the letter but unfortunately it didn't work.
Here's what I did:
- laptop runnin' Windows 7
- tried both USB ports in the unit - 3G and USB
- installed the drivers, installer said everything went fine
- I'm using a tabletop power supply which is working fine
Here's what happens:
I power UP the HU, doesn't matter if I plug in USB or 3G.
This unit is totally bricked. Only the lights in the buttons work.
I press Reset and RELEASE IT right away. When pressed the lights go off, upon depressing they turn back on.
I wait 10 seconds, I press hard on the power button, the lights go off but come back on around 10 seconds later.
I depress it, lights go off, I press hard again within a second or two, lights go on, and then nothing.
I've done this many times and nothing works.
I started frantically pressing the Power button out of frustration and I think I heard the standard "new USB device connected" sound of Windows 7 ONCE, but nothing really happened.
Wife has the car at work right now so cannot try this until later. My unit is a MTCB. Do you think your method will still work? I saw the RK3188 Android TV Mask mode as well but didn't want to risk it since the person i bought it from is willing to attempt a repair/replacement. I found the proper MCU GS file and will flash that with a 5.1.1 Fused Rom so i can use the full internal space! Will report back if all goes well. Thank you
Also noticed i cannot flash a MCU alone with the batch tool. update_5_1_1_FUSE_1024X600_RK3188_04_MAL_06_09_2016_MTCB This is the closest firmware I can find that may work for my MTCB GS unit. Will it work?
Possible Extra Steps
NaviPR said:
@ibdegen
Thanks for the help, I followed your guide to the letter but unfortunately it didn't work.
Here's what I did:
- laptop runnin' Windows 7
- tried both USB ports in the unit - 3G and USB
- installed the drivers, installer said everything went fine
- I'm using a tabletop power supply which is working fine
Here's what happens:
I power UP the HU, doesn't matter if I plug in USB or 3G.
This unit is totally bricked. Only the lights in the buttons work.
I press Reset and RELEASE IT right away. When pressed the lights go off, upon depressing they turn back on.
I wait 10 seconds, I press hard on the power button, the lights go off but come back on around 10 seconds later.
I depress it, lights go off, I press hard again within a second or two, lights go on, and then nothing.
I've done this many times and nothing works.
I started frantically pressing the Power button out of frustration and I think I heard the standard "new USB device connected" sound of Windows 7 ONCE, but nothing really happened.
Click to expand...
Click to collapse
@NaviPR
Sorry it didn't work. I'm encouraged if in fact the computer chimed.
First try the same thing, but hold the buttons longer, e.g. reset 10 secs, power 20 secs. after reset release.
Also, I did 2 other things before the hard off/on process but didn't think they were related. Maybe they are:
A. Try to get into recovery by:
1. Turning 12V on while holding the power and reset buttons.
2. After 5-10 seconds, release the reset button and keep pressing the power button for another 10-15 seconds
3. Release the power button; within 2 seconds press it again and hold another 10-15 seconds; release
4. If no boot logo shows up after a minute or so, try the hard off/on procedure.
B. Reset the NAND chip (I found nothing to confirm this is how it's done. I just assumed.)
1. Remove the front bezel to expose front of SoM board. Be careful not to damage the ribbon cables.
2. There are 2 pairs of silver test-point looking dots on each side of the NAND chip (see picture)
3. With power disconnected, short each pair individually.
4. Do A again. Then do my hard off/on procedure, holding the buttons longer.
Again, the key is to get the PC to chime and RK Batch Tool to show a connected device.
I don't know if the difference between Windows 7 and Windows 10 had anything to do with it, but you may want to consider it. Maybe try an older RK Batch Tool version with Win7. Also, try a different USB cable.
Hope this helps.
MTCB vs MTCD
shawndak said:
Wife has the car at work right now so cannot try this until later. My unit is a MTCB. Do you think your method will still work? I saw the RK3188 Android TV Mask mode as well but didn't want to risk it since the person i bought it from is willing to attempt a repair/replacement. I found the proper MCU GS file and will flash that with a 5.1.1 Fused Rom so i can use the full internal space! Will report back if all goes well. Thank you
Also noticed i cannot flash a MCU alone with the batch tool. update_5_1_1_FUSE_1024X600_RK3188_04_MAL_06_09_2016_MTCB This is the closest firmware I can find that may work for my MTCB GS unit. Will it work?
Click to expand...
Click to collapse
@shawndak-
I'm sure the MTCB HU uses a different SoM board. With any luck, it's the board that has a NAND with exposed pins like the one in the RK3188 TV Box unbrick thread. If so, try the following procedure:
-Reset NAND by shorting pins 5&6.(See picture)
-Open RKBatchTool.
-Press and hold Reset / Short pins 7&8 / Plug in USB cable at same time (requires 2 hands or contortionist LOL)
-Release Reset after device appears in RK Tool.
According to the thread I borrowed this procedure from, the HU should only be powered through the USB cable. However, if it doesn't work that way, try connecting it to a separate power supply and turn it on after plugging in USB cable.
Good luck!
PS. Sorry, I don't know if the FUSE firmware will work on the MTCB. @Malaysk has separate sections for MTCB/MTCC firmware and MTCD firmware, so you may want to confirm that you sourced the firmware from the correct section.
PPS. I want to credit the author of the TV Box thread, but I can't find it again.
UNBRICKED!!!! I hooked up the laptop with the drivers installed and batch tool open. Loaded the firmware. Then i did this exactly,
1. Turning 12V on while holding the power and reset buttons.
2. After 5-10 seconds, release the reset button and keep pressing the power button for another 10-15 seconds
3. Release the power button
Boom computer recognized the device. I pressed restore and it flashed the unit in about 5 minutes. Then it booted up!!!! Feeling invincible I loaded the 5.1.1 rom over the 4.4.4. Everything worked! I have Android 5.1.1 on a PF73AA4A MTCB GS MCU!!! So when are we getting Marshmallow? lol Nougat? The Fused rom is amazing, so much room for activites!!! Thanks everybody!
@shawndak Tried your method, doesn't work.
Try a different computer. You said a male to male cord, are you using a usb to usb B (mini) and plugging it into the front of the unit?
Make sure you have the most updated tools as well https://androidmtk.com/download-rockchip-factory-tool. You have to install the drivers!!!! They are located at the bottom of that page!
@shawndak The unit doesn't have a front USB, only back USBs.
NaviPR said:
@shawndak The unit doesn't have a front USB, only back USBs.
Click to expand...
Click to collapse
Whats the model? Can you send a link or a picture?
@shawndak It's just a KGL model for a pre-lifting W203 Mercedes-Benz without a front USB.
I've already unbricked that one + two other units using @Malaysk's other method http://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
It worked 100%, although I had to use a USB drive.
All you have to do is create a recovery card using the program from the post, get a USB drive, load some factory firmware onto it, then insert the card into the GPS slot and the pendrive to the USB. Then, if the card initializes recovery but gives you an error message, remove it - it will go into regular recovery mode - and update from the USB.
NaviPR said:
@shawndak It's just a KGL model for a pre-lifting W203 Mercedes-Benz without a front USB.
I've already unbricked that one + two other units using @Malaysk's other method http://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
It worked 100%, although I had to use a USB drive.
All you have to do is create a recovery card using the program from the post, get a USB drive, load some factory firmware onto it, then insert the card into the GPS slot and the pendrive to the USB. Then, if the card initializes recovery but gives you an error message, remove it - it will go into regular recovery mode - and update from the USB.
Click to expand...
Click to collapse
Very interesting. Perhaps slow format those cards and attempt it again. If not try a warranty claim with whomever you bought it through. Good luck!
@shawndak I don't think the card is at fault here.
Anyway, read Malaysk's guide and follow it to the letter. In case your unit gives you an error message saying that you have to remove the card, do it and you will be dumped into regular recovery mode with the USB stick still plugged in. Just load the firmware from there.
Like I said, I've unbricked 3 KGL units using this method.
@NaviPR
Did you try both of my alternative methods?
It shouldn't matter that the USB port is not on front other than having to remove the HU to access the rear ports.
Admittedly, I also have a W203 so I know it's not as easy as removing the HU from a W220.
However, it sounds like @Malaysk's method is better because you don't have to remove the HU, etc. Is that right?
Wish it popped up during my search. Would have saved me a lot of time if it worked.
Nevertheless, since @ShawndaC and I were successful with my solution(s), maybe yours bricked under different circumstances.
using malaysk technique I can fix 60% of bricked devices I get
another 40% need the hardware repair and parts.
I repair many head units daily
shawndak said:
UNBRICKED!!!! I hooked up the laptop with the drivers installed and batch tool open. Loaded the firmware. Then i did this exactly,
1. Turning 12V on while holding the power and reset buttons.
2. After 5-10 seconds, release the reset button and keep pressing the power button for another 10-15 seconds
3. Release the power button
Boom computer recognized the device. I pressed restore and it flashed the unit in about 5 minutes. Then it booted up!!!! Feeling invincible I loaded the 5.1.1 rom over the 4.4.4. Everything worked! I have Android 5.1.1 on a PF73AA4A MTCB GS MCU!!! So when are we getting Marshmallow? lol Nougat? The Fused rom is amazing, so much room for activites!!! Thanks everybody!
Click to expand...
Click to collapse
5.1 working normaly or lil bit lagY?
I've tweaked it a bit so it's running pretty dang good. I'd wait for the update that's coming out soon!