Database Users

Bricked/Blind/Barely alive magic, no recovery screen (SPL ****up) any suggestions?

Hi
similar to an other thread here if tried to change my SPL
and never recovered.
I can still get the blue led going using TrackBall + EndCall buttons.
The orange led lights up when I connect the usb cable.
But I cannot see it from the pc in any way (adb/fastboot).
there is some life in it but not a lot, have not seen the screen light
up at all.
Would it be possible to get a new bootloader/spl on it? Perhaps using
some kind of automatic update mechanism that is build in using an
update.zip file on the sd card?
Any help is more than welcome.
abe

*bump*
hmm, post needs al least 10 chars... should be enough now...
Has everyone also drawn a blank on this?
abe

Try downloading the ruu from your phone's official reseller.

T-Mobile USA standard OS.
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.

Sorry to hear that. I was thinking of installing Haykuro Apps to SD ROM and it needs to change the SPL. But I think not worth taking a risk.
Can you tell a little bit more which ROM were you planning to install?
Which SPL did you update to?
Which ROM did you have at the time of SPL update?
Which thread or instructions did you follow if any?

Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
@Reignzone
I do have a nandroid backup but I cannot get back into recovery mode,
or fastboot mode or anything... the pc does not recognize it either.
@technicolor
I installed the Cyanogen recovery image and was able to install
one of his rom's. It worked fine but then I wanted to install
a Hero rom and I wanted to update the SPL.
Used the cyanogen recovery to update the spl using an update.zip
file. the phone restarted the "android" update screen came on
briefly and it never came back on...
changing the recovery rom should not be an issue,
and normally I think you do not need to flash your spl at all any more.
you can do a lot with the fastboot mode and one of the recovery roms
mentioned by Reignzone
abe

Reignzone said:
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Click to expand...
Click to collapse
This is the same advise you gave me yesterday on my bricked MT3G, but if you can't enter recovery mode, a nandroid backup ain't gonna help much, is it?
Also, any cupcake downloads are not going to help either, if you can't fastboot or enter recovery.
I appreciate you trying to help, but if you pay attention to the OP (and my own post), you'll see that your advise isn't going to solve anything.

For starters:
My advice to have those of you who are in need to take an approach that allows you to backtrack you work. Perhaps you left out various details of your issue or process taken in order to end up where you're at.
Your bitterness isn't appreciated for my having misread the problem.
YOU are the one with the F***** device, not me.
Anyway, all that aside; you might try to read-up on various threads that could be of some help. Google search, HTC support, ADB, etc.
There's always something to be done.
Good luck.

abeman said:
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
Click to expand...
Click to collapse
forum puffering aside, RUU is ROM Upgrade Utility
Prepackaged programs that bypass the phone's software altogether to reflash the rom
My carrier is Rogers of Canada and I have their "HTC Magic" phone
Be warned that Rogers is intentionally altering their hboot to disable system changes, you may not be able to cook your os after using this rom update.
Their updates page
https://your.rogers.com/web_auth/techsupport.asp
has the update
http://downloads.rogers.com/wireless/products/htc/magic/RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe

Rogers magic update freeze/brick

Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?

good news and bad news.
good news, im pretty damn sure thats not a brick as you can still get into fastboot (the vol down + power)((atleast thats what i think fastboot is))
bad news, i dunno how to fix it.
i know theres a way to revert to original stock ROM via fastboot, so im sure it is fixable. don't know about custom ROMs via fastboot.
bed time, though. good luck, man, and dont get bummed cause im 99% sure you aren't just plain ****ed.
edit: just noticed screenie, but can't see it because my girlfriends retarded wanna-be stepdad decides to look at pr0n all night and continues to install "mywebsearch" **** and i can't get to it. :/
Hopped on my mytouch, still think your good but let someone else who knows more vertify that.

another option
one other thing you can do,
go to a rogers store, and tell them you tried applying the so called essential upgrade 'b/c you care about your safety' and the '911 issue is a important fix'. tell them you recieved instructions to do w/e it is using the SD card method.
basically, you tried the update ---> phone got messed up.
i know someone else did it and it was grounds for them just giving you a new phone.
not saying 100% it'll work, but its worth it b/c you get a new device with the new ROM on it if it does.
goodluck.

