yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] psxsnake:
i have some problem to understand how install 5.9 on multirom, I'm still on CM11s as primary and 5.5 as secondary... can I update to 5.9 on secondary as usual or I have to do something before?

and if I want use temasek CM12 as primary, what i have to do?

thanks
[ONE Android Development] brunes:
Tried to upgrade to v5.9 Sabermod 3P from first post. It does not boot, crashes out of the boot after 5 seconds and back into recovery. Yes, I have flashed the bootloader update (a couple of times now)... any ideas how to troubleshoot?

EDIT: Also, I find with this ROM I am often getting symlink failures while flashing. I then need to flash it again.

PS: Has anyone ever heard of any ROM mods that let you totally disable the boot screen animation so that you can see boot messages? It has always driven me insane when trying to troubleshoot issues that Android doesn't allow you to see the boot messages. logcat on boot does not always work.
[ONE Android Development] tobitege:
[MENTION=377318]brunes[/MENTION]: install LiveBoot by [MENTION=631273]Chainfire[/MENTION] to see rom boot messages. But that requires the kernel to boot up, of course. For kernel errors only kmesg logs can be of value.
[ONE Android Development] azsl1326:
Same thing happens to me on Linaro 2p v5.9. Nothing I tried worked.
[ONE Android Development] :
Same problem, I reboot into recovery and I have these error messages. I am trying to install the 2p, both versions of 5.9 do this. I am running TWRP modified 2.8.4

E: Mount: unable to find partition for path '/sdcard'

E: unmount: unable to find partition for path '/sdcard'

E:Mount: unable to find partition for path '/sdcard'

E:TWFunc: : Copy_Log -- can't open destination log file: '/cache/recovery/log'

