yashsingh1/xdaforums huggingface dataset:
[Xposed General] KevinX8:
Well you still haven't specified the device so it's really hard to find any info to help you. Whatever Manufactuer maintains your device is really strange as they have stayed on android 4.3 yet they still provide updates. Most devices running stock 4.3 ot lower have not gotten an update since the release of the device
[Xposed General] Portgas D. Ace:
Security updates differ from ROM updates (Android version update).

BTW: a solution for OP has already been posted in post #2.
[Nexus 6 Q&A, Help & Troubleshooting] symbiansucks:
I am having random reboots on my Nexus 6 running Pure nexus (android 6.0) with lean kernel (both latest versions). This is very annoying as the phone randomly reboots after playing a certain notification sound ( which i don't know is caused by what).

I am attaching both logcat and ramoops. Anyone please help me know the cause?
[Nexus 6 Q&A, Help & Troubleshooting] symbiansucks:
new files

Here are new files attached after a fresh random reboot
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
the fatal system error is caused by the app Landroid.
[Nexus 6 Q&A, Help & Troubleshooting] Yoinx:
There was a modification to the sound drivers recently that apparently causes RR's when playing sounds. BuckMarble had pointed it out, if Imsoyeon merged it and hasn't reverted it yet... that might be your issue.
[Nexus 6 Q&A, Help & Troubleshooting] symbiansucks:
I think I have found the cause. It was due to life360 app which I have uninstalled and now I haven't had a reboot in 10hrs. Let's see if it is actually the cause
[XDA Assist] :
please help me out....
[XDA Assist] OfficerJimLahey:
Hello, and welcome to XDA! :cowboy:

As long as this is on the up-and-up, there are two situations I can think of:

ADB was turned on and recognized with a PC before password was forgotten. In that case, connect the device to the same PC and run "adb devices." That will determine if you can start pulling files.

Bootloader was previously unlocked (or you have a device that unlocking BL does not wipe device). In that case, you can load (flash or preferably boot) a custom recovery and then use ADB to pull files.

If the device is Samsung, option two will be different, as it does not have a fastboot mode. I cannot remember if you can flash a custom recovery through Download Mode and not wipe your userdata. I imagine they would have patched that hole by now.

This may give you some options, even if not for your device:

> Samsung Galaxy S II I9100 > Galaxy S II Q&A, Help & Troubleshooting > [Q] forgot pin - can I avoid hard reset? SOLVED

The thread is getting quite old (and probably not for your device), so I don't recommend posting there.

You can ask followup questions in this thread (once you have an account):

> General discussion > Questions and Answers > [HELP THREAD] Ask ANY Question. Noob Friendly.

Hope this helps, and good luck! :)
[ONE Q&A, Help & Troubleshooting] dendi:
hey i just flashed the boeffla kernel on stock rom and its running pretty good !

although UNDER MISCELLANEOUS 1 ,, first option SYSTEM TWEAKS

can anyone tell me what does that option do exactly and to which do i set to it ?

there are 3 options : Boeffla tweaks,, speedmod tweaks and Mattiadj tweaks ! can someone help me out with this ?
[ONE Q&A, Help & Troubleshooting] Phantogenic:
If you have the kernel and app installed you would have been to Lord Boeffla's download page. All the info and links are provided. The man is nothing short of thorough in what he does.

TLDR - http://www.boeffla-kernel.de/index.php/kernel-settings
[iPAQ rw6828, XDA Atom Software Upgrading] Emad_d_37:
I have 02 Xda atom exec withe rom 200607181wwe i have tray and downlowd many rom form xda-developers.com iny rom i wont to tray on my mobile give me error ****ry code i dont know haw to solve this brablem and today i have dawnloade this vargon ATOMWM603WWE and give the same error haw i can solve this brablem pls. hape

thanks.
[iPAQ rw6828, XDA Atom Software Upgrading] ironeagle:
ATOMWM603WWE is for ATOM only not for ATOM EXEC

