d80020y issues getting recovery flashed - AT&T LG G2

New to the G2 world, unit just came in yesterday, rooted with stump root brute force. Worked well, got busybox, flashify, sqlite, and tibu all working. Tried to flash twrp 2.8.5.0 in flashify and think I fubared my recovery. When I try to boot into recovery using quickboot, I get white text up top
ERROR: boot certification verify
Secure boot failure
Then screen quickly goes black, from there I can hold power button and reboot, only issue when booting phone, upon unlock I get com.google.process.location has stoped, otherwise phone seems to function perfectly.
If I use hardware buttons to boot into recovery, I get a white screen with two option, yes or no to factory reset. Assuming this is stock LG recovery, regardless not sure if I should try CWM or stick with my trusty twrp. A lot of stuff on the forum about downgrading bootloaders/ firmwares, making sure modems match the rom flashing. At this point I just want a custom recovery. Any help would be very much appreciated. Don't want to screw it up anymore.

Nerds, help a brother out... this forum sucks compared to note 3 section.

I think I replied elsewhere recognize your username. Use autorec.
If you can get into Android.

thor1k said:
I think I replied elsewhere recognize your username. Use autorec.
If you can get into Android.
Click to expand...
Click to collapse
I use this Autorec, it stated it completed and gave option to boot into recovery or to exit, do we need to use this program to initiate recovery or should it be an option when I choose reboot?
I see everyone mention to use this Autorec apk but I did not see any sticky on our phone about how to use it after we install it or any mention of enabling or using recovery after the install on any of the 6 threads I located with its reference...
When it ran it said 2.7.0.0 in the header, is the version I used old?
If you used this Autorec, what next? Thanks..

sobitthen said:
I use this Autorec, it stated it completed and gave option to boot into recovery or to exit, do we need to use this program to initiate recovery or should it be an option when I choose reboot?
I see everyone mention to use this Autorec apk but I did not see any sticky on our phone about how to use it after we install it or any mention of enabling or using recovery after the install on any of the 6 threads I located with its reference...
If you used this Autorec, what next? Thanks..
Click to expand...
Click to collapse
it's an option for me when I reboot because of GravityBox and Xposed framework, but you can use the usual method to get to recovery after it's flashed. Use the app to get to the recovery once to make sure it's there, then you can safely do the "factory reset" on startup (it won't actually reset it'll just go to recovery) to go to the recovery.
yeah there isn't too much clear documentation about the whole process but follow the steps in sequence that are listed under the Guide section here: http://forum.xda-developers.com/showthread.php?t=2715496
finally you may need to update the touch firmware after-- I did at least: http://forum.xda-developers.com/showthread.php?t=2736166

thor1k said:
it's an option for me when I reboot because of GravityBox and Xposed framework, but you can use the usual method to get to recovery after it's flashed. Use the app to get to the recovery once to make sure it's there, then you can safely do the "factory reset" on startup (it won't actually reset it'll just go to recovery) to go to the recovery.
yeah there isn't too much clear documentation about the whole process but follow the steps in sequence that are listed under the Guide section here: http://forum.xda-developers.com/showthread.php?t=2715496
finally you may need to update the touch firmware after-- I did at least: http://forum.xda-developers.com/showthread.php?t=2736166
Click to expand...
Click to collapse
I tried to see if the TWRP manager would detect it, said it wasn't there, so installed Clockwork manager and it installed some old version of recovery, wouldn't let me choose the IMG file for touch I had downloaded, there was option for boot into recovery within that app, I did, and poof, I was into TWRP .
Unknown waters since never used it. I tried same method as other ROMs, although did not factory reset, or see option to install new ROM like in CWM, wiped dalvik n cache, installed zip of cm12, gapps, su, wiped cache again, it started process of updating android, hope all is well, that app was new and different for me and I was expecting the good old clockwork I used for years to be there so I didn't research it too much since I thought it failed to load since our device is not on list of supported devices.
Looks like it worked, and it knew my previous device and all my apps from my other Lollipop Atrix HD I had, likely through Google back-up, and is downloading all my apps for me, even before logging into Cyanogen account, which usually did that for me...
Was like 40 apps to load, will see if she still works after all the apps load, didn't think I had that many on previous device, hope not every app I ever tried out...
Will try and uninstall the CWM app if that is still there since TWRP seems to load, or just keep to initiate recovery mode for updates..
---------- Post added at 03:44 PM ---------- Previous post was at 03:05 PM ----------
No, that must not have been the correct way...
All was fine until I opened up Facebook, then every single app on my phone started to open up, settings were moving about, like a dozen people were in my phone remotely changing up every setting possible...
ruh roh...
After another forced reboot it seems to be working fine for now, although the phone is now called a AT&T Lge LG-D801 in Google Play when it is a D800.

