Related
I tried to update my Hboot the other day to .92 i believe from .78. Thinking it was as simple as flashing it through bootloader and thats it. I was stuck at the white htc screen for hours so I figured I was screwed. I wiped everything with no luck and then I flashed something so now my HBoot is 0.77.0000 and my Radio is 1.00.03.04.06. I was previously running CM7 nightlies. After flashing whatever zip I did I was trying to reverse what I did by "downgrading" and what I did was delete everything. I cant boot and I also dont have recovery anymore. I can only use Bootloader. PLease any help I can get is appreciated. If u can tell me how to fix this ill make a 10 dollar donation to your paypal. My e-mail is [email protected] if u want me e-mail any information. Thanks a ton
Try the following link.
You may need to get an usb sd card reader. That way you can put the needed files using your pc.
I am sure someone more knowledgeable will come along to help you.
I read somewhere that if you can get to the bootloader, it might have not neen bricked yet.
http://dougpiston.com/?page_id=77
Download this file
http://www.fourty.net/~berzerker/sto....605.1_RUU.zip
Rename it to PB31IMG.zip, put it on the root of your SD card, Boot into the bootloader (hold vol- and pwr) and let it run the update. After it is done you will be back to a stock 2.2.
I forgot to mention in my initial post that I also updated my radio to the newest 2.15 but still had recovery after I did that and after that is when I tried to downgrade everything and lost my recovery. Didnt know if that makes a difference or not. Thanks for the quick replies
Goos3y that link you sent me says 404 not found.
ok there is hope. I am a littl confused though. Do you have recovery?
No i do not have recovery only hboot. I am using my lady's Droid X with my SD card to put any files on the card that I need to.
http://dougpiston.com/?page_id=108 download the PB31IMG.zip put it on the root of the sd card and flash through bootloader as previously stated. Make sure it is named PB31IMG.zip or it wont get recognized. You will loose root and have S on. Thank doug piston for the dl.
sent from my streak7
this is not in the right section but if you can still get into recovery restore a working nandroid back up. after that go to backup and restore>advanced restore and restore your boot image. im pretty sure upgrading you hboot erases your boot image.
EDIT: I saw that someone posted a PB31IMG up earlier. I'd try that one first,
This is for the RUU exe.
An RUU is a program which links to any phone that can get into bootloader, and installs a completely unrooted stock image to your phone. It can be done either by using the linked program (an exe) or getting an ruu version that is a zip and running it on bootloader with a specific filename "PB31IMG.zip"
This tutorial is for the EXE version linked below.
WARNING: I have no idea what happens if this is used on an SLCD incredible.
Therefore, you need to know what kind of screen you have, and I'm no expert on that.
DONT use this RUU if you find out you have an SLCD screen.
I am not sure whether android sdk tools or htc usb drivers are nessesary for the ruu, so if anyone can comment on the necessity of these, i would appreciate it.
Heres what you need:
1. A PC
2. The RUU exe file
3. a cable to connect the PC to your phone
4. The knowledge of whether your phone is an SLCD or not.
Instructions:
1. Hook up your phone to the computer
2. Put the phone into hboot
3. Run the ruu
4. If it messes up at the usb detection thing, keep the phone plugged in, exit the ruu program, and then run it again. It should work then.
At the end of this process you should have a fully functional unrooted froyo incredible.
You dont need to give anyone $10. We all want your phone to work.
The link:
http://forum.xda-developers.com/showthread.php?t=829783&highlight=ruu
Thanks Football!
Hellzya said:
http://dougpiston.com/?page_id=108 download the PB31IMG.zip put it on the root of the sd card and flash through bootloader as previously stated. Make sure it is named PB31IMG.zip or it wont get recognized. You will loose root and have S on. Thank doug piston for the dl.
sent from my streak7
Click to expand...
Click to collapse
You will lose root (easy to get back) but will still be S-off.
You can either use the PB31IMG or the .exe method. Just grab the files off doug piston's website. We've had a lot of problems with SLCD owners grabbing the RUU off youtube and other sites then having a screen that no longer works.
I tried the PB31IMG zip method but in hboot after searching through the file it says no image. I am going to try the RUU now. Do i need to have the android sdk stuff on this computer for the RUU to run correctly? I am using a different laptop, one which does not have the driver files installed that I needed to initially root my INC.?
s197 said:
You will lose root (easy to get back) but will still be S-off.
You can either use the PB31IMG or the .exe method. Just grab the files off doug piston's website. We've had a lot of problems with SLCD owners grabbing the RUU off youtube and other sites then having a screen that no longer works.
Click to expand...
Click to collapse
Unfortunately Marty, its not easy to tell which is amoled and SLCD without having the phone on to verify that its hardware revision is 002 or 003.
002=amoled
003=slcd
If you still have the box i'd recommend looking at it.
I thought you loosed s-off but ok. Did you make sure the PB31IMG.zip was not named .zip.zip?
sent from my streak7
marty454 said:
I tried the PB31IMG zip method but in hboot after searching through the file it says no image. I am going to try the RUU now. Do i need to have the android sdk stuff on this computer for the RUU to run correctly? I am using a different laptop, one which does not have the driver files installed that I needed to initially root my INC.?
Click to expand...
Click to collapse
Well, if you run it without them, and it doesnt work, it wont make anything worse. It just wont work, and then youll know. It probably has nothing to do with the SDK and more to do with HBOOT USB drivers. I would say go for it without any of that.
The most important thing you can know is that your incredible is not bricked. Its totally fixable.
I screwed mine up in precisely the same fashion early on, and used the EXE with good success.
Im positive. I got the phone in august of 10 through verizon. I dont have the box anymore. I have looked into it before and think "think" I have the amoled screen.
marty454 said:
Im positive. I got the phone in august of 10 through verizon. I dont have the box anymore. I have looked into it before and think "think" I have the amoled screen.
Click to expand...
Click to collapse
August = AMOLED
SLCD didnt start to ship until september.
The RUU is loading now. Its at 76% on Updating system. So, if this does work where does my phone stand? Do I need to re-root get s-off and things of that nature?
You will still have s-off. Your phone will be on a .92 hboot with the 2.15 radio. You will need to either rerun the root tool to get recovery back or use a recovery that is flashable through hboot. If using the PB31IMG didn't work for you before I suggest rerunning the tool.
Once recovery is installed do not attempt to restore from within recovery, instead download another rom and flash it through recovery.
Just wanted to drop back in and say thanks to everyone who helped me get my INC back. I really appreciate it and I can throw the BB Storm back in the closet!
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
What problems are you having with the RUU that you flashed? You can't downgrade, as you found out, so being stock S-ON you don't have many options other than flashing a different 2.3 stock image, and/or waiting for the actual OTA.
resyek83 said:
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
Click to expand...
Click to collapse
The only way i know to get back to 2.2 is to s-off your phone then ruu the 2.2. which will get you back to s-on 2.2, but you will be get the update nag every day once they start pushing the OTA out again.
resyek83 said:
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
Click to expand...
Click to collapse
For the moment, I think you are SOL, only because the same thing happened to me.
If you have 2.3.4 and S-ON, there's not really a way to downgrade back to 2.2, as HBOOT won't allow a downgrade. In fact, only PB31IMG.zip files that are signed by HTC will allow to be flashed. All others will not be recognized by HBOOT.
Unrevoked will no longer root after you have flashed RUU and have S-ON. You will get the error you are describing.
I have also tried newer root tools, such as Revolutionary, which is in the Beta phase.
Unfortunately, this method is not supported for the Incredible, and per Unrevoked's support channel on IRC, this is not likely, as apparently a phone that is only over a year old is considered a 'Legacy' device.
At this point we can only hope for the following:
HTC unlocks the Bootloader for the Droid Incredible on HTCdev.com. Only a handful of devices are listed at the moment.
Team Unrevoked releases a new version of Unrevoked that can find an exploit for 2.3.4 and enable root.
Revolutionary adds support for 'legacy' devices such as the incredible.
We are in a small minority, but hopefully enough devices will get the OTA, or refurbs get sent out with 2.3.4 that users will eventually require a new way to root.
Hang in there.
Yeah, if you're s on then from everything I've read, your screwed for now.
ahh ok....yea i kinda figured. I should have done a tad more research before I did it....everything works ok at the moment, except my battery life isnt as good as it was, but its not terrible. I guess I'll wait for the official OTA or wait and see if Unrevoked can come up with a solution.
your best option woulda been to root first. While you still had S-off flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-on.
TheBr0ken said:
your best option woulda been to root first. While you still had S-on flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-off.
Click to expand...
Click to collapse
Doing that with S-On is what has OP in this position in the first place. You have the right idea but mixed up S-On and S-Off.
TheBr0ken said:
your best option woulda been to root first. While you still had S-on flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-off.
Click to expand...
Click to collapse
Thank you, Captain Hindsight. In my situation, I was coming from a Rooted, 2.3 Sense 3.0 ROM, with S-Off.
I believe S-off is swicthed back to S-ON when you flash the RUU.
In the mean time, my phone is borked. Too new of a firmware on too "old" of a device.
SlimSnoopOS said:
Doing that with S-On is what has OP in this position in the first place. You have the right idea but mixed up S-On and S-Off.
Click to expand...
Click to collapse
yup, fixed.
deadsoulboy said:
Thank you, Captain Hindsight. In my situation, I was coming from a Rooted, 2.3 Sense 3.0 ROM, with S-Off.
I believe S-off is swicthed back to S-ON when you flash the RUU.
In the mean time, my phone is borked. Too new of a firmware on too "old" of a device.
Click to expand...
Click to collapse
what killed you was you musta flashed the s-on patch for some reason. I ran the same file you did. I still have s-off
The RUU does NOT turn the security flag to -ON. You do lose root until you flash a custom recovery and superuser, which is done easily.
Any hope for us S-ONs with 2.3.4? Is there something by way of unrevoked or something we can flash to try and get back to root?
There has to be something...
So I have a droid inc that I'm sending back in, and I want to revert it to stock. Right now, I'm running s-off, with a rooted stock OTA 2.3.4 (Incubusj's, I think) with the latest CWM. What do I need to do to make this thing bone stock to return it? I've done a search, and maybe I just suck at searching, but I can't find good, concise directions, and I don't want to screw it up.
sk8erord said:
So I have a droid inc that I'm sending back in, and I want to revert it to stock. Right now, I'm running s-off, with a rooted stock OTA 2.3.4 (Incubusj's, I think) with the latest CWM. What do I need to do to make this thing bone stock to return it? I've done a search, and maybe I just suck at searching, but I can't find good, concise directions, and I don't want to screw it up.
Click to expand...
Click to collapse
Search for the Ultimate get back to stock thread. It'll tell you what you need to to to get back to Stock 2.2 with S-ON.
That thread seems rather old. I'm running the 2.15.10.07.07 radio on hboot .92. Do I still just run the s-on and then run the RUU?
Well, was probably unnecessary, but I reverted to the old radio, flashed a rooted stock rom, then ran s-on through recovery, then a stock pb31img rom through bootloader. So it is bone stock again.
sk8erord said:
That thread seems rather old. I'm running the 2.15.10.07.07 radio on hboot .92. Do I still just run the s-on and then run the RUU?
Click to expand...
Click to collapse
True, that thread is old, but the info is still good. Good call on reverting back the radio, as you don't want that to cause any troubles. Pretty easy to get back to stock and S-ON huh?
So the usb port on my EVO is messed up. Sometimes I have to wiggle it around in order for it to charge and if I move the usb cable it disconnects. This also makes it a hassle to transfer files between my phone and PC. I want to bring in my phone to repair, so I have to unroot it. I just want to make sure I go about this correctly. I want to unroot it and have it still be rootable again. I don't know what information you guys need, I'll give you as much as I can.
Hardware 0003
I rooted it with unrEVOked 3 and I didn't have to use the unrEVOked forever s-off patch, the unrEVOked 3 did that. I rooted it stock (did not update ever). I'm currently running a 2.3.5 rom with HTC Sense 3.5.
Would flashing Forever S-ON and then a PC36IMG through hboot be all I would need to do? Would the phone be rootable again after they repair it?
Yes, put a pc36img of a stock rom on the root of the card, then reboot and run s-on tool. Or run s-on tool and then run a stock ruu.
My radios or anything like that don't matter?
Also can I have a link to a stock PC36IMG? I have one but I don't know if it's 2.2 or 2.3.
Edit: Nvm it's froyo! I will unroot and update you on my progress.
When I attempted to flash S-ON, I got an error:
Unsupported radio version.
I booted into HBOOT, my radio is currently 2.15.00.05.02
How do I downgrade (or upgrade, whatever I need to do) my radio?
vulf search for calkulkin's thread about radios. The thread has every radio starting from the beginning to the newest radio. Take an older one and flash it in recovery. You should be good to go.
Sent from my PC36100 using Tapatalk
Ok, I rooted with unrevoked a long time ago. Broke my screen and need to unroot. I followed the unroot unrevoked guide as closely as I could, but the rom in the link was not found. So I downloaded a different ruu.zip of factory rom, don't ask me which one, because I can't find the link anymore, but currently here is where I stand. Hboot kept saying that the img was older or something, and wouldn't flash. So I did a stupid thing and pushed the zip with clockwork. So now I'm running s-on with clockwork recovery and a stock unrooted rom. So, I tried the next thing, downloaded an 3.7 ruu .exe and tried to run that from windows, but it gives me an hboot usb connection error f*ucking **** 1 thing after another.
This is the unrooting guide I used http://forum.xda-developers.com/showthread.php?t=780141
I got s-on, and tried that pc36img but it wouldn't work, originally. Before I went on to screw things up.
I've been at this for hours, something that should have taken 10 minutes if I wasn't an idiot, or bad links, or what ever. Can someone tell me or point me in the right direction, of what to do here, preferably not to a 2 year old thread with outdated links? What should I do?`
A List of android stock RUU zips with radio, pri, recovery all in one would be great, but I give up on trying to find that, its buried or does not exist.
I found this list http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs but its just the rom not everything.
So here is where my phone stands
S-ON
Hboot .97
Clockwork recovery 2.5.0.7<<<<<<
Android version 2.2.2
Build number 4.54
PRI 1.90_003
Angrychair420 here is a stock RUU that I know is good you should be able to run the RUU from windows.
http://geekfor.me/evo/ruu/evo_ruu_1326511/
thanks, that says its img version 1.32.651.1, assume thats safe to use. I assume thats andoid 3.26 which is what came on my phone. Ugh I'm in over my head. Why did my screen have to break, i was totally happy with CM7 and everything the way it was.
what if I wipe my data and caches, remove SD card, put on a PC36IMG.zip and boot the phone into hboot, will it still give me the older version error?
edit: the link you gave me gives me the same error as the other ruu.exe:
The ROM Update Utility cannot update your android phone
Please get the correct ROM Update Utility and try again
Possibly but I did have to return mine for repair and I know that using it as a .exe file trough windows I had no problem. Not sure about making it into a PC36IMG.zip file though I have not tried it that way.
Angrychair420 said:
thanks, that says its img version 1.32.651.1, assume thats safe to use. I assume thats andoid 3.26 which is what came on my phone. Ugh I'm in over my head. Why did my screen have to break, i was totally happy with CM7 and everything the way it was.
what if I wipe my data and caches, remove SD card, put on a PC36IMG.zip and boot the phone into hboot, will it still give me the older version error?
Click to expand...
Click to collapse
It might. There are 3 PC36IMG files in the first "My Links" link in my signature. You can try them in order if you'd like, if you get the "main version is older" message, but if the first two don't work, the last one definitely will.
Thanks cpt, about to give them a try. Sigh man, this is frustratingly harder than rooting :-D If it was as easy as doing the s-on and copy the pc36img.zip to the root of sd and booting into hboot and DONE, I would of been having a much better day.
Try the latest RUUs from this link man:
http://www.filefactory.com/f/acf0b850b0f70d7b/
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
You can also try this
http://www.goodandevo.net/2011/03/how-to-unroot-your-htc-evo-4g.html
I appreciate the help guys. I will keep posted. You know how much it sucks to slide on a touchscreen thats broken? lol
partyman1971 said:
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
Click to expand...
Click to collapse
Yes, that's the first RUU.exe I tried. said this RUU can't update
ok i got a pc36img.zip installing from hboot right now.
edit:dang main version is older error. Trying a wipe then hboot then pc36img.zip
Same outcome, main version is older.
partyman1971 said:
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
You can also try this
http://www.goodandevo.net/2011/03/how-to-unroot-your-htc-evo-4g.html
Click to expand...
Click to collapse
yes, they are basically the same method I used in my OP from xda forums.
On to captain_throwbacks second ruu.
Just to make sure, this all isn't in vain, and make you all hate me, after applying one of these successfully, my recovery should go back to factory and no longer be clockwork, right? or wrong, because I'm starting to think I am. But won't taking your device in for service with clockwork be a dead giveaway that it was rooted.
I think I'm just going to go get a new phone for a $100 deductible at this point. and replace the screen my self on my old one and keep it as a backup/test device. Thanks for all the help, but I am surrendering :-D hopefully I can reroot this thing again with unrevoked, since my hboot is still .97 and fix the screen my self.
It generally doesn't matter if its rooted. I've never unrooted since launch day. And I've had 3 screen replacements, 3 speaker rwolacements , a bezel replaced, and camera lens cover replaced (last time, I dropped it off with ICS), about to go get my 4th screen (just cracked it again lol).
Sorry for your experience/frustration.
sent from AOKP heaven
well last stupid question i promise, since i still have clockwork isntalled, i can just restore my CM7 backup, but how do i get s-off back, re unrevoked it i assume?
If your'e worried about the warranty thing, just flash a stock rooted rom, or use a phone repair service. i see three or four repair places on craigslist (granted, that you live in a large city).
yeah no worries. Got it back to S-OFF, and CM7 back on it, just going to fix the screen my self, ordered one for $15.
thread can be locked, deleted, or what ever.
Seriously. Dude, isn't there a sprint store near you?. Just take it in. Put a stockish rom on it if you're that worried about it. They should replace it for free.
sent from AOKP heaven
Wifes evo 4g started dropping data. Running cm9. Tried cm7. Same thing. Tried all of the sense stuff posted throughout... anyway. Decided to ruu and start fresh. I don't recall what the hboot originally was. Its been a hella long time since this thing was rooted. Read several threads where it said all the stuff needed to match up for ruu to work (hboot, radio, pri, etc.) Installed hboot 2.16 and all of the matching stuff. Ruu.exe failed with the usual usb failures. Read more. Found that the pc36img.zip ruu works better. Found one. Matched up all of the stuff again. Installed and earlier hboot. Again everything failed. Later I noticed on a thread that hboot 2.16 it not downgradeable. But, when I installed the older hboot, it distplayed the older versions of the hboot when vol.down + power.... wth? I've since then tried 2.16 again and also the 6.16 I found in another thread. I can install any of these and it shows the installed hboot. But I can't fastboot a pc36img.zip on any of them. When it runs through the green text where its looking for the .zip or .nbh, etc. it never picks them up. I've tried it with recoveries, ruu's, splash images, etc. No go. I've made sure all of the PC36IMG.zip files are spelled the right way and not .zip.zip, etc.
Has anyone ever seen this before? Any ideas? I just want to ruu the dang thing and start fresh. Is it possible that it has remnants of multiple hboots lingering around causing errors? I know this sounds stupid, and I agree. Its the craziest thing I've seen. I can flash images with joey krims flashimagegui, and can change radios, hboots etc when flashing the zips from within recovery, just can't run any PC36IMG.zips.
Any pointers
Sent from my PG06100 using xda premium
jsp254 said:
Wifes evo 4g started dropping data. Running cm9. Tried cm7. Same thing. Tried all of the sense stuff posted throughout... anyway. Decided to ruu and start fresh. I don't recall what the hboot originally was. Its been a hella long time since this thing was rooted. Read several threads where it said all the stuff needed to match up for ruu to work (hboot, radio, pri, etc.) Installed hboot 2.16 and all of the matching stuff. Ruu.exe failed with the usual usb failures. Read more. Found that the pc36img.zip ruu works better. Found one. Matched up all of the stuff again. Installed and earlier hboot. Again everything failed. Later I noticed on a thread that hboot 2.16 it not downgradeable. But, when I installed the older hboot, it distplayed the older versions of the hboot when vol.down + power.... wth? I've since then tried 2.16 again and also the 6.16 I found in another thread. I can install any of these and it shows the installed hboot. But I can't fastboot a pc36img.zip on any of them. When it runs through the green text where its looking for the .zip or .nbh, etc. it never picks them up. I've tried it with recoveries, ruu's, splash images, etc. No go. I've made sure all of the PC36IMG.zip files are spelled the right way and not .zip.zip, etc.
Has anyone ever seen this before? Any ideas? I just want to ruu the dang thing and start fresh. Is it possible that it has remnants of multiple hboots lingering around causing errors? I know this sounds stupid, and I agree. Its the craziest thing I've seen. I can flash images with joey krims flashimagegui, and can change radios, hboots etc when flashing the zips from within recovery, just can't run any PC36IMG.zips.
Any pointers
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Hey jsp..., read your post...sounds like when you tried to flash the diff radios, boot.img, etc. you changed to s on by mistake preventing you from flashing th pc36img. verify? you should just be able to flash a ruu.exe from your pc after achieving s-on to be completly stock and re root from there. however, if youre re rooting you dont need to go that far as to achieve s on. so it sounds like you are doing the right thing...it just sounded like what i did by flashing a new radio and loosin root and not able to do anything. what hboot do you hav now? can you see any watermark or s off? if no then you lost your privleges and have to do a root method that supports what hboot you have. let me know some more details.
this is crazy. im s-off, and still rooted. i still havent been able to flash any ruu. i've just about said screw it, but thought i would play around. cant really screw it up.
i can flash recovery flashable files from cwm, twrp, and ra.
i can "fastboot flash zip name.ext" from cmd in windows 7 as long as i'm running hboot 0.76.
i JUST CANNOT flash a freaking PC36IMG.zip from hboot. none. not a damned one. no splash. no recovery. no ruu, no damned thing.
the green text just goes right on past it. doesnt even slow down to smell it. i cant figure it out. i have tried every single hboot listed in caulkin(sp?)' thread. every danged one of them.
i did however get a modified ruu to work. i took the 4.54.651.1 ruu and inserted hboot 0.76 inside it so i could maintain remote fastboot abilities. it worked, except i was still s-off, had that hboot, and had no superuser at all.
although i would like to know what is causing this, i cant really complain i guess. i cannot get into a hboot-loop because it tries to reflash a PC36IMG.zip each time it cycles. it scrolls right on passed it and gives me the recovery option. but, on any hboot other than 0.76 i dont have an option to flash anything. again,