yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] wildstang83:
Warning! There is a huge risk that you will permanently loose root with no way to regain root. Do not flash s-on before you flash this RUU. You will permanently loose root if you do!!!

Incredible_C_GB_S_VERIZON_WWE_4.06.605.2_Radio_2.1 5.10.07.07_NV.zip - 180.6 MB

MD5 Sum:	096d841530dd2f223ef4a1b701c7d429​

Install Instructions:

•Rename the file to PB31IMG.zip

•Drop it on the root of the SD Card

•Boot into the bootloader

•Flash as usual

Next go here* to learn how to get root back. Your phone must still be s-off in order to regain full root.

*Sorry guys link is down. I'll add in the instructions here tomorrow.

Want to contact unrEVOked on IRC about the root situation and how you can help?​

You can speak to the unrEVOked team live.

Go to: unrEVOked IRC

IRC Instructions:

1. Type in a nickname into the nickname box. This is your name that will be displayed during the chat.

2. Type in the captcha.

3. Press connect.

Once connected the page will load and give some brief info. The page will fully load and you will notice a list of usernames on the right. These are all the people currently in the IRC chat. You will also notice a text box at the very bottom of the page. Just type what you want to ask or say there and press [enter] on your keyboard to send your message. Just wait after you send your message. Someone will soon reply. The IRC is similar to an instant messenger, its just web based.

Hopefully this will help some of you to know where to go to get the info you need for this issue.
[Droid Incredible Android Development] k.electron:
now someone pull the radio from this and post it.
[Droid Incredible Android Development] thekidkid32:
http://xdaforums.com/showthread.php?t=1227215
[Droid Incredible Android Development] tiny4579:
So I pulled the RUU today, extracted system.img via yaffsexpert app from the market. Transferred to my PC for inspection. build.prop is exactly the same as the other leak using diff. I don't see any significant difference but we'll wait to hear from one of the official devs if there is a difference.
[Droid Incredible Android Development] tiny4579:
Also, the boot.img from the RUU broke adb for me. Maybe I have to do something special with it.
[Droid Incredible Android Development] evilstewie23:
So everybody who did this is unrooted now or what
[Droid Incredible Android Development] jermaine151:
Ignore: I'm goofy and flashed the old zip instead of the new. :)
[Droid Incredible Android Development] tiny4579:
If you flashed the zip file in the OP then it will return you to stock recovery and you will be unrooted yes. I don't know about S-OFF though, I'm not sure if it reverts it. It will install the bootloader but I thought S-OFF was deeper in the system than that. Maybe someone who installed this can tell us. If you're still S-OFF you should be able to flash a custom recovery. It will say S-ON or S-OFF at the top of the bootloader.
[Droid Incredible Android Development] wildstang83:
Check the build.prop for sdk level and make sure your sdk is updated to what is required by this rom. Your Android drivers may be out of date? I'm just talking to hear myself talk, but it sounds good enough to check our bases here.

Yes if you flash this as is you are now unrooted.
[Droid Incredible Android Development] davwman:
I got the nag on first boot but havent after that
[Droid Incredible Android Development] evilstewie23:
K thanks guess ill just wait to get this when I unroot for the official ota as soon as it cones out and someone discovers another rooting method for 2.3
[Droid Incredible Android Development] jermaine151:
I rebooted a few times and got it every time. Hmm... I wonder if it's just me. I think I've figured out how to stop it though. Testing to make sure.

EDIT: LOL! I may have flashed the original one I had. Let me double check.

I'm pretty sure I flashed the original instead of the new. I had them named to close to the same. Sorry. :D
[Droid Incredible Android Development] tiny4579:
I actually compared the build.prop in this to the build.prop in the rooted zip released earlier this week using diff and they're identical. It was the first thing I did as soon as I extracted the system.img from the RUU.

When I reverted to the earlier boot.img from the rooted zip or the boot.img from the leak a few months ago I got adb back. I don't think it's a change to the kernel but I bet they modified the ramdisk to disable adb.

