Database Info

HELP

Hi all I know there's been many a post about being stuck in the bootloader and I even went to the wiki to see what to do.
Firstly, when following the wiki (http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader) on the mtty_utility there is no option for USB only comm 1, 2, or 3 (am i being stupid?).
Secondly, I had a guess and tried all the comm's and eventually comm three seemed to be the only one working, but when I type in the commands it does not do anything.
Any help would be greatly appriciated as I would hate to see my uni go its been so good to me.
Thanks in advance
Jo

Please help

The USB option is at the very bottom of the list. Unless your PC isn't registering the ports, you should be able to get MTTY to work for that part at least.

Thanks for the reply but there wasn't a USB option, I've tried everything, I think it may be to do with vista continuously wanting to run mobsync.exe whenever I plug the uni in but there's no way to stop it.
I've tried ending it as a process but mtty still doesn't have the option of USB.
If you have any ideas please post them, am I right in beleiving that you cannot charge in bootloader mode? Or is that just off the USB?
Thanks
Jo
P.S. The laptop I'm using can read other things through the USB ports, and I have tried every port just to double check that they are not all on the same line (ie an internal hub).

I think it may have something to do with Vista... I'm not sure as I don't have a Universal...
If you have access to XP it may be faster and easier...

I think you may be right
I shall wait untill my housemate gets back in, if it doesn't work in safemode!
Cheers for your help anyway!
I shall keep all informed just in case anyone else ever has this problem

Got it working!
Right finally got it working! It took some time but I managed to revive it!
1) Connect your device in bootloader (Hold light button, power button, and reset),
2) Open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections,
3) Goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity,
4) goto device manager and find your device and update the driver to the one that can be found here: http://forum.xda-developers.com/showthread.php?t=313001&highlight=vista (it is the one in the modem folder, do not follow their instructions, it will not work in this case),
5) Open task manager and kill wmdc.exe, or anything with wm infront of it, also kill mobsync.exe
6) Goto: http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader and follow the instructions (you should be able to see USB as an option now).
In mtty it took a couple of commands before it actually executed then once finished it looked as though it were completely dead, but connect the uni to the comp again in bootlaoder mode and all should be well!
With Reference to:
http://forum.xda-developers.com/showthread.php?t=291723

PS could someone put this in the wiki under the title "If mtty does not have the USB option in vista" I'm being a dunce and don't really know how to do it

[Q] How to connect over ADB when "USB Debugging" is diabled