AKU 3.3.2b is the only cooked ROM available for ATOM EXEC .. See thread http://xdaforums.com/showthread.php?t=321286
[K3 Note General] sandeep.sethi:
Good guide but if the roms support sdcard as default storage then its worth dual booting
[K3 Note General] 911-Future_Maker:
Congrats for this great tutorial my friend! :) I'm sure it will help many peeps having questions around. Also thanks for mentioning me in the credits. :P

---------- Post added at 18:34 ---------- Previous post was at 18:30 ----------

Why? You can dualboot no matter what's your default write disk. You must just have enough free space. Using 4 roms currently, my default disk is internal storage and my primary rom has a tons of apps installed. Btw [MENTION=5450421]sandeep.sethi[/MENTION] I'm having problems trying to dualboot your latest AICP rom. :laugh: 5 fast vibrations and back to recovery.
[K3 Note General] sandeep.sethi:
4 roms ? are they all vibeui based ??

whats ur internal memory space left

---------- Post added at 10:10 PM ---------- Previous post was at 10:06 PM ----------

i dont know bro maybe space is interferring it
[K3 Note General] 911-Future_Maker:
Of course, screenshot attached. ;) Unfortunately only around 500MB free internal storage.
[K3 Note General] sandeep.sethi:
its the problem

internal space will be less available
[K3 Note General] 911-Future_Maker:
Wait! That was an old shot my bad. The one attached below is representing my current usage. I'm using BlissPop, it's a monster. :)

Interestingly enough I'm same person with the guy who's using the niklabs username [MENTION=5344025]needrom[/MENTION]. lol:D Nice to meet you mate.:highfive:

To be honest 4 roms are overkill, 3 roms can serve me just fine.
[K3 Note General] TheDarkKnight:
Thanks.

Thanks. You are welcome [emoji6]
[K3 Note General] sandeep.sethi:
nice to meet you too
[K3 Note General] Pradeepnegi:
failed to flash zip

Sir I'm not able to flash zip. I'm getting error. Image is attached below. Please help
[K3 Note General] TheDarkKnight:
Which is your ROM??

It's because of the ro.build.product of your build.prop
[K3 Note General] 911-Future_Maker:
This is easy. I'll guess you're installing MIUI or CM right? Because these roms usually contains this limitation about "hermes" only devices. Just open the updater-script which can be found in META-INF/com/google/android path, open it as text via some root file manager and edit it removing the following lines:

getprop("ro.product.device") == "hermes" || abort("This package is for \"hermes\" devices; this is a \"" + getprop("ro.product.device") + "\".");

Success.
[K3 Note General] 911-Future_Maker:
Hey [MENTION=5207461]Salman A.[/MENTION] bro I have a little update on your question about that can we install a VibeUI on extsd-slot or in any other slot different than primary. Good news - it works like a charm, screen attached from last night when I was again playing with flashing roms on my phone lol. :D

Installed VibeUI_1604_ST on extsd-slot all working, I just edited the updater-script to prevent boring errors like that one above removing these line:

getprop("ro.product.model") == "Lenovo K50-t5" || abort("This package is for \"Lenovo K50-t5\" devices; this is a \"" + getprop("ro.product.model") + "\".");

So now running VibeUI from my extsd card lol, I flashed it just to confirm it's possible, but I think I'll wipe it and flash it again as primary because I mostly play games on VibeUI and I don't want to run a heavy game from my extsd while the entire phone system is also running from the card. It will slow down the things. ;)

Meanwhile I still can't make the AICP rom by sandeep a multiboot ready. :( Sometimes it hangs at the logo, sometimes vibrates 5 times and reboots back to recovery. I posted at the dualboot thread and really hope that Chen will help me.
[K3 Note General] TheDarkKnight:
That's great! I'll try out the MM ROM then.
[K3 Note General] 911-Future_Maker:
Wait! I forgot to mention that I also tried VibeUI_1606 from needrom and it while it had instaled fine it doesn't boot! :( Got stucked at the logo... I don't know for the other MM roms, you may want to try 1605 as I already tried 1606 and as you can see without success. So may be no multiboot for MM for now...if you have enouh space on internal you may try and report. So the bottom line:

