yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Now I know why its not working. I'm formatted to f2fs and elementalx doesn't support f2fs. Can I give it f2fs support via make menuconfig? Because it says that that feature is expiremental. Thanks for the help though! I still don't know why it says bricked-hammerhead-twrp. I never flashed it before.
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
Why did you not mention this earlier??

Now that you mention it, look at your logs:

<3>[ 2.321738] EXT4-fs (mmcblk0p28): VFS: Can't find ext4 filesystem
<6>[ 2.327327] fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/userdata,/data,ext4)=-1
<6>[ 2.331619] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/userdata
<6>[ 2.376084] e2fsck: e2fsck 1.42.9 (28-Dec-2013)
<6>[ 2.376214] e2fsck: ext2fs_open2: Bad magic number in super-block
<6>[ 2.376349] e2fsck: /system/bin/e2fsck: Superblock invalid, trying backup blocks...
<6>[ 2.376428] e2fsck: /system/bin/e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata
<6>[ 2.376615] e2fsck:
<6>[ 2.376691] e2fsck: The superblock could not be read or does not describe a correct ext2
<6>[ 2.376824] e2fsck: filesystem. If the device is valid and it really contains an ext2
<6>[ 2.376904] e2fsck: filesystem (and not swap or ufs or something else), then the superblock
<6>[ 2.377036] e2fsck: is corrupt, and you might try running e2fsck with an alternate superblock:
<6>[ 2.377200] e2fsck: e2fsck -b 8193 <device>
<6>[ 2.377279] e2fsck:
<6>[ 2.377358] e2fsck: e2fsck terminated by exit(8)

mmcblk0p28 is the userdata block.

F2FS support is in the ramdisk, not the kernel image.

ElementalX uses the ramdisk of the kernel it was flashed over, so you have to flash a kernel that has F2FS support, then you can flash ElementalX over it.

Try flashing this dummy kernel: https://basketbuild.com/filedl/devs...droid-5.1-Kernel-Cl3Kener-Kexec-Enforcing.zip

Then flash ElementalX immediately right afterwards.

Also, I Google'd a bit and that bricked kernel is the TWRP kernel apparently. No point giving a last_kmeg if you didn't even try booting with your own kernel previously lol.
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
I just downloaded the Code Blue zip and it has this script which renames files:

mv /system/etc/sysctl.conf /system/etc/sysctl.conf-bak
mv /system/bin/thermal-engine-hh /system/bin/thermal-engine-hh-bak
mv /system/bin/mpdecision /system/bin/mpdecision-bak
mv /system/lib/hw/power.msm8974.so /system/lib/hw/power.msm8974.so-bak

Rename them back with a file manager app, then it might be okay to flash ElementalX over it.

If it doesn't work, then you'll have to reflash your ROM, flash the dummy kernel for it's ramdisk then flash your ElementalX zip.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Sounds hard what should I rename? rename to what? I don't understand. I really don't want to reflash my ROM because I just did it like 4 times in the past hour and I feel my phone is stressed out right now. And it's heating.
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
Look at the script:

mv /system/etc/sysctl.conf /system/etc/sysctl.conf-bak

mv = move (or rename)

/system/etc/sysctl.conf

was renamed to

/system/etc/sysctl.conf-bak

so you rename "sysctl.conf-bak" back to "sysctl.conf"

Your phone can handle heat. The CPU has a hardcoded thermal shutdown temp of 105C, where it will forcefully shut down no matter what when reaching that temperature. If you're worried, you could just give it 5 minutes to cool down, which is plenty of time.

Its 2:41am here for me, I need to get my sleep. If you need any further assistance I'll respond when I get up. :)
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Ok, Thank you so much. It works now. But now I have another question. Can I also compile for codeblue kernel? Because I do not want to keep flashing the f2fs-ext4 kernel then the elex_defconfig compiled kernel whenever I try to install a new build. I looked inside the def_config of the codeblue kernel but it doesn't show the CONFIG_LOCALVERSION that I can change the name of the kernel with. And also inside the kernel zip file, there is no zImage file that I can replace. And also this is the same for the hammerhead_defconfig from the stock sourcecode. I read somewhere that I can edit the "EXTRAVERSION" inside "makefile" to the kernel name that I want instead of using the def_config. I also noticed that even though there is no zImage inside the kernel flashable zip for codeblue, there is a boot.img. So do I make the zImage into a boot.img then replace it in the flashable kernel zip? And how do I do that?

