Database Users

[Q] Controlling Nexus 4 on the PC after breaking screen, possible?

Hey guys,
Haven't been here for a while. Okay, so I have a bit of a dilemma and every solution I've found requires something I just can't do. Here's the situation: my screen is broken, it has a lock screen, not in developer's mode, not unlocked.
This means:
I won't be able to transfer my files over, as I have to get past the lock screen
I can only install applications from Play store on my computer, but can't launch them
No use for any method that requires phone to be rooted
Can't even activate any USB options to transfer files some other way
Still need to be able to control it to create backups and such of important SMS messages, get files off
Does anyone have any suggestions at all? I don't want to have to resort to replacing the screen, as that'll end up costing me enough time and money where it's more cost-effective to purchase a new phone; however, I really need what's on my phone as soon as possible. Thanks in advance.

I think I have a solution for you: http://forum.xda-developers.com/showthread.php?t=2177440 Specifically, you'll want to read this post:
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key​11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
In the future, always enable USB debugging in case of incidents like this. You can then use ADB commands to do a heck of a lot of things. Of course, it does make your phone data vulnerable if it gets stolen, but I'm willing to take the risk, plus 10 wrong PIN tries = reset anyway.

machoman1337 said:
I think I have a solution for you: http://forum.xda-developers.com/showthread.php?t=2177440 Specifically, you'll want to read this post:
In the future, always enable USB debugging in case of incidents like this. You can then use ADB commands to do a heck of a lot of things. Of course, it does make your phone data vulnerable if it gets stolen, but I'm willing to take the risk, plus 10 wrong PIN tries = reset anyway.
Click to expand...
Click to collapse
Now with 4.2.2 the adb device appears as offline and the only way to bring it online is to use the touch screen.... I have an important email on my phone just looking at me and its driving me completely INSANE that I cannot get to it.
I have to wait 4 days to get a screen in just to get to this important email..... THANKS GOOGLE!
oh and tmobiles insurance is a joke $100 deductable... the clear your phone. my way $79 new screen and same phone.

ikarma said:
Now with 4.2.2 the adb device appears as offline and the only way to bring it online is to use the touch screen.... I have an important email on my phone just looking at me and its driving me completely INSANE that I cannot get to it.
I have to wait 4 days to get a screen in just to get to this important email..... THANKS GOOGLE!
oh and tmobiles insurance is a joke $100 deductable... the clear your phone. my way $79 new screen and same phone.
Click to expand...
Click to collapse
where did you get the screen for $79???

hi, what does this mean?
2. Install the USB driver from the SDK so that it appears as an ADB device

michaeliang said:
hi, what does this mean?
2. Install the USB driver from the SDK so that it appears as an ADB device
Click to expand...
Click to collapse
1. It means that if you have the SDK Manager installed on your computer, somewhere between the last packages at the bottom of the list, you'll see "android drivers" (or something similar). With those drivers, your device will show up in "Device manager"(the Windows' one) as an adb device.
2. But if you don't want to get the SDK Manager and be quicker, you can download only those drivers, directly from the "Google developers" page and install them manually by going to "Device manager", right clicking on the Nexus 4 (it will appear with a yellow triangle on it, maybe), then "Update driver", "...BROWSE computer...", then click again on "Browse", then go to where the drivers have been downloaded and select the entire folder by highlighting it and clicking ok (or something). The folder with the driver would look like this "latest_usb_driver_windows" and inside you'll see another folder called "usb_drivers". That's what you need to select and install.
So that's what you need to do to make your phone appear as an adb device in "Device manager". And, of course, adb let's you do a lot of stuff to your phone through your computer, but probably you already knew that.

T-r42 bricked

Hello,
i need an update.zip or an update.img of stock firmware for T-R42 B351 V1.0 or V1.1
to be put into the external sd card to recover the system
I have recovery version 4.2.01, that prompts for this options:
update from external storage: needs update.zip
update rkimage from external storage: needs update.img
I have no other options because my pc is no more able to recognize my T-R42 B351 V1.1
Where can i found such files?
Thanks