cdstewart said:
I attempted the update via SD card method
Click to expand...
Click to collapse
Can you clarify which SD card method? Was it using the official DREAIMG.nbh from Rogers?
I thought that I had bricked my phone because I went for a hail mary attempt to root my phone. But unfortunately it wouldn't get past the Rogers screen.
However, after talking to a CSR, they sent me a link to the Windows 7 file and it rewrote everything back onto my phone and I was able to boot it normally again.

@r3s-rt
Ya, thanks. I figured I wasn't completely boned.
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
@dotster
This is the method,
Upgrade Instructions for Rogers HTC Magic
Requirements:
Rogers Magic
Battery Level of 50% or more. Do not start upgrade if battery level less than 50%
MicroSD card formatted in FAT32, please note cards formatted in FAT will not work.
Installing the Update via MicroSD Card:
Part1
The first part will prepare the device for the actual update but will not upgrade the Operating System, the upgrade itself will be performed in Part2.
1) Download the HTC_Magic_Update_File1.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents and please do not change the file name.
2) Backup your personal data: All personal data (contacts, applications, photos, bookmarks, etc) stored on the device will be lost after the update process. There are also 3rd party applications on Android Market place to back up your applications and personal data.
3) Power off the device.
4) Remove the existing microSD card from your device (if there is one already installed), press in on the microSD Card to eject it and then remove it from the slot.
Insert the microSD card with the SAPPIMG.zip on it in the microSD slot, slide it into the slot until you feel a “clickâ€.
5) Press and hold the Volume Down Button and the Power buttons until the display turns white.
6) The update will begin installing, please follow any onscreen instructions, press the trackball when prompted to press “Actionâ€
7. Once the update is complete, “Press Action to Complete†will be displayed on the screen, press the TrackBall for the device to reboot and complete the first part of the upgrade process.
8. Power off the device to prepare for the step 2 below.
Part 2
Upgrading the device.
1) Delete the SAPPIMG.zip from the microSD card
2) Download the HTC_Magic_Update_File2.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents. Please do not change the file name.
3) Follow the same instructions as in Part 1 - step 3 TO 8.
4) Delete the SAPPIMG.zip file from the card.
Click to expand...
Click to collapse
Keep in mind this is magic and not dream
Thanks for the help guys.

cdstewart said:
Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?
Click to expand...
Click to collapse
I had the same problem while installing the new update yesterday. I had to call Rogers to guide me through it and even he couldn't figure it out. My phone just kept rebooting over and over after installing the first update. Even in recovery mode it didn't give me a chance to wipe, flash or restore anything because it would reboot in a matter of 2 seconds. The tech support guy on the phone had no idea what to do. I finally realised that I had a seperate Mini SDcard USB adapter that I could put my SDcard in and then plug into the USB. That allowed me to access my SDcard so I was able to delete the first SAPPIMG and then put the new SAPPIMG from the second update onto the SDcard. I repeated the same process from the first update (I was able to access fastboot without it rebooting), everything installed perfectly and now the phone is up and running great. If you don't have a Mini SDcard to USB adapter I'd suggest picking one up at your nearest Electronics store. I believe I picked mine up at BestBuy for $35 which came with a 4gb class 4 SDcard. The adapter is so small that it actually sits on my key-chain. Hope this helps.
Rogers Magic
Radio: 6.35.10.18
SPL: 1.76.0010
(unrooted)

cdstewart said:
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
Click to expand...
Click to collapse
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.

@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?

cdstewart said:
@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?
Click to expand...
Click to collapse
I was rooted before, this is why I'm sure I've had the same problem as many of you. It seems though that this issue doesn't just stop at us... This issue has been happening with many other carriers and I'm not sure why (as of yet). I've flashed dozens of other Sense ROM's and even ROM's without Sense for ei. Espresso and Eclair and they all worked fine before. This new Sense ROM from Rogers is fantastic. So try what I did and you should be on your way with no issues.
Now if only we can root this damn phone.
Rogers HTC Magic (32A)
HBoot - 1.76.0010
Radio - 6.35.10.18

