[Q] ADB does not see MyTouch 4G - myTouch 4G Q&A, Help & Troubleshooting

I used Visionary+ to s-off via term em and then flashed hboot-eng via term em, rebooted and now it will not get past the mytouch 4g splash screen. I can get to bootloader and it lets me go from hboot to fsatboot with no problem.
I have downloaded the drivers and can see the device on USBDeview but cannot get ADB Devices or ADB shell to see it.
Any help would be greatly appreciated.
By the way I do not consider myself a noob, just stumped.
running windows xp
phone info:
GLACIER PVT ENG S-OFF
HBOOT-0.76.2000 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Aug 20 2010, 16:51:01

pjw111 said:
I used Visionary+ to s-off via term em and then flashed hboot-eng via term em, rebooted and now it will not get past the mytouch 4g splash screen. I can get to bootloader and it lets me go from hboot to fsatboot with no problem.
I have downloaded the drivers and can see the device on USBDeview but cannot get ADB Devices or ADB shell to see it.
Any help would be greatly appreciated.
By the way I do not consider myself a noob, just stumped.
running windows xp
phone info:
GLACIER PVT ENG S-OFF
HBOOT-0.76.2000 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Aug 20 2010, 16:51:01
Click to expand...
Click to collapse
You have these correct?
-HTC driver.exe thats on phone's SD CARD when you first get it
-Android SDK updated
ADB doesnt work in fastboot or recovery last time I check, correct me if im wrong
While phone is on turn on usb debug in settings and then open CMD on pc....Type adb shell and then type adb devices
After that report back here

I have installed them.
Thats the problem the phone will not load past splash. I can only get to hboot usb or fastboot usb

pjw111 said:
I have installed them.
Thats the problem the phone will not load past splash. I can only get to hboot usb or fastboot usb
Click to expand...
Click to collapse
In fastboot can you use fastboot to flash things still?

I think i could if I can get adb to recognize the phone
or do you mean from an sd card?

pjw111 said:
I think i could if I can get adb to recognize the phone
or do you mean from an sd card?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4066552&postcount=2
Old but still relevant to what you need, fastboot can flash different things, so you can get the phone to stock or working condition.
If recovery isn't working you can put a new one, you should try finding CWM and use that in fastboot with
fastboot flash xxx.img
Then you can use recovery

pjw111 said:
By the way I do not consider myself a noob, just stumped.
Click to expand...
Click to collapse
then why did u post this in the development thread

Thanks i will let you know if i get it to work.
totally forgot about this...

Related

recover Magic 32A from fastboot [with beer prize]

