Database Users

Bricked Verizon apache

Need link to info regarding a possible bricked Verizon xv6700.
Phone receives power via USB port....but phone will not come on.
Any way to repair??
Coworker bought from a 2nd party.

Is it showing "USB" very fiently on the screen? If so you may need to do the Putty usb port change to break out of boot loader....

ok,
I was trying to upgrade my ROM, which I've done like 5 or six times before with the same phone, but now when upgrading my ROM, it sits in Bootloader and I can not get out of it.
What is "the Putty usb port change" trick? I can't find any info on it.

De-Bricking a Bootloaded Apache
The program is called mtty.exe (they guy who gave me a copy called it Putty... don't know why)
Anywho
http://forum.xda-developers.com/showthread.php?t=304408 Helmi C has a nice walk through in the upgrade section
1. Install mtty
2. Connect your device
3. open mtty
4. select USB as your connection
This will open a window that looks like a telnet console
5. type "set 14 0"
this modifies the speed and timeout I think....
6. flash your device again
From this point forward it is recommended you continue to use the same USB port for all flashing operations.
Hope this helps.

Samsung SGH-i607 flashed with SGH-i600 ROM - Does anybody know how to flash it back?

I have flashed my i607 with the i600 new ROM and now I can't flash the phone back.
The phone works because I haven't flashed this part, however had flashed the PDA and have no camera anymore, no vibrator, but at least a working O/S.
I have tried the following:
a ) Purchased the D820 cable. I can see the phone connected using Tera Term in COM1, however is not seen by the WCE downloader as this is looking at USB ports.
b ) I have tried installing the modem drivers time and again, and tried to connect ActiveSync in COM1 according to these instructions:
(1) Use a Samsung D820 cable with Serial Port and plug into your i60x
(2) Connect the cable to your PC's serial port (probably COM1)
(3) Install the Samsung Blackjack Modem Driver
(4) Uncheck the "Allow USB connections" in Active Sync option and select COM1 in "Allow connections in one of the followings"
(5) Let Active Sync to search for the i60x and wait for "Connected"
(6) Run the i600 firmware update program as usual.
NO results. ActiveSync does not connect.
c ) Tried Corona Downloader ver 3.2 for Samsung SGH-D500, it connects to the phone, but vendor ID sent is 0x44 and the phone responds 0x52, aborting further exchanges. I also tried OneNAND downloaders ver 1.4, 1.7 and 1.8 with similar results. I know these flashers may not work on my phone, however gave me an idea some exchange was taking place...
d ) I tried to load the bootloader eboot.nbo in root of the SD card, however i don't know if there should be a key combination to boot from SD card or if there is one other trick nor what name the file should have. Any ideas here?
e ) I have made dumps prior this mishap of all 4 raw partitions in the phone. Is it there a way to write a partition using a utility that I can place in the SD card? Is it there available a SD flasher that may run from the phone?
f ) Is it there a way to modify the WCE downloader to work on COM1 instead of USB?
g ) Is it there a way to modify the device driver to accept the phone as it is now? Apparently the phone device driver messages windows with a device malfunction and Device not recognized. Is it there any way to bypass this?
h ) I even tried to use a Serial-USB bridge and WCE downloader. No results either.
If you have any ideas, please respond to this thread. Any input will be deeply appreciated. Thank-you in advance.

Hi,
Is your Samsung device a derivative of a HTC product or have you posted in the wrong place?
WB

I don't think so
I don't think the Samsung is a derivative of the HTC, nor I want to enter a discussion of territorialism, now with all due respect I though this forum was a place to openly exchange knowledge on xda devices, and yes, as this topic has to do with hacking, and yes, because I have seen postings on Samsung i60x and i71x devices, is why I have posted here. Do you have any insight about the subject matter?
Thank-you