Chynkinese said:
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.
Click to expand...
Click to collapse
After the update your phone won't be rooted anymore, therefor your warranty will still be in effect. After flashing the first update it already changes your SPL and Radio therefor Rogers wouldn`t know if you were rooted prior to the update. If you stuck in the boot loop just follow my instructions and you will be home free.
Now if only we can root this damn phone.
Rogers HTC Magic (32a)
HBoot - 1.76.0010
Radio - 6.35.10.18

@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.

cdstewart said:
@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.
Click to expand...
Click to collapse
Happy to hear that I could help. They did misname the files but how could you blame someone who goes by the name of Rogers. I have several services with them and it's nothing but headaches with them.
I'm sure it was a rushed update as well. The devs at HTC were probably pressed for time to get this update up and out the door within a couple of days. Rogers will possibly be a major distributor for them in the next upcoming years.

Thanks a lot!
That solved it.

Anyone been able to root this ROM yet..?? I have tryed everything and I just keep semi bricking my phone.. but I can always recover it.

Need help I have tried everything

Hi guys, I'm pretty new here so I hope someone can help me.
I am having serious issues trying to load ANY new ROM onto my missus HTC Vodafone Magic 32B Details -
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAP10000)
CPLD-10
RADIO-2.22.19.26I
Apr 9 2009,23:30:40
Since getting the phone second hand from eBay it has played up like nothing else, it now will not even boot into the OS, I’m pretty sure the guy I bought it from, who I cannot get in contact with, stuffed something up when he unlocked it for different carriers. But I'm positive it is an OS issue and not a straight hardware fault.
Anyway I have spent about a day and a half mucking about on here trying things and reading a HEAP of stuff and I just can’t seem find a definitive answer to my problem.
I have tried installing many different roms:
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.7 Swap
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.6 Swap.zip
st0kes-v1.4.1
HTC_Magic_Vodafone_AU_Original_ROM
and a few others I cannot remember.
I am using Amon RA recovery ROM, I have rooted the phone based on method 2 in the magic rooting wiki (everything went smoothly), I have updated the SPL to version 2005 which are all the apparent pre requisites for performing this kind of operation.
Anyway down to the problem every time I try and apply a ROM, by renaming it to update.zip, copying it to the root of my SD card, then loading up RA recovery ROM and going to flash zip from SDcard I get the following messages:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Install from sdcard...
finding update package...
opening update package...
verifying update package...
E:corrupt file:
<various file names based on which ROM I’m trying to use, always the same one on each ROM though>
E:verification failed
Installation aborted
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This is starting to drive me insane, I really need to get ANY usable ROM on there I don’t care which one, otherwise I have a AU$400 lump of useless technology.
Any help people can provide me with be unbelievably appreciated.
Thanks in advance

i cant guarantee i can help, but i will try to see if i can, or also help wit some research for ya
first, what version of amon ra are you using???
2nd, do you know if you got 1.5 or 1.6 firmware???
idk too much about firmware, all i know is my mytouch was cupcake when i got it (1.5) then updated to 1.6 ota...
also are you making sure that you wipe before you try to load the roms???

Hi mate, thanks for getting back to me so quickly
The version of amon ra i am using is recovery-RA-sapphire-v1.6.2G.img this seemed to be the right one as i have a google branded phone
I am not sure what version of firmware i have, is there an easy way to check? the only real details I have is what i get from the fastboot screen as i posted above
And yes I am definately wiping the phone before I install the roms, every single time
Thanks

well i just did a few searches and i couldn't find out how to check the firmware...
i dont want to tell you to try something and then crash your system, but...lol...
i would try to "Unroot" the device, basically placing it back to 1.5 firmware and then you can "Root" it yourself.
if you want to try this here is the link for the 1.5 software
link for tutorial:
http://theunlockr .com/2009/08/22/how-to-unroot-your-mytouch-3g/
link for file:
http://www.megaupload .com/?d=BLM4EDGE
no space in the url tho...
all you have to do is,
boot into recovery
go to wipe, and wipe the top three options
go back to the main screen and select Usb-Ms toggle
then plug your device in via usb
and drop the file to your sd card. (not in a sub folder)
then safely remove your phone from pc
then press home on your phone to disable usb
then choose power off.
now to turn it back on,
holding Volume "Down" + "Power"
DON'T PRESS ANYTHING YET
after it reads the image it should show at the bottom, Action:yes, and then click trackball,
let that run all the way thru, and make sure you have enough battery juice, for this to run all the way thru.
when it's complete it will ask if you want reboot, then click Action for yes (trackball)
i believe that should unroot your phone but PLEASE PLEASE PLEASE
do as much research as possible and also question others about this method and see if you can come to a conclusion in which you are satisfied.
as always, i am in no way responsible for the Bricking or Exploding of your device...
here is a link that has great tutorials & and also you might want to check youtube, thats where i findout how to alot of things...

