coderus | # 651 | 2013-10-31, 18:04 | Report

you dont need to flash emmc to get back to closed mode
you dont need to perform --erase-user-data
you can flash only fiasco image and you dont lose MyDocs data, userfs data including conversations, contacts and etc. (but lose all installed apps)

peterleinchen | # 652 | 2013-10-31, 21:38 | Report

He he, nice one


@coderus
But .aegis and .accounts are on /home (p3). They will not be deleted on 'just' flashing fiasco, right? So how to do then? Again need to delete these dirs? Or are they not created when booting up on closed mode, enabling developer mode and disable warranty warning. Flash back to closed and again open mode (would not be necessary according to your post)?

p.s.: maybe we should open up a new thread for this, as it seems that there is still not a full proven theory?

---

Last edited by peterleinchen; 2013-10-31 at 21:56.

juiceme | # 653 | 2013-10-31, 22:06 | Report

Good point... Maybe those are overriden when firmware is flashed? The flashing is not "just" flashing, as the APE might do other things as well, for example delete/modify files not on the flashed partition.

Well it should not be too difficult to test, just check the directories, content&timestamps, and then flash just firmware.bin and compare if anything changed.

Another indication should be if you need to re-enter passwords and account details after it...
Personally I have always flashed emmc+firmware if I needed to initialize the device, so I would not know...

coderus | # 654 | 2013-10-31, 22:17 | Report

just remove .accounts folder. its enough. as common user you will never get profit after removing aegisfs mounts.

peterleinchen | # 655 | 2013-10-31, 22:24 | Report

Mee too , that's the reason I asked again...

You mean remove contents of .accounts folder, not whole directory, right?
Personally I am running my device that way atm (having removed contents of folders .aegis .accounts and .activesync).

---

Last edited by peterleinchen; 2013-10-31 at 22:30.

juiceme | # 656 | 2013-10-31, 22:36 | Report

That works for the problem with user accounts and passwords, but there are other things that are left hanging.

I do not know exactly what is the reason, but these things affect especially unit startup when Harmattan is ran as 2nd level boot under ubiboot.
If the device is not correctly prepared, there's going to be a lot of process trashing in startup, and some devices / variants are more susceptible to this. In worst case it means that device will not boot, or will do so slowly or not every time.

If this procedure is done like I described, then this will not happen, the device will boot cleanly.

TMavica | # 657 | 2013-11-01, 01:41 | Report

After read, i decided to flash my n9 again..

traysh | # 658 | 2013-11-01, 02:49 | Report

Hi,

First, thank you so much for this marvelous piece of software. It is not only functional, it is pretty and makes not only N9, but open source software in general look better.

I installed it 2 days ago following the instructions in the wiki page, but it didn't work reliably. The simptoms were similar to the ones TMavica is reporting, but sometimes (< 10%) the system booted. So I found the post quoted above, and checked:

I never edited, chmoded or chowned these files, so this is how they were inside preinits.tar. The problem is not that the files belong to an inexistent user, but that preinit_harmattan is not executable. After fixing this, now I can boot successfully all the time.

Please fix preinits.tar!

Now I would like to edit the "info" menu option, can someone point me to a post/document/readme that show me the way?

Thank you so much again!

Edit: also, md5sum of preinit_harmattan is wrong in the wiki.

---

Last edited by traysh; 2013-11-01 at 02:58.

plourde | # 659 | 2013-11-01, 03:31 | Report

I flashed the plain open kernel and its booting fine, i added kernels and got nothing to boot at all, NITDroid wouldnt and no kernels for Harmatten would boot, i added the open kernel and even just letting the device go on its own to boot would just black screen and shut down as it appeared but I would need to hold power 8 seconds and then hold power again for it to reboot, I DID get the menu however and could see the OS's and when I had the phone plugged in to the computer on boot it did go in maintenance mode

plourde | # 660 | 2013-11-01, 04:27 | Report

I have never removed the openboot warning, could that be a reason why i can not boot any kernel? i am back to the openboot kernel and really want to get this working, I am not sure why nothing will boot