So as the title says, I recently lost control of my phone and in a panic full wiped everything. I figured this wouldn't be such a big problem as the hardware was fine, however, I'm now realizing that without developer mode and usb debugging enabled I can't do ANYTHING. I've tried to reflash stock via adb but the device isn't recognized, likely for the above reasons. Under normal circumstances I would just plug my phone into my computer and use MTP to move a rom over, however since the default mode is USB charging and I don't have have an OS installed, it seems I can't change that.
I've been told that it's essentially impossible to brick a nexus nowadays, but I feel like I somehow managed and for the silliest reasons. . Someone please help.
Edit: I should mention that I still have access to TWRP somehow.
cri7ica1 said:
So as the title says, I recently lost control of my phone and in a panic full wiped everything. I figured this wouldn't be such a big problem as the hardware was fine, however, I'm now realizing that without developer mode and usb debugging enabled I can't do ANYTHING. I've tried to reflash stock via adb but the device isn't recognized, likely for the above reasons. Under normal circumstances I would just plug my phone into my computer and use MTP to move a rom over, however since the default mode is USB charging and I don't have have an OS installed, it seems I can't change that.
I've been told that it's essentially impossible to brick a nexus nowadays, but I feel like I somehow managed and for the silliest reasons. . Someone please help.
Edit: I should mention that I still have access to TWRP somehow.
Click to expand...
Click to collapse
While in TWRP, use ADB Sideload and install the latest OTA zip from Google:
https://developers.google.com/android/nexus/images?hl=en
Edit: How did you reflash stock? Because you should be able to do the above, ADB push, or drag and drop via TWRP. You may have to mount the file system before doing so.
Sent from my Nexus 5X using Tapatalk
cri7ica1 said:
So as the title says, I recently lost control of my phone and in a panic full wiped everything. I figured this wouldn't be such a big problem as the hardware was fine, however, I'm now realizing that without developer mode and usb debugging enabled I can't do ANYTHING. I've tried to reflash stock via adb but the device isn't recognized, likely for the above reasons. Under normal circumstances I would just plug my phone into my computer and use MTP to move a rom over, however since the default mode is USB charging and I don't have have an OS installed, it seems I can't change that.
I've been told that it's essentially impossible to brick a nexus nowadays, but I feel like I somehow managed and for the silliest reasons. . Someone please help.
Edit: I should mention that I still have access to TWRP somehow.
Click to expand...
Click to collapse
USB OTG pre-populated with a ROM maybe?
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 am having problems with my N7 not connecting to my desktop. I can get into bootloader and recovery but I can not mount USB to add a rom. I'm SOL as of right now and have no clue what to do...
uitfenc families
makross said:
I am having problems with my N7 not connecting to my desktop. I can get into bootloader and recovery but I can not mount USB to add a rom. I'm SOL as of right now and have no clue what to do...
Click to expand...
Click to collapse
Could it be related to this issue:
http://forum.xda-developers.com/showthread.php?t=1821536
If you have plugged your Nexus 7 on a car charger, the usb might be dead and only be used for charging (and so unable to transfer new ROM data).
charging is fine...is it possible that I did not enable usb debugging before i wiped to factory reset that it would prevent me from connecting???
alright heres alil update i tried using WUGS toolkit and trying to unroot everything was going fine until it cannot find the flashstock.bat...now im back to square one. i cant find the flashstock.bat anywhere
I was having the same problem. It would see the camera mode, but not the mtp. I read in another thread to turn off debugging in settings. What do you know. It worked! Computer sees the tablet now just fine.:victory:
I'm not sure when this problem first appeared. For whatever reason, my phone doesn't show up at all when connected to either of my two PCs. It must have when I first rooted the phone (to load ChainSU) but I'm not sure if the problem is recent or occurred immediately thereafter.
USB debugging is disabled. When I plug my phone into a computer, it attempts to install the MTP Driver and fails. When I uninstall my device, it disappears and I'm unable to manually install the driver's I've downloaded from other threads. When I load into the Bootloader, my device is recognized by Fastboot.
I'm hesitant to factory reset as this will leave me unable to root if the problem persists, which is important to me as I can get rid of the yellow tint on this screen.
Any thoughts?
Edit: $10 via Paypal for anyone who successfully helps me to a solution!
Are you definitely sure usb debugging is disabled? The phone should install as a portable device on your pc. Also ensure to enter your password onto your phone when connected otherwise the phone will not show up its contents.
Make sure for windows media player to be updated to the latest, for the windows mtp driver.
duraeas said:
I'm not sure when this problem first appeared. For whatever reason, my phone doesn't show up at all when connected to either of my two PCs. It must have when I first rooted the phone (to load ChainSU) but I'm not sure if the problem is recent or occurred immediately thereafter.
USB debugging is disabled. When I plug my phone into a computer, it attempts to install the MTP Driver and fails. When I uninstall my device, it disappears and I'm unable to manually install the driver's I've downloaded from other threads. When I load into the Bootloader, my device is recognized by Fastboot.
I'm hesitant to factory reset as this will leave me unable to root if the problem persists, which is important to me as I can get rid of the yellow tint on this screen.
Any thoughts?
Edit: $10 via Paypal for anyone who successfully helps me to a solution!
Click to expand...
Click to collapse
There are a few things you can try. Have you tried uninstalling the drivers completely then reinstalling from the toolkit? In the past, I've had issues where the phone wouldn't be accessible in some way on one computer but would be fine on another, so maybe try a different computer to try to narrow down the problem as to whether it's an issue with the phone or the computer? Also, this may sound a bit ridiculous, but simply switching USB cables and / or ports has fixed detection issues for me in the past as well--something to consider.
Sent via Morse code from my Nexus 4
Remove any existing drivers (while phone is connected), do the same for other android devices if you have any, then reboot and install Universal Naked Drivers. Have always had success with this driver pack.
Rizy7 said:
Are you definitely sure usb debugging is disabled? The phone should install as a portable device on your pc. Also ensure to enter your password onto your phone when connected otherwise the phone will not show up its contents.
Click to expand...
Click to collapse
100% sure on both counts.
I have this same issue with my rooted nexus 4, I've tried 3 different computers and several cables and it never connects to the PC and only charges the phone. It doesn't even give me option to choose media files.
I've had this issue before, my Nexus/Computer was acting in complete stupidity. When connecting the phone to your computer you will see a notification saying "Connected as a media device" on your phone, just touch it, and change it to "Camera (PTP)". It might access the camera for you, but It actually accessed the storage for me.
YeledKaki said:
I've had this issue before, my Nexus/Computer was acting in complete stupidity. When connecting the phone to your computer you will see a notification saying "Connected as a media device" on your phone, just touch it, and change it to "Camera (PTP)". It might access the camera for you, but It actually accessed the storage for me.
Click to expand...
Click to collapse
Thats not the problem, it doesn't give any option. It doesn't show up on the computer at all and only charges. It's the same for every computer.
yuriorkis said:
I have this same issue with my rooted nexus 4, I've tried 3 different computers and several cables and it never connects to the PC and only charges the phone. It doesn't even give me option to choose media files.
Click to expand...
Click to collapse
I'm thinking we've screwed something up with the phone's side of the MTP protocol - mine is totally independent of the cord/computer used. All the correct drivers installed.
Have you tried Factory Resetting? I'm really hoping this is a workable option.
If you have a recovery back up the current Rom and flash stock and see if it's working
Sent from my KFTT using xda premium
if the phone is locked with a pin/password/pattern unlock it.
I had same problem on my pc yesterday. Even if the drivers installer showed up that installation was successful, somehow for a mtp mode system was using some other Microsoft driver. Correct one was only used in ptp mode. So when I connected n4 in mtp mode storage wasn't available, when I switched to ptp mode everything was fine. Turn on your usb debug, switch on mtp and connect. Go to device manager in system, find your nexus there and rmb on it and manually reinstall driver. After this my n4 is visible in system in mtp mode again.
Sent from my Nexus 7 using Tapatalk HD
my screen is cracked and phone is useless now (replacement coming tomorrow) can i connect it and wipe it back to factory before i have to send it out?
K0v4L said:
I had same problem on my pc yesterday. Even if the drivers installer showed up that installation was successful, somehow for a mtp mode system was using some other Microsoft driver. Correct one was only used in ptp mode. So when I connected n4 in mtp mode storage wasn't available, when I switched to ptp mode everything was fine. Turn on your usb debug, switch on mtp and connect. Go to device manager in system, find your nexus there and rmb on it and manually reinstall driver. After this my n4 is visible in system in mtp mode again.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
The problem is that even if I switch between MTP and PTP it still does nothing, I have tried multiple cables, computers and have reflashed the ROM and wiped the device but it still does not connect with the PC. This is frustrating.
yuriorkis said:
The problem is that even if I switch between MTP and PTP it still does nothing, I have tried multiple cables, computers and have reflashed the ROM and wiped the device but it still does not connect with the PC. This is frustrating.
Click to expand...
Click to collapse
Is yours able to connect during Bootloader/Recovery? Fastboot/ADB have no trouble recognizing my device.
It's really odd that if these things work, meaning your USB connection is fine, replacing the all of software fixed nothing... unless MTP occurs at a much lower level of the OS (maybe kernel is corrupted?)
I've got a similar problem that others have posted - PCs not detecting my N4. I got it last Friday (2/1) from Google and after the registering process and updating to 4.2.1, I connected it to my Win7 laptop and it showed on the PC as a drive. But since I couldn't copy/paste Office docs to that drive and had to do that through Dropbox, I didn't bother trying to reconnect until Monday, at which time the PC didn't detect it. Neither will one other Win7 nor two XP (both with WMP10) PCs. Have tried multiple cables, all of which work with other Android devices (pre 3.0). I've seen several suggestions on this and other threads, but one major issue I'm having is that some of the fixes require enabling USB Debugging. For the life of me I can't find that option in the N4's Settings. Unlike my other phones, there is no Applications subcategory under Settings on my N4 (4.2.1, Build JOP40D). Can anyone help me find that option? TIA.
Edit - Found answer. Click on Build in About Phone setting 7 times. That activated Developer options. Now to try the fixes which require USB Debugging mode turned on.
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
DTTD said:
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
Click to expand...
Click to collapse
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Fallon9111 said:
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for providing more information on this. I have done a Factory Reset via Settings and also via Recovery, but still not available.
I think I'm making progress with adb via Ubuntu over USB, but USB Debugging still gives the Epic crash and still will not charge while On, which is more just annoying than anything else.
Asus/Google Support are saying it is a physical pin issue, but that doesn't explain why USB Debugging is failing. Does anyone know where the USB files are contained? I'm wondering if I've messed up at the Kernel level. Any thoughts?
About my Nexus - More Info
I forgot that I should provide more information about what I'm running:
Phone: Nexus 7
Android Version: 4.2.2
Kernel version: 3.1.10-g05b777c
Build number: JDQ39
Prior to issue also had:
Recovery: TWRP
ROM: Stock JDQ39
MultiROM: Yes
UPDATE
So after more work on my Ubuntu we have found more information and seem to have narrowed down the issue! :fingers-crossed:
I have been able to flash via Fastboot just fine, which has thus allowed me to get TWRP installed and now I'm back rooted. I still cannot adb via USB though. We've double checked with multiple Nexus 7's of the same type, which allow command: adb devices and their devices will show, while it does not for my device. (Side note: my version of Ubuntu does not "see" the adb command in its pwd so... But tests have been done on other machines and worked...)
So after sifting down to adb issues, we found that in /data/property I'm missing persist.sys.root_access and persist.sys.usb.config ... But creation of persist.sys.usb.config didn't do anything...
I dropped my N4 on the ground this past weekend and it now has both a shattered front and back glass. The digitizer does not work so I can't use the touchscreen at all.
Here's what I can share about the status of the phone:
It is still on, I can see the screen, and is fully charged receiving messages.
The power button and two volume buttons work.
The phone's storage is encrypted with the stock android encryption.
I have a 4-digit PIN enabled on the lock screen.
The phone did not have USB debugging enabled when this occurred.
I've tried to mount it to a computer to get the files, but nothing shows up as I believe I need to unlock it with the PIN before it will mount.
I can install apps remotely from the Play store.
I have the Sophos mobile app installed and configured but I don't believe there are any commands to UNLOCK the device, only to lock it and wipe it.
Honestly, I just want my data off of the phone and would rather not replace the screen and continue using it. I love the phone but it is way too fragile. Is there any way to transfer my data? I looked into connecting a mouse to the usb and using that to enter the PIN, but the N4 does not support mice. Since USB debugging was not turned on, I can't connect via ADB. Is there some sort of app I can remotely install from the play store to turn on USB debugging? Is there some sort of app I can remotely install to remotely unlock the device with my 4-digit PIN? If I let it die and then try to boot into recovery, will ADB work then? If so, how would I get the data off of the device if it is encrypted? Any guidance would be greatly appreciated.
Thanks in advance!
Is it running a custom recovery?
If yes, just go into recovery and do a nandroid, boot back into android and copy the backup.
If no, there's a thread somewhere with instructions on how to unlock your bootloader WITHOUT wiping your phone.
Unfortunately this is the only android phone I've ever owned that I haven't touched and left completely stock... No custom recovery, no custom ROM. I'll try to look for the instructions on how to unlock the bootloader without wiping the phone, but if I do a nandroid and boot back into android how will I transfer the data? I'd be stuck at the screen where I have to type in my encryption password, and even if I got past that I still can't mount the device in Windows to transfer the data?
Anyone?
Exousia said:
Unfortunately this is the only android phone I've ever owned that I haven't touched and left completely stock... No custom recovery, no custom ROM. I'll try to look for the instructions on how to unlock the bootloader without wiping the phone, but if I do a nandroid and boot back into android how will I transfer the data? I'd be stuck at the screen where I have to type in my encryption password, and even if I got past that I still can't mount the device in Windows to transfer the data?
Click to expand...
Click to collapse
The only way I can think is flash an advanced version of cwm (if it doesn't already have one) that has a file manager and make a backup, and copy the recovery to a location on the SD. Then mount USB storage and copy everything over.
Edit: actually, you could mount USB storage in cwm to copy files over, then make a backup through adb on to your computer, there's some tutorials on how to do that
Sent from my Nexus 4 using xda premium
do you have adb installed? cant you copy the files in bootloader mode to the computer? havent tried yet, and im on my work laptop right now, cant try it.
zakoo2 said:
do you have adb installed? cant you copy the files in bootloader mode to the computer? havent tried yet, and im on my work laptop right now, cant try it.
Click to expand...
Click to collapse
as far as I know no. In bootloader mode is only fastboot, not adb
Sent from Halo.
what i dont understand is how you cannot connect the phone with mtp... that should work without debugging.
EDIT: sorry, youre right, when the device is encrypted, you have to unlock it before mounting.
looks like you made pretty damn sure there is no way for you (or anyone else) to get access to the data on your device :/
although i dont know about unlocking without wiping. maybe that could work.
sent from my Nexus 4...
Google search a program called Motorobo; equivalent to what service providers use.
Sent from a neXus device