T-R42 B351 V1.0 stock firmware
Vicolodo said:
Hello,
i need an update.zip or an update.img of stock firmware for T-R42 B351 V1.0 or V1.1
to be put into the external sd card to recover the system
I have recovery version 4.2.01, that prompts for this options:
update from external storage: needs update.zip
update rkimage from external storage: needs update.img
I have no other options because my pc is no more able to recognize my T-R42 B351 V1.1
Where can i found such files?
Thanks
Click to expand...
Click to collapse
All the stock firmware for are here: T-R42 B351 V1.0 or V1
http://pan.baidu.com/share/home?uk=2134144741#category/type=0

el_easy said:
All the stock firmware for are here: T-R42 B351 V1.0 or V1
http://pan.baidu.com/share/home?uk=2134144741#category/type=0
Click to expand...
Click to collapse
thank you,
i am a newbie,
do you think that with stock rom it is possible to update the device
putting the rom in the sdcard and choosing `update rkimage` option?
thanks!

Vicolodo said:
thank you,
i am a newbie,do you think that with stock rom it is possible to update the device
putting the rom in the sdcard and choosing `update rkimage` option?
thanks!
Click to expand...
Click to collapse
stock firmware you update using your computer with Rockchipbatch tool
- Download firmware from T-R42 B351 V1.0 and extract the file save it to your desktop.
- Press the recover button of T-R42 and don’t loose it. Then you can connect T-R42 and computer by using micro USB cable (OTG port of T-R42 to USB port of computer.
- You can now launch the Batch Tool by double clicking on the file named RKBatchTool in the folder where you extracted the Batch Tool 1.7 to. You should see the following:

el_easy said:
stock firmware you update using your computer with Rockchipbatch tool
- Download firmware from T-R42 B351 V1.0 and extract the file save it to your desktop.
- Press the recover button of T-R42 and don’t loose it. Then you can connect T-R42 and computer by using micro USB cable (OTG port of T-R42 to USB port of computer.
- You can now launch the Batch Tool by double clicking on the file named RKBatchTool in the folder where you extracted the Batch Tool 1.7 to. You should see the following:
Click to expand...
Click to collapse
thank you,
but the problem is that my pc cannot see the t-r42

Vicolodo said:
thank you,
but the problem is that my pc cannot see the t-r42
Click to expand...
Click to collapse
You may be bricked. If so you can jump pins 8&9 on the nand chip to get it into MaskRom mode.
1.Load RKBatchTool with your ROM.
2.Connect only OTG cable - power is not required.
3.Hold power button down.
4.Short pins 8 and 9 with needle or pin until Batch tool display blue icon that is MaskRom mode.
5.Remove needle and load firmware into program.
6.Click restore and wait for success.
Hope this helps

BRICK0044 said:
You may be bricked. If so you can jump pins 8&9 on the nand chip to get it into MaskRom mode.
1.Load RKBatchTool with your ROM.
2.Connect only OTG cable - power is not required.
3.Hold power button down.
4.Short pins 8 and 9 with needle or pin until Batch tool display blue icon that is MaskRom mode.
5.Remove needle and load firmware into program.
6.Click restore and wait for success.
Hope this helps
Click to expand...
Click to collapse
THANK YOU!!
but HOW CAN I FIND THE NAND CHIP on my T-R42 board?
i already asked in other threads and other forums but i have not get answers yet
In attachment i link the snapshot of the board... can you help me?
THANKS!

Vicolodo said:
THANK YOU!!
but HOW CAN I FIND THE NAND CHIP on my T-R42 board?
i already asked in other threads and other forums but i have not get answers yet
In attachment i link the snapshot of the board... can you help me?
THANKS!
Click to expand...
Click to collapse
what does it say on the big rectangular chip above the heatsink? I think it might be on the other side of the board though, can you take a pic of the other side?

BRICK0044 said:
what does it say on the big rectangular chip above the heatsink? I think it might be on the other side of the board though, can you take a pic of the other side?
Click to expand...
Click to collapse
Yes,
here is the link to all the snapshots i did (there are also snapshots of the power adapter, you can skip them)
https://www.dropbox.com/sh/fnz01w8ylpxuzxi/oc5gJHjO5g

Vicolodo said:
Yes,
here is the link to all the snapshots i did (there are also snapshots of the power adapter, you can skip them)
https://www.dropbox.com/sh/fnz01w8ylpxuzxi/oc5gJHjO5g
Click to expand...
Click to collapse
I don't see any of the other side of the board, but I need to know the numbers and letters on the Toshiba chip. I can't make them out in the pics

BRICK0044 said:
I don't see any of the other side of the board, but I need to know the numbers and letters on the Toshiba chip. I can't make them out in the pics
Click to expand...
Click to collapse
Ok thank you, i understand,
i am not at home now
When this evening i go back to home i will send to you the numbers and letters of the Toshiba chip,
and higher resolution snapshots of all the chips
I will try also to take some snapshots of the other side of the board (not yet done this because i had fear to break some connector to take it out)
Thank you a lot!

Vicolodo said:
Ok thank you, i understand,
i am not at home now
When this evening i go back to home i will send to you the numbers and letters of the Toshiba chip,
and higher resolution snapshots of all the chips
I will try also to take some snapshots of the other side of the board (not yet done this because i had fear to break some connector to take it out)
Thank you a lot!
Click to expand...
Click to collapse
Almost sure it is the Toshiba chip above the heatsink but need the number, may not get right back to you because Im going on vacation but will try.
---------- Post added at 12:51 PM ---------- Previous post was at 12:29 PM ----------
BRICK0044 said:
Almost sure it is the Toshiba chip above the heatsink but need the number, may not get right back to you because Im going on vacation but will try.
Click to expand...
Click to collapse
I magnified the Toshiba chip and it is your nand chip. I use the end of a needle with the eye in it and be patient it might not work the first time just keep trying with the directions I gave you. As soon as you see the blue light in rkbatchtool come on remove the needle and restore. Good luck let me know . By the way the number one pin is the one by the dot on the chip and count down from there.

BRICK0044 said:
Almost sure it is the Toshiba chip above the heatsink but need the number, may not get right back to you because Im going on vacation but will try.
---------- Post added at 12:51 PM ---------- Previous post was at 12:29 PM ----------
I magnified the Toshiba chip and it is your nand chip. I use the end of a needle with the eye in it and be patient it might not work the first time just keep trying with the directions I gave you. As soon as you see the blue light in rkbatchtool come on remove the needle and restore. Good luck let me know . By the way the number one pin is the one by the dot on the chip and count down from there.
Click to expand...
Click to collapse
hello, thank you!!
the numbers and letters are:
TOSHIBA SW2857
TAIWAN 13359AE
TC58TEG6DCJTA00
here the snapshots:
https://www.dropbox.com/sh/vmkcl05ha541j11/_orwLkI82h

NAND CHIP FROM OTHER T-R42 board
These are examples from other boards that are bricked, look at it ,are similar like your...
Try 8 and 9 pins with a needle..
I have read that the NAND chip like the pin 5 ,6 , 6 and 7, 7 and 8 or 8 and 9. as work too.. , But 8 and 9 work for many people... . Don't hurry up it may take many attempts ...
More Information here:Unbrick or fix NAND on the MK808

el_easy said:
These are examples from other boards that are bricked, look at it ,are similar like your...
Try 8 and 9 pins with a needle..
I have read that the NAND chip like the pin 5 ,6 , 6 and 7, 7 and 8 or 8 and 9. as work too.. , But 8 and 9 work for many people... . Don't hurry up it may take many attempts ...
More Information here:Unbrick or fix NAND on the MK808
Click to expand...
Click to collapse
Hello,
thank you
counting starting from the pin no 1 (i suppose it is the pin on the corner near the dot on the chip, can you confirm?),
i tried with 6,7 and 7,8 and 8,9
but with no results
instead, shortening the 9,10 i get on the pc the message: 'unknown usb device' (like when i press the reset button) but RkBatchTool (v 1.7) does not go to Mask Rom Mode.
and i get this message only when the power adapter is connected
But seems that the NAND flash is not resetted:
turning off / on the device, i see that is loaded the same firmware (boot animation starts as before...and so on)
I supposed that this operation should reset the NAND flash, or i am wrong?
Thanks!

Vicolodo said:
Hello,
thank you
counting starting from the pin no 1 (i suppose it is the pin on the corner near the dot on the chip, can you confirm?),
i tried with 6,7 and 7,8 and 8,9
but with no results
instead, shortening the 9,10 i get on the pc the message: 'unknown usb device' (like when i press the reset button) but RkBatchTool (v 1.7) does not go to Mask Rom Mode.
and i get this message only when the power adapter is connected
But seems that the NAND flash is not resetted:
turning off / on the device, i see that is loaded the same firmware (boot animation starts as before...and so on)
I supposed that this operation should reset the NAND flash, or i am wrong?
Thanks!
Click to expand...
Click to collapse
8,9 pins should be around here

el_easy said:
8,9 pins should be around here
Click to expand...
Click to collapse
ah...thanks!
so i have not to count the pins starting from the dot that i see on the corner of the chip?

Tc58teg6dcjta00
hello,
i am searching for the pdf datasheet related to the chip TC58TEG6DCJTA00
I searched it on many websites, but i am not able to find it...

el_easy said:
8,9 pins should be around here
Click to expand...
Click to collapse
I don't think you are right, the dot is on the other side. So pin 8,9 should be on the other side.

buhohitr said:
I don't think you are right, the dot is on the other side. So pin 8,9 should be on the other side.
Click to expand...
Click to collapse
thanks,
i asked the datasheet to toshiba,
but they answered me they can not send informations to private persons ...
by the way... i tried with all pins 1,2 2,3 3,4 4,5 etc but there is no way to get the Mask Rom Mode...
the only message i get on my pc shortening some couple of pins (es.: 9,10, but also some others) is 'unknown USB device'... (and this happen only when i connect the power plug... when it is not connected i have no messages...)
(like when i press the reset button)

[Q] Power Button Light and Nothing Else - Please Help

Just as the title states - the power button will light up, but just a black screen.
I've read around, holding this button and that button, loading zip files on the sd card - holding this and that, still nothing.
I get no vibration and still a black screen like it's turned off.
Perhaps a bad logic board? - If so, I'll stop wasting my time and yours.
Thanks in advance for any replies.

samething here...power light on , black screen. Is it totally bricked?

Helps to see that I'm not the only one with the same issue.
I can only hope someone chimes in to direct us both in the right direction.

I think you should try to enter apx mode (you have to keep pressing reset with a needle or something like that, press the power button for 3-4 seconds, and after 1 second release the reset), and see if you can flash a new bootloader and recovery with the A500APXFlash tool (search in the web). But you have to retrieve the cpuid of your tablet, in order to use the flash tool...It's a kind of mess, but it can be done.

omniastrider said:
I think you should try to enter apx mode (you have to keep pressing reset with a needle or something like that, press the power button for 3-4 seconds, and after 1 second release the reset), and see if you can flash a new bootloader and recovery with the A500APXFlash tool (search in the web). But you have to retrieve the cpuid of your tablet, in order to use the flash tool...It's a kind of mess, but it can be done.
Click to expand...
Click to collapse
I'm lost.
Let me just say, when I mean a black screen, I mean it's black - no lcd back-lighting or vibration from the unit.
I've tried what you described w/o a micro sd card in the slot and nothing hooked up to the tablet what so ever - nothing happens, except the power light coming on.
I've searched for the tool, read a little bit, but I'm getting lost within the terms.
Nothing I come across really explains what and how to do from a dummy standpoint.

Velocity_Stack said:
I'm lost.
Let me just say, when I mean a black screen, I mean it's black - no lcd back-lighting or vibration from the unit.
I've tried what you described w/o a micro sd card in the slot and nothing hooked up to the tablet what so ever - nothing happens, except the power light coming on.
I've searched for the tool, read a little bit, but I'm getting lost within the terms.
Nothing I come across really explains what and how to do from a dummy standpoint.
Click to expand...
Click to collapse
I know that feeling...It's non easy, even for those who knows a bit of pc and electronic devices (like me). In these days I have tried all I could try in order to revive the Acer of my friend. At one point it didn't even show the Acer logo, neither anything on screen, only the power light on. I suppose that the bootloader was corrupted somehow. So, if you wanna try, you will need:
1) the CPUID of your tablet. For this you can use usbdeview, if you have ever connect the tablet to your pc (if you haven't it's much more difficult!). Double click on USBdeview.exe, click on "edit" and then on "find" (or simply CTRL+F). Search for "Acer Iconia" and then double click on the result. Now copy the serial number somewhere.
2) If you got the cpuid you can get the SBK (copy the serial numer on this site, and click on "generate my SBK". Now copy all the SBK and paste it on notepad or similar. All the 4 parts, with all the spaces!)
3) Now the tricky part: open the A500APXFlash tool, click on "Bundle market", "view bundles" and select one of the bootloader with a decent recovery (for example the bundle number 17). Type the number of the bundle, and click on "download". You can download it on your pc, or you can download the bundle in a temporary file. It doesn't change much, you choose.
4) You can skip the "BTC selection", and go on. Now follow the instructions on screen, and if your tablet get in apx mode maybe you are lucky enough to recover it.
I don't remember if you have to install the Iconia drivers in advance, but maybe you already have them on your pc.
If you manage to flash the bootloader, then you could flash whatever rom you want. If something is not clear, feel free to ask.