Related

[Q] Please help, Root and rom has failed my phone...

I Rooted my phone and added a fresh ROM, for some reason the Gapps didn't install, so I downloaded a separate one and added it via recovery screen (holding down up, menu and power button) as instructed. However, now my phone won't work and when starts only says "Unfortunately, Setup wizard has stopped" once I clear this message, another pops up and says "Unfortunately, Google services framework has stopped" i click ok but the message just keeps appearing! my phone will NOT work, please someone help me, I tried re-rooting the way i did before using Odin, however, that didnt work, I can't seem to locate in the recovery menu where the faulty Gapps is located!
Any help is please welcomed, Also the phone is samsung note 2
c0ldp0ison said:
I Rooted my phone and added a fresh ROM, for some reason the Gapps didn't install, so I downloaded a separate one and added it via recovery screen (holding down up, menu and power button) as instructed. However, now my phone won't work and when starts only says "Unfortunately, Setup wizard has stopped" once I clear this message, another pops up and says "Unfortunately, Google services framework has stopped" i click ok but the message just keeps appearing! my phone will NOT work, please someone help me, I tried re-rooting the way i did before using Odin, however, that didnt work, I can't seem to locate in the recovery menu where the faulty Gapps is located!
Any help is please welcomed, Also the phone is samsung note 2
Click to expand...
Click to collapse
What rom did you flash? You may have flashed gapps for the wrong android version. You need to make sure that you download the Gapps in the OP of the rom you want so you know you're getting the right one
Sent from my CLEAN Note ll
Have you done a Nandroid backup? Do a recovery or download a stock RUU. Goodluck man
Sent from my HTC One X+
I did that with my tablet once, I just wiped and re-flashed and put GAPPs on correctly and it was fine.
Failed Flash
Download an app like root checker to make sure you are still rooted.
What kind of recovery are you using on your phone?
You should wipe the phone completely, system, cache and dalvic.
Try doing the factory reset, check for root and follow the instructions from the original thread.
As stated earlier, make sure you download the correct Gapps for the ROM you are installing.
Also, you need some type of file explorer, I use Root Explorer. You can use that to search for the Gapps.
If you downloaded it on the phone it may still be in your download folder if not look in \system\app folder.
Hi everyone, I managed to fix the Gapps problem, however, now I have a problem with EVERY rom i install, i have tried Slimbean and Crashrom but I can't seem to get the EFS to work, i backed up using efs pro and an efs backup tool but it wont restore, so I have no network coverage, so i end up having to keep going back to ****ty stock, I have ended up going back and forth 18 times!! people say about baseband, but i don't know how to change that...
Pennycake said:
I did that with my tablet once, I just wiped and re-flashed and put GAPPs on correctly and it was fine.
Click to expand...
Click to collapse
yes.i do same:good:
c0ldp0ison said:
Hi everyone, I managed to fix the Gapps problem, however, now I have a problem with EVERY rom i install, i have tried Slimbean and Crashrom but I can't seem to get the EFS to work, i backed up using efs pro and an efs backup tool but it wont restore, so I have no network coverage, so i end up having to keep going back to ****ty stock, I have ended up going back and forth 18 times!! people say about baseband, but i don't know how to change that...
Click to expand...
Click to collapse
Your baseband is the modem/radio the phone uses.
Here is a link http://forum.xda-developers.com/showthread.php?t=2044937
At the bottom are some flash-able modems you can try.
Hope this works for you

[Q] Having a lot of trouble