UPDATE*: I downloaded kernel tools master and extracted codeblue's boot.img. I found that the boot.img included 2 parts: the zImage and the ramdisk. So what I need to do is replace the codeblue zImage with my compiled zImage and then compress both the new zImage and the codeblue's ramdisk back into a boot.img? How do I do that?

And by the way, thanks you for all this help.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
EDIT* I realized i needed apt-get install ccache

Now i only need help with the questions above.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Ok, I took the codeblue kernel compiled zImage and it wouldn't flash when i compressed it with codeblue's ramdisk into a boot.img. It would just stay on the Google screen. So I put the zImage into the Elementalx zip file and when I flashed it I got a mix between the Elementalx and codeblue kernel. It had Codeblue's zImage and Elementalx's ramdisk. So basically a mix between them. But since you said that elementalx just uses the ramdisk of the previous kernel, does that mean if I flash it over the stock kernel it wouldn't have f2fs support?
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
Did you use zImage or zImage-dtb? You want to only use zImage-dtb and ignore zImage.

You package a zImage-dtb along with a ramdisk into a boot.img using the mkbootimg tool. Whatever tool you used to do this, was using mkbootimg.

If you flash ElementalX over the stock kernel, it will be using the stock ramdisk, which does not have F2FS support.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
yes I used zImage-dtb. So I did try to use mkbootimg but I didn't really know how to use it well so I just made the zImage. Can you please tell me how I can use the mkbooting tool? My kernel is running fine (thanks to you and theesotericone :) I can't thank you guys enough) the only thing i want to do is combine the ramdisk and zImage-dtb into the boot.img using mkbooting tool. Thanks again.
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
If you do not have mkbootimg/mkbootfs, I have attached them in the .zip in this post.

If you have an unpacked ramdisk, you will need to run this to create a ramdisk.gz:

./mkbootfs unpacked/ramdisk/folder | gzip > wherever/you/want/ramdisk.gz

Then to pack zImage-dtb and ramdisk.gz into a boot.img:

./mkbootimg --kernel directory/to/your/zImage-dtb --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 msm_watchdog_v2.enable=1' --base 0x00000000 --pagesize 2048 --ramdisk_offset 0x02900000 --tags_offset 0x02700000 --ramdisk wherever/this/is/ramdisk.gz --output wherever/you/want/boot.img

Replace the directories wherever applicable.

Keep in mind that if you put ElementalX into a boot.img and flash it, you will be missing other files that the original zip also places into the system partition, and this may cause issues.