omniastrider said:
I know that feeling...It's non easy, even for those who knows a bit of pc and electronic devices (like me). In these days I have tried all I could try in order to revive the Acer of my friend. At one point it didn't even show the Acer logo, neither anything on screen, only the power light on. I suppose that the bootloader was corrupted somehow. So, if you wanna try, you will need:
1) the CPUID of your tablet. For this you can use, if you have ever connect the tablet to your pc (if you haven't it's much more difficult!). Double click on USBdeview.exe, click on "edit" and then on "find" (or simply CTRL+F). Search for "Acer Iconia" and then double click on the result. Now copy the serial number somewhere.
2) If you got the cpuid you can get the SBK (copy the serial numer , and click on "generate my SBK". Now copy all the SBK and paste it on notepad or similar. All the 4 parts, with all the spaces!)
3) Now the tricky part: open the A500APXFlash tool, click on "Bundle market", "view bundles" and select one of the bootloader with a decent recovery (for example the bundle number 17). Type the number of the bundle, and click on "download". You can download it on your pc, or you can download the bundle in a temporary file. It doesn't change much, you choose.
4) You can skip the "BTC selection", and go on. Now follow the instructions on screen, and if your tablet get in apx mode maybe you are lucky enough to recover it.
I don't remember if you have to install the Iconia drivers in advance, but maybe you already have them on your pc.
If you manage to flash the bootloader, then you could flash whatever rom you want. If something is not clear, feel free to ask.
Click to expand...
Click to collapse
I hooked the tablet up to my pc and saw the term APX pop up at the bottom right of the pc screen, like any new usb device does.
I ran usbdereview in section 1 of your instructions. Found APX in the list, double clicked and it brought up very little info about the device, but no serial number. Is the serial number on the original box the box the tablet came in possibly be the same serial number I might be trying to find? Cause I have the original box with all the bar code label info.
I won't go any farther until I hear back from you.
Thank you very much for attempting to walk me through this process, it really means a lot.
By the way, I'm a pc guru too, on a hardware platform mostly. I've built may puters and enjoy overclocking them to see how far I can push them, but when it comes to phones and tablets, I'm lost.
Thanks again.

