Database Users

Bricked?! Halp!

I've got a 32A mt3g 1.2.
PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
I can get into fastboot. but have no recovery. and CM6.1 just sits at the CM screen forever, but I have adb access at that screen.

MotoMudder77 said:
I've got a 32A mt3g 1.2.
PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
I can get into fastboot. but have no recovery. and CM6.1 just sits at the CM screen forever, but I have adb access at that screen.
Click to expand...
Click to collapse
First of all, wrong section. Moving to General. Next time your post will be trashed.
Secondly, your not bricked. Please check your definitions.
Third, try flashing the engineering bootloader via goldcard method and then fastboot flash recovery recovery.img (Amon_RaG or ClockworkMod for MyTouch/Ion).
Then power off your phone and hold the home button while powering it back on.
You should now have a recovery. From there try flashing the rom again. If it still doesn't appear to be doing anything then do a wipe and reflash.

Thanks for the tips, ill go for that right now.
sorry for the wrong section. Im wouldve put it in the Q&A section if there was one.
EDIT:
The only guide for a goldcard I've found requires a working phone. Mine doesnt work.

MotoMudder77 said:
Thanks for the tips, ill go for that right now.
sorry for the wrong section. Im wouldve put it in the Q&A section if there was one.
Click to expand...
Click to collapse
Seriously?
myTouch 3G, Magic General
Discussion about the T-Mobile myTouch 3G, HTC Magic (general Q&A, tips & tricks)

Ok Im blind, sorry.
But still have a bricked phone. and if the MT3g section is anything like the HD2 section. the only place to get answers is the DEV section.

Your going to have to find someone with an Android phone (any Android phone will work) to create the goldcard.

No need. If you got adb access you can flash the custom recovery from there (cm 6.1 has the SU and flash_image binaries).
Then simply load the custom recovery and fix your rom/OS (flash a new one or wipe or what ever).
Take a look at my guide (check my signature) and you will find all the steps needed. Just make sure you use G recovery and NOT H.
Good luck hunting!

To add to that, what radio are you using? You only gave us your hboot.
Sent from my HTC Magic using Tapatalk

MotoMudder77 said:
...
The only guide for a goldcard I've found requires a working phone. Mine doesnt work.
Click to expand...
Click to collapse
If you put the goldcard in and boot to your bootloader and press the back key it will load your goldcard and flash the engineering spl.
mumilover said:
No need. If you got adb access you can flash the custom recovery from there (cm 6.1 has the SU and flash_image binaries).
Then simply load the custom recovery and fix your rom/OS (flash a new one or wipe or what ever).
Take a look at my guide (check my signature) and you will find all the steps needed. Just make sure you use G recovery and NOT H.
Good luck hunting!
Click to expand...
Click to collapse
He stated that the rom won't load and he can't load the recovery. His spl is S-ON so from where I sit the goldcard method is his ONLY choice.
If that doesn't work then he's pretty much SOL.

Binary100100 said:
He stated that the rom won't load and he can't load the recovery. His spl is S-ON so from where I sit the goldcard method is his ONLY choice
Click to expand...
Click to collapse
MotoMudder77 said:
I can get into fastboot. but have no recovery. and CM6.1 just sits at the CM screen forever, but I have adb access at that screen.
Click to expand...
Click to collapse
Well, i disagree :0)
Look above.
My method should work with no problems... it will actually take less then 2 min ( 70 sec if done by me... YES i timed it ;0) OR 10 sec if using a script!)
DonJuan692006 said:
To add to that, what radio are you using? You only gave us your hboot
Click to expand...
Click to collapse
Good point :0)
If you have a ****ed spl/radio combo, then all this is for nothing and there are other issues to be fixed first!

Its kinda a difficult situation. I only have adb access for a little while while @ the Cm screen, then it goes away, and Im stuck at the CM screen. I have attemped the goldcard a couple times, but I dont have the correct card, and none of mine seem to work. Wife was shopping, and could only find SanDisk cards, and it didnt work.
Radio is 2.22.23.02
Im gonna attempt anything and everything I can think of to get it to work, but I might have to just run into town and find a damn Kingston card.

