Develop Bugs

Updated radio issue - phone not booting

I had success with the unrevoked root, so I decided to give the 2.2 upgrade a shot. I successfully reverted to a fresh stock unrooted 2.1, using the PB31IMG.zip file. This also took away my Clockwork Mod. Next I moved to the step of loading the dinc_ota.zip. After the 3 cycles it went to the HTC incredible boot screen and didnt move. I waited 15 minutes and nothing changed. I decided to pull the battery but no luck, still hangs on the white screen when i turn the phone on. I can still get into HBoot, which shows my radio as the updated 2.05 and my hboot is .79.
I've tried the RUU but I cannot boot the phone past the white htc screen so it wont work. I've also tried to load the PB31IMG.zip file from the sdcard agian, which doesnt. I get an error saying its too old.
Is there a way to restore my phone from Hboot?
Do you have any suggestions of threads I could read for the answer?
Thanks

Try the image again, then try the ota.
Sent from my ADR6300 using XDA App

i would not try the radio update again, that's pretty much a sure fire way to brick. I would wait for the opinions of others first.
PB31IMG.zip doesn't roll the radio back does it? It reverts to stock recovery and ROM, but does it roll the radio back too?
I thought you had to follows this to roll the radio back, http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html

k_flan said:
i would not try the radio update again, that's pretty much a sure fire way to brick. I would wait for the opinions of others first.
PB31IMG.zip doesn't roll the radio back does it? It reverts to stock recovery and ROM, but does it roll the radio back too?
I thought you had to follows this to roll the radio back, http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
Sorry, my bad. DONT APPLY THE UPDATE AGAIN!
Sent from my ADR6300 using XDA App

Try a clear storage.

jdkoreclipse said:
Try the image again, then try the ota.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I tried the image again, same error, it reads:
Main Version is older!
Update Fail!
Do you want to reboot device?
vol up yes
vol down no
I tried the reboot and it still hangs at white screen.
k_flan said:
i would not try the radio update again, that's pretty much a sure fire way to brick. I would wait for the opinions of others first.
PB31IMG.zip doesn't roll the radio back does it? It reverts to stock recovery and ROM, but does it roll the radio back too?
I thought you had to follows this to roll the radio back, http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
As for the radio update, I agree that it would be a bad idea to try to reaplly it, especially since my HBoot shows it as the updated radio.
I also saw the thread you pointed out to me but that requires clockwork mod to be installed and that was removed when i reverted to stock.
Any helpful ideas are greatly appreciated.

Does it show up on adb?
Sent from my ADR6300 using XDA App

jdkoreclipse said:
Does it show up on adb?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I did try to clear the storage, but it still hangs.
Also tried adb devices in hboot, at the htc incredible white screen, and in the fastboot menu, all with no luck. When I try to boot to recovery it hangs at the same white screen. Might just have to bring it to Verizon tomorrow, I'm beginning to think I may be holding a brick.

To revert your radio back to the original 1.x, you need to have access to adb and pushing to your data directory
Long story short, you dun goofed by pulling the battery
HTC Incredible, rooted w/ modified Sense 2.1

I think its a brick
Sent from my ADR6300 using XDA App

ilinfinityil said:
To revert your radio back to the original 1.x, you need to have access to adb and pushing to your data directory
Long story short, you dun goofed by pulling the battery
HTC Incredible, rooted w/ modified Sense 2.1
Click to expand...
Click to collapse
Once the radio update completed, the white htc inc screen came up and hung there for 15 minutes, I didnt think I had much of a choice.
In that situation what should I have done?

aaman137 said:
Once the radio update completed, the white htc inc screen came up and hung there for 15 minutes, I didnt think I had much of a choice.
In that situation what should I have done?
Click to expand...
Click to collapse
When i did the ota, it took about 7-10 min total. Yours hung on that incredible boot screen for 15 min. You did the right thing.
Sent from my ADR6300 using XDA App

I appreciate all the help, this is why I came to xda. As for my Incredible, I guess its going back to Verizon tomorrow to see what they can do for me. I'm sure I'll be waiting a good week or two until I have my Incredible back, DOH!

