Database Develop

[Q&A] [ROMS][SGH-T679]Mass CM Thread

Q&A for [ROMS][SGH-T679]Mass CM Thread
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

I noticed that the kernels are linked separately from the ROMs. Am I supposed to download and flash the kernels separately? I've flashed about half a dozen ROMs, but I've never flashed a kernel before. From what I've read, though, it sounds like following the same procedure. How about GApps? Do I need to download and flash those, too? And, if so, which pack should I use?

fajrero said:
I noticed that the kernels are linked separately from the ROMs. Am I supposed to download and flash the kernels separately? I've flashed about half a dozen ROMs, but I've never flashed a kernel before. From what I've read, though, it sounds like following the same procedure. How about GApps? Do I need to download and flash those, too? And, if so, which pack should I use?
Click to expand...
Click to collapse
Roms come with a kernel the kernel linked is just special some have overclock under volt etc etc.
Explains the kernel options.
If you do flash them do it after rom.
Gapps you dont technicly have to but yes. (for a standard setup flash gapps)And there should be a gapps linked at the start of rom. If not there will be soon.

Can't import contacts from SIM
Thanks! That clears up a lot.
I installed CM, and it looks very cool and smooth. But when I tried to import contacts from my SIM card, it said "No contacts". I thought maybe it was because I hadn't installed GApps, so I downloaded the "small" GApps package linked from the CM wiki and installed it from CWM. Still no contacts on the SIM card. Next, I thought that maybe my contacts actually weren't on my SIM for some reason. So, I booted back into CWM recovery and restored my previous system. Then, from the phone app, I went to Import/Export > Manage SIM card contacts. Sure enough, all of my contacts were there.
It seems like CM isn't reading my SIM. Any idea what's causing this?
Edit: Never mind. I found out that newer versions of Android don't allow you to store contacts locally. Somehow, the contacts got silently added without me having to import them, though. That's odd, because I don't remember allowing Google to store them in the cloud, and the SIM card appears blank... Oh, well, I installed MyLocalAccount, so I'll see if I can store the contacts locally that way.

@cars1189 running 10/18 build with 10/19(PAgapps micro) and 9/9k^k UV vhm kernel and have had no issues! Thanks for the great work, this runs solid and smooth!

I recently installed 10.2 and am loving it so far. One thing I ran into though was that the cLock widget was showing lots of wakelocks, so I disabled it and battery life has been great. Haven't run into any other issues (other than the screen staying on when off and charging), so this one is a keeper for me.
Didn't see this problem with 10.1, so curious if this is a known issue or not with the cLock widget? Also, are there any other planned updates coming for 10.2?
Thanks.

@RobbyG2112 I noticed it too when I was on 10.2 how ever I only ran it for a week maybe b4 going to cm11 I will say not sure if cars will update 10.2 but if you haven't tried cm11 its super stable and gets updated monthly!!

Thanks for confirming canodroid15, I wasn't sure what the lock screen would show when I disabled the widget but it put the default digital clock and date in it's place so it works out ok. I had disabled the weather and alarm widgets also so wasn't sure why having only the clock widget would cause wakelocks.
I'll probably get around to installing CM11 next, I'm a little slow on upgrading. I had been using CM10 for a long time and finally got tired of seeing the green preview pictures every time I used the camera so decided to go to CM10.1/10.2 recently.

Sure man, about the wakelocks you can try to catch it in a log. Enjoy 10.2 bro!!

kernel for cm11 (SGH-T679)
I recently installed @cars1189's CM11 10-4-14 build for the SGH-T679, with kernel 3.4.104-cyanogenmod-gda4bf58. It took a few tries, but it finally succeeded.
However, there's a slight issue in that I can't access my SIM card contacts. When I try to import from the dialer, it says "no contacts." I've searched around these threads and on the internet, and it seems that it is an issue with the kernel. Would it be possible for someone to recommend or point me to a compatible kernel that would fix that issue for me? Thank you so much for your help!

@valmeras I really don't think it has anything to do with the stock cm kernel but if your on 10/4/14 you can flash 9/9k^k kernels safely on that build about sim contacts idk I use my Google account to sync my contacts hope this helps good luck!
Edit: look for the rom & kernel dates/links in OP.

