[Q] MyTouch 3G boot Issue (Recommended here for help) - myTouch 3G, Magic General

I went though some of the forums and didn't quite find what I was looking for, BUT a friend on Reddit pointed me over to this forum for help. I loaded Engineerings SPL on to my phone and when I booted up the phone I got a totally new boot screen saying "HTC Magic" After about 20 minutes I realized my phone isn't going to boot at all, I thought no big deal and tried to unroot my phone with the unlocker website and the sapping.nbh file failed during installation. (The last two items had an odd error) BUT when I rebooted my phone it now had the green mytouch 3g loading screen but again failed to boot. And thats it, this is where I am stuck.
I Have a My Touch 3g 3.5MM jack phone and I was simply trying to load a custom rom onto my phone, I can access fastboot and the android recovery console (Thing for wipe and update.zip from sdcard) But everything I have tried fails! I am really starting to stress out about this but a I was told it doesn't seem to be very serious if I can access all the menus like that. If you need anymore info I will be checking the thread regularly. Sorry for causing the trouble I am probably just another pest who made a dumb novice error , for that I am sorry. But if anyone could help me out it would be much appreciated.
EDIT!: Also I forgot to add I have GoldCard from before my phone broke, not sure if this will still work but it might help.

Post there all fastboot info, ALL.
Also the outcome of this command done in fastboot mode
Code:
fastboot getvar version-main
When you refer to "the android recovery console (Thing for wipe and update.zip from sdcard)" do you mean android stock recovery or custom recovery?

Im trying to get the data from that fast boot thing but Im kinda new to all this in order to get that data I hook my phone up to pc with usb cord start up cmd prompt and type
cd\
AndroidSDK\tools\adb
then type in that command? Kinda lost on what im doin there.
And how do I find out if it is stock or custom? it has the symbol for the FlashRec app in the backround though if that helps.
But the stuff on the top of the fast boot is.
Sapphire PVT 32A Ship S-ON G
HBoot-1.33.0013 (SAPP31000)
CPLD-13
Radio-2.22.19.26I
Oct 21 2009, 22:33:27 (Some weird date?)
Trying to type it into cmd prompt straight from cd\ doesn't work. I need some way to mount the device from fast boot it seems

http://forum.xda-developers.com/showthread.php?t=734617

mumilover said:
http://forum.xda-developers.com/showthread.php?t=734617
Click to expand...
Click to collapse
What does this do for me? My phone is stuck in an unusable state almost I cant root it at this point.

THANK YOU!!!!
THANK YOU SO MUCH! My phone is 100% fixed and running a shiny new OS! I can't thank you enough!

LemonFondler said:
THANK YOU SO MUCH! My phone is 100% fixed and running a shiny new OS! I can't thank you enough!
Click to expand...
Click to collapse
Good to hear. Now make a nandroid backup and don't fix what isn't broken.

LemonFondler said:
THANK YOU SO MUCH! My phone is 100% fixed and running a shiny new OS! I can't thank you enough!
Click to expand...
Click to collapse
What did you do after getting that link to get your phone fixed? That way if someone else gets stuck in the same boat they'll know what you did.

Related

Stuck at vodafone screen< HELP?!?!?!?!?!?