Um, you already have amon ra recovery on there. I assume you've already bought it rooted?
You can only check the firmware by booting up your phone and going into settings. Since you've wiped and aren't able to install a rom, you aren't able to use the phone right now, am i correct?
sanman1185, I'm glad you try to help but you gotta get more info from him first. Cause if he's already rooted, doing what you're telling him to do won't make much progress. Edit: Ok, he's already rooted. You're just telling him to do what he's already done? And he doesn't have any firmware because his phone lacks any rom right now.
Anyways, answer some of those and don't be too worried about bricking your phone. The main reason that people brick their phones is when they touch the radio and SPL.
Edit: Ok I just read that you rooted your phone so you don't need to "unroot" and root it again.
You also put on SPL 2005 instead, so post your boot info again. I assume it's an ENG SPL too, if you haven't found a solution, send me a PM and I'll help you on google talk / MSN or something.
Ps. You don't have to rename the roms to update.zip, his new recovery allows you to flash w/e zip you want. Try another SD card as well, maybe that'll help? but if not, yeah just pm me

KAwAtA - def. understand what your sayin, only reason i was thinkin to unroot and start fresh is cuz, when i started flashin roms, i ended up being stuck on the boot screen for over 30mins. pulled the battery, then read somewhere to partition sd card, then that wiped the zip from my card, lol...so what i did instead of placing another rom on the device, is "unrooted" and started fresh from the start. my theory is if you think your "Jack'd" then start from the beginning and find your mistake.
and if he did unroot and it ran Cupcake on device, and actually loaded wouldn't that have been making progress??? since he couldnt get it to load in the first place???
like i said just a thought, theory, or 2centz (sense)...
but again, i'm glad someone actually responded with a diff method or with additional ?'s, so this way he can get answers from all angle's ya kno...
and if you guys do figure this nifty lil'thang out, could you post what you guys did on here, so myself or future ppl'z that may run into this can have it as a ref??? thnx... Pce

[Q] What can I do? (Stuck in Fastboot)

I was using the new HTC Gratia Rom that was posted in the development forum, was restoring some apps with Titanium Backup manager when my phone rebooted, then it got stuck in a boot loop. I wiped it and rebooted again but no joy, stayed stuck in the loop.
Anyway, I recently installed a new recovery image, one of the ones for jailbreaking the PS3, so I have no USB access. Also it has a few extra options for wiping than the Amon RA recovery, and I guess I shouldn't have used the format boot option! Now on bootup all I get is "FASTBOOT USB", though I can still get into the psfMod recovery image.
That isn't much use to me though, as I stupidly deleted my nandroid backup and the update.zip file from my SD Card earlier while tidying it up a little bit. I don't have any other way of accessing the SD card and attempts to push another recovery image (with USB access) have failed.
I've also tried to install RUU's, both a T-Mobile UK one and a WWE one. That results in the following error: "ERROR [140] BOOTLOADER VERSION ERROR".
I guess because the current image version is: 3.31.110.1 and the RUU is only: 2.73.110.26. I don't think there's an RUU of this version available, from reading it sounds like it was an OTA, it's not something I installed myself, T-Mobile sent me this phone recently after my screen stopped working properly.
If you've managed to read this far without falling asleep, any suggestions would be welcome hopefully not just that I should buy a card reader cos I could do with getting my phone going again asap.

You got access to another phone which uses a micro SD? Could use that to put the zip onto the card.
Making a goldcard springs to mind as well
Sent from my HTC Hero using XDA App

