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...
Related
There wasn't any info that was an exact fit for the Docomo, but I gave it a go.
It's a 32B SAP2000
It had a perfected SPL 1.33.0006, so I flashed a 1.33.0009 SPL.
It got to Fastboot, but now showed H instead of G and the radio was different.
Fastbooted into RA's 1.5.2 recovery.
Instead of applying my nandroid backup I thought I'd apply the radio from HTC site. The one for 32B.
Rebooted to the unboxing screen for 20 seconds, then back to HTC Magic splash screen.
Since then I can't get fasboot or recovery.
Putting in the battery causes the phone to instantly vibrate a little and come on.
Holding the different combinations of buttons whilst the cable is connected/unconnceted does nothing.
I can't issue fastboot commands via cmd prompt.
Hmm... this seems like a challenge, no? Anyone think they know where to even begin to de-brick this?!
No challenge, it's impossible! unfortunately once you've bricked it only HTC can help. Try to get it replaced if it's under warranty (tell them that you've tried to install an official update and that something went wrong).
No fastboot (back+power) or recovery (home+power) = dead phone
Shame. Ah well. Time to bid on another one!
This time I'll hunt down with Android 1.5; will make life so much easier!
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...
I just rooted my Mytouch a couple days ago and everything worked perfect and i did it without bricking my phone. I was trying to get the supercsdiv4 rom, but i needed to flash the lateset radio and heres where the problem started. the radio tried to flash was 2.22.23.02. I used the recovery image to flash it and then when i rebooted the phone it stayed stuck at the splash screen and i cant get into fastboot or recovery anymore. it just boot to the splash screen and stays there. I know i cant get my phone back but i want to know what i did wrong so that i dont ever do it again. maybe it was because the radio i had was a 32a radio and this radio i tried to flash might have been 32b but im not sure why that wouldn't work if my phone is 32b
here was my system
pvt 32b
Hboot 1.33.2005
radio 3.22.20.17
have you tried taking the battery out for a bit.. relax a while, then put it back in and try to get into recovery mode (home and power)
this actually happened yesterday and my phone was off the whole time so it has had plenty of time to rest. My phone is truly bricked
well im sorry to hear that, but i have no idea what you did wrong, unless you did flash a 32a over a 32b or the other way around, im sure that could really mess up the phone.
may be a useless idea but have you tried a hard reset
1. With the phone turned off, press and hold the HOME and BACK buttons.
2. Briefly press the END CALL/POWER button while continuing to press the HOME and BACK buttons.
3. When you see the screen with the 3 Android
images, release the HOME and BACK buttons, and then press the TRACKBALL.
i have no idea if it will do anything but might as well explore EVERYTHING.
Similar Problem (Partial Brick?)
Not to take anything away from clint1225 but
I have a similar problem and didn't want to start another thread.
I tried unrooting my devices using the method
described at theUnlockr.com. Everything was fine up until I tried using
their sappimg file (said it worked for all old magics).
At the hboot stage, it found the sappimg but the update failed.
However, the magic now says:
SPL-1.33.0006 (SAP50000)
Radio- 2.22.19.261
Ship S-On G.
It's a 32A version.
I had an engineering spl and 6.35xx radio before I attempted to unroot.
Oh I'm not able to access recovery but I can access
fastboot (computer can't find it though under "fastboot devices")
Other than that, it's stuck at the first splash screen.
Any advice/tips?
Sorry for the long post and thank you.
Good luck to you too, clint1225!
UPDATE *Similar Problem (Partial Brick?)*
In the adb, the serial number
of the htc magic is coming
up under "fastboot devices".
However, if I try to
flash a recovery for example, the adb
returns "remote access not allowed".
I've read about the gold card method
but my phone won't boot up properly
(stuck at splash screen) and I can't
access recovery. Only fastboot seems to be
working.
Any help is greatly appreciated.
Thanks!
Take it for what it's worth coming from a newb. But from my understanding if you can reach your phone with Fastboot your a NOT bricked. But this is what I have heard here on XDA, I haven't proven this myself.
Check around and hopefully with fastboot you can get your phone back. Good luck.
I did the exact same thing a few weeks back. I flashed a 3.22 radio over my 2.22 radio, thinking it's an upgrade but after it reboots, it wont get past the logo screen. I spent the whole day trying to find ways to recover it but cannot find any. Thank god I have warrenty on it so I went to the Tmobile store, told them I updated it and when it restart, it got stuck on the logo screen. They gave me a new phone and told me dont f-up this one. Now I'm afraid of updating my phone to the 6.something radio.
Update *Similar Problem (Partial Brick?)*...again.
MasterColdSoul and koolpre,
Thanks for the tips and luck!
I figured it wasn't a total brick so I searched
the whole day on google and xda.
What I can tell you is that I now have a functional phone.
I used the rogers "mandatory" update (2 sappimgs) to
get my phone (rogers 32a) working again (boots fully).
However, I now have the SPL 1.76.0010 which means
I've lost root functionality and it's harder to get root.
But I could use the phone to make a gold card and get root again.
Boy I'm glad this worked! I should have learned my lesson
but I will probably try to root, hehe!
Thanks to google search and xda community!
koolpre said:
I did the exact same thing a few weeks back. I flashed a 3.22 radio over my 2.22 radio, thinking it's an upgrade but after it reboots, it wont get past the logo screen. I spent the whole day trying to find ways to recover it but cannot find any. Thank god I have warrenty on it so I went to the Tmobile store, told them I updated it and when it restart, it got stuck on the logo screen. They gave me a new phone and told me dont f-up this one. Now I'm afraid of updating my phone to the 6.something radio.
Click to expand...
Click to collapse
just because the radio starts with bigger numbers doesn't make it an update. 3.22 was the old radio and 2.33.23.02 is the latest radio so you were actually downgrading your radio and thats why your phone brick. Just letting you know because you seem to be under the wrong impression. Dont make that mistake again. just do a little research to find the latest radio.
Hey everyone.
I was rooting my MyTouch 3g w/3.5mm this morning. I'm following the instructions from here ( http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/ ). I had apparently messed up when I was at the restart after flashing sappimg.zip onto the phone and was stuck at the HTC Magic Screen. I restarted my phone by holding down the Reject Call + Volume Down key and told it to flash sappimg.zip onto the phone again so I could redo it correctly. Unfortunately, it's stuck at the "[1] SYSTEM - UNZIPPING" stage. I'm afraid to turn it off because it says to not power off the device.
So, yeah, have I bricked my phone or is there a way to restart this process so I can successfully root?
Thanks much, and have a happy holiday.
EDIT: This sort of resolved itself, but now I can't get into recovery mode. :/
Rhaseo said:
Hey everyone.
I was rooting my MyTouch 3g w/3.5mm this morning. I'm following the instructions from here ( http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/ ). I had apparently messed up when I was at the restart after flashing sappimg.zip onto the phone and was stuck at the HTC Magic Screen. I restarted my phone by holding down the Reject Call + Volume Down key and told it to flash sappimg.zip onto the phone again so I could redo it correctly. Unfortunately, it's stuck at the "[1] SYSTEM - UNZIPPING" stage. I'm afraid to turn it off because it says to not power off the device.
So, yeah, have I bricked my phone or is there a way to restart this process so I can successfully root?
Thanks much, and have a happy holiday.
Click to expand...
Click to collapse
So your flashing the engineering spl for the first time or are you flashing the stock spl back?
Binary100100 said:
So your flashing the engineering spl for the first time or are you flashing the stock spl back?
Click to expand...
Click to collapse
I'm flashing the engineering spl onto there for the first time.
It appears that being stuck at the Magic screen is normal according to a different (but similar) guide from the Cyanogen Wiki. Would it irreparably damage my phone if I removed the battery despite it being at the "Unzipping" screen for Sappimg (as I was unzipping sappimg for a second time) and proceeding with CyanogenMod's guide instead?
EDIT: It appears my phone just turned off on it's own (battery probably died). I'm going to try CyanogenMod's instructions and see if that works.
EDIT 2: So, I reflashed it with the sappimg that Cyanogen has on his wiki. So everything was smooth sailing until I got to the Recovery step. I cannot, for the life of me, to get it to boot in recovery mode. I hold HOME+POWER but nothing pops up.
EDIT 3: And it appears as if I've bricked it.
Rhaseo said:
I'm flashing the engineering spl onto there for the first time.
It appears that being stuck at the Magic screen is normal according to a different (but similar) guide from the Cyanogen Wiki. Would it irreparably damage my phone if I removed the battery despite it being at the "Unzipping" screen for Sappimg (as I was unzipping sappimg for a second time) and proceeding with CyanogenMod's guide instead?
EDIT: It appears my phone just turned off on it's own (battery probably died). I'm going to try CyanogenMod's instructions and see if that works.
EDIT 2: So, I reflashed it with the sappimg that Cyanogen has on his wiki. So everything was smooth sailing until I got to the Recovery step. I cannot, for the life of me, to get it to boot in recovery mode. I hold HOME+POWER but nothing pops up.
EDIT 3: And it appears as if I've bricked it.
Click to expand...
Click to collapse
Will the rom start? If so, you didn't brick it.
Do you have the Engineering SPL on it? What SPL version do you currently have on there? Remember that if you have the T-Mobile US MyTouch w/3.5mm jack then you MUST have 32B recovery and radio and STOCK (1.33.0013) SPL before flashing a custom rom.
Best way to do it is to flash your custom recovery (I suggest Clockwork Recovery for Mytouch/ION devices) by fastboot.
Afterwards then flash your stock (S-ON) SPL back and then boot to recovery to flash your rom.
REMEMBER!!! YOU DO NOT HAVE A 32a DEVICE! DESPITE WHAT THE SPL SAYS... IT'S NOT TECHNICALLY A 32a DEVICE!!! You MUST treat is as a 32b.
Binary100100 said:
Will the rom start? If so, you didn't brick it.
Do you have the Engineering SPL on it? What SPL version do you currently have on there? Remember that if you have the T-Mobile US MyTouch w/3.5mm jack then you MUST have 32B recovery and radio and STOCK (1.33.0013) SPL before flashing a custom rom.
Best way to do it is to flash your custom recovery (I suggest Clockwork Recovery for Mytouch/ION devices) by fastboot.
Afterwards then flash your stock (S-ON) SPL back and then boot to recovery to flash your rom.
REMEMBER!!! YOU DO NOT HAVE A 32a DEVICE! DESPITE WHAT THE SPL SAYS... IT'S NOT TECHNICALLY A 32a DEVICE!!! You MUST treat is as a 32b.
Click to expand...
Click to collapse
Oh, wow. That explains why I bricked the phone. The Amon_RA Recovery I put on there was 32a... I'm an idiot.
The phone won't start up at all. :/ Looks like I'm out $100 or so.
Thanks for that, though. I was going to give you a "Thanks" but it appears the button has disappeared for me.
Rhaseo said:
Oh, wow. That explains why I bricked the phone. The Amon_RA Recovery I put on there was 32a... I'm an idiot.
The phone won't start up at all. :/ Looks like I'm out $100 or so.
Thanks for that, though. I was going to give you a "Thanks" but it appears the button has disappeared for me.
Click to expand...
Click to collapse
Can you still get into fastboot?
Binary100100 said:
Can you still get into fastboot?
Click to expand...
Click to collapse
Nope. It won't turn on at all.
Rhaseo said:
Nope. It won't turn on at all.
Click to expand...
Click to collapse
Won't boot, no recovery, no fastboot.
If it looks like a brick, if it sounds like a brick then it's probably...
I have a similar problem. I purchased this phone and it just almost works. It boots into fastboot just fine but not recovery. Here are the specifics as they stand now.
Sapphire unknown 32A ship S-on H
CLD 13
Radio 3.22.20.17
May 8 2009, 21:02:32
I made a good gold card...tried the 2010 spl...still hangs during unzip step of the flash process. Any other ROM and I get a main version older error.
Fastboot info version main 2.53.707.2
cid T-MOB010
Any help would be greatly appreciated.
Nice job on probably bricking your phone. You've got the myTouch 1.2 which means you just flashed an incompatible radio. Congratulations!!! I honestly not sure what to tell you. Which sappimg are you trying to use to get the engineering SPL?
Like i said...it was like this when I bought it.
I'm going to try to do a poorman's JTAG...wish me luck.
jonk26.2 said:
wish me luck.
Click to expand...
Click to collapse
Good luck! You can do it!
If you have any questions along the way, please don't hesitate to ask.
JTAG did in fact de-brick my MT3G 1.2 (bought from ebay) the first time I tried it. I made the mistake of flashing the stock ROM, so I would get to the "touch the android to begin" screen and couldn't get any further without a data plan. It wasn't until I probably flashed the wrong sappimg in a root attempt that I started experiencing the stuck at unzipping/FAIL-PU/remote signature verify fail problem...
FYI, I tried flashing radio 2.22.28.25 (the one from the OTA) using JTAG and the radata command, and it fixed my USB. I haven't experiemented much beyond that, but I'm planning to try some more things this weekend.
Moderators, I'd like to suggest merging this thread with http://forum.xda-developers.com/showthread.php?t=773368 and http://forum.xda-developers.com/showthread.php?t=771622 since they all seem to be discussing the same problem.
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.