[Q] My PC is not recognising samsung focus...:(:(

Device driver failed... Error Code 28... Please help

cj.arvind said:
Device driver failed... Error Code 28... Please help
Click to expand...
Click to collapse
What operating system are you using? Do you have the latest samsung pc drivers installed?

Is this when in "download mode"?

this happened to me before. Go and buy a new charger and see if that works. Also have all of your apps closed maybe that will work

Not recognised...
M using Windows 7 64-bit.. And it got detected after selecting zune sync... How ever the PC suit for focus is not available and if I select USB + tethering , the phone will not get detected I wanna user tethering.. Plz help..
PS:this phone is AT&T unlocked.. let me if its possible or not

I had got Samsung Focus ATT unlocked one and my windows 7 64-bit is not recognizing it. I had tried all the options suggested in the wp7 forums, but of no luck.
I want to connect to Zune and upgrade to Mango, but due to this, am not able to do anything.
Friends, please help me out here, and really appreciate all your inputs.

tech4pk said:
I had got Samsung Focus ATT unlocked one and my windows 7 64-bit is not recognizing it. I had tried all the options suggested in the wp7 forums, but of no luck.
I want to connect to Zune and upgrade to Mango, but due to this, am not able to do anything.
Friends, please help me out here, and really appreciate all your inputs.
Click to expand...
Click to collapse
Have you tried on another computer?

no, I have not tried in another computer. Will try as soon as I get to work.

tech4pk said:
no, I have not tried in another computer. Will try as soon as I get to work.
Click to expand...
Click to collapse
Use the instructions below and select Zune.. That should work.
Dial ##634#
In the diagnostics mode that opens up, enter *#7284# in the phone dialer.

vivakh said:
What operating system are you using? Do you have the latest samsung pc drivers installed?
Click to expand...
Click to collapse
The drivers aren't available. I have to use Zune to make it work.!! May thats how the Windows phones are designed, im guessing...

had to to do go to diagnostics on my wifes focus the other day , simple fix:
*#7284#
Micro USB Test
USB Path Control:
Zune Sync
Modem,tethered Call
Modem,USB Diag.
she was in Modem USB Diag , had to check Zune Sync , reboot works fime and synced immediately with Zune!

Vintage144 said:
had to to do go to diagnostics on my wifes focus the other day , simple fix:
*#7284#
Micro USB Test
USB Path Control:
Zune Sync
Modem,tethered Call
Modem,USB Diag.
she was in Modem USB Diag , had to check Zune Sync , reboot works fime and synced immediately with Zune!
Click to expand...
Click to collapse
I changed and tried 3 of them but it didnt work.

PC cant recognize
I have been struggling with this issue as well.
Simple solution i found (and after reading about million posts on web as well)... ORIGINAL CABLE seems to solve the issue. I saw it posted even on one Korean forum. Seems simple enough, use original data cable that came with phone and that seems to be it. wierd

Totally agreeing with PP
PP is correct in suggesting the original data cable being used.
I had the same issue, the pc would not recognize the phone. The fix for me was to connect to the usb ports on the back of my pc. They were the only ones that let the phone connect to zune.

Sondie said:
PP is correct in suggesting the original data cable being used.
I had the same issue, the pc would not recognize the phone. The fix for me was to connect to the usb ports on the back of my pc. They were the only ones that let the phone connect to zune.
Click to expand...
Click to collapse
Btw, for these issues with USB only working on the back of the comp the culprit is either the motherboard (drivers or other) or the PSU (not enough power).

Enderpsp could be right.... Mine was the USB port, I had to plug it in a different port and it started working... Just keep trying, make sure you don't have any USB options about power management in your computer's bios
Sent from my SGH-i917 using XDA Windows Phone 7 App

Has anyone found a solution to the dead PC/USB connection?

Running CM 10.1.3, I can no longer connect the phone to my PC (Win 7, x64). There is no acknowledgement from either the phone or the PC that a data connection has been made (other than that it was charging). I used to be able to connect okay, but now it's not working.
Searching around, this is apparently a common issue with the S4. I've made various attempts at dealing with this, including re-installing the Samsung drivers, with no success. I don't even know if it's specific to CM, or the phone's hardware/firmware.
Has anyone found a solution for this problem?

Hope this works for u. I had an issue connecting my Galaxy S4 as well. Here's the solution I found.
Click the phone icon to access the dial pad and type *#0808#
A menu will appear once the last character is entered.
Choose : AP on upper section and for USB Setting choose MTP.
Reboot the device. Good luck.
Credits to sucah for this solution.

willieamm said:
Hope this works for u. I had an issue connecting my Galaxy S4 as well. Here's the solution I found.
Click the phone icon to access the dial pad and type *#0808#
A menu will appear once the last character is entered.
Choose : AP on upper section and for USB Setting choose MTP.
Reboot the device. Good luck.
Credits to sucah for this solution.
Click to expand...
Click to collapse
I can't get USSD codes to work. I get an error "Connection problem or invalid MMI code". Adding a comma at the end doesn't fix it. As soon as I can get past this problem, I'll give that solution a try. Thanks!

Haphim said:
Running CM 10.1.3, I can no longer connect the phone to my PC (Win 7, x64). There is no acknowledgement from either the phone or the PC that a data connection has been made (other than that it was charging). I used to be able to connect okay, but now it's not working.
Searching around, this is apparently a common issue with the S4. I've made various attempts at dealing with this, including re-installing the Samsung drivers, with no success. I don't even know if it's specific to CM, or the phone's hardware/firmware.
Has anyone found a solution for this problem?
Click to expand...
Click to collapse
My computer has USB 3.0 equipped with fast charge, ASUS. The app updated and screwed my usb connections to any chargeable device. I wound up having to remove the app and then reinstall the drivers. Don't know if that might be an issue with your computer but it's with a check.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

I discovered that those USSD codes are Samsung specific, which means that they only work on the stock ROM. In CM, they are invalid.
Any other ideas?

[APP][TOOL] ADB-Over-WiFi-Helper

Free for XDA members and as a thank you for all the information, tools and roms XDA Developers has provided over the years here is something I created that makes it easy to connect adb over tcpip to multiple Android devices. Get rid of the wires!
One click to switch adb on all usb connected devices to tcpip.
One click to switch adb on all tcpip connected device back to usb.
Auto discovery of the devices listening on tcpip.
The application consists of two parts. "Helper.jar" to run on the pc and "Helper.apk" for the device.
View attachment 2455389Helper.jar
- Installs the Helper.apk on the device.
- Attempts to switch adb on the device to use tcpip.
- Sends broadcast messages to look for devices on the network.
- Initiates an adb connection over tcp to any ip that responds to the broadcast.
- Provides a button to switch all usb devices to tcpip.
- Provides a button to switch all tcpip devices to usb which also uninstalls the helper.apk file, leaving no "junk" on the device.
{
"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"
}
On the device, Helper.apk
- Turns on WiFi if not already on.
- Checks and shows if the adb port was indeed opened.
- Listens and responds to udp broadcasts from Helper.jar.
Some android devices will work without root but if you get a red message from the helper on the device, you will need to root it to enable adb in tcpip mode. The rooted method to set adb to use tcpip is used in case the device is rooted.
If you like the tool and want to contribute, please feel free to buy the app on the Play store. The attachment contains exactly the same files for free.
Feedback is welcome and I hope someone finds this useful!
Adrian
UPDATE!!
A new tool I am calling "ADB Master" that includes all functionality of ADB-Over-WiFi-Helper plus a lot more is now also available for free to XDA users.
Get the new ADB Master here: http://forum.xda-developers.com/showthread.php?t=2707556
It is highly recommended to use the new download rather than the file attached to this post!

Thanks for this. Much appreciated. :good:

If you need an icon or Banner created let me know.
Nice work!

so now if i broke my USB port i can lock bootloader with this?Yes?
Nexus 4

ADB over wireless
I think this will be a very useful application for anybody requiring to make changes when on the road, or away from one's main computer.
Running ADB over WiFi should be a great addition to anybody's 'tool kit', I for one, look forward to making use of this application.
Many thanks for bringing this to all of us at XDA.
Thank you!

this apps is awesome make adb over wifi easier

Nice
extremewing said:
Free for XDA members and as a thank you for all the information, tools and roms XDA Developers has provided over the years here is something I created that makes it easy to connect adb over tcpip to multiple Android devices. Get rid of the wires!
One click to switch adb on all usb connected devices to tcpip.
One click to switch adb on all tcpip connected device back to usb.
Auto discovery of the devices listening on tcpip.
The application consists of two parts. "Helper.jar" to run on the pc and "Helper.apk" for the device.
View attachment 2455389Helper.jar
- Installs the Helper.apk on the device.
- Attempts to switch adb on the device to use tcpip.
- Sends broadcast messages to look for devices on the network.
- Initiates an adb connection over tcp to any ip that responds to the broadcast.
- Provides a button to switch all usb devices to tcpip.
- Provides a button to switch all tcpip devices to usb which also uninstalls the helper.apk file, leaving no "junk" on the device.
View attachment 2455388On the device, Helper.apk
- Checks and shows if the adb port was indeed opened
- Listens and responds to udp broadcasts from Helper.jar.
Some android devices will work without root but if you get a red message from the helper on the device, you will need to root it to enable adb in tcpip mode. The rooted method to set adb to use tcpip is used in case the device is rooted.
If you like the tool and want to contribute, please feel free to buy the app on the Play store. The attachment contains exactly the same files for free.
Feedback is welcome and I hope someone finds this useful!
Adrian
Click to expand...
Click to collapse
Nice tool Bro :good:

Thank you for the Christmas gift. I'm on HTC DNA and I am rooted but I get the red port closed message about root required.
No request for root occurs in supersu from this app.

rayjr13 said:
Thank you for the Christmas gift. I'm on HTC DNA and I am rooted but I get the red port closed message about root required.
No request for root occurs in supersu from this app.
Click to expand...
Click to collapse
Same issue here, on my rooted Xperia J. No entry regarding this apk's request for root is found in Super-SU's logs, whatsoever.

Wow, thanks for all the comments!
The helper on the device does not use or need su and ONLY does the following:
1) Checks if the adb tcp port was indeed opened on the device (by creating a tcp connection attempt to it)
2) Listens and then responds to a udp broadcast from the java app.
In future, it could do more.
All the work is done over the USB cable (or WiFi to switch back) using adb from the java app.
In essence, the java app executes the following abd commands to each device (both the "rooted" and non rooted methods are attempted each time):
To turn ON tcpip mode:
adb -s <devicename> tcpip 5555
adb -s <devicename> shell su -c 'setprop service.adb.tcp.port 5555'
To turn OFF tcpip mode:
adb -s <devicename> usb
adb -s <devicename> shell su -c 'setprop service.adb.tcp.port -1'
Please explain a bit more what is happening when the red message appears?
Is the device connected over USB and appearing in the left hand list on the java app?
Perhaps post the output from the java app when you press Switch to WiFi.

