Related
what information do we have on rooting after the 4.4.2 ota update? Also is there any information on unlocking the bootloader? I'm trying to see what other people have tried before I keep going at the same things that have failed. Also is there any information on changing the imei/flashing this? My end goal is cyanogenmod on Virgin Mobile. I've done this with other phones and I just got my hands on this one but there doesn't seem to be as much into on this as others.
Tldr version
Root after 4.4.2 ota?
Unlock Boot loader after ota?
Is it flashable to virgin mobile?
Kin Kira said:
what information do we have on rooting after the 4.4.2 ota update? Also is there any information on unlocking the bootloader? I'm trying to see what other people have tried before I keep going at the same things that have failed. Also is there any information on changing the imei/flashing this? My end goal is cyanogenmod on Virgin Mobile. I've done this with other phones and I just got my hands on this one but there doesn't seem to be as much into on this as others.
Tldr version
Root after 4.4.2 ota?
Unlock Boot loader after ota?
Is it flashable to virgin mobile?
Click to expand...
Click to collapse
Root after 4.4.2 ota? no not yet unless your unlocked.
Unlock Boot loader after ota? no probably never.
Is it flashable to virgin mobile? maybe, not 100% sure but check out this thread by @dragonhart6505 http://forum.xda-developers.com/showthread.php?t=2389740
billycar11 said:
Root after 4.4.2 ota? no not yet unless your unlocked.
Unlock Boot loader after ota? no probably never.
Is it flashable to virgin mobile? maybe, not 100% sure but check out this thread by @dragonhart6505 http://forum.xda-developers.com/showthread.php?t=2389740
Click to expand...
Click to collapse
****. So I'm holding an unrootable piece of crap? What information do we have on methods of root attempted and such. Maybe I can contribute to this I've got nothing but time.
Edit: your thread unlocks gsm support. VM would probably need me to reprovision everything and change my IMei to match a donor phone.
I've been attempting various root methods for 4.4.2 and for the RAZR in general. I've had no luck. Is there a collective of people working on this cause I'd love to contribute however I can.
root xt926 4.4.2 Solved with towelroot apk
Kin Kira said:
I've been attempting various root methods for 4.4.2 and for the RAZR in general. I've had no luck. Is there a collective of people working on this cause I'd love to contribute however I can.
Click to expand...
Click to collapse
google towelroot apk click on upsidedown y to download apk and install apk on phone run it and your in business. :good::good::good::good:
juliolopez76 said:
google towelroot apk click on upsidedown y to download apk and install apk on phone run it and your in business. :good::good::good::good:
Click to expand...
Click to collapse
Just as an FYI, that is called "lambda" which is a greek symbol.
Also, this works on 183.46.10 (the current KK ota that came out a few months back), but it does NOT work with the latest soak test (183.46.14), so you need to stay on 183.46.10, root with towelroot and then unlock your bootloader. If you do not do this AND if you take the soak test, you will be unable to root as a root exploit for 183.46.14 does not exist.
I don't want to say it won't ever be rooted, but as more and more exploits are patched up, it becomes harder and harder to root this phone, so your best bet is to root and unlock the bootloader on 183.46.10. Don't take the chance on whether a root exploit will be found or not. You'll save yourself, and the rest of us, a lot of headaches.
If you have already applied the 183.46.14 before rooting and unlocking your bootloader, you are SOL. There is NO way to go back to the previous version and root and unlock, so please do NOT ask how to revert back from the current soak test (183.46.14) and root and unlock your bootloader because you can't. You just can't, so don't ask.
I repeated what I just said because people always ask "well, if you flash back to 183.46.10". The problem is, the exploit that allowed unlocking of the bootloader is in a protected area that even unlocked bootloaders cannot write to without the proper encrytion keys. Once that area has been patched via the latest soak test, you have no way to write over it again because you would need the proper encryption key inside the image to flash in order for it to work. Unless Motorola becomes nice and gives you the key, it won't work. And the previous OTA's key is now invalid, so again, flashing the previous FXZ (183.46.10) will not work. It will just skip writing the protect area.
Clear as mud? Hopefully.
thats lambda....but you knew that
I've searched high and low and I'm not able to find a non-tripping version of root. I don't want any fancy roms just rooted stock. Help.<br/>
Nope no way to keep Knox as of now.
But the root method that's out there. Will just flash a recovery and root. It's shouldn't f change the system image. (I could be wrong but last I check.)
I like to keep Knox just in case I need to exchange the phone for any reason
Whats the best method if you have a USA AT&T note edge?
Looking for a way to root without tripping Knox as well...
Someone should start a pledge thread for it, that should get the devs interested...
Beach_Head said:
Looking for a way to root without tripping Knox as well...
Someone should start a pledge thread for it, that should get the devs interested...
Click to expand...
Click to collapse
Probably won't come for a while since not alot of devs have the phone yet.
NitroSS said:
Whats the best method if you have a USA AT&T note edge?
Click to expand...
Click to collapse
There is no current way to root the N915A. AT&T has it locked and so far no one has bothered to try to get it unlocked to achieve root.
Sent from my Samsung Note Edge using Tapatalk
In the same boat witha 915FY , willing to chip in if needed.
I'm sure I read it somewhere, just can't remember ATM....but there is a way to reactive Knox After rooting correct? I have the tmobile n915t.
strboy said:
I'm sure I read it somewhere, just can't remember ATM....but there is a way to reactive Knox After rooting correct? I have the tmobile n915t.
Click to expand...
Click to collapse
Dont think so mate... else what would be the point ? or even the hold up here ? just root and reset ?
If it were possible it woulda been announced by now i guess...
strboy said:
I'm sure I read it somewhere, just can't remember ATM....but there is a way to reactive Knox After rooting correct? I have the tmobile n915t.
Click to expand...
Click to collapse
As I understand it, KNOX flag is basically written as a "fuse". Once it's triggered, there's no going back.
And everyone, for the love of all things good and pure, AT&T and Verizon have locked bootloaders and there are NO root methods currently available. KNOX is irrelevant.
Finally, for anyone wondering about a non-KNOX-tripping method for actually ROOTABLE devices, nope. Not yet as far as I know. But why? Carriers still service phones that have the flag tripped.
jooniloh said:
As I understand it, KNOX flag is basically written as a "fuse". Once it's triggered, there's no going back.
And everyone, for the love of all things good and pure, AT&T and Verizon have locked bootloaders and there are NO root methods currently available. KNOX is irrelevant.
Finally, for anyone wondering about a non-KNOX-tripping method for actually ROOTABLE devices, nope. Not yet as far as I know. But why? Carriers still service phones that have the flag tripped.
Click to expand...
Click to collapse
In theory yes , you still get serviced but that mostly depends on the IQ of the person on the other end.
Im currently in Portugal. I took my note 3 to service and the knox was tripped . Battery Issue. They refused . I called customer service. They refused.
"If you tampered with the device, its your own fault"
I explained in other countries its still serviced , in France for example.
"this is not other countries , this is not France."
I have a 915FY now and , if possible , I would like to avoid this situation.
siriom said:
In theory yes , you still get serviced but that mostly depends on the IQ of the person on the other end.
Im currently in Portugal. I took my note 3 to service and the knox was tripped . Battery Issue. They refused . I called customer service. They refused.
"If you tampered with the device, its your own fault"
I explained in other countries its still serviced , in France for example.
"this is not other countries , this is not France."
I have a 915FY now and , if possible , I would like to avoid this situation.
Click to expand...
Click to collapse
Hmm I see. I wasn't aware of that issue. The service centers here have seen that the KNOX flag is tripped on my devices and still serviced them. All I can say is, pretty much everything that works for the note 4 (except roms) has been compatible with the edge (including root tools, TWRP, recovery-flashable mods, system file tweaks, etc.), so if any progress is made on finding a non-KNOX-tripping method, you're gonna see it on the Note 4 forums first. I'd keep an eye on that for any updates concerning your model.
I was hoping Geohots work on TowelRoot might be adapted somehow for 4.4.4 and eventually used for Note4/edge.(it stopped working for anything over 4.4.2 i was told)
I heard hes working for google now so he cant help anymore...
siriom said:
I was hoping Geohots work on TowelRoot might be adapted somehow for 4.4.4 and eventually used for Note4/edge.(it stopped working for anything over 4.4.2 i was told)
I heard hes working for google now so he cant help anymore...
Click to expand...
Click to collapse
Towelroot was only ever supposed to work on the S5. That it worked on anything else at all was chance. Anyways, it hasn't been updated in ages so don't hold your breath. If you really need root, I'd just go with one of the available methods. If you need it serviced, flash a stock ROM, go to a service center for your carrier, and act stupid. Don't start talking about root and all that. That has worked 100% of the time for me. When you took it in for service in the past (when they didn't service it) was your phone still rooted or have a custom recovery installed?
i think he did, or i do not know how to navigate his site. can anyone double check?
Did you see this part at the end of the instructions?
"UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !"
I reckon if you're on stock NRD90M.G920VVRS4DQD1 your bootloader is locked.
isn't it possible to downgrade and upgrade Verizon roms for the G6 as long as we remain anove 5.1.1?
by the way, there are two Nougat roms available for the G6 over at samsung-updates, one ends in ...DQD1 and the otherone ends i ...DQE1.
There is a root from Vhai fire for the ...DQD1, not for the other one, but... because both roms are Verizon's and meant for the same device, flashing either one shouldn't brick the device, because both have Verizon's digital signature.
is that how it works?
***
honestly i just want to root the phone, im fine with the stock firmware.
nevermind, you are totally right. however, the fact that chainfire released a root for the ...DQD1 tells me he had to have unlocked the bootloader first, which now brings us to the question... how did he unlock the bootloader?
You could downgrade to the OK7 firmware and root that. The string attached is that you will need to run MrMike2182's rootatboot script every time you want to boot the phone.
so has anyone tried this? does it work?
I know it trips KNOX but i don't really care. i just dont want a brick.
EvilRubberDuck said:
Did you see this part at the end of the instructions?
"UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !"
I reckon if you're on stock NRD90M.G920VVRS4DQD1 your bootloader is locked.
Click to expand...
Click to collapse
sikk, then all i need is a unlocked bootloader and im rooted! :good:
Arethmetik said:
sikk, then all i need is a unlocked bootloader and im rooted! :good:
Click to expand...
Click to collapse
Good luck for that Verizon won't budge and there's no development at all.
xdanilva said:
Good luck for that Verizon won't budge and there's no development at all.
Click to expand...
Click to collapse
This makes me so sad. What phone should I get next that is root-friendly, i.e. I can keep the software/firmware up to date and still keep my root.
Smidley said:
This makes me so sad. What phone should I get next that is root-friendly, i.e. I can keep the software/firmware up to date and still keep my root.
Click to expand...
Click to collapse
Any phone that doesn't use verizon or at&t as a carrier
---------- Post added at 05:04 AM ---------- Previous post was at 05:03 AM ----------
There's temporary root for this phone and it works but that's it
xdanilva said:
Any phone that doesn't use verizon or at&t as a carrier
---------- Post added at 05:04 AM ---------- Previous post was at 05:03 AM ----------
There's temporary root for this phone and it works but that's it
Click to expand...
Click to collapse
Thanks for the reply.
Is US Cellular root-friendly? I've been waiting for the Pixel 2 to be released, but I want to make sure I can root it and still keep it up to date.
Also, I am still interested in the temporary root on the S6 if it means I can update to Nougat. Looking into MrMike2182's rootatboot now. Thanks!
Smidley said:
Thanks for the reply.
Is US Cellular root-friendly? I've been waiting for the Pixel 2 to be released, but I want to make sure I can root it and still keep it up to date.
Also, I am still interested in the temporary root on the S6 if it means I can update to Nougat. Looking into MrMike2182's rootatboot now. Thanks!
Click to expand...
Click to collapse
S6 root only runs under android 5.1.1 also you need a vm to flash the kernel to the phone. Us cellular is root-friendly. Only at&t and verizon and sprint and T-Mobile lock their bootloaders.
leandrummer said:
nevermind, you are totally right. however, the fact that chainfire released a root for the ...DQD1 tells me he had to have unlocked the bootloader first, which now brings us to the question... how did he unlock the bootloader?
Click to expand...
Click to collapse
Chainfire just runs an automated script which generates a CF-Auto-Root file for ANY model, whether the bootloader is locked or not.
So the answer is, he didn't unlock it, but simply generated a file regardless, and it's up to the user to figure out the their bootloader status.
Smidley said:
Thanks for the reply.
Is US Cellular root-friendly? I've been waiting for the Pixel 2 to be released, but I want to make sure I can root it and still keep it up to date.
Also, I am still interested in the temporary root on the S6 if it means I can update to Nougat. Looking into MrMike2182's rootatboot now. Thanks!
Click to expand...
Click to collapse
Same as Verizon, it's locked down tightly.
Your best bet would be a Sprint version, which has an unlocked bootloader and can be unlocked for both GSM (ATT /TMO) and LTE (VZW) with the proper equipment (unlocking boxes). Or the Tmobile version also has an unlocked bootloader which can be unlocked using online unlocking services but it will only work with GSM cards (ATT/TMO, no VZW!). Both can be rooted via CF-Auto-Root and/or through custom recovery.
Temp root can let u flash a recovery. That's all u need
jerryspring said:
Temp root can let u flash a recovery. That's all u need
Click to expand...
Click to collapse
The bootloader is locked you can't flash a custom recovery
Shaden Stewart said:
The bootloader is locked you can't flash a custom recovery
Click to expand...
Click to collapse
Yes... I know...it's a hypothetical statement. Lol
Would it be possible to sign packages like twrp or cwm to bypass the bl
I think no need to Downgrade the firmware if there is another method to root the phone without unlocking bootloader that is called ENG Root here is a link to download G920V ENG Root Bit4+How to Flash
G920V ENG Root
h2five said:
I think no need to Downgrade the firmware if there is another method to root the phone without unlocking bootloader that is called ENG Root here is a link to download G920V ENG Root Bit4+How to Flash
G920V ENG Root
Click to expand...
Click to collapse
Thanks for the nice info,
Just curious what is Bit4? Can we flash this Eng Root to SM-G920V 7.0 but Bit4 is confusing me
please guide me in details
h2five said:
I think no need to Downgrade the firmware if there is another method to root the phone without unlocking bootloader that is called ENG Root here is a link to download G920V ENG Root Bit4+How to Flash
G920V ENG Root
Click to expand...
Click to collapse
U sure u aren't posting spam?
I have the Google Pixel on Verizon Android version 7.1.2 and Build Number NHG47Q with the latest August 5, 2017, security patch. Is it possible to unlock the bootloader and root? I purchased the Soft-Skip toolkit from mskip but have been unsuccessful trying to root and that thread doesn't have much action in it. I've read in a few other threads that it isn't possible to root with unlocking BL. So I'm confused and am wondering if any of you have other information.
No
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
No
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
haha, thought so.
Ever since I learned about the Google Pixel being unlocked and rooted with Verizon 7.1.1 version, I've been kicking myself for stupidly updating to 7.1.2. Well, it been a while and my phone is pressing me to update to 8.0. I've been searching for a temp root to edit the build.prop with no avail. My Question is after hesitating then giving kingroot one more shot for root access, is there a workaround for access? Here's what I have so far....
According to kingroot, it says "root successfully" however it also says "Notice: this model restricts ROOT authorization"
Looking at the OEM unlock from developer options, it's still greyed out.
Any help or solutions here?
ShadowWeasel said:
Ever since I learned about the Google Pixel being unlocked and rooted with Verizon 7.1.1 version, I've been kicking myself for stupidly updating to 7.1.2. Well, it been a while and my phone is pressing me to update to 8.0. I've been searching for a temp root to edit the build.prop with no avail. My Question is after hesitating then giving kingroot one more shot for root access, is there a workaround for access? Here's what I have so far....
According to kingroot, it says "root successfully" however it also says "Notice: this model restricts ROOT authorization"
Looking at the OEM unlock from developer options, it's still greyed out.
Any help or solutions here?
Click to expand...
Click to collapse
You don't have to have an unlocked bootloader in order to root. I've had plenty of Samsung's with root and no unlocked bootloader.
---------- Post added at 06:19 PM ---------- Previous post was at 06:04 PM ----------
Digital DJ said:
I have the Google Pixel on Verizon Android version 7.1.2 and Build Number NHG47Q with the latest August 5, 2017, security patch. Is it possible to unlock the bootloader and root? I purchased the Soft-Skip toolkit from mskip but have been unsuccessful trying to root and that thread doesn't have much action in it. I've read in a few other threads that it isn't possible to root with unlocking BL. So I'm confused and am wondering if any of you have other information.
Click to expand...
Click to collapse
In general an unlocked bootloader is not a prerequisite for root. I've had several phones with a locked bootloader but with root.
Tulsadiver said:
You don't have to have an unlocked bootloader in order to root. I've had plenty of Samsung's with root and no unlocked bootloader.
Click to expand...
Click to collapse
It claims to be rooted, but is not.... Any tips? I'm still trying both mobile and PC version. I'm kinda thinking of something between injecting thru ADB (not side loading) to finding out a way to decompile dePixel8 to make changes then recompile it to make it work. Only thing about the latter is it's years that I have done any type of actual programming and would like some steps from jcase or beaups.
---------- Post added at 02:15 AM ---------- Previous post was at 01:26 AM ----------
Here's everything I've done on rooting so far.... And supposedly kingroot apk is only way.
Others that failed includes kingroot (PC), iroot (both variants), kingoroot (both variants), skipsoft unified toolkit, Nexus root toolkit (don't ask, I leave myself open to possibilities), towelroot, z4root, pootroot, weaksauce, etc. (Even root methods as far back as to gingerbreak.)
One thing that is on my mind though is when you bring up the bootloader it shows it's being ran by Samsung?!? Any theories on that? I'm kinda leaning on looking backwards on how Samsung bootloader's were unlocked through ADB or fastboot. I remember back then there was a certain way of doing that, but my mind is moving so fast that I'm having a hard time remembering.
ShadowWeasel said:
It claims to be rooted, but is not.... Any tips? I'm still trying both mobile and PC version. I'm kinda thinking of something between injecting thru ADB (not side loading) to finding out a way to decompile dePixel8 to make changes then recompile it to make it work. Only thing about the latter is it's years that I have done any type of actual programming and would like some steps from jcase or beaups.
---------- Post added at 02:15 AM ---------- Previous post was at 01:26 AM ----------
Here's everything I've done on rooting so far.... And supposedly kingroot apk is only way.
Others that failed includes kingroot (PC), iroot (both variants), kingoroot (both variants), skipsoft unified toolkit, Nexus root toolkit (don't ask, I leave myself open to possibilities), towelroot, z4root, pootroot, weaksauce, etc. (Even root methods as far back as to gingerbreak.)
One thing that is on my mind though is when you bring up the bootloader it shows it's being ran by Samsung?!? Any theories on that? I'm kinda leaning on looking backwards on how Samsung bootloader's were unlocked through ADB or fastboot. I remember back then there was a certain way of doing that, but my mind is moving so fast that I'm having a hard time remembering.
Click to expand...
Click to collapse
I don't have any tips. Just trying to clear up a misunderstanding about bootloader and root.
---------- Post added at 07:32 PM ---------- Previous post was at 07:31 PM ----------
ShadowWeasel said:
It claims to be rooted, but is not.... Any tips? I'm still trying both mobile and PC version. I'm kinda thinking of something between injecting thru ADB (not side loading) to finding out a way to decompile dePixel8 to make changes then recompile it to make it work. Only thing about the latter is it's years that I have done any type of actual programming and would like some steps from jcase or beaups.
---------- Post added at 02:15 AM ---------- Previous post was at 01:26 AM ----------
Here's everything I've done on rooting so far.... And supposedly kingroot apk is only way.
Others that failed includes kingroot (PC), iroot (both variants), kingoroot (both variants), skipsoft unified toolkit, Nexus root toolkit (don't ask, I leave myself open to possibilities), towelroot, z4root, pootroot, weaksauce, etc. (Even root methods as far back as to gingerbreak.)
One thing that is on my mind though is when you bring up the bootloader it shows it's being ran by Samsung?!? Any theories on that? I'm kinda leaning on looking backwards on how Samsung bootloader's were unlocked through ADB or fastboot. I remember back then there was a certain way of doing that, but my mind is moving so fast that I'm having a hard time remembering.
Click to expand...
Click to collapse
I don't have any tips. Just trying to clear up a misunderstanding about a unlocked bootloader and root.
If I had the skills I think I would find someone with a pixel 2. Load an assembly language debugger and run the fastboot command that unlocks the pixel 2. If the same command could be injected into the pixels fastboot binary running on the phone you might trick it into unlocking just like the pixel 2.
Sent from my Pixel using Tapatalk
baknblack said:
If I had the skills I think I would find someone with a pixel 2. Load an assembly language debugger and run the fastboot command that unlocks the pixel 2. If the same command could be injected into the pixels fastboot binary running on the phone you might trick it into unlocking just like the pixel 2.
Click to expand...
Click to collapse
Assembly language debugger? Hmm. If this is true, wooden somebody had saved file and upload it to XDA? I'm getting curious now....
ShadowWeasel said:
Assembly language debugger? Hmm. If this is true, wooden somebody had saved file and upload it to XDA? I'm getting curious now....
Click to expand...
Click to collapse
Not many hackers are versed in assembly language. I've used it a few times over the years to patch an executable but, I had specific step by step instructions on how to do it. There are a lot of people around that know what they are doing but, I doubt we find them hanging around an android forum.
Sent from my Pixel using Tapatalk
baknblack said:
Not many hackers are versed in assembly language. I've used it a few times over the years to patch an executable but, I had specific step by step instructions on how to do it. There are a lot of people around that know what they are doing but, I doubt we find them hanging around an android forum.
Click to expand...
Click to collapse
I may check the deep web for some answers
Knowing or not knowing assembly won't help, you cannot modify the bootloader in any way when it's locked basically making this a fruitless effort.
Nick80835 said:
Knowing or not knowing assembly won't help, you cannot modify the bootloader in any way when it's locked basically making this a fruitless effort.
Click to expand...
Click to collapse
Don't need to modify the bootloader. Would just need to jump into the fastboot code in the same exact place with the same exact instruction that caused the rogue routine to run on the pixel 2. I would think it would be reasonable to assume the same coding bug that exists on the 2 might also be present in the other pixels. But, we'll never know unless someone with the knowledge were to try it.
Sent from my Pixel using Tapatalk
Tulsadiver said:
You don't have to have an unlocked bootloader in order to root. I've had plenty of Samsung's with root and no unlocked bootloader.
---------- Post added at 06:19 PM ---------- Previous post was at 06:04 PM ----------
In general an unlocked bootloader is not a prerequisite for root. I've had several phones with a locked bootloader but with root.
Click to expand...
Click to collapse
For the Pixel yes you do. You can't root without an unlocked bootloader
For what it's worth, it is relatively common any more, from what I hear, that an unlocked bootloader is required to root. The VS985 (Verizon) LG G3 was an exception in that the bootloader had an exploit that could be taken advantage of to effectively allow everything that an unlocked bootloader does. The HTC 10 is an exception in that you can just S-OFF and never unlock the bootloader and it's just as good if not better. There are always exceptions - when there are other avenues someone is clever enough to find, but as a rule going the other direction, if you can unlock the bootloader of a device, then you can usually easily root the device. As someone else said, on the Pixel, an unlocked bootloader has always been required to root.
I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
wheelbarrel said:
I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
Click to expand...
Click to collapse
If it's a Verizon one probably not. If it's a Google store pixel, Yes just unlock it again. It will wipe again.
Why did you relock it in the first place
KittyRgnarok said:
Why did you relock it in the first place
Click to expand...
Click to collapse
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
KittyRgnarok said:
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
Click to expand...
Click to collapse
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
b00ster23 said:
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
Click to expand...
Click to collapse
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
KittyRgnarok said:
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
Click to expand...
Click to collapse
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
b00ster23 said:
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
Click to expand...
Click to collapse
Tru Tru
wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Poebat said:
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Click to expand...
Click to collapse
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
Ah. I figured that might be the case.
b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
I mean almost every custom kernel for pixel og has proper safety net support
I appreciate all your input everyone! Unfortunately I am going to have to wait until it's time to buy a Pixel 2 lol, which is getting close
This is proof you should read EVERYTHING first lol