Develop Bugs

[Question] Bootloader broken?

I was trying to redo Toast's part 1 method for root and when I flashed the PC36IMG.zip, it suddenly stopped, the screen flashed, it showed the status again, but then failed. Now whenever I try to flash a PC36IMG.zip, it loads fine, but then shows "Checking PC36IMG.zip..." After that, it takes me back to the menu, without giving me the option to flash. This is really frustrating, and I can't seem to fix it. I tried running the RUU but got a bootloader incompatible error. Please help!

What version do you have 1.3xxx or 1.47. xxx? If you have 1.47 you wil need the newer ones to root then run toast method.
Sent from my PC36100 using XDA App

Just a little heads up, ask the MOD to move this to Q & A so you don't get flamed.

does it flash the "checking sdcard for PC36...." and then go back to the bootloader? If so, you may want to assure PC36IMG.zip is on your SDCard and that it's formatted as fat32.

Sorry, wasn't sure if this should be a development or Q&A question. Mods please move. Thanks afflaq, that is the problem I'm having. I'll try reformatting the sd card and see if that helps. I just can't figure it out. Its almost like something broke in the bootloader. Anyways, I'll try to reformat and try again.

Tried a different SD card and formatted it. Still has the exact same problem. I think my HBoot is messed up. Does anyone know how I can fix it without using the PC36IMG.zip method?

Is it actually named pc36img.zip or just pc36img? If you have the .zip it won't read it. Not sure if this is your problem but troubleshooting here.

Huoter is a flame

churchwin88 said:
Is it actually named pc36img.zip or just pc36img? If you have the .zip it won't read it. Not sure if this is your problem but troubleshooting here.
Click to expand...
Click to collapse
Its pc36img.zip. I can check and make sure its not zip.zip, but I'm pretty sure it isn't. It loads, so it must have the right name, but then it says checking and after a few seconds just stops. My phone is having some major issues lately, and since I can't seem to use the PC36IMG method, does anyone know where I can pick up the latest RUU? The older one won't work, so I need the newest one even though I'll lose root. This is a freaking nightmare!

Ok, I tried the latest RUU and everything went through. I'll go follow the instructions to root it again and hopefully I'll be able to get everything working again.

Ok, I used quickroot and everything seems fine. Even loads the PC36IMG.zip's correctly now. Thanks for everyone's help. Hopefully this thread will help someone else who gets a bad bootloader.

UnrEVOked issue

I'm sorry if this has been covered before, but I couldn't find anything exactly like the issue. My friend has an EVO and asked me to help him with getting custom roms onto it, so we set out to root it last night. We used unrEVOked as it seems the most idiot-proof, and the last thing I wanted to do was brick his phone. The whole root process ran without a hitch, and afterwards we were booting into recovery, and when booting back into the main OS, the superuser app was on the phone. But, when I downloaded wireless tether, the computer would connect to the app, but no bandwidth was allowed.
The only issue I could think of was that we rooted with the sd card removed, as he was afraid of it being wiped for some reason. When the phone was booted into recovery, it seems like something error-ed out due to the sd card not being there. Any help would be GREATLY appreciated.

Are you using "Wireless Tether for Root Users"
http://www.appbrain.com/app/wireless-tether-for-root-users/android.tether
This app has many, many isuues. If you just downloaded it from the Market or AppBrain you likely got the generic, older build.
Go here...
http://code.google.com/p/android-wifi-tether/downloads/list?q=label:Experimental
for the various different versions and find one that works for you.

Thank you, I had no idea. When I get ahold of his phone next, I'll try one of those builds.

jrp07f said:
Thank you, I had no idea. When I get ahold of his phone next, I'll try one of those builds.
Click to expand...
Click to collapse
I could never get more than about .3kbs and .1 up and I tried em all. now finally with pre 15 it's working. I get about the same between my laptop tethered and what the phone gets by itself.

jrp07f said:
I'm sorry if this has been covered before, but I couldn't find anything exactly like the issue. My friend has an EVO and asked me to help him with getting custom roms onto it, so we set out to root it last night. We used unrEVOked as it seems the most idiot-proof, and the last thing I wanted to do was brick his phone. The whole root process ran without a hitch, and afterwards we were booting into recovery, and when booting back into the main OS, the superuser app was on the phone. But, when I downloaded wireless tether, the computer would connect to the app, but no bandwidth was allowed.
The only issue I could think of was that we rooted with the sd card removed, as he was afraid of it being wiped for some reason. When the phone was booted into recovery, it seems like something error-ed out due to the sd card not being there. Any help would be GREATLY appreciated.
Click to expand...
Click to collapse
I tried using Wireless Tether for Root as well and I had the same issue wihich forced me to search out a ROM that already had HotSpot unlocked, I am currently using Frost and it comes with the Sprint Wifi Hotspot unlocked and it works great. I know there are several other ROMs out there that also have this feature... If he isnt too hooked on the stock ROM, maybe you could suggest him finding a new ROM...

All right, I've confirmed root on the Evo and flashed clockwork recovery, and now trying to flash a rom. On the page for installing CyanogenMod, it mentioned installing an Engineering SPL, and I was wondering what the purpose of this is and if it is necessary. We are trying to install Warm if that makes any difference.

Boot Loops, forever.

So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!

Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App

i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...

Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App

I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.

You can also try wiping /system and /boot.

*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.

All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.

SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility

no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)

wow... what a bummer. thanks for the help anyway, it's much appreciated.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium

I'll try it again to verify the code, I'm pretty sure it was "170"

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had

sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468

This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App

=D
Sent from sweet snacks off tapatalk.

[Q] A little assistance would be appreciated!