I just purchased a p509 as a backup phone and figured I could easily root it and flash a better ROM on it. I am not new to the whole flashing process. I've had no problems doing all this on three other phones (LG G2x, Galaxy Centura, and a Galaxy S 4G).
I rooted it using Gingerbreak. Seemed to go ok. My first problem was having error messages using Astro File Manager. I then got a little carried away with Titanium Backup and deleted the LG Home launcher and probably something else I shouldn't have. I of course then had no home screen. I used Gmail to send the APK to myself and install it. I then had my home screen, but I still got error messages every time I hit the home button.
I then installed ROM manager to try and get a recovery on the phone and wipe out all my issues with a new ROM. It gets to 100% installing CWM and then I get a Superuser error message. If I try and fix permissions I get the same thing.
Any advice? The only factory restore help i can find is the basic hard reset stuff.
Every time something needs Superuser, SU gives me a FC. I can't even install Busybox. Is there no way to return this phone to the way it came from the factory?
Ok so I seem to have SU working now. But Busybox still won't install...
Well even though no one cares to help (not surprised on XDA) I want to add some info. I have tried flashing a recovery two different ways through terminal emulator with no luck. My current status is using this guide: http://forum.xda-developers.com/showthread.php?t=2003080
I'm trying to type in "flash_image recovery /sdcard/recovery.img" and getting a not enough memory message. This is becoming the most pain in the ass thing i have ever tried to do. I would love to just have it back to the way I received it with all the stock apps and games and not having to email myself the LG Home launcher every time I reset it. Any insight would be appreciated.
the problem is that rom manager is not compatible anymore with O1(if you managed to install recovery do not boot into it from rommanager, use combo keys), so read this post to install recovery http://forum.xda-developers.com/showthread.php?t=1827723 (to go in fastboot try to use quickboot from playstore), search forum for flashable recovery thread for O1,
or, to make it stock just flash an oldbb GB rom 2.2 and use LG support tool from LG site and update to latest version available, worked for me
Thank you very much. I actually just solved the problem with this guide:http://forum.xda-developers.com/showthread.php?t=1318750 and running GingerDX.
Good to know how to get it back to stock though. I swear I searched and got nothing but "Hard reset" results.
Thank you very much. I actually just solved the problem with this guide:http://forum.xda-developers.com/showthread.php?t=1318750 and running GingerDX.
Good to know how to get it back to stock though. I swear I searched and got nothing but "Hard reset" results.

Need help on how to flash TWRP properly (Exynos) (SM-G930F)

