Q&A for [COLLECTION] Somcom3x's Experimental Corner
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [COLLECTION] Somcom3x's Experimental Corner. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Multirom TWRP
Somcom3X said:
Hello there!
Welcome to my custom build thread. Here you'll find most of the things I am currently working on.
This is where all of the unofficials/experimentals will go! Enjoy!
Recovery downloads:
TWRP-v2.8.3.0 (Loads much faster/with full selinux support)
TWRP-v2.8.2.0
TWRP-v2.8.0.0 (No throttling commits within)
TWRP-v2.8.0.0
CyanogenMod Unofficial Downloads (Newest to Oldest):
cm-12-20150107-UNOFFICIAL-peregrine
cm-12-20150105-UNOFFICIAL-peregrine
cm-12-20150103-UNOFFICIAL-peregrine
Older CM Builds:
cm-12-20150103-UNOFFICIAL-peregrine
cm-12-20141229-UNOFFICIAL-peregrine
cm-12-20141227-UNOFFICIAL-peregrine
cm-12-20141226-UNOFFICIAL-peregrine
cm-12-20141223-UNOFFICIAL-peregrine
cm-12-20141217-UNOFFICIAL-peregrine
cm-12-20141214-UNOFFICIAL-peregrine
cm-12-20141213-UNOFFICIAL-peregrine
cm-12-20141211-UNOFFICIAL-peregrine
cm-12-20141207-UNOFFICIAL-peregrine
cm-12-20141130-UNOFFICIAL-peregrine
cm-12-20141126-UNOFFICIAL-peregrine
cm-12-20141123-UNOFFICIAL-peregrine
Enjoy!
Click to expand...
Click to collapse
Hi Somcom3X, do you have any plans to build a Multirom capable TWRP recovery? I know this would also need an appropriate kernel with kexec to work. I have seen one for falcon, but not peregrine.
Can any one confirm SD support with the latest twrp? Does it format cache properly?
CM auto-update not working
my cm12 can't update automatically,
stops in main menu ...
someone else remark the same problem?
Please compile!
2.8.5.0 is out...
and repair the problem witch cm12 ota-updater
... Waiting for someone who compile it for peregrine...
Thankyou for TWRP-v2.8.3.0. My Moto G LTA (xt1040) Loves it!! (now i can use the sd card and OTG)
(hope you keep with future updates of TWRP)
Xplorer4x4: Yes works the SDcard. Disabling the Mttp suport on mount options, fix the problem .
2.8.6.0 is possible... But nobody build it for peregrine...
2.8.3.0 works not automatically with cm12 at my peregrine...
send with tapatalk...
"Google Play services stopped" and "android.process.acore stopped", these messages appear to me , and I can not open all applications
Thank you for this rom
..
---------- Post added at 02:18 AM ---------- Previous post was at 02:14 AM ----------
Excellent rom, so far it has solved many problems. I tested it with a lot of videos which looked slow in CM12 so far I haven’t had any closing of apps, I compare it about speed with Google Play Edition 5.1 XT1032. Excellent job, but I still find this line in the file built.prop, use.voice.path.for.pcm.voip=true, which has to be deleted on each update of CM12 for calls via WhatsApp, Line, Viber, etc. Again, good job and thanks.
MarcoAurelioBrasil said:
"Google Play services stopped" and "android.process.acore stopped", these messages appear to me , and I can not open all applications
Click to expand...
Click to collapse
This is because of Google contacts being messed up.
Disable, erase data and enable back did it for me.
mcastagnaa said:
This is because of Google contacts being messed up.
Disable, erase data and enable back did it for me.
Click to expand...
Click to collapse
Tnx,this was because I did a dirty flash, after I made a wipe data, sistem, cash, dalvik cash and internal , everything worked fine !
I just updated my XT1040 with the recently leaked OTA for 5.1 and wanted to root it again, so I used the TWRP-v2.8.3.0 in this thread.
as I went into recovery I was scared because yet again that now traumatic weird horizontal transparent line happened. From trying to get CM12 to work multiple times and failing I thought it meant I had ****ed up. Fortunately the recovery seemed to work fine, SD card and OTG visible and all. What caused this?
TWRP and PA and on Peregrine XT1039
TWRP ver.2.8.3
Paranoid Android ver.5.1
Thank you to all the developers they work together very well and give full access to sd card (TWRP).
Somcom3X many thanks for your work ...
Working fine on xt1039
The latest recovery is working on my XT1039, but I can only install zips via flashify - trying to install directly from TWRP causes my phone to crash completely. I also cannot access recovery from the bootloader, yet I can access it with either "adb reboot recovery", or advanced rebooting into recovery.
This is fine, although flashify only offers 3 flashes per day - which was a pain, but the latest Sabermod version no longer has a Google play services glitch so this is alright. P. S. This is on 5.1, which you say you don't support.
Good job for having a working recovery, I hope you can fix those two glitches!
Hey I've been using twrp for almost a year now but 3 days ago it stopped succesfully updating cm12.
I don't know whether that is a twrp issue or cm12 so I flashed the latest twrp from this thread without encryption.
The same error still occurs though.
Code:
E: Error executing updater binary in zip '/sdcard/cmupdater/cm-12.1-20150724-NIGHTLY-peregrine.zip'
tsaber said:
Hey I've been using twrp for almost a year now but 3 days ago it stopped succesfully updating cm12.
Click to expand...
Click to collapse
On peregrine you need bootloader 41.1A since
https://github.com/CyanogenMod/andr...mmit/50bd8f55e8c14b8a22fdf646e186dc279ddb08e9
sevenrock said:
On peregrine you need bootloader 41.1A since (SNIP)
Click to expand...
Click to collapse
Where do you get and how do you install the new bootloader?
I found a thread with a Windows-only tool to automatically install an updated bootloader for falcon or peregrine devices but do not have a Windows computer to use it.
Partition SD Card button is missing
Hi,
I flashed TWRP 2.7.8.0 on my XT1039. Everything seems to work except that there is no "Partition SD Card" button in the Advanced screen (there is a void where the button is supposed to be). TWRP sees the SD just fine and I had no problems making a backup on the SD card. Why is the button missing/hidden?
Regards,
-Roger
I have been flashing this afternoon trying to find a ROM that meets the following needs (without going into too much detail), but have not been able to find one that will will work without bootloops.
Basically, I am looking for a CM12 5.0 ROM that supports the AK kernel with working encryption. BlissPop has been badly buggy for me since late February, and I just tried with Temaseks 8.8 (last android 5.0.X version, still supports exposed) twice. First time tried to encrypt after flashing latest AK kernel and UKM zip, but my OPO would just reboot without encrypting. Then I tried flashing on a new clean install after encryrpting, and got a bootloop. I have also tried this on some other ROMs, even some F2FS ones but it didn't work (I don't think encryption works with F2FS).
Any help would be greatly appreciated. I can give more details as necessary. I never post on XDA, but I am by no means a novice to Android or flashing.
Hello and thank you for viewing my thread!
To start, my device is the OnePlus One, and i am running the latest Release of CyanogenMod 13 with the Latest Lightning Kernel for it's kexec/hardboot patch
I have tried multiple times, installing the multirom files, as well as flashing a factory image and flashing from a fresh install. Nothing seems to work.
The exact problem would be, even after performing the inject boot sector action, multiboot or the boot menu fails to appear.
I have no idea how to view kernel logs or anything of the sort. However i will gladly provide any logs or files if needed! Ill just have to figure them out is all.
Any help is greatly appreciated. Thank you in advance!
Edit:
1. I think i have the kernel ruled out as the problem as i have already tried a modified stock kernel, as well as bouffla's kernel.
2. The rom also doesnt seem to be the problem as i have tried both COS 12.1 and CM 13
3. The recovery seems to be ruled out as well. I rolled back to a previous version of TWRP and still have the same issue, no multiboot menu after proper installation.
4. This is really confusing. I even tried using the files built into the multirom manager application and that fails as well.
P.S. (on a semi-unrelated note)
I currently have a strong feeling it is a very low level issue (at least for my experience) due to the fact that kali nethunter is also failing to install and causing my device to brick every time i attempt an install.
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!
Just signed up here first post to the threads but you guys been helping me out for years different devices programs huge thanks to everyone here.
New to this device I'm starting to really dig it ran couple stable 8.1 ROMs got magisk+systemless xposed running. I previously dualbooted lineage nougat with stock on my droid bionic using safestrap(wanted to add a gingerbread) before getting this phone. I flashed the Multirom Twrp but app said I was having kexec kernel issues then ended up bootlooping os or getting black screen few times ended up just full reflashing cm firmware putting regular twrp back up.
Seen video of multibooting many ROMs( but I assume older non Oreo ROMs) and Ubuntu touch from a flash drive. Is it possible for me to bootup with a safe stock, ubuntu, and a 8.1 ROM(read Aosp extended is compatible but couldnt flash a kernel on top of it)? Couldnt find stock cm 6.0.1 bacon zip was gunna try and flash think it was ap kernel again over that but I tried a couple kernels didn't know which one was the right one.
Is there any newer Multirom alternatives or proper current kernel patch link? Does EFI droid work better could I still get ubuntu? Any advice would be appreciated pointers in the right direction tried to do some digging trying to really superpower my device if I can before I log into my all apps and stuff again. Is this a wild goose chase? Or was I like one step away