E: Datamanger : : Output_Version – unable to make /cache/recovery
[ONE Android Development] krxz:
I tried to update yesterday. Dirty flashed 2P version. Endet up in an encrypted phone. Dunno why that happened but i had to format userdata via fastboot and had to reinstall clean
[ONE Android Development] fabryx92:
Same thing happend to me
[ONE Android Development] MrPhilo:
3P Bootloop :(

Anyone got a clue whats going on? It hasn't worked since v5.5
[ONE Android Development] zaphodbeeb:
Dirty flashed fine for me. Did u wipe cache, dalvik, have u got the latest firmware?
[ONE Android Development] f41lbl0g:
After formatting my /cache and /data to f2fs, I installed temasek as my primary rom. Now, when I try to go boot to multirom recovery, it crashes. I've tried searching but nobody seems to have this problem. Are there people that have multirom recovery not working with 2p f2fs temasek, or is it just me?
[ONE Android Development] phermey:
i have been using smint's 5.9 for the last couple of days with no issues on a dirty flash. i think zaphod has been messing with it (rom) in order to get it to boot on any type of partition set-up. i am not going to speak for him, or step on any toes, but it seems as though this might be the problem. of which.... i have no doubt he will get it fixed. in the meantime... you can use the ones smint has uploaded. and be sure to give the guy a thanks. links are in his sig. and his last posts were on the previous page.

hope this helps.
[ONE Android Development] phermey:
[MENTION=3874152]zaphodbeeb[/MENTION] [MENTION=4877142]tobitege[/MENTION] [MENTION=4164878]smint86[/MENTION]

maybe one of you guys can help me out here. so i installed the android kitchen. i installed notepadd++ (edit the fstab and updater-script), and went through the process. for some reason things will not geehaw when i flash or sideload. so let me take you through my process right quick.

things to note: windows xp and winrar for zipping. in zaphod's post.. he sid to double click on the updater-script and it would open. all i can get it to do with winrar is 'view'.

1 extracted boot.img from winrar into boot-tools

2. unpacked with the batch

3. replaced code with notepad++ and saved.

4. repacked and cleaned.

5. added boot.img back in with winrar

6. could only view the updater-script. so i extracted with winrar to boot-tools.

7. pasted the two lines of code (2p) unsing notepad++.

8. saved and added back in with winrar.

9. could not profit.

i got a real quick installation aborted when flashing. and when sideloading... it said 'comparing TZ blah blah with TZblah blah'. the script suceeded, but was stuk on 1+ screen.
[ONE Android Development] smint86:
For now I can't see what's going wrong. I got no windows system, but what you've done looks right. You could try to use 7zip as archive tool, it's open source and I was always happy with it back in my windows days. But it should make no difference imo. Which AIK version did you use? Did unpacking/repacking boot.img go through without errors?

Besides that, I'm gonna drop 2P v6.0 ln/sm later today. Using the “old“ fstab layout, because for me there haven't been any problems using it so far.
[ONE Android Development] krxz:
Yes, yes and yes. I dunno why that happened. After the clean flash now everything works flawlessly. But now I am afraid of having trouble again when dirty flashing next time :D
[ONE Android Development] fabryx92:
I had got the latest firmware but i didn't wipe cache and dalvik. I ever do the same things to update this rom and no problem previously occured.
[ONE Android Development] phermey:
i stuck 7zip in last night, and then got busy doing things around the house. i will go ahead and give it a shot when i get done here. my pc is hooked up to the tv, so i don't read things much. all i saw was the bottom line said press any key. this time though i will sit closer and read. i used the v2.0 win32 version of the aik. if all else fails... i will figure out how to slap ubuntu on this chromebook and do it that way. i will not be defeated.

Thanks for the response.

---------- Post added at 07:42 AM ---------- Previous post was at 07:14 AM ----------

it is doing the same thing with 7 zip. i am going to go to the aik thread and go from there.
[ONE Android Development] smint86:
Temasek v6.0, 2P F2FS-mixed, linaro & sabermod:

https://www.androidfilehost.com/?a=show&w=files&flid=24578

If not done already, flash bacon_firmware_update_2015_01_23.zip prior to flashing the ROM.
[ONE Android Development] f41lbl0g:
To clarify, I'm having an issue with the multirom twrp, not the rom itself. Regular twrp works fine, but only after flashing philz, which also works. As soon as I install multirom twrp, and I boot into the recovery, it stays at the TWRP logo for a while, then reboots, giving no access to the recovery. The rom works fine. This only started to happen after I formatted /data and /cache to f2fs and used the 2p version. I will try smint's version, but I don't think it will solve the problem.
[ONE Android Development] tobitege:
[MENTION=5775439]f41lbl0g[/MENTION]: already updated today's MultiRom recovery update through MultiRom app?
[ONE Android Development] krxz:
Can I flash smint build over zaphod?
[ONE Android Development] DominiCOne:
Yes ,i think i've flashed smint 5.9 over zaphod 5.5 & had no problem..on my way to flash the 6.0
[ONE Android Development] krxz:
So it happened again. Flashed v6.0 over v.5.9 and got encrypted again. I really have no clue why this always happens
[ONE Android Development] f41lbl0g:
Today's multirom update fixed the issue. I am happily back to TWRP! Thank you for the tip.
[ONE Android Development] brunes:
The problem I have is smint has no 3P version. I have a ton of stuff on my phone and am somewhat "tired" of constantly having to re-build it so really don't want to re-build it as a 2P version. I also can not root my phone due to work software (every time I flash I actually have to use TWRP to manually delete the "su" binaries before booting....) and thus can't use backup-restore apps easily. This is also why I dirty flash in the first place. Really hoping the issue is fixed in zaphod's 6.0 when 3P is posted.
[ONE Android Development] papajonpizza:
I was able to dirty-flash zaphodbeeb 2P over 3P. I made nandroid, first. Formatted /system as EXT4. Installed zaphodbeeb 2P. No wipes.

I think one or 2 settings were lost. No problems whatsoever and still running it now v.5.5 (also an upgrade from my 3P v4.7 version). Still waiting to dirty-flash the next upgrade as I'm seeing reported issues on the main Temasek (katinatez thread) of wifi.
[ONE Android Development] phermey:
so i stuck ubuntu on my xp machine and managed to convert the 6.2 rom. using ubuntu... i actually read the guide line for line instead of skipping the 'bash unpackimg.sh' part. had i read that section i would have seen that i needed to delete the boot image and rename the new boot. go figure. at least i have ubuntu on my machine now. :victory
[ONE Android Development] phermey:
smooth sailing for the last six hours. 2p sm 6.2.
[ONE Android Development] smint86:
Thanks for sharing your build :).

In addition: smint86-temasek-bacon-ln-6.2-2P-f2fs.zip

Added v6.2 2P Sabermod as well, as I already built it before seeing that [MENTION=4584934]phermey[/MENTION] shared his, also want to be up to date in my folders, just in case.

Also, is anyone willing to test a 3P version (Linaro & Sabermod available)? Added two folders at AFH (check my sig) or here: https://www.androidfilehost.com/?a=show&w=files&flid=24578

ATTENTION: 3P are TEST releases. It could be possible, that flashing them results in a bootloop. So make sure you did a nandroid you can fall back to. You've been warned ;). 2P versions should be safe, though. Running 2P Linaro on my own, without problems.

