Develop Bugs

Trying to avoid a brick! Quick help.

I got myself into a interesting situation. A quick answer would be greatly appreciated:
1. I'm rooted.
2. Trying to install the OTA so I can run 2.2 the right way.
3. I started a thread asking for help because I was confused on unrooting my phone. Didn't get much help, a quick flame, and last someone chimed in to install the OTA from Rom Manager. I asked if I could do this with Root and the thread was killed.
4. I did. The boot screen was the new one. But the radio wasn't updated.
5. I then attempted to unroot my phone. Followed the PB31IMG.zip method. Phone booted normally. Root was lost.
6. This is where I am now.
7. My question is, if I install the OTA now renamed update.zip on my SD card, will I run the chance of bricking my phone because I installed it once from Rom Manager while I had root (#3/#4)??????
Please advise so I don't MOD EDIT up my phone.................
And if you're going to flame and insist I should of just followed the 2.2 leak instructions, you're correct. But I took someone's quick answer and tried it assuming they knew a better method.

mapko11 said:
I got myself into a interesting situation. A quick answer would be greatly appreciated:
1. I'm rooted.
2. Trying to install the OTA so I can run 2.2 the right way.
3. I started a thread asking for help because I was confused on unrooting my phone. Didn't get much help, a quick flame, and last someone chimed in to install the OTA from Rom Manager. I asked if I could do this with Root and the thread was killed.
4. I did. The boot screen was the new one. But the radio wasn't updated.
5. I then attempted to unroot my phone. Followed the PB31IMG.zip method. Phone booted normally. Root was lost.
6. This is where I am now.
7. My question is, if I install the OTA now renamed update.zip on my SD card, will I run the chance of bricking my phone because I installed it once from Rom Manager while I had root (#3/#4)??????
Please advise so I don't MOD EDIT up my phone.................
And if you're going to flame and insist I should of just followed the 2.2 leak instructions, you're correct. But I took someone's quick answer and tried it assuming they knew a better method.
Click to expand...
Click to collapse
Wat is the hboot versoin?
Sent from my Incredible using XDA App

Where do I find that out?

mapko11 said:
Where do I find that out?
Click to expand...
Click to collapse
In the bootloader it should say.
Sent from my Incredible using XDA App

Hboot-0.79.0000

mapko11 said:
2. Trying to install the OTA so I can run 2.2 the right way.
Click to expand...
Click to collapse
Well, "the right way" would be to wait for the actual OTA. Verizon would also have your back if you brick. But, anyway...
If you're still on the 1.00.03.04.06 radio, you can probably follow the instructions in that thread now that you've flashed back to the stock ROM. However, there still seem to be a few cases of people bricking their phones or being stuck in a bootloop after flashing leaks.
If you are confused/concerned/afraid of bricks then you just shouldn't flash the leaked OTA. This is not a flame, this is sound advice. Wait for the real one.

I'm fine with flashing. I just keep hearing about this "double install OTA and brick your phone" issue and I'm trying to avoid doing that. If the one guy didn't chime in with the suggestion to use ROM Manager, I wouldn't of had this issue.

My radio is still 1.00.03.04.06. I just want to make sure I don't run a risk of bricking.

If the hboot updated, i would say not to apply again. If it didnt update then i would say to see what happens, but dont take my word for it 100%
Sent from my Incredible using XDA App

jdkoreclipse said:
If the hboot updated, i would say not to apply again. If it didnt update then i would say to see what happens, but dont take my word for it 100%
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
How do I know if the HBOOT has been updated? I posted my version above?

mapko11 said:
How do I know if the HBOOT has been updated? I posted my version above?
Click to expand...
Click to collapse
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App

jdkoreclipse said:
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Anyway to undo this and go back?

mapko11 said:
Anyway to undo this and go back?
Click to expand...
Click to collapse
Try the PB13IMG.
Sent from my Incredible using XDA App

jdkoreclipse said:
Try the PB13IMG.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
And you needed to un root before applying the ota
Sent from my Incredible using XDA App

jdkoreclipse said:
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I personally have had a .77 HBOOT since I got my phone in April. My mom's phone, on the other hand, had the .79, which she has had since May, and she sure as hell didn't have no 720p camcorder. I don't think that the OP's phone having .79 means with any certainty that the OTA already applied once. I think the radio version listed on the HBOOT screen would be a better indicator.
But absolutely, running the PB13IMG should ensure that he's as far back as he can go, so why not try it just to be safe...

jdkoreclipse said:
Try the PB13IMG.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
That's what I just did before I posted this thread. I installed the PB13IMG and restored everything back to stock. You asked about the HBOOT version and that's .79. I'm comfortable flashing and doing the update. What should HBOOT say? Has anyone successfully updated the OTA from .79 HBOOT?
Thank you for the help. Sorry for the questions. I completely comfortable with rooting, flashing roms, and kernals. This is going back to unroot stock is just new.
I want to install the OTA and I'm good to go. Just making sure it's safe now....

alexdw369 said:
I personally have had a .77 HBOOT since I got my phone in April. My mom's phone, on the other hand, had the .79, which she has had since May. I don't think that the OP's phone having .79 means with any certainty that the OTA already applied once. I think the radio version listed on the HBOOT screen would be a better indicator.
Click to expand...
Click to collapse
Thats a high possibility that hboot means nothing in this scenaroi, but im not gonn. Be risky with someome elses phone. I only provide methods of doing things that i would use on my phone too.
Sent from my Incredible using XDA App

jdkoreclipse said:
Thats a high possibility that hboot means nothing in this scenaroi, but im not gonn. Be risky with someome elses phone. I only provide methods of doing things that i would use on my phone too.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Agreed, however, I noticed after running the PB13IMG, my HBOOT was also .79, which could have only come from the PB13IMG since I hadn't tried to do the OTA yet. Just trying to add pieces to the puzzle to get a better picture for future reference...I'm sure this guy wont be the last to ask...

alexdw369 said:
Agreed, however, I noticed after running the PB13IMG, my HBOOT was also .79, which could have only come from the PB13IMG since I hadn't tried to do the OTA yet. Just trying to add pieces to the puzzle to get a better picture for future reference...I'm sure this guy wont be the last to ask...
Click to expand...
Click to collapse
I appreciate the help guys. I guess my question would be if I ran PB13IMG, lost my root, back to stock, my HBOOT is .79 and my radio is still 1.00.03.04.06 and not 2.05.00.06.11, I should be at the same point as everyone else for installing the OTA from my SD card. Right or wrong?
When you read these threads and people are installing the OTA twice and bricking, are they installing the OTA again when the radio is already updated to 2.05.00.06.11?

Yep. I think you can flash it again, but be real cautious, as this is your second time flashing it, but if the radio is still the old versoin, you should be safe.
Sent from my Incredible using XDA App

Need help updating from radio 2.05 to 2.15

Hey all.
I am not ready to turn s-off yet. But I want to upgrade my radio.
The problem is when I try and use the same pg3img file I used to go to stock when I first went to 2.05 it tells me "main is older. Update failed"
And then I have to reboot.
So does anyone know what I am doing wrong. Do I need another pg3img file (can they only be used once?)
Or did I just mess something up?
Any help appreciated.
Sent from my ADR6300 using XDA App

Mean Sixteen said:
Hey all.
I am not ready to turn s-off yet. But I want to upgrade my radio.
The problem is when I try and use the same pg3img file I used to go to stock when I first went to 2.05 it tells me "main is older. Update failed"
And then I have to reboot.
So does anyone know what I am doing wrong. Do I need another pg3img file (can they only be used once?)
Or did I just mess something up?
Any help appreciated.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
from what i understand you need to have s-off to flash to 2.15

wowthatisrandom said:
from what i understand you need to have s-off to flash to 2.15
Click to expand...
Click to collapse
Correct. The whole process of flashing the 2.15 radio depends on the signature checking system within the bootloader to be disabled.

Thanks to both of you.
I didn't know this was the case.
Guess I will have to seriously consider turning s-off.
Sent from my ADR6300 using XDA App

It's easy as pie. If your inc has clockwork mod it can seriously be done in less than five minutes, along with that you can flash a stock recovery in case you have to return the phone.
Sent from my ADR6300 using XDA App

s-off, 2.15 radio, skyrider 2.2 = all within 15mins or less i think.

I may have to exchange my phone is why I am hesitating on the s-off.
I understand once that is done I can never truly go back to stock. At least not s-on anyway.
Sent from my ADR6300 using XDA App

Mean Sixteen said:
I may have to exchange my phone is why I am hesitating on the s-off.
I understand once that is done I can never truly go back to stock. At least not s-on anyway.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
You think the verizon guys are gonna find out if the flag is s-off or s-on?.. NO WAY!!..
As long as it boots and there is no water damage/screen damage.. you could be on Froyo for all they care!

The pbing file wont work because it consists of an older radio and hboot. The phone wont let you downgrade your radio unless you have NAND unlocked and S-off. The only way to get the 2.15 radio i think is to have S-off. Hope this helps

mikeacela said:
The pbing file wont work because it consists of an older radio and hboot. The phone wont let you downgrade your radio unless you have NAND unlocked and S-off. The only way to get the 2.15 radio i think is to have S-off. Hope this helps
Click to expand...
Click to collapse
It actually doesn't work because the zip isn't signed with the correct signatures, so HBOOT won't flash it.

[Q] Unrooted: Why still S-OFF?

I just unrooted my phone by running the RUU update for 3.29.xxx and at bootloader screen, it is still showing S-OFF. Shouldn't it be S-ON? I'd appreciate some feedback as I am heading back to the sprint store and want to be sure the phone is completely unrooted. I recall the other time I ran this same procedure, it went back to S-ON.
TIA

You need to flash the Unrevoked s-on tool. It can be found in several unrooting threads.
Sent from my PC36100 using XDA App

TheMagicalSock said:
You need to flash the Unrevoked s-on tool. It can be found in several unrooting threads.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks. I suspect it was the tool I used to root that had the Unrevoked component (never had this problem first time around); should've read the fine print...
Sent from my PC36100 using XDA App

so you need to re-root (maybe with unrevoked even) and then flash the s-on tool through recovery. it can be found in the unrevoked wiki. after that, then run the ruu.

dkdude36 said:
so you need to re-root (maybe with unrevoked even) and then flash the s-on tool through recovery. it can be found in the unrevoked wiki. after that, then run the ruu.
Click to expand...
Click to collapse
Yup.... exactly. Thanks.....highly appreciated. I guess this explains why most prefer not to use the Unrevoked method.
Sent from my PC36100 using XDA App

glad i could help. another reason people dont like unrevoked is it is now outdated. if you run it with the new protected hboot 2.02, you will get screwed pretty bad.
it used to save people hours of struggle, now it kills ruthlessly (haha)

Just flash this as PC36IMG.zip:
http://goo-inside.me/evo/stock/RUU_...0.09.01_NV_1.77_003_release_154209_signed.zip

drmacinyasha said:
Just flash this as PC36IMG.zip:
http://goo-inside.me/evo/stock/RUU_...0.09.01_NV_1.77_003_release_154209_signed.zip
Click to expand...
Click to collapse
Does this downgrade HBOOT to .76.2000? If not, please list the exact steps + files to use. I have copies of Hboot_0.76.2000.zip and Hboot_2.02.0001-Patch but not sure of the other in which to flash them.
Thanks.
EDIT: I was able to get back S-ON, although I observed that bootloader doesn't show the updated value after flashing the unrevoked-s-on zip; not until you attempt to flash the stock PC36IMG file. The above RUU allowed me complete the unrooting process (now with hboot 2.02).
I guess the other pressing question is why do I need hboot 2.02 and not .93 or .76.2000?

Unroot Help!

I just tried to unroot my htc evo. Initially I has S-OFF, so I applied the S-ON patch, this changed me to S-ON. I then tried to flash PC36IMG.zip from and I was getting Main version is older. It looks like I am running hboot 0.93.0000. Any help is appreciated.

http://forum.xda-developers.com/showthread.php?t=780141
Which pc36img.zip did you download, from this link?
Sent from my PC36100 using Tapatalk

I downloaded the one in the thread. I was doing some searching and maybe this has to do with my hboot version? I was able to restore a nandroid backup, so I'm back at CM7, but I need to unroot so I can get the lcd on my phone fixed.

My buddy just unrooted his evo as well for the same issue, we just compared the radio and hboot version. Both are running hboot 0.93.0000, the difference is on the radio versions, mine is 2.15.00.11.19 his is 2.15.00.07.28. So is the "Main Version in older" error happening because of the radio version?

joshmeyer31 said:
I downloaded the one in the thread. I was doing some searching and maybe this has to do with my hboot version? I was able to restore a nandroid backup, so I'm back at CM7, but I need to unroot so I can get the lcd on my phone fixed.
Click to expand...
Click to collapse
If you want to completely unroot just flash the s-on then run the ruu exe file. Make sure you have htc sync installed. It might be easier this way. Try running it in bootloader in fastboot mode. Just a suggestion......
http://goo-inside.me/supersonic/sto...0.09.01_NV_1.77_CNV_release_150224_signed.exe
Sent from my PC36100 using Tapatalk

So when you say completely unroot, will that cause me any issues on rooting again? I will want to root again once I get my phone fixed.

joshmeyer31 said:
So when you say completely unroot, will that cause me any issues on rooting again? I will want to root again once I get my phone fixed.
Click to expand...
Click to collapse
If you unroot you WILL be able to root again as long as you don't accept the OTA GB update. Accepting the ota will leave without root for good.....at least until a new method is achieved.
Sent from my PC36100 using Tapatalk

My current image version is 3.70.651.1 and this updater is for 3.29.651.5, i ran it and it doesn't let me go backwards.

Just run the 3.70 ruu.
Sent from my PC36100 using XDA Premium App

joshmeyer31 said:
My buddy just unrooted his evo as well for the same issue, we just compared the radio and hboot version. Both are running hboot 0.93.0000, the difference is on the radio versions, mine is 2.15.00.11.19 his is 2.15.00.07.28. So is the "Main Version in older" error happening because of the radio version?
Click to expand...
Click to collapse
I'm sure by now you have found out that yes, the radio version does make a difference, downgrade your radio to get the son.

the 3.70 ruu did the trick, thanks for the help guys

[Q] Just took the ota update. Is it too late to root my One?

I updated to Kit Kat this morning. What are the necessary steps for me to gain root? I haven't rooted a phone since my Droid X, so I might be out of the loop on some things. Thanks for any help!!!

So why would you take the update before asking this
Sent from my HTC One VZW using Tapatalk 4

You can still root it. If you go into RUU mode, flash one of the older system RUU's, then get s-off before updating. You pretty much gave yourself a **** ton more steps to do it, but yes, you can.
This link has the info to flash back to an older version - http://forum.xda-developers.com/showthread.php?t=2475216&highlight=s-on
You won't need the s-on / lock part of that, but you will probably need to flash one of those old system images, then use rumrunner to get s-off and unlocked, then you can update to 4.4, then flash a recovery.

Use firewater-soff.com. Use the temp root method.
Sent from my HTC6500LVW using Tapatalk

ccarr313 said:
You can still root it. If you go into RUU mode, flash one of the older system RUU's, then get s-off before updating. You pretty much gave yourself a **** ton more steps to do it, but yes, you can.
This link has the info to flash back to an older version - http://forum.xda-developers.com/showthread.php?t=2475216&highlight=s-on
You won't need the s-on / lock part of that, but you will probably need to flash one of those old system images, then use rumrunner to get s-off and unlocked, then you can update to 4.4, then flash a recovery.
Click to expand...
Click to collapse
If you are s-on hboot will not allow you to flash an older ruu version than you are currently on (downgrade). So that wont work. But as stated in the post above firewater will get you bootloader unlocked and s-off.

cmlusco said:
If you are s-on hboot will not allow you to flash an older ruu version than you are currently on (downgrade). So that wont work. But as stated in the post above firewater will get you bootloader unlocked and s-off.
Click to expand...
Click to collapse
You are totally right, forgot about that feature. Goodluck with firewater. lol
Glad i s-offed and unlocked on original 4.3 lol

I rooted my One yesterday and installed some custom roms...
It was updated to the newest version, so it is possible to root it... easy ^^

disconnecktie said:
Use firewater-soff.com. Use the temp root method.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So Firewater can achieve S-off with completely stock kit kat? I ask because I just sent my One to be repaired (4.3 S-off) but I have this feeling HTC will update me and possibly return me to S-on.

lancasterv3 said:
So Firewater can achieve S-off with completely stock kit kat? I ask because I just sent my One to be repaired (4.3 S-off) but I have this feeling HTC will update me and possibly return me to S-on.
Click to expand...
Click to collapse
It is supposed to work for the newer versions. The worst case scenario is that it won't work.
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
It is supposed to work for the newer versions. The worst case scenario is that it won't work.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Thanks, from what I have read in the S-Off thread the temp. root has in fact been blocked so I do not think this will work unless I am reading it wrong.

lancasterv3 said:
Thanks, from what I have read in the S-Off thread the temp. root has in fact been blocked so I do not think this will work unless I am reading it wrong.
Click to expand...
Click to collapse
Yeah I must have missed that. Lots of off topic stuff in there right now. That sucks. Hopefully I don't have to ever send my phone off for repair.
Sent from my HTC6500LVW using Tapatalk