Debloated MM ROM for H631 / MS631 (TMP / MetroPCS) - LG G Stylo Guides, News, & Discussion

I don't have time to make a really awesome ROM like GameTheory did with Katana. However, I am debloating the MM ROM as much as I can. It is a slow process since I don't know what can't be removed because of dependencies. So, I have to make a backup in TWRP, remove some stuff and see if it blows anything up. If it does, I have to revert to my backup and try again.
When I am done, the only thing that will be installed is the play store, dialer, and any other crap that just can't be gotten rid of (for example -- I *think* the stock messaging app has to stay -- we will see). Bottom line, when I am done, it will be up to you if you use it to install anything that you want / need (for example a camera app). I will not be installing Xposed. If you want it, it is very easy to install. I want a ROM that is literally as stripped as possible.
Anyway, the reason I am posting this is to see if anyone else is working on this as well so we can share knowledge on what can / can't be removed.
If anyone else comes across this thread and knows of a better way to figure out what can be removed besides my trial / error / revert to a good image method, *PLEASE* let me know.
Thanks,
-- Brian

Following! BUMP!
Sent from my LGMS631 using Tapatalk
---------- Post added at 07:21 PM ---------- Previous post was at 07:18 PM ----------
@edubyah
Sent from my LGMS631 using Tapatalk
---------- Post added at 07:22 PM ---------- Previous post was at 07:21 PM ----------
How do we tagg another member?
Sent from my LGMS631 using Tapatalk

So, this process was taking an incredible amount of time because I was being a dumb ***. I had converted my SD to adoptable storage. Well, the version of TWRP that we have available to us doesn't understand adoptable storage, so I have having to use OTG to make my point in time snapshots.
This was moronic for a couple of reasons:
1 - You can create a mixed mode SD card. Part adoptable storage, and part portable storage. Now, you can't remove the card while the OS is booted (because of the adoptable storage on the SD card). However, you CAN remove it and use it as portable storage if you shutdown your phone. This *ALSO* allows TWRP to see the SD card again as external storage (at least the part that is NOT adoptable storage). So, no more having to use OTG. By the way, there is currently no way to do the split AS / PS (Adoptable storage / Portable storage) without dropping to a shell prompt, or using adb shell. I am working on a little app that will let you carve your SD card into part AS and part PS. The portable storage is great for apps that don't understand AS yet.
and that leads us to #2.
2 - I was using freaking Titanium backup to uninstall things and like I said, revert to a restore point if I blew something up. I found a MUCH faster way with adb. So I should have a completely debloated MM ROM this weekend. As an added bonus, I think I may be onto how to fix the secure boot BS so that we can lock our bootloaders back.... more tests to come.
-- Brian

Anything happening? Can't wait to try this out. You need a tester, just let me know.

stovo06 said:
Anything happening? Can't wait to try this out. You need a tester, just let me know.
Click to expand...
Click to collapse
Check out @Edubyah 's thread here: http://forum.xda-developers.com/lg-...lashable-update-6-0-mm-twrp-insecure-t3362853
Since he was already working on a debloated ROM, I am focusing my efforts on making us a recovery.img and boot.img that can be used without having to unlock your boot loader. I have a boot.img that allows me to boot with a locked boot loader, however, getting TWRP to cooperate is proving more of a challenge.
Anyway, for now, if you just need a debloated ROM, I am running @Edubyah 's and it is great.
As soon as I have a TWRP image that will let me boot with a locked boot loader, I will be posting it for everyone to try. As an added bonus, I am trying to add adoptable storage support to our TWRP. I don't mind having to go with a mixed mode SD card, but hey, it is nice to have options.
-- Brian

Well, this has me really excited: http://www.droidviews.com/sign-unlock-boot-images-lg-devices-bump/
The site is down that was supposed to do the automatic bump, but based on what I am reading there, it is a matter of taking a sha1sum of the image (recovery or boot) and appending it as a block to the image. That information alone at least gives me a starting point. My first try will be:
* Get block size of the images
* Take an sha1sum of each image
* append the sha1sum along with padding to create a proper size block
If that doesn't work, I will try putting the padding first, and then the sha1sum at the end of the block before appending.
-- Brian