darkmatthew said:
so now if i broke my USB port i can lock bootloader with this?Yes?
Nexus 4
Click to expand...
Click to collapse
This app needs you to be able to first connect the USB and is intended to make it easier to work with lots of devices at the same time. For a rooted device without USB / damaged USB, any ADB to WiFi switching app on the play store should work to get adb onto WiFi and then, yes, you should be able to execute your required adb commands.

Thank you in advance for this very important tool!
extremewing said:
This app needs you to be able to first connect the USB and is intended to make it easier to work with lots of devices at the same time. For a rooted device without USB / damaged USB, any ADB to WiFi switching app on the play store should work to get adb onto WiFi and then, yes, you should be able to execute your required adb commands.
Click to expand...
Click to collapse
I have a HTC One, 4.3 Sense 5.5, ( 3.62.771.3 ), and need to reset it back to stock. My USB port doesn't function when the phone is on.
(Works OK in fastboot mode) - and I need to be S-off, then S-on again (locked, remove tampared via revone, moonshine,
or rumrunner) but all those require USB adb. and I can't do that.
So I'll try this and let you know how it goes.

spereree said:
I have a HTC One, 4.3 Sense 5.5, ( 3.62.771.3 ), and need to reset it back to stock. My USB port doesn't function when the phone is on.
(Works OK in fastboot mode) - and I need to be S-off, then S-on again (locked, remove tampared via revone, moonshine,
or rumrunner) but all those require USB adb. and I can't do that.
So I'll try this and let you know how it goes.
Click to expand...
Click to collapse
Please note, this app also requires USB ADB to start off.