[MENTION=3874152]zaphodbeeb[/MENTION] told me that there are problems with 3P since v6.0 (v6.2 also), so we'd like to try to break it down. We'll see... if anybody is willing to test.
[ONE Android Development] mmcneil:
Quick question for the F2FS users; What kernel are you using? I usually run Sensei because it has the pegasusQ governor, but I wanted to see if there were and other recommendations. Thanks.
[ONE Android Development] smint86:
I'm using [MENTION=3685904]ak[/MENTION] kernel, as I'm fallen in love with the msm_mpdecision hotplug (aka bricked, originally developed by [MENTION=4195844]show-p1984[/MENTION]) :D.
[ONE Android Development] phermey:
i mostly run ak. between it, tyr, green, & stock cyan... it seems to be the fastest from touch to loaded when an app is cached. i sometimes remember to load the special edition ukm that goes with it.
[ONE Android Development] tobitege:
[MENTION=4164878]smint86[/MENTION] [MENTION=4584934]phermey[/MENTION] [MENTION=3874152]zaphodbeeb[/MENTION]

I've been using Beyond Compare to compare a previous zaph 5.9 2P boot.img with the correlating one of [MENTION=4164878]smint86[/MENTION] builds and can't see any obvious reason/difference (for me as a layman wrt linux) that would cause boot issues, unless the "init" (within boot.img) or the updated mk2fs has "problematic" changes (wild guesses).

Unfortunately, my phone is full with 40+GB and I don't want to redo it all over for F2FS. :silly: I wish it came with external SD card... :D
[ONE Android Development] krxz:
Has anyone tips for updating so that I won't get encrypted AGAIN?? :d
[ONE Android Development] phermey:
you are dual booting right?
[ONE Android Development] krxz:
Nope only primary rom. I wipe cache/dalvik, flash rom, flash ukm and ak kernel and bam, result is encrypted phone. I am scared now to update :D
[ONE Android Development] phermey:
hmm. wierd. k. so to be clear. you are data/cache-f2fs. system on ext4. using a 2p rom. coming from a 2p rom. or all f2fs using a 3p rom. coming from a 3p rom. you were using philz to convert. and when you clicked on yes to install... it said 'yes - convert /data to f2fs' etc.

when i had the problem it was because my partitions were still formatted wrong. or i didn't sideload the rom, or something. but once i got it done right... it has not happened again. and i have flashed a dozen or so times since then. hope this helps.
[ONE Android Development] krxz:
I have /system ext4 and cahe/data on f2fs. Using 2P. Was initial on zaphod version, then switched from 5.5 to 5.9 to smint. Got encrypted. Then flashed 5.9 zaphod over 5.9 smint. Again encrypted. I have doubts on philz recovery. I like twrp vetter but with that i didn't get the partitions right

Now I am on 6.0 smint and downloaded smint 6.2
[ONE Android Development] mmcneil:
Thanks to you both for responding. I used to run ak exclusively, but never on the F2FS builds. I'll give it a try. Thanks again.

Mike
[ONE Android Development] smint86:
Maybe try [MENTION=3814731]katinatez[/MENTION] unofficial TWRP 2.8.4.1: https://www.androidfilehost.com/?fid=95916177934517315

Worked fine for me, being on 2P f2fs since v4.2 or so, always dirty flashed. In the beginning versions by [MENTION=3874152]zaphodbeeb[/MENTION] then by me (which are almost the same in the end).
[ONE Android Development] tobitege:
I think TWRP is due to its more recent development more up-to-par with partitions and encryption headers inside of it. It could well be, that Philz screwed up partition sizes and now the current CM firmware doesn't work right with it.

Reference: [MENTION=912474]Dees_Troy[/MENTION]'s G+ post: https://plus.google.com/113698630295260555736/posts/RLktBGSCr7m and his comments for it (Jan 16th, 2015).
[ONE Android Development] krxz:
Thanks for your help. But when I now switch to twrp, do I have to repartition again? :/
[ONE Android Development] tobitege:
That's a good question, might be the safest way to go. :fingers-crossed:
[ONE Android Development] krxz:
Well I changed to twrp and ckecked file formats. System is shown as ext4 and both data and cache are f2fs. I think I will try it. Wish me luck :D
[ONE Android Development] tobitege:
*wishing you luck* :D
[ONE Android Development] phermey:
no word from [MENTION=3293392]krxz[/MENTION]. i hope that is a good thing.
[ONE Android Development] katinatez:
I agree philz recovery is outdated, going to update recovery with new f2fs commits. There is a boat load of f2fs commits philz recovery is missing. But as far as encryption it has never supported that, I remember talking to Phil3759 about this at one time.
[ONE Android Development] krxz:
I am sorry for taking so long but it worked :) just flashed rom, let it boot abd then flashed ak. All fine now thanks to you guys and twrp
[ONE Android Development] zaphodbeeb:
Hi thanks for producing the 3P test version. Its exactly the same as the version I produced, and, on my device at least, causes exactly the same problem. Bootloop. I think its a kernel problem. fstab settings are also exactly the same. The updater-script looks good to me and shoud work. Thanks for your help though. Appreciated.
[ONE Android Development] tobitege:
[MENTION=3874152]zaphodbeeb[/MENTION]: what if you replaced the boot.img in your archive with the one from [MENTION=4164878]smint86[/MENTION]'s archive? Or just replace the "init" from inside it.

