Glad to see a new thread open up. Looks like the classicnerd is about to make it's official debut and no longer in the shadows

Originally Posted by advocate2

I'm having the same problem on my 16 that I had on the thirty-two. Coming from Xron 2.9.1 Wipe, wipe, wipe. Install zip. Choose zip. Buttah first, then Gapps v.8.

Message:

Checking uImage...Invalid size

BOOT FAILED

Press SELECT to continue.

Repeated entire process again, same result.

Repeated entire process again, same result.

On my thirty two, I then did acmeuninstaller, acmeinstaller2 with Dalingrin's ICS and all worked fine. I am determined to get the 16 running Buttah. Please help.

I had the same problem. Run remove moboot entries and buttah will install ok.

Congratulations Leo and team! I'm excited!

Is camera working? Currently on cm9 and I really miss skype...

Originally Posted by chicle_11

Some feedback:

Ran Tommy's remove moboot entries and buttah installed fine.

Ran 2 Antutu benchmarks, 2750 and 2770.

Asphalt 6 and Gun bros would not run.

No problems at all with wifi.

Restored cm9 06.

Antutu benchmarks, 5350 and 5570.

Asphalt 6 and Gun bros run fine.

Wifi runs fine.

Will keep switching back and forth through the day and post the results.

Something off. I have over 5k scores. Did you reboot and let the scripts settle in and clear the memory?


Sent from my PG86100 using Tapatalk

Originally Posted by Leoisright

None of them have hd video right now. It's the codecs causing issues.

Sent from my PG86100 using Tapatalk

Leo, with webos becoming open source will these codes become available?

Originally Posted by Leoisright

Something off. I have over 5k scores. Did you reboot and let the scripts settle in and clear the memory?


Sent from my PG86100 using Tapatalk

I rebooted twice and wiped cache and dalvik cache.

I'll try again in a couple of hours (have to pick up daughter at airport).

Great stuff leo!!


Some notes:

- Moboot theme was erased when i flashed. This also happened with SE, so I assume it is intentional, probably a cleanup of some kind. Re-flash right after and it was fine.

- If your Moboot entry does not say "Classicnerd" you are likely suffering from a full /boot partition. There are several ways to fix it as noted earlier in the thread. This will likely result in boot issues or the red box problems. (Does not apply if you are running a custom kernel)

- During this flash I lost my Gapp settings. I think it may have been because I tried to open gmail and youtube before re-installing Gapps. Just do it as part of the install and you should be fine. Worst case just fill out info again and you will be up and running.

- Black screen after Moboot and before boot animation is a known issue.

- I did flash right over SE and so far it has been very stable. If you do run into issues try wiping first.

- I don't know if anything new was done with wireless but both this build and the SE have been very rock solid on my work network. Previous builds would have issues due to the need for proxy servers, overlapping access points with staggered channels, and PEAP authentication. With this build I was able to connect to my phone, download the build, reboot 3 times, and every time I was reconnected before I could login. Wonderful job

Tonight I will work on a format system, cache, and moboot to make things easier for everyone. We need a better cleanup then thru recovery format.

One flash and fix moboot and system will be a nice addition.

Sent from my PG86100 using Tapatalk

Originally Posted by chicle_11

I rebooted twice and wiped cache and dalvik cache.

I'll try again in a couple of hours (have to pick up daughter at airport).

On SE I was pulling 6029. I am running now with the new update.



Just finished with a 6033. This is with SetCPU overclocking at 1.7.


Edit: Just ran with Chainfire3D reducing the textures and got a 6274. Really looking forward to when the HD stuff gets worked out

Originally Posted by Leoisright

Your /boot is full which is causing the issue. Try flashing the uImage cleaner that tommy posted in the download section first, then wipe everything then flash.

Option 2.

WebOS, use internalz pro. Got to /boot and delete the following if you have them.

uImage.Cyanogenmod
uImage.Classicnerd-SE
uImage.Evervolv
Moboot.background.splash.tga
any splash.tga except webOS one.

Then try flashing again. The problem is when you have full /boot, the uImage can't be copied over and then it won't boot. uImage is like the kernel if you will extracted from the boot.img

This method worked for me fine when I had boot failed messages.

Goodluck.

Sent from my PG86100 using Tapatalk

I used the Internalz and none of these files were on my system. On the other hand, I see a uImage-2.6.35-palm-tenderloin, which was also on my thirty-two. Should that be there or should it be deleted?

Update___ After deleting the uImage-2.6.35-palm-tenderloin, all worked fine. Hope this helps others.