NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery - Page 218

akbyrner · #**2171** (**permalink**) 03-26-2011, 07:13 PM

Hey guys. Don't know if you've run into any errors with the new way of installing, but I'm getting the same "Modules are not installed. Download the matching androidupdate.tgz and boot into recovery mode to install". I made sure I had the right files, along with the correct .nbh. Still nothing. So I used the old method to re-flash. Just letting you guys know.

**natemcnutty** · #**2172** (**permalink**) 03-26-2011, 07:17 PM

Quote:

Originally Posted by akbyrner

Hey guys. Don't know if you've run into any errors with the new way of installing, but I'm getting the same "Modules are not installed. Download the matching androidupdate.tgz and boot into recovery mode to install". I made sure I had the right files, along with the correct .nbh. Still nothing. So I used the old method to re-flash. Just letting you guys know.

As per the first post:

Quote:

Installation Procedure
You need 4 files to get NAND up and running:
androidinstall.tgz (system)
androidupdate.tgz (modules/updates)
recoveryinstall.tgz (recovery)
RHODIMG.NBH

1) The names must match exactly as listed, so you will need to rename the autobuild files appropriately.
2) The first three files must be in /sdcard/andboot, and then flash the NBH (either with the CustomRUU or from the root of the sdcard).

On first boot, hold Volume Up when prompted to get into recovery. Once the Android logo shows, press the Power Button to bring up the menu, use Volume Up/Down to select the option (Install System), then use the End Call button to select.

Follow the directions, and you won't get that error

Also, it will be changing very soon. I'm going to update init so it forcefully installs recovery and boots into it the first time after you flash. That should make this even more user friendly.

akbyrner · #**2173** (**permalink**) 03-26-2011, 07:33 PM

Quote:

Originally Posted by natemcnutty

As per the first post:
Follow the directions, and you won't get that error

Also, it will be changing very soon. I'm going to update init so it forcefully installs recovery and boots into it the first time after you flash. That should make this even more user friendly.

Well, that's what I was saying. I was trying to use the NEW system you guys were testing (removing recovery.tgz, and letting the boot screen run without touching it after updating with the new .nbh, which if I read correctly, has recovery packaged in with it). That's when I get that error. After trying a few different thing to see if it would work (to no avail, obviously) I went back to the original system and all was right with the world. I just didn't know if any of you had run into the same issue that I had.

**natemcnutty** · #**2174** (**permalink**) 03-26-2011, 07:41 PM

Quote:

Originally Posted by akbyrner

Well, that's what I was saying. I was trying to use the NEW system you guys were testing (removing recovery.tgz, and letting the boot screen run without touching it after updating with the new .nbh, which if I read correctly, has recovery packaged in with it). That's when I get that error. After trying a few different thing to see if it would work (to no avail, obviously) I went back to the original system and all was right with the world. I just didn't know if any of you had run into the same issue that I had.

Ahh, sorry, I misunderstood. The files on the autobuild do not have the auto-recovery install method yet. Only the ones that I have been building have that. I will be pushing those changes to the git later today after I get a chance to make a couple more minor adjustments and test them.

akbyrner · #**2175** (**permalink**) 03-26-2011, 08:01 PM

That explains a lot then. What exactly is the install method for the .tgz and .nbh that I was using? Was I supposed to leave recovery on my SD card?

**natemcnutty** · #**2176** (**permalink**) 03-26-2011, 08:31 PM

Quote:

Originally Posted by akbyrner

That explains a lot then. What exactly is the install method for the .tgz and .nbh that I was using? Was I supposed to leave recovery on my SD card?

Yeah, before you needed androidinstall.tgz, androidupdate.tgz, and recoveryinstall.tgz in your andboot folder, then flash the NBH, then hold the screen to boot into recovery (which installed when not found and then loaded up), then install system from in there, and then reboot.

I just pushed the change to include recovery.tgz in initrd and have it extract it if /recovery/init.recovery is not found. I don't think it will initiate an auto-build, but from here on out, I think ACL's autobuild files will include the new method which allows us to get rid of recoveryinstall.tgz from the sdcard.

jadenq · #**2177** (**permalink**) 03-26-2011, 09:11 PM

Quote:

Originally Posted by akbyrner

I had the same problem once. Once the phone turns on after booting, unplug the phone and pull the battery out. Then put the battery back in and hold volume down while you turn the phone on. From there you can re-connect the phone to your computer, make sure to re-run the custom RUU.

I think it has something to do with the battery. My friend has the same phone so he let me try his battery and the power button worked fine then and it booted no problem. I couldn't try your solution because the power button wont turn on the phone it only turns on after it has been plugged in for about 5 minutes. Then it tries to boot but only gets half way through and turns off. Any thoughts?

Edit: I got it to boot into the menu when i hold down the volume down button but it wont charge. I am going to keep trying.

akbyrner · #**2178** (**permalink**) 03-26-2011, 10:43 PM

Quote:

Originally Posted by jadenq

I think it has something to do with the battery. My friend has the same phone so he let me try his battery and the power button worked fine then and it booted no problem. I couldn't try your solution because the power button wont turn on the phone it only turns on after it has been plugged in for about 5 minutes. Then it tries to boot but only gets half way through and turns off. Any thoughts?

Edit: I got it to boot into the menu when i hold down the volume down button but it wont charge. I am going to keep trying.

If your friend has the same phone, charge your battery then do what I said before. Chances are your power button isn't the problem, but the fact that your battery doesn't have enough of a charge to start up.

tiger2wander · #**2179** (**permalink**) 03-26-2011, 10:57 PM

Quote:

Originally Posted by jadenq

I think it has something to do with the battery. My friend has the same phone so he let me try his battery and the power button worked fine then and it booted no problem. I couldn't try your solution because the power button wont turn on the phone it only turns on after it has been plugged in for about 5 minutes. Then it tries to boot but only gets half way through and turns off. Any thoughts?

Edit: I got it to boot into the menu when i hold down the volume down button but it wont charge. I am going to keep trying.

Quote:

Originally Posted by akbyrner

If your friend has the same phone, charge your battery then do what I said before. Chances are your power button isn't the problem, but the fact that your battery doesn't have enough of a charge to start up.

yall need an external charger as I said in few earlier pages to get your batt enough energy before it can continue its job, else u will get a boot loop because of early boot process will not charge your batt and it will simply drain and power off.

mangus580 · #**2180** (**permalink**) 03-26-2011, 11:00 PM

Quote:

Originally Posted by natemcnutty

As per the first post:
Follow the directions, and you won't get that error

Also, it will be changing very soon. I'm going to update init so it forcefully installs recovery and boots into it the first time after you flash. That should make this even more user friendly.

Please tell me you updated this since my post last night, and I am not an idiot - who missed it even after reading several times!!!

Now I see how to install it! Thanks