[SOLVED, BUT DON'T SHUT THREAD FOR NOW] Boot loop after "apt-get upgrade"
 

Put it straight - I previously had CSSU Testing, Kernel-Power 50, Kernel-BFS 10 and NITDroid 12 @ kernel 06-final1 running harmoniously, but after my school shut down its schoolwide WiFi I hadn't updated my wares for 2 total months... Then today I decided to update using "apt-get update" and "apt-get upgrade"(which is same as usual) via notebook-shared WiFi (through cable) and hell, it works fine and everything was updated. I remembered seeing a lot items like osso-xxxx (CSSU related?) but no else. Then I pushed "reboot" via power menu and phone rebooted to usual Multiboot menu, but whatever kernel I chose, the NOKIA logo appears, blackens (all usual) AND after 2 or 3 secs random colour notif. LED light pops up and phone reboots. REBOOT LOOP?! (I'm sure I'm fully charged)
Now stuck in a WTF condition - phone bootable, Multiboot enterable, system almost enterable, NITDroid working as usual (strange)... any way to reverse previous changes? Any way to solve this loop apart from flashing?

[SOLVED with rescue OS]

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

me too,,我的也是，哥们，拔掉电池等30秒再试下！

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

@Andy Yan
this happened with me too month ago and that is because of your /root directory is full i think the only way is reflashing and i hope not :D

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Aww shucks... I don't wanna reflash anymore... cuz a reflash kills 2 whole days plus a GB of data flow... Any other way?

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

http://talk.maemo.org/showthread.php?t=83939

See the above link. This caused a reboot loop for some people.

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

All right I see that post, but I don't know whether I'd updated that package that day (or ever installed that) AND even if I happen to know, there's no way to undo it in Android, right? I HAVE TO reflash, right?!

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

@AndyYan,

You don't happen to have backupmenu or recovery console installed?

With either of them you'd be able to replace the broken lib (libxau6).

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Don't even know what they are in the first place... So that means there's absolutely no solution?

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

dont do apt-get upgrade when devel repository enabled, unless you know and sure what are you doing, just saying, :)

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

http://maemo.org/packages/view/backupmenu/
http://maemo.org/packages/view/recovery-boot/

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

You probably do need to reflash. Backupmenu would have got you back to normal in just a few minutes.

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Okay... I'll be doing this later this week if no more solution found... Will be playing with my Milestone and soon-arrival, screen-broken Epic 4G...

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

One more thing. Will backupmenu back up ALL system's state into an image? So this takes lots of space and time? And I should do the backup every time before an "apt-get upgrade"?

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Try Backumenu and see for yourself. It is fairly quick and not that space-consuming. Yes, it saves everything

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

No, it's that I haven't installed that before everything went awol and now Maemo is unbootable, let alone any actions like deb installation... REAL QUESTION IS, CAN I FIX THE PROB UNDER ANDROID (NITDroid with root, can access /home and subdirs)?

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Got the self same thing a couple months back. Had to do a reflash, couldn't reflash normally by doing EMMC first then O/S because the N900 kept losing the connection, so ended up going O/S first; EMMC next and then the O/S again.

Haven't bothered with any custom kernels since.

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

If you can access /usr/lib directory of Maemo then you should be able to replace the two files with the older version:

/usr/lib/libXau.so.6
/usr/lib/libXau.so.6.0.0

Old version of package can be downloaded at http://repository.maemo.org/pool/mae...o1.1_armel.deb and you can extract the files listed from it. Good luck!

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