Sorry to keep replying to my own thread, but this is here to help others and I think individual posts are better than editing previous posts...
So, that whole idea of creating a signed boot loader was a dead end. Hell it was a dead end a LONG time ago (feel free to Google on the massive drama behind it). Anyway, after running into a dead end it occurred to me that I was trying WAY to hard. We had a device that booted without unlocking the boot loader. We still have a device that is very easy to unlock the boot loader. So, I decided since Android is open source to read up on how Google suggests that people make their images so they can't easily be modified.... What I came across was so simple I will be floored if it works. Unfortunately I am at work so I won't be able to test this for a few hours.
Here is the build.prop from the LP boot.bin:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=boot
ro.adb.secure=1
wlan.lge.dcf.enable=true
wlan.lge.multisimaka=yes
camera2.portability.force_api=1
ro.zygote=zygote32
persist.sys.ssr.restart_level=ALL_ENABLE
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0
And here is the build.prop from MM boot.bin:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.adb.secure=1
persist.sys.usb.config=boot
camera2.portability.force_api=1
ro.zygote=zygote32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
ro.dalvik.vm.native.bridge=0
debug.atrace.tags.enableflags=0
persist.sys.ssr.restart_level=ALL_ENABLE
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Tue Feb 16 12:17:56 KST 2016
ro.bootimage.build.date.utc=1455592676
ro.bootimage.build.fingerprint=lge/g4stylusn_tmo_us/g4stylusn:6.0/MRA58K/1604712041b1a:user/test-keys
Notice anything different? It looks like all LG did was use build.prop to specify a fingerprint. I am 99.9% sure that when I remove the ro.bootimage.build.fingerprint line and make a new boot.bin we will be able to lock our boot loaders back. Also in the system build.prop there is:
Code:
ro.expect.recovery_id=0xf422d751348b9f37597f49c62958a13ed456b2dd000000000000000000000000
This one I haven't researched much yet, but considering it doesn't exist in the LP system build.prop -- I have hope.
If this is all info that was known, awesome -- it still gave me a chance to learn, and it isn't documented very well if it is known.
-- Brian

runningnak3d said:
I don't have time to make a really awesome ROM like GameTheory did with Katana. However, I am debloating the MM ROM as much as I can. It is a slow process since I don't know what can't be removed because of dependencies. So, I have to make a backup in TWRP, remove some stuff and see if it blows anything up. If it does, I have to revert to my backup and try again.
When I am done, the only thing that will be installed is the play store, dialer, and any other crap that just can't be gotten rid of (for example -- I *think* the stock messaging app has to stay -- we will see). Bottom line, when I am done, it will be up to you if you use it to install anything that you want / need (for example a camera app). I will not be installing Xposed. If you want it, it is very easy to install. I want a ROM that is literally as stripped as possible.
Anyway, the reason I am posting this is to see if anyone else is working on this as well so we can share knowledge on what can / can't be removed.
If anyone else comes across this thread and knows of a better way to figure out what can be removed besides my trial / error / revert to a good image method, *PLEASE* let me know.
Thanks,
-- Brian
Click to expand...
Click to collapse
Keep it up im working on a stoc based kernal with a few tweaks and mods but this is gonna be for h or ms631. Mm unlocked bl

Good luck to you both in your developing.
It is much appreciate for us T-Mobile/Metro Stylo owners.

Following
Sent from my LG-H631 using XDA-Developers mobile app

Related

cbackup v0.4 - backup/restore tool