Velocity_Stack said:
I hooked the tablet up to my pc and saw the term APX pop up at the bottom right of the pc screen, like any new usb device does.
I ran usbdereview in section 1 of your instructions. Found APX in the list, double clicked and it brought up very little info about the device, but no serial number. Is the serial number on the original box the box the tablet came in possibly be the same serial number I might be trying to find? Cause I have the original box with all the bar code label info.
I won't go any farther until I hear back from you.
Thank you very much for attempting to walk me through this process, it really means a lot.
By the way, I'm a pc guru too, on a hardware platform mostly. I've built may puters and enjoy overclocking them to see how far I can push them, but when it comes to phones and tablets, I'm lost.
Thanks again.
Click to expand...
Click to collapse
Unfortunately the serial numbers are not the same....
Now, if you can't find the cpuid using usbdeview, there is another option, you have to use Linux! Here is the guide to follow to get the cpuid. After obtaining the cpuid, the rest is pretty easy. I hope this will help!

omniastrider said:
Unfortunately the serial numbers are not the same....
Now, if you can't find the cpuid using usbdeview, there is another option, you have to use Linux! Here is the guide to follow to get the cpuid. After obtaining the cpuid, the rest is pretty easy. I hope this will help!
Click to expand...
Click to collapse
I got lost pretty quick.
This is how far I made it: I downloaded Ubuntu 14.04.2, burned the image to disc, ran it live as a trial (wow, it's different than windows), used the embedded Firefox to install all of the needed libusb (not sure I did all that correctly).
The thread said "grab the code eppeP posted and save to to a text file as apx.c", so that is where I got lost.
I restarted the PC to come back here for more guidance.
I'm also unclear on the following from where I left off in the guide "fire up terminal, brouse to where the apx.c file is ........ect" What terminal are they talking about? How do I get there?
Then farther down in the thread it says "run the following commands: sudo su gcc apx.c -o apx -apx -lusb-1.0 ............ How do run these commands?
Like I said, I'm lost and very sorry I can't grasp this.

Velocity_Stack said:
I got lost pretty quick.
This is how far I made it: I downloaded Ubuntu 14.04.2, burned the image to disc, ran it live as a trial (wow, it's different than windows), used the embedded Firefox to install all of the needed libusb (not sure I did all that correctly).
The thread said "grab the code eppeP posted and save to to a text file as apx.c", so that is where I got lost.
I restarted the PC to come back here for more guidance.
I'm also unclear on the following from where I left off in the guide "fire up terminal, brouse to where the apx.c file is ........ect" What terminal are they talking about? How do I get there?
Then farther down in the thread it says "run the following commands: sudo su gcc apx.c -o apx -apx -lusb-1.0 ............ How do run these commands?
Like I said, I'm lost and very sorry I can't grasp this.
Click to expand...
Click to collapse
Sorry if I didn't answer before, but I was a little busy...So, Linux can be a little tricky, especially if you're not a developer (I learned something in school). By the way, all you have to do is to install those softwares, and then compile this piece of code, using gcc (the Gnu C Compiler). The linux terminal is basically like the Dos terminal, known as command line terminal, as you may know. There may be many kind of terminals in the Linux environment, one of the most used is the Bash Shell. In Ubuntu you can open a terminal by pressing CTRL + ALT + T.
So, just to be sure to be clear:
1) save this code in a file called apx.c
2) Boot Ubuntu, install GCC, lsusb, libusb-1.0.x, libusb-1.0-dev
3) Open the terminal, change the "working directory" with the "cd" (it's "change directory" in short) command. You have to get to the directory where the apx.c file is.
4) Run the following commands
sudo su
gcc apx.c -o apx -lusb-1.0
5) Next, pop your tablet into APX mode - plug in microUSB, hold the RESET button, and press power for around 4 sec
6) Run the following commands (assuming same root terminal permissions. If not run sudo su beforehand)
./apx
If all went well, you should obtain the cpuid, or whatever it's called. Don't forget to write that damned number somewhere (even taking a screenshot or a photo of the screen!!). I hope this can help you.

