Right this might sound a little funny, but I've been given a horrible task of gaining access of my partner grandfather's phone who's recently pass away. I wanted to see if there's any advice or if a method of flashing twrp without having OEM unlock enabled or does anyone know any other known methods for gaining access.
I can understand the nature of this request so I understand if no one wishes to help
Have you tried fastboot commands? All you can do is wipe everything and start fresh. TWRP requires Android 9, a custom kernel, and unlocked bootloader.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Related
Hello. I'm pretty terrible at all this rooting stuff (or at least, I only do it once for each android phone I get, and then don't really look into it or stay up to date on all of it afterwards, I just use a few pluses that come along with being rooted).... Anyways, I really do need some help this time, as the confusion has really gotten to me, and I've lacked being able to find some simple answers (probably because they are just THAT simple) on google/reddit/on this forum.
Anyways, I've rooted my phone awhile back, lost it when my verizon pixel auto updated to 7.1.1 (idk how or why, pretty sure I had that disabled with root even, very frustrated) and even attempted to regain root by flashing SU with TWRP, but for some reason SU said I didn't have root still, and eventually just gave up in frustration. But now, my verizon pixel has been shutting off at ~40% battery power, and I read in the google forums that this was patched in the 7.1.2 update for pixels, and it was a software glitch rather than a malfunctioning/bad battery... So now I really want to upgrade to 7.1.2 from 7.1.1 not only to fix the battery/software issue, but also because I really want root.
I have an unlocked bootloader from when i first got my pixel and did this stuff, but now im unrooted on 7.1.1 because of that update awhile back, and want to update to 7.1.2 and root, but I've heard theres issues with rooting on the verizon because of bootloader, but that shoulden't be an issue since I unlocked it already (right? at least, I think? please let me know).
My only question (since i think i'll be able to follow this guide once I get the answer to this) is in the post he says: "Works with 7.1.2 (NJH47F, Aug 2017)".......... but since i have the verizon pixel (small version, not XL), should i be downloading this version: 7.1.2 (NHG47Q, Aug 2017, Verizon).... Or would it just be acceptable to allow my phone to auto download the update i have on it right now? Or must I download the NON verizon version as stated in the post and flash that one? Thanks for the help guys!
Thanks for any help!
-Synk
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
jhs39 said:
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
Click to expand...
Click to collapse
Thank you so much for the explanation. Truly, it's actually crazy how I was unable to find all of this neatly, nicely, and simply stated. Great to hear, I'm going to go on rooting, here's to hoping I don't blow it up.
Hi guys, I finally decided to replace my good old Galaxy S7 edge and I came to the conclusion that I wanted, after using Samsung, OnePlus and Sony phones for years, the most streamlined Android experience possible without having to deal with OEM bloat, delayed updates, etc. anymore.
Result: I made the most obvious choice and I got an unlocked white 128GB Pixel 2 XL from the Google Store directly (I can't wait to receive it!).
I have a few questions though...
1) Will unlocking the bootloader alone (without actually rooting the phone) cause OTA updates to fail?
2) It's now possible to root your phone with Magisk without installing a custom Recovery (TWRP). Once installed, Magisk allows you to temporarily restore the stock, unrooted "boot.img". Is it enough for OTA updates to install properly or will they fail as soon as Magisk has been installed, even if the stock boot.img has been restored?
3) Does the Pixel 2 have an "e-fuse" that will get triggered once the bootloader is unlocked that will cause features to not work properly anymore, like on Samsung phones?
4) Any other recommendations or things I should be aware of?
Thanks guys
Only other thing I would read up on is how to work around the whole dual slots "feature" that these Pixel phones have. The last couple times I've tried to update to the latest security update, I get a "your device is corrupt and cannot be trusted" message and the phone won't boot. I end up have to scramble to flash stock boot.img to both slots A and B, flash the factory image to both slots, and hold my breath as to whether or not it's going to work. I wish there was an idiot's guide to updating firmware for this phone. Everyone that posts on this subject has a different opinion on how to do it properly. Going form any given security update rooted with Magisk, how does one update to the next month's firmware, without temporarily bricking the phone or wiping data? I've been unlocking phones and flashing custom roms since before Android was even invented. So I'm no stranger to this stuff, but it has become quite a production to keep up to date with this stuff.
Phazonclash said:
Hi guys, I finally decided to replace my good old Galaxy S7 edge and I came to the conclusion that I wanted, after using Samsung, OnePlus and Sony phones for years, the most streamlined Android experience possible without having to deal with OEM bloat, delayed updates, etc. anymore.
Result: I made the most obvious choice and I got an unlocked white 128GB Pixel 2 XL from the Google Store directly (I can't wait to receive it!).
I have a few questions though...
1) Will unlocking the bootloader alone (without actually rooting the phone) cause OTA updates to fail?
2) It's now possible to root your phone with Magisk without installing a custom Recovery (TWRP). Once installed, Magisk allows you to temporarily restore the stock, unrooted "boot.img". Is it enough for OTA updates to install properly or will they fail as soon as Magisk has been installed, even if the stock boot.img has been restored?
3) Does the Pixel 2 have an "e-fuse" that will get triggered once the bootloader is unlocked that will cause features to not work properly anymore, like on Samsung phones?
3) Any other recommendations or things I should be aware of?
Thanks guys
Click to expand...
Click to collapse
To answer your questions.....
1. No
2. Yes. But you'll have to unroot and completely uninstall magisk to take the OTA.
3. No
4. There are several guides to explain how to unlock the bootloader, install twrp, kernels, and root. Let me know if you'd like links, or you can search on your own if you'd like. Welcome to the P2XL. We hope you enjoy your stay ??
Hi XDA
I have a son with Asperger syndrome and that give parents sometimes unusual task to solve.
He got a Sony xz2 compact, but he refuses to use a phone until the camera and google services are disabled, do to security lags. He wants to remove the system camera software to make sure no one can exploit the camera.
In other words, he wants to be so anonymous and hacker free as possible - and the camera is a big issue for him.
And yes, I know is possible to disable the camera in Sony configuration (and it's done) but that is not enough.
I hope getting some help to find a solution this two tasks:
1) How to get or make an image of the phone to store/save in my pc so it can be restored if needed.
2) How to root the xz2 compact and uninstall the camera
I will really appreciate some help in this issue.
(sorry my English)
Regards.
1. There is not much you can do, backup related on a Sony phone with locked bootloader. You can use google backup, if you want, but even Sony's solution won't work on a phone with Android Pie, after bootloader is unlocked (it would, if you are on Oreo and you would apply drm-fix after unlocking). Almost all other solutions need root, which you don't have on a locked phone.
2. In this thread you will find a step-by-step guide to install twrp recovery and root (by flashing Magisk) and the download for twrp recovery, made by @MartinX3
I won't link the recovery file itself, because it depends on the way you want to proceed. You can use Sonys stock rom or you can install aosp/omnirom.
In your case i would use aosp or omnirom, because it comes without google crap and it is pure Android. You only need to delete/rename the camera with a root explorer and you are good to go.
But i'm sure, @MartinX3 can tell you more about aosp or omnirom and how to flash it, because i have not used it yet. Anyway, camera is not finished on aosp/omni, so you won't loose very much.
old.splatterhand said:
1. There is not much you can do, backup related on a Sony phone with locked bootloader. You can use google backup, if you want, but even Sony's solution won't work on a phone with Android Pie, after bootloader is unlocked (it would, if you are on Oreo and you would apply drm-fix after unlocking). Almost all other solutions need root, which you don't have on a locked phone.
2. In this thread you will find a step-by-step guide to install twrp recovery and root (by flashing Magisk) and the download for twrp recovery, made by @MartinX3
I won't link the recovery file itself, because it depends on the way you want to proceed. You can use Sonys stock rom or you can install aosp/omnirom.
In your case i would use aosp or omnirom, because it comes without google crap and it is pure Android. You only need to delete/rename the camera with a root explorer and you are good to go.
But i'm sure, @MartinX3 can tell you more about aosp or omnirom and how to flash it, because i have not used it yet. Anyway, camera is not finished on aosp/omni, so you won't loose very much.
Click to expand...
Click to collapse
Thanks for the useful information. I'm not very firm at the Android version (oreo or pie) - but the phone is a Sony Experia xz2 model H8324 and Android ver. 8.0.0 (patch level april 1, 2018). Hope this make sense
This is my first sony, so i'm not the "most helpful hand", i think.
Backup related, if you use sony backup before unlock on oreo, you can flash drmfix after unlock and then you should be able to use sony backup to restore your data.
If this is successful, you are rooted and you should be able to use Titanium Backup.
But as sony newbie i don't know how far sonys backup solution goes.
Anyway, i'll recommend in your case a rom like aosp or omni, because there are no Google things in it.
Why not cover the cameras with stickers if that's the biggest issue? You'll have to root the phone to completely disable all the G Apps, some of the firmware versions allow you to completely disable the G services - if you trust it.
You can use pm uninstall command thru adb shell. This way the app gets removed for the user, and thus seems totally removed. The apk itself do still remain in the system folder, and can be reinstalled if wanted, but can't be launched. This method do not need rooting either.
You can't make and image of the phone, at least not without rooting it first. But that will break some stuff, like camera, and that can NOT be restored in ANY way (drm keys are lost forever). For most (all?) Xperia devices there are images available for flashing with FlashTool/Xperifirm, but note that this will not recover the lost drm keys if you unlocked the bootloader in the first place.
Just want to know how i can go about re locking the device to set up G-pay
Don't want to end up bricking the device,
Anyone able to assist?
If you are 100% stock, and have a backup of everything of importance, as this will wipe your device, just execute: fastboot flashing lock
I relocked my bootloader on Q DP3, no luck using Google Pay. The beta rom is not CTS compatible.
collindubya said:
Just want to know how i can go about re locking the device to set up G-pay
Don't want to end up bricking the device,
Anyone able to assist?
Click to expand...
Click to collapse
Several people in the Pixel 3 forum are reporting issues with Google Pay on Beta 3, but I used it Tuesday afternoon with no issue. I haven't tried again yet but I updated in the afternoon and rebooted to complete the update when I got in my car to go home. Stopped at the store on the way and used Google Pay without issue.
Gpay works. Did you wipe your wipe after relocking it? I know it says it wipes it. But doesn't truly wipe everything unless you access factory recovery and wipe it there too. I relocked my bl and gpay works fine. Beta 3 is certified now. Look in play store settings. Certified. So everything will work now. Having the oem ticked on with the bl locked will also deny some features. That switch has to be off to be truly locked. After relocking you have to go into settings and flip that off. It will be on after relocking.
So I have successfully unlocked my motorola by following the official guide but am stuck on the next step because I don't know what I'm supposed to download next. I installed magisk from the official github onto my phone but that's about it. Thanks in advance for any help.
Which rom are you using?
So all I have done so far is unlocked my bootloader, do I need to download a rom next. I'm very inexperienced on this subject and saw a video of the different cool customizations you can do with a rooted phone.
So, there are two different things.
1. rooting gives you access to system files, so they can be modified/erased etc.
2. a custom ROM doesn't necessarily give you root access, but it can give you cool customizations built-in, or a newer version of Android, for example.
Personally I'm not a big fan of rooting in general. Because that comes with a couple of caveats. One being that your banking apps won't work anymore, unless you fiddle with magisk stuff to make it show like the device is not rooted, and stuff like that. I don't need root, so I don't generally need Magisk either.
But if you want to try a cool ROM for this phone, and you like stock Android, you could try the Pixel Experience ROM. The only thing that doesn't work (and I don't know how to fix right now), is VoLTE and VoWIFI. But it might work for you.
LineageOS works for VoLTE (with IMS APN added by the user), but still doesn't work for VoWIFI. It could be that it requires a few specific files to be flashed from the stock ROM. I don't know. So far I couldn't get it to work.
So, next step would be either staying on stock ROM, and fiddling with Magisk (but keep in mind some DRM apps won't work, some payment stuff won't work and so on so forth), ooor go flash a custom ROM (such as Pixel Experience), and enjoy it the way it is.
The choice is yours.
One advice I have: don't relock the bootloader unless the option in Developer Options > OEM Unlocking is ON. Doesn't matter if it's greyed out or not. But it needs to be ON.
Why? Because, if something happens and you can't boot because you locked your bootloader on a custom ROM for example (which you should never do, by the way), you won't be able to unlock it again, so you can fix your boot, if that option is OFF. So be very careful with that.
When that option is ON, it means bootloader is allowed to be unlocked (it's unlockable). When it's OFF, it's not. If it's not unlockable, you can't unlock it, so you can't flash anything. Which is really bad if you need to fix something and the only way is flashing.
Ok, I took some time to reflect based on what you said. I really do value being able to use banking apps so i guess I will try to fiddle with magisk stuff after I root my device. Speaking of which I was following this guide and I went through the procedure twice but for some reason after I ran the root checker plus app from the play store it says that root was not properly installed. Not sure what part of the process I did wrong but I await any feedback.
Technically, all you need is Magisk installed. That will also give you root access. You don't need anything else.
But maybe flashing was not done right? I don't know. Do you get an error? If so, it would be good to know which error.