Develop Bugs

Not Working: Root Evo 4G

I've completed the steps on SimpleRoot OTA, along with spending several hours now online trying different walkthroughs. None of them are resulting in me having a rooted system. I installed ROM Manager and I still get error when trying to run privileged command.

I would flash back to factory, then use unrevoked 3
*This was posted from my Evo 4G*

Okay, before the question can be answered:
1) What version is your phone currently at: i.e. 1.47, 1.32?
2) Have you tried any other versions of rooting besides SimpleRoot for your phone?
PM me if your really stumped. I'm always willing to help out where I can.
~Jasecloud4

my software number is 1.17.651.1. The boot animation is the HTC logo and 'silently brilliant' (ironically it plays a really loud chime while writing this).
As far as methods I've tried:
Toast 1 and 2
Simple Root OTA 4-click
whitslack's method
jiqqaman's simpleroot 3-click

Start by determining your HBOOT version. Full root means you have NAND unlocked which allows you to do anything.
79.00 = locked
76.20 = unlocked
Reboot and upon start-up hold down the volume down and power buttons at the same time until the white screen appears. HBOOT version will be listed at the top in green letters I believe.
If you have 76.20 I would recommend going back to the Whitslack method and starting there. If it is 79.00 you have additional work to do.
I believe that version number is the pre-release version and I never had that one. It probably came from one of the different methods you tried. I was lucky enough to root prior to the OTA using Toast 1 & 2. Since your version seems "older", if you don't have HBOOT 76.20, you may be able to use the original toast 1 & 2 method.
Bottom line....once you get HBOOT 76.20....you are GOD

I have 76.20. I don't feel like a god =[
I discovered that i can in fact su to root in a terminal.
However, I'm trying to install Fresh ROM, and since I've not found any instructions on here on how to actually do that, I'm guessing it's with this ROM Manager app. When I run the first part of that app I get error when trying to run privileged command. This is what led me to believe I wasn't rooted.

I would suggest starting with the Whitslack method. I know you indicated that you tried it but I'm not sure of the order in which you did so. Its a piece of cake with the 76.20 HBOOT.
Whitslack gives you the best "starting" point for future ROM's and is in fact where I began before flashing Fresh 1.01.
I did NOT have to flash the Radio and WiMax updates included in the Fresh thread.
1. Whitslack
2. Install Clockwork (ROM Manager) and flash alternate Recovery (Amon RA)*
3. Wipe Data/Dalvick/Cache (Use Amon RA Recovery)
4. Flash Fresh 1.01
5. Setup
6. Configure Fresh Updater using instructions at the link in the Fresh 1.01 thread
* This step may be optional if you already have Amon RA installed as a recovery. It works better than clockwork during the wiping process and I recomend just sticking with it once you get it installed.

As far as I can tell whitslack's method doesn't work. I've tried it twice, to the T.
At step 15, instead of a menu I get a red triangle with an exclamation mark. That's it. Cannot continue.

n4th4nr1ch said:
As far as I can tell whitslack's method doesn't work. I've tried it twice, to the T.
At step 15, instead of a menu I get a red triangle with an exclamation mark. That's it. Cannot continue.
Click to expand...
Click to collapse
Honestly I have not reviewed the Whitslack thread for sometime now. When I did it it was 2 steps total and it worked. Apparently he has added new information for a select few people.
Did you receive that "Fail-PU" Error?
Do you know what recovery you are currently running?

I finally figured out that he has failed to mention you need to hold volume up and press power at this page apparently.
However the next step is 'Using the Volume and Power buttons as before, select "Flash zip from sdcard."'
There is no option for Flash zip from sdcard.
I see:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition

Have you seen this thread?
http://forum.xda-developers.com/showthread.php?t=717955&highlight=toast+part
Between this and the "Starting Over" thread your answers are there. Didn't realize that it had become more complicated than when I (luckily I guess) performed it.
Bottom line...like I said...having HBOOT 76.20 is the majority of the battle. Follow the flowchart in the thread I posted above and report back.

I finally got into Fresh. Thanks. Wish there was somewhere which clearly in plain english outlined the relationships between all these steps; would have made this a lot easier to get to, since all the walkthroughs seem to have trouble keeping up with each new change every version, or whatever.

EVO 2.2 UPDATE (Froyo), HELP !!!

