Related
I want to post my findings here. It could be useful for developers playing with bootloaders, and for users who accidentally break their Droid.
DISCLAIMER: I am not responsible for any damage, caused to your phone, when you did something using information from this thread. Be extremely careful shorting any pins (and to do at YOUR OWN RISK)
There is two types of bricked device (by bricked I mean no fastboot available):
1. Device does not boot up, but responding to USB VIDID = 05c6:9008 = QHSUSB_DLOAD mode
This is qualcomm standard emergency download mode. This device become serial port (it is required drivers for Windows), and could be flashed with special protocol.
Attached is package which successfully recover Droid Ultra.
Once you see device with VIDID = 05c6:9008 = QHSUSB_DLOAD, you should run this command:
python qdload.py MPRG8960_MOTO.bin -ptf _ultra/partitions.txt
after this you should be able to use fastboot to flash desired official image back.
Tested on Windows, drivers for QHSUSB_DLOAD now included into package, serial port auto detection added, same command use. For both windows and linux you should have Python >= 2.6 installed, and PySerial installed.
2. Device not responding to USB, but start responding after battery disconnect (you need to disassemble your phone) as VIDID = 05c6:f006 = Qualcomm modem mode.
In most cases this mean that you has HARD bricked device. I still could not provide soft way to switch from this mode to QHSUSB_DLOAD mode, so currently with this situation you has only one possibility - is to find pin, which will force device to QHSUSB_DLOAD mode. For droid Ultra (and I believe Maxx) you could find this pin marked on picture attached. On my picture you could see, that I remove shield completely, but you could reach this pin by opening shield cup only. This is the shield near display connector. This pin should be grounded to force QHSUSB_DLOAD mode. Once you see device with VIDID = 05c6:9008 - STOP shorting pin to ground and follow unbrick 1 procedure.
If you not stopping SHORT ping to gound, you may have issues with uploading images in step 1 !!!
This both unbrick tested on Droid Ultra, but I assume it should work on Droid Maxx as well (I include _maxx folder with files for maxx).
Instruction to generate partitions.txt from working phone (Note you could have different name instead of mmcblk0):
1. adb shell dd if=/dev/block/mmcblk0 of=/sdcard/pt.bin bs=1024 count=10
2. adb pull /sdcard/pt.bin .
3. ./gpt_parser.py pt.bin > partitions.txt
Edit: Split package into 5 packages: 1. Image files for MAXX, 2 Image files for ULTRA, 3. Loader .bin for Motorola_8960 4. Window drivers for QHSUSB_DLOAD mode, 5. qdload.py script
qdload.py script updated to V1.2 with lot of usefull info printed.
move gpt_parser.py script to main post
VBlack said:
I want to post my findings here. It could be useful for developers playing with bootloaders, and for users who accidentally break their Droid.
DISCLAIMER: I am not responsible for any damage, caused to your phone, when you did something using information from this thread.
There is two types of bricked device (by bricked I mean no fastboot available):
1. Device does not boot up, but responding to USB VIDID = 05c6:9008 = QHSUSB_DLOAD mode
This is qualcomm standard emergency download mode. This device become serial port (it is required drivers for Windows), and could be flashed with special protocol.
Attached is package which successfully recover Droid Ultra.
Once you see device with VIDID = 05c6:9008 = QHSUSB_DLOAD, you should run this command:
python qdload.py MPRG8960.bin _ultra/partitions.txt
after this you should be able to use fastboot to flash desired official image back.
I didn't test it on Windows, but it could work, you just need to specify COM port, by additional parameter to qdload.py:
python qdload.py -tty COM10 MPRG8960.bin _ultra/partitions.txt
2. Device not responding to USB, but start responding after battery disconnect (you need to disassemble your phone) as VIDID = 05c6:f006 = Qualcomm modem mode.
In most cases this mean that you has HARD bricked device. I still could not provide soft way to switch from this mode to QHSUSB_DLOAD mode, so currently with this situation you has only one possibility - is to find pin, which will force device to QHSUSB_DLOAD mode. For droid Ultra (and I believe Maxx) you could find this pin marked on picture attached. On my picture you could see, that I remove shield completely, but you could reach this pin by opening shield cup only. This is the shield near display connector. This pin should be grounded to force QHSUSB_DLOAD mode. Once you see device with VIDID = 05c6:9008 - follow unbrick 1 procedure.
This both unbrick tested on Droid Ultra, but I assume it should work on Droid Maxx as well (I include _maxx folder with files for maxx).
Click to expand...
Click to collapse
WOW! Nice job, bud.
I would normally ask you to add a disclaimer to be extremely careful shorting any pins (and to do at YOUR OWN RISK), but anyone who needs to do this is already in a pickle, and their device useless.
Great work, impressive.
samwathegreat said:
WOW! Nice job, bud.
I would normally ask you to add a disclaimer to be extremely careful shorting any pins (and to do at YOUR OWN RISK), but anyone who needs to do this is already in a pickle, and their device useless.
Great work, impressive.
Click to expand...
Click to collapse
Done, I also add note about stop shorting this pin to ground once you get to QDL MODE, since it will cause eMMC instability, and may forbid to flash images.
Add: Package repacked with drivers for windows and updated version of qdload.py with windows serial port auto detection.
VBlack said:
I want to post my findings here. It could be useful for developers playing with bootloaders, and for users who accidentally break their Droid.
DISCLAIMER: I am not responsible for any damage, caused to your phone, when you did something using information from this thread. Be extremely careful shorting any pins (and to do at YOUR OWN RISK)
There is two types of bricked device (by bricked I mean no fastboot available):
1. Device does not boot up, but responding to USB VIDID = 05c6:9008 = QHSUSB_DLOAD mode
This is qualcomm standard emergency download mode. This device become serial port (it is required drivers for Windows), and could be flashed with special protocol.
Attached is package which successfully recover Droid Ultra.
Once you see device with VIDID = 05c6:9008 = QHSUSB_DLOAD, you should run this command:
python qdload.py MPRG8960.bin _ultra/partitions.txt
after this you should be able to use fastboot to flash desired official image back.
I didn't test it on Windows, but it could work, you just need to specify COM port, by additional parameter to qdload.py:
python qdload.py -tty COM10 MPRG8960.bin _ultra/partitions.txt
Tested on Windows, drivers for QHSUSB_DLOAD now included into package, serial port auto detection added, same command use. For both windows and linux you should have Python >= 2.6 installed, and PySerial installed.
2. Device not responding to USB, but start responding after battery disconnect (you need to disassemble your phone) as VIDID = 05c6:f006 = Qualcomm modem mode.
In most cases this mean that you has HARD bricked device. I still could not provide soft way to switch from this mode to QHSUSB_DLOAD mode, so currently with this situation you has only one possibility - is to find pin, which will force device to QHSUSB_DLOAD mode. For droid Ultra (and I believe Maxx) you could find this pin marked on picture attached. On my picture you could see, that I remove shield completely, but you could reach this pin by opening shield cup only. This is the shield near display connector. This pin should be grounded to force QHSUSB_DLOAD mode. Once you see device with VIDID = 05c6:9008 - STOP shorting pin to ground and follow unbrick 1 procedure.
If you not stopping SHORT ping to gound, you may have issues with uploading images in step 1 !!!
This both unbrick tested on Droid Ultra, but I assume it should work on Droid Maxx as well (I include _maxx folder with files for maxx).
Click to expand...
Click to collapse
This is great!! Mind if i add it here? With proper credits of course? Or quote you?
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Sure, no problem, but you need your own set of files for moto x (could be obtained from fastboot oficial image), and partitions.txt.
partitions.txt you could obtain using following instruction from working phone:
1. adb shell dd if=/dev/block/mmcblk0 of=/sdcard/pt.bin bs=1024 count=10
2. adb pull /sdcard/pt.bin .
3. ./gpt_parser.py pt.bin > partitions.txt
Edit: gpt_parser moved to main post.
VBlack said:
I want to post my findings here. It could be useful for developers playing with bootloaders, and for users who accidentally break their Droid.
DISCLAIMER: I am not responsible for any damage, caused to your phone, when you did something using information from this thread. Be extremely careful shorting any pins (and to do at YOUR OWN RISK)
There is two types of bricked device (by bricked I mean no fastboot available):
1. Device does not boot up, but responding to USB VIDID = 05c6:9008 = QHSUSB_DLOAD mode
This is qualcomm standard emergency download mode. This device become serial port (it is required drivers for Windows), and could be flashed with special protocol.
Attached is package which successfully recover Droid Ultra.
Once you see device with VIDID = 05c6:9008 = QHSUSB_DLOAD, you should run this command:
python qdload.py MPRG8960.bin _ultra/partitions.txt
after this you should be able to use fastboot to flash desired official image back.
I didn't test it on Windows, but it could work, you just need to specify COM port, by additional parameter to qdload.py:
python qdload.py -tty COM10 MPRG8960.bin _ultra/partitions.txt
Tested on Windows, drivers for QHSUSB_DLOAD now included into package, serial port auto detection added, same command use. For both windows and linux you should have Python >= 2.6 installed, and PySerial installed.
2. Device not responding to USB, but start responding after battery disconnect (you need to disassemble your phone) as VIDID = 05c6:f006 = Qualcomm modem mode.
In most cases this mean that you has HARD bricked device. I still could not provide soft way to switch from this mode to QHSUSB_DLOAD mode, so currently with this situation you has only one possibility - is to find pin, which will force device to QHSUSB_DLOAD mode. For droid Ultra (and I believe Maxx) you could find this pin marked on picture attached. On my picture you could see, that I remove shield completely, but you could reach this pin by opening shield cup only. This is the shield near display connector. This pin should be grounded to force QHSUSB_DLOAD mode. Once you see device with VIDID = 05c6:9008 - STOP shorting pin to ground and follow unbrick 1 procedure.
If you not stopping SHORT ping to gound, you may have issues with uploading images in step 1 !!!
This both unbrick tested on Droid Ultra, but I assume it should work on Droid Maxx as well (I include _maxx folder with files for maxx).
Click to expand...
Click to collapse
this should be stickied for all of android. while i realize your methods were device specific, i'm guessing there are enough similarities in your situation that it can be applied globally.
640k said:
this should be stickied for all of android. while i realize your methods were device specific, i'm guessing there are enough similarities in your situation that it can be applied globally.
Click to expand...
Click to collapse
It is Qualcomm specific. Most of current Qualcomm chips has emergency download mode. the only problem is to have proper load file MPRG8960.bin is for 8960 chips family, and looks like Motorola specific (maybe I'm wrong). So for sure not all Android device could use this, but most Qualcomm device should be fine, you just need model specific set of files, which, for example, Motorola provides with fastboot flashable images.
good points and good observations. this thread definitely shouldn't get buried in a single (aging) device. there's good info here.
I don't know if it is a problem, but I used this script to try and unbrick my phone.
When running as #1 as you state above, there is a "finished with errors" after the script. So I looked at it and saw that "MPRG8960.bin" was going to be pushed to the phone and the next line states "File not found "MPRG8960.bin." Looking at the files, the file it was looking for was named "MPRG8960_MOTO.bin," so I changed it to the file it was looking for and it worked great.
I'm a noob when it comes to the guts of programming and utilities, but it's something I spotted and figured I would let you know.
This seems really promising for my bricked xt907...
HamBone625 said:
This seems really promising for my bricked xt907...
Click to expand...
Click to collapse
Op has no fix files for the M, they have never been leaked.
HamBone625 said:
This seems really promising for my bricked xt907...
Click to expand...
Click to collapse
Since XT907 use same Qualcomm chip MSM8960 - you could try to use this utility, but first you need to obtain partitions.txt from working XT907 according to instructions.
Files needed you could take from latest firmware package (sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn, rpm.mbn, emmc_appsboot.mbn is aboot.mbn)
MOTO X
Hi. Can somebody post the partitions.txt for the moto X? please
To get the partition.txt from a working moto X it has to be root?
thanks
When I execute the script on my Droid Mini, with their proper partitions txt file and the MBN files from the ULTRA, I got this:
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com64
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960_MOTO.bin' to addr 0x2a000000...
Executing...
Found TTY port: com64
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending secureMode...
Sending openMulti ...
LOG: Open multi failed, unknown error
ERROR: 0x00000007: Open multi failed, unknown error
Sending SBL Reset...
Done, with errors!!!
Where I can get the MBN files for a Droid Mini?
Hi, you could try to find it inside one of official (fastboot) package for empty flashing like in Ultra package. It fails in very strange place - I will look at it on Monday.
Sent from my XT1080 using Tapatalk
VBlack said:
Hi, you could try to find it inside one of official (fastboot) package for empty flashing like in Ultra package. It fails in very strange place - I will look at it on Monday.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I tried the MBN files from a 4.4 fastboot from an Ultra and from the Droid Mini too, but i'm getting this errors, I don't know what's wrong or what I'm doing worng.
My phone powers up and can enter to fastboot, but it fails to boot, when i use "fastboot reboot" it reboot to QHSUSB_DLOAD... but well, something is wrong,,,
HELP
When i do the third step yo obtain partitions.txt (./gpt_parser.py pt.bin > partitions.txt)
i got a message
can't create partitions.txt: Read-only file system
any help?
C:\droid_ultra>python qdload.py MPRG8960_MOTO.bin -ptf _ultra/partitions.txt
'python' is not recognized as an internal or external command,
operable program or batch file.
BUZZAPT said:
When i do the third step yo obtain partitions.txt (./gpt_parser.py pt.bin > partitions.txt)
i got a message
can't create partitions.txt: Read-only file system
any help?
Click to expand...
Click to collapse
You should execute it on PC in writable folder.
Sent from my XT1080 using Tapatalk
Hi everyone,
I have a Nexus 6P which simply refuses to connect via USB on my Mac (i.e. it doesn't show up as a valid device under adb devices or via Android File Transfer). I believe it was working at some point but it seems to have stopped now. Might be worth noting, I did try connecting it to my car's charger a few months ago but had the worst time with it, it would charge and disconnect every few seconds (may or may not be relevant in this case as it pertains to the USB). I tried a different charger and it works fine with it though.
I have tried a lot of different things (which I'll list below) but have had no luck getting my Nexus 6P being recognized as a device when I connect it to my Mac (or any other). I do have the Developer settings enabled and I am able to switch to MTP but I never get the prompt to change USB mode. Anytime I connect my device, adb devices doesn't list it at all. I tried ADB File transfer as well and that also says "Please connect your device".
Here are some of the things I have tried so far:
1. Used different cables - no luck
2. Used a different mac - no luck
3. Tried a different Nexus 6P with my cable, it works fine (so it is not a cable issue)
4. Tried a different Nexus 6P with my mac, it works fine (so my Mac seems to be OK too)
5. Restarted in recovery mode - no luck
6. Tried removing a bunch of apps in case there was something conflicting - no luck so far
7. Chatted up Google support - They couldn't tell me much outside of the last option - Factory Reset - I have been holding off on that since I want to be able to transfer my files out first but I really want to avoid having to try that before exhausting all other options. They did offer to replace with a refurb'ed device but I had to decline that.
I did create a bug report dump using the device to see if anything interesting showed up and the only thing noticeable there is an exception related to USB. I am putting that info here in case it is useful in helping with this.
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
Any help here is really appreciated! Thanks
desimunda42 said:
Code:
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Click to expand...
Click to collapse
That seems suspicious. Was this taken while the phone was connected to your mac?
Here's my phone's dump while NOT connected to a computer
Code:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
[COLOR="red"] Last key received: blahblahblahblah (not null)
User keys: blahblahblahblah (no exception)
[/COLOR] System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Here it is when connected to computer
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
[COLOR="red"] mConnected: true
mConfigured: true
[/COLOR] mUsbDataUnlocked: false
mCurrentAccessory: null
[COLOR="red"] Kernel state: CONFIGURED
[/COLOR] Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
[COLOR="Red"] Last key received: blahblahblahblah (not null)
User keys: blahblahblahblah (no exception)
[/COLOR] System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Are you on a custom rom? Do you get an authorization prompt if you call "adb device" after doing "Revoke USB debugging authorizations" from Develop options?
adotkdotjh said:
That seems suspicious. Was this taken while the phone was connected to your mac?
Are you on a custom rom? Do you get an authorization prompt if you call "adb device" after doing "Revoke USB debugging authorizations" from Develop options?
Click to expand...
Click to collapse
I wasn't connected to my Mac at the time I pulled the report (I confirmed by repeating it just now and still get that 'FileNotFoundException" in the logs for USB device. I don't have a custom rom, I have the standard OEM from the Google Store and didn't do anything else with it.
Also, I did revoke the USB debugging auth multiple times and inspite of that I never get any prompt when I connect.
I also got the report while connected to the Mac and am still seeing the same exception:
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
desimunda42 said:
Hi everyone,
I have a Nexus 6P which simply refuses to connect via USB on my Mac (i.e. it doesn't show up as a valid device under adb devices or via Android File Transfer). I believe it was working at some point but it seems to have stopped now. Might be worth noting, I did try connecting it to my car's charger a few months ago but had the worst time with it, it would charge and disconnect every few seconds (may or may not be relevant in this case as it pertains to the USB). I tried a different charger and it works fine with it though.
I have tried a lot of different things (which I'll list below) but have had no luck getting my Nexus 6P being recognized as a device when I connect it to my Mac (or any other). I do have the Developer settings enabled and I am able to switch to MTP but I never get the prompt to change USB mode. Anytime I connect my device, adb devices doesn't list it at all. I tried ADB File transfer as well and that also says "Please connect your device".
Here are some of the things I have tried so far:
1. Used different cables - no luck
2. Used a different mac - no luck
3. Tried a different Nexus 6P with my cable, it works fine (so it is not a cable issue)
4. Tried a different Nexus 6P with my mac, it works fine (so my Mac seems to be OK too)
5. Restarted in recovery mode - no luck
6. Tried removing a bunch of apps in case there was something conflicting - no luck so far
7. Chatted up Google support - They couldn't tell me much outside of the last option - Factory Reset - I have been holding off on that since I want to be able to transfer my files out first but I really want to avoid having to try that before exhausting all other options. They did offer to replace with a refurb'ed device but I had to decline that.
I did create a bug report dump using the device to see if anything interesting showed up and the only thing noticeable there is an exception related to USB. I am putting that info here in case it is useful in helping with this.
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
Any help here is really appreciated! Thanks
Click to expand...
Click to collapse
I usually only get the key prompt for ADB authorzation when I connect my device and type "adb devices"..... If worse comes to worse, You can restore your phone to factory settings without wiping your sd card. Then you could test that option with compromising your data. Just flash each image from the archive yourself when restoring the firmware as opposed to using the flash-all scipt, or resetting the phone from settings... DO NOT flash the "userdata.img" included in the factory firmware archive or issue the command "fastboot format userdata" during the restore process and all of your files will be fine. This may be an option as long as fastboot is still functional on your device. Ive come across so many different devices in so many different conditions over the years, as long as the device could power on and the usb port was functional, fasboot has worked time and time again.
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac. Youll have to pull up your terminal and and direct it to the folder containing adb and fastboot. Its usually ina a folder called "platform-tools" Which can be found in the dictory in whch you installed the Android SDK or SDK Tools packages... Now that I think about it, you have to download adb from the SDK package I just mentioned. After doing so, youll find the platform tools folder and it should contain what you need. As long as java is correctly installed on your mac then everything should work once you issue the "adb devices" command in a terminal session thats points at the "platform-tools" folder. YOU ALSO HAVE TO HAVE JDK INSTALLED in order for it to work with your device. I just looked at what you posted and it looks like youred missing JDK"...
If you havent done any of this yet the thats the problem. If everything I just typed seems confusing then you can try this which explains everything you need to do to set up adb a whole lot better than my attempt above lol buts its going to take some time to accomplish https://seo-michael.co.uk/how-to-setup-adb-on-os-x/
or
You can also install and configure adb a whole lot easier by issuing the following commands from within your mac terminal.... (This will install Brew on your Mac, if you arent familiar with what it is, Its a software distrobution platform. Sort of like git hub and linux software repos. When in doubt, do a little reading first. It'll solve all your problems....
-Install Brew - Copy and paste this command into a mac terminal and follow the prompts that show up.
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
-Once that finishes, next use this command
brew update && brew cask install java
-Once that is complete enter this last command
brew install android-platform-tools
Those 3 commands will do 99 percent of the work. When its done just find the platform tools folder and go from there. Hope this helps.
Sass86oh said:
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac. Youll have to pull up your terminal and and direct it to the folder containing adb and fastboot. Its usually ina a folder called "platform-tools" Which can be found in the dictory in whch you installed the Android SDK or SDK Tools packages... Now that I think about it, you have to download adb from the SDK package I just mentioned. After doing so, youll find the platform tools folder and it should contain what you need. As long as java is correctly installed on your mac then everything should work once you issue the "adb devices" command in a terminal session thats points at the "platform-tools" folder. YOU ALSO HAVE TO HAVE JDK INSTALLED in order for it to work with your device. I just looked at what you posted and it looks like youred missing JDK"...
Click to expand...
Click to collapse
He says he already tried adb devices which didn't list anything. That tells me adb is configured correctly. Otherwise it should've given errors. Plus, he also said another Nexus 6P worked on the same mac.
adotkdotjh said:
He says he already tried adb devices which didn't list anything. That tells me adb is configured correctly. Otherwise it should've given errors. Plus, he also said another Nexus 6P worked on the same mac.
Click to expand...
Click to collapse
Yep
Sass86oh said:
I usually only get the key prompt for ADB authorzation when I connect my device and type "adb devices"..... If worse comes to worse, You can restore your phone to factory settings without wiping your sd card. Then you could test that option with compromising your data. Just flash each image from the archive yourself when restoring the firmware as opposed to using the flash-all scipt, or resetting the phone from settings... DO NOT flash the "userdata.img" included in the factory firmware archive or issue the command "fastboot format userdata" during the restore process and all of your files will be fine. This may be an option as long as fastboot is still functional on your device. Ive come across so many different devices in so many different conditions over the years, as long as the device could power on and the usb port was functional, fasboot has worked time and time again.
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac.
Click to expand...
Click to collapse
Thanks for the detailed steps but like adotkdotjh mentioned, I already have a working adb (and it worked fine with a different Nexus 6P on the same mac). How would 'fastboot' work if the computer does not even see my device under list of devices? I've never done any image flashing before so that would be quite an unfamiliar territory but I'd be willing to explore. Where would I get these image files and how do I issue the command to the device while it is not being recognized? Thanks
desimunda42 said:
Yep
Thanks for the detailed steps but like adotkdotjh mentioned, I already have a working adb (and it worked fine with a different Nexus 6P on the same mac). How would 'fastboot' work if the computer does not even see my device under list of devices? I've never done any image flashing before so that would be quite an unfamiliar territory but I'd be willing to explore. Where would I get these image files and how do I issue the command to the device while it is not being recognized? Thanks
Click to expand...
Click to collapse
Fastboot (also refered to as "download mode") is a tool used to essentially reprogram your device in the event that you are unable to enter into recovery mode in oreder to fix whatever issue your device is having. Android devices have 3 working modes, normal function, recovery mode, and fastboot. Number one is obvious, recovery allows you to completely reset your device without using a computer if every other measure youve tried hasn't worked. When you use this feature everything on your device is erased and your phone is completely restored to factory settings. Its convienet becuase not everyone is computer savvy and its to the point. But say you were updating (system update) your phone and accidently dropped it causing the battery to fall out and the device to shut off in the middle of the update process. What will most likely happen is the system partition will become corrupt, causing the phone to stick at the initial boot screen. Usually if that happens you can still access recovery mode and just reset but if for some reason that didnt work you would go to the manufacturers website and download the latest firmware for your device. You put the phone into fastboot mode by holding volume down and then pressing and holding the power button at the same time (while the phone is off).The process varies bydevice, If done correctly you will see on your screen a bunch of info along with Andy (the Android) chillin with his hatch open. You connect your phone to your computer and as long as your computer is set up correctly with adb and fastboot, you now have the abailty to reprogram (flash) your device using a series of commands that are issued from either the command line (windows) or terminal (linux/mac).
YOUR BOOTLOADER NEEDS TO BE UNLOCKED BEFORE CONTINUING. IF YOU DONT SEE A LITTLE LOCK AT THE BOTTOM OF YOUR DEVICE UNDER THE GOOGLE LOGO WHEN YOU FIRST TURN IT ON THEN YOU NEED TO GO TO SETTINGS, ABOUT DEVICE, FIND BUILD NUMBER AND TAP IT RAPIDLY UNTIL YOU SEE A MESSAGE POP UP SAYING YOU UNLOCKED DEVELOPER OPTIONS. GO BACK TO THE SETTINGS MENU AND SELEC DEVELOPER OPTIONS WHICH SHOULD NOW BE THERE AND INSIDE THERES AN OPTION CALLED "ALLOW OEM UNLOCKING" TURN IT ON. AND CONTINUE
Eextract the firmware archive you downloaded which will produce a folder containing 2 ".img files" files, another ".tar" archive, and some script files that you can use to make the process pretty much automated.
There are two of them, one for Windows (flash-all.bat) and one for Linux and Mac (flash-all.sh)....
Open the folder that was extracted from the firmware archive... Hold shift then right click a blank area in the folder. Select "open command prompt here" (Windows)
or
Type in terminal : cd ~/downloads/xxx where "xxx" is the name of the folder that was extracted but make sure that folder is moved to your "downloads" directory first
Then type the following commands:
IF YOU HAVENT UNLOCkED YOUR BOOTLOADER BEFORE THEN THIS IS WHERE YOU WILL NEED TO:
For Mac/Linux type: ./fastboot flashing unlock **Make sure you use the ./ or the command wont be recognized**
For Windows type: fastboot flashing unlock
Select yes on the phone when it asks if youre sure..... BAM, unlocked bootloader.
Your phone is completely free of restrections if you want to install custom firmware now. If not you can relock it after flashing the stock firmare by enterning fastboot mode again and typing
fastboot flashing lock or ./fastboot flashing lock (mac/linux).....
Now we can proceed with flashing the device...
For Windows: flash-all.bat and hit enter. The computer will do the rest.
Linux/Mac: ./flash-all.sh Make sure you use the ./ or the command wont be recognized.
If youre feeling brave you can do the entire process yourself by extracting the files in that second archive that was produced and flash each of them individually using a series of command in a specific order.
The 2nd extracted archive will give you a folder with five .img files
boot.img
cache.img
system.img
recovery.img
userdata.img ***** DO NOT FLASH THIS IMAGE. FORGET ITS EVEN THERE****
Take all five and move them to the original folder that was extracted. There are 2 other .img files that were extracted from the first archive also like I mentioned above, one that says "BOOTLOADER.xxx.xx.img" and one that says "RADIO.xxx.xxx.img"... Rename RADIO.xxx.xxx.img to | radio.img |and the other to| bootloader.img |ALL LOWER CASE keep them in that folder along with the other five. Now you should have 7 total image files in one folder. (Its smart to use the folder that your command prompt or terminal was opened in, if you decide to use a different folder then you have to direct each fastboot command to the folder where the .img file is located.
from the command line you flash each img individually with the following commands.....
(Mac/Linux need to include ./ before every fastboot command begins like this: ./fastboot or it wont work.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader (phone will reboot then go back into fastboot mode, dont worry should only take seconds)
fastboot flash radio radio.img
fastboot reboot-bootloader (reboots again)
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot format userdata (this command takes place of the "userdata.img" file I told you to forget about)
fastboot reboot
As long as you see action on the screen and a "complete" after every command then youre in business. If you get an error check your spelling. THE COMMAND LINE IS CASE SENSETIVE. You might type the correct words but if one letter is capital the command wont work. If theres an extra space between words then the command wont work so check everything. Safe rule: Everything should be in lower case letters with 1 space after every word.... THIS S*** MATTERS
Its not as hard as it seems if you arent familiar with the process, but its also not something to mess with unless youve done your homework. Read up on it, there are so many good posts and people in here so you'll be able to find everything you need without any issue.
Fastboot can also be used to install a custom recovery like TWRP which would then allow you to install custom firmware (roms) on your device as long as theres support for it. Nexus devices are built for that very reason! They tend to have a huge selection of development within the Android community. They come with Android as Google intended it to be! No extra BS.... And its wicked easy to unlock the bootloader. That is why they are, in my opinion, the best Android devices available. But someone who doesnt really care much for things like modding and installing custom firmware might see the Nexus as plain device which lacks the bells and whistles included in other devices. Which is ok! I personally love the simplicity of pure Android and the whole philosophy behind the Nexus Program. To each is own! If you need anything else send me a message!
Have not read it all on here lol install this on your Mac https://www.android.com/filetransfer/ and see if it sees you 6p make sure you plug in them change from charging to file transfer on the phone then exit out of the app and reboot that will tell you if your Mac sees your phone
Hi,
I never root or do anykind of development or advance usage of my shield 2015 pro,
but about 15days ago it just deside do not boot anymore . i don't think it got the last update, so i have no clue why it suddenly not boot anymore
The green light is there, but there is no output.
i tried to invoke the android fastboot with this nethod : http://nvidia.custhelp.com/app/answ...NNXg0SmNhUFlvNHpHMGkwM29mRlZxTVdQUVElMjElMjE=
i also tried to factory reset with :
http://nvidia.custhelp.com/app/answ...hen-you-are-unable-to-access-android-settings
but didn't succeed to see anything, there is no output at all (the TV says so, and i try other stuff the TV works)
i don't know what to do ?
is it actually bricked ? can i do somthing about it ?
Thank you in advance
Bobzer
bobzer said:
Hi,
I never root or do anykind of development or advance usage of my shield 2015 pro,
but about 15days ago it just deside do not boot anymore . i don't think it got the last update, so i have no clue why it suddenly not boot anymore
The green light is there, but there is no output.
i tried to invoke the android fastboot with this nethod : http://nvidia.custhelp.com/app/answ...NNXg0SmNhUFlvNHpHMGkwM29mRlZxTVdQUVElMjElMjE=
i also tried to factory reset with :
http://nvidia.custhelp.com/app/answ...hen-you-are-unable-to-access-android-settings
but didn't succeed to see anything, there is no output at all (the TV says so, and i try other stuff the TV works)
i don't know what to do ?
is it actually bricked ? can i do somthing about it ?
Thank you in advance
Bobzer
Click to expand...
Click to collapse
You didn't mention it so i ask, did you try with other HDMI cables? If still no go and as it is the pro which is more tricky, then better request RMA.
Have you also tried running fastboot commands blindly? I mean do the steps to boot into fastboot/bootloader mode, then if you haven't installed windows drivers try to do so, check device manager, does it recognize your device? What does it show?. If your device is recognized by your PC in fastboot mode and you succeed to install drivers then that will tell us something, otherwise is hard brick but still could be a hardware issue.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
lavero.burgos said:
You didn't mention it so i ask, did you try with other HDMI cables? If still no go and as it is the pro which is more tricky, then better request RMA.
Have you also tried running fastboot commands blindly? I mean do the steps to boot into fastboot/bootloader mode, then if you haven't installed windows drivers try to do so, check device manager, does it recognize your device? What does it show?. If your device is recognized by your PC in fastboot mode and you succeed to install drivers then that will tell us something, otherwise is hard brick but still could be a hardware issue.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Click to expand...
Click to collapse
Hi,
thanks for trying to help me,
I tried the cable with another device so the cable is fine
i tried the fastboot blindly but no success (maybe/probably/hopefully i don't do it correctly )
about windows i didn't saw it on windows at all, but that wasn't worry me at that time because i didn't know where to look, so i thought it was maybe normal
about driver no idea of what should i do. during my search i saw little bit about adb
all my search bring me to topic where people did stuff to there shield (root, try rom , etc) i didn't do anything so i don't know what information is relevant for me or not
tonight i will install driver and try again.
just to summarize :
After installing the driver:
- if i see the device in the device manager there is hope
- if not it's hard brick and so i can do nothing ?
if that true ?
thanks you
I would have a look at the SSHD to SSD migration Threads here on XDA (Shield TV), and attempt to make a backup of the SSHD. (If possible). This will of course be of MAJOR IMPORTANCE if you wish to retain any of the Widevine L1 DRM Provider Content (e.g. Amazon, and Netflix. etc.. etc...)
It seems to me that the Bootloader got wiped / corrupted (Which is actually the good news), or the SSHD has died. (Well it probably can't get worse than that.)
In the SSD Migration Thread there is a link to download an Backed up version of someone else's Shield TV. I managed to use this to recover a hard bricked Shield before. My mistake was not making a backup of the Security Sectors of that Device, and I lost all those Services.
It is however possible to rewrite that backup over a working backup to recover the correct L1 Widevine Keys though. IF YOU REMEMBER to make that Backup first. So it's probably not too late to do that. The worst case scenario? Your just gonna lose a buttload of DRM Services that you may, or may not even depend on. If your more of a Kodi Person, than this shouldn't even affect you much. But, of course it would be wiser to try and, retain those Widevine Keys if possible.
bobzer said:
Hi,
thanks for trying to help me,
I tried the cable with another device so the cable is fine
i tried the fastboot blindly but no success (maybe/probably/hopefully i don't do it correctly )
about windows i didn't saw it on windows at all, but that wasn't worry me at that time because i didn't know where to look, so i thought it was maybe normal
about driver no idea of what should i do. during my search i saw little bit about adb
all my search bring me to topic where people did stuff to there shield (root, try rom , etc) i didn't do anything so i don't know what information is relevant for me or not
tonight i will install driver and try again.
just to summarize :
After installing the driver:
- if i see the device in the device manager there is hope
- if not it's hard brick and so i can do nothing ?
if that true ?
thanks you
Click to expand...
Click to collapse
Right, if your PC recognize your shield in fastboot mode then it means is alive. When people have hard bricked their devices by corrupted bootloader some are able to boot into APX mode, which confirms their device won't be able to recover (unless Nvidia release the tools), but for others the device won't even turn on.
If your pc recognizes your shield tv in fastboot mode and you are able to install windows drivers and you get an id when typing fastboot devices in cmd, then there is a 50/50 chance of recovering, don't forget the possibility of hardware failure.
The following video can help you, just follow until i open command line and start typing fastboot commands but you just have to type "fastboot devices" command nothing else, if you get an id it means that the link with your shield tv is successful.
https://youtu.be/LQaYb4oVHVc
Report back!. Oh but still try other good hdmi cable(s), i tell you for experience, weird **** happens. I have had weird issues with hdmi port and hdmi cable (Amazon basics brand) in the past.
Ichijoe said:
I would have a look at the SSHD to SSD migration Threads here on XDA (Shield TV), and attempt to make a backup of the SSHD. (If possible). This will of course be of MAJOR IMPORTANCE if you wish to retain any of the Widevine L1 DRM Provider Content (e.g. Amazon, and Netflix. etc.. etc...)
It seems to me that the Bootloader got wiped / corrupted (Which is actually the good news), or the SSHD has died. (Well it probably can't get worse than that.)
In the SSD Migration Thread there is a link to download an Backed up version of someone else's Shield TV. I managed to use this to recover a hard bricked Shield before. My mistake was not making a backup of the Security Sectors of that Device, and I lost all those Services.
It is however possible to rewrite that backup over a working backup to recover the correct L1 Widevine Keys though. IF YOU REMEMBER to make that Backup first. So it's probably not too late to do that. The worst case scenario? Your just gonna lose a buttload of DRM Services that you may, or may not even depend on. If your more of a Kodi Person, than this shouldn't even affect you much. But, of course it would be wiser to try and, retain those Widevine Keys if possible.
Click to expand...
Click to collapse
thanks, for the idea, i'll first check with the driver.
and after i'll backup the drive at the same time i'll check if there is smart value. in case is the drive which is in a bad state
lavero.burgos said:
Right, if your PC recognize your shield in fastboot mode then it means is alive.
Click to expand...
Click to collapse
to entering the fastboot mode the only way is pressing for about 3sec after powering up or thanks to the drivers it will enter automatically ?
lavero.burgos said:
The following video can help you, just follow until i open command line and start typing fastboot commands but you just have to type "fastboot devices" command nothing else, if you get an id it means that the link with your shield tv is successful.
https://youtu.be/LQaYb4oVHVc
Click to expand...
Click to collapse
thanks i can't watch it right now but i'll as soon as possible tonight
lavero.burgos said:
Report back!. Oh but still try other good hdmi cable(s), i tell you for experience, weird **** happens. I have had weird issues with hdmi port and hdmi cable (Amazon basics brand) in the past.
Click to expand...
Click to collapse
I will thanks
bobzer said:
to entering the fastboot mode the only way is pressing for about 3sec after powering up or thanks to the drivers it will enter automatically ?
Click to expand...
Click to collapse
Better to do it manually as i show in the video, the other method from windows never worked for me and for many.
lavero.burgos said:
Better to do it manually as i show in the video, the other method from windows never worked for me and for many.
Click to expand...
Click to collapse
ok thanks
looking forward to try this
so i'm currently trying and sadly i can confirm that the green light is on, cable plug to shield but not recognize at all in the device manager
lavero.burgos said:
Better to do it manually as i show in the video, the other method from windows never worked for me and for many.
Click to expand...
Click to collapse
i did exactly as explained and the nothing happend except that the green light turn off
so when i plug the cable i remove my fing and put it back on the shield and waiting and after a few second the light goes off and stay off but windows still not recognize
Ichijoe said:
I would have a look at the SSHD to SSD migration Threads here on XDA (Shield TV), and attempt to make a backup of the SSHD. (If possible). This will of course be of MAJOR IMPORTANCE if you wish to retain any of the Widevine L1 DRM Provider Content (e.g. Amazon, and Netflix. etc.. etc...)
It seems to me that the Bootloader got wiped / corrupted (Which is actually the good news), or the SSHD has died. (Well it probably can't get worse than that.)
In the SSD Migration Thread there is a link to download an Backed up version of someone else's Shield TV. I managed to use this to recover a hard bricked Shield before. My mistake was not making a backup of the Security Sectors of that Device, and I lost all those Services.
It is however possible to rewrite that backup over a working backup to recover the correct L1 Widevine Keys though. IF YOU REMEMBER to make that Backup first. So it's probably not too late to do that. The worst case scenario? Your just gonna lose a buttload of DRM Services that you may, or may not even depend on. If your more of a Kodi Person, than this shouldn't even affect you much. But, of course it would be wiser to try and, retain those Widevine Keys if possible.
Click to expand...
Click to collapse
so i removed the sshd and try to backup it...
that's first that i wasn't able to recover anything from a drive that's appear on my computer
it's so strange because it's there the smart see it but i can't read nothing at all :
Code:
[email protected]:/mnt/raid/backup/shield# ls -l /dev/sdb
brw-rw---- 1 root disk 8, 16 juin 14 02:56 /dev/sdb
[email protected]:/mnt/raid/backup/shield# fdisk -l /dev/sdb
fdisk: impossible d'ouvrir /dev/sdb: Aucun fichier ou dossier de ce type
[email protected]:/mnt/raid/backup/shield# ddrescue -f -n /dev/sdb shield.dd mapfile
GNU ddrescue 1.19
Press Ctrl-C to interrupt
rescued: 0 B, errsize: 0 B, current rate: 0 B/s
ipos: 0 B, errors: 0, average rate: 0 B/s
opos: 0 B, run time: 1 s, successful read: 1 s ago
Finished
commande : 'smartctl' -i -H -c '/dev/sdb'
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Laptop SSHD
Device Model: ST500LM000-1EJ162
Serial Number: W764J2R0
LU WWN Device Id: 5 000c50 082dc3e28
Firmware Version: NV9D
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Wed Jun 14 03:02:44 2017 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Invalid status byte (0x00) [JMicron]
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 139) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 99) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x10b1) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
here the dmesg :
[270724.389743] usb-storage 3-2:1.0: USB Mass Storage device detected
[270724.389819] scsi6 : usb-storage 3-2:1.0
[270724.389901] usbcore: registered new interface driver usb-storage
[270727.372913] scsi 6:0:0:0: Direct-Access ST500LM0 00-1EJ162 PQ: 0 ANSI: 2 CCS
[270727.373406] sd 6:0:0:0: Attached scsi generic sg2 type 0
[270730.079345] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[270730.079514] sd 6:0:0:0: [sdb] 72057594037927936 512-byte logical blocks: (0 B/0 B)
[270730.079798] sd 6:0:0:0: [sdb] Write Protect is off
[270730.079802] sd 6:0:0:0: [sdb] Mode Sense: 28 00 00 00
[270730.080127] sd 6:0:0:0: [sdb] No Caching mode page found
[270730.080137] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[270730.080827] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[270730.081756] sdb: unknown partition table
[270730.082349] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[270730.083081] sd 6:0:0:0: [sdb] Attached SCSI disk
[270736.012772] usb 3-2: USB disconnect, device number 5
someone ? do you have any idea ? what could i do ?
Did you follow this Guide?* Essentially you make this backup in Two parts uninspiredly called "firstpart.bin" (Which is the first Six Gigabytes of the SSHD which also encompasses the unique DRM Keys for your Shield.). The lastpart.bin is more or less just the list of checksums for the GPT Partitions.
I wouldn't expect that you would, could or should be able to see anything from the Drive. As most of it is written in a RAW Partition. That is personally beyond my knowledge of how to mount it. That's why you have to make *.bin files which you can then view with a Hex Editor. If you wanted to.
*https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
Ichijoe said:
Did you follow this Guide?* Essentially you make this backup in Two parts uninspiredly called "firstpart.bin" (Which is the first Six Gigabytes of the SSHD which also encompasses the unique DRM Keys for your Shield.). The lastpart.bin is more or less just the list of checksums for the GPT Partitions.
I wouldn't expect that you would, could or should be able to see anything from the Drive. As most of it is written in a RAW Partition. That is personally beyond my knowledge of how to mount it. That's why you have to make *.bin files which you can then view with a Hex Editor. If you wanted to.
*https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
Click to expand...
Click to collapse
i did follow this topic but the problem is that dd doesn't works event fdisk don't work
Code:
[email protected]:/mnt/raid/backup/shield# fdisk -l /dev/sdb
fdisk: impossible d'ouvrir /dev/sdb: Aucun fichier ou dossier de ce type
it's fdisk telling me that it can't open my drive sdb no file or directory
i even tried ddrecue so i feel like i'm screwed
but i don't understand because i never saw this kind of problem with dd, i mean even a damage drive i always could start at least , copy a few bytes ... i don't understand what i miss ...
Did you remember to enter elevated root first?
Code:
$ sudo -s
If you don't do this, or you just throw up a sudo fdisk -l. I don't think it'll work. You have to be in an elevated root shell first.
Then you can use:
Code:
# fdisk -l
To list all the Drives currently in your System. Which will be more complicated depending on how many Drives you have.
Again this should list all the Drives currently on your System. You can easily, spot the Shields SSHD by the fact that it is exactly 499GB. Within in this context is the Drive Address. For me this has always been /dev/sda. Where as the local OS was on dev/sdb.
So when you get to this point:
Code:
dd if=/dev/sdX of=firstpart.bin count=6899870
You need to replace sdX with the correct Address of the Shield TVs SSHD. This will then hopefully create a ~3GB File called 'firstpart.bin'
Likewise
Code:
dd if=/dev/sdX bs=512 skip=976773158 of=lastpart.bin
Will create a 5kb File that hosts the Partition Map?
Again you have to replace sdX with the correct Address where the Shield TVs SSHD is hosted.
Ichijoe said:
Did you remember to enter elevated root first?
Code:
$ sudo -s
If you don't do this, or you just throw up a sudo fdisk -l. I don't think it'll work. You have to be in an elevated root shell first.
Then you can use:
Code:
# fdisk -l
To list all the Drives currently in your System. Which will be more complicated depending on how many Drives you have.
Again this should list all the Drives currently on your System. You can easily, spot the Shields SSHD by the fact that it is exactly 499GB. Within in this context is the Drive Address. For me this has always been /dev/sda. Where as the local OS was on dev/sdb.
So when you get to this point:
Code:
dd if=/dev/sdX of=firstpart.bin count=6899870
You need to replace sdX with the correct Address of the Shield TVs SSHD. This will then hopefully create a ~3GB File called 'firstpart.bin'
Likewise
Code:
dd if=/dev/sdX bs=512 skip=976773158 of=lastpart.bin
Will create a 5kb File that hosts the Partition Map?
Again you have to replace sdX with the correct Address where the Shield TVs SSHD is hosted.
Click to expand...
Click to collapse
thanks I will double check tonight but i'm pretty sure that i was root
Ichijoe said:
Did you remember to enter elevated root first?
Code:
$ sudo -s
If you don't do this, or you just throw up a sudo fdisk -l. I don't think it'll work. You have to be in an elevated root shell first.
Then you can use:
Code:
# fdisk -l
Click to expand...
Click to collapse
fdisk don't see the disk
i don't know what to do
I bought a new adapter because at first i thought it could be the adapter but no it's the drive that is like dead. so i bought a new drive but because i can't get a backup of the old one i don't know what to do
can i find somewhere a full backup that i could put in my drive ?
thx
i try to copy with dd and ddrescue, until now i got 0 bytes rescued so i guess my only luck would be to get a backup somewhere else, but even there would i be able to run netflix ?
You should contact Nvidia for replacement, hardware died, not your fault. Unfortunately if you didn't backup the relevant partitions containing your keys, then no you wont be able to watch Netflix.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Hiyas. Welcome a fresh corpse.
Shield 2015, non-pro, bricked by flashing a wrong image.
Bricked well, no adb, no screen, no button - just green led on powerup.
Nvidia says there's no official service in our swamps (lovely, huh) and I'm up to myself.
Anyone with succesful revival? Thanks guys.
Hi, i was happen to wander around the forum to find a method to root my HD 8 2017, and seems that my tablet has automatically update to the point where root is not possible (the current version was 5.6.4.0 build 636559820), therefore i tried to downgrade to 5.6.0.1,since the root method only covers the 636558520 build version, and after using adb sideload, i found out that the device has been totally bricked and can't be turned on, after a few googling. i've found the post about debricking, but requires me to short the TP28 circuit (which i don't know where it was after removing the cover), so i use amonet and it still didn't work, please help!!
--- and here is the log of the terminal:
[email protected]:~/Downloads/amonet$ sudo ./bootrom-step.sh
[2019-11-04 14:00:27.420553] Waiting for bootrom
[2019-11-04 14:00:43.250282] Found port = /dev/ttyACM0
[2019-11-04 14:00:43.287246] Handshake
* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 256, in <module>
main()
File "main.py", line 129, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/lubuntu/Downloads/amonet/modules/load_payload.py", line 123, in load_payload
dev.write32(0x10007008, 0x1971) # low-level watchdog kick
File "/home/lubuntu/Downloads/amonet/modules/common.py", line 163, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/home/lubuntu/Downloads/amonet/modules/common.py", line 90, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch
Dkhanh0412 said:
Hi, i was happen to wander around the forum to find a method to root my HD 8 2017, and seems that my tablet has automatically update to the point where root is not possible (the current version was 5.6.4.0 build 636559820), therefore i tried to downgrade to 5.6.0.1,since the root method only covers the 636558520 build version, and after using adb sideload, i found out that the device has been totally bricked and can't be turned on, after a few googling. i've found the post about debricking, but requires me to short the TP28 circuit (which i don't know where it was after removing the cover), so i use amonet and it still didn't work, please help!!
--- and here is the log of the terminal:
[email protected]:~/Downloads/amonet$ sudo ./bootrom-step.sh
[2019-11-04 14:00:27.420553] Waiting for bootrom
[2019-11-04 14:00:43.250282] Found port = /dev/ttyACM0
[2019-11-04 14:00:43.287246] Handshake
* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 256, in <module>
main()
File "main.py", line 129, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/lubuntu/Downloads/amonet/modules/load_payload.py", line 123, in load_payload
dev.write32(0x10007008, 0x1971) # low-level watchdog kick
File "/home/lubuntu/Downloads/amonet/modules/common.py", line 163, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/home/lubuntu/Downloads/amonet/modules/common.py", line 90, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch
Click to expand...
Click to collapse
Wow my PM
Please don't pm me for this things, create a thread as you done or ask in the UNBRICK thread.
So about your error..
Mean that you're in Preloader Mode instead of BootROM Mode:
Code:
RuntimeError: ERROR: Serial protocol mismatch
Be sure to have modemmanager disabled.
Try to short again, it can take a lot of tries (For me like 20+).
If still no, change the object that you're using to short.
If thse same, try other USB cable and other USB port (BETTER 2.0 instead 3.0).
If after try all the suggestions still the same error, do the process with the battery disconnected, that worked in most cases.
Cheers!
Rortiz2 said:
Wow my PM
Please don't pm me for this things, create a thread as you done or ask in the UNBRICK thread.
So about your error..
Mean that you're in Preloader Mode instead of BootROM Mode:
Code:
RuntimeError: ERROR: Serial protocol mismatch
Be sure to have modemmanager disabled.
Try to short again, it can take a lot of tries (For me like 20+).
If still no, change the object that you're using to short.
If thse same, try other USB cable and other USB port (BETTER 2.0 instead 3.0).
If after try all the suggestions still the same error, do the process with the battery disconnected, that worked in most cases.
Cheers!
Click to expand...
Click to collapse
Thanks for replying! But can you be more specific about the short process? since i don't know where is the CLK test point of the board, the original guide showed that it is near the the emmc, it would be nice if you can show me the image of where to short on the motherboard? And about the Preloader mode? So i have to use the brick-9820.sh to confirm the brick then proceed to bootrom-step.sh?
Dkhanh0412 said:
Thanks for replying! But can you be more specific about the short process? since i don't know where is the CLK test point of the board, the original guide showed that it is near the the emmc, it would be nice if you can show me the image of where to short on the motherboard? And about the Preloader mode? So i have to use the brick-9820.sh to confirm the brick then proceed to bootrom-step.sh?
Click to expand...
Click to collapse
No, you don't need to run any brick.sh since you already bricked but in the WRONG WAY, so you need to short TP28.
If you search a bit, you can find the TP28 image
https://imgur.com/9ThIUqK (The Light blue one) (thanks @<br />)
You need to short that point with something conductive as a paper clip or a little or a small cable with bare ends.
One end of the object you put in TP28 and the other in any place with metal that is on the motherboard (a screw for example).
At same moment that you're doing this the script should be executed and waiting for handshake the bootROM:
Code:
sudo ./bootrom-step.sh
After that short the point as described and connect the tablet into the computer AT SAME TIME. If all goes OK it will ask to remove the short. Remove it and press enter, the script will do the magic
If you still getting the Serial Protocol error, use my suggestions of my previous post.
That's all, a bit tricky but has solution
Cheers!
I
Rortiz2 said:
No, you don't need to run any brick.sh since you already bricked but in the WRONG WAY, so you need to short TP28.
If you search a bit, you can find the TP28 image
https://imgur.com/9ThIUqK (The Light blue one)
You need to short that point with something conductive as a paper clip or a little or a small cable with bare ends.
One end of the object you put in TP28 and the other in any place with metal that is on the motherboard (a screw for example).
At same moment that you're doing this the script should be executed and waiting for handshake the bootROM:
Code:
sudo ./bootrom-step.sh
After that short the point as described and connect the tablet into the computer AT SAME TIME. If all goes OK it will ask to remove the short. Remove it and press enter, the script will do the magic
If you still getting the Serial Protocol error, use my suggestions of my previous post.
That's all, a bit tricky but has solution
Cheers!
Click to expand...
Click to collapse
Again, thanks bro, you saved my day
Rortiz2 said:
No, you don't need to run any brick.sh since you already bricked but in the WRONG WAY, so you need to short TP28.
If you search a bit, you can find the TP28 image
https://imgur.com/9ThIUqK (The Light blue one) (thanks @<br />)
You need to short that point with something conductive as a paper clip or a little or a small cable with bare ends.
One end of the object you put in TP28 and the other in any place with metal that is on the motherboard (a screw for example).
At same moment that you're doing this the script should be executed and waiting for handshake the bootROM:
Code:
sudo ./bootrom-step.sh
After that short the point as described and connect the tablet into the computer AT SAME TIME. If all goes OK it will ask to remove the short. Remove it and press enter, the script will do the magic
If you still getting the Serial Protocol error, use my suggestions of my previous post.
That's all, a bit tricky but has solution
Cheers!
Click to expand...
Click to collapse
Seems like i've ran into some problems,i still get that same error after numerous times of shortening the circuit,
ModemManager disabled
USB 2.0 port used
A bare-ends wire used to short the circuit
But it still display the serial protocol mismatch error (
Here is the image: https://imgur.com/a/D4JTYhJ
Dkhanh0412 said:
Seems like i've ran into some problems,i still get that same error after numerous times of shortening the circuit,
ModemManager disabled
USB 2.0 port used
A bare-ends wire used to short the circuit
But it still display the serial protocol mismatch error (
Here is the image: https://imgur.com/a/D4JTYhJ
Click to expand...
Click to collapse
Disconnect the battery then.
Rortiz2 said:
No, you don't need to run any brick.sh since you already bricked but in the WRONG WAY, so you need to short TP28.
If you search a bit, you can find the TP28 image
https://imgur.com/9ThIUqK (The Light blue one) (thanks @<br />)
You need to short that point with something conductive as a paper clip or a little or a small cable with bare ends.
One end of the object you put in TP28 and the other in any place with metal that is on the motherboard (a screw for example).
At same moment that you're doing this the script should be executed and waiting for handshake the bootROM:
Code:
sudo ./bootrom-step.sh
After that short the point as described and connect the tablet into the computer AT SAME TIME. If all goes OK it will ask to remove the short. Remove it and press enter, the script will do the magic
If you still getting the Serial Protocol error, use my suggestions of my previous post.
That's all, a bit tricky but has solution
Cheers!
Click to expand...
Click to collapse
Rortiz2 said:
Disconnect the battery then.
Click to expand...
Click to collapse
Well the code did run, but after that nothing happens, i press the power button then the tablet plays a sound, but it still didn't boot up
here is the near end of the log:
[2019-11-05 16:01:19.097336] Force fastboot
[2019-11-05 16:01:19.406864] Flash preloader header
[4 / 4]
[4 / 4]
[2019-11-05 16:01:19.857129] Reboot
Dkhanh0412 said:
Seems like i've ran into some problems,i still get that same error after numerous times of shortening the circuit,
ModemManager disabled
USB 2.0 port used
A bare-ends wire used to short the circuit
But it still display the serial protocol mismatch error (
Here is the image: https://imgur.com/a/D4JTYhJ
Click to expand...
Click to collapse
Well i disconnect the battery and have successfully executed the bootrom-step.sh, and now it still remains bricked, for the first time, when i hold the power button, the tablet plays the start up sound but did not boot up, what should i do now!?
Rortiz2 said:
No, you don't need to run any brick.sh since you already bricked but in the WRONG WAY, so you need to short TP28.
If you search a bit, you can find the TP28 image
https://imgur.com/9ThIUqK (The Light blue one) (thanks @<br />)
You need to short that point with something conductive as a paper clip or a little or a small cable with bare ends.
One end of the object you put in TP28 and the other in any place with metal that is on the motherboard (a screw for example).
At same moment that you're doing this the script should be executed and waiting for handshake the bootROM:
Code:
sudo ./bootrom-step.sh
After that short the point as described and connect the tablet into the computer AT SAME TIME. If all goes OK it will ask to remove the short. Remove it and press enter, the script will do the magic
If you still getting the Serial Protocol error, use my suggestions of my previous post.
That's all, a bit tricky but has solution
Cheers!
Click to expand...
Click to collapse
Well since the method here is almost unusable, i was thinking of flashing the .bin file of my Fire using MiracleBox, maybe this could help with my problem: https://www.google.com/amp/s/ifindhub.com/flash-bin-firmware-files-mediatek-device.html/amp
Dkhanh0412 said:
Well since the method here is almost unusable, i was thinking of flashing the .bin file of my Fire using MiracleBox, maybe this could help with my problem: https://www.google.com/amp/s/ifindhub.com/flash-bin-firmware-files-mediatek-device.html/amp
Click to expand...
Click to collapse
Dude...
That box comunicates with Preloader which is patched on Amazon tablets.. If it were that easy we would have rooted this tablet many years ago.
About your problems, seems like a LCD cable problem. Unmount again the tablet and check all cables, specially the LCD one.
Cheers.
Rortiz2 said:
Dude...
That box comunicates with Preloader which is patched on Amazon tablets.. If it were that easy we would have rooted this tablet many years ago.
About your problems, seems like a LCD cable problem. Unmount again the tablet and check all cables, specially the LCD one.
Cheers.
Click to expand...
Click to collapse
Hmmm, i'll make sure to double check everything again to keep things intact, thanks a lot bro
Hi,
A few days ago, my Fire HD10(2019) refused to power on, or rather it would show some life (amazon screen IIRC), but go no further. Now it doesn't even do that.
On a PC I can see whats its doing across USB. "Bus 002 Device 083: ID 0e8d:0003 MediaTek Inc. MT6227 phone" on usb for about 45 seconds, then it disconnects for maybe 20s, and then repeats. Now I take the 0e8d:0003 device to be the amazon bootloader - so looks to me like the bootloder works, but crashes hard and restarts as soon as it tries to start android. So looks like the box is bricked.
I've tried the various buttons to go into fastboot - no success. Neither "adb devices" nor "fastboot devices" can see the device. On first booting, the machine brings up a serial interface (USB ACM device), alas I've not been able to connect to this.
So what are my options of getting into the machine? If I can't access the bootloader via the serial interface, are there UART pins on the board? If so where? If I can access the bootloader, can I switch to fastboot mode, so I can reflash the android OS? Where is the best place to look for info like this?
davidsummers said:
Hi,
A few days ago, my Fire HD10(2019) refused to power on, or rather it would show some life (amazon screen IIRC), but go no further. Now it doesn't even do that.
On a PC I can see whats its doing across USB. "Bus 002 Device 083: ID 0e8d:0003 MediaTek Inc. MT6227 phone" on usb for about 45 seconds, then it disconnects for maybe 20s, and then repeats. Now I take the 0e8d:0003 device to be the amazon bootloader - so looks to me like the bootloder works, but crashes hard and restarts as soon as it tries to start android. So looks like the box is bricked.
I've tried the various buttons to go into fastboot - no success. Neither "adb devices" nor "fastboot devices" can see the device. On first booting, the machine brings up a serial interface (USB ACM device), alas I've not been able to connect to this.
So what are my options of getting into the machine? If I can't access the bootloader via the serial interface, are there UART pins on the board? If so where? If I can access the bootloader, can I switch to fastboot mode, so I can reflash the android OS? Where is the best place to look for info like this?
Click to expand...
Click to collapse
It is actually the mediatek bootrom (your device can have mtk-su temp root access, if you downgrade). You must have one of the early release ones that have access to it. My guess there is something wrong with the preloader... While i can't pin it down, the information to reload is all in this thread...
New Fire HD10 2019 Bootless Root Method + Bootloader Unlock Brainstorming
There's a new Fire 10 coming out, with an Octacore processor, USB-C charging, and FireOS based on Pie: https://arstechnica.com/gadgets/2019/10/amazons-new-fire-hd-10-tablet-costs-149-and-charges-via-usb-c/ I most certainly don't need any more...
forum.xda-developers.com
Yes it was an early device. Alas it connected to the web, and updated itself from 7.3.1.0 before I disabled most of the amazon processes. So the original mtk-su for 7.3.1.0 never worked on my machine. Alas can't use this any more - as can't get into android any more.
I'm up to page 30 of the thread you posted, alas nothing read so far has managed to get into the machine.
And first progress - bypass_utility version 1.4.2. can connect (when run as root) and gives:
[2023-01-22 14:32:12.028038] Waiting for device
[2023-01-22 14:32:39.691833] Found port = /dev/ttyACM0
[2023-01-22 14:32:40.083041] Device hw code: 0x788
[2023-01-22 14:32:40.083391] Device hw sub code: 0x8a00
[2023-01-22 14:32:40.083586] Device hw version: 0xca00
[2023-01-22 14:32:40.083770] Device sw version: 0x0
[2023-01-22 14:32:40.083959] Device secure boot: True
[2023-01-22 14:32:40.084143] Device serial link authorization: False
[2023-01-22 14:32:40.087904] Device download agent authorization: True
[2023-01-22 14:32:40.088223] Disabling watchdog timer
[2023-01-22 14:32:40.092031] Disabling protection
[Errno 5] Input/Output Error
[2023-01-22 14:32:41.464834] Payload did not reply
davidsummers said:
And first progress - bypass_utility version 1.4.2. can connect (when run as root) and gives:
[2023-01-22 14:32:12.028038] Waiting for device
[2023-01-22 14:32:39.691833] Found port = /dev/ttyACM0
[2023-01-22 14:32:40.083041] Device hw code: 0x788
[2023-01-22 14:32:40.083391] Device hw sub code: 0x8a00
[2023-01-22 14:32:40.083586] Device hw version: 0xca00
[2023-01-22 14:32:40.083770] Device sw version: 0x0
[2023-01-22 14:32:40.083959] Device secure boot: True
[2023-01-22 14:32:40.084143] Device serial link authorization: False
[2023-01-22 14:32:40.087904] Device download agent authorization: True
[2023-01-22 14:32:40.088223] Disabling watchdog timer
[2023-01-22 14:32:40.092031] Disabling protection
[Errno 5] Input/Output Error
[2023-01-22 14:32:41.464834] Payload did not reply
Click to expand...
Click to collapse
It has been a long time. Maybe try disconnecting the battery, not sure if it is staying in bootrom mode.... I remember mine had to have the battery removed or it would try to goto the preloader (i think). I used the process to downgrade back to 7.3.1.0, but it was like a year ago.
Michajin said:
It has been a long time. Maybe try disconnecting the battery, not sure if it is staying in bootrom mode.... I remember mine had to have the battery removed or it would try to goto the preloader (i think). I used the process to downgrade back to 7.3.1.0, but it was like a year ago.
Click to expand...
Click to collapse
Yes - mine stayed in 0e8d:0003 mode, when the device bricked itself - made no difference with battery on or off, always when through the same minute cycle, where the device would disconnect, then reboot.
Interesting after running the bypass utility - it has stayed up in the 0e8d:0003 mode - and hasn't rebooted.
davidsummers said:
Yes - mine stayed in 0e8d:0003 mode, when the device bricked itself - made no difference with battery on or off, always when through the same minute cycle, where the device would disconnect, then reboot.
Interesting after running the bypass utility - it has stayed up in the 0e8d:0003 mode - and hasn't rebooted.
Click to expand...
Click to collapse
it disabled the watchdog timer. From what is can see everything points to a potential wrong setup..
bypass_utility/README.md at master · MTK-bypass/bypass_utility
Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.
github.com
This post shows the same error as you read through it.
Payload did not reply · Issue #13 · MTK-bypass/exploits_collection
[Errno 5] Input/Output Error Payload did not reply
github.com
OK - using SP_Flash_Tool v5.2008 to attempt to flash maverick-downgrade-7.0_PR7310_940N and I get the error:
Connect BROM failed: STATUS_SEC_AUTH_FILE_NEEDED(-1073545198)
Disconnect!
BROM Exception! ( ERROR : STATUS_SEC_AUTH_FILE_NEEDED (-1073545198) , MSP ERROE CODE : 0x00.
[HINT]:
Please select a valid authentication file or ask for help.)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,105))
So where do I get the authentication file from?
Michajin said:
it disabled the watchdog timer. From what is can see everything points to a potential wrong setup..
bypass_utility/README.md at master · MTK-bypass/bypass_utility
Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
ah yes - that explains why it was rebooting. So guess I have to dig into [Errno 5] Input/Output Error.
Seems like only way I have into the tablet any more is the mediatek bootrom, but as the tablet is sick - if that doesn't work, then probably its permanently dead. E.g. even getting access to a uart wouldn't help.
You have to only do file by file.
5. bypass_utility run succes with message "Protection disabled"
6. Run SPFlash Tool and flash boot, recovery, vendor, system. Wait to finish
7. Hold power button 15s to power off (check Ports in Device Manager windows)
8. Hold volume up and power boot to recovery with triactangle icon
9. Hold power and tap volume up then choose reset factory
10. Reboot
Thanks Michajin - I'm obviously having problems with the bypass_utility, whilst it connects to the MediaTek bootrom, it is not able to disable protection - and test mode bombs out. I've taken this up on the bypass_utility thread:
xda bypass utility