Help! Is my phone recoverable? - Desire HD General

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.

Related

[HELP PLEASE] T-Mobile MYTOUCH with VODAFONE HTC Rom - AM I ROOTED?!?!?

Ok - thanks for coming in and reading my post even though you could have skipped right on through.
I have purchased a used MT3G from craigslist (i know). I am a semi-knowledgeable "veteran" when it comes to rooting and flashing on the g1 - but the mytouch is totally new to me.
I have some SERIOUS SERIOUS concerns as to what my phone even is in the first place. I bought it with original TMobile packaging, phone says tmobile in the front and back - yet when I turn it on it's VODAFONE.
When I boot into recovery, I get the Triangle Exclamation with the phone. The rom is a 1.5 HTC rom and here is my fastboot info.
PVT 32B SHIP S-ON H
HBOOT - 1.33.0009 (SAPP30000)
CPLD - 10
RADIO - 3.22.20.17
May 8th 2009
HOWEVER - when I run the "one click root" - it says I have a 32A system. Eventually I followed the instructions for 1 click root using flash rec and flashed (downloaded) the Cyan 1.4.1a from the "recovery installer" (flashrec-1.1.2 2009-0909). They said my phone was 32A, I just went ahead and downloaded and installed - now I have the cyan recovery when I boot up my phone - I just can't flash ANY roms. I tried RAv 1.6 - for both 32B and 32A. 32A keeps rebooting my phone over and over, 32B just sits at the vodafone and hangs for 15 minutes.
After HOURS AND HOURS of reading the forms and the wiki - I'm at a complete impasse. I need some guidance. Do I have a 32A or 32B? Is it possible for 32A phones to show 32B in the fastboot? Some people need a "goldcard" to do this - I just used flashrec did I do something wrong? It seems as if some people are flashing roms with their regular SPLs - do I need engineering SPL - if so HOW do I flash SPL and radio without bricking.
I just want to flash some damn roms, or even get back to OEM and get my phone up to 1.6. It's such a bad feeling buying a phone, then bringing it home and you don't realize what you've gotten......I just want to get my phone rooted and start flashing roms and I've gotten this far.
ANY HELP GREATLY APPRECIATED!!!!!!!!
edit - the only way I've gotten my phone back to the stock HTC MAGIC rom is luckily upon first running of the CYAN recovery I did a nandroid backup and just restored to my backup after the failed rom flashes.
EDIT 2pm CST : I called T-Mobile, they can track your IMEI and Sim card every time you place a call - they CONFIRMED that my IMEI belonged to a TMOBILE MYTOUCH 3G and not any european phone. This leads me to my next question - is it possible to flash this HTC MAGIC rom onto a TMOBILE MYTOUCH 3G through fastboot, or something - WITHOUT a recovery, WITHOUT having root?
My MYTOUCH 3G is running VODAFONE everything, and it's definitely a EUROPEAN HTC MAGIC rom. Did someone install something on this phone before I got it. Please community - any help is appreciated.
A possible explanation is that someone followed Amon_RA's instructions partway through but did not finish. Specifically, they may have flashed the SPL, the recovery image for 32A and then a ROM for 32A. Since the phone is 32B, the recommendation is then to update the radio and recovery and ROM for 32B after it is rooted.
Perhaps this person rooted the phone, and then did not revert to 32B. Just a guess, though.
ok bro first lets calm down. everything is fine. all the information you need is right in front of you. first if its from europe it could be 32b and or 32a. so to check if you have root lets download a terminal app. if you dont have one pm and ill send you one. once we have that run it and type
su
if it asks for permission or just goes to
#
you are good. now type cat /proc/meminfo
for "MemTotal:" if it says 98024 or around there then you have a 32b. there that took care of what kind of board you have now we have radio and splash. your radio is .009. eng radio is .006. most likely the person that had the phone before only did have the steps. so go over them again with doing a "real" rooting. make a goldcard, get a good rec .img and have sdk working on your comp. if you need help i can help the best i can.
my touch 3g problem!! please help!!!
i bought a my touch 3g from craigslist. and when i turn it on it freezes up and says vodafone and it just stays there.. i need help to get it off can anyone help??? please
Turn it on while holding the Home key and tell us what you get? If you get a menu of options then you have a custom recovery image and you can flash a new rom ... if you just get an image of a ! then you have the stock recovery image.
Also turn it on while holding the back key, give us the information from that screen (also known as the fastboot screen) as this will tell us what recovery options are available to you.
I feel you man.
richboii8939 said:
i bought a my touch 3g from craigslist. and when i turn it on it freezes up and says vodafone and it just stays there.. i need help to get it off can anyone help??? please
Click to expand...
Click to collapse
I worked for T-Mobile and got a mytouch before launch. My MyTouch, During the 32B radio flash, fell off my desk, disconnected, and has been stuck where you are ever since.
doing MANY hours of research and trying VARIOUS different methods did not help. I since bought another, (and a nexus. DO NOT MISS THE MYTOUCH) rooted it and my original MT3G, is still stuck on Vodafone red boot screen, and has a hopefully semi-permanent place in the bottom of my shame drawer.
Mine will not respond to Goldcards, and is not picked up by ADB.
If you plug your phone in, on boot and it is recognized by ADB, then you have hope. If its completely shot like mine. I doubt you'll be able to revive it. Unless ive been missing something since July of last year. (I had it early lol).
If it is recognized.
I would...
-Get a 32B radio
-Open CMD in the radio's folder (Shift + Right click will add a button in your right click to Open Command Prompt There)
-Fastboot flash radio <insert file name here>.zip
-Adb will say "Waiting for Device"
-IF IT IS RECOGNIZED It should reboot into Fastboot and flash the Radio and you should be okay.
*Please correct me if I'm wrong. Im can root all day long, but i can barely explain it. XD*

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