Guys,
My Evo says Froyo 2.2 is avail for download when I check HTC Updates... I hit accept, it downloads, then asks if I want to install NOW... I HIT YES, and it takes me to the boot loader page, THEN DOES NOTHING.. It doesn't boot into recovery mode like it is supposed to, and it just sits on the Boot loader screen, NO TRIANGLE, NO BAR on the bottom showing the progress, IT JUST SITS THERE on the boot loader page with the 3 Androids on the bottom... I have already tried to hard reset the phone, BUT that didn't work... PLEASE HELP !!! Is there a way to HARD reset my EVO BACK to BEFORE ALL OF THE UPDATES??? IS THERE A WAY TO Force boot into recovery to apply the "update.zip" ??? Please advise...

Mine did'nt go no where near the bootloader screen...
I hit the download...then it just installed like any other app...except it brought me to a bar progress page a couple of times. Then the phone rebooted and whala...froyo.
I must say this...I was previosly rooted but unrooted to do it!!!
Are you rooted or unrooted to start off with?

Was rooted, but then I did the "update of June 29th" and ruined ALL of my fun... Is there even a way for me to root my phone now??? How do I get it to go into recovery?

Same issue
My EVO ISN'T ROOTED, and I'm having the same exact problem

You're hosed root wise until someone cracks the rom, if they crack the rom. Most likely you'll need to update to the official version once HTC releases an upgrade as they claimed they would eventually do on Twitter.

im not trying to root my phone, i just want froyo

