adb cant find 4g Adas Mirror, any help pls. - General Questions and Answers

Hi!
This is my first post here, I hope I won't make many mistakes and troubles...
A friend of mine asked me to help him with his car Android based mirror.
The mirror is a "4G Adas Mirror" which is now stucked on the boot screen/logo.
Android version on the device is 8.1.
I've tried to reset through the hard reset button, without success.
I tried to connect the device on my PC to try to get access with adb, no success.
Adb cant see the device, the device list is empty.
When I check in the device manager on my PC I can see under "Portable Devices" installed,
with the name "MTP USB Device".
I also downloaded several drivers but can't install them, not for my device.
And now I'm out of ideas.
If somebody have any idea what could I still try to bring back the device into live, I would really appreciate.
Thank you.
Btw.:
My PC is running win10 x64 Pro

You're probably stuck with only the MTP interface (and not a composite device with MTP and ADB) but it might be worthwhile to double check.
Is the MTP interface active? Can you see any files in Windows File Explorer?
You can check with UsbView.exe to see if there is only one interface, the MTP.
The next step is to try various buttons on boot to see if you can get to recovery, fastboot or ROM bootloader.

Thanks for the fast replay, I cant access the device throug any file manager, as you mentioned, I checked with UsbView.exe already, just to be sure.
The MTP is active.
I've tried many many times the switch combination with the reset button, to try to get into any recovery or whatever cmd line mode, but without success.
The device hase only two buttons:
1. Power button
2. Reset button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well, there's many ways to skin a cat.
If you open it up there could be a UART with a rooted hardware console.
There could be pushbuttons or test points to get into some other mode.
Good photos will tell us.

So, here we are....
the mirror crashed until I tried to open it.
However, if somebody is interested to hack and poke around this device, I'm familiar to open the device,
make schematics, pictures and try to hack into the device to try to make it alive again.
If somebody is willing to be a part to this pls. let me know and let's get started.

Open it up and take photos.

I'm trying and searching for a way how to open it but not fully crack the mirror, which is actually also a monitor...
I hope I will open the device soo and be back...

Related

[Q] Urgent Help

Hi Guys,
Have literally spent 8 hours trying to fix this damn phone, it's my mothers which needs a complete wipe using the stock rom. Even my younger brother had a go for a week and has been passed on to me. Not touched an Android phone in about two years so very rusty with the whole roms and flashing etc.
The main issue is I can't get Windows 8.1 to see the phone in USB wether it be plugged directly in Android, USB debug, bootloader or Fastboot USB. I have installed ADB with all the drivers, tried multiple HTC drivers and HTC Sync, PDAnet, AMD chipset drivers, USB controller drivers, random drivers from here on XDA as well as a multitude of other sites. Tried USB 3.0 and 2.0 (front and back slots).
How am I supposed to flash a custom recovery without the computer seeing the phone? If I can just get that sorted I am pretty much set with getting the stock rom on there and the rest. Not sure what my brother has put on it or if he has flashed a custom rom or changed the radio/boot because I have no clue what the phone is supposed to be running.
Please some help here, don't really want to be spending more time on this.
Details:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure how to help you, because i don't even know, if your phone boots to OS or not.
There are some apps out like flashify or TWRP Manager which should be able to flash a recovery from OS, but i never used that tools and don't know, if they work with One SV.
You should really get your fastboot working. I don't have windows 8(.1), but there are many threads here on xda about that.
Other solution could be to search for someone with a windows 7 pc.
old.splatterhand said:
I'm not sure how to help you, because i don't even know, if your phone boots to OS or not.
There are some apps out like flashify or TWRP Manager which should be able to flash a recovery from OS, but i never used that tools and don't know, if they work with One SV.
You should really get your fastboot working. I don't have windows 8(.1), but there are many threads here on xda about that.
Other solution could be to search for someone with a windows 7 pc.
Click to expand...
Click to collapse
Yes the phone does boot into the OS but again is not properly recognized, PDAnet and HTC Sync find the phone but doesn't show up or in ADB. I have checked well over 30 threads on here regarding Windows 8.1, downloading various tools and drivers etc without success.
Will check out those links.
Thanks.

Help with getting SuperCID (11111111)

