Develop Bugs

Any way to update FW without SD card or computer?

On Thursday the 29th my phone decided to take a dump on itself. Since then it has not been able to:
-Read any micro SD cards
-Connecting to computer doesn't fully allow USB connections, it detects something plugged in, but nothing else. No ADB, no RUU update, no Sync, etc.
-Cannot charge unless off
All of the above happened while trying to get onto the leaked Froyo. I cleared the cache and wiped the data then this happened.
I already ordered a replacement from Sprint (which I have yet to hear about), but I think I can fix this one by updating the OS.
Problem is that it downgraded me to a version earlier than the one that was on the phone when I first got it. Being on this version is causing a problem by not allowing HTC Update to even see any updates.
So basically I need to update without the use of USB or SD card.
Any help?

Have you tried this http://forum.xda-developers.com/showthread.php?t=695243

063_XOBX said:
Have you tried this http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
Thanks for the quick response.
That seems like it will be of a lot of help, but unfortunately adb cannot detect the phone.
EDIT:
It's also mildly amusing the way anytime someone also had this problem in that thread (the < waiting for device > in adb due to it not detecting the phone) people would just ignore it and continue on.

I have noticed that the computer can somewhat recognize the phone if it is in HBOOT USB mode. It is enough for the fastboot command to go through but return with a failed.

kbone213 said:
I have noticed that the computer can somewhat recognize the phone if it is in HBOOT USB mode. It is enough for the fastboot command to go through but return with a failed.
Click to expand...
Click to collapse
does adb work while it is in hboot? if so you should be able to push a pc36img.zip to it and fix it that way.

t3project said:
does adb work while it is in hboot? if so you should be able to push a pc36img.zip to it and fix it that way.
Click to expand...
Click to collapse
No, it only is able to recognize some things while in HBOOT. Example would be PDANet, which I used to be able to read the phone in the first place on Windows 7 x64, can see that the phone is connected. Adb still reads no devices though.

I'm pretty sure this happened when trying to wipe the phone to do a clean install. My assumption is that it wiped a file that was otherwise necessary to keep the SD card reader and USB port operational.
Is there any way that I can execute the "fastboot oem enableqxdm 0" somewhere on the phone without using adb?

Did another reset on it. Battery was low and turned the phone off without my knowledge. I turned it on to check if I had any messages or whatnot and got a message saying that the battery is low and that the current being given from the USB is not strong enough to charge it and to switch the cable.
What in the software would cause the current to be low?

[Q] adb hangs during push of large files

My HTC Incredible has 8GiB of internal storage. When I mount it to /emmc and try to push a large (>100MiB or so) file, the push will hang partway through -- no response, only Ctrl+C kills it. I know it has hung because I could check the status of the file via a separate 'adb shell', but the shell also starts returning nothing.
The weird thing is, if I push the large file in recovery mode, it always works completely fine.
If anyone has any suggestions, they'd be much appreciated.

Maybe adb cannot handle pushing a file that large while the phone is operating. It would be better to just copy it over while in recovery mode.
I Haz 3D!

That doesn't make sense though -- it would still count as a major flaw, the same as if your PC downloads stopped working while you played a game.
Even so, the phone is locked during the transfer, so another reason to think it might be more than that.

Yeah, adb has its flaws. I deal with the adb killing error. I never tried pushing a file over 10mb so I would have no idea. I do know the older root method for the HTC Evo 4G included pushing around 4 80mb files or so, so maybe reinstalling adb on your pc would work wonders.
I Haz 3D!

Found the solution -- I had been bitten by the kernel >2.6.35 slow SD card transfer bug. The transfer was timing out.
Using incredikernel with the fix apk, it's all golden now.

Old thread, I know, but thought I'd just post in case it helps someone. Same issue here with adb push. By pressing various random buttons, I got it to restart - it is Alt+C while in the CMD window on a PC that seems to get it going again.