SanDisk cards work, got mine sitting in a box in my closet from where I rooted my phone. It may be a procedure that's wrong, not the SD card.

Ok well I managed to get the goldcard made, but when I get into HBOOT, it scans the card and states: no image or wrong image for the sappimg.zip.
file is @ the root of my sdcard, and wont read it, yet when I dont have the goldcard setup, it reads the file just fine. same exact file.

MotoMudder77 said:
Ok well I managed to get the goldcard made, but when I get into HBOOT, it scans the card and states: no image or wrong image for the sappimg.zip.
file is @ the root of my sdcard, and wont read it, yet when I dont have the goldcard setup, it reads the file just fine. same exact file.
Click to expand...
Click to collapse
make sure it's not sappimg.zip.zip

Binary100100 said:
make sure it's not sappimg.zip.zip
Click to expand...
Click to collapse
Its not. I've managed to get 2 goldcards succefully made, verified that multiple times, but it just doesnt work. It will not read the file from the SDcard.
I can put the same file on my sdcard from my HD2 and it will read it no problem.
I might play around with it more, but for now, Im calling it a brick.

Just to make sure, have you tried downloading the sappimg file again?

DonJuan692006 said:
Just to make sure, have you tried downloading the sappimg file again?
Click to expand...
Click to collapse
Yea, I've got 3 or 4 different ones on my PC, tried all, none work. It reads the sdcard and just passes it by.
Im really stumped. Followed the goldcard method to a "T" with 4 cards, 2 actually succeed in the proccess, but niether will get the sappimg.zip to read.
After installing the card into the phone and, attempting the Hboot, the HEX gets changed on the card also, just a few values, nothing exteme
IDK if thats normal or what, but it happens.

I don't think it should change anything so that may be your problem. I'm pretty sure I looked at mine after using it and it was the same. Weird.

well last resort, gonna turn my 8gb class 6 sdcard for my HD2 into a goldcard, and check.
after putting the sappimg on the sdcard w/o formating, goldcard or anything, the MT reads the sappimg, and attempts, but gets the error, of course. So im attempting the goldcard right now.
UPDATE:
It worked, got eng SPL on the phone, figured I would just follow CM guide for rooting to verify that it will work. but Im stuck:
# Once it finishes flashing, it should ask you to reboot. Reboot and let it load to the new "htc Magic" boot screen.
# Chances are at this point that the phone will not successfully boot. THIS IS NORMAL. Simply remove and re-insert the battery, as we're not done yet!
# Download the following zip file (the stock myTouch SPL and Radio) and extract it: [1]
# Copy the two files inside the zip to the root of your SD Card
# Take the latest Amon_RA recovery you downloaded earlier and copy it to the root of your SD Card.
# Download terminal emulator from the market and run the following commands:
flash_image flash radio /sdcard/radio.img
flash_image flash hboot /sdcard/hboot_7201A_1.33.0013G_091021.nb0
flash_image flash recovery /sdcard/recovery-RA-sapphire-v1.7.0G-cyan.img
Click to expand...
Click to collapse
Items in red are the issue, if the phone doesnt boot, how am I supposed to get into market?

Done and Done! phone is working again. I guess I should've tried my nice sdcard a while ago, but I didnt want to screw it up.
Oh well. Thanks for all the tips and ideas guys!

[Q] [q] Important Question Please!

