unbrick bricked ICOO D70GT - Hardware Hacking General

if your ICOO D70GT is bricked there is a tool for you:
RKBatchTool v1.7 (the cpu is a rockchip 3188 . . .)
connect your windows pc with usb cable and verify with usbview / windows messages that it is
recognized as rockusb device (you will not see it mentioned in browser!)
RKbatchTool will show the D70GT as connected
choose the img and let the program do its work
Your bricked D70GT will start as usual
the latest img for D70GT can be found on:
soft.aoicoo.com/soft/UploadFile/xtgj/
(as per august 2014)
I think that RKBatchTool is a very usefull tool for many other 3188 based tablets.

Related

Pipo W4 Windows Tablet - Drivers

All, does anyone have the Pipo W4? It's a lovely little Windows 8 tablet.
Unfortunately in removing the recovery partition my tab decided to stop booting.
The manufacturer's recovery image (and my own) doesn't seem to work.
I was wondering if anyone has this tablet, and if they can, if they can download a couple of drivers I'm unable to find anywhere else?
Thanks.
V
Hi, I have that tablet.
What exactly do you need?
http://softd.ir/2014/12/pipo-w4-drivers/
Success install win8.1 to PIPO W4
All about PIPO W4 tablet with windows 8.1
After 2 days I success install new windows 8.1 PRO
1. Bios have (V8L_WIN32_JS_PIPO_2014_10_17_20140927_DX.BIN) search in web
2. Windows load to USB via RUFUS (MBR)
3. Format emmc in BIOS
4. With usb OTG cable and HUB connect keyboard, mouse and USB with windows
5. Automatically start boot from USB (in my tab can´t select boot from anywhere)
6. Install windows
7. In device manager, manually update UNKNOWN device
8. Drivers for this tab is 100% functional from techtablets.com/pipo-w8/downloads
Its all, for any questions send email to me...
[email protected]
Good Luck!!!

MK808 Not Recognised By RockChip Batch Tool - Tried Serveral Guides

MK808 not recognised by RockChip Batch Tool - tried serveral guides already
Hello,
I can't flash my MK808 because the RockChip Batch Tool doesn't recognize the device. I tried several guides with no success. I'm on Win7/64
At 1st I followed a guide which I think led me to install the google adb driver. It showed up with "adb devices" but not in the RockChip tool.
I think I was misled here and need the rockchip drivers, don't I?
I downloaded the drivers with Version 3.5 and I also tried the ones which were included in the RockChip Batch Tool (v1.5, v1.6 and v1.8). Windows didn't accept them and kept using the adb or MTP drivers. Now I noticed that in the device manager the MK808 shows as "USB\VID_2207&PID_0001". But in the inf file of the drivers all PIDs were 2xxx or 3xxx. Now just like with the adb driver I added two lines with the ID I got from the device manager. Now the driver is accepted. But I still have no success with the RockChip tool.
I also found a thread which mentions to modify the config.ini of the batch tool but this didn't helped either.
(SUPPORTLOWUSB=TRUE
FULLSPEEDUSB=TRUE)
As I understood I should switch USB debugging off on the device. Than I should go to Settings - USB and click "Connect to PC". Is this right?
Any idea what I might do wrong?
BTW what is the latest firmware for MK808?
thx n rgds
tmg
got it.
Problem was that device was in MTP mode. had to switch it to "mass storage mode". There's another "settings" icon which opens not the standard settinge and there on the "system" tab (?) I could change it. The guid in the web suggest that it could be done in the standard settings, but this didn't worked for my MK808.
usb debugging needs to be off.
At 1st the device is red in the tool. I need to click "switch" to get it green. Wasn't obvious.
1st start seems to take a while ... just came up nice.

Bricked Lumia 950XL and Windows Device Recovery Tool EOL