Curious if this could be further tracked down as there are so little differences, seemingly (to my old eyes).
[ONE Android Development] smint86:
What makes me wonder, is why 2P works just fine and 3P doesn't. We need to hunt it down. If it flashes correctly, I don't think it's about the modified updater-script. So it should be about the modified fstab, for some reason the kernel doesn't seem to like it anymore? Is it possible to grab logs from the booting process? I'm not so much into it, but shouldn't it be possible to start

adb shell cat /proc/kmsg > /sdcard/kmsg.log
adb shell dmesg > /sdcard/dmesg.log

while booting (as early as possible), and then end it via ctrl+c? Maybe someone can help out. Unfortunatly I'm not abled to test as well, as I don't have the time to reformat system atm and I need the phone available almost all the time, because I'm moving flats and so on...

ps: Found that it could also be needed to perform commnands like this:

adb shell su -c "cat /proc/kmsg" > /sdcard/kmsg.log
adb shell su -c dmesg > /sdcard/dmesg.log
[ONE Android Development] phermey:
glad to hear it worked out for yah.

[MENTION=4164878]smint86[/MENTION] - i can format the system and give it a shot for the day. i need to put your version on correct? or should i see if i can get zaphod's to work? or both?

edit: nm. zaphod took his 6.0 down.

edit2: well i guess philz is completely broken now. i could not get it to commit to the system conversion. it worked on 5.9... as i was on the phone with that technocrazy kid getting it done when twrp would not.

it would say 'formatted /system - ext4 after it was done... but it (read: ext4/f2fs) was never up on the no/yes/no. so after trying to flash the 3p rom several times, formating to ext4 half a dozen times with rebooting to recovery etc...i finally flashed the 2p rom back on and it booted with no issues. anywho...i will shut up about philz :P: and will be sticking on twerp asap.
[ONE Android Development] zaphodbeeb:
Hi,

I dont think Philz is the problem. I get the same result with a 3p version on both twrp or Philz. Infact I get some strange formatting results on twrp which result in the phone not getting past the boot logo, until I reflash philz and reformat.

The 3P problem also occurs using the tyr kernel, so I suspect that there is a common problem. Katinatez has advised it could be releated to any one of 7 recent commits. Im on a very limited availability at the moment, but will try to get some more time to investigate this further tomorrow morning. Progress of sorts....
[ONE Android Development] zaphodbeeb:
I hve limited time but will set up a recovery log to run tomorrow to see what that reveals. As per my previous post, the problem is not only limited to this kernel, as Tyr also has a problem in 3P configuration on the rom.
[ONE Android Development] tobitege:
Ok, don't bash me for another theory here: we haven't yet ruled out, that the "newest" firmware is causing issues, because with the current decryption issues I'm speculating, that the QCOMM bootloaders may have changed and interfere with partitioning/formatting... BUT that's just a freaky thought that I couldn't keep in... :D

I'm not a Linux guy, but aren't there tools which could tell us the exact partition sizes (e.g. in bytes) before and after formatting in either TWRP or Philz, especially the /cache partition(s) since 3P has issues?

I better stop hurting my brainzz....
[ONE Android Development] katinatez:
I had pm zap about this, I have merged kernel commits twice. The first merge there is a kernel commit that checks which firmware you are on, that's when all the trouble started with f2fs thread. Now last nights kernel merge (which was the last 7 commits) now does a file system check. Start taking recovery logs to see what I am talking about. Both Philz & TWRP are capable of logs. Recap v6.0 -v6.2 checks firmware. V6.3 now checks firmware & file system. All this is cm kernel commits. I to am pressed for time, f2fs users find the culprit commits and I will revert them in kernel but don't know what the consequences will be. For better or worse.
[ONE Android Development] phermey:
i have the primary-6.3-sm-2p rom booted. runs like a champ.