@canodroid15 - thanks for the response and suggestion. I'll give that kernel a try in the next few days. Not sure this is the solution, but hopefully that works. I've also seen some reference to SIM Tool Kit (STK), but I wasn't able to figure out if it that was the issue.
I would definitely use Google for syncing the contacts once I get this fixed, but for now, that's not possible because my phone is not able to read the SIM properly. I've tried saving a contact to the SIM, but I get an error like "unable to write, SIM is full" but I know for sure that's not the case. Alternatively, I might try to revive my old dumb phone and try to retrieve the contacts that way, then hopefully export that in some way.

@valmeras no prob man, if you have contacts on your sim and u put the sim in the dumb phone and export to storage u could then send a vcard via Bluetooth to the exhibit go into contacts and import from storage then Google sync good luck let me kno if u get it

So I flashed the kernel, but that didn't fix my issue. I do have some more free RAM now though
My old phone doesn't support exporting multiple contacts/vcards via bluetooth, but fortunately, Motorola has a contact exporter utility that exported everything into a CSV file to my laptop via USB. I had to install the drivers for the old phone to be recognised first. I was skeptical it would work given it was a new all-in-one driver thingie and my Motorola was quite old, but somehow it did! The whole process took several hours, but my contacts are now synced!

Sensors/rotation problem
Thanks for posting these ROMs! I just upgraded from Peach Sunrise and I'm really impressed with how well CM11 runs on this phone.
I want to report a problem I had and my solution for the next guy's benefit. With the latest 12-9-14 CM11 ROM, my sensors and compass didn't work correctly. The biggest symptom was auto-rotation did not work at all. Downgrading to the 9-9-14 ROM fixed everything. I didn't try any other ROMs, so they might work too.

Question about getting Google apps running on a SGH-T679
I installed CM 10.2 (cm-10.2-20140627-UNOFFICIAL-ancora_tmo) and it worked fine. I tried a couple different gapps downloads (doing a reinstall of CM10.2 between tries although I may have done that step incorrectly). But no matter what 4.3 gapps build I tried, Google Play Services would crash.
My main goal is to get to 4.3 or higher, so CM 10.2 or CM 11 would be great. (I'm open to other ROMs too. The only reason I'm choosing CM is because those are the only ROMs indicated as still maintained here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G )
My question is whether anyone has either CM version running on a T679 and which gapps did you use? I nearly bricked my phone and would like to know that someone else has gapps running okay before I try again.
Thanks!
EDIT: I followed the 2 following threads to install CM 11 with the PA pico gapp package and added a few other Google apps manually from the Play store. I also made sure to reboot several times to make sure everything got fully initialized.
http://forum.xda-developers.com/showthread.php?t=2542793
http://forum.xda-developers.com/showthread.php?t=2397942

masteff said:
Question about getting Google apps running on a SGH-T679
I installed CM 10.2 (cm-10.2-20140627-UNOFFICIAL-ancora_tmo) and it worked fine. I tried a couple different gapps downloads (doing a reinstall of CM10.2 between tries although I may have done that step incorrectly). But no matter what 4.3 gapps build I tried, Google Play Services would crash.
My main goal is to get to 4.3 or higher, so CM 10.2 or CM 11 would be great. (I'm open to other ROMs too. The only reason I'm choosing CM is because those are the only ROMs indicated as still maintained here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G )
My question is whether anyone has either CM version running on a T679 and which gapps did you use? I nearly bricked my phone and would like to know that someone else has gapps running okay before I try again.
Thanks!
EDIT: I followed the 2 following threads to install CM 11 with the PA pico gapp package and added a few other Google apps manually from the Play store. I also made sure to reboot several times to make sure everything got fully initialized.
http://forum.xda-developers.com/showthread.php?t=2542793
http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
Hey man! I hope you got it figured out! The only Gapps I use are PA Gapps! There are others but PA is the most complete package & has many options "IMO". You need to use a package that will fit your phone I use the micro package, or the nano. You need to use a package that matches your ROMs version, if your on 4.4.x then use 4.4.x Gapps. If on 4.3 use 4.3 Gapps. PA Gapps has a 4.3 package but its hard to find if you don't know where to look. 4.3 package can be found in the devs (Tkruzze) files on android file host, same place as the 4.4.x Gapps! Sorry if you didn't get answered b4 this I haven't been on this thread for weeks it seems! Hope this helps

