[TESTING] - NAND OMGB (1.2.3)

[mayestik1]

Can't wait for testing new improvements. I'm glad to hear about battery fixation

[wizardknight]

A good battery driver would make me take the jump to NAND. I do hope we get a release soon that has this in it.

A question to those running NAND. Any issues with forced reboots corrupting data? I know that the data.img file can be corrupted sometimes on the SD side of things if you lock up and have to force a reboot. I didn't think there were similar issues with NAND, but I thought I would ask.

[htrakr]

There are reboots (rarely but it does happen especially if you have a lot running). There is no data corruption

[rwar]

Originally Posted by wizardknight

A good battery driver would make me take the jump to NAND. I do hope we get a release soon that has this in it.

A question to those running NAND. Any issues with forced reboots corrupting data? I know that the data.img file can be corrupted sometimes on the SD side of things if you lock up and have to force a reboot. I didn't think there were similar issues with NAND, but I thought I would ask.

No issue here with forced reboots corrupting data

[arrrghhh]

Originally Posted by wizardknight

A good battery driver would make me take the jump to NAND. I do hope we get a release soon that has this in it.

A question to those running NAND. Any issues with forced reboots corrupting data? I know that the data.img file can be corrupted sometimes on the SD side of things if you lock up and have to force a reboot. I didn't think there were similar issues with NAND, but I thought I would ask.

Originally Posted by rwar

No issue here with forced reboots corrupting data

Originally Posted by htrakr

There are reboots (rarely but it does happen especially if you have a lot running). There is no data corruption

Data corruption that is experienced on the SD builds is pretty much impossible to experience on NAND - we can't properly unmount the partitions on SD builds, and therefore the data partition/image file always ends up in a dirty state. That and it's all running on FAT32, don't even get me started on what a nightmare that is in practice.

So eliminating those factors have eliminated the data corruption. I've never experienced it on NAND, nor would I ever expect to experience it.

[wizardknight]

Ok. I decided to give NAND a try on my backup phone. I got adb loaded up ok, loaded RHODIMG.NBH onto the phone. I get the minipooploader blue screen, and fastboot devices returns a name. So I think that is all good.

This is where I am stuck. I seem to be missing a step. I put recovery.img into
C:\android-sdk-windows\platform-tools>

I get this error. When I try to flash.
C:\android-sdk-windows\platform-tools>fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'

Could someone give me a hint please?

[arrrghhh]

Originally Posted by wizardknight

Ok. I decided to give NAND a try on my backup phone. I got adb loaded up ok, loaded RHODIMG.NBH onto the phone. I get the minipooploader blue screen, and fastboot devices returns a name. So I think that is all good.

This is where I am stuck. I seem to be missing a step. I put recovery.img into
C:\android-sdk-windows\platform-tools>

I get this error. When I try to flash.
C:\android-sdk-windows\platform-tools>fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'

Could someone give me a hint please?

First, I would download CWM not AOSP recovery.

Then,

fastboot flash recovery cwm_recovery.img

After that, either reboot:

fastboot reboot

Or my personal fave, go straight to recovery:

fastboot boot cwm_recovery.img

Please see the wiki for more info.

[wizardknight]

Originally Posted by arrrghhh

First, I would download CWM not AOSP recovery.


Then,

fastboot flash recovery cwm_recovery.img

After that, either reboot:

fastboot reboot

Or my personal fave, go straight to recovery:

fastboot boot cwm_recovery.img

Please see the wiki for more info.

Thanks. I went with the recovery that was on the first page. The one you pointed me at worked much better. I was still having issues with it timing out. I found that I had a crappy usb cable. Replaced that and I was good to go. I am looking at a NAND system now.

I wish that the wiki you pointed me towards was sticked in the first post. It was helpful.
Thanks again.

[arrrghhh]

Originally Posted by wizardknight

I wish that the wiki you pointed me towards was sticked in the first post. It was helpful.
Thanks again.

Not to be a complete dick, but it is in the first post...

Originally Posted by [ACL]

Instructions are simple. Flash RHODIMG.NBH via sdcard, boot with USB plugged in and flash recovery using fastboot (Make sure you can adb/fastboot prior to attempting this). Reboot into recovery and update from sd and select OMGB. Once you are up and running, you can boot back into recovery and install GAPPS. Don't try to install GAPPS at the same time, I find that it causes some crashes if this way is done. Alternate instructions can be found here.

[wizardknight]

Originally Posted by arrrghhh

Not to be a complete dick, but it is in the first post...

Sorry for failing so badly. I was looking for something called wiki as you called it that. I will be sure that I am punished appropriately.

http://www.youtube.com/watch?v=G316p...eature=related