androidz305
Newbie
How do I extract the framework res. Apk.?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM][WIP][4.4.2] CyanogenMod 11.0
- Thread starter EagerestWolf
- Start date
-
- Tags
- huawei valiant
androidz305
Newbie
Can I just change the hex color number of the keys.
androidz305
Newbie
Got the res. Apk
http://www.4shared.com/mobile/Lr5xLF_3ba/framework-res.html
http://www.4shared.com/mobile/Lr5xLF_3ba/framework-res.html
EagerestWolf
Android Enthusiast
Your res.apk can be used to change the color of the soft keys (the ones like on the Nexus 4). The hardware soft keys are hard coded and cannot be changed.
androidz305
Newbie
Are those gapps a teaser? Good work Wolf. Thanks!
EagerestWolf
Android Enthusiast
They may be. I am getting close. I have finally gotten everything to compile. I am just having issues getting it to pack and sign the zip. It says my recovery.fstab is malformed. So, idk
rbheromax
Android Expert
i have gotten a zip to be made and signed
it takes fstabv2 instead of the old fstab which is the recovery.fstab
my device tree:
https://github.com/rbheromax/android_device_huawei_valiant
http://dt11.net/rbheromax/cm/cm-11-20140201-UNOFFICIAL-valiant.zip
it also has set_perm instead of set_metadata so it should flash correctly if u take out the first two assert_prop lines
it takes fstabv2 instead of the old fstab which is the recovery.fstab
my device tree:
https://github.com/rbheromax/android_device_huawei_valiant
http://dt11.net/rbheromax/cm/cm-11-20140201-UNOFFICIAL-valiant.zip
it also has set_perm instead of set_metadata so it should flash correctly if u take out the first two assert_prop lines
EagerestWolf
Android Enthusiast
Hey, submit a pull request on Github and I will merge your changes and add you as a maintainer on all 3 branches so you can make modifications as needed. One modification that needs to be undone and I will fix is the device (by Cyanogenmod correct standards) is the y301a1. I want to submit this device to make it official, so that has to stay.
rbheromax
Android Expert
the tree i have uploaded was just to get it building and so i can wrap my head around wats going on. i after it gets booting I will "sed" switch back in the y301a1. if u add me as a maintainer, i'll make clean commits and keep the y301a1 in the tree
im just trying to be helpful here lol
im just trying to be helpful here lol
EagerestWolf
Android Enthusiast
Also, had to delete my entire CyanogenMod folder, starting over now. For some reason, it was not building any of the frameworks. Idk.
EagerestWolf
Android Enthusiast
the tree i have uploaded was just to get it building and so i can wrap my head around wats going on. i after it gets booting I will "sed" switch back in the y301a1. if u add me as a maintainer, i'll make clean commits and keep the y301a1 in the tree
im just trying to be helpful here lol
Well I added you as a contributor, so all you need to do is submit a pull request so I can merge your changes, and we shall be good to go. It is always nice to have an extra brain to catch stuff I miss.
EagerestWolf
Android Enthusiast
Zip is a no go. I am in bootloop. So something is wrong somewhere, now we get to track it down.
EagerestWolf
Android Enthusiast
Maybe try compiling with a bootloader? That may be worth a shot.
rbheromax
Android Expert
Commit I made:
when i push commits later today, the kernel will support exfat and f2fs to match the cm-11 boardconfig.mk build params i added
EagerestWolf
Android Enthusiast
Ok, that works. Thanks for all your help. Cyanogenmod has been very uncooperative.
EagerestWolf
Android Enthusiast
Now that there is another person working on this, I gotta remember to push my commits more often.
rbheromax
Android Expert
I KNOW wat the problem is. It cant mount system. If you revert adb to an older version in the source and compile again, and boot it will give a logcat saying:
That means it cant find and mount /system because with 4.3 Google changed how filesystems mount, to support SELinux among other things. Thats why fstabv2 is needed to compile 4.3+. A little ramdisk tweaking and it'll boot
Try flashing the rom WITHOUT a boot.img and see if it will boot (using the stock kernel)
Thats a nogo. while we can do this, it has little chance of working and more chance of HARD bricking your device to where a JTAG/RIFFbox machine is needed
EagerestWolf
Android Enthusiast
Also what make command are you using? I have been using
Code:
make -j8 otaupdaterbheromax
Android Expert
EagerestWolf
Android Enthusiast
I KNOW wat the problem is. It cant mount system. If you revert adb to an older version in the source and compile again, and boot it will give a logcat saying:
That means it cant find and mount /system because with 4.3 Google changed how filesystems mount, to support SELinux among other things. Thats why fstabv2 is needed to compile 4.3+. A little ramdisk tweaking and it'll boot
Try flashing the rom WITHOUT a boot.img and see if it will boot (using the stock kernel)
Thats a nogo. while we can do this, it has little chance of working and more chance of HARD bricking your device to where a JTAG/RIFFbox machine is needed
Well I won't compile with a bootloader then. One thing that may be a potential problem is that the Clockworkmod for this device is from the Cyanogenmod 10.1 tree. Clockworkmod from the Cyanogenmod 11 tree compiles and installs, but the display will not initialize.
rbheromax
Android Expert
if you can extract a /cache/recovery/recovery.log from a non booting cm11 recovery, you can see where it went wrong. the best thing to compile right now would be PhilZ recovery
delete bootable/recovery and replace with:
https://github.com/PhilZ-cwm6/philz_touch_cwm6
see if that helps
delete bootable/recovery and replace with:
https://github.com/PhilZ-cwm6/philz_touch_cwm6
see if that helps
EagerestWolf
Android Enthusiast
One thing to note about the install, when it completes it says
With the stock kernel, it doesn't boot at all. It sits at the Huawei Logo.
Code:
script succeeded: result was [/system]With the stock kernel, it doesn't boot at all. It sits at the Huawei Logo.
EagerestWolf
Android Enthusiast
Will do.
EagerestWolf
Android Enthusiast
Can diff find the difference in 2 ramdisks?