Can't install any 2.1 ROM

[Guest davedontmind]

I've now tried installing 3 different 2.1 ROMs on my Hero (BeHero, Villain, and SenseHero) and all have had the same issue.

I wipe, install the ROM, reboot, and get the ROM's custom animated boot screen. This screen stays there animating for maybe 10 or 20 minutes, then stops animating, and that's it. I have to remove the battery to restart the phone.

Anyone got any idea what's wrong? I have no problem running the MoDaCo 3.2 ROM.

[Guest Dr. dre]

I've now tried installing 3 different 2.1 ROMs on my Hero (BeHero, Villain, and SenseHero) and all have had the same issue.

I wipe, install the ROM, reboot, and get the ROM's custom animated boot screen. This screen stays there animating for maybe 10 or 20 minutes, then stops animating, and that's it. I have to remove the battery to restart the phone.

Anyone got any idea what's wrong? I have no problem running the MoDaCo 3.2 ROM.

That's the Boot Time it should take about 20-25 mins after that it would start definitely just give it a try.

and wipe the 'data' as well as 'dalvik cache' and ext partition if you have it.

[Guest Rashidi Zin]

I suggest that you use adb logcat to see what are the running back-end processes when your phone is booting. It helps to identify any error also, if it stopped running but your phone still haven't start, then there's something wrong.

[Guest davedontmind]

That's the Boot Time it should take about 20-25 mins after that it would start definitely just give it a try.

Up to 25 mins to boot a phone? *boggle* In the 30-or-so years of my computing experience I've never had any device take anywhere near so long to boot.

Ok, so perhaps I was impatient. I will have to try again.

and wipe the 'data' as well as 'dalvik cache' and ext partition if you have it.

I was just using the "wipe data/factory reset" option from the system recovery screen (hold home+power at boot time).

How do I wipe the 'dalvik cache' ?

I suggest that you use adb logcat to see what are the running back-end processes when your phone is booting. It helps to identify any error also, if it stopped running but your phone still haven't start, then there's something wrong.

Aha! I didn't know about this command. Will give it a go.

Thanks.

[Guest goatee]

Up to 25 mins to boot a phone? *boggle* In the 30-or-so years of my computing experience I've never had any device take anywhere near so long to boot.

Ok, so perhaps I was impatient. I will have to try again.

Think how many times Windows used to reboot your machine when you did an install, and how long it took, even once the main install was done - even MCR takes a while for its first boot.

[Guest davedontmind]

Well, 'adb logcat' shows that there is indeed some sort of error.

This is the tail end of the log, starting from just before the first exception:

I/PackageManager( 156): /data/app/net.flixster.android.apk changed; collecting certs

D/dalvikvm( 156): GC freed 18216 objects / 1068296 bytes in 230ms

D/dalvikvm( 156): GC freed 13564 objects / 891408 bytes in 230ms

D/installd( 131): DexInv: --- BEGIN '/data/app/net.flixster.android.apk' ---

D/dalvikvm( 402): DexOpt: load 390ms, verify 3301ms, opt 98ms

D/installd( 131): DexInv: --- END '/data/app/net.flixster.android.apk' (success) ---

D/PackageManager( 156): Scanning app dir /data/app-private

I/PackageParser( 156): game.golf.control.activity: compat added android.permission.WRITE_EXTERNAL_STORAGE

I/PackageManager( 156): /data/app-private/game.golf.control.activity.apk changed; collecting certs

D/dalvikvm( 156): GC freed 14218 objects / 786168 bytes in 241ms

E/System ( 156): Failure starting core service

E/System ( 156): java.lang.NullPointerException

E/System ( 156): at com.android.server.PackageManagerService$PackageSettingBase.<init>(PackageManagerService.java:5904)

E/System ( 156): at com.android.server.PackageManagerService$PackageSetting.<init>(PackageManagerService.java:5995)

E/System ( 156): at com.android.server.PackageManagerService$Settings.getPackageLP(PackageManagerService.java:6295)

E/System ( 156): at com.android.server.PackageManagerService$Settings.getPackageLP(PackageManagerService.java:6110)

E/System ( 156): at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.jav

:2329)