So I've been trying out the CM11 OS2SD ROM (the last one in December), but I need to switch back as the bugs are just too much. I need my phone to work and stay charged, which is not happening on this ROM. And since it looks like CM12 is being worked on now that it's not likely the bugs in CM11 OS2SD will get fixed any time soon.
So first the problem. My USB socket on the phone is a little iffy, so I know that is where most of the problem is coming in. However, on the CM11 OS2SD ROM I'm using right now (the one dated 12/25) it frequently says it is plugged in, but is not charging. I've actually seen times where the battery monitor I'm using shows it has discharged the battery as much as 20% before I caught it, yet the status bar battery icon shows it as full and plugged in. On the older ROMs it didn't do this, so something isn't right with how the ROM handles the charging circuits in the phone. Plus, I've had frequent periods of "cpu hogging" (massive CPU load that doesn't seem to come from any one source and that doesn't seem to show up in OS Monitor) that can end up in a crash-reboot of the phone.
So as a result, I want to switch back to an older version of the CM11 ROM. I was using one of the November builds for quite a while, only having to put up with an occasional crash-reboot (the current ROM seems to do this at least every other day, the older one could go a whole week and maybe have it happen only once). What is the process to undo what was done to the phone for the OS2SD build to be loaded?

can't install
I have a problem after installing it via cwm and rebooting, the ensender shows me a screen where I order a factory reset but when I was I do not ensiende the phone

CM 12 Android is upgrading every boot
Ever since I flashed Cyanogenmod 12 every time I reboot it says "android is upgrading optimizing app 1 of 1" and it takes about 8 minutes. There are no odex files in data/app so that cant be the problem. Someone please help. The first time I flashed CM 12 I wiped data and factory reseted but since i seen this happen I flashed Cm 12 again but this time I formatted System, Data, Boot, and SDcard 0 but it still seems to happen. Also, recently my phone has been shutting off by itself every time I turn off the screen. And I know this isn't a hardware problem because the phone never turns off while music is playing with the screen off. It didn't start happening with CM 12. It was already happening with CM11 but it only started happening about a week ago. Im really thankful for cars1189 working on the rom and anyone else who worked on it. You guys are great. Hopefully you can help me out.

Is there any OS that works ?

Hello .... I'm finding whatever OS I'm trying becoming unstable to use . So, I'm asking if there is any OS that is actually stable enough to use . I don't care whether it's an old version or what . I'm not using the tablet for games, just something I can browser the internet with . TIA

