Related
Ok, so this is a big problem for me. I recently got a new evo (little bro broke screen, so i got a replacement) and i instantly tried to root it. I am on hardware 0003 with hboot .79 running version 1.47. As you can see, I have gotten to 2.1 successfully. I started at 3.29 so this was pretty easy.
But now I have a huge problem. My hboot won't let me flash the pc.zips. I name them correctly, and it loads the zip, and even checks it, but just dumps me back at the menu with no error warning or anything. This is a really big problem. I can't even get back to froyo now.
So I downgraded to hb .79 software 1.47 using the rage against the cage and flashing misc method before the pc.zip. This took a few tries for the zip to update as well.
Then i used the flash exploit to try to root eclair. Everything went great. But my pc goes to checking, and then dumps me back at the menu.
Plz help me
Dk
I had the same issue hboot would search but than drop me back at main menu. This pc36 file woorked for me found it in another post let me know if it works.
View attachment PC36IMG.zip
jdh10475 said:
I had the same issue hboot would search but than drop me back at main menu. This pc36 file woorked for me found it in another post let me know if it works.
View attachment 438729
Click to expand...
Click to collapse
Thanks jdh. I. Will test in the morning. Could you tell me what is in the pc36img.zip? This would be very helpful for me to know what the he'll I am flashing. Does this fox the problem for pc.zips after it, or what? Any more info?
Did you make sure you have plenty of space on your SD card and that you still have S=OFF? I would also try the eng bootloader (.76) since it comes with S=OFF by default
I do have space, but I don't have s-off. I have just run the flash exploit though, so I think that gives me a chance to flash the eng build and then turn s-off. Correct me if I am wrong. I am just trying to root. Again, s is still on
dkdude36 said:
I do have space, but I don't have s-off. I have just run the flash exploit though, so I think that gives me a chance to flash the eng build and then turn s-off. Correct me if I am wrong. I am just trying to root. Again, s is still on
Click to expand...
Click to collapse
The flash exploit still works? I figured they would have fixed that by now, thats a pretty big security hole lol
ya, if you can get the # root prompt you should be able to flash the mtd-eng and then Toast's pc36img. Once you have root his part 2 guide should tell you how to do everything.
Edit: ignore that about the flash exploit, I forgot you said you downgraded lol
Hah ya I think that might be the problem. I did downgrade to the1.47, but I think something is broke. I will wipe, and do netarchy's method of deleting two files in 1.47 and then doing toasts part two (wow, fail htc. Only two files?) and report back. I will also check md5 which I have not yet done.
HBoot 76.200
not working. i am starting to get sort of annoyed. i can't even get back to froyo.
i am going to pm steelh. if he doesnt help, i am going to go to toast. unless anybody has any other suggestions of people i should ask before going straight to the root master
Invoke the OTA updates. About 3 times until you get to 3.29.
(Assuming s-off)
Then everything will work and you can flash whatever you want.
as i said before, s is not off. i am trying to get it off. it is much harder to do in 3.29, so i tried in 1.47 and i am stuck now. no otas. i am giving it another shot right now. thanks for trying
You need to downgrade farther. Go to 1.32
Make sure the s-off file is on your sdcard before you do so. You will lose USB until you upgrade back to 3.29
thanks for the suggestion. where can i find a 1.32 pc36im.zip so i can try it? i'm not even sure if it will accept it. could you post a link? i have rooted 1.32 before, so this should be a breeze
Can someone please explain clearly the difference between Unrevoked 3 (.22) and Unrevoked Forever (for EVO use).
I've read both Wiki's and it seems, for the EVO, that both permanently give root, unlock NAND, and s-off.
If I root with Unrevoked 3, what exactly would be the reasoning for flashing Forever?
Please answer specifically for EVO use.
Thanks
sent from my bad-ass EVO!
sweet...
sent from my bad-ass EVO!
Unrevoked forever achieves S-OFF, which means, even if for some reason you become "unrooted" (such as accepting an OTA) you can always go to recovery and flash a rooted rom. S-OFF is a somewhat permanent NAND unlock.
Unrevoked 3.22 includes the forever flash after the root process, however, I have noticed sometimes it doesn't flash properly, so anyone using unrevoked 3.22, should verify they are S-OFF in bootloader. If you are still S-ON, then download and flash the unrevoked forever .zip until you get S-OFF.
Thanks, but its just hard for me to believe that the whole point of Forever is "just in case" you don't achieve s-off with 3.22. It has to do something extra right?
What is this stuff I've been reading that its not permanent... or is this just old info. When I read the 3.22 wiki it says that it "now" achieves root as of 3 whereas before it did not.
sent from my bad-ass EVO!
generalExpert said:
Thanks, but its just hard for me to believe that the whole point of Forever is "just in case" you don't achieve s-off with 3.22. It has to do something extra right?
What is this stuff I've been reading that its not permanent... or is this just old info. When I read the 3.22 wiki it says that it "now" achieves root as of 3 whereas before it did not.
sent from my bad-ass EVO!
Click to expand...
Click to collapse
Well forever was released after other root methods. So people who rooted either manually or simple root or whatever.. won't have S-OFF, unrevoked were the first to come out with that, and the forever .zip download, lets those people have it too.
Old versions of unrevoked did not reach permanent nand unlock so you'll read a lot of old stuff about how unrevoked isn't a "full root", but now with forever, it does.
Ok, so by rooting with Unrevoked 3 I don't need to flash Unrevoked Forever, right? Because now with version 3 I achieve the same things that Forever does??...
Is this correct.
sent from my bad-ass EVO!
I rooted with unrEVOked 3 and have S-OFF so you should be fine.
generalExpert said:
Ok, so by rooting with Unrevoked 3 I don't need to flash Unrevoked Forever, right? Because now with version 3 I achieve the same things that Forever does??...
Is this correct.
sent from my bad-ass EVO!
Click to expand...
Click to collapse
In theory yes, as I stated, unrevoked 3.xx has included the forever flash, but you just need to double check that it all went through, there have been many reports (in the IRC chan, and my own experience with a replacement EVO) that people are rooted but not S-OFF after finishing unrevoked 3.xx.
VDub2174 said:
I rooted with unrEVOked 3 and have S-OFF so you should be fine.
Click to expand...
Click to collapse
As above.
op-put simply, do the unrevoked3.xx to root your phone. if you get s-off in the process then good no need to do anything else. if you still got s-on then you need to run unrevoked forever. simple as that. just because it worked for someone else does not mean that it will work for you. just do it and then verify it is nand unlock.
OK, just rooted my EVO for the 2nd time ever. Went pretty easy. However, I was using Ubuntu 10.10 64bit and it took a minute to figure out how to run the reflash program as a root user. I did get some errors about the radio not being supported and update failed. After a reboot I noticed that I did not have s-off but did have the ClockworkMOD recovery and the superUser Permission app. So, I ran unrevoked forever and viola I now have s-off (and the unrevoked splash screen). I see now why this is useful, just wondering why I had errors with my radio version.
Code:
unrEVOked forever S-OFF patch v1.1
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in /data/local/unrevoked-forever.zip
(Status 42)
Installation aborted.
Failure at line 1:
install_zip DATA:local/unrevoked-forever.zip
Why the **** won't UnrEVOked 3.32 ****ing run on my Windows XP and EVO??? WHAT THE ****???
HTC Sync is NOT installed
USB debugging is enabled
What the **** am I missing here?
Did you install the driver from the help section?
jstn76rs said:
Did you install the driver from the help section?
Click to expand...
Click to collapse
No... and I totally did read that! Crap! Thanks, hopefully that will be why...
So I would assume I just need to run the .exe file with the phone turned booted back up?
I hope I Don't have to redownload everything...
eyeballer1 said:
Well forever was released after other root methods. So people who rooted either manually or simple root or whatever.. won't have S-OFF, unrevoked were the first to come out with that, and the forever .zip download, lets those people have it too.
Old versions of unrevoked did not reach permanent nand unlock so you'll read a lot of old stuff about how unrevoked isn't a "full root", but now with forever, it does.
Click to expand...
Click to collapse
Using the engineering bootloader, like simple root did, has unlocked the NAND (s-off) since day one. Unrevoked just figured out a way to do it with other bootloader versions
Even more questions of whether I'm truly rooted or not...
First time posting although I've been lurking for quite a while so hopefully I don't get flamed out of here on my first attempt.
First I did root my Evo using unrevoked 3, all seemed to go well and correctly as I ended up with S-OFF, superuser app, etc. I created a backup and everything, (still running stock Sense ROM.) Do I need to try using Unrevoked Forever now?
I started reading posts about backing up RSA keys and WiMAX partitions etc and when I connected the phone (yes usb debugging and charge only); opened a command prompt and browsed to the ADB directory I never get the # confirming I have root access. (I only get the $)
Now from what I'm reading Clockwork mod backs up the WiMax anyway but I still wanted to walk through the process to get more familiar with it. I guess my first question is do I really need to back up the partition and keys if I have a successful nandroid backup?
Also I installed root check and the under the basic setting it said I had no root access, and then under the advanced setting it said I did.
I tried installing Ti backup and clicking under problems to install busy box thinking that may be the problem, but I don't see the setting it describes there where I can change to install busybox.
Finally I also downloaded the busybox installer. It gives two options of where to install it in either /system/bin/, or /system/xbin/....does it matter? Will installing it this way be ok or do I need to push through ADB? If I need to push through ADB then obviously I need to get my # root access figured out.
Thanks in advance to anyone who can try and help me make heads or tails of this situation.
Radio: 2.15.00.11.19
Software Number : 3.70.651.1
Hardware Version: 0003
HBoot: 2.10.0001
Hi guys,
I've been reading through the forums over the past two days but I have to admit it's hard to find what I am looking for now that the G2 forum and the DZ forum are merged, and the search isn't getting me anywhere for this one.
I have Bell Canada Desire Z permarooted and S-OFF'd, with CWMod. I did this before the newer gfree method and from what I can gather this can lead me to some kind of endless loop if I try to flash back to the a Bell RUU or other RUUs for that matter. It also worries me that I can't try new radios, etc.
I am getting very poor battery life compared to others so I want to have my phone replaced. I have an extended warranty from FutureShop so I probably don't even need to reset the phone to stock again (they swap on the spot) but I would like to anyway. It will also allow me to test the battery again with the stock ROM.
So, how do I go about flashing back to the Bell ROM and turning S-ON, and unrooting? Keeping in mind that I used the pre-gfree method. I believe it was Visionary R12 and gtab's guide.
Also as the title implies, I was wondering if it's possible to use the new (better) S-OFF even if I am already S-OFF'd the old way?
Any help is appreciated!
You can use gfree and achieve "real" S-OFF without having to unroot.
Just run it. Worst that'll happen is it fails if you happen to be on a kernel it doesn't like. If this happens, no harm is done, just a reboot.
Just run gfree from where you are, as the previous poster said.
That will put you in a much safer position, where you can get stuck in that boot loop that you can if you've only got the eng hboot.
Then you can flash whichever ROM you want. Then you can undo gfree if you want via its new options (see the Wiki).
Regarding your point about the merger, IMHO this issue isn't anything to do with the DZ specifically, and lots of users are posting about similar stuff with their G2s. It's all the same
Thanks guys,
I've done gfree (which is MUCH easier than the thread and wiki make it look - they need to simplify the text, it's overwhelming to look at given how simple the procedure is) and flashed the Bell RUU.
Now I am just about to root, and use gfree to undo the S-OFF I guess?
Will let you know how that turns out. Thanks again!
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
I'd keep that backup file as it is a dump of your original partition 7 before gfree mods it. You can dd i back and put everything back to how it was, if you ever need to. Do you need to keep it on the phone? No.. store it somewhere on your PC.
With the old "fake" S-OFF you would get stuck if you flashed a stock rom because it would overwrite the engineering HBOOT which was the only thing making your phone think it had S-OFF. With gfree method, you have real S-OFF, so this should be fine.
See http://forum.xda-developers.com/showthread.php?t=838484 for details.
tl;dr You should be fine.
Hm,little bit confused!
The backup I need to get original original partition 7
but not to get S-On.
To get S-On I can use the new gfree method,it`s now
possible with this!
I did the old UBERROOT method with real S-Off!
P.S.I read here about this:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Not 100% sure I understand the question...but:
You don't need that backup file. If you delete it nothing bad will happen. Paranoid people (like me) would copy it to a safe place, but there's no real need.
You can flash whatever roms you like, including stock ones, as long as you have real, radio (gfree) S-OFF.
Hi guys, thanks for the help! I got it all settled, it was easy.
As I mentioned above, I used gfree to do a true S-OFF, which was easy.
Then I ran Bell's RUU and it worked without any issues. I assume the RUU install also flashes the HTC recovery back to the phone, I didn't check but it must..
A little summary for anyone who needs help in the future..
If you rooted/S-OFF'd using a method older than the current rage/gfree method (the one in the wiki) then you need to redo the S-OFF using gfree.
Steps:
Use gfree -f to S-OFF again
Run the stock RUU file on your pc (you need HTC sync installed for this)
Temproot (first part of the wiki guide) the stock ROM
Use gfree -s on to S-ON your phone
Reboot, and everything should appear like stock (aside from still being sim-unlocked).
Were u sucessful in returning your phone to htc after u did the above?
I didn't have to return it to htc, just to future shop, and it was fine.
Sent from my GT-I9000 using XDA App
Alright, I'll try not to make this an incomprehensible mess. I have an evo with s-off that I reset to stock after playing around with some ROMs. I used the unrevoked method to achieve s-off back then. Anyway, after the reset, I don't have superuser permissions. I do still have s-off, but I have no recovery flashed and as far as I can tell I need to get superuser permission first thing anyway.
The superuser app in the store doesn't do anything. As far as I've been able to find out, I need to flash superuser from the sd card. However, since I don't have a recovery installed, I can't do that. And since I don't have superuser, I can't flash a recovery.. see the problem?
So since my bootloader is locked I figured I'd try the HTCDev method for unlocking it, but when I get to the steps with the command prompt commands, I just get a "waiting for device" message. I tried installing the modified unrevoked drivers, which worked, but I still get the "waiting for device".
Basically I'm unsure what I'm supposed to do. Rooting the phone from stock is so goddamn easy, I don't know why it's being so difficult when I already have s-off. Any help would be appreciated. I couldn't find anything relevant by searching here or elsewhere.
AnHero said:
Alright, I'll try not to make this an incomprehensible mess. I have an evo with s-off that I reset to stock after playing around with some ROMs. I used the unrevoked method to achieve s-off back then. Anyway, after the reset, I don't have superuser permissions. I do still have s-off, but I have no recovery flashed and as far as I can tell I need to get superuser permission first thing anyway.
The superuser app in the store doesn't do anything. As far as I've been able to find out, I need to flash superuser from the sd card. However, since I don't have a recovery installed, I can't do that. And since I don't have superuser, I can't flash a recovery.. see the problem?
So since my bootloader is locked I figured I'd try the HTCDev method for unlocking it, but when I get to the steps with the command prompt commands, I just get a "waiting for device" message. I tried installing the modified unrevoked drivers, which worked, but I still get the "waiting for device".
Basically I'm unsure what I'm supposed to do. Rooting the phone from stock is so goddamn easy, I don't know why it's being so difficult when I already have s-off. Any help would be appreciated. I couldn't find anything relevant by searching here or elsewhere.
Click to expand...
Click to collapse
OH my god, it's so easy.
Download the attached files and place them on the root of your SD card. Run the PC36IMG file through your bootloader, and accept the update. Power off the phone (not going to explain that), then boot back into the bootloader. That will give you the Recovery that you need to flash the superuser app. Just go to RECOVERY after these steps and you will see.
I am in desperate need of unrooting my phone now, but due to it being almost 2 years that I've owned this phone I can't remember how I rooted it in the beginning. Any way to figure this out?
Need to know your Hboot version and radio, and also is the phone S-ON or S-OFF (power off, then volume down and power buttons simultaeously).
HBOOT-2.18.0001
RADIO-2.15.00.12.19
Phone is S-OFF
Thanks for your help.
On a side note, my phone is in an infinite boot loop that only loads to the white evo screen, I can't flash custom recoveries, roms, or RUU. I think the problem is the fact that it says LOCKED in the pink label at the top of my bootloader. I tried using the command fastboot oem lock and it says it's already locked and doesn't unlock it or anything of the sort. If you know any way to aid my problem I thank you for the help.
Most infinite bootloops are never fixed, however;
The best advice that I can give you right now is to download these two files.
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
http://goo.im/stock/supersonic/ruu/...15.00.12.19_NV_2.33_release_234563_signed.exe
Connect your phone to your computer, then boot into your bootloader and click on FASTBOOT. The phone should be in FASTBOOT USB. Install the HTCDrivers exe file to your computer. Then try to run the RUU file with the phone still in FASTBOOT USB.
If that doesn't work, then the phone may already be permanently bricked. Interestingly, the phone was rooted nearly 2 years ago, but you have the latest everything. I hope you did not do that with OTA updates.
Thanks shortyydoggg, unfortunately I've tried that method with those exact files already and had no such luck. My last resort is that if I can change the LOCKED pink label to RELOCKED or UNLOCKED, I'll be able to flash through the bootloader again, and temporarily use my phone once more until i can get the EVO LTE. Also, there is basically no way to tell now which root method I used?
Yea, Unlocking the bootloader was going to be my other suggestion after trying the RUU. It's not much else you can do after that.
Sent from my PC36100 using xda premium
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
djs415 said:
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
Click to expand...
Click to collapse
That's the wrong command. You need to go to the htcdev site (www.htcdev.com), register, and unlock the bootloader. Since you're already S-OFF, have you tried running a PC36IMG file for a custom RECOVERY. You might not need to be unlocked to do that.
I'm almost positive I tried to flash a custom recovery through the bootloader and it didn't work... however, you were right and my bootloader is now unlocked so THANK YOU! Will post back after flashing the recovery you attached.
To answer your previous question about which root method you used, unrevoked-forever was used at some point to S-OFF the phone, since you are on Hboot 2.18 and still S-OFF and not on the old Engineering S-OFF Hboot. Whether the phone was rooted with Unrevoked, Toast Method 2, Simple Root or AutoRoot, there is no exact way to tell right now, but it can be guesstimated that it might have been Unrevoked.
Now for the confusion if you dare to read:
AutoRoot is Toast Method 1, unrevoked-forever, and a custom ROM inside a program, and Simple Root is Toast Method 1 and a custom ROM inside a program along with the engineering S-OFF bootloader. Unrevoked is uh, Unrevoked and Unrevoked forever inside a program. Toast method 2 is just a custom ROM flashed along with the same S-OFF bootloader as SimpleRoot. If you used Toast Method 2, then you did everything AutoRoot did in order to S-OFF the phone. You just needed unrevoked-forever to keep it S-OFF for any other and your bootloader. Toast Method 1 alone does not S-OFF the phone. If you used SimpleRoot, which does not use unrevoked-forever, you needed unrevoked-forever at some point again to keep the phone S-OFF on any other Hboot (your 2.18). So again, you would have done everything AutoRoot did.
So that brings it down to AutoRoot and Unrevoked, since everything else you did is the same thing that AutoRoot does. Since you rooted nearly 2 years ago, and Unrevoked-forever is inside AutoRoot, AutoRoot has to be newer than unrevoked-forever to contain it inside its program. Also Unrevoked is newer than AutoRoot and already contained Unrevoked-forever. So the likely-hood that you used Unrevoked is very great, but not for sure. It is also the easier method and the one that nearly everyone else used at that time.
Somehow, still no luck. Flashed that file you linked and it goes through successfully, asks to reboot and then back to white screen boot loop. How can this be possible at this point, with the bootloader unlocked it goes through with the process but the actual writing of the data seems to fail. Trying the RUU one last time now that it is unlocked, but if this doesn't work I'm stumped.
I thought the whole beauty of the the bootloader, and more importantly being able to reach it, was that it meant your phone couldn't be bricked. Last try, will report back.
Bootloader unlocked, RUU flashed this time through PC. Nothing, and completely out of ideas here.
Shortydoggs been doing a lot of help around here for similar situations. There have been cases (maybe a dozen I've seen) where people get into a situation like yours where bootloader is accessible , but that is about it. And from what I've read, in those cases, when the phone tries to boot, it does 4 or 5 short vibrates before going back to bootloader.
Your situation is also strange in that, you rooted 2yrs ago, but don't have S-off, a locked bootloader. Hboot 2.18, which is the latest but is unlockable thru HTC dev, but no S-off available for it yet. And your radios are latest, too (mostly irrelevant).
First there was toasts root for baseband 1.37 (which downgraded you to 1.17 with eng hboot to get s-off before bringing you back up to 1.37). Then there was simple root by jiqqaman, which worked for people who took the baseband 1.47 OTA. Then when froyo came out, anyone who took that OTA (baseband 3.25, or 3.26, I forget) had to wait for unrevoked to be developed. I think hboot at that point was 2.08 and 2.10. Unrevoked forever worked on that, and gave you S-off.
I know none of that info helps you necessarily. It's just puzzling how you rooted 2yrs ago, bit have the latest hboot with S-on. Maybe you didn't finish toasts part 2 S-off guide, then sometime recently updated your radio and hboot? No. You need S-off to flash radio. Were you recently on a stock rooted ROM and took an OTA (is that even possible) when you were still S-on (from not finishing toasts guide)?
Sorry, I know it's not a lot of help. Just trying to figure out how things could not match up so much, and if that's how you ended up in this situation (that could be helpful info for others). I hope you don't have the bootloop of death and can get it sorted. Between shortydogg and captain throwback, I HAVE seen some phones saved.
sent from 2yr old Evo on ICS
Yea, I'm not going to waste your time any further. There's not much else to do.
Ya unfortunately I'm quite confused myself... however, if this information helps you at all... For starters, I have S-OFF and until recently (2 weeks or so since my phone started acting up like this) I was running a ROM perfectly fine until one day it restarted into this never ending boot loop. I'm not sure how my HBOOT is the most up to date, seeing as I was always very careful not to do something stupid like change my HBOOT for no reason. The interesting thing is that I had never seen that pink label before on my bootloader saying unlocked or locked OOW until the problem started occuring 2 weeks ago.
Also something I'm realizing... are you telling me that the HBOOT I have does not have S-OFF yet, and therefore you can't flash roms or custom recoveries... but my bootloader still says I am S-OFF. So the problem is I am S-OFF for the most recent HBOOT which can't be changed to S-OFF yet? Could downgrading hboots work?
He did not realize that you were S-OFF. Your phone is set to stay S-OFF regardless of what Hboot you have or how that Hboot usually comes.
Also, your phone appears to have a hardware, and not software issue, so, changing Hboots, might not hurt to try, but may not help much. In case I'm wrong, do not try anything below Hboot 2.10. Here is one for 2.16.
What rom were you running up until the time the bootloops started happening? This sounds alot like the cyanogen mod bootloop of death which no one has ever fixed I believe.
I believe I was using some version of SOS or a sense rom, but I'm leaning more towards SOS.
Just tried using that HBOOT thought it's still not working. Would going to the engineering hboot make any difference?
What could be the hardware problem causing this?
I see that shortydogg is in here taking good care of you .
The bottom line is, if you can't flash/get into recovery from HBOOT, you're probably in an unrecoverable situation.
It's unclear after my review of the thread, but you have tried flashing a recovery through HBOOT using a PC36IMG.zip file, right? And then after flashing, you choose not to reboot, but to boot into Recovery?
If you can get into recovery, then we can resolve your issue (if in fact it is software related).
If the problem is bad NAND blocks on your recovery or boot partitions, then there's nothing that can be done.
Also, the watermark on your bootloader (LOCKED, UNLOCKED, etc) has nothing to do with your issue. That's just connected to the version you were running. As long as you're S-OFF, that's irrelevant.