E/System ( 156): at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.jav

:2098)

E/System ( 156): at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:19

4)

E/System ( 156): at com.android.server.PackageManagerService.<init>(PackageManagerService.java:611)

E/System ( 156): at com.android.server.PackageManagerService.main(PackageManagerService.java:335)

E/System ( 156): at com.android.server.ServerThread.run(SystemServer.java:135)

E/AndroidRuntime( 156): Crash logging skipped, no checkin service

I/SystemServer( 156): not beta version and not show watermark

I/SystemServer( 156): Status Bar

E/SystemServer( 156): Failure starting StatusBarService

E/SystemServer( 156): java.lang.NullPointerException

E/SystemServer( 156): at android.app.ActivityThread.getPackageInfo(ActivityThread.java:2202)

E/SystemServer( 156): at android.app.ApplicationContext.createPackageContext(ApplicationContext.java:1341

E/SystemServer( 156): at com.htc.res.HtcResources.getContext(HtcResources.java:53)

E/SystemServer( 156): at com.android.server.status.StatusBarService.<init>(StatusBarService.java:323)

E/SystemServer( 156): at com.android.server.ServerThread.run(SystemServer.java:261)

E/AndroidRuntime( 156): Crash logging skipped, no checkin service

I/SystemServer( 156): Clipboard Service

I/SystemServer( 156): Input Method Service

E/SystemServer( 156): Failure starting Input Manager Service

E/SystemServer( 156): java.lang.NullPointerException

E/SystemServer( 156): at android.app.ApplicationContext.registerReceiverInternal(ApplicationContext.java:

46)

E/SystemServer( 156): at android.app.ApplicationContext.registerReceiver(ApplicationContext.java:721)

E/SystemServer( 156): at android.app.ApplicationContext.registerReceiver(ApplicationContext.java:715)

E/SystemServer( 156): at com.android.server.InputMethodManagerService.<init>(InputMethodManagerService.java:426)

E/SystemServer( 156): at com.android.server.ServerThread.run(SystemServer.java:276)

E/AndroidRuntime( 156): Crash logging skipped, no checkin service

I/SystemServer( 156): NetStat Service

I/SystemServer( 156): Connectivity Service

V/ConnectivityService( 156): ConnectivityService starting up

W/dalvikvm( 156): threadid=25: thread exiting with uncaught exception (group=0x4001e390)

E/AndroidRuntime( 156): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception

E/AndroidRuntime( 156): *** EXCEPTION IN SYSTEM PROCESS. System will crash.

E/AndroidRuntime( 156): java.lang.NullPointerException

E/AndroidRuntime( 156): at android.app.ActivityThread.getProvider(ActivityThread.java:4259)

E/AndroidRuntime( 156): at android.app.ActivityThread.acquireProvider(ActivityThread.java:4299)

E/AndroidRuntime( 156): at android.app.ApplicationContext$ApplicationContentResolver.acquireProvider(ApplicationContext.java:1513)

E/AndroidRuntime( 156): at android.content.ContentResolver.acquireProvider(ContentResolver.java:759)

E/AndroidRuntime( 156): at android.content.ContentResolver.query(ContentResolver.java:197)

E/AndroidRuntime( 156): at android.provider.Settings$NameValueCache.getString(Settings.java:499)

E/AndroidRuntime( 156): at android.provider.Settings$Secure.getString(Settings.java:1983)

E/AndroidRuntime( 156): at android.provider.Settings$Secure.getInt(Settings.java:2023)

E/AndroidRuntime( 156): at com.android.server.ConnectivityService.getPersistedNetworkPreference(Connectivit

Service.java:716)

E/AndroidRuntime( 156): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:494)

E/AndroidRuntime( 156): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:67)

E/AndroidRuntime( 156): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:455)

E/AndroidRuntime( 156): Crash logging skipped, no checkin service

I/Process ( 156): Sending signal. PID: 156 SIG: 9

I/ServiceManager( 124): service 'SurfaceFlinger' died

I/ServiceManager( 124): service 'batteryinfo' died

I/ServiceManager( 124): service 'usagestats' died

I/ServiceManager( 124): service 'clipboard' died

