Develop Bugs

few stupid questions

Ok so I just got a Pocket pc siemens sx56 from my dad cause he doesn't use it. I went to install the new rom the one with all the software but it doesn't work I believe that is because im using the USB docking station that came with it.
1.Can I use the Serial cable to usb or does it have to be a serial to serial cable.
2. What type of memory card does the pocket pc use does it take regular SD and Mmc cards or does it require the reduced size cards.
3.I got the xda-tools-Jeff file when I use that it says in the readme to use the cradle but it still didn't work like It opened I selected the file then selected to program but then it opens the sdrom tool and then it says please make sure the power cable is connected. If the power cable is connected then how would I transfer files, is it saying that because I don't have the serial to usb cable. Also is it possible it did not work because I had it connected to my pc and hot synced at the time. Do I need to not have it hot synced.
4. I only have 18 mb free on the sx56 because I don't have a expander card yet Do I need that before I flash the rom or Can I flash the rom from my pc this way I don't need to copy the 31 meg file, because also it is still locked to at&t and I want to use it with tmobile
I really appreciate the help with theses questions thank you again ahead of time
Below are the links to what I was going to purchase for this. are theses the correct items I need to buy
http://www.tigerdirect.com/applications/searchtools/item-Details.asp?EdpNo=1533921&sku=K24-9238 --mmc card
http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=1104129&CatId=618 -- usb cable
http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=1567039&CatId=942-- card reader/writer

well i got the SD card 512 meg of ram and I got a usb card writer but I still dont have the serial cable or the serial to usb cable. Im trying to install the xda rom with all the goodies but it keeps saying connect a power source to the unit. is there a way I can copy the rom to the card in the sx56 and run it from there
than you

im going crazy it keeps saying please plug the power adapter into your pocket pc but i cant because If i do that then it wont be connected to the pc can someone please help me

also im running rom version Siemens English A.20.17 and it has bootloader 5.22

if your cradle have the power connected plug'd into it your power connector IS plug'd into your pda

problems with s-on usb brick

kernel 2.6.35.10
sense 3.0
android 2.3.5
s-0n
just got a dhd from the bay of fleas,the dhd will not perform any usb functions apart from charging.
i have all the drivers and sdk installed on my pc from my desire bravo.
i searched and found a thread about unrooted usb brick,followed all the instructions in fastboot oem enable blah blah,all i get is waiting for device.
when i attatch the dhd to the usb i get nothing,plug in the bravo and all is ok,also when i select recovery i get the red triangle.
i am at a bit of a loss with this problem,dont want to be stuck on a non rooted sense 3.0 its bloody slower that my aio bravo, i might add the phone functions normally apart from the above problem.
waiting to flash thanks mark

markb63 said:
kernel 2.6.35.10
sense 3.0
android 2.3.5
s-0n
just got a dhd from the bay of fleas,the dhd will not perform any usb functions apart from charging.
i have all the drivers and sdk installed on my pc from my desire bravo.
i searched and found a thread about unrooted usb brick,followed all the instructions in fastboot oem enable blah blah,all i get is waiting for device.
when i attatch the dhd to the usb i get nothing,plug in the bravo and all is ok,also when i select recovery i get the red triangle.
i am at a bit of a loss with this problem,dont want to be stuck on a non rooted sense 3.0 its bloody slower that my aio bravo, i might add the phone functions normally apart from the above problem.
waiting to flash thanks mark
Click to expand...
Click to collapse
When you say it wont perform any USB functions, does it acknowledge that the usb cable has been plugged in? i.e do you get the charge only/ Disc drive menu? have you tried different micro usb cables?

ghostofcain said:
When you say it wont perform any USB functions, does it acknowledge that the usb cable has been plugged in? i.e do you get the charge only/ Disc drive menu? have you tried different micro usb cables?
Click to expand...
Click to collapse
nope,nothing at all.when i plug it in no menu at all,even with the usb connected and boot into bootloader no noise from the pc,totally dead ...