Hello,
I've been trying tirelessly to root my phone so that I can modify it with custom roms. Now I'll admit, initially I didn't do as much research as I should have. I tried rooting my device as you would a normal One X (which obviously failed) and tried an assortment of other apps and software (towel root, king root, Hasoon's All in one toolkit, etc.) to no avail. Eventually I learned of the xpwn method. And after much searching on this forum and other sites, across the board, this seems to be the way to go. However following the commands had absolutely no effect on my phone. More research. My problem was that although my computer could recognize adb devices, it could not recognize my device while in fastboot. Because I'm running Windows 10 and both my USB ports are 3.0, no matter what drivers I installed, it would not recognize my phone. Upon learning this, I tried moving to my laptop which has windows 7 installed. Lo and behold, the hard disk crashes upon booting. And any other computers I have access to with windows 7 (At the job, school library) I don't have administrative privileges to tamper with. A friend let me borrow her laptop that has windows 8.1 installed on it. Reading up on it, I know it has a similar problem with recognizing devices while in fastboot. But after more digging, I was able to get it too see my device (yayy!!). So now I finally have a laptop with the proper drivers installed, a USB 2.0 port, and the ability to recognize my phone in fastboot mode. I downloaded and ran a .bat file (several actually) that followed the xpwn method (I wanted a one click method so I couldn't possibly mess anything up). However, anytime it attempts to push files to "data/local/tmp/" blahblahblah, it fails to copy because "Permission Denied." I tried to manually type in the commands and I am met with the same error!! And I can't locate this directory either to see if it's set to read only. ...My laptop only has one account which has administrative privileges. What gives!?!?
Any help or advice would be greatly appreciated.
Bootloader Info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Error Messages:
Phone Info:

Trying to backup a locked Android Phone

So I have a small problem that has giving me a headache the past few days. I got an old Nokia 6.1 from my mom & was asked to get the pictures & documents from it. I removed her pattern lock, because I was annoyed to use it all the time. A couple of days later, the phone has out of the blue a security pin. Which obviously no one knows, because no one configured it...
I spent hours looking different ways to extract the data or to bypass the lock & sofar I think I ran out of all the options.
Here is my current state & I would really appreciate some advice how to proceed.
1. Find my device:
The phone is on the list. But it shows that the last activity was on the 10th january & can't be reached it even though it's connected to the internet via my mobile data. Furthermore it seems that I wouldn't be able to unlock it anyways because it only gives me two options "Call the Phone" & "Set up secure & delete".
2. Installing Aroma to extract the data/remove lock files:
I can't do that because there is no custom recovery installed on the phone. Just the stock.
3. Installing a custom recovery:
I can't install/flash anything on the phone because the developer options, usb debugging & bootloader are not unlocked/enabled.
I came as far as being able to see my dive with adb on my pc, but I couldn't flash anything of it, because the signature fails.
I'm now posting this threar, to see if anybody has some advice for me, how I could get the pictures from the phone.
Thank you all in advance~
Push
The door to any Android device is ADB.
You say
came as far as being able to see my dive with adb on my pc,
Click to expand...
Click to collapse
hence ADB obviously is fullly working, means it should be possible to pull out the data in question by means of ADB.
Hi, thank you for your answer, I have expressed myself wrong/mixed adb & fastboot up. What I wanted to say, is that I can see the device via fastboot. Unfortunately not over adb.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as you can also see in the screen
If I understood what I read, there is no way to access the phone like this, is that correct?
Is there anything else I can do?
The Phone itself gives me an option to "Apply Update from ADB". My knowledge about this stuff is barely anything. But is there a way for example I could install/update an android version/new system without losing the internal data? At that point I don't care about the phone working properly, as I would like to get the pictures from it & root + wipe everything from it.
push
As "Apply Update from ADB" implies this option is used to flash an OS's update provided by OEM/carrier: updating an OS doesn't affect user data stored on phone.
Have you ever tried to exit phone's fastboot mode by running Fastboot commands
Code:
fastboot devices
fastboot reboot
I ended up factory resetting the phone. This Thread can be closed
If you have usb debugging on. Then you can use ADB. You can try to mount user partition and you can copy that partition.

Question ROG phone 5s not recognized in fastboot mode, but ADB works... Windows driver issue?

Hi All,
I bought a ROG phone 5s (ZS676KS) direct from ASUS and I've been trying to root it all week. The firmware version is WW_18.1220.2111.160.
So far, I have been able to unlock the bootloader using Asus' app. My phone displays the unlocked bootloader warning on every boot.
I can't make fastboot work... the "adb reboot bootloader" command does work. I can also boot using the power + volume up button. But the "fastboot devices" command always comes up empty.
I found two possible reasons why fastboot doesn't work. So far I failed to fix either one.
First, the "OEM unlocking" option is missing in my developer options menu. I have the "USB debugging" option checked off. But many of the guides I read online say to allow OEM unlocking and I can't do that. But I've also seen people say that it doesn't matter. So, I don't know if this is a real problem. I can't find any reference to this problem except in Samsung phones. I tried the recommended fix but it didn't work.
Second, something's wrong with the fastboot driver on my computer. When get my phone into fastboot mode and plug it into the computer, device manager shows a device called "ASUS_I005D" with an orange caution icon on it. The error message in the properties menu says "The drivers for this device are not installed. (code 28)". This is probably the real problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Windows isn't finding a driver with its online driver search. I spent a few hours playing with Windows drivers to no avail. But maybe I missed something. I did find "ASUS_Android_USB_drivers_for_Windows_20150212" online and it didn't help.
I have tried different wires and USB ports and I'm using the side port of the phone instead of the bottom (although I tried the bottom port too). I tried another computer and that didn't work. But this was before I realized what was happening with windows drivers so I didn't check the device manager. I'm away from home now so I just have access to the one computer for now.
Does anyone know where I can find the correct driver? Or is there another approach I haven't considered? I hope there's nothing fundamentally wrong with the phone. I kind of just bought it without explicitly verifying, assuming the 5s is rootable since the 5 is...
Thanks Everybody,
Success is disgusted by some people, and will not share any files for free in the future.
It's not your device but likely Win 10 playing games with you. First completely uninstall the device driver to clean things up. Reboot your pc into Safe Mode. Plug in your phone from the side connector with a good data capable USB cable. From Device Manager choose "Add Legacy Hardware" from the menu and point the location to where you have saved the latest official Android USB drivers and install. Reboot Windows normally. If things have gone well, you should be able to both ADB & Fastboot into your device.
What a relief.
I am now able to flash my patched boot.img.
Thanks to both of you. I'm off to the races...
For me I just get a Ubuntu iso, boot your computer off a USB stick, install adb and fastboot via apt, and boom, no crappy drivers needed

Question Pixel 7 Pro stuck on "usb serial device" with no screen

Hey all,
after trying to flash images from a private build
[
1) REPO: repo init -u https://android.googlesource.com/platform/manifest -b android-13.0.0_r11
2) LUNCH: aosp_cheetah-userdebug
3) fastboot flashall -w for the out directory
]
the Pixel was stuck on a boot loop, showing the google screen but nothing more.
after battery drained, tried to put it on fastboot mode, unsucessfully
right now, the device is in this state, with black screen showing nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does someone know what tools are needed to save the device and guide to do it?
and second question - something in the process I described above is wrong about the flashing that caused it to fail?
Wow...where to begin...?!
I completely don't know to what end you were attempting to get to or how you were trying to get there, but looking at such an unconventional method of flashing and unconventional "private build" (so I assume not the full factory images Google publishes on their dev page), I wouldn't be surprised if you didn't permanently brick your device -- especially considering the outcome is a weird "USB Serial Device" and black screen/no fastboot mode...
But what I suggest is powering on using the button combination (I believe it is PWR & VOL+Down), sometimes it takes 1-2+ minutes holding it down.
I would suggest correcting the driver, but I'm unsure if that will lead anywhere if you cannot get into fastboot mode and/or the screen stays black. But, if you think it will help; download the Google USB Drivers (can be found HERE), unzip it, uninstall (and MOST IMPORTANTLY tick the box that says delete the driver software if it pops up) the "USB Serial Device", Scan for New Hardware, if the new driver does not identify as "Android Bootloader Interface" then -- right click the new driver -- click update driver -- and either Browse to the folder where you unzipped the Google USB Drivers or manually "Let Me Pick from available drivers" and manually select the .inf file to install the driver as. That should correct your driver issue, though I don't know how helpful it will be without the screen or being able to get into fastboot mode...
And, if you don't want to risk breaking your P7P, I would suggest from now on sticking with traditional methods of flashing (platform tools or recovery mode) and Google Full Factory Images or established ROMs....
Or maybe research considerably more in the unconventional method you are trying to attempt...
Good luck to you, seems you will need it...
it's basically flashing from here
Pixel Phones as Development Platforms | Android Open Source Project
source.android.com
which I assumed will be no problems
I have tried the combinations to fastboot, but unsuccessfully, all I see is black screen.
thanks for reply.

Categories

Resources