The one that has given me the fewest issues is https://forum.xda-developers.com/showthread.php?t=2712680 [ROM] [4.4.4] [CyanogenMod 11 by Jcsullins] [DM] [06/12/15]
everything works extremely well except the DSP manager when adjusting audio settings for the built in speakers where changes beyond the defaults do not have any effect on the audio.
Sadly many of the links are dead for things like gapps.
The ROM I use is cm-11-20151116-SNAPSHOT-jcsullins-tenderloin.zip
The gapps I use is: gapps-444-base-20160802-1-signed.zip
If needed, I can upload the gapps that I use though I am unsure if the forum has any rules surrounding it if I were to upload them to something like dropbox.
I try the others from time to time (easier for me since I really only use BSplayer and chrome in order to watch videos in a hover window while surfing the web (occasionally using my Bluetooth speakers or headphones).
Anyway, the main reason why I keep coming back to it, is the memory management. For many newer ROMs, you have issues such as the google calendar widget not working,or chrome not working properly, or when it is working, frequeny memory issues, especially if you want to upload an image to a site where it switches to the gallery app. by the time you select an image, it would fail to attach it because it will complain that the previous action could not be completed due to low memory.
With android 4.4, I do not have that issue. I don't know why it keeps happening for me since there are times when there will be over 100MB of free RAM, and chrome will still fail to do things with that error message.
Beyond that, the home screen under android 7.1.1 does not hold as many icons or widgets, even if you set the screen size to small, or adjust the dpi to 120. the home screen holds fewer icons and fewer widgets.
Overall, while it si great that newer versions of android are being supported, I feel that from a hardware standpoint then tablet has reached its limit with android 4.4
While there is also an evervolve version of android 4.4, for some reason it does not perform as well, even with more kernel features such as being able to overclock past 1.78GHz. it takes longer to boot, and some widgets do not work, along with issues with chrome.

https://forum.xda-developers.com/showpost.php?p=71176374&postcount=937
Check out the Nougat Evervolv thread. I've been using it, and it's fantastic.

Thanks for your input Razor512 .... And crazyates : Has this been updated since its first release, because when I gave it a go it was very unstable

Dude905 said:
Thanks for your input Razor512 .... And crazyates : Has this been updated since its first release, because when I gave it a go it was very unstable
Click to expand...
Click to collapse
Yes it has, but you need to download the nightly from their website. The XDA thread has an older version.
http://evervolv.com/devices/tenderloin

Ok, great news there crazyates. I installed evervolv from the YouTube guide, Do you know whether it still will work with those methods in the guide just as long I replace it with
ev_tenderloin-7.1.1-nightly-2017.03.03.zip and I believe you are using gapps-511-base-20161007-1-signed.zip , yes ? Thanks
YouTube >>> https://www.youtube.com/watch?v=ISWZ0c48gNA

Dude905 said:
Ok, great news there crazyates. I installed evervolv from the YouTube guide, Do you know whether it still will work with those methods in the guide just as long I replace it with
ev_tenderloin-7.1.1-nightly-2017.03.03.zip and I believe you are using gapps-511-base-20161007-1-signed.zip , yes ? Thanks
YouTube >>> https://www.youtube.com/watch?v=ISWZ0c48gNA
Click to expand...
Click to collapse
I'm not sure about the Youtube instructions, and I followed the written instructions on the forums.
Also, IIRC, if you're using a 7.1.1 ROM, you can't use a 5.1.1 Gapps. I would recommend downloading the newest 7.1.1 Gapps.
Here are the instructions I followed:
AlwaysLucky said:
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files to the install folder after the TP is mounted
4. When given the option to adjust partition sizes, increase the System partition to at least 1312mb
5. Finish install, and reboot to TWRP
6. While in TWRP, flash the 9/6/16 TWRP 3.0.2.0 or the smaller 9/11/16 TWRP 3.0.2.0
7. Reboot into the new TWRP that you just flashed
8. In TWRP advanced wipe menu, wipe the System partition
9. While still in TWRP, flash the ROM from the OP along with some OpenGapps
10. Worship @jcsullins and @flintman, as they are your gods.
Click to expand...
Click to collapse
Here are the changes/differences I made/noticed:
crazyates said:
Step 3: While you're copying the older ROM/Gapps/TWRP into the "ttinstall" folder, I also copied everything you need for the new install into an "evervolv" folder. This way you can copy everything at once, and formatting a volume in TWRP doesn't destroy your install files.
Step 4: I have a 32GB TP, and don't use hardly any of it, so I increased the System to ~2GB, and the Cache to ~1GB. I figured going on the big side couldn't hurt.
Step 6: There's a newer version of Flintmans TWRP, 3.0.3.0(12/22/16).
Step 8: After you wipe the System, reformat the Data and Cache volumes as F2FS. Because your install files are on the External_SD instead of the Data, you can do this without recopying your install zips back again. I installed the system twice, once with Ext4 and once with F2FS. It feels snappier, and runs a lot better with F2FS.
Step 9: I used the Nightly build for the ROM, which is working great. Then the newest Gapps. Then I also flashed the SKZ overclock kernel at the same time.
Few other notes: Changing the Governor to LionHeart and Scheduler to Tripndroid made a noticeable difference for me. Also, because this doesn't have a lot of RAM, I gotta be careful with what I install, and how much I try to use it. Do NOT install Chrome from the app store. It will eat every bit of RAM available, and slow the whole thing down. I also use Greenify (with root permissions) to hibernate any app I can so it saves a lot of RAM that was as well. I'm using ~329MB (40%) for the system, with ~500MB (60%) available for apps.
Click to expand...
Click to collapse

@crazyates Did you try Evervolv 7.1 nightlies? I'm curious to read your experience feedback because I'm on it and getting tired of always having a non-responsive tablet. I might go back to 4.4 as I'll go mad otherwise.

bobcote said:
@crazyates Did you try Evervolv 7.1 nightlies? I'm curious to read your experience feedback because I'm on it and getting tired of always having a non-responsive tablet. I might go back to 4.4 as I'll go mad otherwise.
Click to expand...
Click to collapse
I am running the 7.1.1 nightlies. I haven't had any problems, and it's running very smooth. I'll randomly update it to the newest nightly, and haven't noticed any issues.
I do remember the time I first installed Evervolv 6.0 nightly last year. I installed it, and the touchscreen didn't work. At all. Looked into it, and it was a problem with that specific nightly build, so I went and reflashed everything with the one from the day before, and it worked great.
Anyways, all that to say it's working great, but it's still a nightly, so sometimes things go wonky.

I am still running a really old ICS build, and I noticed i can't update all my apps no more... what is the best Android version to run on the TP. Bluetooth is a must, but Camera isn't. Heard good things about 4.4.4 and 7.1.1, which one would you guys say runns smoother?

wprpalmeida said:
I am still running a really old ICS build, and I noticed i can't update all my apps no more... what is the best Android version to run on the TP. Bluetooth is a must, but Camera isn't. Heard good things about 4.4.4 and 7.1.1, which one would you guys say runns smoother?
Click to expand...
Click to collapse
Can't say much for 4.4.4, but I'm using 7.1.1 and it's great!
The only argument I could see making for 4.4.4 is if it runs a bit lighter than 7.1.1. These only have 1GB of RAM, so if 4.4.4 is capable of using less RAM for the android system, that means more RAM for apps. On the flip side, 7.1.1 uses such things as zRAM and KSM for better memory management, so it may be a wash.

crazyates said:
Can't say much for 4.4.4, but I'm using 7.1.1 and it's great!
The only argument I could see making for 4.4.4 is if it runs a bit lighter than 7.1.1. These only have 1GB of RAM, so if 4.4.4 is capable of using less RAM for the android system, that means more RAM for apps. On the flip side, 7.1.1 uses such things as zRAM and KSM for better memory management, so it may be a wash.
Click to expand...
Click to collapse
yeah, this is what I want to figure out. The developments in the Android codebase were quite extensive between these two releases, and the huge influx of budget phones in some markets (like mine for example) lead me to believe memory management would have been a key point in developing versions after 4.4.4. I'll give 7.1.1 a whirl and see how it goes.

Here are the instructions I followed:
...
Here are the changes/differences I made/noticed:
Click to expand...
Click to collapse
I tried to follow your instructions, but I get error messages like:
Error: unrecognized/unsopported zip 'FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip'
Error: Incompatible GAPPS/ROM versions None/7.0
I used the latest nightly (ev_tenderloin-7.1.1-nightly-2017.03.08.zip) and tried both open_gapps-arm-7.1-pico-20170312.zip and open_gapps-arm-7.1-pico-20170312, also I tried some of the TWRP-Versions you linked. I'm using TPToolbox v42 2015-01-08). So I wonder how you can figure out which versions fit together, I can remember this nagged me last time until I found a combination that worked...

AlwaysLucky said:
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files to the install folder after the TP is mounted
Click to expand...
Click to collapse
Flexmaen said:
I tried to follow your instructions, but I get error messages like:
Error: unrecognized/unsopported zip 'FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip'
Error: Incompatible GAPPS/ROM versions None/7.0
Click to expand...
Click to collapse
Was that error message from TP Toolbox, or from TWRP? TP Toolbox won't recognize the newer TWRP images, nor will it recognize any 7.1 ROM/Gapps, so you need to use an older version to get things started. Once the older TWRP is installed, then you can use it to update to a newer version.
All in all, I had 8 ZIP files on my HP Touchpad to get a complete 7.1.1 install, but you can do it with as few as 6:
OLD ROM: CM 12.1
OLD Gapps: 5.1
OLD TWRP: 2.8.3.0
NEW ROM: Evervolv Nightly
NEW Gapps: 7.1
NEW TWRP: 3.0.3.0 F2FS
SKZ Kernel (Optional)
SuperSU (Optional)

Thank you! I installed the latest nightly, and it works fine so far.
The only thing I noticed that some apps now are blocking the device. This was also the case with the Android 4.4 Pac-Rom I used before. So it seems that some apps are using recources that aren't working well on the Touchpad at all, or that there is a general problem in several CM-versions.
For example the current version of Google Maps is so slow, you won't use it. I installend an older version (7.7.0), and this one works very fine. Also the new version of Maps lost the WiFi connection, which didn't cause any problem with the older version. So I wonder if there is some kind of incompatibility.
Another example: Fake GPS Location is much quicker than GPS-Emulator which also got stuck from time to time. Also the current Amazon App store was slooow.
Summary: Android 7.x runs fine so far, but you have to make sure that you get rid of the apps which block the device for some reason.

7.x is very slow some times.
Flexmaen said:
Thank you! I installed the latest nightly, and it works fine so far.
The only thing I noticed that some apps now are blocking the device. This was also the case with the Android 4.4 Pac-Rom I used before. So it seems that some apps are using recources that aren't working well on the Touchpad at all, or that there is a general problem in several CM-versions.
For example the current version of Google Maps is so slow, you won't use it. I installend an older version (7.7.0), and this one works very fine. Also the new version of Maps lost the WiFi connection, which didn't cause any problem with the older version. So I wonder if there is some kind of incompatibility.
Another example: Fake GPS Location is much quicker than GPS-Emulator which also got stuck from time to time. Also the current Amazon App store was slooow.
Summary: Android 7.x runs fine so far, but you have to make sure that you get rid of the apps which block the device for some reason.
Click to expand...
Click to collapse
When you say "blocking" you mean very slow? Since I uptaded from 4.4 to 7.x I've noticed that lots of apps are very slow. Some freezes for seconds and returns only when I block the device and turn on again. I dont know if its only on mine or its normal because of the old hardware. Is there any version that run real smooth? Or other system?

giolc90 said:
When you say "blocking" you mean very slow? Since I uptaded from 4.4 to 7.x I've noticed that lots of apps are very slow. Some freezes for seconds and returns only when I block the device and turn on again. I dont know if its only on mine or its normal because of the old hardware. Is there any version that run real smooth? Or other system?
Click to expand...
Click to collapse
Yes I mean very slow. Often so slow that it takes a minute until you can change to another app.
The Problem also existed on my 4.4 Pac Rom, so I guess it's rather caused by new apps who might expect some feature, like multicore, etc. Or it is some fault, that already existed in older custom roms. Not sure. However, I can recommend downgrading apps in this case, older versions often work like normal.

Flexmaen said:
Yes I mean very slow. Often so slow that it takes a minute until you can change to another app.
The Problem also existed on my 4.4 Pac Rom, so I guess it's rather caused by new apps who might expect some feature, like multicore, etc. Or it is some fault, that already existed in older custom roms. Not sure. However, I can recommend downgrading apps in this case, older versions often work like normal.
Click to expand...
Click to collapse
Perhaps using F2FS could help, if not currently using it?

crazyates said:
Was that error message from TP Toolbox, or from TWRP? TP Toolbox won't recognize the newer TWRP images, nor will it recognize any 7.1 ROM/Gapps, so you need to use an older version to get things started. Once the older TWRP is installed, then you can use it to update to a newer version.
All in all, I had 8 ZIP files on my HP Touchpad to get a complete 7.1.1 install, but you can do it with as few as 6:
OLD ROM: CM 12.1
OLD Gapps: 5.1
OLD TWRP: 2.8.3.0
NEW ROM: Evervolv Nightly
NEW Gapps: 7.1
NEW TWRP: 3.0.3.0 F2FS
SKZ Kernel (Optional)
SuperSU (Optional)
Click to expand...
Click to collapse
I guess there is a "new" method out there that can install Nougat 7.1.1 in as little as 3 zip files!!!
check it out, it comes with instructions and a new video...
I can name that tune in 3 zips!!

DoubleStuff said:
I guess there is a "new" method out there that can install Nougat 7.1.1 in as little as 3 zip files!!!
check it out, it comes with instructions and a new video...
I can name that tune in 3 zips!!
Click to expand...
Click to collapse
It doesn't work for me ... I'm having issues . First off I like to ask why he didn't use the latest Rom ? And the part with go to the PC Mounted Touchpad internal drive for the TWRP ? When I open the TWRP folder I don't see twrps file, why not ? There nothing in this folder, its empty . What I done was just placed those zip files in the TWRP folder . Afterwards once I do the final reboot to Evervolv it will just show those Evervolv lights flashing like its trying to load up but it doesn't, it just keeps continuously trying to load but it never does

Problem with lockup / display not turning on across various roms, rooted droid

I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!

What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.

thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks

Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL

MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.

[ROM][XZ][P][9.0][WEEKLY]OmniROM

XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31

Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs

I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.

Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)

XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.

sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad

opps

I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?

Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.

KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p

Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.

oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.

Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx

Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving

KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread

Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.

XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/

KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated

Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official

anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem

Just ordered razer phone 2 looking for custom os instructions.

So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.

SynGreis said:
So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.
Click to expand...
Click to collapse
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:

which one do you suggest? i dont see much of a selection.

SynGreis said:
which one do you suggest? i dont see much of a selection.
Click to expand...
Click to collapse
Right now there really aren't any, although there are a few in development, such as AOSP. I think the initial high price, specialized hardware & relative unpopularity has not helped attract any serious development.
I've noticed that ROM development has decreased significantly in the last few years. I remember the days of the Samsung Galaxy Nexus & the HTC Evo 4G where it seemed as if there was a new ROM released every week. I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult.

Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.

mattwheat said:
Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.
Click to expand...
Click to collapse
Mine showed as in rog 2 the last time I reloaded the OS. It's because it searches for "phone 2" and randomly guesses. No biggie, just fix it in the settings. No issues here from playstore, if you do it's common on every Android phone and fixable by clearing the data from the app. Maybe you should reflash the stock firmware? I don't see why you would call this phone ****ty. It's basically running AOSP stock except some theming from Razer. I fixed some freezing issues by reseating the Sim and SD card that I have. This thing rocks, just saying.