Yep, confirmed it was disabled in the ramdisk. If you want/need adb access don't use the boot.img from the RUU today.
[Droid Incredible Android Development] jermaine151:
+1 just tried it and ADB is disabled.
[Droid Incredible Android Development] tiny4579:
Do you know how to edit and repack boot.img files?

If so all you have to do is to unpack and change default.prop to this:

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1

Try attached. It should work with adb and I believe have module compatibility with my OTA modules zip.
[Droid Incredible Android Development] jermaine151:
Okay, after enough reboots I can say the following about the location nag:

1) If "Standalone GPS" is enabled, you get the nag on every reboot. If you disable that, you don't.

2) If "Fast Boot" is enabled and you power down, then boot up, you won't get it. Reboot doesn't use "Fast Boot" so you get the nag after every reboot. I guess we'll have to hack it to get rid of that.

3) If "Fast Boot" is disabled and you power down, then boot up, you get nagged.

I still see no reason why they delayed the OTA since nothing seems to be changed.
[Droid Incredible Android Development] wildstang83:
Hmm, thats nice to know. I wonder if you guys remembered to go check the adb check box? If so and it isn't working and is disabled how hard it would be to enable it.
[Droid Incredible Android Development] wildstang83:
Maybe because of the wifi issue. Has anybody checked to see if we have wifi back now?
[Droid Incredible Android Development] jermaine151:
Yep, that's with USB debugging enabled.
[Droid Incredible Android Development] wildstang83:
Are you saying you got adb to be enabled?
[Droid Incredible Android Development] jermaine151:
Only time I've heard of a wifi issue was with NilsP using the new OTA kernel with sense 2.1/3.0 rom. WiFi works fine on stock leaks.
[Droid Incredible Android Development] tiny4579:
Confirmed that above fixed adb for me however wifi is still broken on Nil's rom with this kernel so I'll have to revert back to the boot.img from the April leak.
[Droid Incredible Android Development] zoomy942:
So build.prop still isn't right? Not sure about this gb update.
[Droid Incredible Android Development] tiny4579:
build.prop still has sprint stuff in it.
[Droid Incredible Android Development] wildstang83:
Never mind
[Droid Incredible Android Development] zoomy942:
How can an official have something so obviously broken?
[Droid Incredible Android Development] tiny4579:
I don't know but maybe it's not official after all.
[Droid Incredible Android Development] wildstang83:
Well because Sprint has a larger HTC userbase than VZW. So everything is generic by the Sprint standards.
[Droid Incredible Android Development] wildstang83:
Honestly I'll consider it official when it downloads to my phone and installs itself.
[Droid Incredible Android Development] wildstang83:
Yes please run that again, lol. I'm interested to see whats up here.

We got to keep in mind that Android Police did get this from a supposed official 'leaker'. So theres no telling 'if' anythings been touched or not....
[Droid Incredible Android Development] zoomy942:
Agreed my friend. I'll stick to froyo and just enjoy the show.
[Droid Incredible Android Development] dmeadows013:
Wait, so the ROM we got wasn't based off this? And someone will have to convert it? Or that was the ROM based off of the official RUU and not a leak...
[Droid Incredible Android Development] zoomy942:
Thats what we are all trying to figure out
[Droid Incredible Android Development] jermaine151:
Okay Everyone. Here's the deal:

I diff'd both leaks (8/16 and Today's). The ONLY difference between the 2 is the boot.img. I extracted both boot.img's, diff'd them and the ONLY difference between those is the default.prop file. I diff'd those and the ONLY difference is this:

root@bt:~/temp# diff old_boot/boot.img-ramdisk/default.prop new_boot/boot.img-ramdisk/default.prop

4c4

< ro.secure=0

---

> ro.secure=1

6,7c6,7

< ro.debuggable=1

< persist.service.adb.enable=1

---

> ro.debuggable=0