right, I WAS rooted, the update in JUNE fixed that for me =(... NOW I just want FROYO which is available from Sprint/HTC OTA, it just wont install?????????? I think I can install it as an update.zip if I could get my phone into RECOVERY mode... When at the bootloader, if I hit Recovery, it just boots back to the BOOT LOADER????

I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
This is the route I took and was just like you...I had no probs this way!

This is a great recommendation, but I haven't done any ROOT or ROMing to my phone since I've owned it, I've stayed true to the true image they released, and I'm not comfortable downgrading it to some other image that wasn't on the phone. I attempted to do the instructions outlined and I was unable to get pas the stage of pushing the:
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
to the phone. It says USB error, and I have debugging mode enabled.

cardiox said:
I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
This is the route I took and was just like you...I had no probs this way!
Click to expand...
Click to collapse
I RE-Loaded this version, as the other "older" versions would not work (re-loaded, as this is what I already HAD on my phone)... It wiped the system, and ALL of my info/apps (make sure you back up) and then I was able to do the Froyo Update... YES !!!! Thanks...
http://shipped-roms.com/shipped/Sup...51.1_Radio_2.05.00.06.10_release_CL195459.exe

I did the same, thank you !

No prob...have fun!!!

Froyo Update Won't Install
To start off - I have never rooted my evo - my phone is running Android 2.1 update 1 supersonic - and I did not try to do the "pre-release" update put out by HTC. Since late last night, I have been trying to install Froyo through system updates (settings, system updates, htc software update). I am able to download the upgrade, which is about 80 MB, but for some reason the update will not install. When I click install now, my phone restarts in the bootloader. If I click on fastboot, it searches for an image on my SD card but can't find one. If I hit recovery, it just returns me to the main bootloader screen. The only thing I can do is reboot or shut down my phone. When my phone boots back up, it says the update is downloaded and ready to be installed. I have tried redownloading the update but the same thing happens. Any help would be appreciated, preferable without losing contacts and apps. I'm trying to save a factory reset for a last resort.
Thanks,
Nick

Nick,
Please read the earlier posts, and follow the link from Cardiox... He said the following...
"I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-...urn-stock.html
This is the route I took and was just like you...I had no probs this way!"
Then read my posts, and you will see that I had the SAME problem you are having, and this worked for me... I posted the thread... It is pretty easy if you follow the instructions... Let me know if it works for you... Good luck !!!

wolverinexc said:
To start off - I have never rooted my evo - my phone is running Android 2.1 update 1 supersonic - and I did not try to do the "pre-release" update put out by HTC. Since late last night, I have been trying to install Froyo through system updates (settings, system updates, htc software update). I am able to download the upgrade, which is about 80 MB, but for some reason the update will not install. When I click install now, my phone restarts in the bootloader. If I click on fastboot, it searches for an image on my SD card but can't find one. If I hit recovery, it just returns me to the main bootloader screen. The only thing I can do is reboot or shut down my phone. When my phone boots back up, it says the update is downloaded and ready to be installed. I have tried redownloading the update but the same thing happens. Any help would be appreciated, preferable without losing contacts and apps. I'm trying to save a factory reset for a last resort.
Thanks,
Nick
Click to expand...
Click to collapse
I am not a genius by no means thus I am only sharing info that I have from personal trial and error. If you are going to a bootloader screen during this update process and your SD card is mounted then you most likely will need to bite the bullet and either do a factory reset or follow the link instructions so given. For some reason this update can not find the original factory code or RUU that it is trying to update. Sounds like your SD card is mounted but it can't find it...I would strongly consider just starting over with that link program. It does not root you it just puts you back square one with factory code. Then the update will have something to build off of...which you apparently don't have for whatever reason.

Ok, this is what I needed to know. I'm backing up my stuff with bitpim and will just do this. Thanks for all the help and the speedy responses!
-Nick

[Q] Need some direction...

Hey guys. I'm pretty tech savy when it comes to computers and all, but for some reason all this "root", "radio", etc. is all mish mosh to me. I'm pretty sure I have my phone rooted (followed a tutorial). I just got the prompt for froyo from Verizon, and I read somewhere i shouldn't install it from Verizon if my phone was rooted. What I want is to just reset my phone without the root, and be able to install 2.2 just as if I never rooted my phone, because I know I'm going to screw something up that's going to end up costing me. So any help??

you sound like me a few months ago
The OTA will update your OS to 2.2 and will update your radio along with alot of other things.
If you hold optical button and power at the same time (after the phone is off) it will boot to the Hboot screen. on the top of that screen you will see S-ON. This is the security toggle for the phone. I cant tell you what or why it does what it does. but it essentially makes its so you cant flash custom roms without rooting. Before you update your phone to the OTA, you want to google "unrevoked3" . download it, and run it. This will give you the Clock Work Recovery which will load instead of the phones built in recovery console. as soon as you do that, then you run "unrevoked forever" this will set the phone to S-OFF.
once you get S-OFF. Revert your phone back to stock by updating with a stock pb31gm.zip (you should be able to find that all over). this will make your phone stock again (by removing the root you did to it by running unrevoked3) but keep the S-oFF setting.
so by the end of the process you will be totally stock, no root, and have S-OFF. then boot up, install OTA, and then load the update with clock work recovery and you will be all set.
its all kinda confusing if you dont read along the forums. but once you get it, its pretty simple.
Another poster in another thread already addressed this. here it is in simplistic form
use google to look up anything you dont understand.
Assuming you have a truly stock Incredible (meaning you didn't force any third party roms or leaked radios), then you follow this order:
1. Unrevoked Flash/Recovery - Adds Clockwork Mod and Superuser permissions to your phone
2. Unrevoked Forever - Adds S-OFF functionality, which means that the HBOOT startup will no longer check for updates that are signed with HTC's super secret signature... Meaning you can flash anything to the phone.
3. Flash Original Stock Recovery - Removes the Clockwork Mod recovery console. Since you have S-OFF, you can return CWM to the phone whenever you damn well please. The original stock recovery is necessary for the OTA to commence, because it is developed to rely on the stock recovery console.
4. Wait for OTA
5. Upon receiving OTA, flash Clockwork Mod to the phone via HBOOT (using a PB31IMG.zip containing it)
6. Flash the root payload via Clockword Mod recovery console.
7. Go to bed and make love to your wife after beating on your chest in victory like tarzan.
8. Reboot phone, bask in Official Froyo coupled with Superuser permissions.
9. Download the busybox installer from the market and install busybox to the system.
10. Make love to your wife again.

Keyboards said:
Hey guys. I'm pretty tech savy when it comes to computers and all, but for some reason all this "root", "radio", etc. is all mish mosh to me. I'm pretty sure I have my phone rooted (followed a tutorial). I just got the prompt for froyo from Verizon, and I read somewhere i shouldn't install it from Verizon if my phone was rooted. What I want is to just reset my phone without the root, and be able to install 2.2 just as if I never rooted my phone, because I know I'm going to screw something up that's going to end up costing me. So any help??
Click to expand...
Click to collapse
I didnt read your post all the way before i responded... sorry
since you are rooted already, just get unrevoked forever to get S-off.
your rooted and you got the OTA , so that answers some questions for people right there, there has been much confusion about rooted phones will get the update. I guess you did
People say not to update because it will remove your root and not allow you to re-root. By flashing S-OFF you can re-root anytime you please because the phones security check is off.
The problem is, you need root to get S-off. If you flash first, with S-ON you wont be able to re-root to get S-off, make sense? lol. At this point in the game you can only get S-off while using 2.1. if you got to 2.2 with s-on your stuck for a while with no root.
If that doesnt matter to you, then dont worry about it

If you only rooted your phone and did nothing else, you can safely apply the update. Doing so will remove root.
If you installed a custom recovery you will wanted to install the stock recovery before doing the upgrade.
If you plan on keeping root you will need to install unrevoked forever to enable security off (S-OFF) before starting the upgrade process.
Hope that helps a little anyway.

I never did anything to the phone after the root. The only thing that changed on the phone was superuser was put on my app screen, and I don't even know what that does. I don't care for root that much anymore, it sounded cool, but I'm not the kind of person who knows how to use it to it's full potential. So all I have to do is hit install now on the 2.2 from Verizon and I should be good to go?

Keyboards said:
I never did anything to the phone after the root. The only thing that changed on the phone was superuser was put on my app screen, and I don't even know what that does. I don't care for root that much anymore, it sounded cool, but I'm not the kind of person who knows how to use it to it's full potential. So all I have to do is hit install now on the 2.2 from Verizon and I should be good to go?
Click to expand...
Click to collapse
well you will have to run a stock pb31img.zip to remove the clockwork recovery , or the update will fail
lemme look around and see if i can find you a stock image. 1 sec
here it is
http://d01.megashares.com/index.php?d01=CHoQD3B
once you get it downloaded, you need to rename it to PB31IMG.zip, place it on the root of your SD card (meaning dump it on the sd card , not in a folder on the SD card)
hold optical button and power button until you get the hboot screen
with "bootloader" selected hit the power button to select it
the phone will look for the PB31IMG.zip file and load it. wait a few min and when it asks you to reboot, say yes. It may or may not ask you to update again , if it does, say yes, if not let it reboot the phone.
once that is done, run the OTA update you got and your all set.
doing this will retain your stock image, and remove root. THIS WILL WIPE YOUR PHONE. so if you have anything you wanna save do it before you proceed

msticlaru said:
doing this will retain your stock image, and remove root. THIS WILL WIPE YOUR PHONE. so if you have anything you wanna save do it before you proceed
Click to expand...
Click to collapse
Thank you. Will my Market history remain?? Meaning if I bought an app, I can just redownload it??

Keyboards said:
Thank you. Will my Market history remain?? Meaning if I bought an app, I can just redownload it??
Click to expand...
Click to collapse
yup, anything you bought is saved to your google account. you just open the market, hit menu, and then hit "downloaded" and its all there

msticlaru said:
yup, anything you bought is saved to your google account. you just open the market, hit menu, and then hit "downloaded" and its all there
Click to expand...
Click to collapse
That's great, thanks again. I'm going to give it a shot now.

Keyboards said:
That's great, thanks again. I'm going to give it a shot now.
Click to expand...
Click to collapse
Ok I did it and it looks like it's going smooth! One thing I noticed is that after I formatted my card to FAT32, it said my capacity was only 200MB? Is this normal?
It's a 16GB card.

Keyboards said:
Ok I did it and it looks like it's going smooth! One thing I noticed is that after I formatted my card to FAT32, it said my capacity was only 200MB? Is this normal?
It's a 16GB card.
Click to expand...
Click to collapse
interesting... windows says its 200mb or the phone does? see what it says after the update. Maybe it created a 200mb partition?

msticlaru said:
interesting... windows says its 200mb or the phone does? see what it says after the update. Maybe it created a 200mb partition?
Click to expand...
Click to collapse
Phone also says 200MB. Phone is back to stock and ready to roll. Still haven't recieved a prompt for froyo yet, checked about phone, still running 2.1 update 1.

Keyboards said:
Phone also says 200MB. Phone is back to stock and ready to roll. Still haven't recieved a prompt for froyo yet, checked about phone, still running 2.1 update 1.
Click to expand...
Click to collapse
I think i read somewhere that when you don't accept the update it will wait like 20 min or so before it prompts you again. I don't know the exact time limit tho. you could do the *228 update just to make sure its registered right. i don't really know if that will help push the update or not.. but may as well do it.
as far as the card. after the update try formating it again. kinda of an odd issue. could try googling it

msticlaru said:
I think i read somewhere that when you don't accept the update it will wait like 20 min or so before it prompts you again. I don't know the exact time limit tho. you could do the *228 update just to make sure its registered right. i don't really know if that will help push the update or not.. but may as well do it.
as far as the card. after the update try formating it again. kinda of an odd issue. could try googling it
Click to expand...
Click to collapse
Still no prompt. Restarted, did *228, nothing. This card problem is also an issue now. It's showing only 200MB on Mac, PC, and the Incredible.

Keyboards said:
Still no prompt. Restarted, did *228, nothing. This card problem is also an issue now. It's showing only 200MB on Mac, PC, and the Incredible.
Click to expand...
Click to collapse
as far as not getting the prompt, you got me. I cant pretend to know how verizon does their business. Their website says if you ignore the update, it will continue to big you until you get it.
As far as the memory card goes. Thats not really a phone issue. My experience with formatting memory cards stops at the format. Never had it format it wrong. If it was happening to me, i would format it again with a format tool. I dont know your experience when it comes to troubleshooting problems like this. I would start by using multiple format tools on my PC, you said you have a mac, you can try formatting it with the mac. It seems like a simple fix, as it was reporting the right size prior to the format.
Did you format it in windows? did you just right click on it and hit "format" ? try using the disc management built into windows. It should show you the total size of the disc formatted or not. Its possible it somehow was formated as a 200MB partition. if that happened, then you have a 200MB logical partition, and the rest is unformatted and therefor un readable by anything other than a disc management type tool.
depending on your Operating System, your mileage will vary, but google how to open "disc management" for your OS. Stick the SD card in your card reader, then use the tools in disc management to format it to the correct size.
hope that helps.
Also, check your phone. settings > about phone > system information. Ensure you are running 2.1 update 1. and baseband 1.x. If you are, then its a waiting game. also, in the same screen click on "system update" and see if it has an update available. if not... you can always call verizon and play dumb. "ya i got the update, but i had to reboot my phone, when it booted back up i didnt have the update anymore!" see if maybe they can push it to you.
if all else fails you can load the RUU manually.

[Q] Yikes! Failed 2.2 Upgrade. Quick advice needed before I yank the battery.

So I had a very basic rooted phone with a minimum amount of stuff changed. I thought I changed everything back, including the stock recovery, but it failed.
So it started the recovery with the green circle but 1/4 of the way in it turned to the dreaded red triangle with red exclamation point.
My gut wants to pull the battery and hope comes up ok. My brain tells me to ask the people in the forums, who know better than I.
I connected it to my laptop for S&Gs and adb doesn't see the device (naturally).
What should I do?
I fixed anything I had thought I changed on the phone (CityID, removed tethering, etc)
I reverted to stock recovery
I booted the phone and and tried to let it install the OTA the phone downloaded

Just for others that may have this same problem...
So I did a little digging and found the option Volume Up + Power. It must have failed the checksum or something because it said...
Verifying Current System...
Assert Failed: blah, blah, blah
I chose the option to reboot and everything seems fine.
I added a new splash screen and boot animation and had not restored them to normal. Perhaps that was part of the failure. Worst case I'll have to use the RUU if I can't get the update to install properly.

Can you tell us a little more about you setup -
Are you S-OFF or S-ON
You said you were "basic" rooted - so I'm guessing this was at least Unrevoked 3?
There are two "versions" of the 2.1 system - the original with version 605.0 in the number and an HBOOT version of 0.77 and after the first OTA with a version 605.2 and HBOOT 0.79. I had read that people who tried to apply the OTA update from the 605.0/0.77 were having issues and that the 605.2/0.79 was fine.
And (of course) what version is your radio on? 1x or 2x?

Starfire-1 said:
Can you tell us a little more about you setup -
Are you S-OFF or S-ON
You said you were "basic" rooted - so I'm guessing this was at least Unrevoked 3?
There are two "versions" of the 2.1 system - the original with version 605.0 in the number and an HBOOT version of 0.77 and after the first OTA with a version 605.2 and HBOOT 0.79. I had read that people who tried to apply the OTA update from the 605.0/0.77 were having issues and that the 605.2/0.79 was fine.
And (of course) what version is your radio on? 1x or 2x?
Click to expand...
Click to collapse
Sure, and thanks for the help!
I have 2.1 Update 1 running with unrevoked 3 and unrevoked forever with S-OFF.
I have never done any updates to the radio and never updated OTA since I have had the phone for just over a month now (except for the recent 2.2 update, of course).
HBOOT is 0.79.0000
Firmware is 2.1 Update 1
Baseband Version is 1.00.03.04.06
Kernel Version is 2.6.29
Build Number is 1.22.605.2 CL161494 release-keys
Software number 1.22.605.2
PRI Version is 1.28_002
PRL Version is 51920
ERI Version is 5
Way more than you even need to know.
Anyway, I played with pre-releases of CM6 and SR2.2 and ultimately stayed with my stock ROM. But I did change a few things...
Renamed CityID
Installed the wireless tether kernel mod
Added boot animation and boot sound
Replaced splash screen
If there is anything else I did to the system folders, I'm not recalling it. I restored CityID and fixed the tether kernel with stock. The boot animation and splash screen I neglected to fixed before I tried to upgrade to 2.2.
I replaced the Clockwork Recovery with Stock Recovery. The update that I tried to install was the one it downloaded to my cache. It's called 8e5ad8d6ea2d.OTA_IncredibleC_Verizon_WWE_3.21.605.1_1.22.605.2_release_sign.zip. I just tried to apply the update when it prompted me to within the OS. Ultimately it failed and caused me to initially post this thread.
I'm fairly certain it failed the checksum. The odds of me getting it 100% back to stock are probably somewhat slim but I am going to try. The area it appeared to fail was when verifying sys/lib/modules/bcm4329.ko (whatever that is).
Do you think the boot animations and splash screens would cause it to fail the checksum? I didn't think the upgrade would check that.
Any enlightenment would be extremely helpful. I appreciate your efforts!

Hmmm....
I did find THIS in regard to bcm4329.ko.
I'll try updating the file with the one provided in the thread and report back later. I don't really have the time to get into it now...

Your situation does not sound bad (that's good).
I read a while ago that the OTA really does not like a modified system. I can suggest a path that is similar to what I did:
- (Optional) User Titanium Backup to save your user apps
- Save of the OTA file from your cache or download it (from google)
- As you are S-OFF, Use the 605.2/0.79 RUU (either .exe or PB31IMG.zip) and revert to a pristine (non-root, unmodified) 2.1 system. (Ensure that you sd card is formatted FAT32 if you do the PB31IMG route)
- Delete PB31IMG.zip from your sd card if necessary
- Apply the OTA by renaming it update.zip and putting it on your sd card. Boot into (stock) recovery:
-- Power on holding Vol Down and Power
-- Wait a few seconds for it to look for PB31IMG (it will fail) and then select RECOVERY with vol down then power
-- At the red exclaimation point screen, press vol up and power to get the recovery menu and select apply the update.zip
-- As the process works, don't worry too much if the phone seems to reboot and start over, it does that when it updates the radio. Just stick with it.
-- The first real boot takes a while at the Droid splash screen so hang on
- Delete update.zip (the OTA) from your sd card
- Now you are stock 2.2 / S-OFF. Flash ClockworkMod (using the PB31IMG.zip file on Unrevoked's site) by putting it on the sd card and just booting with Vol Down/Power. It will see the PB31IMG file and ask if you want to install.
- Delete PB31IMG.zip after reboot
- get payload_update.zip and a recent version of Superuser.apk as an update.zip file - put them on your sd card
- Boot into ClockworkMod recovery and apply zip file (the "select the file" flavor as opposed to the simple update.zip flavor). Do payload_update.zip first, then the newer Superuser.apk
- Reboot - you are now 2.2 rooted. Go get titanium backup and install it. When it starts you should be prompted for Superuser rights. Hit the "Fix problems" button in Titanium to download a copy of busybox for Titanium.
- I read that it is probably better to reinstall the apps from the market rather than from the Titanium backups - but the backup have the data that you need. So I selectively restored the data from the apps.
So anyway - that's the path I took. Seems to be ok.

Thanks for the info. Got a busy weekend ahead of me but I plan on playing this weekend. Any reason in particular you didn't use the released 2.2 RUU? Seems like you could have elimiated some of the steps. Froyo RUU Post
I'm trying to upgrade if at all possible because of Lockpicker (bypassing Exchange Server security policies). Apparently it seems the upgrade allows the app to continue to function. It does not work using a clean install of 2.2.
I have come across another way to bypass the security policies in the Exchange Server in 2.2. It's not as nice and clean as Lockpicker but appears to have had some success stories.
Worst case, I'll use what you got above here for a clean install. I really appreciate your time.

clambert11 said:
Hmmm....
I did find THIS in regard to bcm4329.ko.
I'll try updating the file with the one provided in the thread and report back later. I don't really have the time to get into it now...
Click to expand...
Click to collapse
Just wanted to touch base...
In my situation, pushing the bcm4329.ko file from the linked thread solved my problem and did allow me to upgrade without issue. I'm rollin' on 2.2 with all the latest versions.
Sadly, however, Lockpicker didn't seem to still work after the upgrade like at least one other person reported. Going to have to try another option I uncovered.
Thanks again for all your help.

[Q] Stupid Root Question

Sorry if it has been answered elsewhere, but I have a migraine and am going for now. I just wanted to post really fast. I rooted my phone recently and have CM 7.2 on my Dinc. Now it suddenly seems that programs seem to think it isn't. Programs such as Titanium Backup won't work saying there is no root. Same with BusyBox and so on. Anyone had any issues like this? Any ideas as to what is next? I am somewhat new to this and would appreciate the help.
Tried to just reroot, but can't seem to get DooMLord's thing to work. Can't get the ADB drivers since, for some reason the Android SDK thingy WILL NOT download the Google USB driver packages. Tried about 6 different times and it just will not download and install them. HELP?

BuffaloChips said:
Sorry if it has been answered elsewhere, but I have a migraine and am going for now. I just wanted to post really fast. I rooted my phone recently and have CM 7.2 on my Dinc. Now it suddenly seems that programs seem to think it isn't. Programs such as Titanium Backup won't work saying there is no root. Same with BusyBox and so on. Anyone had any issues like this? Any ideas as to what is next? I am somewhat new to this and would appreciate the help.
Tried to just reroot, but can't seem to get DooMLord's thing to work. Can't get the ADB drivers since, for some reason the Android SDK thingy WILL NOT download the Google USB driver packages. Tried about 6 different times and it just will not download and install them. HELP?
Click to expand...
Click to collapse
Open the superuser app and hit menu and select preferences. Scroll to the bottom and tap check for updates. If it says you have the latest update then hit the update anyways button. Also make sure you have the latest version of busybox installed. Then see if apps can get root. If not post back with your info.
S-off / s-on (can be found at the top of the hboot screen)
Android version (menu settings about phone software information)
Hboot version (found on hboot screen)
Radio (baseband) version. (also on hboot screen)
Also you can get the adb files and drivers here http://dinc.does-it.net/ADB

Tried that and it said d'ling manifest ... okay, parsing manifest ... okay, checking installed version = 3.0.3.2 . I clicked update anyway and got ,,, d'ling custom busybox ... okay, checking md5sum... FAIL! Tried the update fixer and it doesn't work either.Says no problems detected. In the little window it says checking signatures...ok! I click force and fix and get, extracting tiny busybox...fail! It says something about trying to download update.zip from somewhere but I cant see the rest.
My phone is s-off
Android version says 2.3.7
hboot 0.92.0000
radio 2.15.00.07.28
Now all I need are some good drugs so I can sleep. Migraines suck! It won't even let me do that.

BuffaloChips said:
Tried that and it said d'ling manifest ... okay, parsing manifest ... okay, checking installed version = 3.0.3.2 . I clicked update anyway and got ,,, d'ling custom busybox ... okay, checking md5sum... FAIL! Tried the update fixer and it doesn't work either.Says no problems detected. In the little window it says checking signatures...ok! I click force and fix and get, extracting tiny busybox...fail! It says something about trying to download update.zip from somewhere but I cant see the rest.
My phone is s-off
Android version says 2.3.7
hboot 0.92.0000
radio 2.15.00.07.28
Now all I need are some good drugs so I can sleep. Migraines suck! It won't even let me do that.
Click to expand...
Click to collapse
Try flashing these thru recovery.
http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip, and http://dinc.does-it.net/BusyBox/Busybox_1.19.4_Flashable.zip, then boot and see if your apps can get root.

Flashed them but no good. Still says no root with programs requiring it.
Was going to go nuts and shoot for flashing Condemned CM7.2 to see if I brick my phone or not, but after d'ling the ROM, I'm not sure what I'm supposed to do next.

BuffaloChips said:
Flashed them but no good. Still says no root with programs requiring it.
Was going to go nuts and shoot for flashing Condemned CM7.2 to see if I brick my phone or not, but after d'ling the ROM, I'm not sure what I'm supposed to do next.
Click to expand...
Click to collapse
If you want to flash a new rom, download the roms zip to your sdcard. Go to recovery and go to advanced and wipe dalvik-cache. Go to mounts and storage and format everything in there except sdcard and emmc. Then go to install zip from sdcard, internal sdcard, and choose the rom zip you downloaded, and select yes to flash it.
Are you sure that you have superuser app set to allow, and not deny these root apps. Try opening superuser app ad removing the root apps from the list. Then try using the root apps and see if it propmpts for and allows root.

I have super user set to prompt me every time and I click on allow. And yes, I have deleted and retried them so many times I want to rip out what is left of my hair.
OK, after flashing Condemnedsoul's cm7.2 (post says v12 but in about phone I get v10, go figure) nothing had changed. I got the ROM manager updated and clicked fix permissions and it went through a bunch of stuff. Now, before it wouldn't do anything through the ROM manager and recovery would do nothing either. Guess I found the culprit here. This is the bad thing about not being able to remove and reinstall these little items. Makes you really crazy at times as you are not necessarily sure that it is really the issue and if it is.... it requires a bit of extra work to fix. Live and learn.
Thanks for trying hard to help me though. It is greatly appreciated.
Oh, thanks for reminding me I am an idiot for not realizing one CAN flash ROM's straight from a .zip through recovery. LMAO! (this is meant as self-deprecating and not as an insult to you)

BuffaloChips said:
I have super user set to prompt me every time and I click on allow. And yes, I have deleted and retried them so many times I want to rip out what is left of my hair.
OK, after flashing Condemnedsoul's cm7.2 (post says v12 but in about phone I get v10, go figure) nothing had changed. I got the ROM manager updated and clicked fix permissions and it went through a bunch of stuff. Now, before it wouldn't do anything through the ROM manager and recovery would do nothing either. Guess I found the culprit here. This is the bad thing about not being able to remove and reinstall these little items. Makes you really crazy at times as you are not necessarily sure that it is really the issue and if it is.... it requires a bit of extra work to fix. Live and learn.
Thanks for trying hard to help me though. It is greatly appreciated.
Oh, thanks for reminding me I am an idiot for not realizing one CAN flash ROM's straight from a .zip through recovery. LMAO! (this is meant as self-deprecating and not as an insult to you)
Click to expand...
Click to collapse
Yeah it is recomended not to use rom manager for flashing things, but to go straight to recovery to do it. The only thing i use rom manager for is so that i get notified about new versions of cwm recovery.
If flashing new roms dosent fix the issue there are always ruu's which will put your phone back to complete stock except for still having s-off, making it easy to root again.

Great! Wi-Fi doesn't want to work now! Crap! Gets as far as trying to obtain an IP address from my router and then says out of range while I am about ten feet from the router and the strength meter is showing full...! It just gets better and better some days.

BuffaloChips said:
Great! Wi-Fi doesn't want to work now! Crap! Gets as far as trying to obtain an IP address from my router and then says out of range while I am about ten feet from the router and the strength meter is showing full...! It just gets better and better some days.
Click to expand...
Click to collapse
Sounds like you need to just ruu and start over fresh. Seems something is seriously buggy with your setup. Are you using a custom kernel, or one that came with the rom?

Well, Wi-Fi was working with the original CM7.2. Just seems that it isn't with Condemned's. And I am using the kernel that came with the ROM.
To be honest, I haven't a clue about doing an RUU install.

BuffaloChips said:
Well, Wi-Fi was working with the original CM7.2. Just seems that it isn't with Condemned's. And I am using the kernel that came with the ROM.
To be honest, I haven't a clue about doing an RUU install.
Click to expand...
Click to collapse
Ruus are pretty simple. Make positive you are s-off before doing this, or rerooting will be a lot harder.
Download the ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip
Do not rename it just stick it on the root (in no folders) of your sdcard.
Boot into recovery (if entering recovery thru hboot select no when prompted to update) wipe dalvik-cache in the advanced menu, and format everything in mounts and storage except emmc and sdcard.
Power off the phone and boot to hboot. (hold vol down plus power till a white screen pops up) Hboot will find the ruu automaticly and prompt you to press vol up to update. Do so and let it do its thing, note it will reboot once durring the ruu, be patient and do not interupt it. When done press vol up to reboot. You are now stock.
Do the setup on the phone and then go to menu - settings - applications, and uncheck fastboot. Use a file explorer or pc to remove the PB31IMG.zip from your sdcard.
Power off the phone and boot to hboot again. From the hboot menu select factory reset. This will ensure all corrupt data is gone. After it finishes the phone should boot again. Once again do the setup and uncheck fastboot again.
Download these two files:
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
Do not rename them and place them on the root of your sdcard.
Power off the phone and boot to hboot. It will find the PB31IMG.zip file (cwm recovery) and prompt to press vol up to update. Do so. When asked to reboot press vol down no.
Select recovery from the hboot menu. Once in recovery select install zip from sdcard - internal sdcard- and select the Superuser_3.0.7.zip. Select yes when prompted.
Reboot thr phone and go to the market and download the busybox app. Open busybox and install it. Go to your sdcard and delete or rename the clockwork PB31IMG.zip.
Thats it you should be stock rooted. From here you can stick with stock, or flash a rom of your choosing.

I have a PB31IMG.zip file that is 176,626kb with 8 "files" in it. It has andriod-info.txt, hboot_8x50_0.92.0000_100723nb0, radio.img, boot.img, recovery.img system.img splash1.nb0 and nv_MFG_VZW_1.70_0825_PRL58006.img in it. Any idea what the hell this is for? I thought about trying to use it, but I can't even remember what the hell it is. Sad, I know. I should have renamed it so I would know.
Live and learn ......

BuffaloChips said:
I have a PB31IMG.zip file that is 176,626kb with 8 "files" in it. It has andriod-info.txt, hboot_8x50_0.92.0000_100723nb0, radio.img, boot.img, recovery.img system.img splash1.nb0 and nv_MFG_VZW_1.70_0825_PRL58006.img in it. Any idea what the hell this is for? I thought about trying to use it, but I can't even remember what the hell it is. Sad, I know. I should have renamed it so I would know.
Live and learn ......
Click to expand...
Click to collapse
That is an ruu. Not sure which version, but definitley an ruu.
PB31IMG.zip files can be ruu's, radios, splash screens, recoveries, hboots, or a combination of them.