Hey all! So, a couple weeks back, I flashed a BETA ICS ROM onto my Inspire (Desire HD). Being my normal ignorant, and noob-like self, I completely ignored the fact that the thread said "DEVS ONLY!"
Well, flash forward a couple of weeks, and my Inspire is all but bricked. The ROM did not have mobile data yet, did not have a connection to the micro-SD card, and it was not touchscreen ready yet. I have tried ADB, but to no-avail, my file system knowledge and overall lack of knowledge put me quite a predicament.
I have flashed many ROMs before, but I sincerely messed up big time on this try. So, would any of you be able to help me find a cure for this important issue? Is the fix really simple and easy, and I am just a bonehead?
Thanks!

Not sure what your issue is. You never clearly stated. Does the phone not boot? Stuck in the splash screen? you want to flash a new rom?

marsdta said:
Not sure what your issue is. You never clearly stated. Does the phone not boot? Stuck in the splash screen? you want to flash a new rom?
Click to expand...
Click to collapse
Oops, sorry! My problem is that my phone is stuck on the developer ROM, and I would like to fix it somehow. So, yes, I would like to get another ROM, but I have to remove this one first. The phone itself works great, but with no wi-fi, mobile data, and no touchscreen support, it is hard to live with.

Your nowhere near bricked. Going to ask the basics. Did you make a backup before hand? Did you have another rom on your SD card.?
If you answered yes to either then simply boot into recovery and flash the rom/ backup. You mentioned flashing roms before so I left out the steps.
If you answered no then you have two options. You can mount the SD card from within cwr. So download a rom on your PC. Mount the sd card, then flash away. Or take out SD card and use an adapter/other phone to transfer a new rom.

I was not smart enough to back up onto a computer, but I did back up onto the SD card. The only problem with this is that the ROM, and my computer, will not recognize that there is in fact an SD card inserted into the phone. So, in other words, it's like not having an SD card at all.

CWR will still read the sd card. Trust me. boot into CWR and restore your backup. And you be good as gold

Thanks! But, what exactly does CWR stand for? Haha, I'm not the most knowledgeable on the topic of Android, but is it like Clock Work Mod?

iTookTheByte said:
Thanks! But, what exactly does CWR stand for? Haha, I'm not the most knowledgeable on the topic of Android, but is it like Clock Work Mod?
Click to expand...
Click to collapse
yeah. CWR stands clockworkmod recovery

Okay, in that case, I'm not sure. All of my old files (CM7, CWM, etc.) were on the SD card, and it is unreachable. I have tried to boot into CWR, but it just gives me a black screen. I feel like this thing is just unable to be fixed!

its fixable. just the black screen in CWR is an obstacle. worst case is you have flash an ruu and start over with the whole rooting. i remember reading about the black screen in CWR give me a few minutes to find them to see what to do next

Okay! Thanks a bunch!

Pull the battery and put back in
Press and hold vol-down
Press power and bootloader will start
Select recovery using vol keys and press power
If you have a backup (you really should, and and if you don't consider this experience a learning one), restore it by selecting the backup / restore option
If no backup, goto mounts and select as storage, plug usb into pc and copy your favorite Rom over, then select back and flash from zip, select the zip and you should all be back up
But please, please I'm all for people learning and experimenting, but might be worth reading some of the basics guides and notes on roms before flashing the next one. Oh, and if I forgot to mention.... Do a backup before flashing ANYTHING saves heartache later, the enjoy
Sent from my HTC Desire HD using XDA App

THANK YOU! I remember this now! Thanks everyone

Your welcome, after all, we all have to learn sometime
Sent from my HTC Desire HD using XDA App

ok i couldn't find the specific thread i was looking for. i remember it being stickied but couldnt find it. did find something that might be usefull but it depends on if you have access to an sd card adapter or other phone to transfer the file needed to reflash CWR. If not i would suggest trying to see if flashing an ruu to help.
edit- I'm confused now. thought you said that when you boot into recovery all you get is a black screen?

[Q] Completed Factory Reset (MIUI) and SDCard format and now soft-bricked!

Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace the phone. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.

wigmuke said:
Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace it. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
Click to expand...
Click to collapse
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.

synisterwolf said:
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
Click to expand...
Click to collapse
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.

wigmuke said:
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
Click to expand...
Click to collapse
actually its better to keep it s=off so this type of situation wont happen. Your carrier cant see your hboot from my understanding on how this phone works. They dont care if you have root or not, unless you are trying to exchange the phone for another one from them or for insurance reasons. With root you only void your warranty on the phone and not your contract or anything to do with VZW. S=off is just a NAND lock, meaning you cant add your own custom recover to the phone, and you are limited to builds that come from VZW themselves (ie the security signature check).
If you ever want to take the phone back to them because its defective or call insurance then you need to remove root and S=on. but thats the only time you need to toggle the NAND lock.
ok so you will need to ruu to stock, downgrade then gain s=off over again:
for the ruu for GB:
http://forum.xda-developers.com/showthread.php?t=1227279
a guide to do this all after you ruu:
http://forum.xda-developers.com/showthread.php?t=1306400

OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.

wigmuke said:
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
Click to expand...
Click to collapse
You might have lost root if you did the ruu from hboot. to check download the app "super user" from market that will tell you if you still have root or not.

Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you recommend?
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.

wigmuke said:
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you all recommend?
Click to expand...
Click to collapse
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
---------- Post added at 10:44 AM ---------- Previous post was at 10:35 AM ----------
wigmuke said:
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
Click to expand...
Click to collapse
lol now worries. easiest way to get to the 10 limit is just pad the count in here. ie just say something 10 times and you are good to go.

synisterwolf said:
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
Click to expand...
Click to collapse
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.

wigmuke said:
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
Click to expand...
Click to collapse
Nope I'm RunNing that one and it works well.
Sent from my sexy assistant. (AMOLED HTC Incredible)