Bricked Magic 32B, Any chance of repair?

After installing the latest cyanogen mod my phone started to act sluggishly. So I decided to try and unroot the device, restoring the device to its factory status using fastboot. However, I accidently used the wrong .nbh file for this. I used Sappimg.nbh (which is designed for 32A models). Chaos ensues.
The phone picked up the sappimg and overwrote the system/recovery/spl succesfully, but since it's the wrong image, my phone is bricked. It can still boot, but it will not do anything once you enter your PIN-code, an error pops up after any second of activity, force closing everything. The only thing I am able to do is connect the SD-card to my computer trough quick use of the notification bar. I can't get to my recovery or create a goldcard since it will no longer accept fastboot commands (remote: not allowed error).
Model: HTC Magic Vodafone (Netherlands)
Hboot info:
Sapphire PVT 32B SHIP S-ON G
HBOOT-1.33.006 (SAPP10000)
CPLD-10
RADIO-2.22.19.261
Does anyone have any suggestions? I haven't really tried the goldcard method yet, and I have an additional android phone available it this helps in a way.
You can make a GoldCard with the other phone and it will work in your's. You'll need to get an engineering SPL loaded on your phone before you'll be able to reflash the correct SPL. Go the GoldCard route.
Alright, I've created a working goldcard using my spare android phone. I have never used a goldcard before though, and I'm not really sure how to use it. What are the steps nescessary to flash a new spl?
You just need to grab the correct sapping.nbh for your phone, copy it to your goldcard, put the goldcard in your phone, and boot into fastboot pressing back and power. The phone will check the image then tell you to press the trackball to flash if your goldcard is working right.
Sent from my HTC Magic using XDA App
Using the Sappimg extracted from the Vodafone NL RUU.exe still gives me CID incorrect errors. I have a goldcard inserted; are there certain steps necessary to guarantee its succes? If your pc can still read it after altering the hex values it should be working right?
Meanwhile, I've poked around a bit after booting the phone up, and it turns out I can still get to certain apps, but anything that requires the home screen results in an error that force closes everything, so I can't get into setttings. I can only get to items that are presented in the notification bar like text messages or e-mails. If only I could get to USB-debugging settings I could fastboot my way out of this mess...
I've managed to fix the software part by installing a home replacement app, so I'm good for now; I'll just have to see how I can re-root the device if I want to fix the default launcher I guess
For the incorrect CID, your GoldCard may not be any good. I ran into a problem when I first made mine and it didn't work. I ended up redoing everything, including reobtaining the CID via ADB and it worked the second time around.
Yep, that did the trick! It worked this time, I managed to get the code from my own phone this time through adb, and went through the steps of creating a goldcard again. Thank you, almighty goldcard, my phone is now up and running again Even managed to re-root and re-install cyanogenmod now.
\o/