Hello, i updated my magic with the wrong ROM and now nothing works except FASTBOOT (vol down + power). everything else just freezes to the red vodafone screen. What can i do from here?
Here's the info:
Sapphire PVT 32A SHIP S-ON H
HBOOT-1.33.0010
CPLD-12
RADIO-3.22.20.17
Please please with anything on top help?
ok
let's make things interesting. mods feel free to sticky this...
i really need a solution this weekend. i'll send three bottles of the best local beer to whoever solves my problem.
go!
Do you have a Nandroid backup of your original ROM? If so - see here
http://code.google.com/p/android-roms/wiki/NANDROID_Fastboot
If not, I'm sure a quick search will show someone has posted a full backup somewhere on here.
Sorry...didn't notice before that you have the Perfect SPL. I suggest looking here instead -
http://forum.xda-developers.com/showthread.php?t=547133
alexdroid said:
Hello, i updated my magic with the wrong ROM and now nothing works except FASTBOOT (vol down + power). everything else just freezes to the red vodafone screen. What can i do from here?
Here's the info:
Sapphire PVT 32A SHIP S-ON H
HBOOT-1.33.0010
CPLD-12
RADIO-3.22.20.17
Please please with anything on top help?
Click to expand...
Click to collapse
Have done the same ..as you
I used adb get recovery to work again from fastboot
keepitnang said:
Sorry...didn't notice before that you have the Perfect SPL. I suggest looking here instead -
http://forum.xda-developers.com/showthread.php?t=547133
Click to expand...
Click to collapse
tried that, fastboot gives me the "remote: not allow" error.
alexdroid said:
tried that, fastboot gives me the "remote: not allow" error.
Click to expand...
Click to collapse
Yeah...that's because your phone has the Perfect SPL - it won't allow a fastboot connection. The article I linked to shows you how to change the SPL and enable this. Having said that, have you tried stian230's suggestion concerning connecting via adb to restore a recovery image?
Have a look at Amon_RA's thread for his excellent recovery image. This shows how to push the image to your phone and boot to it -
http://forum.xda-developers.com/showthread.php?t=530492
keepitnang said:
... have you tried stian230's suggestion concerning connecting via adb to restore a recovery image?
Have a look at Amon_RA's thread for his excellent recovery image. This shows how to push the image to your phone and boot to it -
http://forum.xda-developers.com/showthread.php?t=530492
Click to expand...
Click to collapse
adb does not recognize my phone (all the drivers are ok, fastboot can see it). all the guides dealing with this said to make sure i have USB debugging enabled, but i can't access my phone to do this.
changing the spl seems to permanently void the warranty (not sure about this)...
K...sorry...this is where my n00bness runs me into a brick wall. The only way I know of to recover in this instance based on what you have said is to go ahead and flash a 'friendlier' SPL. Perhaps someone infinitely cleverer than I knows of another method though?
alexdroid said:
adb does not recognize my phone (all the drivers are ok, fastboot can see it). all the guides dealing with this said to make sure i have USB debugging enabled, but i can't access my phone to do this.
changing the spl seems to permanently void the warranty (not sure about this)...
Click to expand...
Click to collapse
ADB will find your phone if you try a little while.
I promise
Just take it easy do not stress.
Try the phone off. or try recovery even if you do not get in recovery adb believe that it is the in recovery .
certainly sounds a bit strange but I did it that way
i just can't get adb to recognize my device. i tired on xp and 7, unistalled and reinstalled usb drivers and nothing.
all the guides mention tunring on USB debugging, but i can't get into android to do that. all i have is the damn fastboot. is there any other way to turn on usb debugging?
edit: apparently, adb isn't supposed to work in recovery mode. and since i can't use fastboot, because of my SPL, i'm locked out. any other ideas?
does not sound good. but I had the same problem a week ago. I had flashed a ROM and used the wrong port 32A. phone had a "semibriked" I only had access to fastboot and hboot.
I also have perfect spl. But after many attempts the adb found my phone.
I had an empty sdcard with only recovery-RA-sapphire-v1.5.2H.img on it.
is there any other method to change spl, or make fastboot work? the goldcard thing looks crazy hard...

Q What should i do?