I wouldn't think it's bricked if you can still get into the bootloader. Bricked generally comes about when you can't even power the device on. While I have nothing to add in the way of help, I'd say don't give up on the phone yet. I'm betting one of the *real* devs may be able to help you.

Ruoh said:
I wouldn't think it's bricked if you can still get into the bootloader. Bricked generally comes about when you can't even power the device on. While I have nothing to add in the way of help, I'd say don't give up on the phone yet. I'm betting one of the *real* devs may be able to help you.
Click to expand...
Click to collapse
It may be a soft brick.
Sent from my ADR6300 using XDA App

i brick it this morning, called around dinner time, and they dispatched a replacement to me. overnight free shipping!!!

Its not bricked. I had the same issue. You need to follow this guide. Basically you have to redo it to get it to work, and this is the only way that I could do it.
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
(This was the most important part of the guide for me. Solve that: error saying its too old. All glory to Adrynalyne)
Having troubles with the RUU giving connection errors? Do this.
Go to start, and in the search/run box, type
%temp%
Delete all that you can. Make sure the RUU is not running in the background.
Now run the RUU again. Once it starts to the first screen, it has extracted the files to the temp directory. You can then copy them to a safe place. It will be a long winded numbered folder, with a similar subfolder.
Once you have copied it to a safe place, you can then copy adb.exe, fastboot.exe, and adbwinapi.dll from the latest SDK into it, overwriting the older copies. Then start the RUU by executing ARUWizard.exe. This fixed the problem for me.
You can also rename the rom.zip contained within the extracted files to PB31IMG.zip and put it on your sd card. Booting to HBOOT will scan it and offer to install.

HolyGrail said:
Its not bricked. I had the same issue. You need to follow this guide. Basically you have to redo it to get it to work, and this is the only way that I could do it.
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
(This was the most important part of the guide for me. Solve that: error saying its too old. All glory to Adrynalyne)
Having troubles with the RUU giving connection errors? Do this.
Go to start, and in the search/run box, type
%temp%
Delete all that you can. Make sure the RUU is not running in the background.
Now run the RUU again. Once it starts to the first screen, it has extracted the files to the temp directory. You can then copy them to a safe place. It will be a long winded numbered folder, with a similar subfolder.
Once you have copied it to a safe place, you can then copy adb.exe, fastboot.exe, and adbwinapi.dll from the latest SDK into it, overwriting the older copies. Then start the RUU by executing ARUWizard.exe. This fixed the problem for me.
You can also rename the rom.zip contained within the extracted files to PB31IMG.zip and put it on your sd card. Booting to HBOOT will scan it and offer to install.
Click to expand...
Click to collapse
This only works if he can get to recovery.

TNS201 said:
This only works if he can get to recovery.
Click to expand...
Click to collapse
Your point? He can get into stock recovery, which is all he needs to start over.

HolyGrail said:
Your point? He can get into stock recovery, which is all he needs to start over.
Click to expand...
Click to collapse
His tutorial says you need clockwork, so he might not be ok. You need the ability to push files to your data directory which is why he needs clockwork, unless he can do it the old way when we first got root by the time attack method. I do not know how much functionality adb would have if he was able to access ADB with stock recovery.
This is all his fault for his failure to read. From what I read in the OP, he did this
1. He downgraded with the RUU image.
2. He tried to apply the OTA
He failed to do this or at least didn't acknowledge that he did this, but he didn't install the original OTA which you will get after you RUU back to stock. If you boot your phone back up it should download the OTA from VZW and then you apply the leaked OTA. So sounds like this is the reason for his brick/semi-brick. Failure to read or understand what youre doing leads to FAIL>

s 0n

Having a hell of a time getting my evo 4g to change to s on. I have successfully unrooted it but the s off remains there. I need to take it back to sprint for repairs.
I have tried several with the recent unrevoked 3. But my results are after flashing "waiting 5 seconds because windows hates" message and the other says waiting to reboot" (both freezes forever). Any direction would be appreciated.
Thanks you.

Newsflash. I've never heard one story of Spring checking a bootloader to make sure a phone is S-On.
Flash A stock ROM and you;ll be good, although there have been posts that say Sprint will work on Rooted phones now.