I/ServiceManager( 124): service 'entropy' died

I/ServiceManager( 124): service 'power' died

I/ServiceManager( 124): service 'telephony.registry' died

I/ServiceManager( 124): service 'netstat' died

D/HtcBootAnimation( 165): SurfaceFlinger died, exiting...

E/installd( 131): eof

E/installd( 131): failed to read size

I/installd( 131): closing connection

I/Zygote ( 128): Exit zygote because system server (156) has terminated

I don't really understand from that what's causing the problem, though. I can see it appears to be going through files in /data - is that on my ext3 partition on the SD card? Is it something there that's the issue? Perhaps clearing that would help, as Rashidi Zin suggested earlier?

[Guest masterpfa]

Do you have an ext4 partition, many of three ROMS only work with ext.2 or 3

[Guest Dr. dre]

How do I wipe the 'dalvik cache' ?

It's just written below the 'Wipe data/factory reset'

It should be written something like this 'Wipe Dalvik-cache' and this is necessary to wipe as you are moving from 1.5 to 2.1

[Guest davedontmind]

I plugged my phone into my Linux box, moved everything out of my ext partition, rebooted the phone, wiped, installed SenseHero, and this time it worked!

So I guess it was something in the ext partition that was causing the problem.

Many thanks to all who helped!

[Guest davedontmind]

It's just written below the 'Wipe data/factory reset'

It should be written something like this 'Wipe Dalvik-cache' and this is necessary to wipe as you are moving from 1.5 to 2.1

Not really an issue now, but interestingly I don't have this option on mine.

Edited May 4, 2010 by davedontmind

[Guest Musicmannetje]

This happened to me as well.. None of the 2.1 roms would go beyond the boot screen.

I did a wipe of the data and cache, but not the ext3..

Just to be sure: If i wipe the ext3 I loose my apps, right???

I'll try the linux workaround...

[Guest davedontmind]

This happened to me as well.. None of the 2.1 roms would go beyond the boot screen.

I did a wipe of the data and cache, but not the ext3..

Just to be sure: If i wipe the ext3 I loose my apps, right???

I'll try the linux workaround...

Yes, if you wipe the ext partition you lose your apps and need to download them again. You could always just do as I did and move the apps folder off to another machine, which would allow you to restore them after the upgrade.

However, there are several folders in the root of the ext partition, and you might be able to leave the apps one and just remove the others (I don't know, I didn't try).

What I did was write down a list of all the apps I'd got installed (quite a lot!), wipe the ext partition, upgrade to 2.1, then just re-install those apps that I really needed/used - it cut out an awful lot of crap! :P

The main problem I had was forgetting to backup my Note Everything database before the install, so I lost all my notes. Not a complete disaster but I had to restore the nandroid backup of my 1.6 ROM, run NE, backup the database, go back to 2.1, then restore the NE database. A pain in the bum, but not a catastrophe. So make sure you have backups of everything on your SD card, then copy the contents to another machine just to be safe :-) You can never have too many backups.

[Guest Svashtar]

Don't know for other ROMs, but with Villain 5 series it is normal that the phone "hangs" after the first boot.

When booted the second time, it should be OK.

Read Villain Forums (and others for that matter).

[Guest Wilkcos]

Not really an issue now, but interestingly I don't have this option on mine.

What version of Amon_RA recovery do you have in the lastest you should see under the wipe option:

Wipe data/factory reset

Wipe Dalvik-cache

Wipe SD:ext partition

Wipe Battery stats

Wipe Rotate settings

I always use the first three before a new flash and back up all my apps with titanium backup.

[Guest Musicmannetje]

You can never have too many backups.

You can say that again!! Thanks for the info, and to bad you had to restore 1.6 to get the NA data back.

I did a nandroid backup, including ext3 and wiped everything (a really scary moment!!).

Installed a 2.1 rom and Whoohaaa!! it worked!

I had used WaveSecure to backup the contacts and sms data so after installing WS, I could restore them both..

I restored the nandroid lateron and got my old familiar hero back.. It was just a 'dry run' for the final upgrade, but with the ext 3 backup on linux, i can rest assured that it all will go smoothly.

Thanx.

Patrick.