VIBEUI_1604_ST Android 5.1 is working

VIBEUI_1606_DEV Android 6.0 won't boot.
[K3 Note General] panchalgl:
Phone: Lenovo K3 Note

ROM: 04_K3_NOTE_5.1_1604_STABLE_ROW_004_CUOCO92

Kenrnel fix successful but in primary ROM While updating ram disk it gave error

log file attached

Please help
[K3 Note General] 911-Future_Maker:
Using the latest Dualboot 2162 build with the VibeUI_3.1_1606 - can't update the ramdisk and also not indicating that the primary rom is the currently running.

I still can switch to other rom via the utilities zip so for now it's a compromise that I chose to make.
[K3 Note General] Pradeepnegi:
Now I have installed k3 note mm 6.0 ui 3.5 dev 1605 row cuoco92 as the primary ROM.

And again same error I m having. But now it is saying this device is aio otfp m. Please help. Even I m not able to update ramdisk.
[K3 Note General] Pradeepnegi:
Sir where to find this folder meta inf
[K3 Note General] TheDarkKnight:
In the ROM zip.

You have to change ro.build.product to aio_otfp without _m in your build.prop. If you are still trying that zip, you will still have to edit the updater-script. My advice, don't use it. That's very old. Try the new CM 12.1 Beta 3
[K3 Note General] Pradeepnegi:
updater script is not having those lines. and where to find build.prop.
[K3 Note General] TheDarkKnight:
Give root permission to the file Explorer you are using and navigate to /system/
[K3 Note General] Pradeepnegi:
Primary ROM is not even updating kernel and ramdisk. Why so ?

---------- Post added at 08:54 AM ---------- Previous post was at 08:49 AM ----------

I changed ro product device to aio_otfp in build.prop but still I m not able to update ramdisk and kernel of primary ROM.

---------- Post added at 09:00 AM ---------- Previous post was at 08:54 AM ----------

I got this error after changing ro product device name to aio_otfp . when I tried to flash another ROM this was the error.
[K3 Note General] TheDarkKnight:
Are you having the 6.0 ROM? Maybe that's the reason. Try in LP.
[K3 Note General] Pradeepnegi:
Yes it is marshmallow by cuoco92.. means i should have lollipop as my primary ROM , whether it is any rom built on lollipop ?

Now I have miui7 as primary ROM. But when I tried flashing rom 6.0 by cuoco92 using twrp recovery. It gave the binary zip error.
[K3 Note General] TheDarkKnight:
Yes. LP as primary.

So now you can set kernel and update ramdisk?? You should probably edit the updater-script.
[K3 Note General] Pradeepnegi:
Yes now I can update ram disk and set kernel successfully but still got the update binary zip error. Please tell me what to do with the updater script ?
[K3 Note General] TheDarkKnight:
Open it with Notepad++. The complete instructions are available on the Index thread. 2nd page.
[K3 Note General] Pradeepnegi:
Are you talking about removing ro.built. ....... Type of lines from updater script. Because it didn't work. And not all ROMs are having those lines. .

Can I make 6.0 mm as my secondary ROM ? While having lollipop as primary. ?
[K3 Note General] TheDarkKnight:
No. In the updater-script in META-INF folder in the ROM zip.

All Vibe UI ROMs should have it.

Haven't tried. But it should work..
[K3 Note General] TheDarkKnight:
Here's an edited updater-script for Vibe UI 3.1 6.0 1606: http://xdaforums.com/showthread.php?p=65235852

Thanks to [MENTION=5048731]911-Future_Maker[/MENTION] for this. All you have to do is replace it with the one in the ROM zip.
[K3 Note General] Pradeepnegi:
Can I use it to replace script of k3 note mm 6.0 ui 3.5 dev 1605 row cuoco92 ?????