Tried it...
extremewing said:
Please note, this app also requires USB ADB to start off.
Click to expand...
Click to collapse
OK, so I've tried it, and it seems like it can only pick up an ongoing ADB WiFi connection but I'm sure I'm doing something wrong.
Remember; I can't use USB debugging coz my usb doesn't work when the phone is on. so USB debugging is off, and there is no point using it. I'm using this as an alternative to restore back 100%.
(1) I pushed the apk file to the phone, using "WiFi File explorer pro"
(2) I installed it using "APK installer"
(3) Ran Helper.jar
(4) Opened an already installed WiFi ADB app on my phone, and established a connection (granted SU first)
(5) ran your app, "ADB over wifi helper" - it picked up the connection (showed green, " ... listening on port 5555 ... ", etc)
Back to the Helper.jar, all it does is saying "Searching - Hello to 255.255.255.255" "Timeout"
I was assuming it would have automatically connected it for me (say running a command like "adb connect ip.address:5555" )
or am I getting this wrong?
I kept the path to my android sdk
****Also, I used the mini sdk (It's quite popular, so I'm assuming most users will have this) and I'm missing the "platform-tools" folder. I just have fastboot and adb,exe and some dll files. So, can you provide a link we could get the required "platform-tools" folder alone? (zipped) ****
However, when I connect manually via command prompt, "adb connect ip.address:5555" the Helper.jar automatically detects it, and the option to Switch devices to USB appears (which I will not use, personally)
But the "Searching" cycle still continues.
Also, what is the use of the large text entry form below the "Searching" indication?
Again, thanks for this tool!!!
P.S. imagine a user trying to do what is said in this thread, but doesn't have a functioning USB port to use adb with, and has to result with your app (alongside another WiFi adb app) - This will fill the gap! as in ANYONE can recover / flash roms, etc, even if you have a broken USB port!!!