Not sure if i had the same issue but i guess the command i gave was wrong.
adb push DCIM /sdcard/
Basically i wanted to push the DCIM folder inside the sdcard and the above command worked for me.
Make sure the slash is there infront and back of sdcard as I am pushing into the root of SDcard. I tried it without using the slash at the end and it froze like a minute. It took me some minute to figure it out what was wrong.
Just writing this if someone in the future has the same issue.
I am transferring 33GB photos from my Mac to OnePlus 6T so i dont think there is a lag for transferring file via ADB.

This comes up when I searched for adb push hanging so maybe my solution will help others. I could not push files larger than about 30 MB to my Android device. Eventually I found that the problem was cross-talk between my USB cable and other cables (power, HDMI) connected to my device. Simply moving the USB cable so it was always a couple inches away from the others solved my problem.

[Q] Digitizer Broken - Need to retrieve my Data

Hey all,
I'm in a pinch. I see some people on the other phone sections have had a similar problem, but never truly got it sorted out. My digitizer screen has a crack in it and no longer operates, The phone will power on, but I can't actually do anything with it. I'm trying to retrieve all of my media and data off of it to switch over on to my new Nexus. I'm trying this moborobo program but it doesn't seem to be working. It keeps trying to reinstall the drivers. If anyone could be of ANY help, Please I'm pretty desperate! Thank you.

Does the phone not respond when you connect it to your computer? (no MTP stuff, etc.) If you can still access that, then you should be in luck.
If you want to get more stuff off of your phone than just the basic files, perhaps you can do a backup through CWM recovery, since it's not touch-based, and then restore it onto the new phone.

chronostorm said:
Does the phone not respond when you connect it to your computer? (no MTP stuff, etc.) If you can still access that, then you should be in luck.
If you want to get more stuff off of your phone than just the basic files, perhaps you can do a backup through CWM recovery, since it's not touch-based, and then restore it onto the new phone.
Click to expand...
Click to collapse
The phone does show on my computer as "Galaxy Nexus" but when I try to access it, it is all completely blank. I tried another way useing the adb devices little trick on the windows cmd prompt but it isn't showing up as a device.

StealthCBR said:
The phone does show on my computer as "Galaxy Nexus" but when I try to access it, it is all completely blank. I tried another way useing the adb devices little trick on the windows cmd prompt but it isn't showing up as a device.
Click to expand...
Click to collapse
Sounds like you need drivers. Uninstall any drivers for the GNex on your computer, reboot, reinstall known working drivers. There are links in the stickies for the right ones for your device.
Sent from my Galaxy Nexus using xda premium

Did I "brick" or damage the device somehow?

