Hello everyone. I'm experiencing a slight issue with my MT4G. I'll try to explain as clear as possible. Whenever I plug my phone into the laptop which I rooted and flashed with, the phone would freeze, reboot, and get stuck at the royal ginger splash screen. The searches I did in CK's RG1.2, Q&A didn't pull any similar results.
I setup ADB correctly on my laptop
I installed the HTC drivers that came with the phone on SD, (cleared out any old drivers with USBDeview)
Rooted w/ gfree method exactly as OP stated, got S=Off, installed Eng Bootloader
Flashed RG 1.2 exactly as OP stated
Everything is fine and dandy with the ROM (except Wifi not auto connecting when I get home).
I used the OEM MyTouch cable and my OEM Samsung Vibrant cable...same results. Reboots and sits at spalsh screen. Should I reinstall drivers even though it read my phone's serial# fine before in the command window "adb devices"? Any help would be appreciated. Thanks fellas, fellowettes.
well, don't all answer at once now. j/k
here's some music for you while you read...
Related
These are the steps i used to set up my drive(may not work for everyone dont see why though)
I don't include a step for installing HTC Sync and its drivers as ADB only worked for me when the phone was on and in sync mode, also because the pdanet install wrote over them when i installed
1.Download pdanet for android Here(this will install the proper drivers)
2.Install Pdanet on comp no need for it on phone so if it fails dont worry. Have phone plugged in during install
3.Boot into hboot(vol dwn+power)
4.Boot into recovery(vol up+power to see menu)
5.Unplug phone then plug it back in
Make sure you have debugger on before going into recovery
Now you should see your device as Recovery when you adb devices in command.
If you see 2 devices try disabling(not unmounting) your usb mass storage and then upluggin and plugin the phone back in
I really appreciate it but...
Well i woke up this morning to this new thread, tried your EXACT 5 steps with deleting all traces of the old HTC SYNC drivers and software. Still a no go. The device STILL shows up twice and then disappears. Also disabled through DEVICE MANAGER the MY TOUCH SLIDE USB MOUNT. Unplugging and plugging back in does NOTHING. I am so sick of this it hurts. FOR THE LOVE OF ROOT PLEASE HELP ME TO FIND AN ACTUAL SOLUTION.
According to another person in the forum, another couple of steps need to be added here.
check the #3 post of the other adb thread for more details (I can't link yet :-( )
After installing the pdanet: install htc sync, download the sdk, then install latest drivers.
Then continue with the rest of the process
I haven't had a chance to try it, but thought I would share to see if it will help.
If it helps, we should prolly amend the first post here.
thecracker said:
According to another person in the forum, another couple of steps need to be added here.
check the #3 post of the other adb thread for more details (I can't link yet :-( )
After installing the pdanet: install htc sync, download the sdk, then install latest drivers.
Then continue with the rest of the process
I haven't had a chance to try it, but thought I would share to see if it will help.
If it helps, we should prolly amend the first post here.
Click to expand...
Click to collapse
I believe you're talking about me. I would just point out that I was listing what I did, not nec the steps needed to get the phone to show up in adb devices. Its not clear you need to install pdanet or htc sync.
Both of those drivers let me see the phone in adb devices when it was on, let me issue commands like adb reboot recovery. But neither of those drivers ever had the phone show up except for briefly after clicking recovery from hboot and going away once the recovery triangle showed up.
Finally when I removed all traces of the device driver and installed the (r3) driver from the sdk. The next time I tried it, it worked out for me.
I think a lot of people are misreading the steps or being ham-fisted in their approach. This method is as much an art as it is a science at this point.
seek and you shall achieve.
- faylix / local
Mytouch slide rooted Eugene's Update-1
I'm sry, i was just trying to make sure that any successful attempts were communicated.
I hope i didn't cause more harm then good
dsamuels39 said:
Well i woke up this morning to this new thread, tried your EXACT 5 steps with deleting all traces of the old HTC SYNC drivers and software. Still a no go. The device STILL shows up twice and then disappears. Also disabled through DEVICE MANAGER the MY TOUCH SLIDE USB MOUNT. Unplugging and plugging back in does NOTHING. I am so sick of this it hurts. FOR THE LOVE OF ROOT PLEASE HELP ME TO FIND AN ACTUAL SOLUTION.
Click to expand...
Click to collapse
I did the same thing you did and had the same problems you had. I went to try it on my laptop which is windows vista 64bit (pc is w7 64bit). I was still having the same problem, not detecting anything and it would show up twice or three times then disappear. I installed sync that comes stock with the SD card (I had sync from the HD2 installed). I already had PDANET installed on my laptop. Anyways having doing the same thing over and over which seemed to be half a million times it all the sudden worked. So it will "catch" sooner or later. Just keep doing it. As long as you have the proper sync installed and you dont have an error with you android 1 in the device manager then it will work sooner or later. I know its a MOFO, I've been doing it for 2 days stright now and just barly got it rooted.
Good Luck.
alas it was a no go for me
I havent changed anything with my ADB since it was setup for my G1 and I can still find the device and enter commands like "reboot". Does this mean that my ADB is setup correctly for my Slide?
I got my phone used so I do not have much info following up to my problem, but here's some info none the less.
I got my phone in dec.2010. Rooted and updated to Cyanogenmod 6.1 the same day. The very first time I plugged my phone into USB it recogized it. Afterwards in Windows 7 32bit I kept getting "usb device has malfunctioned". What I really found odd was that when the phone is turned off and plugged into usb I get the "usb device has malfunctioned" error. I am continuously changing to the new roms - currently COS Gingerbread 4122011. My phone IS recognized through fastboot, in recovery I get the same previous errors, in the OS my computer doesn't even notice that I plugged anything into it. I have seen on google about Desire users having corrupted 'misc' partitions (MTD0). Is this a possibility? If no one knows, post me a link of your misc partition from your fully functioning USB G1 and I will test it.
Goto console or terminal emulator and enter
Cat /dev/mtd/mtd0 > /sdcard/mtd0.img
Then post a link to the img.
I hope to get this figured out, I hate having to transfer files and roms wirelessly.
Thanx everyone XDA-Developers. ×D
Sent from my HTC Dream using XDA App
Correction
Cat > /dev/mtd/mtd0 /sdcard/mtd0.img
There is also an mtd0ro in /dev/mtd as well.
I created both but have no way to 'post a link'
So, I'm just passing on the correction for others
Sent from my HTC Dream using XDA App
Have you try to use the usb driver removal tool? And re-install the google usb driver?
Phil - thanx for the correction.
Been - yes I have used "usb deview". I removed every usb driver, pulled mobo battery on my desktop to reset the chipset, I've used 2 stock usb cords, 1 moto usb cord, and 1 generic fat usb cord. No avail. Thanx for looking at my post.
Sent from my HTC Dream using XDA App
Something that I found that you might want to take a look.
http://www.ntcompatible.com/Desperately_need_help_---_USB_Devices_Not_Recognized_t32356.html
See if this will help your problem.
thanx for the link, but that is the same process I've been trying for weeks now. I do believe I may have corrupted something in mtd0.
The only place usb works correctly is in fastboot, and my computer detects it immediately.
Also in 'dmesg' I see SMDxxxxx errors, not flooding just during startup, it says "smem find (14, 40) wrong size 16242" and other similar messages, SMD_DATA1 - SMD_DATA7 SMD_DS SMD_RPCCALL SMD_DATA11 SMD_GPSNMEA SMD_DATA5_CNTL - SMD_DATA7_CNTL. I will try to post my dmesg when I get to my desktop.
Edit: Thank You Philip for sending me your .img files. I see you have a Rogers Dream. Unfortunately editing the image for my device CID and flashing the image using this command : flash_image misc /sdcard/mtd0.img Yielded the same results. Without adb I cant post my dmesg. I also noticed when hex editing the img files, my mtd0.img had a line "NBHLoadsuccess" where the Rogers did not have that line, everything else looks the same.
Here is a link to a post from a Desire forum, about USB Brick http://forum.xda-developers.com/showthread.php?p=6641266#post6641266
I know alot about Android, but I do not know if I can edit the Desire image and flash it to my G1. I am also not sure if maybe a patch has been applied to the img file in the post. I am getting very frustrated with my G1. Although I do truly love my phone COS Gingerbread is the best.
Sent from my HTC Dream using XDA App
Sorry about that. My phone is cyan 6.1.0 the 2708 version, perhaps that's the mod you're seeing.
About the nbh tag you found, isn't nbh the stock rom?
Sent from my HTC Dream using XDA App
I do believe .nbh is stock rom extension.
I'm now thinking about downgrading and unrooting. Then Re-root and upgrade in hopes to fix this.
Here is my setup
SPL: 0013d
Radio: 2708
Recovery: Amon Ra V1.7
Rom: Cos Gingerbread 4122011
CID: T-MO010
That sound like the best way to go.
Yep, that's exactly what I would do in your situation
Sent from my HTC Dream using XDA App
OK, so after unrooting and downgrading my USB still only has function through fastboot. I downgraded to RC29 and nothing. I am stumped, if fastboot works I would not think that my USB hardware is going bad. Anybody else have an idea?
Still no luck. I have read through my "dmesg" and compared it to my brothers "dmesg" - he has a 32A Magic 1.2, but everything looks the same and he has full USB function.
Really nobody has this problem?
Just filling time
one more post and I can post in development.
I am still having this problem. Maybe someone in development will have some insight.
I have noticed that the first time my phone is connected to a computer ( as in the first time ever) Windows will atleast tell me "a device has malfunctioned". Then if disconnected and reconnected windows doesn't recognize that anything has been connected, I have my Device Manager window open while plugging and unplugging, no response. My phone charges fully from USB or AC.
Same problem
I am having a similar problem. My G1 works fine except for USB. USB does not even work in fastboot mode. When I plug it into the PC (more than one, XP and Win7) the connection shows USB\\VID_0000&PID_0000\5&64DAA3C&0&1.
I had this problem before I upgraded to Cyan6 from 1.6. I hoped the upgrade would fix it but it did not.
Flash a rom in recovery
I still have not found a solution. I have flashed many roms, froyo by lazlo, cos ds by roalex, biffmods leaving on a jet plane, and others, still the same outcome. I have gone as far as unrootin and rerooting, tried all combinations for radio and hboot. Fastboot still works over usb tho.
I also noticed that in my dmesg when I plug in USB it thinks it is on AC.
Sent from my HTC Dream using XDA App
First let me get the stats out of the way in case it's a compatibility issue (doubtful):
Mytouch 3g 32b
Hboot 1.33.2005
Radio 2.22.23.02
Running on the last cm6 nightly (307, i believe)
Using this kernel: http://droidbasement.com/db-blog/?p=1531
All flashed through recovery.
Ok, so the problem..
Following this guide, http://forum.xda-developers.com/showthread.php?t=532719, I successfully got the ADB to work properly (calling "adb devices" on a terminal returns my device). However when I boot the phone into fastboot, connect it to the PC via USB and call "fastboot devices" through the terminal (yes, I first cd to the android-sdk/tools folder), it returns nothing. Calling something like "fastboot reboot" simply returns "<waiting on device>" indefinitely.
I googled for HOURS last night searching for a solution but to no avail. I uninstalled the drivers via the Device Manager and tried the PDANet method, but nope. Uninstalled drivers again, rebooted everything, and reinstalled using the method posted in the above guide again, pointing it to the google/usb_drivers folder, just in case I had f*'d up somewhere along the way. I just ended up with the same problem. ADB works. Fastboot doesn't. What am I doing wrong? :/
Basically, I'm stumped. While it's not completely necessary to get this working, I'd like to free up some ram on my phone (http://forum.xda-developers.com/showthread.php?t=831139) and for this I need fastboot. I'm not that noobish so I'm willing to experiment. Any help is appreciated.
Nobody? :/
Thanks to my persistence I finally got it working. I'll share in case anyone else has the same problem.
Apparently there were still old HTC related devices under the Device Manager that would not show even when I clicked on "Show hidden devices." I fixed this by adding a new system variable.
Variable name: devmgr_show_nonpresent_devices
Variable value: 1
This allowed me to see a bunch of HTC labeled grayed out devices under 'Disk drives' and under 'Universal Serial Bus controllers,' some grayed out USB Mass Storage Devices and one USB Composite device which I believe was also a culprit. Uninstalled all of them.
I then restarted the process of setting up ADB using these drivers, mediafire.com/?wzdjcmowziw, which I got from the guide I link to in the first post. Then when I hooked up the phone to the PC under fastboot mode, I used the drivers supplied by PDANet. Worked immediately.
Thanks for all the help. (sarcasm)
Hi,
I recently got ahold of a european XT610 which I rooted and flashed to CM7 without problem. Unfortunately I missed the warnings which said not to run bootstrap after installing cyanogenmod... and now I have the infamous bootloop. It gets to the CM loading screen, but goes on indefinitely from there. I know the answer is to restore the motorola sbf, however I can't seem to get my phone to communicate at all via usb. I installed motorola drivers and RSD and all in windows, but the phone seems to ignore the USB completely. I'm normally a linux guy, so I when I tried to plug it in there and watch the output of dmesg, absolutely nothing came up. Holding R, M and power when I plug in the usb causes a black screen after a bit of the motorola logo, but still no USB. Tried a few different cables, and checked them with other devices to confirm they're working.
So any ideas on how to recover the phone?
Update:
I discovered the main step I was missing was that the bootloader can be accessed by holding down both volume buttons and the power with the device off. For some reason I still couldn't get windows to recognize the correct drivers, even after installing the motorola driver package, but good old linux saw it without a problem. Following these instructions I was able to do a quick SBF and now all is good in the world!
same probleme for me?
ObsidianOps said:
Hi,
I recently got ahold of a european XT610 which I rooted and flashed to CM7 without problem. Unfortunately I missed the warnings which said not to run bootstrap after installing cyanogenmod... and now I have the infamous bootloop. It gets to the CM loading screen, but goes on indefinitely from there. I know the answer is to restore the motorola sbf, however I can't seem to get my phone to communicate at all via usb. I installed motorola drivers and RSD and all in windows, but the phone seems to ignore the USB completely. I'm normally a linux guy, so I when I tried to plug it in there and watch the output of dmesg, absolutely nothing came up. Holding R, M and power when I plug in the usb causes a black screen after a bit of the motorola logo, but still no USB. Tried a few different cables, and checked them with other devices to confirm they're working.
So any ideas on how to recover the phone?
Update:
I discovered the main step I was missing was that the bootloader can be accessed by holding down both volume buttons and the power with the device off. For some reason I still couldn't get windows to recognize the correct drivers, even after installing the motorola driver package, but good old linux saw it without a problem. Following these instructions I was able to do a quick SBF and now all is good in the world!
Click to expand...
Click to collapse
Can you tell me more about it please : i've made the same mistake...
I nead a real lesson !:laugh:
Hi,
I wiped my current rom in TWRP and something went wrong with the rom I was trying to install so I have a phone without an OS now (LG G2 802). Now I am stuck in TWRP. The backup for the phone is on my laptop but I cant seem to get my laptop to recognise the phone any more.
When I connect my phone to the laptop via USB it shows up in the device manager but with an exclamation mark. I've tried pointing to the LG folder under program files for the drives but for some reason they dont work and the device is still showing up with the yellow exclamation mark in the device manager. These drivers were working before this happened (I've connected the same phone to my laptop quite a few time before, including using ADB to root it earlier) so I don't know why this is happening.
Any help would be appreciated, I am completely lost right now.
Thanks...
You can use an otg cable with a thumb drive too.. The driver for this is under Google, see if you can find it. There was a guide somewhere but I've lost the location :/
*edit* FOUND IT
http://forum.xda-developers.com/showthread.php?t=2557248
Sent from my LG-D802 using xda app-developers app
Got around it...phew!!
As it turned out I had a few issue, for anyone else in the same boat here is what I did to get my phone back up.
First, I cant thank Koush enough for his amazing work, after installing his universal adb drivers the laptop started recognizing the phone immediately (as to why it didnt with the official drivers, I have no idea).
The drives can be found here: http://koush.com/post/universal-adb-driver
Once the phone was recognized by the laptop I knew I had some hope, I tried to adb sideload a few roms but kept getting error messages. I looked up TWRP for the latest version 2.7 and updated to that from 2.6.3.2 and the Roms started working immediately. Now I am happily running the PAC KK rom (which by the way looks fantastic).
Hope this helps anyone else who is in the same boat.
Regards,
Tariq