I've been a lurker since I got my eris back when root was a dream. Now I have quite a few things floating around my work dirs that aren't on xda or are wanted, so I figured I would start releasing some of my better/more polished things. So here is my first:
cbackup v0.4
Based upon craft_backup v0.5.3: showthread.php?t=628743 (sorry no links)
Backup and restore apps/data just like craft_backup
Changes/Features of cbackup:
- Change names to cbackup and crestore because I got tired of typing out "craft_backup" and "craft_restore"
- Move backup dir to /sdcard/backups/cbackup/*
- For cbackup, allow a choice for destination in backup dir (defaults to cb<date>)
- For cbackup, automatically move backup dir to timestamped location instead of overwriting it
- For crestore, display menu of all cbackup dirs along with original craft_backup dir if it exists. This menu has the latest last, numbered first with number 1 being the default.
- Works with roms that don't have the busybox symlinks installed
Changelog:
v0.3
- First public release
v0.4
- Fix problem when missing bb symlinks
Disclaimer: I am not responsible for damage caused by this app. I take no credit for the good work done on craft_backup, I just wanted something it didn't do so I hacked it up to suit my needs. Eventually it became nice enough to share. I will not support it, unless there is something wrong with my added code (which is possible, since the listing code is complex). Refer to the original app's thread for almost all problems.
nXuaJunYYc
Testing it now.
EDIT: WORKS PERFECTLY- 5 STARS.
Crestore- not found.... help?
I assume you're running "crestore" and not "Crestore" nor "Crestore-". Can you post the output of:
echo "$PATH"
from adb shell?
If that's fine, I think I know what may be wrong, but try that first
edit:
I'll be uploading a new version in a minute that I think will fix your problems, but if it doesn't, if you could also try the following it would be helpful:
# which crestore
# which sed
# echo abc | sed -es/a/d/
# ls -l /system/bin/crestore
# ls -l /system/bin/cbackup
# /system/bin/crestore
So I got it to find it, but it says not found for everything. Also comes up in Italian no matter what, but no biggie.
or use the eris master app, which can do most of that right now. the good thing is that its in a gui interface. jamezelle and i will be adding additional features later for the backup / restore apps as well. and one thing that we will have shortly is the ability to restore market update links for apps installed outside of the market.
@ECLIPS3:
Sorry, I'm a command line guy and I'm a linux guy. I really don't want to install wine and mono on my poor little linux netbook just to run your app and then navigate a gui. Plus these scripts run entirely on the phone, so you should be able to run them anywhere with only your phone (maybe even using terminal on the phone...haven't tested that yet). And before we start a war, I'm not saying that there is anything with wrong with your app, and I'm sure it has/will help a lot of people who want the easy gui, but it wasn't for me, and I thought other people may feel the same way. There's no reason both apps can't exist. I also appreciate you letting people know in this thread so the less cli-oriented people know their options.
@Erisftw:
That is really strange if it's continuing to not give you a choice for language. Are you sure you flashed the latest one that I uploaded (cbackup-v0.4-signed.zip)? And that you made your backup either using v0.4 or using v0.3 on a phone with busybox properly installed. If so could you copy and paste the first ~20 lines of output from crestore, and let me know if you are on windows or linux?
dont worry, not trying to start a flame war at all. i love diversity and competition as it creates better programs to arise, that ultimately are better for the end user. theres plenty of room for everyone here. i love CLI as well, but not a lot of people do. arent you glad this is a free world to have competition?
Changed to 4, restored. fine, but it has old rosie, and when you click on the app, it says app no longer installed.

Back To Basics - A Simple shell script to do it all

This is a simple shell script (written on a mac, don't think it will work on windows... somebody feel free to prove me wrong?) which has many options, such as flashing a boot splash image, a boot animation, changing the fonts, running an adblock script, etc.
It was written because everytime i flash an update of KaosFroyo, i had to manually go remove all the apps i didn't want, reflash my boot animation, push my eri file, run the adblock script, and i was kinda tired of it... so thus we have BackToBasics v0.4 (versions 0.1, 0.2, and 0.3 were local and be glad you missed them)
So please feel free to give it a try and provide lots of feedback!
multiupload.com/KCK3YEF42F
(sorry i can't post a link)
As always:
If its breaks, it's yours not mine.
Always read the help sections first, or ask me a question if you are unsure about something.
Few things to think about:
Automatically reboot the phone after flashing bootanimation, fonts, eri, or adblock rather than having to do it manually?
Anything broken, or a better way to do something?
Good job. Some parts seem to be personal customizations, but it would be a good starting point for someone else wanting to do similar things. If you had the inclination, you could expand this into a more general 'app'.
Thank you for putting it out here. I would love to see more people post their home made scripts and such. No need to reinvent the wheel so often, you know.
Tuckface1 said:
This is a simple shell script (written on a mac, don't think it will work on windows... somebody feel free to prove me wrong?) which has many options, such as flashing a boot splash image, a boot animation, changing the fonts, running an adblock script, etc.
It was written because everytime i flash an update of KaosFroyo, i had to manually go remove all the apps i didn't want, reflash my boot animation, push my eri file, run the adblock script, and i was kinda tired of it... so thus we have BackToBasics v0.4 (versions 0.1, 0.2, and 0.3 were local and be glad you missed them)
So please feel free to give it a try and provide lots of feedback!
multiupload.com/KCK3YEF42F
(sorry i can't post a link)
As always:
If its breaks, it's yours not mine.
Always read the help sections first, or ask me a question if you are unsure about something.
Few things to think about:
Automatically reboot the phone after flashing bootanimation, fonts, eri, or adblock rather than having to do it manually?
Anything broken, or a better way to do something?
Click to expand...
Click to collapse
Good idea give people the option to create their own customizations
Sent from my nonsensikal froyo using XDA App
it is a bit of a personal thing, but i figured, what the hell, it's pretty open to be changed by anybody else, and things can be added, and the scripts can all be changed, but it's a base point to start with. I do intend to keep expanding the script and making it a much broader script for use in many more situations.

Keep Root through OTA

Read up on this in my Google New reader app.
Just installed it to see if it works on our tabs, and it appears to.
What I believe it does is make a backuo of your root.
Before you do an OTA, you uninstall root (after you've backed up root) through the app, then after OTA you restore your root.
For those of you that like to stay stock, but have root, here's the link.
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
interesting But i bet acer is Already working on patching this... I also think that is what takes them so long to push updates.. Patching holes. to prevent dev. on There devices that we PAID For ...APPLE Ceo did not die He Quit and it working with Elvis at Acer... Giggles..
erica_renee said:
interesting But i bet acer is Already working on patching this... I also think that is what takes them so long to push updates.. Patching holes. to prevent dev. on There devices that we PAID For ...APPLE Ceo did not die He Quit and it working with Elvis at Acer... Giggles..
Click to expand...
Click to collapse
I guess you didn't understand what it does?
Doesn't your sig say "reading is power"?
yes i read what it does.. Just not sure how long it will remain valid and i d/loaded it will check it out give it a try
erica_renee said:
yes i read what it does.. Just not sure how long it will remain valid and i d/loaded it will check it out give it a try
Click to expand...
Click to collapse
It does nothing to the bootloader, merely retains root. After you backup root with the app, you get your OTA, then restore your root through the app.
OK What i do not understand.. is IF it can retain root thru the OTA.. ota updates change they system file permissions and protects them. The use some type of exploit to root the device. This app is doing the same Am i correct.. And if i am acer can plug that exploit. Also.. is this works to reroot afer a ota unrootes the device.. why will this not just root the tablet as well. looks like someone could take it apart and create a new way to root the tablet without DOWNGRADING or flashing a new rom..
IS the above true or am i just STUPID For thinking all of this... the dev might know something that is not known on the a500 forums ...
I can tell you exactly how it works.
In Linux there is a command called chattr which allows you to change the attributes on a file like in Windows (readonly for example). However, in Linux it is much more powerful. So, what you do, is set the chattr bit so NOBOBY can modify a file. Not even root. If root wants to change it, then root has to remove that bit first.
So, if you want to keep root you chattr it. Then when the update.zip runs and walks through the /system folder it cannot remove the su sticky bit because it has been chattr'ed.
However, some updates delete everything in the /system/xbin folder therefore the tool makes a backup to another folder called /system/backupsu. This backup usually remains. Usually, that is, unless ACER loads a NEW /system image. Like they need to expand the size, or want to reload everything, then they lay down a NEW system image and it's gone. ALL GONE.
Some ask, why don't you chattr to another folder other then system, well most other mount points have su sticky bit turned off, therefore making su not work from another mount.
So will ACER plug the chattr hole? I don't think so, this in the kernel and part of the file system. They could walk the system mount and un-chattr everything, but then again you can just use another approach.
The chattr trick normally only works on simple OTA's. For example, I think when ACER went to 3.2 they relaid down system. I could be wrong, I'd have to check my notes. But thankfully, most vendors don't reload system that often so you'r find that chattr'ng the su file works 99% of the time.
Hope this helps,
TD
---------- Post added at 06:25 PM ---------- Previous post was at 06:10 PM ----------
Also, 411 on rooting.
To root, you find a hole and then set the 'sticky bit' on an executable so it now runs as root for example: rwsr-xr-x. Notice the 's' in the owner permissions. When this file is executed it runs with the owners permissions on the file system. So to make a simple root, just copy the ash shell to /system/xbin make the file owned by root and then set the sticky bit. Now, if you are not root, you just run /system/xbin/ash and because this version of ash is owned by root and has the sticky bit set, you get the root(#) because the ash shell is now running as root.
So, you use the exploit to gain root and then set up a program to give you root anytime you want it. Usually that program is named su. Now, when an update runs, it walks the entire /system tree resetting all files to rwxr-xr-x which removes the sticky bit and breaks root.
What is heartbreaking, is you now need to use the exploit to get root so you can set back your sticky bit. If the update patched your exploit then you have find another one.
So, the question is, once you get root, how do you keep it. Using chattr is one way therefore if the update removes your exploit, hopefully it doesn't matter because you 'locked in' your sticky bit with chattr.
This is why once any version is rooted you can root most any other version. It now becomes possible to move back and forth through OTA's while allowing you to keep root. But time traveling a root OTA is only possible into the future, you can never go back in time prior to the invention of the root. But you can always travel forward with root. This is exactly how we root the 3.2.1. We take a tablet that has 3.0.1 on it and use iconia root exploit to root it. Then we lock it, add other backdoors, and roll forward in time through the minefields of the OTA's until it stops. Hopefully, you still have root. In other words, it's the flux capacitor and is what makes future rooting possible.
So it doesn't matter, as long as you chattr (chatter), because who cares if ACER's heart goes pitter patter <<== Sounds like a Roll'n Stone lyrics <lol>
"Don't you know the crime rate is going up, up, up, up, up
To live on this forum you must be tough, tough, tough, tough, tough
You got rats at ACER dreaming of the west side
Software bugs on upgrades
What a mess, this forum says chatter (chattr), so my root won't be shattered
My brains been battered, splattered all over this forum
but what's that matter.
Ah look at me, my root is chattr'ed
I'm not wanting my root shattered
Look at me- I'm a chattr'ed, look at me
Man time to go drink heavily.
"SOFTMOD" app
SORRY PPL COMPLETELY CONFUSED 2 DIFFERENT TOPICS IN 2 DIFFERENT THREADS - ALZHEIMER's RULES OK!! - Deleted this response
timmyDean your making my head spin. Thanks for the info.
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
erica_renee said:
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
Click to expand...
Click to collapse
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
kjy2010 said:
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
Awesome.
It seems interesting
Click to expand...
Click to collapse
kjy2010 said:
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
Click to expand...
Click to collapse
You the man. I could not recall if 3.0.1 to 3.1 to 3.2 did a system reload. What some OEM's do is erase /system. Lenovo did that when they went from 11 to 12 and then from 12 to 13. But, I could not recall if ACER did. You'll find that chattr works 99% of the time, maybe 100% on an ACER. That's why I turn off OTA's so they don't occur automatically. Then when one becomes available, I download and look at what they're changing before allowing it. This is really important now that they've locked the bootloader. If you take an OTA and it patches your root exploit, removes chattr, deletes your backup su, and breaks root then you might be stuck in the future with no root. If this happens you have to hope there's a way back without root.
So thanks.
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
erica_renee said:
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
Click to expand...
Click to collapse
Not a full system, it's how they load it is the key. They push full systems all the time and they really just copy over all new which keeps chattr'ed files. They really have to reformat /system (or destructively destroy it). They'll do this if they need to increase the size, change from ext3 to ext4, etc.
Hope this helps
TD
Thanks sirs for this if we get the doubtful ota I might do this n sell the tap to my little brother or keep it who knows lol
Sent from my HTC Inspire 4G using Tapatalk
timmyDean said:
You the man. I could not recall if 3.0.1 to 3.1 to 3.2 did a system reload. What some OEM's do is erase /system. Lenovo did that when they went from 11 to 12 and then from 12 to 13. But, I could not recall if ACER did. You'll find that chattr works 99% of the time, maybe 100% on an ACER. That's why I turn off OTA's so they don't occur automatically. Then when one becomes available, I download and look at what they're changing before allowing it. This is really important now that they've locked the bootloader. If you take an OTA and it patches your root exploit, removes chattr, deletes your backup su, and breaks root then you might be stuck in the future with no root. If this happens you have to hope there's a way back without root.
So thanks.
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
Not a full system, it's how they load it is the key. They push full systems all the time and they really just copy over all new which keeps chattr'ed files. They really have to reformat /system (or destructively destroy it). They'll do this if they need to increase the size, change from ext3 to ext4, etc.
Hope this helps
TD
Click to expand...
Click to collapse
Yes i do understand. Maybe i did not explain what i was saying correctly.. Acer's update is not aware or looking for those files. There for they do not touch them. as they are just scanning and updating files to reflect there changes.. I to agree that its likely this will remain valid.Atleast we know it is for the os updates and release that are available up to now..
erica_renee said:
Yes i do understand. Maybe i did not explain what i was saying correctly.. Acer's update is not aware or looking for those files. There for they do not touch them. as they are just scanning and updating files to reflect there changes.. I to agree that its likely this will remain valid.Atleast we know it is for the os updates and release that are available up to now..
Click to expand...
Click to collapse
Exactly, so much for being blonde <lol>

[Q & A][ROM] [4.4.4] Plain-Andy

Feel free to discuss any possible bugs/issues that are to arise.
Plain-Tweak:
Ever wanted to control your kernel from a file on your internal storage? Now you can! There are currently 3 different ways
1.) Manually create a text file on the root of /sdcard
named 'plaintweak' with the following values:
gov=(your choice of governor)
maxkhz=(max cpu clockrate for all cores)
minkhz= (min cpu clockrate for all cores)
scheduler=(choice of IO scheduler)
tcpcong=(choice of TCP Congestion control)
2.)Invoking the instruction 'plaintweak' with adb shell or Terminal Emulator.
3.)Separate aroma package for your device(not yet created) or through the rom installer.
When I run 'plaintweak' from aroma package adb shell or Terminal Emulator wouldn't it get overwritten?
No! Not at all. Your old settings are saved at /sdcard/plain-tweak listed by date.
Don't like the values? Want a different configuration? Rather use Performance Control or another app?
Simply rename your current plaintweak file or move an older plaintweak file located in /sdcard/plain-tweak to root of /sdcard.
Def the most stable aosp on lg g2. On the new build im getting echos while in convo. Not on my side but on their side. Tried both dirty and clean flashing. Reverted to 10/25 and issue is gone. Regardless thanks for your work. Saves me from the stock software ?
Awesome rom I love the feel and how quick it is.. head and shoulders above the last stable CM11 (M6, which I had been using since May) for D800.
Couple questions - I viewed back about 15 pages but couldn't find anything..
I know CM has had some issues lately with rotation, proximity sensor and light sensor. I just flashed the 11/7 version and my phone won't rotate. Not a big deal to me, and I'm not sure if it's known, but I wanted to throw that out there.
Also, might be a stupid question but I removed the stock lockscreen and can't seem to get it back. Reflash?
@RamOdin
First, thank you for the feedback. Second; Reflash. Third; make sure you're on an unmodified kitkat baseband. Also check your quick toggles for the autorotate toggle prior.
Thanks - will do this evening. Is it normal for all ROMs to only be able to do google login from Wifi?
---------- Post added at 10:54 AM ---------- Previous post was at 10:42 AM ----------
Ignore that last post.. I'm a dummy sometimes. Additionally, I cannot edit it.
@RamOdin
Flash ROM. Boot. Reboot back to recovery. Flash gapps. Then on boot, launch Play store, that will bring up the Google account wizard.
@Snuzzo
So it's not your ROM causing the issues on my phone. I flashed both LiquidSmooth and DirtyUnicorns, both having the same issue.
Strangely, the only thing that fixed it was flashing the latest nightly from CM11, watching it go into a bootloop and then wiping in recovery and restoring my last backup of CM11 M6...
Weird.. *shrugs*
Any ideas? I know it's not your job to troubleshoot me, but I really love this ROM and would love to use it daily.
No clue unfortunately. These G2's can be finicky. Try doing a TOT/KDZ restore to stock.
I love it. Will update to your L rom when available.
On a side note for anyone who doesn't know, if you're using the ls980 (sprint variant) but on an American gsm network the dialer trick does work.
Remember, it's *#*#4636#*#*

Noob Friendly Tips, Tricks, General Information + Great Information_Pixel_XL_Marlin

I'm creating this thread to aggregate information in to one location and help anyone out who isn't sure what to do next. I'll be adding to this if and when I can and of course anyone who has anything to add, plz do. This may seem late in the game for some folks, but I'm new to this phone and therefor wanted to help anyone else just picking one up to get familiar with the territory. I have gained SO much from this website over the 7 years I've been here that anything I can give back I'm going to do, and I'm off today with a little time to spare. This won't be overly complicated, and I keep things very simple for ease of use. I'm also aware there are other guides/posts and I will add them to the links as well. This is a small list to start, and will not focus on any one thing, other than making our phones more stable, easier to use and battery efficient. I take no responsibility for anything you may do wth this information, and I take no credit for anything I'm posting here. Links and discussion starting in post 2.
Pixel XL Information Collection - started on 6.1.2018
Swapping Home / Recents Button
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
https://forum.xda-developers.com/pixel-xl/help/swap-recent-button-oreo-t3687721
Root Method: Magisk or Supersu. Magisk 16.4 as of writing
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Bootloader Unlocking: Google Play Store model works a treat, and as of writing, Verizon model now as well thanks to exploit found by XDA member Burduli. - His profile link: https://forum.xda-developers.com/member.php?u=5642246 -
Verizon Bootloader Unlock:
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
APN Settings, including alternative for each. All confirmed working as of writing
https://bestmvno.com/apn-settings/straight-talk-wireless-apn-settings/
Battery Life Threads, including which wake locks to block, greenify options, etc.
https://forum.xda-developers.com/showpost.php?p=60429417&postcount=4
Audio & Battery guide
https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124
Information on IO Schedulers for kernels - I am a huge fan of IO Schedulers and they don't get enough love for what they do
https://androidmodguide.blogspot.com/p/io-schedulers.html?m=1
Guide on how to create your own flashable zip files to flash in TWRP. Confirmed working as of writing
https://goo.gl/zfVGTJ
Camera NX, best camera mod out there. If you're not using this, stop right now and download/install
https://chromloop.com/2018/03/apk-c...camera-5-2-features-bring-back-hdr-nexus2015/
SDK Platform-Tools Stand Alone
https://developer.android.com/studio/releases/platform-tools
How to take a log cat. PLZ read this if you don't know, it's dead simple
https://forum.xda-developers.com/showthread.php?t=1726238
Pixel Beta Downloads
https://developer.android.com/preview/download
Pixel Factory and OTA images
https://developers.google.com/android/images
How to add your APN settings to a ROM if you're on Verizon Wireless and can't edit APN's
https://forum.xda-developers.com/showthread.php?t=2387346
A proper flashing guide, explaining slots A & B
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Do not EVER RELOCK your bootloader. Here's why.
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Guide on unlocking, flashing images and kernels, etc.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
MTP Windows 10 fix if your phone isn't being recognized by your computer:
https://forum.xda-developers.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625

Categories

Resources