Hi there. Recently (just yesterday) I tried flashing TWRP 3.1.0-0-herolte via Odin V3.12.3.0. However I ran into a little issue. Bootloop. TWRP seemed to work fine, but the phone wouldn't boot into android (stock touchwiz), exhibiting the 'samsung galaxy S7' logo periodically, but not going past that. Firstly I'll give some details on the phone and how I 'tried' to to flash TWRP. The phone I have is an Exynos variant SM-G930F running Android 7.0 and the recent update from late March. It is an Australian model (otherwise known as the 'international' version I think). Anyway as for what I was using as a guide, it was this. Before attempting this I enabled 'OEM unlocking' within the developer options but not 'USB debugging' (not sure if this contributed to the issue, but thought I'd mention it anyway). Later on I downloaded the Samsung Mobile Drivers and the tar file for TWRP. Installed the drivers, opened up Odin, entered download mode on the S7. I placed the tar file in AP and connected via micro usb. Almost everything, including auto-reboot, was turned off except F. Reset Time. Though chances are I probably left it on because I'm a doofus. After all that I pressed 'start' without doing any button combinations. Then after the screen went blank I pressed volume up + home hey + power button, roughly all at the same time. And then I entered TWRP. I then swiped to 'allow system modifications'. However as I didn't want to root the phone at the time, I decided to power it off through the menu. The next time I pushed the power button however, it was stuck in a bootloop. I then went back into TWRP and noticed that when I went into the install menu and was looking at the internal storage it appeared as 0mb (I thought that twrp had deleted all my files at the time), and I couldn't access the files I normally do like the downloads folder or app folders. However it seemed like most of the system folders were there like 'root' and 'data' etc. I then formatted the data and then did a factory reset as I thought it might fix the problem but it didn't. I swiped to install the twrp app but unchecked the two boxes. I then did some research and found out that if I ever were to run into an issue like this that I should flash the stock firmware, which is what I did. And viola! It worked again! I was slightly stressed at the time, lol. Luckily the apps and data I had previously were stored in the cloud.
After all this I have a question, what do you guys think I did wrong? Have you ran into this issue before? And what do you think may have caused the bootloop. I eventually want to start rooting my S7 and perhaps flash a rom, but I don't want to run into the issue again. Cheers!
P.S. I'm probably the biggest tech noob I know so go into a little bit of detail if you know what I did wrong so I don't make the same mistake again
Sounds like you hit the problem listed in step 9 & 10.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot
Click to expand...
Click to collapse
You swiped to allow system modifications, but you chose not to root and turned it off.
I don't see any mention of you flashing the dm-verity and force encryption disabler zip in TWRP which is required even if you're not rooting.
Beanvee7 said:
Sounds like you hit the problem listed in step 9 & 10.
You swiped to allow system modifications, but you chose not to root and turned it off.
I don't see any mention of you flashing the dm-verity and force encryption disabler zip in TWRP which is required even if you're not rooting.
Click to expand...
Click to collapse
Hm, that might actually be it. As a question how would be able to do that? Do I need to download that separately or something ( the dm-verity and encryption disabler zip I mean)?
EDIT
Actually never mind, it seems to say it right within the guide lol. So the problem should go away if I do that first yeah?
Yep just download it and put it on an SD card or transfer to the phones internal storage (I think TWRP lets you USB transfer) and go install zip in TWRP and select it.
That should stop your boot issues after installing TWRP, should even work even if you do it after a failed boot.
Beanvee7 said:
Yep just download it and put it on an SD card or transfer to the phones internal storage (I think TWRP lets you USB transfer) and go install zip in TWRP and select it.
That should stop your boot issues after installing TWRP, should even work even if you do it after a failed boot.
Click to expand...
Click to collapse
Hey bro, just wanted to say thanks. Got it rooted soon after as well. I found out I had to format data first before because it wouldn't let me install any zips. But after doing that it worked without any hiccups.
Cheers.
You should reset/wipe ur device after you have installed twrp through odin. That's a simple that some people wouldn't see in the tutorial. Then if you want root access you can flash SuperSu. Hope your problem will be solved. Good luck.
amalantony said:
You should reset/wipe ur device after you have installed twrp through odin. That's a simple that some people wouldn't see in the tutorial. Then if you want root access you can flash SuperSu. Hope your problem will be solved. Good luck.
Click to expand...
Click to collapse
Already did that before bro. Works as swell as a bell.
TheNickleS said:
Hey bro, just wanted to say thanks. Got it rooted soon after as well. I found out I had to format data first before because it wouldn't let me install any zips. But after doing that it worked without any hiccups.
Cheers.
Click to expand...
Click to collapse
Glad it's all working.
First time I installed TWRP I installed a ROM straight after which said to to format data, so never knew TWRP install alone needed the format data too.
Beanvee7 said:
Glad it's all working.
First time I installed TWRP I installed a ROM straight after which said to to format data, so never knew TWRP install alone needed the format data too.
Click to expand...
Click to collapse
From what I understand that's because the ldm-verity triggers. And so formating the data removes any encryption allowing for things to be flashed. But because I didn't do all of that first my S7 wouldn't boot up past flashing twrp.

OP6 stuck in bootloop - how do I fix this?

Hello!
I seem to only post on this homepage whenever I f*** up, and so here I am...
I'll try to explain this as best as possible.
I decided I wanted to root my OP6 so I could cheat in PoGO since the weather turned bad.
I followed a guide precisely - https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6-with-magisk-beginners-guide-0185541/ - this one specifically.
So my phone is now rooted and I've got Magisk and TWRP, everything seems fine. I go to download the Root Checker and it gives me an error that it's not compatible with my device.
I freak out and try out various things inside Magisk Hide to make it work. It eventually works out and "YAY MY PHONE IS IN FACT ROOTED". Although the SafetyNet thing gives me an error.
Okay, I Install PoGo, go to Magisk Hide and select it. Start it up, log in.... Failed.... "Oh no". Failed... Failed... Failed...
Urgh, whatever I think. Let's just get rid of the root and TWRP then. Can't be too hard? Oh Magisk has an uninstall feature, let's hit that up. Uninstalled. Huh? PoGo still not working.
I've spent a few hours now trying to get this to work, my phone is wiped and not really useful. Let's remove TWRP then right? Right??! Steps are simple.
Wipe Phone, get a stock OP6 rom thing.
Press the install button. Nothing happens, wait for 10 minutes. It now asks me to reboot, no errors show up.
Good, it's booting. It's been twenty minutes, still booting... 30 minutes, still booting...
I'm stuck.
I know I screwed up somewhere, but does anyone know what I can do?
I can reboot to recovery, which is stock recovery now.
EDIT: Okay, so I couldn't idly sit by, so I went into recovery and wiped data yet again. It booted up this time and is now asking me to update my OS!
One problem resides, I can't download Netflix, which means I'm tripping the safetynet thing. Is it because my bootloader is unlocked? If so, how do I lock it again?
EDIT2: I really can't sit still. Googled, found out how to lock bootloader. Let's see if Netflix works.
EDIT3: Netflix can be downloaded, so I think everything works as it should again. I'm now installing official updates to my phone. If it breaks, I'll be here again.
LOL.
At least you have a working device again.
Once you unlock your bootloader your widevine level goes to 3 (level 1 is default meaning bootloader locked). There are people reporting to get netflix working but HD streams seem to be broken then so just SD quality.
I guess you messed up with your a/b partitions. This happens when you don't install twrp properly to both slots. Installing means to boot twrp with fastboot and install latest twrp.zip.
After that you flash magisk. Right now to keep dm verity you need to flash magisk 16.0 (stable). After rebooting your system, open magisk switch to beta channel and install latest version (16.7) directly through the magisk app. After reboot you should have dm verity ticked.
For safety.net passing: magisk needs an update due to api changes from safety.net/ google.
If my rom doesn't boot I just reinstall latest oos build, boot twrp and flash twrp.zip, then magisk.
lol, glad you have everything up again. I remember when i used to go through these scenarios on the regular. Do you want root for any specific reason? i only ask because after years of being rooted, i really feel that the pros no longer outweigh the cons. Once the whole A/B partition thing was introduced (i believe it was in Nougat?), it opened up the doors to a lot of possible issues with softbricking, etc. I'm still here on xda to see if there's anything that will bring back the itch for tinkering/rooting, but for the time being, you can find just about any nonroot alternative to what you might need.
PhilGizzle said:
Hello!
I seem to only post on this homepage whenever I f*** up, and so here I am...
I'll try to explain this as best as possible.
I decided I wanted to root my OP6 so I could cheat in PoGO since the weather turned bad.
I followed a guide precisely - https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6-with-magisk-beginners-guide-0185541/ - this one specifically.
So my phone is now rooted and I've got Magisk and TWRP, everything seems fine. I go to download the Root Checker and it gives me an error that it's not compatible with my device.
I freak out and try out various things inside Magisk Hide to make it work. It eventually works out and "YAY MY PHONE IS IN FACT ROOTED". Although the SafetyNet thing gives me an error.
Okay, I Install PoGo, go to Magisk Hide and select it. Start it up, log in.... Failed.... "Oh no". Failed... Failed... Failed...
Urgh, whatever I think. Let's just get rid of the root and TWRP then. Can't be too hard? Oh Magisk has an uninstall feature, let's hit that up. Uninstalled. Huh? PoGo still not working.
I've spent a few hours now trying to get this to work, my phone is wiped and not really useful. Let's remove TWRP then right? Right??! Steps are simple.
Wipe Phone, get a stock OP6 rom thing.
Press the install button. Nothing happens, wait for 10 minutes. It now asks me to reboot, no errors show up.
Good, it's booting. It's been twenty minutes, still booting... 30 minutes, still booting...
I'm stuck.
I know I screwed up somewhere, but does anyone know what I can do?
I can reboot to recovery, which is stock recovery now.
EDIT: Okay, so I couldn't idly sit by, so I went into recovery and wiped data yet again. It booted up this time and is now asking me to update my OS!
One problem resides, I can't download Netflix, which means I'm tripping the safetynet thing. Is it because my bootloader is unlocked? If so, how do I lock it again?
EDIT2: I really can't sit still. Googled, found out how to lock bootloader. Let's see if Netflix works.
EDIT3: Netflix can be downloaded, so I think everything works as it should again. I'm now installing official updates to my phone. If it breaks, I'll be here again.
Click to expand...
Click to collapse
thefallen924 said:
lol, glad you have everything up again. I remember when i used to go through these scenarios on the regular. Do you want root for any specific reason? i only ask because after years of being rooted, i really feel that the pros no longer outweigh the cons. Once the whole A/B partition thing was introduced (i believe it was in Nougat?), it opened up the doors to a lot of possible issues with softbricking, etc. I'm still here on xda to see if there's anything that will bring back the itch for tinkering/rooting, but for the time being, you can find just about any nonroot alternative to what you might need.
Click to expand...
Click to collapse
It is just different.
You have to forget the "old way" and then you don't face any problems.
Same with encryption that wasn't present before.
I still can't live without root.
Too many missing functions (xpsoed edge, titanium, afwall, xprivacy, gravitybox).
And the newer rom system by just applying a magisk module is pretty cool.
pdppdp said:
LOL.
At least you have a working device again.
Once you unlock your bootloader your widevine level goes to 3 (level 1 is default meaning bootloader locked). There are people reporting to get netflix working but HD streams seem to be broken then so just SD quality.
I guess you messed up with your a/b partitions. This happens when you don't install twrp properly to both slots. Installing means to boot twrp with fastboot and install latest twrp.zip.
After that you flash magisk. Right now to keep dm verity you need to flash magisk 16.0 (stable). After rebooting your system, open magisk switch to beta channel and install latest version (16.7) directly through the magisk app. After reboot you should have dm verity ticked.
For safety.net passing: magisk needs an update due to api changes from safety.net/ google.
If my rom doesn't boot I just reinstall latest oos build, boot twrp and flash twrp.zip, then magisk.
Click to expand...
Click to collapse
hey, i rooted my device yesterday on 10.3.3, all was good until i got into a bootloop after installing busybox from the magisk repo. i keep going back to the fastboot mode, i still have access to twrp but sadly i didnt make a nandroid backup. i really dont know what to do now and i know this is not the relevant thread to ask this question. im sorry, but if anyone knows a method to solve this please let me know. thanks
I would make a nandroid (just in case) now and then flash the full firmware again, reflash twrp and then xxx. This keeps your data and you should have a working system.
pdppdp said:
I would make a nandroid (just in case) now and then flash the full firmware again, reflash twrp and then xxx. This keeps your data and you should have a working system.
Click to expand...
Click to collapse
Make a nandroid of the Bootlooped system? Is it OK to flash the full firmware without performing a factory reset? Thanks...
EDIT- thanks a lot for this method Bro. .worked like a charm and now I'm back into system. .reflashing twrp and magisk now..thanks again
You're welcome.
Nandroid of your data in case something goes wrong and wipes the device. System is 'replacable'
pdppdp said:
You're welcome.
Nandroid of your data in case something goes wrong and wipes the device. System is 'replacable'
Click to expand...
Click to collapse
Yup that's a good precaution to take in case things go south. Anyways i was reading your earlier post on how unlocking the bootloader sets the widevine level to 3 and causes some problems to use netflix. I was unaware of this issue before i rooted. It's really a bummer, soon after reading your post i realized that netflix was missing and i went to play store to download. I couldn't find the app,then i downloaded the app from apk mirror and after installation i had this error that the device is not supported by the app. I did some research on the issue and on a OnePlus forum i found a solution, i went to the netflix website and logged in with my account, then i tried playing something which indicated me to download the app from play store and viola, the app got downloaded and works perfectly fine, it's kinda surprising. Thought I'd share this here if in case it might work for someone else...

Coming Over From Rooted Marshmallow Galaxy S7 - What Do I Need to Know?

I've got a rooted S7, apps backed up with Titanium Backup, etc.
Is there anything I need to know about getting this transferred over to a Pixel, which will presumably be running Oreo or Pie? I'd certainly like to take the opportunity to upgrade; I'm still on MM on the S7 mostly because it's just hassle to reflash the ROM (running Superman ROM, not stock).
I assume Nova Launcher will come across okay? What about things like Good Lock? It presumably won't work, but will it break anything or will I need to remove it from my backups before restoring?
Titanium allows me to create a zip of all my backups. Do I just flash that in TWRP? I don't think it's used from within the app itself, is it?
Any ROM recommendations? I use GravityBox so something AOSPish would be ideal, Pie would be awesome but I'd settle for Oreo. I'm not sure what Pie's release status is at the moment - I didn't think it was out yet but it seems to be. This is a very rushed thing (the S7 just stopped working and will be too expensive for repair to be worthwhile), so everything's very scrambled in my head at the moment and I'm just throwing thoughts out there, largely. EDIT: Actually, I assume Xposed and such aren't set up for Pie yet? If so Oreo would be the way to go.
Since I have GMail and such installed as user apps, not system apps, and backed up as such, I'm assuming I'll need to find a way to arrange the same with the Pixel? Superman ROM offers the option to install those apps or not through the Aroma installer.
Does anyone have any input on this?
I'm also curious as to the differences between rooting with/without tripping SafetyNet. I'm assuming there are some, or everyone would do the latter?
Do you have your Pixel, yet? Unlock the bootloader, install the latest factory image, use the latest TWRP & Magisk (do it properly, & a SafetyNet check will pass). When your phone is booting up fine and rooted, we can talk about transferring data.
I don't, but it should be arriving today. I like to be prepared, rather than getting into a situation where I have the phone and want to get everything sorted immediately, only to end up rushing and causing issues. I think I was reading and asking questions about two weeks ahead of my purchase of the S7. As I said, I'm replacing the S7 due to a fault, and I've been without it for a couple of weeks now, so the more I can get my head around before it arrives and I get all "OMG do everything immediately", the better.
If you really need Xposed, you can install a Magisk version of Xposed. Personally, I am no longer using Xposed; Magisk gives me root, and I can install all the modules I need.
Do you have the Pro version of Titanium Backup? You have to jump through some hoops to get it to recognize your Pro key. I would just transfer your entire backup directory to the backup directory on your new phone, then use the app to select which apps to restore. Do the app restores in waves, to help you narrow down a problematic restoration.
Even if you already have the latest version of Android installed on the Pixel, download the full factory image so that you can extract the boot.img file from it. Flashing the stock boot.img can get you out of most bootloops. Here's some reading material to help you understand what has changed.
Personally, I'm happy with the stock ROM, rooted. I suggest you look at Tulsadiver's mod. It has some sorely needed customization options.
:good:
post-mortem said:
If you really need Xposed, you can install a Magisk version of Xposed. Personally, I am no longer using Xposed; Magisk gives me root, and I can install all the modules I need.
Click to expand...
Click to collapse
So Xposed modules work in Magisk? Or....? I have GravityBox for notification control, as I find the default LED blink speed too low and like to change the sound/LED colour on a per-app basis far more than the apps themselves allow, along with Unbeloved Hosts, MinMinGuard, Airplane Mode Helper, Screenshot Delay Remover, Secure Settings, XToast and YouTube AdAway.
Do you have the Pro version of Titanium Backup? You have to jump through some hoops to get it to recognize your Pro key.
Click to expand...
Click to collapse
I do. There's an option to just create a flashable install of Titanium, and to back up its settings, which is what I've always done in the past. Is this different now?
EDIT: Which guide do I follow to install TWRP and Magisk? I thought this would be the go, but reading through it requires a custom ROM to begin with.
I followed this guide. I really don't know if it's actually necessary to uninstall com.android.phone, though I did it. The command you'll want to use to unlock the bootloader is fastboot flashing unlock, as stated at the top of this Google page.
If the enable OEM unlocking option under developer settings remains grayed out, you might have to get out of the settings and reenter them, restart your phone, or even reflash and start all over. For some reason, a number of people have reported that executing the command am start com.android.chrome in a terminal or adb shell allows the OEM unlocking options to become toggleable.
post-mortem said:
I followed this guide. I really don't know if it's actually necessary to uninstall com.android.phone, though I did it. The command you'll want to use to unlock the bootloader is fastboot flashing unlock, as stated at the top of this Google page
Click to expand...
Click to collapse
Why "flashing" and not "oem"? And then how do I install TWRP? The page you linked to has "install" zips and normal zips, not sure which I'm meant to download.
EDIT: Phone arrived, and is running 7.1.2.
Read the top of the Google page with the links to the Factory Images.
TWRP is temporarily booted using a PC with fastboot boot <TWRPfilename.zip> . Once you're in TWRP, you install the TWRP installer zip like any other zip. So the .img file stays on your computer (fastboot will load it onto your phone and boot into it), and the .zip goes on the phone so that you can install the TWRP installer.
post-mortem said:
TWRP is temporarily booted using a PC with fastboot boot <TWRPfilename.zip> .
Click to expand...
Click to collapse
Should that be the .img file, not the .zip file? Just guessing from context, otherwise you're using the zip file twice and the img file never.
So:
Unlock bootloader
Flash TWRP
Use TWRP to flash TWRP
Use TWRP to flash Magisk
Yes?
EDIT: Wait, that doesn't include flashing the system thing. When and how do I do that?
Unpopular opinion, but...
If I were you I would just use the phone as it is for at least a couple of days.
I don't want to sound like a Pixel fanboy but I'm liking the stock firmware much better than any custom ROM on this phone.
Of course I'm rooted and running a custom kernel, but I'm positive that Magisk will have the answers to most of your modding needs.
You got a new phone, why go out of your way and risk messing up stuff just to make it feel like your old one?
I mean, I'm cool with stock in theory, I just liked the debloated ROM I had last time because, well, debloating. And GMail and YouTube and such are now user apps on the S7, so my backups treat them as such.
Where do I find the drivers? I installed an "adb setup" thing that claimed to have them, but my PC isn't recognising the Pixel. Google's links to OEM drivers include a bunch of brands that aren't Google, so I'm not sure what to download.
EDIT: Okay, got it. Now running Android 9. When I'm installing TWRP, do I need to wipe anything? I miss the S7 forums and their one clear rooting guide that went step by step through everything.
koberulz said:
I mean, I'm cool with stock in theory, I just liked the debloated ROM I had last time because, well, debloating. And GMail and YouTube and such are now user apps on the S7, so my backups treat them as such.
Where do I find the drivers? I installed an "adb setup" thing that claimed to have them, but my PC isn't recognising the Pixel. Google's links to OEM drivers include a bunch of brands that aren't Google, so I'm not sure what to download.
EDIT: Okay, got it. Now running Android 9. When I'm installing TWRP, do I need to wipe anything? I miss the S7 forums and their one clear rooting guide that went step by step through everything.
Click to expand...
Click to collapse
No. just fastboot twrp img > flash zip via booted twrp. Reboot to system. That's all you gotta do
How do I boot into TWRP once installed? And come to that, what's the point of installing if I can boot to it regardless?
koberulz said:
There's an option to just create a flashable install of Titanium, and to back up its settings, which is what I've always done in the past. Is this different now?
Click to expand...
Click to collapse
Okay, this seems not to work. I've tried flashing it and there's no sign of the app at all.
koberulz said:
How do I boot into TWRP once installed? And come to that, what's the point of installing if I can boot to it regardless?
Click to expand...
Click to collapse
Doesn't the command fastboot boot twrp.img just boot it?
It does that for me, then I just have to flash twrp pixel installer.zip and it sticks.
I do this every time I update my factory image (which resets recovery to stock)
Anyways, I'm in. Had to manually install TB, then restore all my backups...and it screwed everything up big-time. Contacts are horribly broken; they initially kept crashing and now it says there's no contacts app installed. GMail crashes every time I open it. And the vibration has been replaced with a quiet beep.
I expected that... Just reflash latest factory image
Look, don't restore any apps, yet, especially any apps made by Google. You shouldn't need to restore any data, as all Google info is in the cloud, anyway. Just launch the app and log in to your Google account.
You don't need to "permanently" install TWRP if you don't want to.
I don't use Drive, so no it isn't.
I've managed to get everything over except my contacts. They killed it last time so I'm disinclined to try again. Not sure how else to get them over though.
My S7 had an "only display contacts with a phone number" option, does Pixel have an equivalent?
Since I don't have Xposed, I don't have any of my ad blockers. Are there options available?
I also had a lock screen with a tray of apps I could drag up to unlock straight into that app, the clock on the right instead of the left, and a percentage instead of just a battery icon on the lock screen and without swiping down. Any way I can set that up?
I tried Light Flow, but it doesn't seem to be working, I'm not getting any LED lights. It was working fine while I was setting up last night, but I unplugged the phone to go to bed and it's stopped.
I've looked at that Pie Aroma Mod Installer thing, but there's three files offered for download and I'm not sure what they are?
Is there a way to stop the screen turning on and the phone making a sound when I plug/unplug it?

Categories

Resources