• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Details on Installing Nov OTA to Rooted Incredible

Its been forever since I've had to understand file allocation stuff, but once I get clockwork installed from my Fat32 SD card, do I revert it back to what it was before or does the phone not care what formatting its in?

I guess Im asking if I keep it fat32 will I see any downsides?
 
Just as a general FYI, I have run into the phone not seeing or installing files because the card needed to be reformatted to FAT32.

This has resolved the issue every time.

Yes, you can leave it that way.
 
I know ppl said it could be done on a Mac but I have been having some trouble.

Can anyone who did it on a Mac make a step by step guide??? (for noobs)

thanks!!!
 
What kind of trouble are you having, JSS12? I found Bob's guide quite easy to follow and I would classify myself as rather new to the whole Android rooting business. The major difference as I stated before was getting into the adb shell under Mac OS X. I didn't need to as I just used Root Explorer to move any old programs back to their respective places.

As I followed Bob's guide when I originally rooted, my 2 GB MicroSD was already formatted to FAT 32. I remember I had to do this under my Windows Bootcamp install as Disk Utility wasn't helping me. Anyway, good luck.
 
+1 Root Explorer. Well worth the money. I've used it on multiple occasions in place of adb shell commands. :)
 
I have rooted, did not delete the crapware, only added Titanium Backup, Wireless Teather for Root, AdFree Android, drocap2 for root users, Quick Boot and Autostarts. I don't have Tasker, System Monitor, AutoMemoryManager, SetCPU or Widget Locker. I know I can skip step 2 and probably step 1.

Main question is how does this file work when the OTA did not work with my setup? I have read and re-read the instructions and trying to figure out how this works when the OTA does not work even though it is the same file? I can see where the RUU update would work but still trying to figure this one out.

I will probably install this update starting at step 3 and have already downloaded the 3 files needed.

Thanks for clear instructions.
 
mshepp said:
I have rooted, did not delete the crapware, only added Titanium Backup, Wireless Teather for Root, AdFree Android, drocap2 for root users, Quick Boot and Autostarts. I don't have Tasker, System Monitor, AutoMemoryManager, SetCPU or Widget Locker. I know I can skip step 2 and probably step 1.

Main question is how does this file work when the OTA did not work with my setup? I have read and re-read the instructions and trying to figure out how this works when the OTA does not work even though it is the same file? I can see where the RUU update would work but still trying to figure this one out.

I will probably install this update starting at step 3 and have already downloaded the 3 files needed.

Thanks for clear instructions.
Click to expand...

The OTA does some file and setting checks that fail if you are rooted. If you read this, it has you bypass that by doing it manually.

Trust me, it works. I've done it on about 25 phones now.
 
Anyone else getting stop errors since doing this? I removed the bloatware listed in the guide (not all of it, just the ones I did not want or use) and I got a stop error that Skype force closed. I had removed that. After realizing that there was a part of it still in the phone (an update that I uninstalled from inside market). Now, I get The process android.process.acore has stopped unexpectedly. When I get a text message.
 
mshepp said:
I have rooted, did not delete the crapware, only added Titanium Backup, Wireless Teather for Root, AdFree Android, drocap2 for root users, Quick Boot and Autostarts. I don't have Tasker, System Monitor, AutoMemoryManager, SetCPU or Widget Locker. I know I can skip step 2 and probably step 1.

Main question is how does this file work when the OTA did not work with my setup? I have read and re-read the instructions and trying to figure out how this works when the OTA does not work even though it is the same file? I can see where the RUU update would work but still trying to figure this one out.

I will probably install this update starting at step 3 and have already downloaded the 3 files needed.

Thanks for clear instructions.
Click to expand...

The OTA cannot account for your phone using the clockworkmod recovery, which is why in this process you use clockwork to apply the update.zip.
 
feelfreetoblameme said:
What kind of trouble are you having, JSS12? I found Bob's guide quite easy to follow and I would classify myself as rather new to the whole Android rooting business. The major difference as I stated before was getting into the adb shell under Mac OS X. I didn't need to as I just used Root Explorer to move any old programs back to their respective places.
Click to expand...

How does one do this???

THANKS!
 
Step 2i says "move the stuff". What do I move and where??

EDIT: Nevermind, I am an idiot. This was only if I removed the crapware, which I didn't so I'm good to go. Too much beer tonight. lol
 
Thank you so much for the directions, now my phone will stop nagging me. Now, I have to take care of my girlfriend's

Couple notes, I didn't end up with the double icon issue and I had to use a microSD formatted to FAT32 in order for the PB31IMG.ZIP update to apply.
 
Will there be a more simple way to do this after the update has been out for awhile?

Really dont feel like getting back "in" the phone. Consider myself fortunate for not bricking it the first time!
 
Worked perfectly! Thanks!

Wasn't as hard as it looked, well worth it to get the update and get rid of the annoying update notification.

I did have to format my SD card to FAT32, may want to mention that in the instructions, because I panicked a bit before checking the thread for the solution!

Thanks,
Jim
 
PLEASE HELP ME! Have unrooted my DInc and superuser permission is gone. But S/Off is still set. How in the world do I get my S/Off set so that I can get the latest Verizon OTA? It never reboots when it says it is going to. Will doing a factory reset set the S/Off to S/On? I do not want to reroot my phone at this point. Clockwork recovery is gone from my phone and I never deleted any of the bloatware. Can I just rename the manual OTA file to Update.zip and then HBoot and let it install the OTA?
 
Well nevermind. I downloaded the manual OTA from the following link:
00cb7fa66e35.OTA_IncredibleC_Verizon_WWE_3.26.605.1_3.21.605.1_release_sign.zip I then moved to a FAT32 SD card to the root directory and renamed it update (note it is already a compressed file so don't rename it update.zip or it will be update.zip.zip). I then booted the phone into HBOOT (Power button and Vol Down). The update started automatically, and I waited about 5-7 minutes and it was done. After it automatically rebooted, it said congratulations, new update was successful.

My phone was back to stock 2.2, no bloatware had been deleted however, the S/Off was still in play. So far so good.
 
You must log in or register to reply here.
Back
Top Bottom