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.
Related
So I never rooted, I have been waiting for the Over the Air.
If I root now, when I get the OTA will I still be rooted? And if so, what steps should be taken?
I know there are two unrevoked applications that need to be run...the first for root...the second for s-off (which I am still not entirely sure what this is)....
I have also seen that unrevoked is much simpler on a Mac and thankfully I just got one.......
So if rooting now and getting the OTA and keeping root is possible.... is there a step by step of the order I should do this in? (please don't flame and say I can search...I did...couldn't find.. I did however find a ton of threads where people say to search.......if you need to flame me can you at least post a link to where I was stupid enough to miss it)
Thanks
I am wondering the same. I have rooted with unrevoked3 and forever but have not touched the radio. Will I receive the OTA like this? If not what do I have to do to get the OTA and then get root back ?
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.
UPDATED: with slightly better instructions
Note: If u are s-off and on a custom rom, or have already s-off and customized your current rom you can start at step 3. make sure u have s-off by checking hboot. i put this in because many people asked me what to do if they ddnt start in a stock state.
This process is for people with a fully stock phone who want to apply the stock 2.2 update and maintain root.
I just went through this process.
(sd card must be formatted to fat32. without that most of this will fail.)
Step 1: do this -> http://unrevoked.com/recovery/
(this will root your phone and flash clockworkmod recovery.)
Step 2: do this -> http://unrevoked.com/forever/
(this will use clockworkmod recovery to permanently unlock the nand, also known as s-off.)
-- To backup apps that you want after the phone is fully updated at this point download titanium backup and backup whatever apps u need. make sure u take the backup folder from the sd card and store it on ur pc for later use.
Note: Titanium is probably going to tell u that it couldnt get root. that is because busybox is missing. hit the problems button on titanium and upgrade busybox. this will upgrade busybox if ur using an older version, or download the right version if u dont have one. this should take care of all busybox needs.
Step 3: do this -> http://forum.xda-developers.com/showthread.php?t=756850
(put into sd card and hboot apply)
(this will restore the recovery back to stock as it is needed for the RUU)
now u have an s-off phone with everything else stock.
Step 4: now either get the RUU -> http://forum.xda-developers.com/showthread.php?t=765596
or wait for OTA
(install htc sync to be able to run this. the RUU will load the stock 2.2 rom 2.15 radio that is needed. everything will be wiped, but that is a good thing imo.)
once u have updated ur phone fullly
Step 5: get recovery here http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
put in sd card and hboot apply
(this will load clockworkmod recovery on your phone so that u can apply updates.)
Step 6: put in sd card -> http://forum.xda-developers.com/attachment.php?attachmentid=388592&d=1282834695
and
http://bit.ly/su234ef
and use recovery to install both those zips.
(clockworkmod recovery allows u to apply .zip files, use that option to do this.)
(this will re-root the newly updated phone and install the superuser.apk.)
congratulations now u have an OTA/RUU applied phone with root.
-- If you had titanium backups you want to restore, paste the folder u saved on the desktop back here, re-install titanium from the market and restore apps. It is recommended to redownload the app from the market and just restore the data for the app if possible.
Note: Titanium is probably going to tell u that it couldnt get root. that is because busybox is missing. hit the problems button on titanium and upgrade busybox. this will upgrade busybox if ur using an older version, or download the right version if u dont have one. this should take care of all busybox needs.
notes:
* to enter hboot turn off phone then hold vol down and power till hboot appears.
* to enter recovery, enter hboot and select recovery.
* to check if nand is unlocked, hboot must read S-OFF
* you only need stock recovery to load the RUU, so if you have flashed a different rom, simply revert to the stock recovery and apply the RUU
* all links are property of their original creators, thanks to all of them.
EDIT: and yes please make love multiple times.
Wow... Thanks... This should definitely be stickied as a guide!
Sent from my HTC Incredible
No prob, if you need any help when you are getting to the nitty gritty pm me and I'll give you a phone number to call me at, I love doing this stuff.
Thanks... Will probably wait til the phone starts nagging me to update (from other phones I have seen its pretty persistent). This way in case anything new pops up I can add it to the process.
Also its 2 AM in New York right now, I have never rooted, let alone do everything to get ready for the OTA (definitely waiting for the push... Not applying it manually).... I'd probably frak it up at this hour!
Sent from my HTC Incredible
Thanks rdmerck and k.electron...very helpful and exactly what I've been looking for. After waiting a while, I finally decided to root tonight prior to the impending OTA update.
One cautious newbie question for step 3 (Flashing The Original Stock Recovery). Once in hboot (I entered this by holding down the volume down while powering up, right?), how do you know it will be running the PB31IMG.zip file (Stock Rom)? I didn't see it listed anywhere on the screen and it only offers the option of running recovery or not. I want to make sure that it's running off the correct .zip file. It lists:
INCREDIBLE XC SHIP S-OFF
HBOOT-0.77.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Mar 23 2010,19:26:22
HBOOT
Parsing...[SD ZIP]
[1] RECOVERY
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Just wanted to be sure before running the update. I assume you can delete the unrevoked-forever.zip once it's run, but can you delete the "update.zip" that appeared on the sdcard after running unrevoked?
Thanks in advance for any and all help!
chaint said:
Thanks rdmerck and k.electron...very helpful and exactly what I've been looking for. After waiting a while, I finally decided to root tonight prior to the impending OTA update.
One cautious newbie question for step 3 (Flashing The Original Stock Recovery). Once in hboot (I entered this by holding down the volume down while powering up, right?), how do you know it will be running the PB31IMG.zip file (Stock Rom)? I didn't see it listed anywhere on the screen and it only offers the option of running recovery or not. I want to make sure that it's running off the correct .zip file. It lists:
INCREDIBLE XC SHIP S-OFF
HBOOT-0.77.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Mar 23 2010,19:26:22
HBOOT
Parsing...[SD ZIP]
[1] RECOVERY
Do you want to start update?
Yes
No
Just wanted to be sure before running the update. I assume you can delete the unrevoked-forever.zip once it's run, but can you delete the "update.zip" that appeared on the sdcard after running unrevoked?
Thanks in advance for any and all help!
Click to expand...
Click to collapse
I just went through doing the same thing. I deleted the update.zip from my SD card just to make sure there was no confusion. Then I clicked yes when it asked to apply the update. Also, after this, if you boot into recovery ( its a couple options down in hboot, move with your volume button) you should get a red caution sign after a few seconds. Apparently this means you are back to stock. All credit goes to someone who helped me in another thread but I cannot find it right now.
chaint said:
Thanks rdmerck and k.electron...very helpful and exactly what I've been looking for. After waiting a while, I finally decided to root tonight prior to the impending OTA update.
One cautious newbie question for step 3 (Flashing The Original Stock Recovery). Once in hboot (I entered this by holding down the volume down while powering up, right?), how do you know it will be running the PB31IMG.zip file (Stock Rom)? I didn't see it listed anywhere on the screen and it only offers the option of running recovery or not. I want to make sure that it's running off the correct .zip file. It lists:
INCREDIBLE XC SHIP S-OFF
HBOOT-0.77.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Mar 23 2010,19:26:22
HBOOT
Parsing...[SD ZIP]
[1] RECOVERY
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Just wanted to be sure before running the update. I assume you can delete the unrevoked-forever.zip once it's run, but can you delete the "update.zip" that appeared on the sdcard after running unrevoked?
Thanks in advance for any and all help!
Click to expand...
Click to collapse
Yes, where it says
Parsing...[SD ZIP]
[1] RECOVERY
It is informing you that the only thing contained in the PB31IMG.zip file is a recovery image to be flashed. In this case, it is the stock Android 2e recovery that you will need. Press the volume up key to flash it, and then you can boot into the recovery console to verify that it works.
When you see a black screen, with a phone and a triangle with an exclamation point, you are in Android 2e recovery (your goal all along), press power+plus volume up, and you will see a meaningless error message and then a menu will appear at the top of the screen.
The first option will be to reboot the system, make sure it is selected and press the power button again. When you do, it will bring you back into your operating system.
Wait. I went out of order and started with the love making. That's as far as I got....
Sent from my ADR6300 using XDA App
amdpimp said:
Wait. I went out of order and started with the love making. That's as far as I got....
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
what? nooooo.... rooted 2.2 is the main thing your wife is interested in.. and your incredible too..
amdpimp said:
Wait. I went out of order and started with the love making. That's as far as I got....
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I most certainly hope you bricked lol
Sent from my ADR6300 using XDA App
When I do this method (and waiting for the OTA) do I need to back up anything? Or does it leave my apps and data untouched?
Sent from my HTC Incredible
Format FAT32 required on storage card
I'd like to point out that step 3 REQUIRES your storage card to be formatted FAT32. Clockwork will not update to "[Recovery] Stock 2.1 Recovery Image for DI" without you having first formatted your storage card to FAT32. This may be common sense but for a first rooter like myself, I figured it out by trial and error.
k.electron said:
I just went through this process.
first do this -> http://unrevoked.com/recovery/
then do this -> http://unrevoked.com/forever/
then do this -> http://forum.xda-developers.com/showthread.php?t=756850
(put into sd card and hboot apply)
now u have an s-off phone with everything else stock.
now either get the RUU -> http://forum.xda-developers.com/showthread.php?t=765596
or wait for OTA
once u have updated ur phone fullly
get recovery here http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
put in sd card and hboot apply
put in sd card -> http://forum.xda-developers.com/attachment.php?attachmentid=388592&d=1282834695
and
http://bit.ly/su234ef
and use recovery to install both those zips.
congratulations now u have an OTA/RUU applied phone with root.
EDIT: and yes please make love multiple times.
Click to expand...
Click to collapse
NYC Coyote said:
When I do this method (and waiting for the OTA) do I need to back up anything? Or does it leave my apps and data untouched?
Sent from my HTC Incredible
Click to expand...
Click to collapse
It will leave all data and apps untouched but get in the habit of backups ALWAYS. You never know when playing around like this. You may do one thing wrong and will be wishing you had taken 5 minutes to do a backup.
anothen said:
I'd like to point out that step 3 REQUIRES your storage card to be formatted FAT32. Clockwork will not update to "[Recovery] Stock 2.1 Recovery Image for DI" without you having first formatted your storage card to FAT32. This may be common sense but for a first rooter like myself, I figured it out by trial and error.
Click to expand...
Click to collapse
thank you and yes fat32 for all things sd card related.
anothen said:
It will leave all data and apps untouched but get in the habit of backups ALWAYS. You never know when playing around like this. You may do one thing wrong and will be wishing you had taken 5 minutes to do a backup.
Click to expand...
Click to collapse
frankly its much better to just use the ruu and have it update everything and wipe the phone. 2.1->2.2 app and data moving can sometimes leave behind some stale stuff that u dont want.
before i did the RUU i installed titanium and saved any apps that had states that i needed, like games. then after i installed the RUU and reinstalled the apps from the market, i just titanium restored the data for the app so it still had the latest app, but my save games were back in. that will give u a good factory like device but with whatever data you find necessary.
i also mounted system in recovery after the whole process and removed things like cityid, vzwnav, stocks etc.
k.electron said:
frankly its much better to just use the ruu and have it update everything and wipe the phone. 2.1->2.2 app and data moving can sometimes leave behind some stale stuff that u dont want.
Click to expand...
Click to collapse
If you ran the RUU straight up were you rooted before hand with S-off? Then you ran the full RUU and retained root?
I currently have root, stock radio and no s-off yet. and want to update and retain root.
Thanks.
-Lil'
rdmerck said:
Yes, where it says
Parsing...[SD ZIP]
[1] RECOVERY
It is informing you that the only thing contained in the PB31IMG.zip file is a recovery image to be flashed. In this case, it is the stock Android 2e recovery that you will need. Press the volume up key to flash it, and then you can boot into the recovery console to verify that it works.
When you see a black screen, with a phone and a triangle with an exclamation point, you are in Android 2e recovery (your goal all along), press power+plus volume up, and you will see a meaningless error message and then a menu will appear at the top of the screen.
The first option will be to reboot the system, make sure it is selected and press the power button again. When you do, it will bring you back into your operating system.
Click to expand...
Click to collapse
Thanks rdmerck. I didn't see the phone and triangle when flashing, however. When I originally pressed volume up to flash, it took just a few seconds, then prompted me to reboot which I did, then it loaded the OS as normal. Not sure if I needed to do something else, or if there's a way to check to see if it worked (I still see SU Permissions in my apps). Should I just try again? Any thoughts. Thanks, and sorry for these newbie questions!
Help a noob out
OK can someone help out ANOTHER noob here?
I have been following this thread among 30 others since yesterday and there seems to be a ton of different ways to go about getting the same results, which for me is the new leaked build with root. I am hoping someone can set me straight as I have info overload right now.
I am currently running stock 2.1 and used unrevoked to root.
I have not done anything else at this point. No radio update, no s-off, no roms.. nothing. I do not mind wiping the phone and reinstalling all my apps and probably would want to start fresh with the new install.
Someone made a reference a few post up about just running the RUU. Can I do that without losing root? Do I need to update my radio first? Should I installed 'forever' s-off before hand?
Any help would be greatly appreciated. I basically want to install what seems to be the official OTA/RUU and retain my root access so I can run wireless tether and remove bloat I dont want. Once some of the roms get cooked with the new build I can full around with them. Just need some help getting over the hump right now, so I can be running some Froyo goodness.
Thanks so much for any help you can lend.
-Lil
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.
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.
Hi,
I have my DHD root for some time and I followed instructions to retain root when I did the OTA in December. Since then I had many issues with superuser so i found a version that works correctly.
I decided to install and try Rom Manager to update my recovery to the latest.
Rom Manager opens, but at the prompt, it will not allow me to select OK to continue. I can cancel fine, so its not crashed/hung.
Is this the app not requesting root access in the same way as other apps?
Fastboot and busybox all work correctly with superuser.
Any help?
Anyone got any ideas?
I even installed fresh, LeeDroid last night and still it wont let me select OK to go in to ROM Manager?
Maybe something on my SD card?
CodeJACK said:
Hi,
I have my DHD root for some time and I followed instructions to retain root when I did the OTA in December. Since then I had many issues with superuser so i found a version that works correctly.
I decided to install and try Rom Manager to update my recovery to the latest.
Rom Manager opens, but at the prompt, it will not allow me to select OK to continue. I can cancel fine, so its not crashed/hung.
Is this the app not requesting root access in the same way as other apps?
Fastboot and busybox all work correctly with superuser.
Any help?
Click to expand...
Click to collapse
You are better off without the latest version of CWM if you have no plans of flashing CM7.
Damn, I just purchased the full Rom Manager in the hope that it would work.
What a waste of 4 Euro.
So I guess I wanted it for the ease of ability to manage ROM's as i use my phone more as a gadget rather than a phone. I like messing with all the great work chefs produce
Ill continue to flash via clockwork recovery and continue to upgrade clockwork recovery with the SDK.
I have a 16Gb Class 10 card on the way so when it arrives, ill do a full wipe and flash with a blank card to see what i get.
Any other suggestions greatly appreciated.
Going to bring this post back up as i was wondering if anyone had anything similar since?
I have gone totally back to stock now and done a fresh root and Eng and radio s-off but still Rom Manager opens but wont let me slect OK to continue.
I think its almost cetainly related to root access as I'm not able to choose allow when apps pop up requesting root. i have to deny them, close the app, then swap them to allow in Superuser and then run them again!
This is a real pain in my ass at the moment.
Is your superuser the latest version?
Yeah, have tried both the one in ChainsDD's thread which I know is very old.
Also tried the patched version that works properly with the later froyo build.
Have tried flashing LeeDroid and Revolution ROM's but still the same problem persists.
I went back to stock today, thinking it might have been a step i missed/screwed up. Still this problem persists.
I'm stumped. Could it be some hardware issue?
Well Damn crap n balls to it anyway!
Turns out after all this time, all I had to do was touch the search button at the bottom right of my HD to bypass the disclaimer of Rom manager.
I feel so dumb now. Still having issue with superuser allow button but I can work around that for now.
Sent from my Desire HD using XDA Premium App
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.
OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager
Older Recovery versions are available on "dougpiston.com" just follow the directions.
www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.
Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip
Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?