rosario04 said:
Having a hell of a time getting my evo 4g to change to s on. I have successfully unrooted it but the s off remains there. I need to take it back to sprint for repairs.
I have tried several with the recent unrevoked 3. But my results are after flashing "waiting 5 seconds because windows hates" message and the other says waiting to reboot" (both freezes forever). Any direction would be appreciated.
Thanks you.
Click to expand...
Click to collapse
Ignore this, double post. Next post.

rosario04 said:
Having a hell of a time getting my evo 4g to change to s on. I have successfully unrooted it but the s off remains there. I need to take it back to sprint for repairs.
I have tried several with the recent unrevoked 3. But my results are after flashing "waiting 5 seconds because windows hates" message and the other says waiting to reboot" (both freezes forever). Any direction would be appreciated.
Thanks you.
Click to expand...
Click to collapse
You have to have a custom recovery to do that (Amon-RA or Clockwork). You need to reinstall Amon-Ra Recovery by putting this in the root of your SDCard and rename it "PC36IMG.zip": http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
Then flash this: http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
After that just run an RUU from here: http://goo-inside.me/supersonic/ruu
In case the RUU won't work from your computer, download one of the ZIP ones, put it in the root of your SDCard and rename it "PC36IMG.zip". That always works.

I am not sure what you mean by "Spring checking but I have flashed the stock rom PC36IMG.zip onto the root of the sd. My understanding that once your successful doing this you basically revert to the original rom. I have done that thanks to this site. But, I cannot for the life of me get the s on back on. Rooting my phone with three different custom roms were easier. Not all Spring stores like rooted phones. Id rather revert to original with the s on to be sure. product F thanks for the reply I will try that..perhaps I missed something. Thank You.

HipKat said:
Newsflash. I've never heard one story of Spring checking a bootloader to make sure a phone is S-On.
Flash A stock ROM and you;ll be good, although there have been posts that say Sprint will work on Rooted phones now.
Click to expand...
Click to collapse
That plus the leaked document from the sprint employee forums that said that sprint supports rooted devices means we don't have to fret over s-on for service just make sure that your phone is running a sense rom when it is taken in otherwise they can't use the diagnostic commands from the dialer to fully support the device.
Sent from my PC36100 using Tapatalk

s on
Well I think my biggest problem is that i unrooted my phone because Clocwork will not work for me to flash forever s on because it is unrooted. Is this correct? Thanks

rosario04 said:
Well I think my biggest problem is that i unrooted my phone because Clocwork will not work for me to flash forever s on because it is unrooted. Is this correct? Thanks
Click to expand...
Click to collapse
If you're using Clockwork, you have to disable Signature Verification.

s on
Product F(RED) said:
You have to have a custom recovery to do that (Amon-RA or Clockwork). You need to reinstall Amon-Ra Recovery by putting this in the root of your SDCard and rename it "PC36IMG.zip": http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
Then flash this: http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
After that just run an RUU from here: http://goo-inside.me/supersonic/ruu
In case the RUU won't work from your computer, download one of the ZIP ones, put it in the root of your SDCard and rename it "PC36IMG.zip". That always works.
Click to expand...
Click to collapse
But to get clockwork to work you have to be rooted...correct?
Thank you

Yes but you're still s-off so follow those instructions.
Sent from my PG86100 using XDA Premium App

Thanks for staying with me. Appreciate it.
Here is how I wasable to get to recovery to get to the root directory for choosing zip from sd.
STEP 9: TURN OFF DEVICE
Power down the device by holding the Power Button for 2 seconds. Allow it to shutdown completely. Wait about 10 seconds before next step.
STEP 10: RECOVERY MODE
Hold down VOL DOWN + POWER until device boots into a White Screen.
Move to RECOVERY by using the VOL DOWN toggle and select by using POWER button.
STEP 11: TRANSFER PC36IMG.zip TO SDCARD
Connect the MICRO USB Cord. There is an option for this in both the Amon RA and Clockwork recovery.
Transfer the PC36IMG.zip to the ROOT of your SDCard.[/SIZE][/SIZE]
It was the connection and discnnection of th usb cable. Everything was in green. Is that normal.
So, my next step was to flash the forever s on zip. The results were unsupported radio version. Update failed. The current version I have is 2.15.00.05.02. on the new update on my evo. I tried it first by removing the pc36img.zip nd then tried it with it on...same results.
So I found this radio version (EVO_Radio_2.15.00.05.02_WiMAX_27243_PRI_NV_2.15_003), but I am not sure if this is what version is needed. Anyways, I apologize for this long everyone, but I am trying to provide as much info and hopefully I can minimize your time. Thanks alot.

