I'm a bit angry right now and thought: maybe other T-BBS'ers also feel the way I do from time to time, so here's a thread for that sort.
The thing that brought it on:
A couple of days ago I bricked my phone. Well, sorta: I froze it in a boot-loop, where it boots quite like normal but before getting to a point where I can interact with it it re-boots and re-boots and re-boots and re-boots...
Sure, I brought it on myself (that's what you get for fiddling around with apps that are still in development
) and I know precisely what I did to get here.
Never having actually bricked the device before I had to go look up how to flash the rootfs.
This should be easy enough, I thought after reading about how it's done, and got started...
Right, easy isn't the word I should have used as I got some weird error-messages as a result -and had to go back to the forums to find out what those meant.
AH! -I'd been using the wrong flasher -no problem, just install the right one and do over, right?
Yeah, well, not exactly; that only gave me another weird error-message in the command-line window where I controlled the flasher:
Hmm, other people are bound to have gotten that before I did; back to the forum to look up that error-message...
Took me a while -looking through solutions until I found one that was for the Windows version on my PC.
Still got the same error. Back to the forum.
AHA! -it doesn't work when your device is connected to your PC through an USB-hub!
BUT: my frakking Acer PC has a lot of USB-ports and I have no idea which of them are actually connected to internal hubs.
Turns out: all of them!
I am now at a point where I've decided to go pay a guy in a phone-store to do it for me come Monday.
The thing that brought it on:
A couple of days ago I bricked my phone. Well, sorta: I froze it in a boot-loop, where it boots quite like normal but before getting to a point where I can interact with it it re-boots and re-boots and re-boots and re-boots...
Sure, I brought it on myself (that's what you get for fiddling around with apps that are still in development

Never having actually bricked the device before I had to go look up how to flash the rootfs.
maemo.org said:Rootfs is the filesystem that the root directory (also called ‘/’) is on. The N900 has a 256 MB OneNAND chip that is used for the rootfs, bootloader and kernel, together with a (slower) 32 GB eMMC flash that is partitioned as 768 MB swap space, 2 GB /home and 27 GB
This should be easy enough, I thought after reading about how it's done, and got started...
Right, easy isn't the word I should have used as I got some weird error-messages as a result -and had to go back to the forums to find out what those meant.
AH! -I'd been using the wrong flasher -no problem, just install the right one and do over, right?
Yeah, well, not exactly; that only gave me another weird error-message in the command-line window where I controlled the flasher:
Code:
Suitable USB-device not found, waiting.
Took me a while -looking through solutions until I found one that was for the Windows version on my PC.
Still got the same error. Back to the forum.
AHA! -it doesn't work when your device is connected to your PC through an USB-hub!
BUT: my frakking Acer PC has a lot of USB-ports and I have no idea which of them are actually connected to internal hubs.
Turns out: all of them!

I am now at a point where I've decided to go pay a guy in a phone-store to do it for me come Monday.