Every time I try to flash secondary ROM, it says update binary error. ? Why
[K3 Note General] TheDarkKnight:
Try it. Also try flashing to a different slot. Extsd-slot, for example.

It should be because of the updater-script.
[K3 Note General] 911-Future_Maker:
An update binary error is usually indicating a problem with the updater-script. I don't recommend using the 1606 script for installing a 1605. It might work, no guarantee here just try it you lose nothing.
[K3 Note General] 911-Future_Maker:
Hi guys currently flashed the new 6.0_VibeUI_1608_3.177.1 without any editing of the updater-script using the 2255 build. The /data partition is below 1GB pretty streamlined dev rom I would say.
[K3 Note General] TheDarkKnight:
Wow, that's great!

Is that untouched?
[K3 Note General] 911-Future_Maker:
Yes! This is the original rom zip, only patched for dualboot. No editing anymore, well at most of the time. :D
[K3 Note General] thisisNiK:
can you provide the link to the rom? :D

Is this it? : www[dot]needrom[dot]com/download/vibe-ui-v3-1-1608/
[K3 Note General] 911-Future_Maker:
No, it's the 6.0_VIBEUI_V3.1_1608_3.177.1_DEV_K50-T5.zip rom from this google drive link
[K3 Note General] thisisNiK:
Okay, I installed the MM rom from the link I posted before. Worked very well.

But when I installed patched gapps for 6.0, they weren't there on MM rom.

But when I returned back to my default lollipop rom, additional gapps were installed, and some of them are not working properly. I think somehow the MM gapps got flashed on lollipop.

Now how to get rid of them, and install lollipop gapps? I mean should i download gapp uninstall zip for MM or for lollipop?

Btw I did not like that marshmallow rom at all. It was really bad, and not even rooted. :rolleyes:

---------- Post added at 02:42 PM ---------- Previous post was at 02:21 PM ----------

Nevermind, I installed lollipop gapps, so they replaced the marshmellow gapps. Problem solved. :good:
[K3 Note General] TheDarkKnight:
You should have installed it without patching it for multiboot slot.
[K3 Note General] thisisNiK:
This multi-boot feature is amazing. Finally I can check out roms by myself, instead of googling videos about it.

I had some issues while doing so. Here is how I solved them:

My primary rom is Sense V2 (Lollipop 5.1). When I tried to "Update ramdisk" or "Set kernel", it gave me error that the device code "K3_Note" was not identified. If you are getting such error, here is how to solve it:

1. Get "Root Browser" (Or any app from which you can browse system files).

2. Goto system folder. Open "build.prop" using RB Text Editor.

3. Scroll down to the very end. Then add this line to file:

ro.patcher.device=aio_otfp

4. Save the file, and reboot the device.

This will solve the problem with Update Ramdisk and Set kernel. Follow the next instructions as mentioned.

Again thanks for all the people who made this possible, and also [MENTION=5207461]Salman A.[/MENTION] and [MENTION=5048731]911-Future_Maker[/MENTION] .... :D
[K3 Note General] TheDarkKnight:
Yes, that's right. That's because some ROMs changes the codename and we have given only aio_otfp, K50-T5 and K50a40 as codenames.
[K3 Note General] 911-Future_Maker:
Well this is just the stock DEV as it is with no modifications. It's easy to flash SuperSU and Xposed.
[K3 Note General] thisisNiK:
Yeh, I guess you are right. I am so used to the custom aosp roms that I cant even stand stock roms anymore... :p
[K3 Note General] 911-Future_Maker:
Yes, I also like the aosp and cm roms more. Currently my daily driver is BlissPop. :)
[K3 Note General] hemant4409:
I just tried and my memory card got corrupted :( Please help [MENTION=5207461]Salman A.[/MENTION]

---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------

Please guide me what to do with utility.zip file>???? I think i m not able to get proper step so its memory corruption issue but in TWRP mmc is showing all files.......
[K3 Note General] TheDarkKnight:
What did you do?? Please elaborate. Explain what you have done and what has happened.

Why do you want to use DualBootUtilities.zip? It is used to switch and wipe ROMs but doesn't have any other capabilities.
[K3 Note General] hemant4409:
Rightnow m on nexus rom earlier on 6.0 so app was not working correctly.

Now its working lets me do some R& D and i will net you know if some issues thanks bro for instant reply.
[K3 Note General] TheDarkKnight:
You are welcome :)