rosario04 said:
.
...
So, my next step was to flash the forever s on zip. The results were unsupported radio version. Update failed. The current version I have is 2.15.00.05.02. on the new update on my evo. I tried it first by removing the pc36img.zip nd then tried it with it on...same results.
So I found this radio version (EVO_Radio_2.15.00.05.02_WiMAX_27243_PRI_NV_2.15_003), but I am not sure if this is what version is needed. Anyways, I apologize for this long everyone, but I am trying to provide as much info and hopefully I can minimize your time. Thanks alot.
Click to expand...
Click to collapse
The radio package you mention is the same radio you already have, so you'll want an older version. I'm not exactly sure of the version number, but I do know that is not the correct one.
Remember when you flash radios to not pull the battery. It'll flash, then upon rebooting it'll finish. You'll see a screen that you probably haven't seen before, it'll most likely be an arrow pointing down to a phone or an Android in a box... or something like that. Regardless of what you see after the flash, don't freak out and pull the battery - you'll end up bricking your phone. It's one of the few ways to guarantee a real brick, the phone will never turn on again. You may already know this, or it may be in whatever guide you're using, but it's good to know.
Anyway, I'll see if I can find the correct radio for you, and good luck!
Edit: I read somewhere that someone used this one to get s-on: http://www.mediafire.com/?v0ymbhaa0ltcvyy
However, you may need to do some trial and error. It should work, but here's a link to all of them: http://forum.xda-developers.com/showthread.php?t=715485
These are from Calkulin, so if they're PC36IMG files you'll be fine, but I'm pretty sure you flash them in recovery. Sorry, it's late & I'm lazy. Anyway, I think Calkulin still uses amend scripting, which will render them incompatible with ClockworkMod. You'll either need to switch to Amon Ra to flash them or find a different flashable zip. I think you'll only need to flash the radio, not all of them, but I could be wrong.
Sent from my PC36100 using Tapatalk

You don't need S-OFF to have sprint work on your phone for repair. My cousin just got an insurance replacement Evo 4g because he washed his phone with his clothes. He brought it over to me to be rooted and the phone he got was already S-OFF and that is an Insurance REFERB. also with the leaked forum of how Sprint will infact work on Rooted phones gives it away that you dont need S-OFF

Plainjane. Thanks for the info. I downloaded the zip from the first site you showed here and it ran well with the exception that it got stuck on formatting cache. So, I rebooted. s off still on. I will try the next one here in a few. Thanks everyone.

s on
well. While I continue to try and solve this puzzle I will attempt to attach this link on how to flash a radio to evo. i take no credit.

well i am happy to say i have finally go the s on back on. I believe the problem was that i left the recovery supersonic ra image on the root directory of the sd. i deleted that and flashed the supersonic s on image and voila!!! Everythin crumbled under the rosario wrath and s on is on. Thats Boricua power. My next problem is flashing sense back on. Khilbron, I wasnt ignoring your post on sense, it was just I was trying to get the other things done. So can you please expand on the sense. Thanks to everyone who took out the time even you kipkat with your kind of unfriendly comments. Dueces.

s on
rosario04 said:
well i am happy to say i have finally go the s on back on. I believe the problem was that i left the recovery supersonic ra image on the root directory of the sd. i deleted that and flashed the supersonic s on image and voila!!! Everythin crumbled under the rosario wrath and s on is on. Thats Boricua power. My next problem is flashing sense back on. Khilbron, I wasnt ignoring your post on sense, it was just I was trying to get the other things done. So can you please expand on the sense. Thanks to everyone who took out the time even you kipkat with your kind of unfriendly comments. Dueces.
Click to expand...
Click to collapse
i took my phone back to sprint and they replaced both speakers. now to root again.
Again. Want to thank everyone for their help.