Just a minor update to what I've done so far, with questions. LOL
I decided to load Ubuntu as a side OS on my old laptop, which Vista resides on. I didn't want to screw with my tower in case of a crash, but wanted to retain my downloads and work instead of working on a *live" platform. (not knowing anything about dual boot OS)
Went well I guess, but Ubuntu takes over as the main OS if no action is taken on the boot screen, then if action is taken and you don't log into Windows, Ubuntu resorts back and loads. (lame IMO)
Ubuntu does not recognize any kind of wireless signal and wanted me to set it up manually (like I know all the numbers to make this happen, not), so I just hooked a CAT5 cable from the living room router for my next steps.
I attempted to to download the files mentioned, but remembering when I was running the *live DVD" there was a Ubuntu site for software packages, so I went there to grab what I needed. (I think this method was a fail)
When on the Ubuntu package site, I had the option of AMD64 and i386 for each file, I chose the AMD64 first and it gave a error window, then I followed up with the i386 and got nothing but a window with the circular icon and nothing in the window after that, so I closed the window.
I really have no idea if any of the downloads and installs actually work at this point. The laptop does have Intel hardware, so I'm thinking maybe the AMD64 software error-ed out because of that, but it doesn't explain why I never got a confirmation running the i386 software.
Should I have just stayed away from the Ubuntu site all together and just installed for a basic Linux system?
I'm done for tonight, but on vacation for the next week, so hopefully I can gain some ground and move forward to revamp this bricked Acer tablet.
I really appreciate your help and patients you've provided me to this point.

