[Q] Concern before continuing install of custom ROM....

---

Alrighty..... I've read / had open the posts regarding ADB, Unrooting, Nandroid, etc multiple times, and I want to make sure things are OK / voice some concerns before I continue.

I've installed the USB drivers needed (installed those only, did NOT install the rest of the components).

Ran SDK setup, edited the android_winusb.inf (have original as .bak)

Had USB Debugging enabled

Confirmed Android Phone listed in Dev. Manager as Android Bootloader Interface

Ran UnrEVOked3 reflash tool, without difficulty, and phone finished in koush clockworkmod recovery, and rebooted.

Used Nandroid Backup to backup to SD card, later confirmed via exploring SD card for confirmation with observing clockworkmod folder. Afterwards, reset back to "Charge Only"

At this point, I wanted to confirm root, and using ADB shell in command prompt typed in at $ su and was rewarded with the response of su / Permission denied / $.

A bit concerned, I rebooted the phone, everything works (well, I don't directly observe any issues, can make / receive calls, texts, etc).

Under "Software Information" I see:
Firmware Version: 2.1-update!
Baseband version: 1.00.03.04.06

I'm very much aware that I need to update the radio, plan on using unrEVOked Forever. I have the option to use Clockworkmod "apply sdcard:update.zip" next.

I'm wanting to make sure things are "OK" and the phone is sucessfully "rooted" before I carry on.

I have no doubt this is the "umteenth" thread, but it's my first "smartphone", and my first time doing this, so please be gentle, it really is my first time

Thanks for any time on this, and posted responses.

If you got permission denied when running su in adb shell the your root didnt go correctly. It should of just dropped you to a # prompt. When you typed su did you then go to your phone and get the popup by superuser asking if you allow or deny? Did you select allow?

while in adb and typing su it should look like this

$su
#

I never got the option, or I didn't see it. ::Confirmed::, I still get the $ after typing in su

Another question: Should I install the packages listed in the SDK update as well? I have 2.2, API 8, revision 2, 2.1-update1, API 7, revision 2, and 1.6 listed, and 2.1-update1 is listed as my latest firmware

**Update** Via unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery, I see device listed with (recovery) next to it. I presume with the 3 files listed to download, I place them in the root of my SD card?

I think that $ is normal on the stock rom with the phone booted up. Your nand is still locked because you haven't done the unrevoked forever, yet. Boot into recovery and do it and you should get the # root prompt. Sounds like you're on the right track.

Typed on my Incredible phone!

Last question (I think)....

I'm assuming that I rename unrevoked-forever.zip to update.zip, and thats the file that I place in the in the root of my SD card, reboot into recovery and select apply update?

#
The update can be installed like any custom .zip file. Simply flash it from your custom recovery. Both Amon_RA and Clockworkmod Recoveries support custom .zip installs from the sdcard.
#
Either select the option to install a .zip from your SD card, or apply it as an update.zip as follows:
#
Place the update.zip file into the root of your SD card. You can do this with adb with the command: adb push unrevoked-forever.zip /sdcard/update.zip


I have a feeling I'm misunderstanding some part of that, but I want to make sure before I finalize this.

Does this look good for a final step?

***Update****

Applied Forever Patch, no issues what so ever. Phone loads back to previous states, now I get the # after su request in shell.

I"m still seeing a Baseband Version of: 1.0.03.04.06. The next step is to update the radio, then off to a custom ROM of my choice?

Originally Posted by HyperTension

***Update****

Applied Forever Patch, no issues what so ever. Phone loads back to previous states, now I get the # after su request in shell.

I"m still seeing a Baseband Version of: 1.0.03.04.06. The next step is to update the radio, then off to a custom ROM of my choice?

Correct. Be sure to do a nandroid before you do each thing. I know it sounds silly and like a lot of backing up, but you'll be glad you've got it if something goes wrong. You can almost always get back to good with a nandroid backup.

Isnt that the truth

Takes 5 minutes to backup, and 5 seconds to break lol. NANDROID

I have not had a chance to flash the radio / install a custom ROM, but everything works!

Big thanks for the support / guidance through this!