i rooted my mytouch and was trying to revert to the 32b board and preformed all of these commands, all of which were successful,
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.2.0G.img
but now my phone is stuck at the red vodaphone screen, please if anyone can help it would be greatly appreciated.
how long has it been stuck at that screen for? did u keep it on for a few minutes? try taking out the battery for a few minutes, then re inserting it.
run fastboot into recovery on computer and it will wait for device. plug phone in without battery then put battery in phone and it should throw phone into recovery .
alrite i was able to get into fastboot an i reflashed sappimg, hopefully all will be good i think i'll just stick with 32a until i figure out what i did wrong, thanx all
Hang on, Firstly you said reverting back to 32B. Then you said you'll stick to 32A? Which do you have? You run a risk of bricking the phone putting the wrong firmware on it.
I have a t-mobile mytouch, when i rooted it the board ends up being 32a (im pretty sure everybodys is like that) so i started to follow the "daredevil steps" to change the board to 32b but that created the stuck vodafone screen
adelco93 said:
I have a t-mobile mytouch, when i rooted it the board ends up being 32a (im pretty sure everybodys is like that) so i started to follow the "daredevil steps" to change the board to 32b but that created the stuck vodafone screen
Click to expand...
Click to collapse
Yeah I think it was stuck because you need to install a ROM first.
MOD EDIT
Moved to general forum as not related to android development
Breakthecycle2 said:
Yeah I think it was stuck because you need to install a ROM first.
Click to expand...
Click to collapse
Is there any solution?
robotician said:
Is there any solution?
Click to expand...
Click to collapse
ya bro. he didnt flash a 32b rom. thats all that was left. when you dont have a rom and revert back it sits at the splash because the phone is looking at you or whoever saying "ummmm ya i dont know what to do now?? rom???" lol. its an easy fix. have fun all!!!! yeah!!!!!!!!!!!!!!!!!!!!!!!!!!
One problem is that you can not see the red text "Recovery Mode" on the red background. Someone had the same problem on another forum.
Slick_42 said:
One problem is that you can not see the red text "Recovery Mode" on the red background. Someone had the same problem on another forum.
Click to expand...
Click to collapse
Can you provide a bit more info on this? This might lead to somewhere. I read some folks have red background with blur logo (maybe mean the recover text is hidden there)? I will be happy if it is in deed in recovery mode with red background. However, my bricked phone has red background with clear logo.
I have this from a german site
http://www.android-hilfe.de/vodafone-htc-magic-forum/3419-nach-flash-handy-startet-nicht-mehr-2.html
roughly translated: he thought that he stuck on the start screen but actually was in fastboot mode. he just couldn't see it trough the red Vodaphone screen. He pressed home+power and could load the backup from th PC into the phone.

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...

Splash screen catastrophy...

