Database Info

[Q] no USB connection

Hi everyone,
I have a Mytouch 3G Fender, rooted (of course), and I'm running Ginger Yoshi RC7 with the recommended SPL and radio and the kernel that is specifically recommended for the Fender. Everything's been going absolutely great for about a week, but now, when I plug the phone into my computer, it won't recognize that anything is plugged in. The phone starts to charge when I do it, but no data connection is made. It's as if I'm plugging it into a wall outlet. I took my phone and cable to work and tried it on my work computer, and same thing. I've plugged it into that computer before, and it recognized it. This tells me that it's the phone, not the computer or any drivers or anything. What's really crazy is that I just did a full wipe and reflashed the rom and kernel thinking that whatever got jacked up would be wiped or reset, but the problem remains. Any thoughts? Thanks in advance.

If anyone can help me out with this, I'd really appreciate it. I should add that I just went to t-mobile earlier today and they gave me another cord, and that didn't work either. So we know it's not the computer or the cord. It must be the phone. If anyone has any ideas on why it's doing this and what I can do about it, please let me know. Thanks.

come on people, anyone?
I should add one thing that I just discovered. I AM able to make a connection in fastboot mode, but that's it. I cannot get it to recognize in ADB, in recovery, or when the phone is turned on normally.
I'm sure someone out there has some input for me. If I should be posting this elsewhere, let me know. Someone please assist. Tethering is my source of home internet, so I REALLY need to be able to plug my phone to my computer.

Does Ginger Yoshi RC7 come from Cyanogen mod?

hoshikoong said:
Does Ginger Yoshi RC7 come from Cyanogen mod?
Click to expand...
Click to collapse
I don't think so. Here is the link for it.
http://forum.xda-developers.com/showthread.php?t=932118
However, I don't think it has anything to do with the rom, for three reasons. First, I've looked through the posts in the link above and no one else seems to be having this problem. Second, I've tried getting rid of it and flashing the stock rom for this phone, and still nothing. Third, I can't even do a USB-MS toggle when I'm in recovery mode. In recovery mode, it doesn't matter what rom I have in there, if any at all. I know it's not a hardware issue since I am able to get fastboot to see it. I am quite stumped...

thank you very much work on my device

[Q] Failed Valhalla Final flash