Thanks for the tip, I had considered this already but I thought my brothers Legend (he doesn't live close) was my best bet. Turns out I had access to an N95 that did the trick

same problem
im a complete n00b
screen got replaced last month. new software was installed im guessing.
tried to use the tmobile ruu's to repair. there isnt one i can use though.
tried putting an engineering spl onto my sd card and using fastboot not really sure what happened there but it did not work.
does anyone have the appropriate update in zip format. not sure how i will get it to work but im trying all the things i read.
i do have backups but im not really sure what to do with them.
other than htc has anyone ever created an ruu?
mithdol

mithdol said:
im a complete n00b
screen got replaced last month. new software was installed im guessing.
tried to use the tmobile ruu's to repair. there isnt one i can use though.
tried putting an engineering spl onto my sd card and using fastboot not really sure what happened there but it did not work.
does anyone have the appropriate update in zip format. not sure how i will get it to work but im trying all the things i read.
i do have backups but im not really sure what to do with them.
other than htc has anyone ever created an ruu?
mithdol
Click to expand...
Click to collapse
What is the problem with urs exactly?

the problem is that im stuck in a cyanogen boot loop.
i have access to the generic fastboot only. therefore i have no ability to repair my phone from within the phone itself.
my phone is currently on hboot 1.76.0007.
i thought i had flashed clockworkmod. but for some reason or another beyond me it has disappeared.
the version of android i have running is 2.1, the tmobile version. the update number is 3.31.110.1. i understand that is the perfected spl version.
i have tried to fix using the ruu files. but i understand that the version on my phone as an ota update. therefore no ruu is applicable at this time.
i have tried many methods mentioned in various forums with no success.
thanks for responding to my post so quickly.
mithdol

Problem solved now
and the solution was so obvious............

...and what was that obvious solution? Because I'm facing a similar problem...
Thx in advance!

RUU Cannot Find Bootloader

Goodmorning,
I did a good few searches and could not find an answer to my delima. I am pretty informed about rooting and flashing ROMs. What happened was I already had a phone rooted and mikroms 4.61 but needed to exchange it due to a bad camera. I recieved my new evo 4g (hardware v4...hboot 2.10) and rooted it with unrevoked. Everything went will and was rooted within minutes. I then went to downgrade the hboot (this is where the problem began). I followed the same instructions I did with my previous evo (I believe it was hardware v3) and did the update, did not reboot, installed the .zip file. I then went and wiped everything (Full Wipe). Dalvik and Cahche as well. I then went to install mikfroyo and everything seemed ok. I them went and rebooted and now I am stuck on the bootloader. The hboot is still 2.10 but it has s-off. I tried a RUU, the RUU finds the evo and reboots the phone. Then the RUU cannot get to the bootloader. It stays waiting for a good minute but can't seem to find the bootloader even though the phone is on the bootloader. All drivers are installed properly as I checked the Device Manager and no question marks come up. Any ideas would be fully appreciated. Thank you.
By the way...I cannot get into Recovery either. When I choose that option it just heads right back to the Bootloader screen.

Why would you downgrade the hboot?
I know people have dome this to try and solve issues with their phone not booting at all, but to just do it?? Why?

HipKat said:
Why would you downgrade the hboot?
I know people have dome this to try and solve issues with their phone not booting at all, but to just do it?? Why?
Click to expand...
Click to collapse
For some reason I thought the evo would just function better with the previous hboot, doing nandroids and flashing ROMs. If I didn't need to do it I would not have even looked that way. Guess I am not as experienced as I thought. I just did that because it worked well with my previous evo. I hope I don't have to go to sprint and replace it again for my ignorance. There's other phones that have true issues that deserve to be exchanged next to mine.

Your phone is bricked. Try fastboot devices, if you get 123456789012....your screwed. You now have bad blocks and partition info is mixed up. Sorry.
Your new phone has newer block sizes

snandlal said:
Your phone is bricked. Try fastboot devices, if you get 123456789012....your screwed. You now have bad blocks and partition info is mixed up. Sorry.
Your new phone has newer block sizes
Click to expand...
Click to collapse
That stinks. Well, I will go in ahead and have it sent in through Best Buy. Thanks a bunch, friend. Godbless