[Q] MyTouch 3G boot Issue (Recommended here for help)

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.

[Q] Some serious problems with Magic 32A.

Hi,
First of all, let me tell you what happened. I have had a standard htc magic with sense UI (perfected spl) so I done everything what was needed to upgrade my phone to other ROM. Everything was ok untill my girlfriend told me next day that she can't call me. I tried to call her, an it works but in other direction doesn't. So I decided to downgrade radio and engeniering SPL to flash other ROM and everytime I was trying to downgrade radio the phone screen turns dark. After a couple of times I came up with an idea to simply use patched RUU aplication to do it. This time it won't work either. Whats more the phone turned into s-on and it only boots into something like fastboot screen but there's nothing more like some informations about radio and stuff and RUU. And here is my question.
What can I do with my phone to bring him to life?
Is it posible to make a goldcard synthetically, I mean without pluging phone into USB to get some codes?
ps: Sorry about my english. I think my phone is more important at this time.
possible solution
Hello there,
yes, you can read the CID of an SD card from your pc too.
the CID is basically a serial number for your SD.
since S in SD stands for secure, some programmers can limit their applications to run only in the SD they were installed to by verifying the CID.
anyway, if you can access HBOOT mode (vol down + power), it would be a lot simpler flashing a basic RUU rom, then root it, install a recovery and do whatever you want.
If you choose to follow this method, I suggest you to restore a RUU with android 1.5 or 1.6, it's easier to root and you're sure everything will work. i heard 2.x version of android sotck roms for htc magic can have some problems in rooting process.
good luck to you!
I will try to get the CID of my SD card, but what's more complicated is that whatever way I want to turn my phone on it only boots with something like fastboot screen, but instead of options to choose on the screen i there's only RUU and when i plug-in the USB cable the sign changes into RUU USB. So accesing any other mode is imposible. Only the blue light mode works. :/
mikamikamika said:
I will try to get the CID of my SD card, but what's more complicated is that whatever way I want to turn my phone on it only boots with something like fastboot screen, but instead of options to choose on the screen i there's only RUU and when i plug-in the USB cable the sign changes into RUU USB. So accesing any other mode is imposible. Only the blue light mode works. :/
Click to expand...
Click to collapse
What carrier is your phone from and what is your current hboot info? You should be able to see it from the RUU fastboot-like screen.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
hboot info:
sapphire PVT 32A SHIP S-ON H
HBOOT-1.76.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
The phone works in Orange PL
I would be very thankful if You, or anyone could help.
Download this, plug your phone into the computer and turn it on so that you have "RUU USB" on the screen, the double-click the downloaded file and run it. See if that gets you anywhere.
The same situation as later. Everything goes ok until the radio is being updated, then the screen fades black. The whole process ends at 36%.
Your going to have to see if mumilover adds his comments here.
Sent from my HTC Glacier using Tapatalk
Hi, Not sure if this helps, check out this thread as it is a good source and also there is an article on flashing without the sd card. http://forum.xda-developers.com/showthread.php?p=12210523#post12210523
mikamikamika said:
sapphire PVT 32A SHIP S-ON H
HBOOT-1.76.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Click to expand...
Click to collapse
You got radio/spl combo mismatch.
Run this command and give us the result:
Code:
fastboot getvar version-main
Are you sure that the above info is correct and updated?
version-main is 3.05.401.1
I made a mistake, hboot is actually 1.76.0008.

Categories

Resources