Related
Hi,
Sorry, for my poor English. I'm from Turkey. I bought a Reeder W7iC windows Tablet in Turkey. It's the same EMDOOR EM-I8170. I installed the wrong bios file, while android trying to install. Now, tablet won't turn on. Back light is on. I connected keyboard and mouse on usb otg. It all works. l I found the original bios file. How do i run again it? How do i install android? Thank you in advance for your help.
Tablet specifications:
Intel Baytrail-CR Z3735G, Quad Core
1GB DDR3 FLASH 16GB
Windows 8.1
16:9, 7" 1024*600 IPS
Does it have hdmi? Then connect it to a monitor or tv. What happens if you keep pressing both Vol- and Vol+ and then power on the tablet?
Please send a link to the correct bios, then I can try to make a bios flash package for a usb pen drive.
Yes it has hdmi. I connected to tv. I keep pressed Vol+ and vol- and power on the tablet. dnx mode on the tv. Then, what will i do?
I can't write outside link because i'm new users. [*] is [.]
Correct bios file link:
www*reedertablet*com/reeder/yazilim/reeder_w7ic/bios/ReederW7iC_BIOS_UPDATE_V1.6.8.zip
I want to install android.
EM-I8170 Android Files is here. There is bios file, too. I think for android.
yiyun*baidu*com/wap/link?shareid=772798033&uk=3053780477&third=0&dir=%2Fintel%2F7%E5%AF%B8android-I8170&page=1&
How can i install android to tablet? Thanks for reply.
Ok sounds good. So first thing to do is to flash the original bios/firmware. I will prepare a package in the next half hour. You need a usb hub, a usb stick, a keyboard. Power off the tablet now and try to enter bios menu (press del or escape or f12) and post which bios version is installed. Best is to post a photo. PS: I don't own this tablet and will only help you to recover it with the original bios.
I'm at work right now. I can try them when you get home in the evening. I'll write the results.
Assuming you could enter bios and you have a USB hub, usb stick and keyboard, then you can flash the original bios as follows:
============
Flash new bios
============
1. Connect the USB hub to Reeder tablet and plug in the keyboard and the USB thumb drive containing the new bios files. Power on the device and press DEL or Escape to enter into BIOS.
2. Navigate to "[email protected]", and then choose "Launch EFI shell from filesystem device"
3. After entering shell, type FS?: and then press ENTER
( ? stand for a numeric character. It depends where your USB drive resides, for example, if your USB drive is at FS4, you type FS4: You can always try between FS0 and FS4 )
4. Then type dir and then press ENTER to check if you selected the correct drive
5. Type fpt32.efi -f ReederW7iCBIOS_V1.6.8.bin and press ENTER
6. Type fpt64.efi -f ReederW7iCBIOS_V1.6.8.bin and press ENTER
(PS: you may get an error after either running fpt32.efi or fpt64.efi, but make sure at least one of the flash commands succeeded !)
7. Type exit and press ENTER
8. When you return to BIOS, choose "save changes and reset"
Good luck!
Note1: there is a readme.txt which describes how to install dual-boot Android/Win8.1 on a Voyo A1 Mini (also a EMDOOR tablet). This may be helpful for you to install Android on your tablet.
Note2: if you can't enter BIOS then we must try to flash your tablet using DNX protocol
I tried what you wrote. It installed bios from fpt64.efi. Installation completed. I selected Save Changes and Reset in Bios Menu. Frozen in bios menu. I closed the tablet keep power button. It won't turn on. Now, backlight is off. I think it hard brick. Is there anyone who can help me?
I connected to the tv with hdmi cable. Nothing happened.
Are you sure that bios was the original version? Check if battery is charged and also if you can still enter dnx mode.
İt was original bios file v1.6.8. Battery is full. I can't enter Dnx Mode. I connected it to pc. My pc don't see it m3 or m6 chip also. I think it isn't hard brick. It is Deep Brick.
Try also power on with only Vol+ pressed, alternatively with Vol- pressed. It could be it will then switch to 32-bit mode. Otherwise try disconnecting the battery from the mainboard and reconnect after a minute. If that doesn't help you must buy a flash programmer. There are various at Alibaba for about 30$ with cable connectors for on-board programming.
I tried vol+ or vol- and power button, vol+ and vol- and power button. Nothing happened. I cannot try disconnecting the battery. Because i haven't soldering iron. I think i'll send service it.
hi I have a tablet identical to the Reed W7İC.j'ai reinstalled the system and I managed to install all the drivers but my touch is shifted. that is to say, when I press for example the top of the screen is down there he reponse.dans the system at the touch function is written, limited touch support with 10 points of contact. help me if you plait.il is Emdoor EM-I8170. thank you in advance
devinci1 said:
hi I have a tablet identical to the Reed W7İC.j'ai reinstalled the system and I managed to install all the drivers but my touch is shifted. that is to say, when I press for example the top of the screen is down there he reponse.dans the system at the touch function is written, limited touch support with 10 points of contact. help me if you plait.il is Emdoor EM-I8170. thank you in advance
Click to expand...
Click to collapse
My emdoor tablet i82h not are showing display. Does i reprogrammer the BIOS and also not showing the display. came at with windows 10.
Hello, my name is Marc-Yvan from Douala, Cameroon and I will tell you the whole story about how I successfully unbrick my Android Tablet. My aim is to share with you some tips about how to recover from a desperate situation of having an unusable tablet.
How I hard-bricked my Tablet:
First of all, let me tell you how I hard-bricked my beloved tablet after trying to unlock it from its original network lock. I got this tablet from a relative who live in USA but it was unfortunately network locked to the AT&T network. So I tried to unlock it by multiple means (by myself). I found a cracked software called “Octopus for Samsung” who was said able to unlock any kind of Samsung phones/tablet. When I tried to unlock my Tablet, the software starts the work and then told me that the device will turn off and turn on after a short time. But the Tablet did not turn on anymore and I spend 02 months trying to bring it back from the grave.
Definition:
Let me explain to you what is called a hard-bricked smartphone/tablet. It’s simply a smartphone/tablet which is unusable, doesn’t turn on (desperate black screen) and doesn’t react to any stimulation. But you have to know that these hard-bricked devices are displayed as unrecognized devices when plugged onto a computer. So a hard-bricked device is not a physically damaged device but is a sort of hardly logically damaged device which cannot boot at all and is not recognized by common flash tools such as Odin, etc.
How I unbricked my tablet:
Lucky Context (GOD’s help):
Fortunately, GOD helps me by guiding me through this situation in order to recover from it in a miraculous manner. I will explain it to you in a couple of points:
1- My Tablet was rooted before the incident. I did it by using an application found in play store: “Kingroot.apk”.
2- My Tablet was equipped with some tools like “Es explorer” and “Terminal Emulator”. You will understand how it fortunately helped me before the incident.
3- The real hand of GOD: In my quest of finding a mean to network unlock my tablet, I tried a method which was asking to save some partitions of the eMMC (A kind of processor memory. Sorry but I’m not an expert ). So I saved it to the memory of my Tablet and then transfered it to a folder in my computer (By using command lines with “Terminal Emulator”). This actually helped me after to revive my tablet.
Advice N° 1 (Prevention)
Before trying to explore the whole abilities of your Tablet by flashing it or trying to network unlock it; Do a backup of the primary boot partition of your eMMC by executing this command in the “Terminal Emulator” of your rooted device:
cat /dev/block/mmcblk0> sdcard/mmcblk0.img
Be careful, this command could save the life of your beloved Tablet. This command will actually copy the primary boot partition of your eMMC in a disk image which has the same name. So you have to keep that disk image in a safe place such as your computer or an external removable disk.
Advice N° 2 (Resolution)
The Story:
In my desperate actions trying to revive my hard-bricked tablet, I read tremendous forum posts and tried countless methods. Which lead me to install a new OS in my computer. It was actually Linux Ubuntu 16.4. I found a method which told me to try to write some kind of partitions images down to an SDCard to boot my Tablet with. But the partitions images proposed by the method didn’t succeed in recovering my Tablet. So some days later, when I turn on my computer, I fortunately found a file opened; it was the primary boot partition image file of my tablet that I saved before the incident (The real hand of GOD). So I decided (Inspired by the Holy Spirit) to try the previous method with the original boot partition image file of my tablet.
The Tip:
You will need an SDCard with a correct format (FAT32) and size (16Gb or 32Gb). You will also need to work in a Linux command line terminal. To write the boot partition image in your SDCard you will have to execute this command line:
sudo dd if=mmcblk0.img of=/dev/sdb bs=1024k status=progress
Note: The sd card may not be sdb though. In order to confirm, before writing, browse to /Dev and look at the properties of sdb to ensure it is in fact there (it might be sda, sdb, sdc, etc...). You can also try to unplug and then plug the SDCard to see the changes.
The Last Step (Eureka!!!)
The last step is just to insert the SDCard into the slot of your Hard-Bricked device, Turn it on and then feel its vibration that will let you know that your mission is completed. Your device is alive again.
Conclusion
The only conclusion that I can give is to NEVER GIVE UP when you are trying to solve a problem. You can be closer to the solution than you think.
Good Luck!
What are the chances you would upload the boot partition for me?
I hard bricked mine also, but unfortunately I didn't make a backup. Would you be kind enough to upload the bin file you dumped? I've looked everywhere and no one seems to have an emmc dump of this thing. lol
I dont have a laptop to move near my Shield Tv to use adb. Could all the same be done on my Android phone using Terminal Emulator, or does that over-complicate rooting the Shield Tv?
No help yet....?
Well first you'd have to have adb/fastboot and you'd have to have driver's to connect to device.
I fly racing drones and have seen a clean flight app for configuring flight controller changes. That involves connecting your quad flight controller to your Android device with a USB cable. Typically you would use a PC with drivers very similar an operation to running fastboot to root your phone. I think it comes down to which device is running command prompt can connect with its drivers to the Target device
You should post in other forums like in adb development forum or Nexus up forum.
I suppose I could try it for the yucks... But, since your the One asking? Why don't you just download a Terminal Editor (From the PlayStore), which should allow you to use (e.g. emulate), ADB at the least of it. Not sure if it'll be of much help to you at the Fastboot Level though.
TBQH: I'm not sure this is the best plan of attack. As you would almost have to be very meticulous here, as to not accidentally flash your Phablet with the Shield TV Firmware, or vise-versa.
*EDIT*
Just outta ****s, and giggles I decided to just try it out to see how far One could get with it. As it turns out, you can at least get into the Fastboot System like this. However since I don't have anything like Fastboot, or ADB as a callable executable (From Emulated Android Terminal), I can't issue any Fastboot commands durr.
It could be interesting to look Into if there isn't an Android OS version of Fastboot that could be ran from the Terminal. But, my guess is there wouldn't be. As 99.9% of Devices out there don't require you to be patched into a USB Host just to get into Fastboot / Update / Recovery Mode. And for the times when you do need a PC there is bespoke Software like Kies, or Odin out there to make that task simpler.
*EDIT II*
A quick shufti on ATE, and Fastboot brought up this Gem.
http://www.nairaland.com/2351005/how-set-up-run-fastboot
Of course the usual caveats about being Rooted, (The Device from which you plan to root from. e.g. your Phablet), apply.
I've tried this with my Nexus 6p. 7.1.1 Pure Nexus ROM. ElementalX Kernel. Rooted. I used the included USB C to USB A cable and was never able to get the Shield to show up under adb devices.
I ended up just splicing two broken micro USB cables. You just cut and match the colors. I didn't even seal the wires. No solder, no electrical tape. No heat shrink. Just made sure none of the splices were touching and it worked just fine on my laptop connected to the shield TV 2017. These were USB 2.0 cables. But make sure they're data cables and you shouldn't have any issues.
I personally tried many versions of adb for Android and could never get the Shield to show up. So I just gave up and make the USB A male to male cable and did it the right way.
Sent from my Pixel+XL using Tapatalk
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.
Hello to all
I have a BMW specific head unit running Android 8.1 and px6 processor.
The unit that i own is that one :
https://www.alibaba.com/product-det...l?spm=a2700.7724838.2017115.89.4e3cf8c9o0r9Dr
After performing a factory reset from android menu everything seemed ok.
Fresh start.
After leaving the car for some hours and come back , after start the ignition the head unit saws this ( photo attached )
After reading so much i see that the unit is in recovery but since there are no physical button except e reset hole i cannot move into the recovery and select any of the two options.
I tried to install an external usb keyboard but it is not recognized when restarting the unit with the keyboard hooked up.
I tried to install an external usb mouse that is recognized , i can move between the two options if i long press a button it highlights the option but does not give " enter " command.
Seller send me the firmware file tha is in .zip format so i cannot use the sd card tool .
I run out of options at the moment .
Can someone give a hand on this?
The best thing is have this zip file to img file , make a bootable sd card and start from there.
Is that possible?
Thank you all guys !
I attach some other photos of the board if you have any idea.
I opened searching for the C17 ic to do the shprting thing but unless i am blind i cannot find it
Ok, in order to update you will need to name the zip as "update.zip" - that's how i got mine to start.
Also you need to format the SD-Card fat32 and make sure it's empty when you copy the Update.zip file
The other option is to go in recovery but you need to find a working keyboard, for example a Logitech K120 for example works well with mine.
Try both USB ports, and try to cut the power completely when you restart and switch the port.
If you can't get a keyboard to work it's pretty tricky.
You will need to unsolder the small resistor shown it the picture, and bridge the connections next to it. (Don't loose it, you will need to put it back after flashing!)
After that you have access to the OTG, and you can use ADB - USB.
not sure it will work as expected in your case, because the unit is a bit different but if all else fails and you don't care about warranty, you could give it a try.
Can't post the image here.
the link is hxxps://ibb.co/gD2LWhb - just replace xx with tt
dice66 said:
Ok, in order to update you will need to name the zip as "update.zip" - that's how i got mine to start.
Also you need to format the SD-Card fat32 and make sure it's empty when you copy the Update.zip file
The other option is to go in recovery but you need to find a working keyboard, for example a Logitech K120 for example works well with mine.
Try both USB ports, and try to cut the power completely when you restart and switch the port.
If you can't get a keyboard to work it's pretty tricky.
You will need to unsolder the small resistor shown it the picture, and bridge the connections next to it. (Don't loose it, you will need to put it back after flashing!)
After that you have access to the OTG, and you can use ADB - USB.
not sure it will work as expected in your case, because the unit is a bit different but if all else fails and you don't care about warranty, you could give it a try.
Can't post the image here.
the link is hxxps://ibb.co/gD2LWhb - just replace xx with tt
Click to expand...
Click to collapse
Thank you for your reply
Well i managed to connect a keyboard and try both options
1) try again
2) factory reset data
in some cases the unit boots lets me play with it make adjustments etc.
But after a full reboot unit is unresponsive again and starts again the boot loop cycle.
After full reboot unit complains that the code i entered is correct but files are damaged and needs full factory reset.
I press the button to full reset but it stays forever in BMW Connecting screen.
The thing is that Android 8 has not .img file to use SD card tool to make a bootable sd so i need to get to recovery.
It has zip file that means OTA so i need recovery.
I do not have success on that.
I think that the SoM is corrupted and i do not know how to fix for now.
Any ideas for that?
If you can get into android some times, then do the following.
Try until you are booted in android.
When you manage to get in android, depending on where you play with the unit, try to have it connected to wireless, and with a laptop on the same wireless network.
Then, install Terminal Emulator on the unit.
Open it and try the following commands;
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1Then, on your laptop install adb, and connect to the unit using ADB connect xxx.xxx.xxx.xxx (xxx... is the ip of the unit)
Once connected you can run the adb reboot recovery command to get in recovery(make sure you have the keyboard working)
Btw, you don't need the sdcard to be bootable.
Try to have the zip file you received directly on the sdcard. Should be PX6.zip, or update.zip, have them both.
Also if you have it on the sdcard when it boots in android, it will detect the update, and you can flash it directly from android.
dice66 said:
If you can get into android some times, then do the following.
Try until you are booted in android.
When you manage to get in android, depending on where you play with the unit, try to have it connected to wireless, and with a laptop on the same wireless network.
Then, install Terminal Emulator on the unit.
Open it and try the following commands;
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1Then, on your laptop install adb, and connect to the unit using ADB connect xxx.xxx.xxx.xxx (xxx... is the ip of the unit)
Once connected you can run the adb reboot recovery command to get in recovery(make sure you have the keyboard working)
Btw, you don't need the sdcard to be bootable.
Try to have the zip file you received directly on the sdcard. Should be PX6.zip, or update.zip, have them both.
Also if you have it on the sdcard when it boots in android, it will detect the update, and you can flash it directly from android.
Click to expand...
Click to collapse
I will try that next time it will boots to Android .
The file that the seller send me was px6.zip
I will try both of them.
You mean try them on boot correct?
koutsouk said:
I will try that next time it will boots to Android .
The file that the seller send me was px6.zip
I will try both of them.
You mean try them on boot correct?
Click to expand...
Click to collapse
Have them on the sdcard all the time, and the sdcard connected.
once you manage to get in android, it should pop up a message with the update
dice66 said:
Have them on the sdcard all the time, and the sdcard connected.
once you manage to get in android, it should pop up a message with the update
Click to expand...
Click to collapse
i did that with a usb drive.
Update gone smoothly after request to remove the usb drive the unit boot up correctly but in the next full restart i had all the symptoms again.
I thought that you mean to have the files before boot and it will detect update before going into android.
I tried booting with sd card mounted with px6.zip and update.zip inside
It gives No Signal in every boot even with one of two files inside.
and for sometime now it does not boot to android at all !!
Sorry to invade your thread but I have a similar issue about updates. I have a PX6 unit from AVIN and they have released 2 updates for the unit but they just REFUSE to start. I have followed their instructions 100 percent and it recognizes the USB stick in either USB port but the updates don't start. I've tried multiple USB sticks and nothing works. Their support is worthless. Is there a way to launch the update manually?
hello, how can i get recovery mode??
I try whit reset buttom, touching with 5 fingers.. but nothing