If you're doing this for a kernel that already uses a boot.img, replacing it in the zip will be fine.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Well, the ramdisk is already packed, but it is in a .img form, not a .gz. Is this fine? And I wasn't planning on putting elementalx in a boot.img. I was just planning to replace the original zImage from codeblue and replace it with a custom one I made (compiled from codeblue source) and pack it with the codeblue ramdisk so it would have f2fs support. I'm not planning to use anything from elemenntalx. :)
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
In .img form? :eek: You could try unpacking it and repack it as .gz? A better idea might be to use AIK (http://xdaforums.com/showthread.php?t=2073775) which will unpack the ramdisk into a folder from a boot.img properly. You can then pack the contents of that folder into a ramdisk.gz.

And yeah, ElementalX is DESIGNED to use the previous ramdisk and not flashed as a boot.img, attempting to pack it as a boot.img will likely only cause more issues unless you know what you are doing.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Ok, thanks. I think you should take a break from this. You've been working hard in answering my questions. I'll try to not ask anymore questions until the weekend. I'll follow your steps until then. Thanks for the help so far. See you soon. ;)
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Sorry to interrupt the break but when I do the second command of the mkbootimg it says : ./mkbootimg: permission denied, even when I am root (tried sudo su).

I figured out another way to do it using android image kitchen and repacked the boot img using the kernel image kitchen. But when I tried flashing it it only went to the boot screen, not even the boot animation and was stuck there.
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
Did you make it executable first with chmod?
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
No, I don't know how to do that. Sorry can you please tell me? And do you know why my kernel doesn't boot when i flash the new boot.img?
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
Google "chmod make binary executable"

Not sure why it wouldn't boot, maybe a weird AIK thing, I dunno.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Ok, it compiled the bootimg. I'll test it later. But I noticed that after reflashing my ROM multiple times my battery life is now much worse. I think this is because of the heat to the battery. I used to get <1-2% battery drain overnigtht and now I get >5% battery drain overnight and during the day I almost never use it and the battery drains almost 7% in 7 hours.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Can you please check these logs for me? The kernel wasn't booting. I just recompiled and it just started to do this infinite boot. Thanks.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Also can you tell me where the problem is and how to fix? thanks.
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
logs are corrupt.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
error while making the ramdisk.gz, i finally figured out why it wasn't booting. Because of this:

error: cannot open directory 'unpacked/ramdisk/folder

when doing the command:

./mkbootfs unpacked/ramdisk/folder | gzip > /home/yusuf/Downloads/mkbootimg_mkbootfs/ramdisk.gz

Need help. Thanks.

EDIT*

I replaced "unpacked/ramdisk/folder" with "/home/yusuf/Downloads/mkbootimg_mkbootfs/ramdisk" and it made the ramdisk.gz. I just want to clarify: inside the newly made ramdisk.gz file there is only one file inside called "ramdisk". Is this correct so far? Then i repack the ramdisk.gz with my zImage-dtb to make a boot.img correct? and also do i need to change the name of the zImage-dtb before i repack it with the ramdisk.gz?
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
I already said to change the folder location to wherever yours is.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
EDIT*

I replaced "unpacked/ramdisk/folder" with "/home/yusuf/Downloads/mkbootimg_mkbootfs/ramdisk" and it made the ramdisk.gz. I just want to clarify: inside the newly made ramdisk.gz file there is only one file inside called "ramdisk". Is this correct so far? Then i repack the ramdisk.gz with my zImage-dtb to make a boot.img correct? and also do i need to change the name of the zImage-dtb before i repack it with the ramdisk.gz?
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
don't need to rename the zImage-dtb because you're already specifying the filename when you're packing the boot.img
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
I just want to clarify: inside the newly made ramdisk.gz file there is only one file inside called "ramdisk". Is this correct so far?
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Never mind. the new Code Blue zip files don't include a boot.img. thanks though for the help.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Now everything works fine. Thanks.
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Do you know how to add my own hotplug by the way? I already made my own cpu governor that works, i just need a hotplug. Thanks
[Nexus 5 Q&A, Help & Troubleshooting] Electrex:
Ok
[MDA Compact II Software Upgrading] youser:
Hi guys,

I decided to downgrade from the Wm6-ROM back to WM5 AKU3.3 (offical ROM from T-Mobile Germany). However, something went wrong during flashing and now my Charmer seems to be broken.

When I start the Charmer, all I get is a T-Mobile splashscreen with the following text in the top-left corner:

IPL: 3.08

SPL: 3.08.0000

GSM: 02.69.21

OS: 3.8.2.22

Is there anything I can do to make my Charmer work again?

WM5 or WM6 does not matter, even though I'd prefer WM5.

Thanks alot!
[MDA Compact II Software Upgrading] vlodeck:
Go to bootloader mode (press and hold camera button, tap reset button for 2 seconds, holding the camera button wait for the bootloader screen (threecolor stripes), then release the camera button. Plug in the USB cable and run the AKU 3.3 german RUU.
[MDA Compact II Software Upgrading] youser:
The official update does not work since I cannot establish an ActiveSync connection with the Charmer. I followed your instructions and got the Charmer to the bootloader screen, but then the Update fails (error code 260).

Is there any other way to flash the MDA? :-(

(maybe using the nk.nbf file which is part of the official update?)
[MDA Compact II Software Upgrading] vlodeck:
Maybe. You dont need to have AS connection, just get your phone in bootloader mode and proceed with RUU.
[MDA Compact II Software Upgrading] youser:
Now it worked after I also restarted my computer. :D

Thanks for helping me with the bootloader mode, I'm now running WM5@AKU3.3 again. Once the key mapping issue in WM6 is resolved, I'll upgrade.
[MDA Compact II Software Upgrading] vlodeck:
i wouldnt wait for it :)
[Xposed Framework Modules] Beat_Slayer:
Heres a litle mod I made for my Doogee DG800 valencia that merges the cell and wifi signal indicators.

It supports gemini (1-4 SIMs) and also AOSP alike ROMs running kitkat.

Due to recent various crash reports, only install if you really know what you're doing, until I can add further version trials to the module.

Thanks rovo89 for the Xposed Framework, and Ticklefish for the inspiration with xml mods.

Changelog

v0.3

- Initial Public Release

v0.8

- Added support for non gemini AOSP alike ROMs

- Added option for custom wifi bar color selection
​

Version Information

Status: Stable

Current Stable Version: 0.8

Stable Release Date: 16/03/2015

Created: 12/03/2015

Last Updated: 30/03/2015
[Xposed Framework Modules] Beat_Slayer:
Please report if you test this mod on other mediatek devices and it works, if it doesn't work, or if DPI it's wrong, you can post a screenshot and your SystemUI.apk and I'll make it compatible with your device.
[Xposed Framework Modules] Gaziaggelos:
Nice module

I try it and its nice in my doogee dg800 but how you success to made tranpert your statusbar?! i try everything but i cant :/
[Xposed Framework Modules] Beat_Slayer:
Tinted Status Bar Xposed Module, I believe. I can't really remember if I've done it by myself because I'm always fiddling with the UI. :D:D

I'll soon make an update to this module to support other AOSP alike ROMs, maybe I'll include a transparent status bar option...
[Xposed Framework Modules] moso11:
Lollipop supported?
[Xposed Framework Modules] Beat_Slayer:
In the next version, it will! :D
[Xposed Framework Modules] cpaulin:
UI crashes after activating module and rebooting. I needed to boot in safe mode and uninstall the app to get rid of the problem (with the UI still crashing every second).

You should sign it as an experimental version.
[Xposed Framework Modules] Beat_Slayer:
For the users that are having problems:

Which ROMs are you running? I tested it on several MTK gemini AOSP based ROMs and some normal AOSP ones, without problems.

Anyway I'm going to flag it as test version.
[Xposed Framework Modules] 12:121390:
same here on lg g3 d850 blisspop rom..
[Xposed Framework Modules] pedrazadixon:
work in android 4.2.1 (ThL W200 dual-sim)
[Xposed Framework Modules] sharks2418:
I'm running stock android 4.4.4 on a nexus 5 and the system ui kept crashing for me
[Xposed Framework Modules] himanshu.khanna:
Can u please support android 4.1.2

Sent from my GT-I8552
[Xposed Framework Modules] cpaulin:
Stock KitKat 4.4.4 ROM of the sony xperia Z1.
[Xposed Framework Modules] Cyboy:
plz support for JB
[Xposed Framework Modules] moso11:
Looking forward for a stable Lollipop release.
[Xposed Framework Modules] reemar:
same crash with RR 5.3.9 of d802 lg g2 phone
[Xposed Framework Modules] w0rinal:
See signature :p

SlimKat 9, KK 4.4.4 for SGS3

In one of the first lines in the log it says com.mediatek....

I've read about mediatek devices but I don't know what exactly it is and I'm sure my device isn't

[size=-4]Sent from my Boeffla powered Slim (4.4.4) GT-I9300[/size]
[Xposed Framework Modules] Beat_Slayer:
I noticed that, I believe the autodetection of the system it's having some problems, I'm very sorry for the problems that it caused to the users, but it passed on my tests. :eek:

Once again I'm deeply sorry for all the trouble, just wait till I cook a new solution. :(
[Xposed Framework Modules] w0rinal:
Apology accepted :D

It is flagged experimental in xposed installer so IMO everyone is installing it on their own risk

Take your time :thumbup:

[size=-4]Sent from my Boeffla powered Slim (4.4.4) GT-I9300[/size]
[Xposed Framework Modules] fallenwout:
Same here, stock 4.4.2 lg g2

This is a very good idea, don't give up.

I keep this installed but disabled just to get an update notification in xposed because i really want this.

There is no need to boot in safe in though. Just wait until the phone is fully booted (20sec after first error). Then click the error away and go fast enough to xposed, click new error away and go fast enough to modules, click new error away and uncheck this module fast enough... Reboot.

Sent from my LG-D802
[Xposed Framework Modules] Beat_Slayer:
New version just uploaded, guess that it wasn't a problem on the system detection algorithms, I've just named the xml templates badly. :silly:
[Xposed Framework Modules] Antho02:
hello

thanks for your work wich looks fun, but for now it crashed my phone :/

i'am softbricked :/

can't do nothing but really nothing on screen.

is there a way to uninstall it or disable xposed via adb for i can boot my phone?

thanks in advance
[Xposed Framework Modules] Beat_Slayer:
Here has that info: http://xdaforums.com/xposed/xposed-installer-versions-changelog-t2714053
[Xposed Framework Modules] Antho02:
oh ok thanks

so i have do disable xposed, i cant just uninstall this mod? :/
[Xposed Framework Modules] Beat_Slayer:
Disable, reboot, uninstall module, enable xposed and reboot. ;)
[Xposed Framework Modules] Antho02:
oh yes ok!

thank you!
[Xposed Framework Modules] w0rinal:
I'm probably too late but you could try to edit "/data/data/de.robv.android.xposed.installer/conf/modules.list" via adb and delete the line "/data/app/*this app's package name*" and reboot your device.

In theory the module shouldn't be loaded (= not activated in xposed installer)

[size=-4]Sent from my Boeffla powered Slim (4.4.4) GT-I9300[/size]

---------- Post added at 07:57 PM ---------- Previous post was at 07:19 PM ----------

It's me again

Systemui doesn't crash anymore :)

But it doesn't seem to work. Wifi indicator isn't shown (which is intended I think) bit signal indicator is only stock signal indicator

There is no difference when Wifi is connected or when it's strength changes

[size=-4]Sent from my Boeffla powered Slim (4.4.4) GT-I9300[/size]
[Xposed Framework Modules] Antho02:
thank you i ll try this

but it seems my phone isnt recognized :/
[Xposed Framework Modules] reemar:
Still not working on cm12, is there someone with cm12 that it's work for him/her

?
[Xposed Framework Modules] briatide:
0.9.1 still results in systemui crash on moto g 4.4.3 stock
[Xposed Framework Modules] w0rinal:
Just noticed a vertical bar, underlayed under the left side of the airplane mode icon.

So it kind of works when my device is in airplane mode.

Maybe it's the same on cm12

[size=-4]Sent from my Boeffla powered Slim (4.4.4) GT-I9300[/size]
[Xposed Framework Modules] fallenwout:
Is this mod dead?

Sent from my LG-D802
[Xposed Framework Modules] Beat_Slayer:
No it isn't, I just finished a new version. :cyclops:

New version on the repo in a couple of minutes.
[Xposed Framework Modules] reemar:
will work on cm 12.1(, the new version)?
[Xposed Framework Modules] Beat_Slayer:
Can you try the new version?
[Xposed Framework Modules] Beat_Slayer:
Post your build.prop, I'll integrate it.
[Xposed Framework Modules] yanleites:
Thanks, will work on nexus 5 5.1?
[Xposed Framework Modules] fallenwout:
Why can't I see the updates in xposed? I want it in xposed so i can quickly disable it when it crashes.

Sent from my LG-D802
[Xposed Framework Modules] Beat_Slayer:
The updates are only on the xposed repo, I haven't updated the post apk.

As the versions are flaged as experimental, you have to activate the experimental versions to be shown on the module settings in the xposed installer.
[Xposed Framework Modules] fallenwout:
It removes both my wifi and mobile. I have custom icons though. Probably interference of some other xposed modules.
[Xposed Framework Modules] w0rinal:
It's working now :thumbup:

The Wifi indicator is shown on the right side of the mobile signal indicator when airplane mode is off and when it's on the indicator is shown on the left of the airplane symbol, but that's not a problem, I just wanted to inform you about that.

Suggestion: an option to change the WiFi indicator's location

And to prevent confusion you could add some text informing about the need to reboot the device/restart systemui after changing the color

[MENTION=4303902]fallenwout[/MENTION]

Most likely that's due to other modules :D

I heard that the way xposed works follows the "the latest takes is all" principle (I'm not a native English speaker, do you say it like that?)

I think that's why Statusbar/Statusbar icon tinting apps always 'win'. Every time the color changes they determine which color is applied while this module only applies it's color on boot.

To cut a long story short, I am pretty sure it'll work when modules like FSBI/FSCB/XUI Mod are disabled. At least that's how it's working for me

[size=-4]Sent from my Boeffla powered Slim (4.4.4, AOSP based) GT-I9300[/size]
[Xposed Framework Modules] fallenwout:
Exactly, i got FSCB. It colors the icons at every window change. But FSCB is too beautiful to disable.

Sent from my LG-D802
[Xposed Framework Modules] w0rinal:
Yeah, that's true. FSCB is really missing a "don't color certain notifications/Statusbar icons" function

But for testing reasons you could disable fscb and report back if it's working then :)

[size=-4]Sent from my Boeffla powered Slim (4.4.4, AOSP based) GT-I9300[/size]
[Xposed Framework Modules] fallenwout:
It has that option. I've put this module in the exception list without success. I need to put the signal bar in the ignore list but FSCB only seem to show app-like programs in the list of choices. Signal bar is not a real app.

Sent from my LG-D802
[Xposed Framework Modules] w0rinal:
Ah, wtf

How did I not see that? :D

Probably didn't read the small text and assumed it was a "don't tint Statusbar when inside these apps" function

Tried "use foreground/background color for Wifi/signal indicator" in fscb but no combination showed the WiFi indicator colored

[size=-4]Sent from my Boeffla powered Slim (4.4.4, AOSP based) GT-I9300[/size]
[Xposed Framework Modules] George Tashkov:
Works perfectly on my Xiaomi Note /AOSP 4.4.2 Jotiki ROM. Thank you.