I've bricked 950XL and in the device manger i can see the qualcomm serial device
Now i wanted to download the Windows Device Recovery Tool
-------
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>ResourceNotFound</Code>
<Message>The specified resource does not exist. RequestId:b63fac0c-501e-0003-2f80-4c2de5000000 Time:2021-05-19T07:30:29.8362829Z</Message>
</Error>
-------
I have no idea how i can recover my phone
mathewm said:
I've bricked 950XL and in the device manger i can see the qualcomm serial device
Now i wanted to download the Windows Device Recovery Tool
-------
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>ResourceNotFound</Code>
<Message>The specified resource does not exist. RequestId:b63fac0c-501e-0003-2f80-4c2de5000000 Time:2021-05-19T07:30:29.8362829Z</Message>
</Error>
-------
I have no idea how i can recover my phone
Click to expand...
Click to collapse
bad news microsoft has finally retired the Windows Device Recovery Tool and the last only method to recover a lumia device
according to this thread in Microsoft forum (In Spanish) and is for the end of support of W10M in 2020
From what I understand there is not an installer that does not use the internet as well as the drivers to be able to recover the device
I quote verbatim what he meant
"I can tell you that the Windows Device Recovery Tool is no longer available for download, nor is it functional on computers that are still installed, due to the end of the life cycle of Windows Phone 8.1 in June 2019 and the end Windows 10 mobile support cycle in June 2020"
Sorry for those bad news but I had an lumia 640xl and in order to test windows rt or windows ARM I need the WDRT for drivers and to downgrade my device to WP8.1
MauriJ2001 said:
bad news microsoft has finally retired the Windows Device Recovery Tool and the last only method to recover a lumia device
according to this thread in Microsoft forum (In Spanish) and is for the end of support of W10M in 2020
From what I understand there is not an installer that does not use the internet as well as the drivers to be able to recover the device
I quote verbatim what he meant
"I can tell you that the Windows Device Recovery Tool is no longer available for download, nor is it functional on computers that are still installed, due to the end of the life cycle of Windows Phone 8.1 in June 2019 and the end Windows 10 mobile support cycle in June 2020"
Sorry for those bad news but I had an lumia 640xl and in order to test windows rt or windows ARM I need the WDRT for drivers and to downgrade my device to WP8.1
Click to expand...
Click to collapse
good news.
I could download the file from Microsoft and install it.
The download only worked with my Android Smart Phone (don't know why)
The installation worked too!
Test with the phone i can do in 2 hours
I tried to recover the phone
Possible with instructions
Bricked 950XL
Hi, It seem my 950 is dead brick, when I plug it vibrate, then nothing. No light on sceen, no logo. At least windows seem to recognize an unknow device. To get it back, I tried to follow the tutorial on lumiafirmware website. thor2 -mode...
forum.xda-developers.com
but after the WDRT said... Waiting for reconnection the phone ist no shown anymore in the device manager.
I think now it is completely dead
mathewm said:
I tried to recover the phone
Possible with instructions
Bricked 950XL
Hi, It seem my 950 is dead brick, when I plug it vibrate, then nothing. No light on sceen, no logo. At least windows seem to recognize an unknow device. To get it back, I tried to follow the tutorial on lumiafirmware website. thor2 -mode...
forum.xda-developers.com
but after the WDRT said... Waiting for reconnection the phone ist no shown anymore in the device manager.
I think now it is completely dead
Click to expand...
Click to collapse
I think (I'm newbie in Windows mobile development) the phone has a sudden death at this point you can only recover the phone using programming tools or JTAG
Check again if you can enter to download or serial mode and reflash using the Thor2 method or with windows phone internals if not the phone needs to be recovered with JTAG method
This my opinion and can or can't be asserted (based I'm my experience with android phones I didn't see a hard brick on lumia devices)
Did you succeed or do you need further help?
Best regards, Joachim

CarplayBox - Isudar CP36 (QCM6125 / 4GB / 64 GB) - bricked (QUSB_BULK)

Hi,
I decided to create separate threed for this.
My device is Isudar CP36 (QCM6125 / 4GB / 64 GB).
After firmware update - my device start loading gui and after few seconds freeze and restart.
After restart it displays as QUSB_BULK and nothing happens.
It looks like bricked.
I can switch it to EDL mode:
in device manager it is: Qualcomm HS-USB QDLoader 9008
I try to use MT to make factory restet.
I see it on device list in MT.
When I click start button (for any option: read partitions or factory restet) it shows:
Connection to Phone, Wait...
Done.
CPUID: Xx001750E1
>> CPU: 0x001750e1
and nothing happens
I suppose I should help to have proper mbn file for my device.
Could somebody help me with this, or it is different method to fix my device?

Need Help with getting my PC to recognize MXQ S905W

Hey all, I am trying to flash this box using the USB burning tool (Amlogic) and it is not connecting to my PC for the life of me. I hit the AV button and connect it. the blue light pops on but nothing at all that my PC detects. I tried 2 different cables and made sure they have data on them as well. I plugged it in on a monitor while trying to connect it the monitor says android recovery on it so the box is doing something. my pc is a windows 11 64 bit. I have tried differnt versions of the usb burning tool as well. I think I hit a wall here and need some help. This is what I am trying to do BTW https://docs.google.com/document/d/1PusB45JXq6WyolvezFZgAtQLZN_fPcvJ2FvAbAGihh0/edit any help would be super cool !
To help your PC recognize the MXQ S905W device, you may need to install the appropriate drivers and ensure the correct settings are in place. Here are some steps you can follow:
Connect the MXQ S905W device to your PC using a USB cable.
On your PC, open the Device Manager. You can do this by pressing the Windows key + X and selecting "Device Manager" from the menu.
Look for any unrecognized or unknown devices in the Device Manager. The MXQ S905W device might be listed under "Other devices" or "Universal Serial Bus controllers" with a yellow exclamation mark or a question mark next to it.
Right-click on the unrecognized device and select "Update driver" or "Update driver software."
Choose the option to search for drivers automatically. Windows will attempt to find and install the necessary drivers for the MXQ S905W device. Follow the on-screen instructions to complete the process.
If Windows cannot find the appropriate drivers automatically, you may need to manually install them. Visit the manufacturer's website for the MXQ S905W device and look for driver downloads specific to your operating system. Download and install the provided drivers.
After installing the drivers, disconnect the MXQ S905W device from your PC and reconnect it again.
Check the Device Manager again to see if the MXQ S905W device is now recognized without any issues. It should appear under the appropriate category without any warning signs.
If the above steps don't resolve the issue, there may be compatibility or driver availability limitations for the MXQ S905W device on your specific PC. In such cases, it's recommended to consult the device's documentation, contact the manufacturer's support for assistance, or explore user forums and communities dedicated to the MXQ S905W device for further troubleshooting and solutions.

Categories

Resources