> persist.service.adb.enable=0

In layman's terms, Today's leak is identical to what we already had, except for disabling ADB. :( I'd be surprised if this is pushed to anyone's phone. I wonder if I should create a thread stating this to save all of the excitement and drama?
[Droid Incredible Android Development] cmlusco:
It is possible to root this as long as your s-off. What i did was take the ruu replace stock recovery with cw flashed and then flashed su from recovery. Now i am rooted again.
[Droid Incredible Android Development] cmlusco:
My adb works just fine.
[Droid Incredible Android Development] tincbtrar:
So, in other words, this RUU is the base of the leak that was produced earlier in the week?

Didnt we know this already? lol.

Im assuming you are questioning integrity then of the RUU.

Im confused...
[Droid Incredible Android Development] cmlusco:
They are the same except now we get the radio too.
[Droid Incredible Android Development] wildstang83:
Exactly. I have a feeling that the leaker that gave this to android police is the same leaker that gave it to joel and incubas. And i do not believe that this is the official ota that we are supposed to be recieving. Why? Because, this still has a faulty wifi module. Since the leaker knows there is a new ota coming, he chose to just go ahead and release the whole ruu because its not worth holding the radio anymore for whatever reason he was holding. Does that make since?

Basically this is "A" complete ruu But I don't think this is the 'actual' new ruu thats coming. The new patched ruu is still likely being worked on and will be released at a later date.

Makes since to me but again I'm just thinking out loud on a forum.
[Droid Incredible Android Development] renzo.olivares:
Well WiFi works but only on the inc gb ota Rom it doesn't work with custom roms which isn't what Verizon is aiming for they just want it to work with their official.software....ill download this try and compare with the ruu I recieved
[Droid Incredible Android Development] jermaine151:
I compared them Joel. They're identical besides 2 lines in default.prop
[Droid Incredible Android Development] renzo.olivares:
Ahh alright but yea its not a faulty WiFi module or anything everything works on the official software but they've messed with the RAM disk so that breaks WiFi for custom roms
[Droid Incredible Android Development] wildstang83:
Ok but I'll help you out this is the same 'official leak' you got the other day. Why? Because this RUU also has a deodexed system/app folder. Whats that meen? Well what we have here ladies and gentlemen is NOT the new leak of the official RUU.

I win.
[Droid Incredible Android Development] tiny4579:
Wifi does work on other custom ROMS with the OTA kernel. I made a post on Nil's Sense 3 ROM page that I got it working by flashing via the anykernel updater vs the ROM flash method of using boot.img. Just extract the boot.img from the OTA leak's kernel and copy zImage to the kernel section of the zip and grab the bcm4329.ko from the OTA and place in /system/lib/modules.
[Droid Incredible Android Development] douger1957:
I'm not a dev but I'll confirm that...my wifi works better now than it has in a long time.

I'm running jermaine's debloated gb rom with the new radio.
[Droid Incredible Android Development] wildstang83:
Oh niiiccce
[Droid Incredible Android Development] renzo.olivares:
What I leaked is the official ROM....I also have the official ruu ha I win
[Droid Incredible Android Development] wildstang83:
Lol but if its the same one in the OP...mmm...no its not.
[Droid Incredible Android Development] renzo.olivares:
Yea it is the one in there is official to
[Droid Incredible Android Development] NilsP:
I can confirm that what he did works. I did the same thing with good results (just to prove to myself I could do it) and now have the new kernel running in my next release.

Anyone want to compare it and see if I screwed it up even though it works.

Here is the patched boot.img and module for inclusion in ROM's.
[Droid Incredible Android Development] omniatic:
I flashed Tiny's patch. New kernel, faster phone, works for me.
[Droid Incredible Android Development] eraste:
So this [RUU] is multi device functional? I have the older Amoled inc not the SLCD.... if someone wanted to unroot they could run the security on tool then flash this .zip on the op and be back completely stock unrooted on 2.3.4 right instead of flashing the 2.2 [RUU] or downgrading back to 2.1?
[Droid Incredible Android Development] wildstang83:
Yes this will work on both screen types. You will loose root but your phone will remain s-off as tested here: http://xdaforums.com/showthread.php?t=1227791

Just follow kzoodroid's instructions. You'll be fine.
[Droid Incredible Android Development] wildstang83:
Hey guys I updated the OP with better up to date info
[Droid Incredible Android Development] eraste:
Cool but if someone wanted to or had to take phone in to Verizon, run security on, then flashing this will result in permanent unroot since I don't think there is a root method for this release yet right?
[Droid Incredible Android Development] wildstang83:
Well thats not either true or false. It's simply uncharted territory. If somebody was brave enough to attempt this and find out then we could give a more definitive answer. For now we all just hope team unrEVOked can hook us up with a new root method if it is in fact needed.

I guess that was the long way to say 'I don't know....';)
[Droid Incredible Android Development] eraste:
Me either an not brave enough to try until we get a root method just incase it would unroot permanently after running the s-on tool then flashing the RUU. seems that it would since you would be turning security on and then flashing an official update. To scary to try lol.
[Droid Incredible Android Development] DustinBooyah:
I figured the same thing... As I was using it I was impressed but I kept thinking "no sh*t its fast, its 1.0 Gingerbread". But my gf's phone, which is bone stock, works flawlessly every single time you ask it to do something. This leak had some rom-ish bugs, like it would resize for a split second when I left an app in landscape mode, etc. When I found out it was de-Sprinted I just said f this noise and got back to Warm Synergy. As mentioned earlier I think its worth it to save the headache and run your favorite ROM till peoples' phones download and update themselves.
[Droid Incredible Android Development] evilstewie23:
exactly what u said
[Droid Incredible Android Development] wildstang83:
Yea bud you pretty much nailed it right there. Plus anybody that knows anything can look at this and see its not 'official'. Just look at the system/app folder...its freaking deodexed!!! We all know that htc is not shipping deodexed roms right?

My point is this: Its officialish' but thats as far as it goes. Its simply not the real deal and I feel like the actually real ruu/ota is still on its way. But who am I to know? I've been wrong more than once in my life.
[Droid Incredible Android Development] xwera43:
Wouldn't it be more than that if there's a new radio file or are you one of the few that got the radio on the d/l?

X
[Droid Incredible Android Development] wildstang83:
Yea I think he was just diffing the rom without the radio since in the first leak we didn't have the radio.
[Droid Incredible Android Development] renzo.olivares:
same radio
[Droid Incredible Android Development] dkris2020:
is it better to run this or to flash a rom based off of this?
[Droid Incredible Android Development] wildstang83:
Run a stock Rom based of this so you don't loose root.
[Droid Incredible Android Development] deadsoulboy:
Help!

So, I flashed the Leaked OTA, but I wanted to root again...

I somehow have S-ON now when I start up the BootLoader!

Cannot use reflashpackage.exe anymore, fails to root...

Someone posted a link to a flashable ClockworkMod recovery, which the bootloader does not recognize when I start Bootloader, even after renaming it to PB31IMG.zip

I've even tried to flash the old firmware PB31IMG.zip, but bootloader will not install a previous version..

Is there an updated unrevoked on the way? Another fix so I can get root again? Am I screwed?

Does someone have a solution?
[Droid Incredible Android Development] TheBr0ken:
there is a link on the OP as to how to get root back
[Droid Incredible Android Development] kzoodroid:
If you have s-on you cannot get root back till Unrevoked comes up with a new method and there is no guarantee they will. You can only re-root your phone if you have s-off.

How long ago did you root with unrevoked as the version that came out back in Decemeber (3.21) automatically gave s-off, older version didn't. Or did you try and unroot your phone recently and inadvertently change it back to s-on?
[Droid Incredible Android Development] deadsoulboy:
Gosh, I pretty much install new roms on my Inc almost weekly, up until now.

My last flash of Unrevoked was this morning, but thinking there may be a newer version of the .exe, I downloaded the current one from their site.

I fail to get root, and when I start the bootloader, I show that I now have s-on.

I'm really not sure how this happened. What I am doing now as I type this, is I am re-flashing the OTA leak again in hopes that It will restore s-off.

I'll keep you posted.
[Droid Incredible Android Development] kzoodroid:
When did you first root your phone and do you know the version of Unrevoked you used? The older versions of Unrevoked did not give you s-off you had to run a seperate program called Unrevoked Forever to get it. In December starting with version 3.21 it was an all in one process. I'm thinking that you may never have had s-off to begin with as the RUU has nothing in it to change it back to s-on. Or that you some how ran the s-on utility thats been floating around in the unroot forums.
[Droid Incredible Android Development] deadsoulboy:
Rooted day 1 when I got my phone last April...

I know I've had S-Off, bootloader has said so on the top line of the screen. The unrevoked version I've used (and always used) has been 3.32.

There is a .zip that restores s-on, which I've only flashed on the rare occasion I've unrooted my phone in the time I've had it.

What I deduce happened was, I came from a custom sense 3.0 ROM, flashed the s-on .zip, then flashed the leaked OTA .zip file. That's probably why I have, and am stuck with, s-on now.

damn it...
[Droid Incredible Android Development] cmlusco:
Ok i got a question? If you have s-on could you use a stock PB31IMG.zip with the stock recovery.img swaped for cw recovery to regain root or would it not install.
[Droid Incredible Android Development] deadsoulboy:
Negative, sir..

Bootloader will not let me flash a 2.2 Img. I get a warning that the firmware is old, and it just won't allow the option to flash.

I grabbed a zip with clockwork recovery on it, renamed it to PB31IMG.zip, but the bootloader won't even recognize it. Perhaps it's because the .zip is 2MB, and a standard IMG is around 200MB?

I always thought the file name just had to be correct, but this is a smart bootloader...
[Droid Incredible Android Development] deadsoulboy:
Wait, you mean... replace the stock recovery, with clockwork, then re-zip & flash?

Sounds worth a try. Worst case, I'll just re-flash a stock.

No chance this would brick the thing. Will try this and post an update. you sir, are a gentleman and a scholar.
[Droid Incredible Android Development] deadsoulboy:
No dice. Bootloader checks for the file, scans it, then drops my by the main bootloader menu.
[Droid Incredible Android Development] kzoodroid:
One thing I forgot is that eventually HTC will themselves unlock the bootloader but not sure when this will happen. http://htcdev.com/ As of today it is only live for the Sensation (EU) and Evo 3D but eventually they should add the Incredible but it will probably be a while as they will support the newest phones first.
[Droid Incredible Android Development] wildstang83:
Sorry to hear this happened to you guys. I guess for now theres no way back to root until unrEVOked gets to us or HTC puts the bootloader unlocker on their site.

Do to this experience I'm gonna now re-update my OP. Looks like I was right the first time when I said this would break root.
[Droid Incredible Android Development] deadsoulboy:
Thanks for everyone's advice.

Does unrevoked have a forum? Or do they report here?

Googled and couldn't find a proper link. Let me know.
[Droid Incredible Android Development] wildstang83:
Hey guys I'm currently on chat with some of the guys from unrevoked right now. Their reading through this thread to see whats going on. Hang tight.
[Droid Incredible Android Development] k_nivesout:
It sounds like he flashed the S-ON zip prior to the RUU, and that's where the problem lies. With S-OFF, you can always flash a custom recovery, but by flashing S-ON first, he permanently broke root. As long as you have S-OFF, it should be fine to flash this. Just don't flash the S-ON zip before the RUU (not sure why you would do this anyway).
[Droid Incredible Android Development] wildstang83:
Yup I agree. Thats also what the guys from unrEVOked said as well.