T-Mobile USA MyTouch 3G 1.2/Fender with 3.5 MM Jack
Sapphire PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009,22:33:27
Ok my problem is i stupidly deleted my girls default home launcher when i was gonna use the adwlauncher but the phone rebooted, now it wont load android at all. I've tried the sappimg.nbh and the sappimg.zip but neither will update correctly since my security is on. I cant flash a new rom either since i have no recovery either. Is there anyway i can change my spl to an engineer to get more hboot options unlocked or should i just report my phone stolen and pay the deductible for th new recovery phone, please help you guys i have tried and read tons of threads and have failed miserably lol
You need to reset the device from fastboot...
Look at the menu and you will find it.
You can also just flash your official RUU...
To turn on RUU mode type this:
Code:
fastboot oem rebootRUU
Then just start your ruu update.
Don't start doing all kind of stupid ****... try the above before you make your self a goldcard!
Alright man thanks for the help i'll report back when im done.
I reset the device then it just loads the rom im currently on ( htcclay's TCBY 1.3dsf 2.2 froyo) reboots then hangs on the splash screen. How do i flash or type in that code about the ruu?
Edit**
The phone can only accept calls coming in, but theres still no way of using the launcher it's completely blank cuz of my accident. Im guessing the reset doesnt reinstall the needed drivers or apks to factory setings.
To Get into fastboot power the phone off and the press back + power and hold them down until the fastboot screen comes on. Then try the fasboot commands from the post above in a Windows command prompt. Hope it work for you. If it does please report back, because I am desperately trying to unroot my phone and go back to stock so I can sell it when I upgrade. Thanks.
d12unk13astard said:
The phone can only accept calls coming in, but theres still no way of using the launcher it's completely blank cuz of my accident. Im guessing the reset doesnt reinstall the needed drivers or apks to factory setings.
Click to expand...
Click to collapse
If you got adb connection, then install the launcher using this command:
Code:
adb install -r xxxxxxx.apk
(where xxxxxxxxx.apk should be replaced by the name of the laucnher apk)
ADB confuses the hell outta me lol. ADB = SDK correct? I've tried using it and following direction to push/install from my main drive c/ but can never get it to work right. Guess im just screwed and will have to pay the deductible, i do appreciate the help tho you guys.
I followed the unlockers guide and made a goldcard and with that was able to get back to recovery woohoo, thanks fo rall the help, i just had to really really focus and actually try our adb lol. Mods can lock this now please.

[Q] [FASTBOOT] HTC MAGIC 32A bricked?

specs:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
what i have done:
http://forum.xda-developers.com/showthread.php?t=605239 (the upgrade part)
with the files from *urgh* cant find the link again.. *search in history*
edit; cant find the url, f***, anyway, the filenames was "update-hboot-1.76.2007-signed.zip", "NewRadio.img"
what i want to do:
get a new ROM on the phone, with 2.0+ with sense
i can't flash recovery with fastboot, however, i can boot into 1 with fastboot boot /path/to/img in CMD.
however, that does not seem to work, i suspect it has something to do with the errors im getting on fastboot.
the errors are:
SD Checking...
Loading... [SAPPDIAG.zip]
No image!
Loading... [SAPPDIAG3.nbh]
No image or wrong image!
Loading... [SAPPDIAG2.nbh]
No image or wrong image!
Loading... [SAPPDIAG.nbh]
No image or wrong image!
Loading... [SAPPIMG.zip]
No image!
i have no idea what happend =3 im such a noob on this.. =(
would be very happy if someone could help me ASAP, as i don't have any other mobile at the moment.
oh and, i can't boot into the ROM i've tried to "install" with carz recovery img, the rom "Magic13" that i got from here, somewhere..
actually, i would be very happy if i could just get it back to its original shape, hardrest and all that doesnt seem to work either..
1. These errors are not in fastboot, but in hboot-mode...
SD Checking...
Loading... [SAPPDIAG.zip]
No image!
and blah-blah-blah
2. Your phone is not bricked
3. To get right combo hboot/radio with S-OFF and abiltiy to install custom roms you must do this: http://forum.xda-developers.com/showpost.php?p=5526163&postcount=1
5[Strogino] said:
1. These errors are not in fastboot, but in hboot-mode...
SD Checking...
Loading... [SAPPDIAG.zip]
No image!
and blah-blah-blah
2. Your phone is not bricked
3. To get right combo hboot/radio with S-OFF and abiltiy to install custom roms you must do this: http://forum.xda-developers.com/showpost.php?p=5526163&postcount=1
Click to expand...
Click to collapse
i can't do the RUU because i can't boot my phone, its stuck on splash screen, so the program cant find the phone.
sorry, i should have mentioned that too.
comoba said:
i can't do the RUU because i can't boot my phone, its stuck on splash screen, so the program cant find the phone.
sorry, i should have mentioned that too.
Click to expand...
Click to collapse
1. Remove battery, wait 5-10 seconds, place it back
2. Turn phone on by pressing and holding Back + Power (phone should load into fastboot)
3. Connect to PC, if connected successfully - text 'fastboot' will change to 'fastboot usb'
4. Run RUU
that doesnt seem to help, it (the program) still gives usb connection error 170, but i can access it from fastboot in cmd.
=/
comoba said:
that doesnt seem to help, it (the program) still gives usb connection error 170, but i can access it from fastboot in cmd.
=/
Click to expand...
Click to collapse
Error 170 links to USB connection error.
Make sure that you've installed Android SDK Tools (with drivers package), HTC Sync (with drivers / or drivers only).
In Android SDK Tools there are two utilities: /platform-tools/adb.exe and /tools/fastboot.exe
You can check connection with PC when executing:
adb devices (in normal-mode)
fastboot devices (in fastboot-mode)
If any utility returned serial number - so you don't have any problems with usb connection and can try install RUU
5[Strogino] said:
Error 170 links to USB connection error.
Make sure that you've installed Android SDK Tools (with drivers package), HTC Sync (with drivers / or drivers only).
In Android SDK Tools there are two utilities: /platform-tools/adb.exe and /tools/fastboot.exe
You can check connection with PC when executing:
adb devices (in normal-mode)
fastboot devices (in fastboot-mode)
If any utility returned serial number - so you don't have any problems with usb connection and can try install RUU
Click to expand...
Click to collapse
the only thing im missing on that list is htc sync, so ill download it and try again, i have adb and fastboot, but im not sure that adb can connect to the phone in fastboot ( since i can't boot to ROM )
e; adb and htc sync cant find the devices, as suspected, probably due the fact that i can't boot the device other then with "fastboot boot <recovery img>" in fastboot-usbmode.
and the program still can't find the phone after installing htc sync (same error).
comoba said:
the only thing im missing on that list is htc sync, so ill download it and try again, i have adb and fastboot, but im not sure that adb can connect to the phone in fastboot ( since i can't boot to ROM )
e; adb and htc sync cant find the devices, as suspected, probably due the fact that i can't boot the device other then with "fastboot boot <recovery img>" in fastboot-usbmode.
and the program still can't find the phone after installing htc sync (same error).
Click to expand...
Click to collapse
Yeah. Adb works only in normal-mode, but fastboot.exe works in fastboot-mode.
So...
Load into fastboot-mode
Run command
Code:
fastboot devices
Does it return serial number?
5[Strogino] said:
Yeah. Adb works only in normal-mode, but fastboot.exe works in fastboot-mode.
So...
Load into fastboot-mode
Run command
Code:
fastboot devices
Does it return serial number?
Click to expand...
Click to collapse
yes it returns "HT95PKF03141 fastboot", but what do i do with that?
Your computer can see phone, but you have to change usb-cable or usb-port.
Sent from my A7-040 using Tapatalk
5[Strogino] said:
Your computer can see phone, but you have to change usb-cable or usb-port.
Sent from my A7-040 using Tapatalk
Click to expand...
Click to collapse
oh ok... that makes sense, i think, because i've been using a unorignal cable since my original cable is borrowed out.
who knew a cable could make such a hassle.
comoba said:
oh ok... that makes sense, i think, because i've been using a unorignal cable since my original cable is borrowed out.
Click to expand...
Click to collapse
actually, same error with original cable...
maybe it's the OS? im using win7 64bit.. hmm, ill try find a computer with a 32bit OS.
Edit; got a hold of a winXP computer, it seems to work.
what's a good ROM for atleast 1.6 or higher with HTC Sense?
comoba said:
Edit; got a hold of a winXP computer, it seems to work.
what's a good ROM for atleast 1.6 or higher with HTC Sense?
Click to expand...
Click to collapse
Congratulations)
If you are on 1.76.2007 / 6.35.XX.XX so you can try this:
http://forum.xda-developers.com/showthread.php?t=1025330 (Android 2.3.3 with Sense)
or with Android 2.1 but more native (stable, fast and smooth)
http://forum.xda-developers.com/showthread.php?t=778083
http://forum.xda-developers.com/showthread.php?t=822531
a few questions about the guide posted, since i haven't done anything yet other then the RUU so i could atleast use the phone...
do i really need a goldcard? i've read the guide, and it doesnt seems to do anything but edit my sdcard, which seems weird since it works to the phone already and it seems i already have root, because 'adb shell' gives me #, and i downloaded superuser, which doesn't seem to be any issue, but i still have S-On, so i'm a bit confused about that.
where do i get the SPL & HBoot? the links seems to be missing in the guide.
i guess i should flash new SPL and HBoot before saying this, but the error in hboot still exists after RUU.
thanks for all the help =)
comoba said:
a few questions about the guide posted, since i haven't done anything yet other then the RUU so i could atleast use the phone...
do i really need a goldcard?
Click to expand...
Click to collapse
Every time if you want flash official ROM that is not for your country/operator you need goldcard. In general, phone has own CID (example HTC__037 - Indonesia), ROM has list of compatible CIDs. While flashing ROM is checking list with phone's CID. If they are not equal - you will get error. Goldcard emulates cid 11111111 which is always in ROM CID list.
comoba said:
but i still have S-On, so i'm a bit confused about that.
Click to expand...
Click to collapse
Yeah, to do S-OFF you must flash engineering bootloader. Hboot which compatible to radio 6.35.XX.XX is hboot 1.76.2007
comoba said:
where do i get the SPL & HBoot? the links seems to be missing in the guide.
i guess i should flash new SPL and HBoot before saying this, but the error in hboot still exists after RUU.
thanks for all the help =)
Click to expand...
Click to collapse
SPL and HBoot and Bootloader are same things (in general, when people write manuals)
And yes, you need flash HBoot 1.76.2007 - you will get more abilities (like fastboot commands)
HBoot 1.76.2007 ENG S-OFF here: Download Flash via custom recovery

Can't install any rom on ny Magic, please help

Hi.
I have an 32A HTC Magic.
I don't know what got wrong but I have NO working ROM on my device.
I have Amon Ra 1.6.2, SPL-OFF, Can get into recovery, can get into Fastboot mode.
Tried flashing some ROMs (they installed 100% completely) but when I reboot the logo just shows "htc MAGIC" and nothing happens.
Please what should I try to do?
Your help will be very much appreciated.
Best regards and sorry for not so great english.
Okay, the thing is:
I can get into the Fastboot screen, but cant get into Fastboot USB mode. So no way of sending ADB commands from my laptop.
Also, no way to get into HBOOT. Even from the Fastboot screen, pressing VOL DOWN doesn't do anything.
What the heck do I do? (
It can be caused by stucked buttons.
Tear down the phone
Clean parts
Assemble all back
p.s. Please post spl-info (first 5 rows in fastboot screen) to avoid software incompatability
5[Strogino] said:
It can be caused by stucked buttons.
Tear down the phone
Clean parts
Assemble all back
p.s. Please post spl-info (first 5 rows in fastboot screen) to avoid software incompatability
Click to expand...
Click to collapse
Thank you very much, here is the data:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.10.18
Aug 21 2009, 18:19:15
Your help is very much appreciated. Im still stuck with the Magic.. Have tried everything all night
Best regards
Okay, got into HBOOT finally. I then tried flashed the sappimg.zip - but half way through it said invalid model id.
Now I don't have Amon Ra recover, and Fastboot looks like this now:
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.0006 (SAPP10000)
CPLD-12
RADIO-2.22.19.261
May 27 2009 19:06:41
I tried another sappimg.zip and then in HBOOT but HBOOT doesn't find the sappimg.zip anymore.
Any good advice?
OMG, why? Why you did it? You are successfully half-bricked your magic...
update:
1. Make goldcard
2. try to flash 2.53.707.2 SEA WWE test-signed
http://www.4shared.com/file/160198404/66d482a/RUU_Sapphire_HTC_Asia_WWE_2537.html
Cause Im a bit stupid I guess ...
One thing though, I can't even get my computer to recognize my Magic.
Nothing happens when I plug it to the USB port. Not showing up in Device Manager.
I have tried two mini USB cables, same thing.
Guess Im totally screwed?
It is driver-related issue.
You need explore Windows Device Manager (My computer (right click) / Manage / Device Manager)
There must be Android USB Devices in tree.
You can also install USBDEVIEW
32bit OS: http://www.nirsoft.net/utils/usbdeview.zip
64bit OS: http://www.nirsoft.net/utils/usbdeview-x64.zip
p.s.
1. adb must return serial number when phone in normal state after command "adb devies"
2. fastboot must return serial number only in fastboot-mode after command "fastboot devices"
If you see serial number - no problem with adb/fastboot
slkdk said:
Hi.
I have an 32A HTC Magic.
I don't know what got wrong but I have NO working ROM on my device.
I have Amon Ra 1.6.2, SPL-OFF, Can get into recovery, can get into Fastboot mode.
Tried flashing some ROMs (they installed 100% completely) but when I reboot the logo just shows "htc MAGIC" and nothing happens.
Please what should I try to do?
Your help will be very much appreciated.
Best regards and sorry for not so great english.
Click to expand...
Click to collapse
Hi, slkdk,
Have you ever tried the "RUU_Sapphire_HTC_Chunghwa"
(in Traditional Chinese/English)
You just need to connect your phone with PC, turn on the phone with back+power, and then execute the "RUU_Sapphire_HTC_Chunghwa" on PC.
I remember that Sapphire_HTC_Chunghwa will help you with all the radio/SPL/ROM directly back to the Android 1.5 stock.
Good luck!
yuanlin0823 said:
Hi, slkdk,
Have you ever tried the "RUU_Sapphire_HTC_Chunghwa"
(in Traditional Chinese/English)
You just need to connect your phone with PC, turn on the phone with back+power, and then execute the "RUU_Sapphire_HTC_Chunghwa" on PC.
I remember that Sapphire_HTC_Chunghwa will help you with all the radio/SPL/ROM directly back to the Android 1.5 stock.
Good luck!
Click to expand...
Click to collapse
Just note, but not all phones are Taiwanese Chungwa. Installing ROM for another region (mismatching by CID) will raise "cid error" and half-brick.

[Q] android newbie help, tmob mytouch 4g read but still having issues

Hi my first android phone that I bought off someone. It's stuck at the tmobile splash screen. I can get to hboot and here is what it says
Glacier PVT SHIP S-ON
Hboot-0.89.0006
Microp-0429
Radio-26.13.04.19_M
emmc-boot
Jul 15 2011, 16:45:17
- I've the stock 2.2.1 PD15IMG.zip but it flashed a message that the rom is old
- Put the 2.3.4 PD15IMG.zip and it gets all the way to confirmation if I want to flash it. I press the up arrow and on step 1) bootloader it just says "-updating"
I've installed the sdk and usb drivers (the drivers are installed and my pc sees the android device in hboot and it redetects if I go to fastboot) but when I run adb devices no devices are listed. I've tried multiple drivers, editing the .inf file etc. without luck.
I've tried the downgrades but nothing works. I don't get the PU fail so I'm not sure if I have the bad emmc. Any advice is appreciated.
Thanks
Did you do the part in the guide where you downgrade your current software number so the phone thinks its flashing a new version?
THEindian said:
Did you do the part in the guide where you downgrade your current software number so the phone thinks its flashing a new version?
Click to expand...
Click to collapse
thanks for the input, I did try to downgrade but from what I've read I need adb and when I type in the adb commands no device is listed. Fastboot commands work and I can serial and other info.
The device is dead. Read more on "stuck updating bootloader".
Jack_R1 said:
The device is dead. Read more on "stuck updating bootloader".
Click to expand...
Click to collapse
ok thanks for the heads up this really saves me time.
jedisurfer said:
ok thanks for the heads up this really saves me time.
Click to expand...
Click to collapse
Hit his button to thank him, he deserves it

Categories

Resources