Hello all, any help would be greatly appreciated.
My wife's phone has been rather buggy so I decided to root and rom it. Rooted the phone with the oneclick method. Moved on to getting CWM up and running (it is what I'm familiar with from my G2x). I liked what I was seeing with the Valhalla Final rom OP and decided to give it a try. Read the instructions to install but things have steadily gone down hill.
I am comming from stock. I did a NANDROID backup. Wiped, wiped, wiped and then flashed the ROM. I do believe that I just didn't read carefully enough where it says I "must have pre-installed kernel" . When I rebooted I got a pixelated screen unreadable screen. There was a voice in the background describing what was going on but I plugged along and waited the 5-7 minutes. Figured if it didn't work correctly I would just go back into CWM and restore my nandroid backup. However I can no longer get back into CWM or the recovery prompt that comes before CWM. I just get the Galaxy S 4g screen which then goes to the weird pixelated screen and then it continues in a boot loop.
I tried to follow this debricking thread but got stuck a couple of times. First, that I can't find the boot.bin and sbl.bin files. I google around and found this but the download link no longer works. Does anyone have the boot.bin and sbl.bin files handy?
Also, the Zadig program to install the Heimdall driver doesn't show me any driver options. I suspect that this is because Heimdall or Zadig had not run on the computer before I had the phone properly connected. I saw that it was the Samsung Composite driver that was being asked for. Not sure if I found the correct one but either way it didn't work. I was unable to get the computer to recognize the phone (also phone would continue on its boot loop, also it doesn't change anything whether I am holding down the volume buttons when I turn the phone on or not).
I have stayed up half the night looking for something but am wondering if I just straight up bricked the phone and need to send it to someone with JTAG experience. Let me know if there is something I am missing or some suggestions you have.

Go here:
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
The problem is that you tried flashing a gingerbread rom even though your phone still had Froyo bootloaders. If you flash a gingerbread rom using one of the one click files mentioned in the guide, you'll be able to flash more GB custom roms.
Don't worry your phone is fine, you just need to read a little more and you'll be good to go.

Thank you very much for the link, the post is very through. I am getting stuck because my phone appears to not want to go into "Download Mode." Every time I press the up + down vol buttons and plug in the usb I just get the attached images and they go in an infinite boot loop.
I have tried every usb port on the computer and followed the instructions near the first of the post and uninstalled all ports which had Android or Samsung associated with them. I also tried all the different ways I could to get into download mode based on this link.
I am currently in the process of uploading a clip of the infinite boot loop I am in on Youtube and will post it if it helps.
Again thank you all for your help. The XDA community is the best!

That is the rainbow screen indicating you need GB bootloaders. Just pull your battery. You need to flash twice - second time checking the 'flash bootloaders'.
For the driver issue/phone not recognized by the computer - There is a tool in the guide called USBDeview (in the notes). Use it to make sure you have uninstalled all android related/unknown drivers. Go into uninstall programs and make sure you uninstall Samsung drivers. Restart your computer. I also run the CCleanner reg cleaner. Then restart computer again.
For Download Mode - Pull battery. Plug your USB into your computer only. Make sure you are pushing both the volume up and down buttons simultaneously. Without putting battery back in, plug your USB cable into your phone while continuing to hold volume up and volume down buttons. Keep holding volume buttons with USB plugged into phone and computer and put the battery back in.
Start guide over and read thoroughly.

Fb that's the screen I got coming back from nand back up!!! I had to flash a diff kernel with Odin to fix it

Thanks for all your help. Ironically I was doing everything correctly, but my usb cable had gone bad on me the night that it all happened. So thanks all, espicially lumin30 for the excellent guide and for FBis251 pointing me to it. After switching to a working cable and completing lumin30's guide all is now working great!
As a random side note the driver section showed up slightly differently for me (the device I had to pick was [usb composite] but once I figured that out everything went well).

Glad you figured it out

[Q] Cyanogenmod and clockworkmod questions

I know some of these questions are around the internet on google and in other threads, but try as i might ive never been able to find difinitive answers so i'm wondering if someone can help me out
a little background:
I have previously flashed xsballs ics rom (pretty much the first day it came out) and tried to root it. At this point things went horribly wrong and i soft bricked my phone. I then used the recovery guide to get back to gingerbread and all is well but...
Question 1:
I want to try cyanogen mod 7 but one question i cannot find a difinitive answer to is does the HDMI function in the currently available stable release? whenever i google this all i see is threads where people have tried the nightly and id didnt work.
Question 2:
When backing up with clockwork mod can i restore this backup and replace cyanogen if i dont like it or decide the 3d loss is too much of a hit? the reason im asking is i remember when i was stuck on froyo and every thread about getting to gingerbread involved convoluted methods of flashing kdz files. If this is the case im confused as to why there wasnt just agingerbread backup/rom i that could be restored from CWM
Question 3:
During my bricking/unbricking process i used lg flash tool as in the guide and put my phone into some kind of download/service mode which had a specific screen graphic (i think it was an exclamation mark or something). Since getting gingerbread back on ive never been able to get this screen back. When i try to put my phone back into this download mode the same key presses just give me a black screen. Is this normal?
Question 4:
Does Cyanogenmod 7 support USB OTG and pinless bluetooth pairing?
Thanks for your time

I don't have answers for question 1 and 4, but I can say a few things on 2 and 3:
_ question 2: from what I've seen, gingerbread and CM7 and CM10 uses the same baseband (the key thing to get mobile signal), and I even have 3 different nandroid backups for 3 versions. I can restore them, by CWM, over each other and still have a stable and functioning phone. And you can flash a GB/CM7/CM10 zip file over either GB/CM7/CM10 should you want to start fresh. You MAY notice minor bugs like the screen not being very responsive or alarm clock not working, that's when you would want to change the bootloader
_ question 3: I am able to get to the download mode (that's the mode you are refering to) from all 3: GB, CM7 and CM10. Just turn off the phone completely, then hold vol up, then press(and hold) power. Remove the battery if necessary, and if the phone automatically turns on right after you insert the battery, hold the vol up button BEFORE inserting the battery.

[Solved][Q] Broken boot?

Hello,
Recently (about two weeks ago) a friend of mine accidentally dropped his Galaxy Ace Plus into his toilet,
after he got it out, the phone was still on, but when he turned it off it wouldn't start up anymore.
I offered to have a look at the thing, although he already bought a new phone last week. Today he handed his Ace Plus over to me, and I mentioned that it still give a vibrate-feedback when trying to turn it on. I also found out the phone could still open in Download mode, and later I found the shortcut to the recovery (although stock's recovery has very limited options). When I went out of recovery the phone somehow started.
I went home and flashed the stock firmware of the phone (also flashed CWM and rooted the device to make some backups of data to move to his new phone), but now when I turn it off, it will still not start up when using the power button. And again, when I go to recovery and reboot the phone that way, it DOES start up).
My guess is that somehow the boot (partition?) is messed up.
I tried everything that's in my knowledge of Android 2.* phones (I've got an Sony 4.0 ICS phone myself, it works quite a bit different). I can't find a way to fix it myself, so I turned to this forums in the hope that one of you guys could help me fix his phone.
Regards, Drago
ALSO: to add, does flashing kernels work the same on these phones? Like, via fastboot with command line? I might want to try to re-flash stock kernel, hoping it fixes the boot.

Dragoboss said:
Hello,
Recently (about two weeks ago) a friend of mine accidentally dropped his Galaxy Ace Plus into his toilet,
after he got it out, the phone was still on, but when he turned it off it wouldn't start up anymore.
I offered to have a look at the thing, although he already bought a new phone last week. Today he handed his Ace Plus over to me, and I mentioned that it still give a vibrate-feedback when trying to turn it on. I also found out the phone could still open in Download mode, and later I found the shortcut to the recovery (although stock's recovery has very limited options). When I went out of recovery the phone somehow started.
I went home and flashed the stock firmware of the phone (also flashed CWM and rooted the device to make some backups of data to move to his new phone), but now when I turn it off, it will still not start up when using the power button. And again, when I go to recovery and reboot the phone that way, it DOES start up).
My guess is that somehow the boot (partition?) is messed up.
I tried everything that's in my knowledge of Android 2.* phones (I've got an Sony 4.0 ICS phone myself, it works quite a bit different). I can't find a way to fix it myself, so I turned to this forums in the hope that one of you guys could help me fix his phone.
Regards, Drago
ALSO: to add, does flashing kernels work the same on these phones? Like, via fastboot with command line? I might want to try to re-flash stock kernel, hoping it fixes the boot.
Click to expand...
Click to collapse
Try flashing some custom rom in recovery mode.
or try flashing stock rom using Jtag.
If nothing works then you should go to service center.