OK, so here's the issue. I have an HTC Desire C. It's my girlfriends so I don't know the OS version. I replaced the Touch Digitizer because it was shattered (it did respond to touches though). Now that its replaced it seems to respond to touches but not correctly. I can't get it to swipe the lock screen out of the way. It's as if it is not calibrated correctly. So I'm stuck on the lock screen.
I want to run ADB so I can figure out if its registering touch events correctly, and also try and send them over ADB. But, being my girlfriends phone, she never enabled "USB Debugging". When I hook the phone to the computer, I don't see it showing up as a unknown device in windows Device manager (VISTA). I know it works, cause I tried it with my Nexus S and that shows up. I know the steps are first find it in device manager then manually select the driver as the ADB interface, I've had this working on my Nexus S. But the issue is that it doesn't show up at all in Device manager, and I assume its because USB debugging is off. I tried turning off USB debugging on my Nexus S, hooked it to my computer, and it doesn't show up either. So it seems like that is the issue.
I tried to boot into recovery (power button + volume down), then went into fastboot, connected the phone to the comp again, but it still does not show up.
Below are some of the other things I have tried, but they still brought me no luck:
I have tried installing HTC sync so I get the HTC drivers on my computer, but it doesn't even show up in HTC's software (In fact, it does not show up as a storage device either, I assume cause you have to accept the notification on the phone, but I can't use the phones UI at all). I tried moving the HTC drivers into c:\windows\system32 and it still does not show up. I then tried rebooting the phone and my computer. Still does not show up. It seems like windows isn't even reading the phone as a USB device. Tried swapping USB cables (both work with my nexus s), and still nothing. Is there something I am missing?
Any help would be much appreciated, this is driving me crazy.
Also, after replacing the digitizer, if I first boot into the phone and then hit the power button, I don't get the content window that allows you to choose "reboot", "shutdown", etc. The only thing I can do is hold it for 15 seconds and the thing turns off. I'm hoping this is because I never passed the lock screen for the first time. I'm hoping this is not an indicator that I screwed something up when I opened the phone. I've had my Nexus S open plenty of times.

Another guy had same issue. here
Try that.
life!

Yea let us know if it works

Lifehacker7 said:
Another guy had same issue. here
Try that.
life!
Click to expand...
Click to collapse
I can't get the phone to show up when I type "fastboot devices" or "adb devices". I have tried this from the lock screen, from the bootloader, from the bootloader and in fastboot mode. That is my critical problem now. Cable is actual data cable, and I'm using USB port on back of a desktop computer. Is there anything else that could be causing the phone to not be recognized?

[Q] adb device offline - broken screen

Hello!
Today both the screen as the touch panel of my Galaxy Nexus broke. I wanted to run screencast or some other apps to control my phone via pc BUT after searching for "adb devices" I got my devices number and the word "offline".
I looked up on what I guess the issue was and what I found out was, that I have to verify my pc with this RSA-fingerprint in order to control my device, which I have not done yet on my latest rom, as I just flashed it a few days ago.
Now: can you think of any way, either bypassing the fingerprint or letting me control the device via pc to prompt the fingerprint-request?!
As mentioned, I THINK that is the problem.
Things I have tried:
different USB-port
different USB-cable
updating platform-tools
HDMI-output via MHL-adapter (no signal)
I really am hopeless and happy about all the ways, you could think of showing my phones screen on my pc. I would prefer to keep my current ROM data, as I do not want to wipe arrived messages before viewing them (WhatsApp).
some information:
device: Galaxy Nexus (GSM)
rom: latest AOKP Milestone (4.2.2)
root access of course
device definetly turned on (LED blinking)
-Jakob

Resolved!
I had a similar problem and after hours of research and trial/error, I was able to get this working. Here's how:
1. Download & install the Galaxy Nexus Toolkit and MyPhoneExplorer to your PC
2. Goto the Google Play Store on your PC and remote install MyPhoneExplorer and AF Rescue 2 apps to your phone. Wait 10 minutes or more so that this step has time to complete before continuing (longer is better)
3. Next you have to boot your phone into Recovery mode... pull the battery and usb cable out (so you can be sure your device is off). Put the battery back in, plug in the usb cable (I do this now so I can hear when the device is connected and later so you can hear that the command/reboots are working). hold down both vol up and vol down AND then hold down the power button... I do this for about 10 seconds. After releasing the buttons, your phone should be in bootloader mode, but I give it a minute just in case. now hit the vol up button 2 times then the power button. You will hear the usb connection go on and off several times and when it's done, your device will be in Recovery mode.
4. Launch the Toolkit, answer "no" to the initial question about checking for updates, then choose your device from the list
5. on the next screen (main menu) you should see your device ID listed under ADB mode list with the word "recovery" after it. If so, you have done everything correct so far. (if not, close the toolkit window, go back to step 3 and try again).
6. Next choose option 2 for Backup/Restore. Then select option 3 for "Backup your Internal Storage"
7. This is crucial. On the next screen choose option 2 "manually answer the question". Then when it asks if you are using a custom rom or recovery image, ANSWER "NO" (even if you are). This is the most important step in the whole process because it will then boot your phone into fastboot for you and install an insecure recovery image bypassing the 4.2.2 security!
8. When it tells you that the backup will take a long time and are you sure you want to continue, I recommend doing so. It will take hours (I left mine to run overnight.) Either way, when you get back to the main menu DO NOT REBOOT YOUR PHONE. YOU NEED IT IN THIS STATE.
9. Now if all has worked properly, you can launch MyPhoneExplorer on your PC and choose setup your connection via wifi. Cross your fingers, but if all worked as it did for me, your phone will appear on the screen (if it is all black, just hit the power button on your phone to wake it up). Use your mouse to enter your lock pattern or pin number if you have those set. At this point you should be using your phone through your PC. Just remember that as soon as you reboot the phone, it will revert back to it's secure state and you will have to go through this process again. I hope this helps you and others (and saves everyone the hours of frustration and research I went through).
jakbold said:
Hello!
Today both the screen as the touch panel of my Galaxy Nexus broke. I wanted to run screencast or some other apps to control my phone via pc BUT after searching for "adb devices" I got my devices number and the word "offline".
I looked up on what I guess the issue was and what I found out was, that I have to verify my pc with this RSA-fingerprint in order to control my device, which I have not done yet on my latest rom, as I just flashed it a few days ago.
Now: can you think of any way, either bypassing the fingerprint or letting me control the device via pc to prompt the fingerprint-request?!
As mentioned, I THINK that is the problem.
Things I have tried:
different USB-port
different USB-cable
updating platform-tools
HDMI-output via MHL-adapter (no signal)
I really am hopeless and happy about all the ways, you could think of showing my phones screen on my pc. I would prefer to keep my current ROM data, as I do not want to wipe arrived messages before viewing them (WhatsApp).
some information:
device: Galaxy Nexus (GSM)
rom: latest AOKP Milestone (4.2.2)
root access of course
device definetly turned on (LED blinking)
-Jakob
Click to expand...
Click to collapse

themadczar said:
I had a similar problem and after hours of research and trial/error, I was able to get this working. Here's how:...
Click to expand...
Click to collapse
Thank you very much for your time and effort, I will try this soon!

Sadly I am in the same position as the OP. My screen is cracked and I need to access the phone via adb, unfortunately, it is appearing as offline. Does anyone know a way to bypass this RSA-fingerprint issue?

i9305t can't connect to Odin

I have bought a i9305t with a broken screen through a private sale. After connecting it to a working screen, I discover a few strange problems:
1. I can't get the phone into download mode or recovery mode by the normal key combinations. So I can't do any factory reset.
2. The phone can power up, but it stops at a log in screen requesting a pin input, although when I asked the previous owner about it, he said he never had set up any locking pins.
3. In that pin-entering mode, when I connect the phone to my PC (windows 7), the PC recognise the connection and displayed a i9305t in windows explorer, but the explorer can't show any content details of the phone. When I run the Odin with the phone in this mode, the COM window changes colour, but any attempts to flash any tar file stops at 'SetupConnection..' step, and after a while, it comes back with a 'FAIL!'.
4. I have a usb jig, and with that, I can force the phone in download mode. However, when the phone is in that mode, Odin doesn't recognise the connection at all when I plug the phone in, so I can't do any flashing in that mode.
So I am totally stuck! I thought about going through ALL the pin combinations to try to unlock the phone (assuming the pin is a 4 digit number). After spending one and a half hours to go from '0000' to '0500', I thought this is rediculous! There must be a better way! So I hope some guru out there would be able to help me, as I have exhausted all my tricks (which is not that many!).
If anyone can show me a way to get around my problems, it would be most appreciated!!!

Missing IMEI
tdrinker said:
I have bought a i9305t with a broken screen through a private sale. After connecting it to a working screen, I discover a few strange problems:
1. I can't get the phone into download mode or recovery mode by the normal key combinations. So I can't do any factory reset.
2. The phone can power up, but it stops at a log in screen requesting a pin input, although when I asked the previous owner about it, he said he never had set up any locking pins.
3. In that pin-entering mode, when I connect the phone to my PC (windows 7), the PC recognise the connection and displayed a i9305t in windows explorer, but the explorer can't show any content details of the phone. When I run the Odin with the phone in this mode, the COM window changes colour, but any attempts to flash any tar file stops at 'SetupConnection..' step, and after a while, it comes back with a 'FAIL!'.
4. I have a usb jig, and with that, I can force the phone in download mode. However, when the phone is in that mode, Odin doesn't recognise the connection at all when I plug the phone in, so I can't do any flashing in that mode.
So I am totally stuck! I thought about going through ALL the pin combinations to try to unlock the phone (assuming the pin is a 4 digit number). After spending one and a half hours to go from '0000' to '0500', I thought this is rediculous! There must be a better way! So I hope some guru out there would be able to help me, as I have exhausted all my tricks (which is not that many!).
If anyone can show me a way to get around my problems, it would be most appreciated!!!
Click to expand...
Click to collapse
----------
Problems solved! Well, most of them anyway. I found I got the wrong usb driver on my PC. After updating with the correct Samsung usb driver, I could connect to Odin, thus I could flash a CWM recovery rom, so I could do a factory reset.
However, after the phone has booted up, for some reason, I found the IMEI is missing, so I couldn't connect to any network when I insert my sim card. I don't know how that happened. Can anyone help me with that? Many thanks.

[Q] Bricked worse than I thought? Help! (long)

Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,

JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
Interesting problem. I have bricked my phone a bunch of times and have always been able to get back to at least "download Mode". The method I use to go to "Download Mode" is With the usb cable plugged into the computer only, power off the phone. If phone wont power off, or stay powered off, pull battery, then put battery back in. Now hold vol down and vol up buttons only, keep holding these buttons as you plug the usb cable into the phone. In 3 seconds the download screen should appear. I hope this helps you get your phone back.

JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
This sounds like a time where a jig would be helpful. Any chance you can have your wife order one, and send to you? http://www.youtube.com/watch?v=D7I4dFX_iJ4
This should put you straight into download mode, and you can then flash.

Thanks, guys. I continued fiddling and got the phone into DL mode.
I also noted that when plugging and unplugging the phone, it would show up in zadig as "unknown device."
I tried to load the drivers on that, but (a) it still shows up as "unknown device" and (b) when I run HOC it doesn't see the phone under the list of compatible devices.
So.... still kind of stuck.
Any more ideas?

Oop. duplicate post

It's been awhile since I've played with the one clicks, but, "serial gadget" is what I remember seeing when I used them.

Right. MORE messing around later and "Serial Gadget" is it.
That said, I still think I have a driver issue. I have tried uninstalling and reinstalling the zadig-recommended drivers for Serial Gadget several times. I also tried manually installing the drivers from Super One Click.
Anyway, now when I load up HOC I get the green <<connected>> at bottom; but then sometimes it wants me to install the drivers (again) and sometimes it gets past that part, but then goes to
Flashing Kernel: 0%
...hangs there for about 10 seconds and then
Failed!
So... driver thing you think?
Thanks again,

If you reboot the phone after the 0% hanging for 10 seconds, does it go to the yellow exclamation mark screen? If so, just reflash again and you should be back to working... both my and my wife's phone always did that when I had to flash a kernel.

That's just another download screen that theraze is describing.

Exacatly. But the alternate download screen always came up after restarting the phone after a 'failed' flash where it stayed at 0% where it was successfully communicating through the cable. That just meant to not break the drivers or unplug anything... just reboot fast and finish up quickly.

Okay - I can definitely try that! It had not occurred to me to try and reboot the phone right then.
Question, though - when I get the "Failed!" Then HOC essentially hangs, when it says something along the lines of "ending session..." and never progresses from there. So how do you "restart quickly?" Because I have to like, close and reopen HOC. I guess I will see if it succeeds at ending the session when I reboot.
I will try it again. Strange though, sometimes HOC accepts the existing driver (I managed to DL the Samsung driver installer) and sometimes it wants to reinstall "WinUSB." does that make sense? Is the WinUSB an acceptable one?

The winusb is the right driver for heimdall, it doesn't like the Samsung driver.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Samsung drivers and the one click drivers clash. Yes, uninstall Samsung completely if you want to use the one click.

Hm. Thanks for that - might be part of the problem.
Dunno what I did differently, if anything, but last night I tried flashing again and this time it went through! I was very glad to see the whole HOC process completed successfully!
So anyway - thanks so much for the help, guys.