I just bricked my a696 in the process of doing the official asus update and have been trying to unbrick it using the information in this forum (particularly here and here) without any luck. I was wondering if anyone could help me with this problem. this is what I have figured out and done from my reading:
1. I have downloaded the image file for my unit - A696_dump_wm6_2_eng.rar
2. I have also downloaded USBLoader.exe
when I connect my pda, I can get it into the mode where it accepts usb input (POWER + ENTER + RESET). However when I try to run usbloader I get a bunch of errors that seem to suggest that my computer can't open a connection to the usb port.
------------------------------------
C:\usbloader nk.nb0
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
try to open \\.\wceusbsh002
try to open \\.\wceusbsh003
try to open \\.\wceusbsh004
try to open \\.\wceusbsh005
USB pipe opening error
------------------------------------
I am using vista business, and am running the command prompt in administrator mode. I have also tried doing the same procedure on a windows xp machine and it has given me the same error. When I connect my pda, windows does detect the connection and loads a usb device driver. Active Sync does not start. I feel like I am missing something very basic that I just don't know about. any help would be greatly appreciated, thanks in advance!
Same problem
OK ..I am now up to the same spot. The next step I am going to try is to try to do it from the SD card using this method. I will let you know how I get on.
Anyone else offer any suggestions?
JohnYW
Fixed
I managed to get my ASUS 696 back again, thanks to the info posted on this forum.
Using the NB0 file plus USBloader.exe finally got it to go. It seems the loader only looks at the first 5 USB ports and if you are plugged into anything higher it doesnt find it. I am using a laptop with a docking station and 2 monitors so had numerous USB ports. When I plugged it into one of the two ports on the laptop itself - Voila - it worked and I now have a working ASUS 696 - no longer a brick!
1. Download the A696_dump_wm6_2_eng.rar file plus USBLoader.exe files.
2. Unzip the rar file
3. Run command prompt and navigate to where these files are.
4. Connect USB cable to bricked unit
5. Hold power and Enter and hit reset and hold till unit goes into USBloader mode
6. From the command prompt run the USB tool with the unzip file and sit back and watch. About 2 minutes and it will reboot. Hopefully all well.
To find those files just google them - good luck
Not fixed for me
I only have 3 USB-ports on my Laptop and USBLoader works with none of them.
The PDA installs himselve as:
-Windows CE USB-device
-- ASUS USB Sync
Outside of the USB-Controller tree.
I get the exact same error as influxx described. Is there any other way to get USBLoader check all the USBs or getting the connection going?
My system is WIN-XP SP2.
Half fixed
Well, i managed to establish the usb connection by using a 10-years-old Laptop with only two USB1.1 ports.
Now i get to that point:
C:\PDA>USBLoader.exe nk.nb0
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
The file nk.nb0 was opened
Image total Size 61808640 bytes
NB0 image downloading.....
File nk.nb0 total 61808640 byte read
Size of ACK_PACKET = 20 address of buffer=7c91ee18
<PIPE00> R : request 20 bytes -- 20 bytes read
What we read AckType < 55aa > dwRet < 99 >
Size of ACK_PACKET = 20 address of buffer=55aa
The PDA shows 100% ... but thats all...
No restart, nothing (I waited 15min). If i unplug or reset the PDA i get an infinite number of lines like this:
........
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0.........
And my PDA acts like before. Is my Rom dead?
EDIT: No it wasn't. The mainboard kept analyzing the Battery as too low and so everything (flashing included) was locked.
Asus 696 bricked
Can anyone please post an .DIO and or other fix to get my Asus A696 back to work? (pref. WM6 engl)
It hangs on the ASUS bootscreen, after an unsuccesfull ROM upgrade...
I can't use usbloader.exe and nk.nb0 file since I have not a USB cable, and I am forced to use a method of recovery that use only the SD card.
CyBear said:
EDIT: No it wasn't. The mainboard kept analyzing the Battery as too low and so everything (flashing included) was locked.
Click to expand...
Click to collapse
So what did you do to fix it? I am having the exact same problem. (bricked 636N after failed update to WM6)
--EDIT--
Ok my problem was that I dumped a WM6 from another 636N and the bricked one was WM5. After restoring a dutch WM5 image (which worked) I updated to an english ROM that worked.
The one thing tipping me off to find a WM5 dump was that at around 84% when restoring, the counter jumped back to 1%, continued to 14% then jumped to 100%.
Thx for all the wonderful advice on this forum. Now I have not only a working 636N but also the knowledge to restore one if it breaks in the future (I have around 20)
CyBear said:
Well, i managed to establish the usb connection by using a 10-years-old Laptop with only two USB1.1 ports.
Now i get to that point:
C:\PDA>USBLoader.exe nk.nb0
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
The file nk.nb0 was opened
Image total Size 61808640 bytes
NB0 image downloading.....
File nk.nb0 total 61808640 byte read
Size of ACK_PACKET = 20 address of buffer=7c91ee18
<PIPE00> R : request 20 bytes -- 20 bytes read
What we read AckType < 55aa > dwRet < 99 >
Size of ACK_PACKET = 20 address of buffer=55aa
The PDA shows 100% ... but thats all...
No restart, nothing (I waited 15min). If i unplug or reset the PDA i get an infinite number of lines like this:
........
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0.........
And my PDA acts like before. Is my Rom dead?
EDIT: No it wasn't. The mainboard kept analyzing the Battery as too low and so everything (flashing included) was locked.
Click to expand...
Click to collapse
I have the exact problem, it loads to 100% then gives me these errors. How the hell do i fix this. PLEASE somebody give me some support on this, the battery has been charging for hours so i cant imagine it thinking i dont have enough battery power.
JohnYW said:
1. Download the A696_dump_wm6_2_eng.rar file plus USBLoader.exe files.
2. Unzip the rar file
3. Run command prompt and navigate to where these files are.
4. Connect USB cable to bricked unit
5. Hold power and Enter and hit reset and hold till unit goes into USBloader mode
6. From the command prompt run the USB tool with the unzip file and sit back and watch. About 2 minutes and it will reboot. Hopefully all well.
To find those files just google them - good luck
Click to expand...
Click to collapse
I have asked this in another thread as well with no response. What/where is this ENTER key??????? I know where the POWER button is and I know where the RESET button is but nothing on the unit or in the manual says ENTER.
same problemmm... which is the enter key ???? reset and power i understand... help me pls
The enter key is the one in the center of the circular directional pad. Press that button and the power button while hitting the reset. Hold these buttons until the USBloader screen comes up. Hope this helps, good luck!
Ok guys, I'm trying to look for the product code registry to change it because every time I restore the system it goes back to the original one which from an operator and I'd like to have country variant one. Anyone knows where this registry is?
And the other thing is, how could we add our operator so the roaming triangle is removed?
Thank you guys!
Hello @skyleth,
The product code is never mentioned in the registry.
If the Windows Device Recovery Tool detects normally a Lumia device connected in universal serial bus (USB) on the computer where it is installed, it will then ask you, since its user interface (UI), to select it.
Thus, are retrieved and exploited, by the software, some informations from the Lumia device. Among these, note the presence of a string value representing the product code, written in a file named product.dat, stored in a path of the device provisioning partition (DPP).
Then, the Windows Device Recovery Tool software compares this string value with those on the Microsoft Azure repository servers, to determine which package should it download. After finding this answer, it downloads, itself, a file with the extension *.vpl (variant packing list), which will be stored in a path, intended for this, of the %ProgramData% environment variable of the computer.
In the same time, the Windows Device Recovery Tool software displays, among other things, an Install software button. Once passed the three boring steps directly following the pressing this button, the package download starts. This involves several files of a few kilobytes (KB) and a *.ffu file (full flash update) of more or less than 3 gigabytes (GB), that will be stored from the same path where the *.vpl file is already previously downloaded.
Then, the Windows Device Recovery Tool software checks that the charge level of the battery of Lumia device is of 25% minimum, then sends a command to it to rebooting it immediately in the flash mode. The software checks the status of the anti-theft protection and, that it is enabled or disabled, starts the package installation.
This involves several steps, such as for example the cyclic redundancy check (CRC) of the downloaded files, the root key hash (RKH) control of Lumia device and of *.ffu file, or Platform ID control. However, list all the steps would be much too long.
The installation process completed correctly, the Windows Device Recovery Tool software sends a command to the Lumia device to rebooting it normally, thus initiating, a few seconds later, the out-of-box experience (OOBE).
If you want to change the product code writed in the device provisioning partition, you can do this easily by using the thor2 program (provided with Windows Device Recovery Tool software), by executing the thor2 -mode uefiflash -ffufile "Path\Of\FFU\File.ffu" -productcodeupdate 059x -skip_flash -reboot command.
Best regards,
Thank you, it worked! I'm going to try and see if and update pops up and fix the roaming triangle
Disclaimer: To go through with this, you will have to open up your device to get access to the back of the PCB. This is not for everyone. If you encounter issues, I (or the others here) will try to help you, but the risk is all yours.
First, credit where credit is due. To xyz` for coming up with this and taking the time to help and to k4y0z for helping me get unstuck multiple times.
What's the purpose of this thread, you ask? It's to recover from a bricked 2017 Fire HD 10 as a result of sideloading to a lower version (from anti-rollback). This thread is not about rooting or other apps. Numerous threads of that type exist on these forums. If your device can get to the "amazon" screen or the "Fire" screen, do not waste your time here. Questions unrelated to anti-rollback unbricking will be mostly ignored.
This has only been tested on Linux (Ubuntu 16.04). In general, getting familiar with Linux (as opposed to Windows) can make all the difference in projects like these.
1. Make sure your device is powered off and disconnected from your PC.
2. Take off the back cover, remove the pieces of tape from the battery and display connectors, disconnect the battery and display cables, unscrew the PCB (11 screws), and gently lift it up. Take care not to rip the speaker wires from the board. (To unbrick, you do not have to connect the battery.)
3. Download and extract the contents of unbrick_suez.zip (attached).
4. Navigate to the root of the extracted archive and open a terminal there.
5. Optional: If you see serial port errors, disable or remove modem manager as root (command may vary with distro; try one or more of these commands in Ubuntu 16.04):
Code:
sudo apt-get remove modemmanager
sudo apt-get remove --auto-remove modemmanager
sudo systemctl stop ModemManager.service
6. Run the unbricking script as root:
Code:
sudo ./bootrom.sh
You should see it waiting for the bootrom. Let it be and do the following with the PCB.
7. Connect the microUSB end of the cable to the PCB. This is the more physically-challenging end of the connection. Leave open the PC side.
8. Short the point (highlighted in blue in the attached picture) to ground. Work with what you're comfortable with, but here's my approach (use M/M jumper wire if you have access to it):
a. Gently nudge one end of the wire into the metal case of the SD slot so that it stays in place (keyword: gently). This frees up one hand. You need just enough grip to ensure it doesn't fall off unexpectedly.
b. Hold the other tip of the jumper wire to the point highlighted in blue.
c. Connect the other end of the USB cable to your Linux box (remove the jumper wire when you're instructed to and press Enter on your keyboard).
You should see the following:
Code:
[email protected]:~/Desktop/unbrick_suez$ sudo ./bootrom.sh
[2019-02-03 12:28:08.466131] Waiting for bootrom
[2019-02-03 12:35:22.602290] Found port = /dev/ttyACM0
[2019-02-03 12:35:22.602653] Handshake
[2019-02-03 12:35:22.603225] Disable watchdog
* * * Remove the short and press Enter * * *
[2019-02-03 12:35:27.691503] Init crypto engine
[2019-02-03 12:35:27.709450] Disable caches
[2019-02-03 12:35:27.709854] Disable bootrom range checks
[2019-02-03 12:35:27.721298] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes
[2019-02-03 12:35:27.724457] Send payload
[2019-02-03 12:35:28.262081] Let's rock
[2019-02-03 12:35:28.262834] Wait for the payload to come online...
[2019-02-03 12:35:31.824056] all good
[2019-02-03 12:35:31.824533] Check GPT
[2019-02-03 12:35:33.103565] gpt_parsed = {'lk': (20480, 2048), 'recovery': (174080, 34816), 'MISC': (123904, 1024), 'cache': (3515392, 868352), 'tee1': (22528, 10240), 'dkb': (18432, 2048), '': (0, 1), 'userdata': (4383744, 56687583), 'system': (208896, 3306496), 'PMT': (7168, 9216), 'tee2': (32768, 10240), 'proinfo': (1024, 6144), 'reserved': (124928, 16384), 'metadata': (43008, 80896), 'boot': (141312, 32768), 'kb': (16384, 2048)}
[2019-02-03 12:35:33.103747] Check boot0
[2019-02-03 12:35:34.291300] Check rpmb
[2019-02-03 12:35:34.499043] Downgrade rpmb
[2019-02-03 12:35:34.501403] Recheck rpmb
[2019-02-03 12:35:35.392720] rpmb downgrade ok
It should complete in a few seconds.
9. Unplug the USB cable after "rpmb downgrade ok" appears in the terminal.
10. Put your device back together (PCB and display/battery cables). Do not screw the PCB in or snap the back cover until you confirm your device has been unbricked.
11. Depress the power button (with your nail or a suitable tool) to turn on your device. (If it doesn't turn back on, hold it down for a few seconds. If you hear a ding, that's usually a good sign.) This can be challenging for the uninitiated, but don't complain. Obviously, it's better to verify unbricking now than after you put everything back together.
12. If the device turns back on, you can shut it down and put everything back together. If it does not turn back on, connect it to your PC and see what shows up with lsusb. Time to troubleshoot.
If you have questions, read the two linked threads above. If you cannot find the answer to your question(s), post here. If you append this entire OP to your post (instead of snipping most/all of it), I will, on general principle, ignore your post.
Source code: https://github.com/retyre/amonet/tree/mt8173
@retyre
Awesome effort! But best not to brick it in the first place!
If you want a new challenge, I suggest Fire HD 6/7 2014 on eBay. I need instructions for it, I have 2 very weird bricks
I get an error at wait for payload to come on line. Runtime error. Received {} instead of expected pattern. Format data runtime error received b instead of expected pattern.
DragonFire1024 said:
I get an error at wait for payload to come on line. Runtime error. Received {} instead of expected pattern. Format data runtime error received b instead of expected pattern.
Click to expand...
Click to collapse
I've started over a few times. The same result. I'll post a more detailed log when I get home. This is coming from the same tablet I tried to flash with the unlock.
Sent from my Amazon KFSUWI using XDA Labs
My Fire HD has erased part of the system file, so a boot loop has occurred. I tried adb sideload but never went back. Is it possible to reset factory by application this method?
Sorry Machine Translation.
86chan said:
My Fire HD has erased part of the system file, so a boot loop has occurred. I tried adb sideload but never went back. Is it possible to reset factory by application this method?
Sorry Machine Translation.
Click to expand...
Click to collapse
You can try. It won't cause anymore damage.
Sent from my Amazon KFSUWI using XDA Labs
This method worked and unbricked my 2017 HD 10 after a bad firmware flash. Had to run the script twice, the first time succeeded but the tablet didn't boot up. May have been completely out of battery after running itself down in a media loader bootloop all night but after a short charge the low battery icon flashed and back in business. Also helps to have a friend ready to plug/unplug the USB and hit enter when required, it's a very small spot on the board that you're shorting.
The hardest part was getting the shell off, once you unclip the sides you'll feel it's still "stuck" because there are 3 more clips about 1.5-2" from the left side of the tablet, starting 3" from the bottom. You just have to force them and the shell will pop off. Be careful they clip back in when you reassemble or they will push against the screen and cause white spots.
Thank you retyre for your efforts amongst many posts here, without this guide I'd be stuck with a paperweight. For anyone else with a hard bricked HD 10 2017 model, you've got nothing to lose giving this a go!
followed instructions from this post and from xyz prev one..and this is how it went..
1. try used USB 3 plug no success
2. try used USB 2 worked with no problems..now my Fire HD 10 is alive again..
OS used Ubuntu 18.04
all the thanks to you guys @retyre @k4y0z @xyz
First, Thank you for posting.
i have looked around the solution for bricked fire hd 10.
But, i have same problem like @DragonFire1024.
this is the log
[email protected]:~/Downloads$ sudo ./bootrom.sh
[2019-03-12 04:13:38.983635] Waiting for bootrom
[2019-03-12 04:13:48.574166] Found port = /dev/ttyACM0
[2019-03-12 04:13:48.578815] Handshake
[2019-03-12 04:13:48.586267] Disable watchdog
* * * Remove the short and press Enter * * *
[2019-03-12 04:13:53.935066] Init crypto engine
[2019-03-12 04:13:54.383858] Disable caches
[2019-03-12 04:13:54.391831] Disable bootrom range checks
[2019-03-12 04:13:54.616303] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes
[2019-03-12 04:13:54.621105] Send payload
[2019-03-12 04:14:03.086231] Let's rock
[2019-03-12 04:14:03.093481] Wait for the payload to come online...
Traceback (most recent call last):
File "main.py", line 92, in <module>
main()
File "main.py", line 57, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/skyhyung/Downloads/modules/load_payload.py", line 143, in load_payload
dev.wait_payload()
File "/home/skyhyung/Downloads/modules/common.py", line 171, in wait_payload
raise RuntimeError("received {} instead of expected pattern".format(data))
RuntimeError: received b'' instead of expected pattern
[email protected]:~/Downloads$
Click to expand...
Click to collapse
i am debugging it.
the result of self.dev.read(4) is null at module/common.py 169 line
i run the script on vmware ubuntu 16.04
---------- Post added at 10:24 PM ---------- Previous post was at 10:10 PM ----------
i solved it
i changed the TIMEOUT value to 10 from 5 at modules/common.py line 11
then, it works
@DragonFire1024
please try it like me
Thanks you.
Thanks you! I did restore my devices.
Hi everyone,
I'm trying to do as guided but get stuck at the step number 6, go this message:
[email protected]:~/Desktop/unbrick_suez$ sudo ./bootrom.sh
[sudo] password for nkp:
Traceback (most recent call last):
File "main.py", line 3, in <module>
from common import Device
File "/home/nkp/Desktop/unbrick_suez/modules/common.py", line 6, in <module>
import serial
ModuleNotFoundError: No module named 'serial'
Click to expand...
Click to collapse
I've already run commands in step number 5.
These operated on Ubuntu 18.10 on Dell E4200. Please help me solve this. Thank a lots!
nkphuongxp said:
Hi everyone,
I'm trying to do as guided but get stuck at the step number 6, go this message:
I've already run commands in step number 5.
These operated on Ubuntu 18.10 on Dell E4200. Please help me solve this. Thank a lots!
Click to expand...
Click to collapse
Install python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu something like this should work:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot dos2unix
Original credit to @k4y0z. Definitely check out the original guide this is based on.
@retyre may want to link original thread in OP or atleast add the prerequisite installs.
nujak said:
Install python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu something like this should work:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot dos2unix
Original credit to @k4y0z. Definitely check out the original guide this is based on.
@retyre may want to link original thread in OP or atleast add the prerequisite installs.
Click to expand...
Click to collapse
Hi nujak,
Thank you for your additional guide, I've followed these above steps and successfully run the script.
After that, I press power button for few seconds and hear a ding sound but nothing happen then, I do this for several times but it results the same.
Now I will try to charge it and waiting for lucky thing happen :angel:
P/S: tried to reconnect LCD cable and I can see things running on screen. Thank retyre for this topic!
nkphuongxp said:
Install python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu something like this should work:
Hi nujak,
Thank you for your additional guide, I've followed these above steps and successfully run the script.
After that, I press power button for few seconds and hear a ding sound but nothing happen then, I do this for several times but it results the same.
Now I will try to charge it and waiting for lucky thing happen :angel:
P/S: tried to reconnect LCD cable and I can see things running on screen. Thank retyre for this topic!
Click to expand...
Click to collapse
The location of that cable and with very little slack make it a real pain. If you're sure you're done with the board, a small piece of electrical tape should keep it snug.
Sent from my Amzn KFFOWI using XDA Labs
DragonFire1024 said:
The location of that cable and with very little slack make it a real pain. If you're sure you're done with the board, a small piece of electrical tape should keep it snug.
Sent from my Amzn KFFOWI using XDA Labs
Click to expand...
Click to collapse
Thanks for your enthusiasm, surely I would do that.
One more thing I had to deal with is that I need do adb sideload 5.6.0.0 (update-kindle-40.5.9.5_user_595457020.bin) firmware (from 2017) to make my HD 10 2017 be able to boot into Home screen; otherwise, I would be stuck at Fire OS logo and "Optimising system storage and applications" screen (used adb sideload 5.3.6.4 April 2019)
Doesn't this method work on virtual linux?
I tried but it didn't go on while 'waiting for bootrom' message is on.
Is there anyone tried this, please let me know. Thank you.
------------------------------------------------------------------------------------
I tried actual linux and it worked.
So don't try virtual linux with this problem. Thank you.
Tried several time with same error as below. May you please help~ thanks in advance.
I am on Ubuntu 16.04
error message:
[email protected]:~$ sudo ./bootrom.sh
[2019-05-12 22:43:59.642617] Waiting for bootrom
[2019-05-12 22:44:48.137029] Found port = /dev/ttyACM0
[2019-05-12 22:44:48.146033] Handshake
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 495, in read
raise SerialException('device reports readiness to read but returned no data (device disconnected or multiple access on port?)')
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main.py", line 92, in <module>
main()
File "main.py", line 54, in main
handshake(dev)
File "/home/yhuang168/modules/handshake.py", line 9, in handshake
dev.handshake()
File "/home/yhuang168/modules/common.py", line 100, in handshake
c = self._writeb(b'\xa0')
File "/home/yhuang168/modules/common.py", line 95, in _writeb
return self.dev.read()
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 505, in read
raise SerialException('read failed: %s' % (e,))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
yhuang168 said:
Tried several time with same error as below. May you please help~ thanks in advance.
I am on Ubuntu 16.04
error message:
[email protected]:~$ sudo ./bootrom.sh
[2019-05-12 22:43:59.642617] Waiting for bootrom
[2019-05-12 22:44:48.137029] Found port = /dev/ttyACM0
[2019-05-12 22:44:48.146033] Handshake
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 495, in read
raise SerialException('device reports readiness to read but returned no data (device disconnected or multiple access on port?)')
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main.py", line 92, in <module>
main()
File "main.py", line 54, in main
handshake(dev)
File "/home/yhuang168/modules/handshake.py", line 9, in handshake
dev.handshake()
File "/home/yhuang168/modules/common.py", line 100, in handshake
c = self._writeb(b'\xa0')
File "/home/yhuang168/modules/common.py", line 95, in _writeb
return self.dev.read()
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 505, in read
raise SerialException('read failed: %s' % (e,))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
Click to expand...
Click to collapse
Reset the terminal. Carefully disconnect the tablet from PC and open the back and disconnect the battery cable. Repeat the script with the battery unplugged. Make sure you have as close to a full charge as possible or you will have to perform a few other steps because the tablet won't stay powered on long enough for the payload to fully loaded.
DragonFire1024 said:
Reset the terminal. Carefully disconnect the tablet from PC and open the back and disconnect the battery cable. Repeat the script with the battery unplugged. Make sure you have as close to a full charge as possible or you will have to perform a few other steps because the tablet won't stay powered on long enough for the payload to fully loaded.
Click to expand...
Click to collapse
Thanks a lot for the reply. However, the battery was disconnected per prior instructions. I did close the terminal and tried again several times, same errors occurred. After the handshake, I keep getting :"device reports readiness to read but returned no data' errors...
Any advises will be much appreciated .
[email protected]:~$ sudo ./bootrom.sh
[2019-05-12 22:43:59.642617] Waiting for bootrom
[2019-05-12 22:44:48.137029] Found port = /dev/ttyACM0
[2019-05-12 22:44:48.146033] Handshake
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 495, in read
raise SerialException('device reports readiness to read but returned no data (device disconnected or multiple access on port?)')
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main.py", line 92, in <module>
main()
File "main.py", line 54, in main
handshake(dev)
File "/home/yhuang168/modules/handshake.py", line 9, in handshake
dev.handshake()
File "/home/yhuang168/modules/common.py", line 100, in handshake
c = self._writeb(b'\xa0')
File "/home/yhuang168/modules/common.py", line 95, in _writeb
return self.dev.read()
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 505, in read
raise SerialException('read failed: %s' % (e,))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
Hello
I have a shield tv 2015 with nvidia experience 8.1 (android 9) - last October 2, I upgraded to 8.0.1, installed and when it was to restart, turned off and did not turn on.
Turns on the 2 sec green light and turns it off and the disc works (it seems to be in standby).
I opened a ticket (on nvidia) but it is being useless because the procedures that give me do not work.
I found that underneath is a snap-in cover. so i turned off the hard drive it always turns on the green light but i can't get into fastboot / recovery mode.
At the moment when I connect the usb cable to the pc I have an APX device. does anyone know anything about APX?
Thanks help me please i´m a nood
Your only bet is to get help from nvidia costumer support since it's not a pro version.
Apx mode = your device is bricked.
Mine is the 500GB version I suppose is the PRO version.
I've been reading here in the forum ... in the PRO version the
All software is on the hard drive. So I was trying to create the hard drive with a 500GB disk but to no avail.
parfuar said:
Mine is the 500GB version I suppose is the PRO version.
I've been reading here in the forum ... in the PRO version the
All software is on the hard drive. So I was trying to create the hard drive with a 500GB disk but to no avail.
Click to expand...
Click to collapse
You can try what has been done in this thread https://forum.xda-developers.com/shield-tv/general/bricked-shield-tv-pro-2015-version-t3841024
Or something like this https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
Hi,
One question.
My original hard drive
Info:
[email protected]:/home/ubuntu# hdparm -i /dev/sda
Model=ST500LM000-1EJ162, FwRev=SM16, SerialNo=W763XDYH
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: Reserved: ATA/ATAPI-4,5,6,7
* signifies the current active mode
-------------------------------------------------------------------------------------------------------------------------------------
fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb22c3a15
my new hard drive
info:
[email protected]:/home/ubuntu# hdparm -i /dev/sda
Model=HGST HTS545050A7E380, FwRev=GG2OACD0, SerialNo=TE85113R0Y5TPK
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: mode=0x01 (1) WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7
* signifies the current active mode
----------------------------------------------------------------------------------------------------------------------
--->> fdisk -l
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x4ca778fd
Hard drives are the same, I should with the tutorial, be able to get the shield to work without major problems.
what is wrong?
commands used:
dd if=start.bin of=/dev/sdX bs=4M
dd if=end_976574630.bin of=/dev/sdX seek=976574630
with these files:
https://forum.xda-developers.com/sho...2&postcount=23
My shield(2015 pro) was also bricked by the update reboot loop at nvidia logo and factory reset did not help and fastboot couldn't flash anything, so used this opportunity however to put a ssd in.
Used beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Just booted it up and its gotten past nvidia logo atleast so far
First time it bricked was updating to 8.0, after recovery it was able to get the updates up to 8.0, when i did the 8.0.1 update i also got the same error as those above where turns on then off and does not even wake the display.
HellToupee_nz said:
My shield(2015 pro) was also bricked by the update reboot loop at nvidia logo and factory reset did not help and fastboot couldn't flash anything, so used this opportunity however to put a ssd in.
Used beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Just booted it up and its gotten past nvidia logo atleast so far
Click to expand...
Click to collapse
It worked?
what version of android is it?
on mine it didn't work. only worked with the first part (firstpart.bin which is like this) and with the 5kb file that speak at the end of this thread.
parfuar said:
It worked?
what version of android is it?
on mine it didn't work. only worked with the first part (firstpart.bin which is like this) and with the 5kb file that speak at the end of this thread.
Click to expand...
Click to collapse
In my case, I have the fastboot. but this is difficult because we don't have active developer mode.
Yes, i had done a factory reset also, u can get stuck at the spinning android logo forever without that i find. For the end part of the disk i used my own from my disks image, i've just done it all again and updated back to 7.2.3 stopped there and copied my widevine key off my orginal image so got L1 support and going to make backup of its current state.
parfuar You don't use "sdX" you change the "X" to the letter your drive is from fdisk -l , looks like you need to use "sda", after after you write the two bin files reboot directly into bootloader and select boot recovery kernel which will bring up t wrp recovery and you need to perform a factory reset wipe then reboot and Android should boot up and you will have Nvidia experience 3.3 and you have to do a couple updates to get up to 8.0 just make sure you turn off automatic updates cuz mine automatically updated to 8.0.1 and crashed my hard drive a second time. I used my original hard drive
also posting here that my 2015 500gb gets bricked with 8.0.1. hdd swapped out for crucial mx500. i think the guy here said it happened on his stock 500 sshd?
OK... This is how I got it to work.
Using "DD for Windows"... since I don't have a Linux PC (tested working perfectly on Windows 10 x64)
Download link:
http://www.chrysocome.net/downloads/dd-0.6beta3.zip
Unzip the "dd.exe" file and copy it to:
%USERPROFILE%\AppData\Local\Microsoft\WindowsApps
This gives you the ability to use DD system wide.
Use the beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Connect your drive. I highly suggest using a Desktop PC because it is much faster than a USB to Sata cable.
If you don't have any open Sata slots, just disconnect your CD-rom drive temporarily and use the connectors.
Now:
1) Put the "start.bin" file in the root directory of drive C (example C:\start.bin)
2) Open a command prompt as Administrator and change directory to C: (command: cd C:\ )
3) Type command dd --list to determine the correct disk you want to write to.
4) Use command dd if=start.bin of=\\?\Device\HarddiskX\Partition0 --progress
whereas X is the drive number you determined earlier with the dd --list command
(replace the X with the drive number you want to write to)
5) Watch the write progress and stop the process at about 6GB (around byte 6,500,000,000)
(you can actually see the write counter running)
There is no need to write the "end file". Shut down the PC once finished and remove the drive.
6) Install the drive back into your Shield Pro and start. The green NVIDIA logo should show up soon.
Wait for about 10 minutes and if nothing happens unplug the Shield and do a restart.
Now wait patiently.... it will eventually boot past the green logo and the Android colors.
Now let your Shield self-update to whatever version you desire. It starts with version 3.0
That's it! You just successfully de-bricked your Shield Pro
Enjoy!