Previously I found out I had a bricked phone. I used the gfree method of rooting (which I still don't recommend). I need to get it unrooted so I can return it to T-mobile for a replacement! I was wondering if there was ANY possibly way of unrooting your mytouch 4g if it its bricked? (In my case soft-bricked) I keep getting cache errors in recovery so I know it's bricked but it's a soft-brick. But is there anyway to unroot a soft-bricked mytouch 4g?
THANK YOU for any answers possible.
Justin

Yes, very easily. Download the file from this thread. Ignore all the other instructions there. Rename the file to PD15IMG.zip and place it in the root of your SD card. Then boot into hboot by turning the phone off and turning it back on while holding down Power and Volume Down. The file will automatically be detected and flashed. When that's done your phone will be unrooted and be just like when you took it out of the box.

Thank you for responding! I'm downloading the file right now. I'll tell you what happens in a second.

Okay, I downloaded the file and renamed it like you said and put a .zip and the end and put it in my sd card. But when I went to hboot it said SD card checking Loading image image not found! I'm confused, did I need another file? Or do I have a file that I shouldn't have?
Thank you for everything.

holiday29 said:
Okay, I downloaded the file and renamed it like you said and put a .zip and the end and put it in my sd card. But when I went to hboot it said SD card checking Loading image image not found! I'm confused, did I need another file? Or do I have a file that I shouldn't have?
Thank you for everything.
Click to expand...
Click to collapse
That's the correct file. It's been a while, but I think you have to select "bootloader" from the hboot menu. Then the file will be recognized and flashed.

It still did the same thing. Do you have to take off certain files that you used to root it such as the (part7backup-1308721303) file? Do you have to make sure there is no rooted material?

glad to see someone helping you.
but why do you need a replacement? I hope it's not because you bricked you phone

It was a soft-brick, but the phone was already glitchy before I even thought of rooting.

It was a soft-brick, but it was already glitchy before I even thought about rooting.

Make sure there are no other root or unroot related files in the root of your SD. "Image not found" suggests to me that the file may be corrupt. Delete the current file and re-download one more time. Also make sure the file is named exactly "PD15IMG.zip" or it will not flash.

Do you think I should just wipe my sd card and then only put that file on? (The other file is downloading).

holiday29 said:
Do you think I should just wipe my sd card and then only put that file on? (The other file is downloading).
Click to expand...
Click to collapse
If you can afford to loose all the data on it or can back everything up, then it wouldn't hurt.

Yes I can make a backup folder on my computer. Then, I'll try the file. Again, Thank you so much!

holiday29 said:
Yes I can make a backup folder on my computer. Then, I'll try the file. Again, Thank you so much!
Click to expand...
Click to collapse
Sure thing. I hope it flashes this time. It certainly should, and has worked for many other people to restore back to stock after being bricked and/or getting cache errors in recovery. In fact, in those situations, flashing this file is all you can do.

This is STILL not working. I am very confused. I did everything word for word, but it just won't recognize the file. Do you have any idea why? And will really T-mobile check for S=OFF if I send it back like this? I have only had this phone for roughly five months.
This is what my screen says:
GLACIER PVT ENG S-OFF
HBOOT-0.85.2007 (PD15100000)
MICROP-0.429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Does anything seem out of the norm?

holiday29 said:
This is STILL not working. I am very confused. I did everything word for word, but it just won't recognize the file. Do you have any idea why? And will really T-mobile check for S=OFF if I send it back like this? I have only had this phone for roughly five months.
This is what my screen says:
GLACIER PVT ENG S-OFF
HBOOT-0.85.2007 (PD15100000)
MICROP-0.429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Does anything seem out of the norm?
Click to expand...
Click to collapse
That tells me that your phone is rooted, running the engineering bootloader, and you have the stock TMO-USA MT4G radio. That all looks normal. At this point, I have no idea why you're getting the 'image not found' error. I'm sure someone will come along that can help you out further.
On a side note, that's the second time in as many days that I've accidentally hit the Thanks button. Oh well, you get a free one!

One more thing. You're absolutely positive the file is in the root of your SD, correct? It can't be in any folders or else your SPL will not find it.

A common mistake is that you might have renamed it "PD15IMG.zip.zip."

[Q] stock DZ bricked from OTA update

Hi guys,
before I start, I must say that I have spent 6 hours reading the forum and trying everything I could, whithout succes.
I have a Desire Z from HTC, the OTA update to 2.3 has just been offered to me this morning. My phone is not rooted and I've never tried anything that isn't a click away on the market.
Here is the problem, when I launched the update, I got a "red sign" screen. I search (too) quickly on the web and found a message saying "I got it, just remove the battery and all is well". I did that, and now my phone is stuck at the htc logo.
My sdcard seems dead, my computer doesn't see it. I put a blank one in the phone but no change at all.
I have since searched what to do and tried many things.
- adb doesn't see my device (>adb devices sends a blank)
- fastboot devices says > SH0CERT00230 fastboot but I don't kwow if this is my phone or not.
On the phone, I tried factory reset, recovery, but still no change.
I tried PC10IMG.zip, but it says "main version is newer". I'm currently downloading (slowly) the newest I could find (1.72.405.2) but since I did all the small OTA updates to this day, i'm not sure this will help.
Here is what the Hboot says:
Vision PVT SHIP S-ON
HBOOT-0.85.0010
MICROP-0425
RADIO-26.04.02.17_M2
eMMC-boot
Dec 27 2010,22:19:17
Can my phone still be saved?
Thanks a lot!

You might have the faulty emmc chip problem.
There's some info on it here
If not, you could maybe try using an RUU to downgrade, there's downgrade instructions here as well as a link to an RUU.
Your fastboot is working properly, but seeing as you won't have eng-hboot, you won't be able to use most of the fastboot commands.
-Nipqer

Thanks for the links, I'm on my way to read this.
I forgot to mention that I do have the message "E:Cant mount /cache/recovery/command"
I'll be back as soon as I'm done reading.

I'm back.
I'm not sure the eMMC problem is mine, my phone seems to be more damaged than the one in this thread.
I finally understood that I must put the phone in recovery mode to use adb (newbie inside) but I still can't get it to work, I got "SH0CERT00230 offline" and it won't accept any command.
I can't downgrade either, because it requires adb to run...
I'm going to try PC10IMG with the newer rom and if it doesn't work, I'll send the phone back to htc for a replacement I think (tomorow).

You could try flash the PC10IMG via fastboot, there's some instructions here
Returning it will probably be your best option though.
-Nipqer

I tried to flash via PC10IMG on the sd card, the file is found, but "main version is older" (I said newer before, I was wrong).
I'm calling htc tomorow :-(
Thanks for the help!
At least, now I now how to root and backup my next phone

Pretty sure that error you posted is a tell tell sign of the emmc being busted
Sent from my HTC Vision using XDA Premium App

My answer has been lost in time and space...
I tried installing the newest rom I could find, via PC10IMG on the sdcard. The file is detected but I still get the message telling that the phone version is newer.
I guess I'll have to return it to htc
Thanks for the help anyway!

Hello,
I tried another time with the gingerbread wee Ruu that has been added a few hours ago and it worked!
I will now root my device an be prepared for the next time.
Thanks for the help!

[Q] unrooted Evo still shows root acc. to Sprint cust. service what now?

I once had my Evo rooted when it first came out, ran a rooted update and then did a full RUU (on the XDAwiki page) to unroot sometime around January of 2011. Since then I have ran a stock Evo, I have received and installed all OTA's from Sprint since and from what I can tell my phone is stock.
Over the last month I have been chasing down a new reception issue with my Evo. After two previous visits to two different Sprint repair facilities where I was told they performed a hard reset (pulled the battery) and updated profiles. Sprint phone service checked my local tower and "reset" it. On Tuesday I was told by phone based Sprint to take my phone in and start the insurance replacement process.
Yesterday I took my phone back into the same Sprint center that said they reset and updated my phone and was informed that I still had Superuser capabilities and my phone is rooted (which from what I can tell cannot still be the case)and therefore even though they previously claimed to have updated and worked on my phone now say they can't touch it. Sprint will send me a new phone with the caveat that I will be charged an indisputable 500 charge if my poorly functioning phone is determined to be rooted.
I have already run the RUU (in January) in the XDA Wiki to get it stock, what are my other options?
Will running it again change anything? Is there anything beyond running the RUU I need to focus on?
Thanks for any help provided.

Boot into bootloader (Volume Down + Power key from OFF) and see if it says S-OFF at the top. That might be what they are looking at. However, that isn't Superuser (su) privileges like they are saying. Sounds fishy.
Easiest thing might be to try a different Sprint location if possible.

it does say S-OFF at the top.
How do I remove that?
redo the RUU?

I am going to give this a shot
http://forum.xda-developers.com/showthread.php?t=780141
will update.

insert cust. service joke said:
I am going to give this a shot
http://forum.xda-developers.com/showthread.php?t=780141
will update.
Click to expand...
Click to collapse
From the point you're at now, there is only one way to get it to S-on. You need to install a custom recovery image, then use that recovery to flash the unrevoked S-on tool, and then after that you need to run the RUU again. You'll then be fully stock.
So, download the PC36IMG.zip I attatch. It is Amon Ra V2.3 recovery. Put the file on your sd card, not in any folders. Just on the main directory. Also place the unrevoked forever S-on tool on your sd card at this time. Boot to the bootloader, by holding power and volume down when your phone is turned off. It will scan and find the file and ask you to update. Press volume up to say yes. That will flash the recovery for you. When that is finished up, don't choose to reboot. Then from your bootloader's menu, choose 'recovery.' That will then boot you to recovery. Then in recovery, choose install zip from sd card, and find the unrevoked forever s-on tool that you put on the card. Then select to flash it. That should set your bootloader back to S-on. Once that's done, turn your phone off and boot back to the bootloader. Confirm that it now says S-on. If so, then all you need to do is run the RUU or a PC36IMG.zip of the RUU. You'll be good to go after that. Good luck.

insert cust. service joke said:
I am going to give this a shot
http://forum.xda-developers.com/showthread.php?t=780141
will update.
Click to expand...
Click to collapse
Is your phone currently on software number 4.24?

k2buckley said:
From the point you're at now, there is only one way to get it to S-on. You need to install a custom recovery image, then use that recovery to flash the unrevoked S-on tool, and then after that you need to run the RUU again. You'll then be fully stock.
So, download the PC36IMG.zip I attatch. It is Amon Ra V2.3 recovery. Put the file on your sd card, not in any folders. Just on the main directory. Also place the unrevoked forever S-on tool on your sd card at this time. Boot to the bootloader, by holding power and volume down when your phone is turned off. It will scan and find the file and ask you to update. Press volume up to say yes. That will flash the recovery for you. When that is finished up, don't choose to reboot. Then from your bootloader's menu, choose 'recovery.' That will then boot you to recovery. Then in recovery, choose install zip from sd card, and find the unrevoked forever s-on tool that you put on the card. Then select to flash it. That should set your bootloader back to S-on. Once that's done, turn your phone off and boot back to the bootloader. Confirm that it now says S-on. If so, then all you need to do is run the RUU or a PC36IMG.zip of the RUU. You'll be good to go after that. Good luck.
Click to expand...
Click to collapse
This will get your phone fixed.
Sent from my PC36100 using XDA Premium App

k2buckley said:
From the point you're at now, there is only one way to get it to S-on. You need to install a custom recovery image, then use that recovery to flash the unrevoked S-on tool, and then after that you need to run the RUU again. You'll then be fully stock.
So, download the PC36IMG.zip I attatch. It is Amon Ra V2.3 recovery. Put the file on your sd card, not in any folders. Just on the main directory. Also place the unrevoked forever S-on tool on your sd card at this time. Boot to the bootloader, by holding power and volume down when your phone is turned off. It will scan and find the file and ask you to update. Press volume up to say yes. That will flash the recovery for you. When that is finished up, don't choose to reboot. Then from your bootloader's menu, choose 'recovery.' That will then boot you to recovery. Then in recovery, choose install zip from sd card, and find the unrevoked forever s-on tool that you put on the card. Then select to flash it. That should set your bootloader back to S-on. Once that's done, turn your phone off and boot back to the bootloader. Confirm that it now says S-on. If so, then all you need to do is run the RUU or a PC36IMG.zip of the RUU. You'll be good to go after that. Good luck.
Click to expand...
Click to collapse
K2Buckley, thanks for the help. The phone automatically ran the update, but when I go into recovery and try to flash the unrevoked-son.zip I keep getting Installation aborted. When I boot back to bootloader it still says s off.
Specifically:
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in /sdcard/unrevoked-forever-son.zip
(Status 42)
Installation aborted.

insert cust. service joke said:
K2Buckley, thanks for the help. The phone automatically ran the update, but when I go into recovery and try to flash the unrevoked-son.zip I keep getting Installation aborted. When I boot back to bootloader it still says s off.
Specifically:
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in /sdcard/unrevoked-forever-son.zip
(Status 42)
Installation aborted.
Click to expand...
Click to collapse
What software number does your phone have? Is it the 4.24 GB?

software number: 4.24.651.1
build number: 4.24.651.1 CL61076 release-keys
Kernel version: [email protected] #1
Tue Jun 14 23:58:32 CST 2011
Thanks,
S

Looks like your stuck cuz of the last update like the rest of us with new evos that have the latest build 2.3.3.

insert cust. service joke said:
software number: 4.24.651.1
build number: 4.24.651.1 CL61076 release-keys
Kernel version: [email protected] #1
Tue Jun 14 23:58:32 CST 2011
Thanks,
S
Click to expand...
Click to collapse
The S-ON tool appears to be patched in the GB ROM 4.24. You likely need to
1. Downgrade back to 3.70 (use the same PC36IMG file from
http://forum.xda-developers.com/showthread.php?t=780141
It should work if your phone is truly S-OFF).
2. Remove that PC36IMG file, then copy and run the PC36IMG update for the Amon recovery that Rem3Dy gave you.
3. Remove that PC36IMG file, then flash the S-ON tool from RECOVERY, and then finally,
4. Copy to SDcard and run the PC36IMG file from step 1 again, or the RUU which you were originally using for your stock ROM. Unfortunately, the RUU for 4.24 will permanently remove the ability to reroot the phone until the devs figure it out, but if you are returning the phone, then you might not care at this point.
Hope this works for you this time.

Yeah I was gonna say the same thing. As long as you're s-off, you can downgrade back to froyo to use the s-on tool.
Sent from my PC36100 using XDA App

insert cust. service joke said:
K2Buckley, thanks for the help. The phone automatically ran the update, but when I go into recovery and try to flash the unrevoked-son.zip I keep getting Installation aborted. When I boot back to bootloader it still says s off.
Specifically:
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in /sdcard/unrevoked-forever-son.zip
(Status 42)
Installation aborted.
Click to expand...
Click to collapse
Lousy. When you took the ota, it upgraded your radio. If you're s off, try downgrading your radios back to 3.70 ruu. Then reflash your recovery, and try the s on tool again. Hopefully you can downgrade your radio, because the s on tool doesn't work on your current radio version.
Sent from my PG86100 using Tapatalk

k2buckley said:
Lousy. When you took the ota, it upgraded your radio. If you're s off, try downgrading your radios back to 3.70 ruu. Then reflash your recovery, and try the s on tool again. Hopefully you can downgrade your radio, because the s on tool doesn't work on your current radio version.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Ed zachary, you need to flash an older version radio.
Sent from my PC36100 using Tapatalk

K2Buckley, and Shorty Doggg
Thanks for all your assistance, and the idiot proof step by step instructions. I finally have S-on, and am updating to current as we speak. I am looking forward to stopping by the other Sprint repair facility tomorrow. Hopefully I can get a new phone that works again sooner than later.
s

insert cust. service joke said:
K2Buckley, and Shorty Doggg
Thanks for all your assistance, and the idiot proof step by step instructions. I finally have S-on, and am updating to current as we speak. I am looking forward to stopping by the other Sprint repair facility tomorrow. Hopefully I can get a new phone that works again sooner than later.
s
Click to expand...
Click to collapse
Glad you got it working.
Sent from my PC36100 using XDA Premium App

insert cust. service joke said:
K2Buckley, and Shorty Doggg
Thanks for all your assistance, and the idiot proof step by step instructions. I finally have S-on, and am updating to current as we speak. I am looking forward to stopping by the other Sprint repair facility tomorrow. Hopefully I can get a new phone that works again sooner than later.
s
Click to expand...
Click to collapse
Glad you got it squared away and all set. Good deal. As always, glad to help.

insert cust. service joke said:
K2Buckley, and Shorty Doggg
Thanks for all your assistance, and the idiot proof step by step instructions. I finally have S-on, and am updating to current as we speak. I am looking forward to stopping by the other Sprint repair facility tomorrow. Hopefully I can get a new phone that works again sooner than later.
s
Click to expand...
Click to collapse
Just an fyi, if sprint found your phone rooted, they may have completely blacklisted the phone, and they may not provide service on it anymore. Just giving you a heads up.

So...I thought sprint didn't care if your phone was rooted or not? From all the stories I've heard at least. This means if I try to do an insurance claim due to a cracked screen or something they won't allow it?

I Need Help

Hi , okay i lost my old MyTouch 4g from launch , and received a new one back in August. I decided to finally do the downgrade via ADB , i got through every step and when it was time to do the "manual Downgrade" i put the Rom on the root of the SD card and when i booted to the bootloader it said PD15IMG.zip was found but the nbh file wasn't found
SD Checking...
Loading... PD15DIAG.zip
No image!
Loading... PD15DIAG.nbh
No image or wrong image!
Loading... PD15IMG.zip
No image!
Loading... PD15IMG.nbh
No image or wrong image!
and it never performed a downgrade , now when i tried to reboot back to the current rom, it gets stuck at the MYtouch 4g sign
i have a G1, so im able to swap memory cards to move files if need be because im not sure if i could access the USB mass storage through the bootloader
More information i have is at the Bootloader is
GLACIER PVT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.11.04.03_M
eMMC-boot

If I see and you type what there really is, then it didn't find any PD15IMG.ZIP.
That would be either because you have your card formatted in some weird way, or because you didn't follow the guide, didn't read the multiple warnings and unknowingly named your file PD15IMG.ZIP.ZIP (because your Windows isn't set to show file extensions).
So, formatting the SD card before use with regular FAT32 and making sure the name is right will solve that.
Moreover, you should check the MD5 of the PD15IMG. It will keep looking for .nbh only if the file is wrong.

no i downloaded the PD15IMG zip file from the guide i didn't have to change anything it was already named that file, so if i format the memory card all should be good ?, would i have to worry about doing the ADB again because i had multiple reboots by taking out the battery because of being stuck at the splash screen.
EDIT: Thank You Progress was made i just Formatted the memory Card now, its performing the Update through the Bootloader to 2.2.1 with the blue side bar , i'll keep this posted with another Edit
EDIT: 2.2.1 update wasunsuccessful it getts stuck at the purple "updating" words i went to a youtube video to see what the update process would be like its supposed to go "updating, OK, OK, Unzipping"
imma try to reinstall 2.3.4 then doing the ADB method if possible
EDIT: updating to 2.3.4 does nothing but the same thing 2.2.1 update did , now im stuck scratching my head

It means that the phone is stuck updating one of the partitions, which is bad.
You could attempt to flash Panache RUU on this thing. HTC have their own downloader, inaccessible through regular modes, which is invoked when RUU is being flashed using EXE file. You might also need a goldcard for your phone to attempt it. In the Mobilicity/Panache rooting thread in General section you'll see all the info on creating a goldcard. A bit of search will get you the Panache RUU .exe file
If the RUU is successful - you'll have HTC Panache for a phone. From there, you can attempt rooting and downgrading instructions in the Panache rooting thread.
If you still have warranty - I'd use it. Flashing Panache RUU, if it won't get you luckier with PD15IMG, will be irreversible, since I don't know of MyTouch 4G RUU in .exe format.

alright i have all the necessary files such as the RUU exes i tried to make the gold card but was unable to do so using the simple Gold card method , how would i go about turning my phone into the Panache if my phone cant even turn on fully ?

HTC software running on PC doesn't need your phone to be booted, it can automatically put the phone into HTC-specific download mode from any other mode.
Run the RUU.exe while the phone is in the bootloader, for example, and see if it flashes, and if not - what error does it show.

the RUU.exe says USB error, everytime i plug my phone in through the bootloader the computer comes up with a Android 1.0 New Hardware wizard i dont know if this is interfering with the .Exe not finding the phone
EDIT: Found Android 1.0 drivers , now the error was the phone not being charged LOL! , ill keep this posted with another edit after the phone is charged, thank you for the help i appreciate it.

Yes, you'll need the driver operational.
Use Windows 7 computer, it'll automatically find and install the needed driver.

Thank You So Much for your Help i went to T-Mobile , and my insurance covered for a new phone i took the option of going for the Sensation instead of getting another Mytouch 4g and running into the same problem,
I Enjoyed this community from my First MyTouch 4g of flashing multiple ROMS , this was and is a powerful phone i wish it had more dev/hacker support with this phone