Hello all,
Since there is no official CyanogenMod for M7 Dual SIM, i want to give it a try and do it myself (also since the phone is old enough, I don't care if it is bricked or something
Also since Android 5.0+ has dual SIM support/APIs, I think it would be a good learning.
What I have done so far:
1. Downloaded CM Source (repo sync).
2. Downloaded HTC m7cdug Kernel Source.
3. Reading and experimenting the build process.
Since this a new device in CM branch, need your support to understand the steps.
Please advise/participate if anyone is interested.
Progress Update
1. CM12 flashing was failing from TWRP. Updated the updater-script. Flash successful.
2. CM Kernel + CM ROM = Black Screen
3. HTC KitKat Kernel (Android 4.4.3) + CM ROM = Boot Loop (init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting into recovery mode)
Next Step
1. Test with HTC Lollipop Kernel (recently released) and investigate the Boot Loop.
2. Test with CM Kernel and investigate black screen.
3. Replace m7 libraries with m7cdug Lollipop stock libraries and check the result.
4. Flash CM12 m7 ROM with all stock HTC Lillipop libraries and check the result.
Progress Update: HTC Kernel (5.0.2) + CM12 ROM for m7
After replacing the display drivers from m7cdug, Boot Animation is visible... eeeeyyyaaaaaaayyyy...
Still stuck at boot animation. Investigating last_kmsg, need help...
Have you made any progress since your last post? I'm interested in getting a CM12 build on my M7CDUG and willing to help in any way I can
Seems like I've been doing it all wrong, booting using HTC stock Kernel is actually like booting HTC ROM, using HTC RC scripts etc. Useless...
Booting with CM Kernel is failing and doesn't even go till logcat service is up. Only available log is last_kmsg, which is too much log to identify the problem.
Perhaps, compete ROM building is required...Need some last_kmsg expertise and help to troubleshoot the problem...
Attaching last_kmsg if anyone can troubleshoot and identify the problem.
Great idea!
Hello!
I have same idea about porting Cyanogenmod to cdug.
I have several experience in linux kernels, modules, drivers etc.
We can try to collaborate. Your carrier is HTC RUS, do you speak russian? Can we contact via skype etc?
Thank you!
Related
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this? I've spent around a combined 12+ hours searching, researching, and tinkering trying to figure this out, but no success. I typically receive a "com.android.systemui" error message or "Unfortunately, System UI has stopped" message. After I acknowledge the message, it pops up again in a second or two. I have to force a shutdown of the phone and recover via TWRP. I've detailed my history and attempts below.
On the CM website, it says something about how "ghost" is a unified OS for every Moto X, except AT&T, since it's not unlockable. With Sunshine, shouldn't I be able to install the "ghost" ROM? Or does it not matter? I hope this isn't a case of, "even though you have an unlocked bootloader, the 'ghost' ROM isn't intended for your version of the phone." If that's true, it looks like all development on the XT1058 has pretty much stopped.
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
I recently tried using the feature, "fixing permission" in TWRP thinking it might help with the "ghost" installations. I started getting bootloops when trying to restore to previous ROMs. The only restore that worked was my true original stock backup; the other restore attempts on SlimKat and other stock instances failed. That worries me. While I have successfully restored my phone, does anyone know if I may have screwed up my phone for the long-term?
(Answered by KidJoe; thank you!) Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
(Answered by KidJoe; thank you!) Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
HISTORY
Phone: AT&T Moto X XT1058, non-developer edition
Android: 4.2.2 | No attempt has been made to upgrade the OS beyond 4.2.2
Used Sunshine to unlock the bootloader while still on 4.2.2
Recovery: Installed TWRP v2.8.1.0, and I use TWRP to backup and install old and new ROMs (I think it's version 2.8.3... I never downloaded a version 2.8.1, but that's what the screen says. I'm wondering if the authors just forgot to update the version number in the program.)
Successful ROM installs:
SlimKat build 7 Official, msm8960dt
Cyanogenmod 11 Snapshot M5 msm8960dt (2014-04-05)
Failed ROM installs:
Cyanogenmod 11 Snapshot M12 ghost (2014-11-15)
Cyanogenmod 11 Nightly ghost (2014-12-19)
LiquidSmooth KitKat v3.2 Nightly ghost (2014-10-31)
LiquidSmooth Lollipop v4.0 Nightly ghost (2014-12-20)
Other Notes:
GApps were always installed when available. I also tried not installing them.
cxwong1 said:
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
Click to expand...
Click to collapse
I will answer these two....
1. NO you can not. Once you have 4.4.2, 4.4.3 or 4.4.4 on your phone, do NOT attempt to downgrade, even if you have an unlocked bootloader... For more details see what I typed here -> http://forum.xda-developers.com/moto-x/general/4-4-4-downgrade-possibility-t2971847/post57563419 along with the other discussions in that SHORT thread.
2. The older root and write protection disable processes for a Moto X with a locked bootloader (like ATT and Verizon) rely on taking advantage of vulnerabilities in the 4.2.2 w/Camera update rom version, or the 4.4 rom. These processes walk you through downgrading your ROM to 4.2.2 w/Camera update and following a set of steps to upgrade which will keep root and disable write protection. NOTE: It was safe to downgrade from 4.4. to 4.2.2 w/Camera update when following the SlapMyMoto/MotoWpNoMo processes. But that was the only time it was safe!!!!
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
cxwong1 said:
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
Click to expand...
Click to collapse
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
syckman said:
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
Click to expand...
Click to collapse
Hey! Nope, I haven't found the answer, unfortunately. I haven't really tried to upgrade my OS since.
cxwong1 said:
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this?
Click to expand...
Click to collapse
I bit the bullet yesterday and paid for the Sunshine bootloader unlock. After replacing the stock bootloader with TWRP and making a backup, I started looking into putting CyanogenMod onto it, as I had just updated a Galaxy Tab 2 7.0 to KitKat (via CyanogenMod 11) last week and it wasn't right that my phone had an older Android build than my tablet. I ran into conflicting information here and elsewhere, but the bottom line:
I have CyanogenMod 11 running on my AT&T Moto X.
More specifically, it's this zipball (remove spaces in next line to bypass the forum's lame link blocking):
https :// download.cyanogenmod.org / get / jenkins / 90775 / cm-11-20141115-SNAPSHOT-M12-ghost.zip
I also tried the latest 12.1 nightly, but while it appears to boot up, it reboots almost as soon as you try to set it up.
One thing that seems to help: before loading any ROM (whether stock, CyanogenMod, or whatever), wipe the flash. I have the ROM and Google Apps files on a flashstick that gets connected through an OTG cable, so I just tell TWRP to wipe everything but OTG storage, restore the ROM, let it boot up, then go back to TWRP to install the Google apps.
(Good thing I had the stock ROM backed up...had to revert to it this morning to back up aCar and Stocard data so I could bring them into CM.)
Starting configuration for my phone: AT&T XT1058, stock 4.4 firmware, rooted with the usual means for doing so, bootloader locked until Sunshine worked its magic.
Hi guys, I had bought this device in anticipation that this will also see as much development as first gen, and was disappointed. But here's a hacky sort of way to flash new ROMs on the MTK variant.
1) Make sure you are running the same STOCK Android version of which you want to install the ROM. I am on 6.0.1 and will be using CM 13
2) Find yourself a "sprout4" ROM which you would like to flash.
3) Boot into TWRP, then backup your boot partition and perform a clean wipe.
4) Flash the ROM, then restore the boot image backup.
5) Reboot. Enjoy!
Bugs :
Of course, there have to be some.
1) Battery percentage : Battery percentage will always be around 3000+, can't help that. Deal with it.
2) Sudden lockups : When I was on OmniROM, sometimes the quick settings drawer refused to open, and home button only worked when in recent apps. I created a guest user, then switched back to my own and these bugs vanished.
3) Some ROMs may not work : I couldn't boot Resurrection Remix on this, so maybe some more ROMs exist that cannot do that as well.
I am not responsible for any damage you may end up doing this method. I was successful using it and therefore decided to share it with everyone only after I was sure that stuff worked.
Thread closed at OP's request
Alright, we need to stir the scene up... and God is it past the due time.
Blu has had the Kernel sources available in their ftp server since August IIRC and the Gionee equivalent of this phone has been running Marshmallow for more or less the same time.
So here's my github with the kernel sources on it: https://github.com/batoussai/android_kernel_VivoXL
I fixed the problems I found with improper makefile prepending and inclusions in headers and c files. It compiles successfully but so far I haven't had time to test if the phone works with it flashed, and I really need some sleep now.
What needs to be done now is:
-Get a reliable way to unlock the bootloader.
-Test the kernel as it is now.
-Start development of modified kernels.
-Think of what should be done afterwards.
Anyone and everyone is more than welcome to help (specially since I'm mediocre dev and things will take forever with only me working)
Reserved
you mention getting the bootloader unlocked, but is that only to get TWRP on there or allow kernel changes? i have TWRP, supersu, but still have a locked bootloader... I have been wanting to make some real changes on this phone
stonerphoner said:
you mention getting the bootloader unlocked, but is that only to get TWRP on there or allow kernel changes? i have TWRP, supersu, but still have a locked bootloader... I have been wanting to make some real changes on this phone
Click to expand...
Click to collapse
I'm not sure you will be able to edit the kernel partition with a locked bootloader.
My phone decided that it would accept having the bootloader unlocked now and I don't really want to test relocking it.
And in other news, the compiled kernel works as supposed and my phone still boots after flashing it (had to repack the ramdisk from the stock kernel to make the boot.img)
let's try it for variant condor pgn-605 p8 the same as blu vivo xl but bootloader is already unlocked
i have bootloader unlocked i hope i can test it with rom like cm 13 as soon as one of you can make it for us
https://atozhacks.blogspot.com/2016/10/rommmhios-rom-for-gionee-splus-by-splus.html
i found this rom work perfectly
This might might provide some pretty useful references for me. Thanks @mwalid25!
And updating a bit, currently working on the device tree and proper ramdisk generation. As soon as I get results I'll upload it to github too.
Also, if anyone wants to help pester Blu into releasing the stock firmware too, that'd be appreciated since currently we depend on third party stock releases that I can't attest the integrity since I didn't bother comparing them to my stock firmware while I could.
Hey Guy's
So for my 626g I was experimenting with some custom roms. And I've came across this rom Viper OS V2.1 - 7.1.2 - PYTHON by Arkanium.
At first it was taking for ever to start at the first stept of setup... it asked for a backup or as a fresh start... and it doesn't matter if fresh or backup... continuous loop.
That's if you flash zip in recovery for gapps. If without gapps than all goes fast and without interruptions. But it's still in yearly stage and camera app not working... also phone service also the data... still lot's of bugs. If only someone could look at this build and maybe get all together. Thanks a lot for your support and work put in fixing lot's of builds and giving hope to our phones.
The link from where I found it .... getdroidtips.com/viperos-htc-desire-626g
Hello all!
I'm trying to play with Linux kernel source code for various reasons: e.g. add new feature to netfilter.
But i got problems even with pure "vanilla" kernel!
What i've do:
downloaded Google source code for Linux kernel
built it
copy to <rom_src_root>/device/google/coral-kernel (replacing old one)
make bootimage
adb reboot bootloader
fastboot boot <rom_src_root>/out/target/product/coral/boot.img
Touchscreen and Wi-Fi don't work at all.
I moved touchscreen driver to drivers/staging, make it compile, and after that touchscreen began to work.
So, how one can debug kernel with complete ROM flashing?
Do fastboot requires fully monolithic kernel, or i am doing smth wrong?
P.S. My first post here, don't sure where to place such kind of question
Hi!, I know this is from a while ago. Sorry sorry for disturbing you with this.
I'm facing the same issue.
Did you happen to find a solution for this?
eraxillan said:
Hello all!
I'm trying to play with Linux kernel source code for various reasons: e.g. add new feature to netfilter.
But i got problems even with pure "vanilla" kernel!
What i've do:
downloaded Google source code for Linux kernel
built it
copy to <rom_src_root>/device/google/coral-kernel (replacing old one)
make bootimage
adb reboot bootloader
fastboot boot <rom_src_root>/out/target/product/coral/boot.img
Touchscreen and Wi-Fi don't work at all.
I moved touchscreen driver to drivers/staging, make it compile, and after that touchscreen began to work.
So, how one can debug kernel with complete ROM flashing?
Do fastboot requires fully monolithic kernel, or i am doing smth wrong?
P.S. My first post here, don't sure where to place such kind of question
Click to expand...
Click to collapse