Gratz on the RC [MENTION=2538833]katinez[/MENTION].
[ONE Android Development] tobitege:
[MENTION=4164878]smint86[/MENTION] [MENTION=4584934]phermey[/MENTION] ... are you guys by any chance using MultiRom with your F2FS builds? Just curious.
[ONE Android Development] phermey:
i am not. i guess i should be sure to mention primary when i link.
[ONE Android Development] tobitege:
Just a little anecdote(?):

My last F2FS install was a couple of weeks ago, but with MultiRom and zaph's build at the time as primary.

It all worked, but the funny thing was, that backing up the primary indeed created "f2fs" nandroid files (like "data.f2fs.win000").

The secondaries, which were "regular" roms (no extra f2fs touch-ups), installed and ran fine too, though.

But backups always created nandroids as ext4 files (like "data.ext4.win000"), even though all partitions were F2FS.

Now, I assume that it worked as expected, since the nandroids are surely the same file format and the extention just came from fstab or something.

But I was a little surprised at first. Learning new stuff every day (especially since I'm not a Linux user). :)

/OT
[ONE Android Development] krxz:
Whose build is this? Smint?
[ONE Android Development] phermey:
that's pretty neat. have you seen the reddit guide that was posted the other day on coding apps? here.

---------- Post added at 04:29 PM ---------- Previous post was at 04:28 PM ----------

i uploaded it. same thing as what smint would put up.
[ONE Android Development] tobitege:
Doing software development for 20+ years, but Android scares me... lol... thanks, bookmarked it for tomorrow. :)
[ONE Android Development] katinatez:
Wow! This is where I am blown away! If your ready to convert pm me? I have tried about a dozen distros, before I settled with Arch linux.
[ONE Android Development] zaphodbeeb:
I dont think this is a kernel problem, else flashing AK, or another kernel would fix the problem. It doesnt. Assuming that the updater-script is correct, and that there is no other non kernel component of the rom that could cause the problem, I think its most likely to be a firmware related problem.
[ONE Android Development] katinatez:
All kernel devs merge with cm kernel repo. Take a look at their repos and check if they are few commits behind or caught up with cm. I may be wrong but i am just saying that I recently merged twice with cm kernel repo.
[ONE Android Development] phermey:
here is the 6.5-ln-2p primary build. saber is not out yet. where i found 6.3 to be laggy once i got back to it... this one seems to be a bit of a boss. getting 'fast and smooth' comments on katinatez's thread. unread count is turned on in notifs. and i am seriously digging the new wallpaper that comes up.

katinatez said the saber will be out later on. but i don't really see a need in uploading it. maybe zaphod or smint will if they get on today.

EDIT: Lock Screen Gestures are Working! Woot! no V for flashlight yet.

hit 49,411.
[ONE Android Development] smint86:
You became fast :). It's now also ready in the folder in my signature. I think I'll add Sabermod as well, as soon as it's released and I got time. Still no progress with f2fs-all unfortunatly, that's why I won't make versions of it. I don't think [MENTION=3874152]zaphodbeeb[/MENTION] will as well.
[ONE Android Development] tobitege:
[MENTION=1228651]fusionjack[/MENTION] mentioned recent commits which also caused SlimSaber to no longer work with F2FS and I was wondering if similar commits exist at all in Temasek, but I'm not good in navigating repositories... yet. :p

Here's his post: http://xdaforums.com/showpost.php?p=58511209&postcount=4639

Referencing this code commit:

https://github.com/SlimSaber/android_system_core/commit/607135c633ccfcfd2abcac079cf2992b53ad2844
[ONE Android Development] katinatez:
Nice find will revert this commit on SaberMod since I have not built it yet.
[ONE Android Development] smint86:
For me, github is very difficult as well. I never learned all this stuff at school but learned all by myself, starting with pyramid (june '11). Bacon is my second android now, it's getting better but still difficult. Especially because I'm still a newbie in reading and understanding code. But it makes fun to learn, time is my only problem :). If someone knows useful tutorials, I'm always in for ideas (if you got some good stuff in german [MENTION=4877142]tobitege[/MENTION] I'd be even more happy, but english is fine as well :D).

Nice find with the commit, [MENTION=3814731]katinatez[/MENTION] if you revert it in v6.6, I'll build another f2fs-all test version (if nobody else is faster).
[ONE Android Development] katinatez:
Yup temasek repo has this commit fusionjack mentioned. Take a look

https://github.com/temasek/android_system_core/commit/d1bec30dacc7435ed75a4429c21c12057d754f02