Hi everyone!
I'm terribly sorry if I write something that's been solved. But i searched throughout this forum as well as the internet, and I'm desperatedly turning to you guys,
because I'm completely lost
So I have two HTC Magic, the one writes in fastboot:
32A SHIP S-ON H
H-BOOT-1.76.0009
CPLD-12
the other:
(As I know) is a 32B (but that's all I know so far) because when I turn it on, it only shows the vodafone logo and hangs forever...
Yes I tried to boot up with "volume-down" button, tried with "home" button, with "back" button, and also with "home"+"back" buttons; I tried to take out the battery for 10-20 minutes, but it always shows the vodafone splash screen...
UPDATE Now I remember what happened to 32B Magic: I tried to flash the recovery via fastboot
bit it sad "FAILED (remote not allow)" I found out, that maybe I have perfected SPL. Than I followed this "[How-To] Fix perfected SPL (fastboot remote: not allow)" tutorial here in xda-devs,
and after I flashed the ROM "v2.16.151.1", happened this splash screen mis(t)ery... Could it be, it's bricked?:S Was it the wrong ROM? How should I have known which is good??
And just in case I have an other problem with the 32A one as well. I followed the "TheUnlockr.com one click root" tutorial, ok, at least i tried, but when I try to flash the recovery-RA-sapphire-v1.7.0H.img in recovery flasher in the phone it says:
"Backup FAILED: Could not run command."
PLEASE! SOMEONE! HELP! I have these two great phones for... almost nothing. I'm totally desperate...
Is saying a "go to hell" or a "you are totally dumb" so hard?
it's already 88 views... I don't think noone has a helpful or useless advice.
You and i are in the same boat. I just ran into the same issue today. Lemme know if you figured it out i'm dying to find out also. Hopefully someone here has the correct answer.
For the one that won't boot into fastboot (back+power), hboot (volume down+power), recovery (home+power), or the regular OS, you've bricked your phone.
I have no experience with the one-click root method so I'm not going to comment on the other.
I can tell you, I spent some weeks with searching, and there is no exact answer... not until some competent and experienced volunteers start to move their asses and look after these tiny losers, us. I say sorry to those "volunteers" for the previous expression...
DonJuan692006 said:
For the one that won't boot into fastboot (back+power), hboot (volume down+power), recovery (home+power), or the regular OS, you've bricked your phone.
I have no experience with the one-click root method so I'm not going to comment on the other.
Click to expand...
Click to collapse
Thanks for your reply DonJuan692006, that was the answer I was afraid of...
Ok, I consider that the one which hangs is bricked (oh hell).
But what is with my other problem?
Again: On the 32A the Recovery Flasher says "Backup FAILED: Could not run command." I tried to flash the recovery via fastboot USB but it sad "FAILED (remote not allow)"
So the question is: Is it something with the SPL? Do I need to flash a sappimg.nbh with goldcard? If yes which one should I flash exactly?
Again: PLEASE!!! I know there are a bunch of guys out there who know these issues and their potential solutions.
UPDATE:
I solved the issue with the 32A by following a guide from wiki.cyanogenmod.
Well, if surely noone has a word about my (other) bricked HTC, I consider this case as closed...

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.

Help! Is my phone recoverable?

Hi All
I am hoping someone can help me out. When i switch my phone on it loads up a black screen with HTC in the middle, and 4 exclamation marks, one in each corner of the screen, and will not switch on.
My phone is rooted and i have ENG S-OFF. I have clockwork recovery installed but cannot boot into it. I cant boot into bootloader but i can run fastboot commands.
So far i have tried the following;
Flash several RUU's, they seem to run smoothly upto the part where they write the sent IMG's, then i get a UNKNOWN ERROR 150.
Update with PD98IMG.zip by running fastboot command "fastboot update PD98IMG.zip", it sends the files to the phone then i get an error when its writing the images, something about links being too long.
Unfortunately the phone will not recognise the SD card either
Im hoping someone can help me out, as ive been without my phone for 3 weeks now, and its driving me insane
Thanks
Jody
Jody I feel your pain as I have a similiar problem.
Phone is running 2.2.1, rooted, Radio S-OFF, ENG S-OFF but won't boot into the bootloader. Tried running 1.32 RUU to downgrade, but comes back with an "unknown error."
Fortunately in my case, the phone works fine, its just that I was trying to upgrade to gingerbread.
If anyone knows a fix for this it will be much appreciated.
I am by no means an expert but a problem with writing files should point to the SD card being bad shouldnt it?
Give this thread a go: http://forum.xda-developers.com/showthread.php?t=749707
Looks like someone with the same problem, some possible fixes in there.
Thanks for the suggestions so far, ill give them a try and report back.
Just noticed also, when the phone is on the black HTC exclamation mark screen and plugged into the laptop, if i un plug it, it switches to a white screen similar to the bootloader one, but without the 3 androids on the bottom. At the top of the screen it now says "ACE PVT SHIP S-OFF RL". Anyone know what the RL is about?
Cheers
Jody
ItsJody said:
At the top of the screen it now says "ACE PVT SHIP S-OFF RL".
Click to expand...
Click to collapse
If you had ENG S-OFF, it should say something along the lines of:
Code:
ACE PVT ENG S-OFF
If you had this before, and it's now changed, it could be a problem with HBOOT. What were you doing the first time around when it broke?
retznto said:
If you had ENG S-OFF, it should say something along the lines of:
Code:
ACE PVT ENG S-OFF
If you had this before, and it's now changed, it could be a problem with HBOOT. What were you doing the first time around when it broke?
Click to expand...
Click to collapse
I was trying to restore my nandroid backup via fastboot to see if i could sort the SD card not being recognised issue i was having.
Is HBOOT BOOT.IMG?
HBOOT is the bootloader, nandroid won't have backed it up. I'm not totally certain about how HBOOT works, but you could try using this, to restore ENG S-OFF (and possibly HBOOT too). Be very careful when messing with HBOOT though, from what I gather, it's very easy to brick a phone if you mess it up.
Cheers for that, prob is phone is not recognised by ADB so i cant run any ADB commands
Its weird how the RUU runs fine until writing the images, then comes up with the error about not being the correct rom for the device.

Categories

Resources