Howdy y'all,
So I was rooting and flashing and when I tried to flash after successfully rooting the device, I went to wipe everything in TWRP and then flash another ROM. Well, something happened and it gave me an error saying it could not wipe (I think it was OTG something something, it's been 2 weeks now since I did this), and now it won't allow me to transfer ANYTHING from the computer to the device. It will not allow me to create folders, nothing. I have uninstalled the drivers, installed the drivers and tried SO many drivers. Anyone able to provide me a suggestion? The odd thing is on the device itself, I can create folders and everything, but when it connects, eventually, I can open the device from my computer, BUT when I attempt to create a folder, the PC gives me an error dialog saying that the device is not there anymore.
Any help would be greatly appreciated!
Thanks!

kassem277 said:
Howdy y'all,
So I was rooting and flashing and when I tried to flash after successfully rooting the device, I went to wipe everything in TWRP and then flash another ROM. Well, something happened and it gave me an error saying it could not wipe (I think it was OTG something something, it's been 2 weeks now since I did this), and now it won't allow me to transfer ANYTHING from the computer to the device. It will not allow me to create folders, nothing. I have uninstalled the drivers, installed the drivers and tried SO many drivers. Anyone able to provide me a suggestion? The odd thing is on the device itself, I can create folders and everything, but when it connects, eventually, I can open the device from my computer, BUT when I attempt to create a folder, the PC gives me an error dialog saying that the device is not there anymore.
Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Have you tried using ADB push to get a new rom onto the device? Also I'd do a permission repair
Edit: As a side note, I don't think it's possible that you did actual damage to your device. It's probably just the software that's messed up. If you want a sure way to fix it, try downloading and flashing the stock factory image.

Funzo22 said:
Have you tried using ADB push to get a new rom onto the device? Also I'd do a permission repair
Edit: As a side note, I don't think it's possible that you did actual damage to your device. It's probably just the software that's messed up. If you want a sure way to fix it, try downloading and flashing the stock factory image.
Click to expand...
Click to collapse
Thanks so much for the reply. I just finished doing a complete stock re-image of the original bootloader and OS, but I'm still getting the same error message. I'll attach an image below of the error I keep getting.
Any more suggestions?

kassem277 said:
Thanks so much for the reply. I just finished doing a complete stock re-image of the original bootloader and OS, but I'm still getting the same error message. I'll attach an image below of the error I keep getting.
Any more suggestions?
Click to expand...
Click to collapse
Is it possible for you to try with a different computer?

Funzo22 said:
Is it possible for you to try with a different computer?
Click to expand...
Click to collapse
Unfortunately no and not for a very long time. Shoot.

kassem277 said:
Thanks so much for the reply. I just finished doing a complete stock re-image of the original bootloader and OS, but I'm still getting the same error message. I'll attach an image below of the error I keep getting.
Any more suggestions?
Click to expand...
Click to collapse
Have you done a wipe data factory reset?
It wasn't clear from what you described.
Bootloadeer wouldn't help and neither would ROM as this problem has to do with /data

sfhub said:
Have you done a wipe data factory reset?
It wasn't clear from what you described.
Bootloadeer wouldn't help and neither would ROM as this problem has to do with /data
Click to expand...
Click to collapse
Sorry about the lack of clarity. I have wiped multiple times, cleared all caches, dalvik, etc. I have installed and uninstalled ALL devices from USBDeview pertinent to anything ADB or android related.

kassem277 said:
Sorry about the lack of clarity. I have wiped multiple times, cleared all caches, dalvik, etc. I have installed and uninstalled ALL devices from USBDeview pertinent to anything ADB or android related.
Click to expand...
Click to collapse
Have you rebooted your PC?
Have you reconfirmed you are using mtp rather than ptp?
Does your /sdcard show more directories than dcim and pictures when viewed in adb shell?

sfhub said:
Have you rebooted your PC?
Have you reconfirmed you are using mtp rather than ptp?
Does your /sdcard show more directories than dcim and pictures when viewed in adb shell?
Click to expand...
Click to collapse
I have rebooted multiple times
I am in debugging mode as well as in ptp mode and my sdcard shows that I do have many folders there, however in my computer it is only showing DCIM and pictures.

kassem277 said:
I am in debugging mode as well as in ptp mode and my sdcard shows that I do have many folders there, however in my computer it is only showing DCIM and pictures.
Click to expand...
Click to collapse
That's your problem right there. PTP mode is camera mode, so you only get access to a couple of directories. Switch to MTP mode (menu under Settings / Storage).

tni.andro said:
That's your problem right there. PTP mode is camera mode, so you only get access to a couple of directories. Switch to MTP mode (menu under Settings / Storage).
Click to expand...
Click to collapse
I've tried MTP mode before and I get nothing. In fact the computer doesn't recognize the tablet is there. It's odd b/c I have done EVERYTHING I can think of and read about to install drivers (multiple kinds, like PDA, android, RAW, etc) and uninstall drivers. It sounds like a driver issue but I don't think it is.
EDIT: ok so after switching to MTP mode on the tablet, I went to device manager and uninstalled the "portable ADP drivers" as some people were saying they had issues that were similar to mine (but not exactly) here (http://forum.xda-developers.com/showthread.php?t=2380978&page=1).
After doing so, I unplugged and re-plugged the N7 back in and had it re-install the drivers from the Google USB drivers that I downloaded onto my desktop. That allowed me to get it to work and access the internal SD card on the device. BUT, when I go back into the PTP mode (camera) mode, I still have the same issue where I cannot creat subdirectories, transfer anything to the device AND I cannot see any directories except for DCIM and pictures. Really weird. Both modes obviously worked before I rooted it. Now that I have unrooted and gone back to bare bone stock I am still not getting it to work.

kassem277 said:
BUT, when I go back into the PTP mode (camera) mode, I still have the same issue where I cannot creat subdirectories, transfer anything to the device AND I cannot see any directories except for DCIM and pictures. Really weird. Both modes obviously worked before I rooted it. Now that I have unrooted and gone back to bare bone stock I am still not getting it to work.
Click to expand...
Click to collapse
That is how ptp mode is supposed to work.
That is why people prefer mtp mode.

kassem277 said:
BUT, when I go back into the PTP mode (camera) mode, I still have the same issue where I cannot creat subdirectories, transfer anything to the device AND I cannot see any directories except for DCIM and pictures.
Click to expand...
Click to collapse
Like I said, that's what you get in PTP mode. You are able to write to those 2 directories though (not the root directory).
Really weird. Both modes obviously worked before I rooted it. Now that I have unrooted and gone back to bare bone stock I am still not getting it to work.
Click to expand...
Click to collapse
No way. PTP mode is restricted on purpose. Here is the commit:
https://android.googlesource.com/pl...er/+/1e950b8090d90bbf92e528a974ecb8c5c48dff84

Thanks guys. I appreciate all the continued help and patience. Now that I went back and thought about it, I was only transferring images WHEN it was working before. It is all good now that my silly drivers were all sorted out. Really odd how the drivers just took a crap on me like that. Weird. All is well now though and I can get back to studying my PDF's for school.
Thanks again y'all!

Thanks guys. I appreciate all the continued help and patience. Now that I went back and thought about it, I was only transferring images WHEN it was working before. It is all good now that my silly drivers were all sorted out. Really odd how the drivers just took a crap on me like that. Weird. All is well now though and I can get back to studying my PDF's for school.
Thanks again y'all!

Damaged phone-backup data with adb

Sad day today.. dropped my S6 Edge and the result was a shattered front screen. I can't use any of the touch function, but the phone does appear to work partially ( I still get email alerts on my connect android wear).
I wanted to perform an adb backup , I'm able to connect the phone to my computer, however, when I give the :
adb backup -all -f C:\backup.ab command, it wants me to unlock the device and confirm the backup operation.
I tried unlocking with my fingerprint but it's not working. I can't see anything on screen, other than a flashing light.
Any other suggestions how to backup/ transfer data from phone? sadly kies no longer works which would have worked...
Thanks for all help in advance.

That sucks big time. Turn the phone off, put the phone in download mode and issue the commands that way. This will by pass the phone asking you to unlock it.. See if that works for you.

grneyez said:
That sucks big time. Turn the phone off, put the phone in download mode and issue the commands that way. This will by pass the phone asking you to unlock it.. See if that works for you.
Click to expand...
Click to collapse
I just tried that. When I give the adb backup command screen reads: "waiting for adb Mode" and does not seem to progress. when I loaded odin it does seem to recognize phone ready to go so the connection is live.
any other suggestions?

Are you rooted? If so, do you have developer options checked?

S6 edges is not rooted. Developers options was enabled previously since I had used Helium for date transfer from my older S5 to edge.

Not sure why you can't ADB in download mode. Wish I could of been more helpful.. Maybe someone else will be able to help.

grneyez said:
Not sure why you can't ADB in download mode. Wish I could of been more helpful.. Maybe someone else will be able to help.
Click to expand...
Click to collapse
So I rooted my phone even though the screen is cracked. I tried everything I could think of, not much to lose anymore.
I can still access the adb , shell, but still having same issue.
I tried the pull command but I get an error after screen starts creating a list " No such file or directory"
Any more suggestions?