Flashing ROM

I have downloaded the ROM Classic v0.1.0 Supermagic, placed it on my SD card. I have also unlocked my bootloader and have CWM recovery. I have returned to the bootloader screen, went to recovery mode, and went to select which zip I wanted to flash. I found the classic v0.1.0 file and slected it, which I thought would begin the flash/download. It simply opened and gave me 3 more options for files. data/, system/, and META-INF/
I should probably mention that after getting the classic v0.1.0, i extracted it and put that file on my sd card.
I have an EVO 4G, unlocked but still with the S-ON, although I can still flash files. I really appreciate any help.

Don't extract a rom..and use smelkus recovery its better than that one
Sent from my PC36100 using xda premium

but other than that mistake, it looks like I'm on track? and speed really isn't an issue right now. As new as I am, I simply want it to work.

WeAreGuns said:
but other than that mistake, it looks like I'm on track? and speed really isn't an issue right now. As new as I am, I simply want it to work.
Click to expand...
Click to collapse
+1 on what Ireyes said and also wipe all except sd card 3 times, then flash.

Read the Evo guide in my signature

MIKESTONY said:
+1 on what Ireyes said and also wipe all except sd card 3 times, then flash.
Click to expand...
Click to collapse
this will help I hope. i'm stuck in a boot loop atm. I eventually cose a different ROM, papasmurfs CM9, but i kept the same procedures, all went well until this boot loop. hope this wipe helps.

HipKat said:
Read the Evo guide in my signature
Click to expand...
Click to collapse
Wow. That helps. I followed the rules and read everything I could before attempting anything and searched and read some more. Somehow I missed that thread. Would have saved me a boatload of time and frustration.

WeAreGuns said:
Wow. That helps. I followed the rules and read everything I could before attempting anything and searched and read some more. Somehow I missed that thread. Would have saved me a boatload of time and frustration.
Click to expand...
Click to collapse
Try fully Rooting your evo I had the same problems when I unlocked the boot loader on the og evo for the second time.don't worry you can RUU it and get back to fully stock if you have any problems.
this right here is my pretty boy swag!

Creating backup

Hey everyone,
So I succeeded in unlocking and rooting the device. I just installed CWM via the RomManager app. When I try to create a backup, initially there is a green progress bar, but after a second or two, a red question mark is displayed.
Is it a problem that I uninstalled some stock apps or is it irrelevant what exactly one tries to create a backup of?

Moved to Q&A. Please post all questions there.
Sent from my HTC Glacier using xda premium

timbohenry said:
Hey everyone,
So I succeeded in unlocking and rooting the device. I just installed CWM via the RomManager app. When I try to create a backup, initially there is a green progress bar, but after a second or two, a red question mark is displayed.
Is it a problem that I uninstalled some stock apps or is it irrelevant what exactly one tries to create a backup of?
Click to expand...
Click to collapse
CWM cannot be installed via RomManager. It must be flashed in fastboot mode.
Go to : http://forum.xda-developers.com/showthread.php?t=1871243

ckpv5 said:
CWM cannot be installed via RomManager. It must be flashed in fastboot mode.
Go to : http://forum.xda-developers.com/showthread.php?t=1871243
Click to expand...
Click to collapse
it can be, but it wont be perm installed, it's just a "temp" recovery and pointless tbh

Sorry about the thread. I tried deleting it, but couldn't find out how to.
So concerning the backup. I did flash it in fastboot mode, but something always went wrong and the flashing procedure didn't advance after some point. When I checked whether it would still work, there was another red warning icon.
I guess I'll give it another try.
----
So apparently the fastboot method either takes a lot of time or it just won't work. The terminal says "sending 'recovery' (5464kb)... for more than 5 minutes now. I did all unlocking, rooting etc. with the exact same devices I'm using now, so that can't be the reason.

timbohenry said:
Sorry about the thread. I tried deleting it, but couldn't find out how to.
So concerning the backup. I did flash it in fastboot mode, but something always went wrong and the flashing procedure didn't advance after some point. When I checked whether it would still work, there was another red warning icon.
I guess I'll give it another try.
Click to expand...
Click to collapse
Make sure you flash the correct CWM for PrimoU (GSM) and PrimoC (CDMA) as you do not mentioned what device that you have.