Now I'm really stuck.
I saved that code on my windows desktop and in Ubuntu desktop - as a windows text file. (not sure if that is the correct way)
Anyway, I did open the terminal using the 3 keys as described.
It shows: user [email protected] name:~$
I can't navigate away from that prompt....... I get: Bash: command not found or file or directory not found.
I started by using: cd/home/user name/Desktop/APX and various combinations.
Man I feel dumb.

We could try another approach: you could create a new file on the Linux desktop called "apx.c", and paste into it the source code. Then, using the command "ls" (which is the same dos "dir" command) and "cd" you could find the path to the file.
I report here some commands I used to compile the application needed to get the cpuid:
[email protected]:~$ sudo su
[sudo] password for white:
[email protected]:/home/white# ls
Desktop Downloads Music Public Videos
Documents examples.desktop Pictures Templates
[email protected]:/home/white# cd Desktop
[email protected]:/home/white/Desktop# ls
apx.c
[email protected]:/home/white/Desktop# apt-get install libusb
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libusb
[email protected]:/home/white/Desktop# apt-get install libusb-1.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libusb-1.0-0' for regex 'libusb-1.0'
Note, selecting 'libusb-1.0-0-dbg' for regex 'libusb-1.0'
Note, selecting 'libusb-1.0-0-dev' for regex 'libusb-1.0'
Note, selecting 'libusb-1.0-doc' for regex 'libusb-1.0'
libusb-1.0-0 is already the newest version.
libusb-1.0-0 set to manually installed.
The following NEW packages will be installed:
libusb-1.0-0-dbg libusb-1.0-0-dev libusb-1.0-doc
0 upgraded, 3 newly installed, 0 to remove and 90 not upgraded.
Need to get 245 kB of archives.
After this operation, 1,795 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty/main libusb-1.0-0-dev amd64 2:1.0.17-1ubuntu2 [54.7 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty/main libusb-1.0-doc all 2:1.0.17-1ubuntu2 [115 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ trusty/main libusb-1.0-0-dbg amd64 2:1.0.17-1ubuntu2 [76.0 kB]
Fetched 245 kB in 3s (74.4 kB/s)
Selecting previously unselected package libusb-1.0-0-dev:amd64.
(Reading database ... 163905 files and directories currently installed.)
Preparing to unpack .../libusb-1.0-0-dev_2%3a1.0.17-1ubuntu2_amd64.deb ...
Unpacking libusb-1.0-0-dev:amd64 (2:1.0.17-1ubuntu2) ...
Selecting previously unselected package libusb-1.0-doc.
Preparing to unpack .../libusb-1.0-doc_2%3a1.0.17-1ubuntu2_all.deb ...
Unpacking libusb-1.0-doc (2:1.0.17-1ubuntu2) ...
Selecting previously unselected package libusb-1.0-0-dbg:amd64.
Preparing to unpack .../libusb-1.0-0-dbg_2%3a1.0.17-1ubuntu2_amd64.deb ...
Unpacking libusb-1.0-0-dbg:amd64 (2:1.0.17-1ubuntu2) ...
Processing triggers for doc-base (0.10.5) ...
Processing 32 changed doc-base files, 1 added doc-base file...
Setting up libusb-1.0-0-dev:amd64 (2:1.0.17-1ubuntu2) ...
Setting up libusb-1.0-doc (2:1.0.17-1ubuntu2) ...
Setting up libusb-1.0-0-dbg:amd64 (2:1.0.17-1ubuntu2) ...
[email protected]:/home/white/Desktop# gcc apx.c -o apx -lusb-1.0
[email protected]:/home/white/Desktop# ./apx
Error: Failed to open device! //failed because there wasn't any tablet attached!!!
Click to expand...
Click to collapse

BMW Head Unit Revive

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 1​Then, 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 1​Then, 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

I bricked my HD 8 2017 after downgrading from 5.6.4 to 5.6.0.1

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