I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.

matt that might be just you i havent experienced any issues with this phone whatsoever.
"I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult."
can you provide more info on this A/B partition? id love to see what customizable stuff i can do with this.

mattwheat said:
I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.
Click to expand...
Click to collapse
The freezing is due to a bug in Google Chrome. All you have to do to fix this issue is roll back the app version to 72 because version 76 doesn't work on our RP2.
Edit: uncheck auto update

Only freeze I had so far was with the infamous switch switch to the tele lens. Not a single other issue with software.

Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?

MasterThiefGarrett said:
Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?
Click to expand...
Click to collapse
Take this with a grain of salt, as I just got the RP2, but its the most responsive, "sticky" feeling Android phone I've used. 120hz is like night and day to me.
On a related note, Firefox Fenix with webrender enabled feels significantly more responsive than Chromium atm, as it seemingly renders the whole page instead of stuttering as you scroll like Chrome.

JDBarlow said:
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:
Click to expand...
Click to collapse
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.

SynGreis said:
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.
Click to expand...
Click to collapse
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/

duplicate post

JDBarlow said:
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/
Click to expand...
Click to collapse
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/

SynGreis said:
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/
Click to expand...
Click to collapse
So are you on the global version? If so let it update to MR2 and fastboot flash boot arter97 r12 and you'll be just fine.
Which version are you running then to get stuck on boot logo?
Edit: if you want to stay on MR1 then flash arter97 r11

i tried updating to mr2 but says installation failed.
all i do is
faatboot flash boot kernal.img?

I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done

JDBarlow said:
I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done
Click to expand...
Click to collapse
My only question is, which version zip of magisk did you use in TWRP to flash? 20 or the latest beta? I'm rooted now with a modded boot.img that someone else used the canary/latest beta. Just don't want to screw myself and end up having to flash mr1 again then taking the update.