My personal feeling would be that the usb port is possibly damaged.

ghostofcain said:
My personal feeling would be that the usb port is possibly damaged.
Click to expand...
Click to collapse
my thoughts as well,does the dhd use a different cable than the standard desire bravo ?.as i did not get a cable with the phone.
is there anyway of checking if the port is damaged ? thanks

If it charges through PC the usb is fine. It could be that the drivers do not mach. Have you tried updating them or connecting to another PC?
Recovery won't work since the phone is s-on meaning you can't possibly flash a radio on it.
Solution: root.
Sent from my Desire HD using XDA App

Try another cable, some are just charge only.

[HOW-TO] Enable OTG(USB HOST) on Galaxy SII

So after painstakingly searching around for an answer on how to get OTG working on the galaxy s2 running a custom ROM and Kernal with little to no help i finally figured it out:
You will need:
OTG Cable ( Micro USB Host cable) (store bough or home made work, i followed this link: http://highonandroid.com/android-howtos/how-to-make-otg-usb-host-cable-for-galaxy-s2-or-xoom/ )
A Kernel that supports OTG ( I'm using { and could only find } http://www.gokhanmoral.com/gm/2012/05/06/siyahkernel-v3-2rc1/ , there is an update to this kernal , but i have not tested the OTG support yet (May/7)
And last but not least, USB Host Controller APP : https://play.google.com/store/apps/details?id=hu.sztupy.android.usbhostcontroller&hl=en
Procedures :
1. Install the kernel by flashing it through CWM
2.Install USB Host Controller App
3. Restart phone
4. plug in usb device into OTG cable
5. Plug in OTG Cable to phone
6. TADAA
if you have any questions feel free to PM me or post a reply...
i had to change the steps from the link to make the OTG cable to make it work!!!
Homemade Cable Troubleshoot:
my cable was a samsung USB U2 cable, i dont know if this makes the biggest difference. but you want to short ( connect) pins 4 and 5.. one of the 2 solder points is the black wire from the usb cable ( ground) and if yours doesnt work with the pin he says to use, you can try plugging in a usb device into the cable and have the wire connected to the ground and simply probe the other pins until you find the pin that works! ( DO NOT CONNECT BLACK AND RED I REPEAT DO NOT SHORT BLACK AND RED, YOU WILL FRY YOU PHONE AND I TAKE NO RESPONSIBILITY FOR THIS, THIS IS YOUR WARNING!!!)

This kernel can work with Galaxy s2 duos tv gt-s7273T ?
I,m trying enable the OTG to my s2 gt-s7273T
This is possible? Using Jelly Bean 4.2.2 stock rooted
With busybox installed .
Please if possible help me

WOW! I have a faulty micro sd card so I could only backup to internal storage. Saw your post which reminded me I have an OTG cable that I use for my Note 4, I'm using CM11 and "hey presto!" CM11 recognizes external USB, no apps needed, I could/can make backups, Love my CM11
Glad I saw your post, Many Thanks, and Kind Regards!!

[GUIDE] How to flash recovery image Nvidia Shield TV using FASTBOOT hardware method

All of the instructions I found for doing this weren't exactly clear, so I'm writing this out in a way that even dummies like me can understand. So, my Nvidia Shield TV got soft bricked when I tried to update my TWRP to this version.
First, you have two options for the cables:
This: http://www.monoprice.com/Product?p_id=9724
and this: http://www.monoprice.com/product?p_id=5443
Plug them into each other so they're just 1 cable now.
The second option is to use a USB to micro USB data/charging cable, like the one that it came with.
Here are the steps, read it completely through 1 time before doing anything. I find that makes things easier to understand when you're ready to actually do it.
Install FASTBOOT DRIVERS: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Install Minimal FASTBOOT & ADB: http://forum.xda-developers.com/showthread.php?t=2317790
Download OS Image: https://developer.nvidia.com/gameworksdownload
Extract the OS Image to your desktop.
Go to the installation folder for Minimal FASTBOOT & ADB and copy its contents into the OS Image folder you just created.
Open a Windows command prompt in this folder.
Make sure power cable & USB OTG cable on NSATV are UNPLUGGED.
Make sure HDMI cable is PLUGGED IN.
Plug the standard USB end of the USB OTG cable pair into a PC.
*** DO THE STEPS BELOW IN THE EXACT ORDER ***
Plug in USB OTG end of the USB OTG cable pair into NSATV.
Plug in the power cable. The next step follows quick.
Quickly touch and hold the power button until the FASTBOOT screen appears on your TV, then release.
Now, go back to your PC.
In the Windows command prompt, type: fastboot devices
Make sure the fastboot device appears.
If you see your fastboot device, then you can follow the instructions in the HowTo-Flash-Recovery-Image.txt file.
I hope this helps. If there's any part that's confusing, let me know and I'll edit it.

Yeah, you guys are awsome, it worked!!!!!
Thanks so much for all your help and advice :good:

You could also just use the charge cable that you get for your controllers rather than buying the extra cables, it works fine.
Sent from my HTC One M9 using Tapatalk

gffmac said:
You could also just use the charge cable that you get for your controllers rather than buying the extra cables, it works fine.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
It doesn't need an OTG cable?

Nope, using the supplied cable just connect the micro usb end to shield other to PC and bobs your uncle ?
Sent from my HTC One M9 using Tapatalk

any idea if this will work for my shield 16GB? since i was updating it to 3.0 this morning and the electric went now all it does it boot right to TWRP recovery. also i still have access to fastboot.

beefy143 said:
any idea if this will work for my shield 16GB? since i was updating it to 3.0 this morning and the electric went now all it does it boot right to TWRP recovery. also i still have access to fastboot.
Click to expand...
Click to collapse
It should?

tried and no it does not just left at the nvidia boot creen with the odd black screen reboot back to the nvidia symbol any ideas as to what i can do to fix my shield?

beefy143 said:
tried and no it does not just left at the nvidia boot creen with the odd black screen reboot back to the nvidia symbol any ideas as to what i can do to fix my shield?
Click to expand...
Click to collapse
Follow the instructions EXACTLY. I have the 16Gb model and mine was doing the same thing as yours.

Just to repeat what others said the back of the shield TV has a microusb port so you don't need a otg cable just use any standard microusb cable you have laying around plug small end into shield TV and big end to laptop/computer

Hi!
I tried but failed. The issue is, that it reboots directly after showing the recovery menu.
Only see it 2 seconds, then reboot. No reaction on menu choices...
I guess it happened when I tried to copy the SD card to another one.

You should be using fast boot to do this. Plus, there's no SD card in the instructions. Not sure what you are trying to do.

JoCamel said:
Hi!
I tried but failed. The issue is, that it reboots directly after showing the recovery menu.
Only see it 2 seconds, then reboot. No reaction on menu choices...
I guess it happened when I tried to copy the SD card to another one.
Click to expand...
Click to collapse
Try again without an sd card attached maybe. Also try 'fastboot boot recovery.img' instead of flashing it.

Neo3D said:
[*]In the Windows command prompt, type: fastboot devices
[*]Make sure the fastboot device appears.
[*]If you see your fastboot device, then you can follow the instructions
Click to expand...
Click to collapse
Hi
All fine up to that point... Fastboot Devices... nothing shows up!
? anyone?
My box is stock, I have not messed with it at all.

if i not enable debug? how to do?

fredphoesh said:
Hi
All fine up to that point... Fastboot Devices... nothing shows up!
? anyone?
My box is stock, I have not messed with it at all.
Click to expand...
Click to collapse
Could be a driver issue? Make sure the drivers are properly installed and working? Try rebooting?

Will these steps work with the 2017 16GB version? Cause I want to have full Android on the Shield but the processes I've seen are pretty confusing.

I want to try this, will this work with the new 5.2 update?

Jabadabaduu!! It solved my problem
Hey Neo
First of all, your guide saved my day! - Thanx!
I know this must be a strange question, but is the person on your XDA profile picture, and the one that has written the article really the same person ?

Neo3D said:
All of the instructions I found for doing this weren't exactly clear, so I'm writing this out in a way that even dummies like me can understand. So, my Nvidia Shield TV got soft bricked when I tried to update my TWRP to this version.
First, you have two options for the cables:
This: http://www.monoprice.com/Product?p_id=9724
and this: http://www.monoprice.com/product?p_id=5443
Plug them into each other so they're just 1 cable now.
The second option is to use a USB to micro USB data/charging cable, like the one that it came with.
Here are the steps, read it completely through 1 time before doing anything. I find that makes things easier to understand when you're ready to actually do it.
Install FASTBOOT DRIVERS: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Install Minimal FASTBOOT & ADB: http://forum.xda-developers.com/showthread.php?t=2317790
Download OS Image: https://developer.nvidia.com/gameworksdownload
Extract the OS Image to your desktop.
Go to the installation folder for Minimal FASTBOOT & ADB and copy its contents into the OS Image folder you just created.
Open a Windows command prompt in this folder.
Make sure power cable & USB OTG cable on NSATV are UNPLUGGED.
Make sure HDMI cable is PLUGGED IN.
Plug the standard USB end of the USB OTG cable pair into a PC.
*** DO THE STEPS BELOW IN THE EXACT ORDER ***
Plug in USB OTG end of the USB OTG cable pair into NSATV.
Plug in the power cable. The next step follows quick.
Quickly touch and hold the power button until the FASTBOOT screen appears on your TV, then release.
Now, go back to your PC.
In the Windows command prompt, type: fastboot devices
Make sure the fastboot device appears.
If you see your fastboot device, then you can follow the instructions in the HowTo-Flash-Recovery-Image.txt file.
I hope this helps. If there's any part that's confusing, let me know and I'll edit it.
Click to expand...
Click to collapse
Awesome, works like a charm

Pixel 2 XL not connecting to PC

UPDATE:
I ended up just returning the phone and getting a new one (it was an Ebay seller so they didn't try to repair it).
New one connected instantly and I can use ADB and Fastboot perfectly.
Definitely something wrong with the first one, weird how the headphone adapter and OTG worked though.
Original post:
I know there are other threads on this but I really need some help on this.
I just got a Pixel 2 XL, but it won't connect to the PC. At all. No connection noise, nothing in task manager. The only change between plugged and unplugged is that the phone starts charging. No notification appears when I plug it in, it doesn't even try to connect.
I've tried three different cables, three different PCs, I've fiddled with USB debugging. I can't do anything with drivers on Windows because nothing changes in device manager when I plug it in.
I don't have any computers with USB C ports so I can't test that but I've tried all different ports on my PC (USB 2 and USB 3).
The headphone adapter works and when I plug in my old HTC U11's earbuds it says "accessory not supported" (which it's supposed to say, those earbuds only work on specific phones) so the port can't be completely broken.
I also tried plugging a USB drive into the full size to C adapter that comes with it and it reads it perfectly. I copied my music library onto the Pixel by putting it on a flash drive first.
I realise it may just be defective but it would be a huge pain if I got a new one only to discover that it was something that I'm doing or my PC causing it. And is it even possible to be defective when it can output music and even transfer files from a flash drive through that same port?
What else can I try?

megaman1574 said:
I know there are other threads on this but I really need some help on this.
I just got a Pixel 2 XL, but it won't connect to the PC. At all. No connection noise, nothing in task manager. The only change between plugged and unplugged is that the phone starts charging. No notification appears when I plug it in, it doesn't even try to connect.
I've tried three different cables, three different PCs, I've fiddled with USB debugging. I can't do anything with drivers on Windows because nothing changes in task manager when I plug it in.
I don't have any computers with USB C ports so I can't test that but I've tried all different ports on my PC (USB 2 and USB 3).
The headphone adapter works and when I plug in my old HTC U11's earbuds it says "accessory not supported" (which it's supposed to say, those earbuds only work on specific phones) so the port can't be completely broken.
I also tried plugging a USB drive into the full size to C adapter that comes with it and it reads it perfectly. I copied my music library onto the Pixel by putting it on a flash drive first.
I realise it may just be defective but it would be a huge pain if I got a new one only to discover that it was something that I'm doing or my PC causing it. And is it even possible to be defective when it can output music and even transfer files from a flash drive through that same port?
What else can I try?
Click to expand...
Click to collapse
Which version of Windows are you trying it on? Can you try it on a Win 7 machine? It's not the phone but the drivers. There are various threads around that will guide you thru it but you have to search some. Some are a little old but they should work. Keep at it, you'll figure it out. There is something in device manager that you need to tinker with if I recall correctly. Happened to me on my Pixel OG and it took me a few days to finally figure it out. Total pain but relief once you get it.

If you have a relatively new computer (Win 7 or newer) then it *should* recognize the Pixel. But sometimes Windows can be a pain in the ass. Download & install Android SDK which will install the latest Android USB driver, reboot the computer, then connect the Pixel again.

sublimaze said:
If you have a relatively new computer (Win 7 or newer) then it *should* recognize the Pixel. But sometimes Windows can be a pain in the ass. Download & install Android SDK which will install the latest Android USB driver, reboot the computer, then connect the Pixel again.
Click to expand...
Click to collapse
I don't think I can install any drivers unless the phone shows up as something in device manager, which mine doesn't

megaman1574 said:
I don't think I can install any drivers unless the phone shows up as something in device manager, which mine doesn't
Click to expand...
Click to collapse
Your computer must have Android USB driver installed before it will recognize the phone.

sublimaze said:
Your computer must have Android USB driver installed before it will recognize the phone.
Click to expand...
Click to collapse
I'll search this in the morning. He needs to uninstall something.. dang it I forget. I'll figure it out tomorrow. Or search my posts from a year ago I'm sure it's there somewhere.
Sent from my Pixel 2 using XDA-Developers Legacy app

sublimaze said:
Your computer must have Android USB driver installed before it will recognize the phone.
Click to expand...
Click to collapse
What I mean is it doesn't show up at all. When I plug the phone in device manager doesn't change.

bobby janow said:
I'll search this in the morning. He needs to uninstall something.. dang it I forget. I'll figure it out tomorrow. Or search my posts from a year ago I'm sure it's there somewhere.
Sent from my Pixel 2 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I had a look through your post history but I'm not sure what I'm looking for... And I can't figure out how to search a post history

megaman1574 said:
I had a look through your post history but I'm not sure what I'm looking for... And I can't figure out how to search a post history
Click to expand...
Click to collapse
Yeah I know, only goes back for like a year or so. This is the guide I followed and it worked. Some still had problems but check out the OP and give it a shot.
https://forum.xda-developers.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625

This may be silly but when my phone was new I had the same issue. I had to go into the USB settings on my phone and change them from charging to file transfer.

I'm having similar issues to the OP, but I've had my phone since it was released. I have done everything known to man to try and get this working--updated Android Studio/drivers, both fixes listed HERE, tried numerous cables, rebooting phone and multiple PCs, still not getting my phone to get recognized at all.
My exact issue is this: I'm still on the August 2018 Security patch, so I wanted to update to October. Downloaded my files then went into Magisk and uninstalled (un-root) restoring stock boot. I waited a few hours before I could try to flash the OTA, but once I did, I connected the phone (USB-C to USB-C OEM cable) to my PC and it successfully connected in Debug mode. Ran "adb devices" and phone was seen. "adb reboot bootloader" successfully rebooted phone, but it did not go into bootloader mode for some reason, it just restarted in normal mode. The only problem is now the phone doesn't talk to my PC no matter what.... the USB-C to USB-C OEM cable doesn't even charge the phone let alone connect to give me file transfer options. If I try a USB-C to USB-A cable, the phone charges but the PC doesn't recognize my phone is connected. Debugging never works. Even my Car Charger (which is USB PD capable) doesn't charge the phone, I have to go back to my regular USB-C QuickCharge car adapter to get it to take a charger. I've disabled Debugging, changed default USB connection type to File Transfer, PTP, etc.
So, is there a way I can try to flash the OTA without connecting to a PC? Maybe even just flash the August Boot.img? I want to try updating the phone to see if that fixes my issues first. I am currently with an unlocked bootloader, no root and stock recovery, so I don't believe Flashify will work without getting root back... I think when I restored my stock Boot via Magisk, it FUBARed something. The only thing I can try is to use my USB-C to USB-A cable and see if fastboot recognizes the phone with that cable... the USB-C to USB-C cable is no dice in Fastboot.

Do you have another Android device? If so, (and it is rooted), you can run adb and fastboot from there. The binaries are available via the Magisk repository. Just grab a terminal emulator and a usb-otg cable and go to town. No driver issues, no fuss, no mess.
I was occasionally successful with a usb-c to usb-c cable, but sometimes the devices would get confused. The otg cable works every time, with the host end facing the adb/fastboot running device.

@hawkjm73 To whom are you talking to? If me, I don't have an OTG cable nor another rooted phone.
I did try the USB-A to USB-C cable and booted into Fastboot, which worked. I was able to at least boot into TWRP and get Magisk re-installed so I'm rooted. I booted the phone back up and still no USB recognition or Debugging. I'm going to wait to try a third PC to see if that will work in getting Debugging/ADB commands to work. All else fails, I'll just do a full Factory October flash without the wipe.
What's puzzling to me is why this all happened and why even my USB-C PD car charger won't work. Something strange is going on.
---------- Post added at 03:01 PM ---------- Previous post was at 02:25 PM ----------
Update: I grew impatient and decided that since my PC was seeing the phone in fastboot, I flashed the full October Firmware manually in fastboot (ran each command in the flash-all.bat one by one). As soon as it booted into the OS, Debugging and USB connectivity (both cables) turned back on. I haven't tested my Car USB PD charger, but I suspect that will work too.
I'm guessing when I uninstalled Magisk and tried restoring the stock Boot.img, something went awry and it was causing the connectivity issues.
So, if you can get your phone into Fastboot and your PC recognizes it, I would suggest a full system image flash, don't forget to remove the -w if you don't want to wipe.

megaman1574 said:
I know there are other threads on this but I really need some help on this.
I just got a Pixel 2 XL, but it won't connect to the PC. At all. No connection noise, nothing in task manager. The only change between plugged and unplugged is that the phone starts charging. No notification appears when I plug it in, it doesn't even try to connect.
I've tried three different cables, three different PCs, I've fiddled with USB debugging. I can't do anything with drivers on Windows because nothing changes in device manager when I plug it in.
I don't have any computers with USB C ports so I can't test that but I've tried all different ports on my PC (USB 2 and USB 3).
The headphone adapter works and when I plug in my old HTC U11's earbuds it says "accessory not supported" (which it's supposed to say, those earbuds only work on specific phones) so the port can't be completely broken.
I also tried plugging a USB drive into the full size to C adapter that comes with it and it reads it perfectly. I copied my music library onto the Pixel by putting it on a flash drive first.
I realise it may just be defective but it would be a huge pain if I got a new one only to discover that it was something that I'm doing or my PC causing it. And is it even possible to be defective when it can output music and even transfer files from a flash drive through that same port?
What else can I try?
Click to expand...
Click to collapse
Time for an RMA...just happened to me a month ago

WoJ... good follow-up update.

I ended up just returning the phone and getting a new one (it was an Ebay seller so they didn't try to repair it).
New one connected instantly and I can use ADB and Fastboot perfectly.
Definitely something wrong with the first one, weird how the headphone adapter and OTG worked though.