I know how to put the boot loader into fastboot mode, power on while holding up. Problem is, I can't get it to load. It started after installing the SlickV6 Rom. Anyway, when I attempted to load the bootloader, the phone shows a black screen inof the fastboot usb text. Worst of all, rebooting the phone will only boot back to this black screen. I have to LGPNST back to stock just to get the phone to load.
Edit: Ok, LGPNST Again, rooted, unloacked, then tried to use Quick Boot to boot directly to recovery, and I get the exact same issue. It's almost as if the recovery is corrupted and it's not allowing me to load the booloader. Problem is, if I can't get into fastboot usb mode, or recovery, I can't flash a new recovery. This is awesome.
plaster said:
I know how to put the boot loader into fastboot mode, power on while holding up. Problem is, I can't get it to load. It started after installing the SlickV6 Rom. Anyway, when I attempted to load the bootloader, the phone shows a black screen inof the fastboot usb text. Worst of all, rebooting the phone will only boot back to this black screen. I have to LGPNST back to stock just to get the phone to load.
Edit: Ok, LGPNST Again, rooted, unloacked, then tried to use Quick Boot to boot directly to recovery, and I get the exact same issue. It's almost as if the recovery is corrupted and it's not allowing me to load the booloader. Problem is, if I can't get into fastboot usb mode, or recovery, I can't flash a new recovery. This is awesome.
Click to expand...
Click to collapse
Try redownloading Freegee and rerunning it. After the phone boots up download GooManager, hit menu, and then choose install openrecovery script. Once it downloads and installs, power down the device. Hold volume up + power until you see the LG logo and it goes black with text. Press volume down twice and then power. It should boot into TWRP recovery. Once you make sure it's working you can flash Sk8's CWM recovery, I you want too.
It's the black screen with text that won't load. If I don't unlock the bootloader the phone ignores the button commands. Once I unlock the bootloader, the phone will boot fine, until I attempt to load the bootloader. It just loads a black screen and sits there forever. The phone will never boot past this, even while forcing a reboot by holding power. I'll give your method a shot. Worst that can happen is another LGPNST.
EDIT: Nevermind the above. It's the act of unlocking the boot loader that's actually causing the phone to not boot. After typing the above response, I unlocked via freegee and rebooted, it shows the LG Logo, then just a black screen and it's stuck. Running LGPNST again. I have no idea what could have happened to the booatloader that would cause it to be unable to unlock without bricking my phone.
EDIT 2: Just tried the freegee.bat from the PC. Says the phone has been liberated, but does the exact same thing. I am stumped. I hope I don't have to wait for ATT to release an update so I can run something other than stock.
Sent from my LG-E970 using Tapatalk 2
Looking through the freegee thread, this seems to be a common problem with the newest freegee. Gonna try an older version and see if that's the issue. If not, guess I'm stuck with simple root until I have time to get on irc and see if anyone knows how to fix the corrupted partition.
What firmware u flashing back to with lgnpst? 10o or 11c
Sent from my LG-E970 using xda app-developers app
10o
Sent from my LG-E970 using Tapatalk 2
Root with korean root then 0.5 freegee u should be fine
Sent from my LG-E970 using xda app-developers app
You mean LGPNST with Korean firmware? Never saw Korean root.
Sent from my LG-E970 using Tapatalk 2
I'm at work now but send me a pm or get on irc this evening and we can fix this for ya
Sent from my LG-LS970 using xda app-developers app
Ok, will do. Thanks in advance.
BTW, iamtha1, I tried the Korean Root. It took, but I had the same issue. The only upside to this is that I'm still able to use the phone. It's the stock firmware, but it's not so bad once you freeze the excessive AT&T bloat.
I am having the same problem, my battery has been acting weird so i drained it completely, now it wont even boot past the black screen with blue text saying recovery. The power button wont do anything so i just have to hard reboot (power +volume up). It will just boot back into that same screen... I have the sprint version with zvb and not rooted or unlocked. please help
Salsathe4th said:
I am having the same problem, my battery has been acting weird so i drained it completely, now it wont even boot past the black screen with blue text saying recovery. The power button wont do anything so i just have to hard reboot (power +volume up). It will just boot back into that same screen... I have the sprint version with zvb and not rooted or unlocked. please help
Click to expand...
Click to collapse
Why are you posting here then? Go to the Sprint LGOG forum.
Related
Soooo before the flame begins, yes i was stupid to do this so that is covered. Was curious today and never played with the app in question (chainfire 3D) and installed in my LTE. Little did I know this app doesn't work with ICS (so i read?..). Well I installed the driver that came with it and since after initial shutdown from installation, I can only get to my splash screen. I've tried recovery and fastboot combos and neither pass the splash screen >.< Anyone?
U try running the RUU?
Sent from my EVO using XDA
Was thinking about trying that. Worried this may brick my secure element : S
Edit: tried the RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed), got an unknown error. Attempted the error recovery method from RUU but was unable to get to the bootloader screen...****.
Gotta do it...
sent from my EVO LTE
See post edit.. : S
naterz said:
Was thinking about trying that. Worried this may brick my secure element : S
Edit: tried the RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed), got an unknown error. Attempted the error recovery method from RUU but was unable to get to the bootloader screen...****.
Click to expand...
Click to collapse
where did you get the 1.12.651.2
all i can find is 1.12.651.1
shipped-roms.com. I guess i could try the .1 version
when i try to run the .1 ruu, it shows im on 1.12.651.1_R2
Just tried the .1 RUU, got error [155]: UKNOWN ERROR again... gonna try the Recover option thru that..
edit* error 155 again after Recovery option success and RUU reflash :'(
edit* I'm not too familiar with ADB, but do you think I could get to my hboot/bootloader screen through it or perhaps Recovery in general?
naterz said:
Just tried the .1 RUU, got error [155]: UKNOWN ERROR again... gonna try the Recover option thru that..
edit* error 155 again after Recovery option success and RUU reflash :'(
edit* I'm not too familiar with ADB, but do you think I could get to my hboot/bootloader screen through it or perhaps Recovery in general?
Click to expand...
Click to collapse
Navigate to your adb tools folder via terminal and type
adb reboot bootloader
tried adb reboot, error device not found : (
ddeecc
naterz said:
Soooo before the flame begins, yes i was stupid to do this so that is covered. Was curious today and never played with the app in question (chainfire 3D) and installed in my LTE. Little did I know this app doesn't work with ICS (so i read?..). Well I installed the driver that came with it and since after initial shutdown from installation, I can only get to my splash screen. I've tried recovery and fastboot combos and neither pass the splash screen >.< Anyone?
Click to expand...
Click to collapse
But you did get to the splash screen and that's a sign of hope..this phone won't even do that. nothing at all screen dead, everything is dead including bootloader. :\
Shutdown the phone and boot into bootloader.
Option 1) do a factory reset and if it doesn't work then,
Option 2) select fastboot then ran Ruu.
Sent from my HTC One X using xda premium
There is no way to boot into bootloader or fastboot, whether through adb or the key combos :S Adb states device not found and the key combos only give me splash then a lightly lit black screen..
Sent from my PC36100 using XDA
Are you positive about not able to boot into bootloader with key combo? Your phone has to pass bootloader before going to the splash screen.
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
So you tried booting as instructed as the above link?
Sent from my HTC One X using xda premium
Ive never really pressed the power button a second time after the initial let-off. I'll give it a shot when I get home, but I'm expecting the same results. Just FYI, I DO see the two Orange bars move on the splash screen (upper right) before it goes blank..
Sent from my PC36100 using XDA
Sounds like a case of the looped boot screen
Sent from my HTC One X using xda premium
UPDATE! Phone was completely drained when i got home...plugged into charger, orange light came on! Was able to enter the bootloader through the key combo and successfully entered my TWRP to do a nand restore. Restore went well and am now running again! Brick fixed by draining battery!
Good to hear:good:. brick was fixed by draining battery :what: then why did you need to do a nand restore? Whatever worked for you
why i said it was fixed via drain was that the charge light finally came on after it died and was plugged in, therefore it allowed me to access bootloader which let me into recovery to restore my backed up clean system files. When the nand restore was completed i was actually able to pass my splash screen! : )
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
blackplague1347 said:
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
Click to expand...
Click to collapse
I had this issue, if you boot into bootloader does it say tampered? If not turn your phone completely off and then boot it into bootloader. Then you should be able to enter recovery. I ciuldnt enter recovery until my bootloader read tampered.
Sent from my HTC One using Tapatalk 4 Beta
You're right, it won't boot to custom recovery until it says tampered. I'm pretty sure I've rebooted several times since installing TWRP, but either way it's working (for) now. I'm not sure what the hell made it "click," but I'll take it. Thanks.
blackplague1347 said:
You're right, it won't boot to custom recovery until it says tampered. I'm pretty sure I've rebooted several times since installing TWRP, but either way it's working (for) now. I'm not sure what the hell made it "click," but I'll take it. Thanks.
Click to expand...
Click to collapse
Yeah it took me more then 10 tries until I just shut it off and then went into bootloader and there was the tampered. Glad it worked out for you.
Sent from my HTC One using Tapatalk 4 Beta
I had the same problem. I just did "adb reboot recovery" once and it worked, and it boots to recovery from the phone now every time.
blackplague1347 said:
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
Click to expand...
Click to collapse
im still having the same problem after allot of tries is there some sort of fix ?
Fastboot Tampered?
im still having the same problem after allot of tries is there some sort of fix ?
Click to expand...
Click to collapse
At the top of your devices when at the fastboot screen does it say Tampered?
Corey.C said:
At the top of your devices when at the fastboot screen does it say Tampered?
Click to expand...
Click to collapse
Yes mine says that. I am a new to this, what do i need to do
Hi thanks for looking at my thread.
My phone was acting up so I rebooted it an then it was just stuck on the loading screen and i was like oh mo big deal so i shut it off and turned it ok again and it did the same thing... So i went into bootloader and clicked recovery like a normal human being and then at the too it said entering recovery... But nothing ever happens. I boot it it just freezes i load recovery it just freezes i click facory restore it freezes. My phone mecer connects to my computer for some reason even when i have adb but either way it was my source of internet so i cant download ruu or anything. I was using a venom rom im pretty sure the latest one and its the at&t model.
Any and all help is appreciated! Thanks.
golabski said:
Hi thanks for looking at my thread.
My phone was acting up so I rebooted it an then it was just stuck on the loading screen and i was like oh mo big deal so i shut it off and turned it ok again and it did the same thing... So i went into bootloader and clicked recovery like a normal human being and then at the too it said entering recovery... But nothing ever happens. I boot it it just freezes i load recovery it just freezes i click facory restore it freezes. My phone mecer connects to my computer for some reason even when i have adb but either way it was my source of internet so i cant download ruu or anything. I was using a venom rom im pretty sure the latest one and its the at&t model.
Any and all help is appreciated! Thanks.
Click to expand...
Click to collapse
Get into the bootloader and use fastboot. Get the HTC all in one tool kit and reflash either CWM or TWRP to try to get into recovery. If that doesn't work, leave it on fastboot and run the RUU from HTC.
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
I took it to Sprint. They thout it was the power button, after replacing it and the same I got a refurbashed phone through TEP insurance at no cost. WIN. Except does anyone have S-off suggestions for Hboot 2.09 and mainver 3.17.651.4 dirtyracun which I am familiar with does not apper to work.
m1gramme said:
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
Click to expand...
Click to collapse
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
fizbanrapper said:
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
Click to expand...
Click to collapse
My HBOOT is 2.09.4444
I believe my ROM was eiter a rooted sense or BeanStalk 4.3. I honestly don't remember because I haven't changed anything in so long.
I had TWP openrecovery-twrp-2.6.3.0-jewel.img
Again this wasn't a problem that came from trying to change anything. My phone froze I soft-reset it and it was in an unstoppable bootloop. No images were found. Telling it to go to recovery still took it to bootloop. Even after power down from bootloader, after 20 seconds it boots back into bootloop.
The problem I feel most at hand is I can't charge the battery enough to do anything because it appears to not charge in bootloader.
I have had my phone rooted and s-off through Dirty Racun for almost a year now and have been using the same setup without changing for at least 6 months.
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
If you're able to and have the proper equipment, I'd test the internal battery with a voltage meter to see if it is even able to hold a charge, will save a lot of frustration.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
Again the hardest part about this is my phone refuses to turn off. I have gone into the bootloader and selected Power Down. The phone turns off and the charge light blinks. Then 20 seconds later without me touching it, it turns on and starts into the bootloop.
I am currently finding some luck by holding the down button so when it starts itself again I can be in bootloader mode and select power down. I have elevated my battery from 3530mv to 3649mv (as per fastboot getvar battery-voltage)
Any suggestion as to where a good number to reach would be helpful.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
See above about "charging" after getting it up a little (and without SD card) I tried booting to recovery (getvar battery-status good) still went to htc bootloop screen. Tried to flash recovery and boot as per
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
in troubleshooting guide. Still continues in bootloop
So a littel update after spending forever with my charging trick I was able to get a little more charge. I was able to run commands of flash recovery it stated it was complete. Still boots to bootloop. I was able to try to run RUU using RUU 3.15.651.16 - HBOOT 2.09
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip RUU.zip
The whole process worked (said it did)
Still in repeating bootloops at htc screen.
Phone still turns itself on into a bootloop even after selecting power down from bootloader.
I'm beginning to think it's the dreaded brick...
Interesting issue, indeed. There were some problems reported with the 3.15 RUU, but none that should cause the issue you're having. Check out the top link in my sig and go to the bottom of the first post. Hit up the link for VipeRUU. I suggest trying it and returning your phone to stock. If after returning your phone to stock the issue persists, then you most likely have a hardware issue (already sounds like that's likely the case). If you have TEP with Sprint you can take the phone to a Sprint service center and see about getting it replaced.
Sent from my HTC device
My wife had that issue as well but a factory reset fixed
Sent from my EVO LTE using Tapatalk
Hi all,
This is my sons phone which he doesn't use as phone - just for games.
Last night he dropped it and it froze, after removing battery it started powering and boot-looping on white htc logo screen.
I powered it with vol down and went on boot-loader and I thought I just restore it via recovery to a state I made him few months back, but failed to go to recovery, again on white screen loop.
I tried installing shipped ruu and after few fails I did it, but again restarts on white screen.
I can connect it to pc and all, running fastboot commands usualy comes with "remote not allowed"
I was sure that I did unlock bootloader for this phone but it says locked, so I am not sure ( having 4 htc phones in same house hard to know what I did to which )
This phone prior to drop had:
4EXT_Recovery_Touch_v1.0.0.5_RC7
S-OFF
not sure on unlocked bootloader
and
Cool-ICS-v17-EvoC
any ideas appreciated
Thank you
PS
I tried to go to htc page and unlock boot-loader, but numbers i paste are not recognized ( I did this many times so its not my error in copy paste)
I guess I cant edit my post.
I managed to unlock bootloader
I installed "Cool-ICS-v17-EvoC" rom via sd card as PG86IMG.zip as I can't load into recovery
and it reboots on white htc logo again
help
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Brian706 said:
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Click to expand...
Click to collapse
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
cipher101 said:
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
Click to expand...
Click to collapse
Apologies, I went and re-read the op and now I see that.
I think you are having trouble with the fastboot commands because of the locked bootloader like you said. You could also use the juopunutbear patched hboot since you are s-off, it will give you access to the extra fastboot commands regardless of locked/unlocked state. It can be flashed as a PG86IMG.zip via the bootloader.
If you use the patched hboot you could attempt to boot recovery into memory by using fastboot boot recovery.img
Because you are s-off, you can also flash a recovery via the bootloader as a PG86IMG.zip. If you want to try, here is 4ext recovery:
https://www.dropbox.com/s/t6q8wi58xzidgan/4ext_1.0.0.5.rc9_PG86IMG.zip
Obviously just Rename the file and remove everything prior to PG86IMG.zip.
I have a feeling though that since you successfully ran the ruu and it still won't boot, that no amount of software changes will fix the issue. I'm not sure if the motherboard will fix the issue or not buy that's a pretty cheap fix to try
Thanks for help and advice man,
I bought him a working used evo 3d from ebay, it was under $30 so I'll keep this one for parts I guess.
Thanks again