My set cannot be connected by usb so I tried to use adbwireless. Managed to get connected and device put online. However after putting the device in bootloader, I lose connection because it kept saying < waiting for device > in the command line without any action taking place. I need to unroot my device to send it back to Asus. The usb problem and the speakers went kaput too!
Anyone with experience in adbwireless so that I can do the work through it. I tried to google for more info but only the same..
Thanks
K
fastboot and adb are not the same thing.
You will never be able to communicate with the bootloader (for instance to lock the bootloader) via adb - or via any networking for that matter.
If you think the reason your USB port is not working is due to mechanical damage your best bet is to replace the small sub-assembly that has the USB connector and the headphone jack . See the iFixit teardown of the N7.
By building your own variant of a Stock ROM installer it would be possible to flash a stock ROM and stock recovery in one pass; but to lock the bootloader requires the tablet to be in fastboot mode, and afaik there is no networking possible in that mode using publicly disclosed methods.
Related
Just ran into a problem which took me some time to solve. Thought I would share it to save other people some frustration.
After an adb reboot the i5800 got stuck in "modem" mode. i.e. android booted fine but gave a modem and a serial port over usb rather than adb. Reboots did not solve the problem.
The solution is to enter recovery screen:
reboot recovery
OR
press proper buttons to get into recovery mode
And then perform a reboot from there
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
miki.antena said:
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
Click to expand...
Click to collapse
Thanks so much for this!!!! After helping hack a friends build.prop to enable Apparatus compatibility in the Market, I found USB wasn't working properly anymore. Resetting changes in the phone didn't help (I had to do this via the phone terminal) although I at least managed to buy Apparatus before the sale ended.
After initially getting confused due to a lack of drivers and the occasional 'nH' showing up devices without drivers which made me think something was borked, I worked out from the VID & PID it was just the lack of drivers making (well I'm not sure why it did the 'nH' sometimes it got serial something instead), once I installed the drivers all was fine.
Except still mass storage wasn't showing and the Samsung connect manager didn't show up on my phone when I connected USB, nor did ADB work at all. In fact, it didn't even show up in the phone menu as debugging mode if I didn't start phone with it connected (or something like that). Funnily enough when I did get it the debugging to show up I did get the USB mass storage to show up in the phone, but it didn't help (it just unmounted the card which I think is all it ever does).
Anyway after a bit more fooling around I eventuall came across http://forum.xda-developers.com/showthread.php?t=1215103 and the stuff about modem and mkasick's post which sounded a lot like it could be my problem. The code for that Samsung phone didn't work so I searched for the 5800 and came across this giving me the right code. Sure enough UART (but not USB) was set to modem instead of PDA. I was unsure whether that was wrong but changed it anyway and yep that fixed it!
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times. In fact most of the stuff except install a superuser update has been more or less repeated. I guess it was just some strange rare occurence that it somehow got changed. I did have to reconnect the USB while working the first time, not sure why but ADB lost connection then I found couldn't connect. Perhaps that's somehow related. Now that I know what to do, it's trivial but very annoying when I didn't. I still don't get why Samsung decided to make the connect manager (my phone doesn't have that) only to have some hidden option where it can be set to modem or USB.
Partially because of this, I never got to get Tilestorm HD become compatible in time for the sale although my friend wasn't so interested in that. (Eventually I worked out using the THC Tattoo modded market which reports a fake resolution enables it. Well, I also modified the build.prop but I don't know if that was necessary. I wasn't able to do it solely by the build.prop. But it was way too late by then to buy Tilestorm HD cheap.)
Nil Einne said:
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times.
Click to expand...
Click to collapse
This may sound like crazy idea, but is your USB port/connector clean?
(The USB port allows for dozens of different phone functions when using very specific resistance between data pins.)
i bought a LG D802 32gb last night as i was using a 16 gb before i wanted to flash cloudy g3.. so i tried to install custome recovery twrp...
now i am in fast boot mode..
it says :
[880]fastboot mode started
[910]udc_start()
when i attach usb cable
[1100]-reset-
[1110]-portchange-
[1120]-reset-
[1130]-portchange-
[1140]-fastboot: processing commands
i tried holding volume + and and attaching the usb cable but no luck ... so now i have NO RECOVERY, NO DOWNLOAD MODE, AND MY WINDOWS PICKING UP MY PHONE AS "USB MODEM PHONE ADB PORT"
please help
I never thought I'd have to go as far as create a thread pleading for help, but after a lot of Google searching I still cannot find someone with the same problem.
I will explain:
I am trying to use fastboot, which I (don't think) I've any problems with in the past.
I can issue commands in normal use via adb from my PC fine.
I can adb reboot bootloader ok, and can get into the bootloader any other way just fine.
I can use the volume keys to navigate the options in the bootloader just fine.
The problem comes with I connect the USB to my PC whilst in fastboot.
Windows fails to recognise the device, and says it may have malfunctioned.
It won't allow me to reinstall the drivers successfully it seems, and seems to have a problem with the USB Host Controller too.
Fastboot immediately freezes, and I'm unable to even navigate using the volume keys, let alone issue commands from my PC.
My question then is twofold:
1. Is there likely to be a problem with the USB port on my device, or some sort of bootloader corruption?
2. Is it possible to return to stock Android without using fastboot?
Finally, I would like to stress that I've seen plenty of similar looking threads, but it seemed that the posters of those threads merely had problems getting in to the bootloader or recovery.
I haven't got that problem, the problem only arises when a USB is connected to the PC, the tablet becomes unresponsive only in bootloader mode.
If anyone has any advice to offer at all, I'd greatly appreciate it.
Additionally, if the problem is solved, I will post a detailed set of instructions in case anybody else should encounter a similar problem in the future.
__________________________________________________________
Update for anyone who happens to read this in the future:
[This guide](http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html) has a useful FAQ at the bottom which helped a little.
I think I managed to determine the problem was likely a duff usb connection, either on my Nexus or on my computer.
I was able to just about hobble through by keeping the cable in the same place.
In case it wasn't just this, this is what I did:
1. Flashed TWRP recovery from their app.
Went into bootloader and failed to do anything
2. Flashed CWM recovery.
Managed to be recognised in fastboot.
I still had problems with my Nexus 'malfunctioning' -- possible the USB.
I updated the drivers using the ones from [this thread](http://forum.xda-developers.com/showthread.php?t=2588979).
3. Flashed a new bootloader image immediately (there were rumours that a dodgy version had been released accidentally). [This](http://www.androidfilehost.com/?fid=23060877489996594) is the one I used.
Then I managed to get the stock ROM flashed, and the bootloader locked up again.
Fastboot freezes whenever USB plugged in
I'm having a problem with this step...
1. When booting to fastboot with any sort of USB plugged in, your buttons on the side may not respond. In this case, pull the cable and hold down power + Vol Down until it reboots. The buttons should now respond and you can plug USB back in if you wish.
the problem is that whenever the USB cable is plugged in, the buttons don't navigate through the options.
however, whenever the usb is NOT plugged in (and rebooted bootloader) the button work just fine.
I don't have a recovery currently installed.
The issue is not with drivers on the computer,
happens while usb plugged in both windows and linux or simply just plugged into a wall outlet to charge and with different USB cables.
I need to load fastboot but i'm having this issue. Is the device bricked without hope?
any help would be appreciated.
Nexus 7 2012 Model (grouper)
Boatloader version 3.34
Ok so long story short, i have a nexus 7 2012 which a rooted and installed cyanogen mod.
I was using it as a car install and works perfect, i'm using an otg cable to mount usb sticks, triggering soft shutdown and powering the nexus etc. So usb seems to be working fine.
Basically i removed the tablet it to modify the bootloader to turn on automatically with ac power applied, if the battery runs out i have to manually power on with button, but now i'm running into a problem.
Ever since taking the tablet out and trying to connect over usb, none of my computers detect the tablet.
I've tried different operating systems, drivers, cables etc etc.
Also changed from mtp to ptp in storage and also turned on usb debugging mode. If i connect an otg cable the nexus see's the otg and i can mount usb's etc.
So i thought i might try recover the nexus back to factory, maybe there was an issue with the rom corrupted etc, I've downloaded the original 4.2.2 firmware which is currently installed.
Booted into recovery and tried re-installing the 4.2.2 zip, it keeps aborting. A guy in work tried to use sideloader and connect via adb. no luck.
I'm not very familiar with the android platform so i've no other ideas what to do and other idea's how to recover now.
The guy i work with mentioned using a usb jig, would that be the way to go or can anyone else suggest some else that might help.
Thanks
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Does adb see the device
jadesse said:
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Click to expand...
Click to collapse
I last connected the nexus to the laptop a few monts back to load some music onto it, didn't have a problem. It's only been connected to a computer maybe 3 times. once to root/rom it then another few times to load music etc.
I can't see why the usb board maybe faulty as i can read data from a usb key when the otg cable is connected.
It's a strange one. You could be right, i might try pick up a broken nexus and swap some parts. Usb board etc.
crusrod said:
Does adb see the device
Click to expand...
Click to collapse
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
foster182 said:
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
Click to expand...
Click to collapse
I am having this same problem on my (unrooted) HTC One after attempting to "convert" it from an AT&T to a Google Play Edition device with the procedure described here.
As part of the procedure, I attempted to flash the stock Google Play Edition ROM using fastboot commands, but I got an error message. The instructions say to just try the flash again, but the phone no longer connects properly via USB (error 10) while in bootloader mode. While in bootloader mode, the phone indicates there is some sort of problem (a line showing the OS version is highlighted in red), and attempting to enter recovery mode does nothing but display a phone with a big red X in it. The phone seems to operate fine and responds to ADB commands when the phone is fully booted, albeit with the old OS (not Google Play Edition) still in place.
Any Android device could theoretically get in this state. We're sort of "paralyzed", because everything we want to do to regain control of the bootloader and fix the situation seems to require issuing fastboot commands from a computer connected to the phone while it's in bootloader mode. Yet entering recovery mode or getting a computer to connect to it via USB no longer seems possible.
I wonder if there's another way to issue fastboot commands without relying on the USB connection to a computer?
Hello Everyone,
I have an issue with my nexus 6p screen all of a sudden being unresponsive to touch. The big error on my part was not setting up my videos and images to automatically backup. So now what i'm trying to do is unlock the phone using ADB and a usb cable but haven't had any luck. I've gotten as far as listing my devices, which show up an unauthorized and seem I can only authorize it from my phone. Q1. is this true? Could there be any other way to authorize my phone, or am I out of luck and my data is kaput? I've also tried an OTG cable but it doesn't load since i'm guessing the OS has to fully load for the cable work.
Do I have any choice on saving my data with a USB cable and command line or can someone suggest a tool that would help me out of this situation?
Put it into fastboot/download mode and flash the latest TWRP recovery.
Use TWRP's file manager or ADB Pull commands to pull your data off. Use ADB push to push a new ROM image and flash over everything except userdata (back it up just in case).
Hey guys, my phone had a fall from a height and the screen shattered and the phone has bent. Customer care is saying there's no guarantee that phone will work even after changing the display, as the phone is bent.
I can hear notifications, vibrations and alarm is also working.
But not able to connect the my phone to PC as USB debugging if not enabled, mobile to tv through hdmi will not work because of usb 2.0.
Can someone let me know how can I connect my phone to pc so that I can backup the data
Any additional details would helpful:
Is your bootloader unlocked?
Are you running stock ROM?
Are you comfortable using command line utilities such as adb and fastboot?
Welcome to XDA
In the future use a good case and always redundantly backup your data.
The chances of damage to the mobo is high.
High G impacts can internally damage chipsets and break solder joints including hard to inspect/repair BGA chipsets. This was a high G loading impact. A good case spreads out the G loading making severe impacts survivable.
Don't invest a lot of money in trying repair this device. Even if repaired future problems may occur with the original mobo. Replacing the frame, display and especially mobo are cost prohibitive.
Sorry but you're probably better writing it off.
@SMcC2 :
Is your bootloader unlocked?
No
Are you running stock ROM?
No
Are you comfortable using command line utilities such as adb and fastboot?
Not exactly, I tried installing adb command line and tried to see the devices connected using it after connecting the phone with usb cable. But I guess since the usb debugging was disabled it didn't worked. No experience with fastboot yet.
Any help in retrieving the data will be appreciated.
Thanks @blackhawk, my priority is the data retrieval, tried some softwares for days recovery but they all require usb debugging to be enabled and drive approvals on the phone which will not work as my screen is shattered and display is not working.
Buy another one and swap your board in is the only option is see. Then again, I have taken my OnePlus 6t apart many times. It's not the hardest phone to disassemble. But expect to pay about $100-200 and know the possiblity exists that your data is toast. Or find someone you are willing to trust to hook up your board, pull your data and wipe it. I should make that a service. Lol.
Edit: just for shiggles sake, how/where is it bent? A pic would definitely aide in determining the PITA level. I destroyed one OP6t I had in similar fashion, but had BL unlocked, USB debugging enabled, and custom TWRP recovery so the hardest part was paying the cost for a new one for my broken one.
gauravtomar said:
@SMcC2 :
Is your bootloader unlocked?
No
Are you running stock ROM?
No
Are you comfortable using command line utilities such as adb and fastboot?
Not exactly, I tried installing adb command line and tried to see the devices connected using it after connecting the phone with usb cable. But I guess since the usb debugging was disabled it didn't worked. No experience with fastboot yet.
Any help in retrieving the data will be appreciated.
Click to expand...
Click to collapse
Do you know what recovery you have installed?
gauravtomar said:
Thanks @blackhawk, my priority is the data retrieval, tried some softwares for days recovery but they all require usb debugging to be enabled and drive approvals on the phone which will not work as my screen is shattered and display is not working.
Click to expand...
Click to collapse
According to these articles:
Can We Enable USB Debugging using ADB Command?
Is there a way to enable USB debugging from fastboot?
It may be possible to enable ADB by modifying your build.prop and persistent_properties from recovery.
I tested and I was able to boot to recovery via physical buttons and then connect to TWRP command line and pull the files they say need to be edited.
*NOTE* Editing these files is dangerous and could cause the phone not to boot properly.
My process was:
Hold Vol+ Vol- and Power until you feel phone reboot to fastboot mode(short vibration here)
Vol -, Vol -, Power (reboot to Recovery)
Wait a minute or two...
Connect USB cable
adb shell
twrp decrypt *passcode*
*NOTE* If you're using a PIN number you can use the alphanumeric digits, if you're using a pattern you will need the details from the bottom of this link:
TWRP Commandline Guide
adb shell
mount /system_root
adb pull /system/build.prop
adb pull /data/property/persistent_properties
Open files in Notepad++, Make the edits, etc....