I get past the sending part, but then when it's writing the recovery, nothing seems to happen. Is it supposed to take a rather large amount of time?

I somehow never get the "OKAY" when I flash something via terminal, instead it keeps saying "writing...". Apparently it worked, nevertheless.

[Q] Rooting my Captivate Glide [Take 2]

So, I was just told that I was -actually- posting my error that I was getting from my Captivate Glide in the wrong area, I was actually posting it in the Captivate area... so... I'm just gonna quote myself here:
Hazarath said:
Ok, so, first off, yes, as I keep being told by the forums I read, I am a noob. I understand, and respect that. That's not the issue.
So, I have followed the guide that's found here, and I have the Clockwork mod installed, as when I turn on my phone, and press down, it says I have it.
I -had- my phone rooted in the past, and then -finally- the official 4.0.4 update came out. I upgraded from my old rooted image to the new image, and figured I'd wait to see if someone would post instructions on how to update this version, unless I am doing something wrong.
I am sure that I am, or I missed something somewhere. Again, I have -no- idea what I am talking about. I don't claim I do.
So... I try to install Superuser-3.2-RC2 -and- RC3-ARM-signed.zip, as I was advised that may work via pressing power+down, I get this:
E:failed to verify whole-file signature
E:signature verification failed!
I am not sure what I am doing wrong. I copied the file over to the root of the SD card, and all that jazz.
So, is someone ready to point out the error in my method, or more likely, tell me I am an idiot?
-Haz
Click to expand...
Click to collapse
The only solutions offered on that forum was to try SuperOneclick, and I simply get a pop-up after clicking 'Root', a dialog letting me know I have missing drivers. It asks to allow me to install them, and it just goes 'No data Found'. ..amusing error if I ever saw one! Oh, it's better... it repeats the same thing, and I get no further. The application just locks up, all done.
So, as stated as I quote myself... am I an idiot, or is something borked?
-Haz

Try to flash ur phone with proper cwm image file:
http://forum.xda-developers.com/showthread.php?t=2007198
Else, try to install some different ROM, stock is boring

The file signature error generally means a bad download. Try redownloading it. If you don't mind potentially hosing your installed ROM and having to reflash, you could try disabling the signature check.
You did install CWM first, right? IIRC the official ICS update clobbers recovery so you have to reinstall it.
Just a thought, why not flash straight to CM10.1? It comes already rooted.

roothorick said:
The file signature error generally means a bad download. Try redownloading it. If you don't mind potentially hosing your installed ROM and having to reflash, you could try disabling the signature check.
You did install CWM first, right? IIRC the official ICS update clobbers recovery so you have to reinstall it.
Just a thought, why not flash straight to CM10.1? It comes already rooted.
Click to expand...
Click to collapse
What's CM10.1? Forgive me, a newb here. I already did the who re-download thing, from a few sources, no good.
szulco said:
Try to flash ur phone with proper cwm image file:
http://forum.xda-developers.com/showthread.php?t=2007198
Else, try to install some different ROM, stock is boring
Click to expand...
Click to collapse
I followed those steps; it seems that, looking upon my working directory, I already used the recover image provided in the link. So, I already have this tool installed. So, that's that. >.>
I am not against installing a custom ROM, as long as someone here can actually attest to it working! I am a stickler when it comes to operating systems. I don't just go, 'Hey, that looks cool!' *install...* '..wait... it does THAT? Screw that!' *restores stock*
-Haz

Dude I got errors because when I downloaded cm10 I downloaded it 11 times because all ten of the downloads where (bad)
Sent from my SGH-I927 using xda app-developers app

Erm... I just wanted to kinda bump my own thread here... and just FYI:
dude52 said:
Dude I got errors because when I downloaded cm10 I downloaded it 11 times because all ten of the downloads where (bad)
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
If the file I had was damaged, it likely would not have took the first time I flashed the file when I had a different version of 'droid on it. So, that's likely not it.
Any other ideas?
-Haz