You could try the suggestion in this post (http://talk.maemo.org/showpost.php?p...&postcount=231) to boot back into Maemo to replace the offending file with the correct/original one.

I hope you get it sorted without the associated trouble of a reflash.

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Wow, so it seems R&D and lifeguard does what it should... Great idea, will be trying it tonight!

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

@AndyYan,

Just a theory: if you enable R&D mode and disable LG resers then the next time you boot the X server will most likely die (because of the bad libxau lib) and hopefully the phone will not reboot.

The problem is that you won't have a shell, or even a visible framebuffer, meaning you won't be able to even blindly type in the necessary commands to restore the working lib.

Try it anyway, and PLEASE report whatever result you get.

As an alternative, you might want to try putting the "Rescue OS" on a microSD card and boot from it using the flasher.
Link: http://talk.maemo.org/showthread.php?t=75369

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Tried both method.
The "Disable R&D + Lifeguard" gives no user interface, and I'm no blind operator. Anyway to enable UI or at least WiFi+SSH is welcomed!
Meanwhile I booted into RescueOS and WTF, there's no /home... USB Mass Storage is RAW format on Windows... AND no /usr/lib which means I can't replace the wrong lib even if I have the correct file!!
Any suggestions?

UPDATE: Mounting maemo rootfs in rescueOS gives me access to /usr/lib BUT NOT /home (ls returned empty results) so I'm still not able to put files (NITDroid can only access /home)...

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

This advice may be worthless, but don´t you have ssh installed on the N900, so you could use putty in combination with BackupMenu?

That should give you access to the whole device.

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

See, I haven"t got backupmenu installed previously. Or I shoulda solved this in no time...

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

UPDATE 2: Tried blind typing under R&D + LG-off, but with no UI present, it seems that I can't get over the "Disable offline mode" dialog (I use offline mode very often) because I imitated presses on the "yes" button and waited AND Ctrl-Shift-X and "root" and "reboot" and nothing happens...

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Using Rescue OS:

With this you can mount /home from USB. You *do* know that /home is an ext3 partition do you? (hint: use Linux).

Anyway, try putting the original libxau6 somewhere in your SD card, mount rootfs (you said you now know how to do that), and then overwrite the file (I think it's in /usr/lib).

Good luck. and read the documentation!

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

"Hint: use Linux" - You know I'm no Linux boy and I'm not gonna grab a Linux machine for this (I don't have one either)...
Put libxau6 in SD? The external? But isn't it that mount-maemo-root.sh only mounts a part of /(root dir)? Correct me if I'm wrong, I'm n00b on Linux...
If that script does mount the external SD then point out the path for me... Thx :P

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

No need to be a Linux boy, just google LiveCD, burn onto a CD, and boot from there. Shouldn't take more than ten minutes.

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Ain't no better if my notebook PC can read discs... BUT really my PC doesn't even have a disc drive!! WTF am I gonna do...

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

go to any internet center and flash it using thier PC's

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

I don't know or care if you're a "Linux boy" or not. Fact is /home is an ext3 partition so if you want to be able to mount it you either use Linux or find some driver/"app" that lets you do that on whatever OS you're using.

libxau6 should in the end go in /usr/lib, that's your rootfs partition. Since you're booting from an SD card and before that you cannot possibly access the internal memory of the N900, the most logical place to put the new libxau6 is somewhere on that card, and THEN once you've booted, copy it from the SD card to the /usr/lib directory of your N900 root partition (obviously, after you've mounted it).

Other than I have no other suggestion. You either do it or not. If you're not willing to do that ("no linux boy") then your only option is to do a complete reflash.. but beware, flashing may work better under Linux than Windows.

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Wait a minute. Why do you say rescueOS boots from external SD? For now I only know that I can use kernel and boot files stored on a Win PC along with flasher-3.5 to boot into command line... Even the rescueOS post AND documentation don't offer any booting method... Point out the right way for me to boot from SD pls

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

@AndyYan,

I thought you were booting the RescueOS from an SD card (using U-boot). Didn't realize it's not even documented. Sorry for that.

OK. In this case I guess your best bet is to, once you've booted RescueOS, enable USB mass-storage mode and then from your PC copy the new lib to the MyDocs partition (because you use Windows).

Then mount the rootfs and copy the lib from MyDocs to /usr/lib and then make sure it has the same permissions as the existing libXau6.

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Nice try dude, all of the methods was expected to work and I tried them yesterday already... But sorry facts:
1. As mentioned, USB mass storage appeared as "RAW" format in Windows, guess it's Linux format. I can put files under any folder under /home though with Android.
2. Mounting the rootfs gave empty /home. Mounting mmcblk1p1 gave almost empty /home. Mounting mmcblk1p2(which is said to mount /home correctly) reported errors.
3. Any way to acquire and mod permissions? I thought I've seen a command for that (Is that chmod?)

And thx very much for your patience and lasting help!

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Anyone can tell me how to mount mmcblk1p2 correctly in rescueOS? Thx

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

If you have a USB-stick (~600 MB), you can make a bootable one:

ISO-file from here:
http://spins.fedoraproject.org/lxde/

Installation instructions from here:
http://docs.fedoraproject.org/en-US/...USB_Media.html

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

According to the documentation using /rescueOS/mass-storage-enable.sh
should export both the /home (mmcblk0p2 on Maemo) and MyDocs (mmcblk0p1 on Maemo).

The /home partition is ext3, so WIndows won't recognize it. The MyDocs partition is VFAT so Windows *should* recognize it. When you do this, do you only see ONE single partition being exported as USB mass storage?

/home has its own partition, so within the rootfs partition /home is just an empty folder. The actual /home partition is then mounted "on top" of this empty folder.

About the "reported errors": you might want to post them here. It may help :)

/usr/lib/libXau.so.6.0.0 has (at least on my N900) 0644 permissions and is owned by root, group root.

Meaning, once you manage to copy the file (somehow) onto the /usr/lib folder of the N900 root filesystem, you would need to:

in case the libXau.so.6 symbolic link is not there, you do:

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Only one drive appeared in Windows and it's RAW. Dunno why.
You mean mounting mmcblk1p1 on top of /home? I previously mounted it on /mnt/free1... Any difference?
About the errors, yes I'm touching the PC later and will steal into rescueOS for another try and give out the error :-)
And thanks for your codes!

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

Booting from USB stick? Sounds cool, and it's a Fedora too... (I'll punch my Ubuntu classmate in his stomach FXXK YEAH)
Ok so this is a backup plan in case rescueOS won't work in the end... Thx

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

WHAT THE HELL!!! It worked!
And typed chmod & chown commands... WOOT! "Exit offline mode?" The system booted up steadily! Home sweet hildon-home!!!
Thank you Reinob for your PERFECT patience and knowledge of Linux!!

...Question is, when I typed "chown root:root libXau.so.6.0.0" it said "unknown user group root:root"... Doesn't bother booting but what's wrong?

Re: WTF - Boot loop after a normal "apt-get upgrade"
 

root.root, not root:root