kk9999gada said:
Try flashing some custom rom in recovery mode.
or try flashing stock rom using Jtag.
If nothing works then you should go to service center.
Click to expand...
Click to collapse
Thank you, the first method indeed solved the problems.
I flashed the "Slimbean" ROM that has actually been released today, haha.
After that I restored a CWM Nandroid backup I created before flashing the ROM. The phone now starts normally.
Thank you very much.
Regards, Drago

Bootloops -> now Bricked

Hi guys ,
I have a Nexus S (i9023, LCD) that had bootloops, so I installed the lastest official OTA and hoped it would help.
The update worked without errors, but at the next start, the boot animation froze and the phone restarte like it did.
When trying to start the phone again later, there were only some of the keys lit and nothing happening.
Now it doesnt react to anything.
btw: a 300kOhm Jig didn't do anything, but it worked on a S2 and S3, and there was no Voltage.(no idea it thats relevant)
I think it had 4.1.1 at the start and tried to flash official 4.1.2.
So what is the easiest way to recover the phone without having to send it anywhere?
And can someone please attach AdamOutler's Unbrickable Resurrector in a compiled version? The ones here in the board are old versions, and the others on the internet don't seem safe.
And² if you apply the unbrickable mod and remove the wire, does it return to a normal state, even without the resistor?
looking forward to every help :3