spereree said:
Back to the Helper.jar, all it does is saying "Searching - Hello to 255.255.255.255" "Timeout"
I was assuming it would have automatically connected it for me (say running a command like "adb connect ip.address:5555" )
or am I getting this wrong?
Click to expand...
Click to collapse
This is not wrong. After the helper.apk was running on the device, and showing you the port was open, the jar app should be able to discover it. Are both the pc and device connected to the same wifi access point, and that access point allows the two to talk? I assume so based on your later comments. What OS version?
spereree said:
I kept the path to my android sdk
****Also, I used the mini sdk (It's quite popular, so I'm assuming most users will have this) and I'm missing the "platform-tools" folder. I just have fastboot and adb,exe and some dll files. So, can you provide a link we could get the required "platform-tools" folder alone? (zipped) ****
Click to expand...
Click to collapse
Just point the app to the folder containing the adb executable.
spereree said:
However, when I connect manually via command prompt, "adb connect ip.address:5555" the Helper.jar automatically detects it, and the option to Switch devices to USB appears (which I will not use, personally)
But the "Searching" cycle still continues.
Click to expand...
Click to collapse
Searching will always continue. Something is either blocking the udp broadcast or the device is not allowing helper.apk to get them.
spereree said:
Also, what is the use of the large text entry form below the "Searching" indication?
Click to expand...
Click to collapse
That is a log of what the app is doing

extremewing said:
Are both the pc and device connected to the same wifi access point, and that access point allows the two to talk? I assume so based on your later comments. What OS version?
Click to expand...
Click to collapse
I'm on Windows 8.1 x64
and both devices are on the same network (I'm using my PC as the hotspot via a program called connectify. I'm using a USB 3G dongle for internet.
Just point the app to the folder containing the adb executable.
Click to expand...
Click to collapse
So that means I've done that OK...
Searching will always continue. Something is either blocking the udp broadcast or the device is not allowing helper.apk to get them.
Click to expand...
Click to collapse
I believe that might be the problem, but I don't see where that issue comes from...
Also as an addition, When I connect adb over WiFi on my phone, and I list all devices, I see my phone (as an IP address) but with "unauthorized" next to it (please search on the this issue for more info)... This was a brick wall I hit, when I was trying to get my phone 100% to stock, to send it to repairs for my USB issue... MEaning I can't run any shell commands, etc... via ADB... I was hopping this app could find a way around that?

spereree said:
I'm on Windows 8.1 x64
and both devices are on the same network (I'm using my PC as the hotspot via a program called connectify. I'm using a USB 3G dongle for internet.
So that means I've done that OK...
I believe that might be the problem, but I don't see where that issue comes from...
Also as an addition, When I connect adb over WiFi on my phone, and I list all devices, I see my phone (as an IP address) but with "unauthorized" next to it (please search on the this issue for more info)... This was a brick wall I hit, when I was trying to get my phone 100% to stock, to send it to repairs for my USB issue... MEaning I can't run any shell commands, etc... via ADB... I was hopping this app could find a way around that?
Click to expand...
Click to collapse
You have more than one thing going on here.
1) The program you mentioned "connectify" *may* be blocking the broadcast for discovery to work.
2) The "unauthorized" message is due to an out of date adb on the pc. You should upgrade to the latest version in order to connect to newer android devices. Note that you would also need to accept a permission prompt on the android screen.
3) I am also thinking you need to enable USB debugging for anything to work properly when executing adb commands (even over wifi with a faulty usb port).
4) If you get it back to stock, you may want to see if the USB issue you have is fixed.
5) You may also actually use fastboot to flash it back to stock?

Hi, Thanks for the reply.
I'll try all the options and get back to you.
extremewing said:
4) If you get it back to stock, you may want to see if the USB issue you have is fixed.
5) You may also actually use fastboot to flash it back to stock?
Click to expand...
Click to collapse
As for getting back to stock, I would also love to remove the tampered and "unlocked"
warnings from the top, so that I can take it back to repairs under warranty.
So actually ADB over WiFi need to work flawlessly as if I connected the USB cable,
This is so that when rumrunner is run on the device, no problems should be encountered.
Even after multiple reboots (hence, this application should load ASAP when Android booted.)

This tool is so awsome.
Saved alot of time here.
Tyvm

New version out soon
Since there are nearly 1000 downloads, I was going to bring out a new version I've been working on and I wanted some feedback or thoughts about what you would like to see.
The new version at the moment will give you these new features in the JAR app:
- Improved: device lists that will allow you to multi-select devices to perform actions on
- New: list of all apps on all devices (replaces the "console" at the bottom)
- New: Install an APK from your PC onto all selected devices
- New: One click uninstall of multiple apps on all selected devices
- New: One click enable / disable of multiple apps on all selected devices
Is there anything else one would want to do on all devices?