Related
I have an ATT S5 (SM-G900A), completely stock, unrooted, updated to the latest 5.0 OTA update. My requirements for my phone are that it be able to pass Airwatch checks and that it be able to be encrypted (Personal device used at work). Some background first:
Last time I tried to play around with rooting, other mods, and whatnot was on my ATT S3 (I think I747?) and I discovered that an unspecified combination of rooting, installing a custom loader (CWM in my case) and installing a custom mod (Cyanogenmod at the time) made my phone unable to encrypt. At the time I was not required to use Airwatch, but encryption was required for my phone to connect to work, so I gave up on the whole lot.
I have now discovered that ATT, in their infinite wisdom, has replaced the S Voice drive mode with their own "ATT Drive Mode", and it's been verified they went so far as to remove the related APKs from the phone entirely. For those unaware, S Voice Drive mode is an feature of S Voice that (when turned on) reads out all callers and text messages, and then verbally prompts you for actions; reply, answer, ignore, etc. It allows fully hands free functionality. ATT Drive Mode, on the other hand, automatically kicks in whenever speeds of 20 MPH are detected (even if you're a passenger), rejects all calls and texts excluding a user-defined 5 person list, and essentially makes your phone useless anytime you're in a car. The goal is to "reduce texting and distracted driving", but as I'm on-call as part of my job and need to at least be aware of texts that come in within 10 minutes of receipt, it actually makes my drive much more dangerous. ATT Drive mode is a good idea for teens, perhaps, but i'm not a teen.
This brings me to my question: What are my options?
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
Honestly, the ideal solution would be something like the stock rom from the international version that would run on my ATT version...but I don't know if such a thing exists or is possible. I don't mind Samsung's cruft, but I do dislike ATT's lobotomizing of my phone to push their own little product that treats me like a kid. I know that I am less safe as a driver without the S Voice drive mode than I was with it.
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
sheaiden said:
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Waiting4MyAndroid said:
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Click to expand...
Click to collapse
Actually, while I greatly appreciate the fact that you took the time to reply (seriously! at least you took the time!), this is neither easy nor related to the questions I asked. If you look at my post, I'm not asking "how can I root", I'm asking three rather different questions:
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
In fact, I am unable to remain rooted (Airwatch; it's part of the post title), and the whole point and thrust of my question lies in the fact that I am looking to find out what affects encryption and what options I have as far as getting S Voice Drive mode on my phone while staying Airwatch compliant (not rooted). In addition, "if you can find the s voice drive app" is part of the problem too, as evidenced by the third question I asked above; I don't know where to find said app.
Does anyone know anything regarding what I was actually asking?
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
https://www.dropbox.com/s/oe7i2g81iuhjv38/S-Voice_Android_phone_J.apk?dl=0
Waiting4MyAndroid said:
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
Click to expand...
Click to collapse
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
sheaiden said:
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
Click to expand...
Click to collapse
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
OPOfreak said:
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
Click to expand...
Click to collapse
Interesting. I had been under the impression that I had seen people referring to installing clockworkmod or some similar thing on an S5, but I think I may be getting caught up in terminology; those are recoveries, aren't they? not bootloaders? Or perhaps people were posting about the other S5s with unlocked bootloaders. 15 different versions of S5, and I get stuck with the most apple-like of all the carriers....(in the sense of "you take what we give you and don't play with it!")
So, assuming I don't manage to get it installed via the link Waiting4MyAndroid was kind enough to post, I think that rules out anything other than the method of:
--wait for a root method to be established for the new OTA
--root, install the drive apk
--unroot, so I can encrypt and pass airwatch
Does anyone know if the old method of rooting broke encryption? and whether encryption was able to be performed after unrooting again?
Edit: Attempted to Sideload. Sadly, it is telling me "App not installed" (other sideloads do work; it's not the unknown sources setting). I'm thinking either the apk is marked for s4, and it's not compatible, or it's trying to overwrite files from the established svoice system, and that's not allowed. I suppose if someone has the drive apks from a tmobile S5 image or some such thing (same model, different carrier), then I could try again, but unfortunately this apk doesn't work. Thanks for the attempt, Waiting4MyAndroid!
I've got a S6 Active that when I received it was on Lollipop. I was able to flash MM (using thread here on XDA) to it before it was officially released from the carrier. Then I was able to flash back to stock Lollipop and then received the MM 6.0.1 update from the carrier. I wanted to flash back to Lollipop for testing purposes but was unable. I think it's because the bootloader is locked?
I've read a bunch of threads saying that the S6 active has nott been rooted? Has a locked bootloader? Can't run custom roms?
Can someone please give me the scoop on this. I'd like to go back to lollipop for testing but I don't think its possible. Is that the case? Thanks.
Roveer
roveer said:
I've got a S6 Active that when I received it was on Lollipop. I was able to flash MM (using thread here on XDA) to it before it was officially released from the carrier. Then I was able to flash back to stock Lollipop and then received the MM 6.0.1 update from the carrier. I wanted to flash back to Lollipop for testing purposes but was unable. I think it's because the bootloader is locked?
I've read a bunch of threads saying that the S6 active has nott been rooted? Has a locked bootloader? Can't run custom roms?
Can someone please give me the scoop on this. I'd like to go back to lollipop for testing but I don't think its possible. Is that the case? Thanks.
Roveer
Click to expand...
Click to collapse
hi
yes it's not possible to downgrade your rom or your bootloader because of the locked bootloader that prevents any try to modify the device...
is this typical of most phones? I've read of others frutrations about the S6 active still having a locked bootloader. Did I just pick a bad platform? Is S6 the same way? How about S7 series? Thanks.
roveer said:
is this typical of most phones? I've read of others frutrations about the S6 active still having a locked bootloader. Did I just pick a bad platform? Is S6 the same way? How about S7 series? Thanks.
Click to expand...
Click to collapse
Locked bootloaders are often the case for phones provided by carriers. While a phone purchased directly from the manufacturer is usually able to have its bootloader unlocked, carrier phones are locked by the carrier themselves, preventing any tampering by the end user. A custom ROM is any modified version of Android not developed by the company that made your phone. Think of it like a third party system. To get these custom ROMs onto your phone you must "flash" (simply, install) the ROM from your computer to your phone. However, a locked bootloader prevents this. While in some cases there are ways to get around carrier locked bootloaders, it is generally futile. If you purchased the S6 Active in hopes of tinkering around with custom ROMs, I'm afraid you have picked the wrong phone. The S6 Active, as of currently, is permanently locked to Samsung's and AT&T's "stock ROM"
EDIT: as for going back to Lollipop, the reason this is generally not possible is due to the fact that the Marshmallow update also updated critical parts related to the bootloader. It is impossible to roll back these changes once they have been made as they are strictly one way.
Thanks for the explanation. I didn't buy the phone for the express reason for changing android versions but rather to use as my daily driver. We are a BES 12 (Blackberry Enterprise Server) shop and I have found a bug that causes the VPN portion of the software to drop after an hour or so. Simply hitting the home button (waking the phone up re-establishes the vpn and mail flow continues). I'm working with BB to determine what's going on. I've disabled all power saving and doze settings yet still the problem. They are going to activate some other phones on my system to see if they see the problem. My reason for wanting to go back to lollipop is that I don't believe I saw this problem when I was on that OS so I was hoping to go back to confirm that behavior. I like the "active" phones for their ruggedness but don't have an unlimited budget to be buying handsets.
Roveer
roveer said:
Thanks for the explanation. I didn't buy the phone for the express reason for changing android versions but rather to use as my daily driver. We are a BES 12 (Blackberry Enterprise Server) shop and I have found a bug that causes the VPN portion of the software to drop after an hour or so. Simply hitting the home button (waking the phone up re-establishes the vpn and mail flow continues). I'm working with BB to determine what's going on. I've disabled all power saving and doze settings yet still the problem. They are going to activate some other phones on my system to see if they see the problem. My reason for wanting to go back to lollipop is that I don't believe I saw this problem when I was on that OS so I was hoping to go back to confirm that behavior. I like the "active" phones for their ruggedness but don't have an unlimited budget to be buying handsets.
Roveer
Click to expand...
Click to collapse
If the software you are referring to is something provided by blackberry, perhaps they need to patch their software for compatibility with Android Marshmallow. While not all software is broken by a major Android update, there are definitely some that are. Of course enterprise level software is entirely foreign to me (I'm only 17), so getting a second opinion on this issue would definitely be a good idea.
OK, I understand locked bootloader preventing from flashing any custom roms etc. Even preventing previous official android. Here's another question: Is there a way to flash current android version? I'm on G890AUCS4CPF3 which is an AT&T build. What is the carrier's method to reflash current OS when there has been some corruption to the version that is on the phone. Not just wipe, but reload entire android, re-create file system etc... That's what I want to try next. Blackberry has activated a Samsung S6 on my server and it (so far) is not exhibiting the same problem as my S6 Active. This leads me to believe that it my be a problem with my hardware. I want to do a reload at this point. Any ideas how I can do that? Odin flash? Is there a repository for the G890AUCS4CPF3 ROM?
Thanks,
Roveer
roveer said:
OK, I understand locked bootloader preventing from flashing any custom roms etc. Even preventing previous official android. Here's another question: Is there a way to flash current android version? I'm on G890AUCS4CPF3 which is an AT&T build. What is the carrier's method to reflash current OS when there has been some corruption to the version that is on the phone. Not just wipe, but reload entire android, re-create file system etc... That's what I want to try next. Blackberry has activated a Samsung S6 on my server and it (so far) is not exhibiting the same problem as my S6 Active. This leads me to believe that it my be a problem with my hardware. I want to do a reload at this point. Any ideas how I can do that? Odin flash? Is there a repository for the G890AUCS4CPF3 ROM?
Thanks,
Roveer
Click to expand...
Click to collapse
Carriers can tell if your Firmware is theirs or not because official Firmware is digitally signed by Samsung and AT&T.
As for using Odin, that would be your most viable option. However, I am not aware of any Odin images for the Marshmallow update on the S6A. As far as I know, Odin cannot get around the restriction of having a newer Bootloader, so you cannot flash down.
One thing you can try is to wipe cache partition. If that fails, factory reset from within the bootloader. Just make sure you've backed your data up.
EDIT: Take note that there is a difference in Firmware between the S6 vs the S6A.
EDIT 2: In your other thread you stated you can't flash back to lollipop due to a locked bootloader. This is actually due to, as stated before, the newest bootloader tha to the latest Android Marshmallow update.
FevenKitsune said:
Carriers can tell if your Firmware is theirs or not because official Firmware is digitally signed by Samsung and AT&T.
As for using Odin, that would be your most viable option. However, I am not aware of any Odin images for the Marshmallow update on the S6A. As far as I know, Odin cannot get around the restriction of having a newer Bootloader, so you cannot flash down.
One thing you can try is to wipe cache partition. If that fails, factory reset from within the bootloader. Just make sure you've backed your data up.
EDIT: Take note that there is a difference in Firmware between the S6 vs the S6A.
EDIT 2: In your other thread you stated you can't flash back to lollipop due to a locked bootloader. This is actually due to, as stated before, the newest bootloader tha to the latest Android Marshmallow update.
Click to expand...
Click to collapse
So I wiped the cache partition and factory reset within the bootloader and tried my app again. It continued to fail. I even found the MM image in the S6 Active MM thread and sideloaded it. It was only 400+ megs though. Still the app doesn't work so I'm starting to doubt that my problems are related to my particular S6 but its always a possibility. I'm trying to get Blackberry to dig up their own S6A and test on their own. They've been testing with a S6 for the past 2 days (on my BES server) and haven't seen the same problems, so it's either my device or a problem with the S6A (which as has been pointed out does use a different firmware version than the S6), but until I can get another S6 Active device to test I won't know.
Roveer
I tried installing several different ROMs onto my AT&T Galaxy Note 3 (N900A). I managed to downgrade to Android 4.4.2 and root the phone (from the current AT&T-forced OC3). I had different results for each ROM I tried. I used Safestrap to perform a Wipe of everything except my MicroSD card in the ROM Slot (#1) I was using before each ROM installation attempt.
Cyanogenmod (cm-13-20151101-UNOFFICIAL-hlte.zip) - Immediately produces a "failed" message trying to install from SafeStrap 3.75 hlteatt, because my phone is hlteatt and not hlte.
MagMa NX (MagMa_NX_UX10_Ultimate_XDA.zip) - Trying to install from Safestrap: progress bar freezes at 0% done.
Resurrection Remix (RR-N-v5.8.2-20170309-hlte.zip) - Installs successfully, but won't boot. First try reboot just stops on a black screen. 2nd reboot gives me the menu seen when booting with Vol Up + Home held down. (Is this the AT&T's firmware "bootloader?")
Any suggestions on getting any of these working? From reading other's experiences, it appears that some are successfully using some custom ROMs with this model phone. Barring that, what (stable) ROM works?
The phone has a locked bootloader; therefore, you can't install twrp. Only custom ROMs that are based off a stock rom and that can be flashed with safestrap will work.
I have yet to understand what it means for a bootloader to be "locked" in firmware/software terms. My initial reaction from the name is that the very first program the phone runs upon starting is the bootloader like a BIOS (apart from hardware self-testing), and the one that came with the phone cannot be bypassed to run a user-made one. But the existence of SafeStrap (originally leaked from Samsung iirc) shows the phone is capable of installing additional OSes. I would be very thankful if someone could provide a link or fill in my lack of knowledge about this.
From screenshots SafeStrap and TWRP almost look identical. I'm not sure what TWRP would do that SafeStrap can't. SafeStrap installed the Resurrection Remix ROM without complaining.
https://forum.xda-developers.com/wiki/Bootloader
Awesome, I'll unlock my bootloader then give it another try. Thanks!
EDIT: aha, that won't work. AT&T's "unlock" feature only allows the phone to be used with another carrier.
Solution: time to get a non-Samsung phone (definitely not from AT&T). This is all to stop being forcefed so many "offers" and "opportunities"—aka "spamware." For the life of me I can't think of a reason other than unchecked greed to deny the ability to remove unwanted software.
Only phones from att, sprint, and Verizon have locked bootloaders.
HTC is a good choice. M8 is a good cheap phone m10 is a good newer phone for 350ish
HTC phones are mostly all unlockable either for free by htcdev or if you require more then by sunshine for $25
Safestrap was not leaked by Samsung it was made by a dev named @Hashcode. He is very talented and worked hard also on the kindle scene. I believe he currently works for lenovo.
The software you are thinking of is odin.
It allows Samsung devices to flash firmware and software but it needs to be signed or your hardware needs to be unlocked. It will help a bootloop it will help you upgrade or get back to stock but it will not help you here.
Oh, thanks for the correction. That would explain why TWRP and SafeStrap look similar. (Neither looks like it is from a corporation.)
Do you mean that AT&T is technically capable of unlocking my phone so it can be flashed with a custom ROM that is not signed, e.g., Resurrection Remix?
Att is responsible for your locked bootloader.
Fun fact note3 was the first Samsung phone to be bootloader locked..
They requested it (demanded) of Samsung.
Verizon is even more demanding.
No, they will not unlock it.
It would be nice if after a device is no longer supported by a carrier they offered bootloader unlocks but that isn't happening either.
It is depressing that a 3 gig ram phone is stuck on lollipop.
I lent a phone out to a friend and received it back with the boot loader unlocked and the system, data, and internal storage wiped. I don't know if they were trying to run custom firmware or what.
I was thinking of just flashing something on it, but I was wondering if there would be any way to return it back to stock (or as close as possible). It was purchased from Google. Confirmed to be an Android One Moto X4, 32 GB from my order history.
I'm assuming that this is a US version XT1900-1.
The firmware is here: https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Here is a possible guide, I haven't done any this myself.
https://forum.xda-developers.com/moto-x4/development/rom-moto-x4-retail-android-pie-t3876156
dougo007 said:
I'm assuming that this is a US version XT1900-1.
The firmware is here: https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Here is a possible guide, I haven't done any this myself.
https://forum.xda-developers.com/moto-x4/development/rom-moto-x4-retail-android-pie-t3876156
Click to expand...
Click to collapse
Thank you so much. I was finding links to that repository, but I couldn't get any of the links to work. Yours did.
Edit: Just got it flashed and started it up. I'm a bit confused. The order screen shows it's an Android One Moto X4 from Google, but I know when I originally got it the bootup screen would play the Motorola "Hello moto" with the people flipping the f out. This one's just the Android One logo. Do I figure this out just by seeing if the OTA updates fail, and then I try a different channel?
Also, this dm_verrit notification, I'm guessing this would be because encryption was removed when he wiped it. Is there a way to re-enable that and remove the message?
I remember on the Nexus 5x there was an image you had to flash to avoid the notices about having a modified system image. Is there a similar way for me to get rid of the message stating that the phone is running different firmware after I've locked the bootloader?
Hi,
A question I hope someone can answer:
The short version; would this (N920PVPS3DQF1_N920PSPT3DQF1_SPR.zip) ROM be compatible with the N920P Note 5 variant that's currently on this (NRD90M.N920PVPS3DRH1) build number?
The long version; My GF has a Note5 of the Sprint N920P variety which she bought new in 2017(? The hardware version is N920P.04, if that matters). The phone is still on Android 7.0 (build number NRD90M.N920PVPS3DRH1)
The phone has (always had) lousy battery life and a tendency to crash at random, so I thought I'll take a crack at rooting the device to get some of the Sprint crap out, and maybe even install a more recent version of Android.
Apparently the latter will not happen (or is not worth trying as GF can't/will not deal easily with any obstacles/work arounds) as there seems to be no ROMs that's fully working on this Sprint version [is this really true?!]), but Magisk root route is still available, with one caveat.
When I went to look for a backup factory firmware (here), just in case something goes wrong, I could not find the ROM GF's phone has, and the closest one is this ROM (N920PVPS3DQF1_N920PSPT3DQF1_SPR.zip). Would it be compatible with her phone?
Also, is TWRP the only recovery available for this phone?
Thanks for any pointers
Rooting it is easy just use Magisk. The version of the zip looks ok. TWRP is the best - Not sure why you would want to use anything else. Also use TWRP to make a backup if possible. I used an OTG drive to make a backup.
Best rom so far is MOAR.Check XDA. Be aware banking apps detects rooted phones.
MarSOnEarth said:
Hi,
A question I hope someone can answer:
The short version; would this (N920PVPS3DQF1_N920PSPT3DQF1_SPR.zip) ROM be compatible with the N920P Note 5 variant that's currently on this (NRD90M.N920PVPS3DRH1) build number?
The long version; My GF has a Note5 of the Sprint N920P variety which she bought new in 2017(? The hardware version is N920P.04, if that matters). The phone is still on Android 7.0 (build number NRD90M.N920PVPS3DRH1)
The phone has (always had) lousy battery life and a tendency to crash at random, so I thought I'll take a crack at rooting the device to get some of the Sprint crap out, and maybe even install a more recent version of Android.
Apparently the latter will not happen (or is not worth trying as GF can't/will not deal easily with any obstacles/work arounds) as there seems to be no ROMs that's fully working on this Sprint version [is this really true?!]), but Magisk root route is still available, with one caveat.
When I went to look for a backup factory firmware (here), just in case something goes wrong, I could not find the ROM GF's phone has, and the closest one is this ROM (N920PVPS3DQF1_N920PSPT3DQF1_SPR.zip). Would it be compatible with her phone?
Also, is TWRP the only recovery available for this phone?
Thanks for any pointers
Click to expand...
Click to collapse
It's true that the N920P doesn't have a fully working custom rom available right now. You could try flashing noblelte but mobile data may not be working, and if it is, you may not get LTE, let alone CDMA.
Yes, N920PVPS3DRH1_N920PVPS3DRH1_SPR is the currently most recent that the stock rom version, so there is no benefit or reason to flash QF1 on it, since R comes after Q in the alphabet
TWRP is the only recovery for N920P.
Crossfire81 and ripee, thank you both.
GF lived, suffered, survived, and now with the T-mo/Sprint merger, she's moved on to an unlocked N10+ just last month, so the N5 is my to play with.
MarSOnEarth said:
Crossfire81 and ripee, thank you both.
GF lived, suffered, survived, and now with the T-mo/Sprint merger, she's moved on to an unlocked N10+ just last month, so the N5 is my to play with.
Click to expand...
Click to collapse
Great, if you want to give any feedback on roms on the SPR variant, find our threads and let us know.
Crossfire81 said:
Rooting it is easy just use Magisk. The version of the zip looks ok. TWRP is the best - Not sure why you would want to use anything else. Also use TWRP to make a backup if possible. I used an OTG drive to make a backup.
Best rom so far is MOAR.Check XDA. Be aware banking apps detects rooted phones.
Click to expand...
Click to collapse
Hello bro do you know if the n9020p has an lock or unlocked bootloader?