It should be the issue of that particular ROM. MM ROMs are still not very stable.
[K3 Note General] hemant4409:
Getting this error what to do pls suggest
[K3 Note General] hemant4409:
New issue Now it dont even update ramdisk and force close in flashing but patch.zip is created successfully,

Please check attached images. I am very good rom tester its my hobby now this will really help me out. please help me to get rid of this.
[K3 Note General] TheDarkKnight:
Did you edit the updater-script?? Try installing in recovery as said.

Open your build.prop and see what the ro.product.model is. Most AOSP based ROMs have different codenames for it but only a few have been codenames have been listed for our device in Dual Boot Patcher app.
[K3 Note General] hemant4409:
You mean I just need to restart and boot in to recovery ie TWRP and flashing Patched.zip ?

---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------

I haven't edit anything just flashed downloaded ROM after patching it
[K3 Note General] TheDarkKnight:
You have to edit the updater-script before flashing Vibe ROMs. See the Index thread.
[K3 Note General] hemant4409:
OK thanks
[K3 Note General] drakula1000:
As far as I understood, app sharing redirect loading/storing of user data for some app from system default place to /data/multiboot/_appsharing/data/[app] on primary ROM which can be approached by any ROM installed.

If I copy folder /data/multiboot/_appsharing/data/[app] (for example for Viber app) to secure location and install new primary ROM, can I reuse stored Viber app folder, after I configure again appsharing on new primary rom (by copy-paste Viber app folder to /data/multiboot/_appsharing/data/). Point is to avoid repeated activation of Viber after flashing new primary ROM and of course to allways have old messages.

Another question. If I set ringtone in shared Viber on primary ROM (for example) that does not exist in another ROMs on my phone, what happens? Sharing does not work or...? Or is enough just to have same name of the ringtone for app sharing to work?
[K3 Note General] TheDarkKnight:
It may work, but it should be better to back it up with TitaniumBackup or similar apps. You can restore it after setting app sharing (just installing and turning on app sharing for it) and it will work fine.

I think there won't be a problem. It must just act as if that ringtone got deleted and get reset to default ringtone.
[K3 Note General] 911-Future_Maker:
What's going on guys? I love to see this thread active, big thanks to my friend [MENTION=5207461]Salman A.[/MENTION]

Below is my new record dualbooting 9 I repeat 9 roms!! lol

Free space on internal 2.2GB

I was able to achieve this with moving the dalvik cache to the ext4 2nd partition on my 64GB extsd card. No all roms support that, for example MIUI and AOSP are not friendly about moving the dalvik to sd. CM roms are usually fine with that. :D
[K3 Note General] drakula1000:
For two Android 6.0 ROMs, what modification to updater script have you done (if any) before patching with dual boot tool?

Are official 6.0 ROMs going to flash stock recovery in the process of flashing as primary ROM or on SD card?
[K3 Note General] 911-Future_Maker:
Mainly removing only the first lines if they contain a text like "get.prop." , "abort", " verifying " and so on. I can share the updater-script for the 6.0 ROMs I have installed if you're interested. No need for stock recovery all flashed via the DualBoot app or TWRP 3.0.2-1 recovery. Some guys reported problems with the multiboot if using Vibe MM as primary. So keep the Vibe 6.0 ROMs on extsd.
[K3 Note General] drakula1000:
Sorry, my english was very bad in the last sentence. My question was weather MM ROM is going to replace TWRP with stock recovery?

About updater scripts, it would be nice if you share them. Thanks!
[K3 Note General] 911-Future_Maker:
No, it doesn't touches the recovery when the ROM is patched via the DualBoot app.
[K3 Note General] TheDarkKnight:
First of all, thanks. This thread isn't exactly active but I answer the queries that come here.

Then, WHAT THE HELL??!? 9 ROMs??! That's insane! But about moving the dalvik cache part. How did you do that? I had asked Chen about making cache as image file on extsd, like the system partition, but he said it will insanely reduce your SD card's life. I saw you asking the same. So, what's the trick now?

Please tell me.

Thanks. :)
[K3 Note General] 911-Future_Maker:
I move the dalvik to my sdext2 partition on extsd using the Apps2SD app bro, check it out on Google Play here

Tried the Link2SD but it doesn't work for moving the dalvik.

Yes I asked Chen for about nearly the same thing, but my question was mostly refered to placing the /data partition on extsd as image just like the system.img. After he told me that this will kill my extsd in no time I gave up on this. But note that moving the dalvik is not the same as moving the data, it doesn't have the same impact on the lifetime of the card and also the performance loss is minimal and negligible. The /data partition stores every single apk and it's data of every single app you have installed. On the other hand the dalvik cache gets created once and it's leaved alone. So the card is safe.
[K3 Note General] satyaprasad317:
multiboot

i am trying to flash but its saying this device is 'k5o' hen flashing through twrp recovery......bu using app its showing hermes.....i am currently running miui
[K3 Note General] TheDarkKnight:
This is because ro.product.model in your build.prop is hermes which is the codename of Redmi Note 3, I think. You have to change it to K50-t5. Use Root Explorer or Build.prop editor.
[K3 Note General] satyaprasad317:
not booting

my rom succefulliy flassed but not booting at all... i tried to switch to primary through utilities.zip but it is get vibrated 4 or5 times and again going back too recovery kindly help....plz
[K3 Note General] TheDarkKnight:
Are you having low internal storage? That might be the problem
[K3 Note General] :
When flashing external zips.

Sir I'm going to try to multiboot my k50a40. I want to ask that if I flash some other zips like Xtrememusic, so where will it get flashed? To the primary? And if I use other apps (gonna try them for tweaking, like LSpeed or something like that) what should I do? Please guide me.
[K3 Note General] TheDarkKnight:
Just patch it as you patch ROMs zips. Use the same location (eg.: Primary, extsd-slot1, etc.)
[K3 Note General] drakula1000:
I use this Dual Boot Patcher tool for some time now, and I think it opened possibility for testing various ROMs without any troubles (loosing data, ...).

I especially appreciate app sharing, but experienced some issues in using it. They are related to app sharing for Viber app.

When I dual boot official VibeUI MM (1617DEV, 1622ST) rom with any other non VibeUI lollipop based ROM (Kaka's ROMs, LR Team ROMs, Cheskins ST5), I cannot make app sharing feature for Viber to work properly (all other apps that I tried, worked OK).

Namely, MM rom does something to Viber shared folder, that on other ROMs is not supported, because they ask me to register again on Viber. When I restore Viber's data with Titanium backup tool on lollipop ROM, app sharing works when I boot to MM ROM. But, when I boot back to the lollipo ROM, it is again the same story (Viber asks for registratuion).

Is there a cure for this issue?

Just to note that when I combine 1604ST, with other lollipop based ROMs, app sharing for Viber works just fine.
[K3 Note General] TheDarkKnight:
I haven't experienced any issues like this. You mean only MM has issues, right? No LP roms? Maybe it's the way MM ROMs handle app data. Ask in the official thread if the issue persists.
[K3 Note General] drakula1000:
MM ROM (only official tested) does something to the shared data folder, which makes it unreadable/unrecognizable to the LP ROMs. Only for Viber app, other work just fine