Related
Hey folks. It's me again :victory: So I've got another super easy video guide on how to root your shiny new Samsung Galaxy S4 I337 or I337m.
This guide is using djrbliss's Motochopper tool. This tool has made it easier than ever to root a device! So BIG thanks goes out to him!
Links to everything can be found in the video description.
Enjoy
Here is a couple of more. I figure its better to keep them all in one place so people can decide which guide they want to use.
http://forum.xda-developers.com/showthread.php?t=2257039
http://forum.xda-developers.com/showthread.php?t=2257058
I think there might be a couple more out there but this should help people to answer any possible question about rooting that they could ever have.
If you have the AT&T OTA (MF3) for the SGH-I337 S4, the method in the OP does not work. Here is a method for rooting MF3:
http://forum.xda-developers.com/showthread.php?t=2387577
For Canadian MG1 Firmware, try CF Auto-Root download for the SGH-I337M:
http://forum.xda-developers.com/showthread.php?t=2293800
Just sold my Rogers S2 LTE because I upgraded to the S4. My quick question, if I ROOT and retain the original Samsung Recovery will I be able to still get and do official firmware upgrades? This is the only thing stopping me from going forward with rooting.
You can still get updates, but you will loose your root access with each update.
thanks: im now rooted and sim unlocked for free!
Slade8525 said:
thanks: im now rooted and sim unlocked for free!
Click to expand...
Click to collapse
Hey, how did you sim unlock it for free, do you mind sharing?
yeah sure!
similar method worked for my GS III; havent tested the GS IV with different sim just yet but GF's old GS III is working just fine for her sister in Canada (Bell i think). GF found it actually, and did it to hers 1st. ill know if it works when we leave for work in Montreal next week or if i bum a t-mobile cell from a friend.
http://forum.xda-developers.com/showthread.php?t=2282683
Stoneyguy said:
You can still get updates, but you will loose your root access with each update.
Click to expand...
Click to collapse
WRONG, I am unable to update my device, it says that my phone has been modified, and yes, I have rooted it with this video.
Whenever I try this method, when it goes to push the exploit, it says error multiple devices or something. when I only have the S4 plugged in. Followed step by step.
Dragosmp said:
WRONG, I am unable to update my device, it says that my phone has been modified, and yes, I have rooted it with this video.
Click to expand...
Click to collapse
My phone is rooted and still shows official in phone status. There is a post on how to regain that status while still maintaining your root.
Stoneyguy said:
My phone is rooted and still shows official in phone status. There is a post on how to regain that status while still maintaining your root.
Click to expand...
Click to collapse
Could you post a link to where it shows how to regain the status will maintaining the root?
rsarwar said:
Could you post a link to where it shows how to regain the status will maintaining the root?
Click to expand...
Click to collapse
The link has already been posted on the first page.
thanks worked great just rooted min in 5 min
Safe to root?
Excuse my ignorance, but on another thread it was suggested that in the absence of recovery and a backup image rooting might be premature. Is the general consensus now that it is safe to root? There seems to be some backup images around thought I don't know if they have been tested, and I haven't heard about recovery.
sblevine
Newbie here... couple of questions
I have the same concern as the member above... is it already possible to restore the phone if something goes bad? Is there instructions anywhere around this forum? where?
Also, once you root the phone you can proceed to download a ROM and install it... when a new ROM version is available and I download and install it, do I lose the root?
What is the best (if more than one is already available) for the ATT S4?
Thank you all and sorry for the "newbieness"....
Cheers:good:
speed2001 said:
I have the same concern as the member above... is it already possible to restore the phone if something goes bad? Is there instructions anywhere around this forum? where?
Also, once you root the phone you can proceed to download a ROM and install it... when a new ROM version is available and I download and install it, do I lose the root?
What is the best (if more than one is already available) for the ATT S4?
Thank you all and sorry for the "newbieness"....
Cheers:good:
Click to expand...
Click to collapse
No, rooting gives you certain superuser privileges. You can use Titanium Backup to freeze and restore bloatware, AdBlock to block advertisements, etc. Some phone tracking software and remote desktop control software requires root as well.
You cannot modify the basic operating system (ROM) until the bootloader is unlocked. You can overwrite the files, but that will brick your device since the bootloader checks signatures.
There is a bootloader exploit for the ATT S4 that will be released within the next week. The developer was waiting until the Verizon version of the S4 was available so more people would be able to use the exploit before it was patched.
Do not accept an OTA update for your device as that is how they will patch the bootloader exploit.
1. Root your device.
2. Carrier unlock your device.
3. Install custom ROM when bootloader is exploited later this week.
Relys said:
No, rooting gives you certain superuser privileges. You can use Titanium Backup to freeze and restore bloatware, AdBlock to block advertisements, etc. Some phone tracking software and remote desktop control software requires root as well.
You cannot modify the basic operating system (ROM) until the bootloader is unlocked. You can overwrite the files, but that will brick your device since the bootloader checks signatures.
There is a bootloader exploit for the ATT S4 that will be released within the next week. The developer was waiting until the Verizon version of the S4 was available so more people would be able to use the exploit before it was patched.
Do not accept an OTA update for your device as that is how they will patch the bootloader exploit.
1. Root your device.
2. Carrier unlock your device.
3. Install custom ROM when bootloader is exploited later this week.
Click to expand...
Click to collapse
Cool, thanks for the reply. I was under the impression that the bootloader was already exploited. Pure BS those protections that always end up broken like the IOS ones. What I would like is to have the S4 as factory released and load a good ROM without any problems and no bloatware. If not for the warranty I would buy an unlocked phone elsewhere.
Well, let's wait for the exploit next week. I don't want to brick my phone and not able to restore it. I will keep checking back.
Cheers and thanks again
Speed
Relys said:
No, rooting gives you certain superuser privileges. You can use Titanium Backup to freeze and restore bloatware, AdBlock to block advertisements, etc. Some phone tracking software and remote desktop control software requires root as well.
You cannot modify the basic operating system (ROM) until the bootloader is unlocked. You can overwrite the files, but that will brick your device since the bootloader checks signatures.
There is a bootloader exploit for the ATT S4 that will be released within the next week. The developer was waiting until the Verizon version of the S4 was available so more people would be able to use the exploit before it was patched.
Do not accept an OTA update for your device as that is how they will patch the bootloader exploit.
1. Root your device.
2. Carrier unlock your device.
3. Install custom ROM when bootloader is exploited later this week.
Click to expand...
Click to collapse
Regarding the bold above, I am honestly not that interested in the Custom ROMS right now, only rooting and with this method it does not install any custom recovery, right? As well, if I root via this method will I be able to still do the OTA updates since Samsung recovery is untouched? I know and understand that I will likely loose root, but I can always re-root, right?
I am itching to root and this is the only thing stopping me as there seems to be much confusion about this.
BTW I am on Rogers (Canada) i337M if it makes a difference
rsarwar said:
Regarding the bold above, I am honestly not that interested in the Custom ROMS right now, only rooting and with this method it does not install any custom recovery, right? As well, if I root via this method will I be able to still do the OTA updates since Samsung recovery is untouched? I know and understand that I will likely loose root, but I can always re-root, right?
I am itching to root and this is the only thing stopping me as there seems to be much confusion about this.
BTW I am on Rogers (Canada) i337M if it makes a difference
Click to expand...
Click to collapse
I've been a bit confused as well despite reading hundreds of posts and watching referenced videos (I've also been hesitant to ask questions given the culture of this board). Here is what I hope is accurate, please correct where I am wrong:
We can root I337 now.
Doing a simple root now is reversible, ie, can be un-rooted.
The bootloader unlock is needed primarily for custom roms.
If one does not desire a custom rom, there is no reason to wait to root.
And, a few questions:
Does rooting wipe out apps, settings, and/or data?
Will an AT&T android system update remove the root?
If so, can we just root again?
Thank you for clarifications. I'm sure there are many that are not posting with some of these questions. I will be glad to put together a noobie's guide if I can get a handle on all of this. It is all out there somewhere, but very fragmented, and often one post is contradicted by another.
zekeblue said:
I've been a bit confused as well despite reading hundreds of posts and watching referenced videos (I've also been hesitant to ask questions given the culture of this board). Here is what I hope is accurate, please correct where I am wrong:
We can root I337 now.
Doing a simple root now is reversible, ie, can be un-rooted.
The bootloader unlock is needed primarily for custom roms.
If one does not desire a custom rom, there is no reason to wait to root.
And, a few questions:
Does rooting wipe out apps, settings, and/or data?
Will an AT&T android system update remove the root?
If so, can we just root again?
Thank you for clarifications. I'm sure there are many that are not posting with some of these questions. I will be glad to put together a noobie's guide if I can get a handle on all of this. It is all out there somewhere, but very fragmented, and often one post is contradicted by another.
Click to expand...
Click to collapse
Your assumptions are correct:
1. Yep.
2. Yes, you can delete busybox and su in your system directory to get your phone switch your phone from "Custom" to "Official" status. If you install SuperSu and remove Superuser you can have root while keeping "Official" status.
3. Correct.
4. If you **** up while messing around with root you can recover to stock ROM via Odin or Kies. There is no reason to wait for root.
To answer your questions.
1. No, nothing changes. You just enable superuser privileges.
2. Typically yes. Don't accept OTA's until your know they're safe.
3. It depends if they patch the exploit or not.
Good afternoon people of XDA,
Today is the dawn of a new day. A day where we begin the road to unlocking the bootloader to something that many believe is unlockable. Me and a few other users are starting a bounty to bring the incentive to life for all active developers. You can find my previous thread here. Now, when I say progress has been made, I mean that we have gotten into fastboot, we have donation incentives and we already have root so our tools are there we just have to find the exploit. Every day people are finding new exploits furthering our cause into reaching our goal. Now to the developers who want to pursue this, I've very much so tried to get active commands in fastboot but basically its just a dead fastboot for right now. The board on this phone and technologies behind it are so similar to its predecessors that somethings got to give. If you are interested in this cause, i.e. donating or deving on it, please contact me here, or email me at [email protected]
This is in our grasps friends. Spread the word, grab your fellow developers and lets get this thing to be a free wad of cash for whoever can bust it. Lets do this.
Attached is the spreadsheet for the current donations.
this kind of things never work...i mean, you make a donation and the people or the persons behind the scenes when getting high values like 400-500$ then buy a new phone and move on letting the desired phone to get development in the trash!!
Noooo, people should see, if a year old phone never came to life in development in the first 6-8 months then the development for it is dead and if you like to custumize the phone and flash things you need to move to a more flashable-friend device!
I have to agree with this. The Tmobile version has unlocked bootloader yet barely no development. What would make me that unlocking VS990 bootloader would all of a sudden spur development.
beavis5706 said:
I have to agree with this. The Tmobile version has unlocked bootloader yet barely no development. What would make me that unlocking VS990 bootloader would all of a sudden spur development.
Click to expand...
Click to collapse
I personally (and I think many other users) don't really need cooked roms. With gravity box, xposed and some other apps, I can "cook" my own rom (and believe me, it won't be that hard). All we need is a method for rooting. Using an android without rooting is even worse than an iphone without jailbreaking since iphones are undoubtedly smoother
presariohg said:
I personally (and I think many other users) don't really need cooked roms. With gravity box, xposed and some other apps, I can "cook" my own rom (and believe me, it won't be that hard). All we need is a method for rooting. Using an android without rooting is even worse than an iphone without jailbreaking since iphones are undoubtedly smoother
Click to expand...
Click to collapse
Indeed, a rooting method for version above MM is the most importing thing for us rather than flashing custom rom. However, system-less root is need to root MM or above and this is required modifying boot.img, therefore, bootloader unlocking is need. Unless, we have found a way to sign the modified boot.img to deceive the offical bootloader.
ivangundampc said:
Indeed, a rooting method for version above MM is the most importing thing for us rather than flashing custom rom. However, system-less root is need to root MM or above and this is required modifying boot.img, therefore, bootloader unlocking is need. Unless, we have found a way to sign the modified boot.img to deceive the offical bootloader.
Click to expand...
Click to collapse
What did you mean by "unless"? Have you found an evidence that MM bootloader is unlockable or not?..
presariohg said:
What did you mean by "unless"? Have you found an evidence that MM bootloader is unlockable or not?..
Click to expand...
Click to collapse
I mean even if the bootloader is not unlockable, somethings can be done to let us perform the same things just like bootloader is unlocked.
For example, some dev in G2 and G3 have released a tool called "Bump!" before that can sign any third party image and let it able to be run on offical locked LG bootloader.
source: http://forum.xda-developers.com/lg-g3/orig-development/bump-sign-unlock-boot-images-lg-phones-t2935275
But of course, since LG have fixed the bug, we can no longer do the same tricks now.
In China, there is name ???he has lg tool, this tool can unpack repack kdz tot, add root in tot.
This is weibo id http://m.weibo.cn/u/1684239753
Need help
andy_zhang said:
In China, there is name ???he has lg tool, this tool can unpack repack kdz tot, add root in tot.
This is weibo id
Click to expand...
Click to collapse
Hey, So I've been working to be able to get root, so far I have added root to the system.img and that's all done, I need this tool to be able to repack. Can anyone, or you, contact him and get this tool? This would be so helpful for me to get root and release it!!!!
abine45 said:
Hey, So I've been working to be able to get root, so far I have added root to the system.img and that's all done, I need this tool to be able to repack. Can anyone, or you, contact him and get this tool? This would be so helpful for me to get root and release it!!!!
Click to expand...
Click to collapse
What version of Android you are going to add root? I wonder that you cannot simply add root in /system after Android 6.0.
ivangundampc said:
What version of Android you are going to add root? I wonder that you cannot simply add root in /system after Android 6.0.
Click to expand...
Click to collapse
I'm trying different things but still i need to figure out how to repack a tot to find out what's going to work!! Does anybody know how to get that application?
abine45 said:
I'm trying different things but still i need to figure out how to repack a tot to find out what's going to work!! Does anybody know how to get that application?
Click to expand...
Click to collapse
For MM, unless you've found a way to get the SELinux context needed, repacking the system image will not work.
anyone having any luck with rooting MM?
I think at this point what we really need is a small set of testers who have a good insurance policy on their phones and are willing to risk bricking their phones. We've got the outline of a method which looks viable, but the details haven't been worked out and is hence likely to produce a few bricks before we get it working.
Sorry for dropping of the face of the planet for the past two months. In testing with my device it ended up being FUBAR after wiping my aboot completely and with that the phone would not boot to anything but a black screen. I sent it into LG and after some time they finally just replaced my motherboard. But the absolute sad part is that they have me upgraded to 6.0 which absolutely is crushing my world. SO until further notice I will not be testing the unlocking of the bootloader anymore but I will make efforts here in a few weeks to start work on rooting the device. @alvislee[email protected]
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
newbienic said:
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
Click to expand...
Click to collapse
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Awesome! Thanks for the info... Really glad to know I can convert if need be. Thanks again!
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
newbienic said:
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
Click to expand...
Click to collapse
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
ITGuy11 said:
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
Click to expand...
Click to collapse
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
danaff37 said:
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
danaff37 said:
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hypathetically, if I didn't want root or anything custom at all, do you think that relocking the bootloader could cause an issue while using the Stock Google image on a Verizon Pixel? I wish I had more knowledge on this, but I'm pretty in the dark on this stuff as of late... Thanks for your help!
Should be fine if all stock I think, just know that you may not be able to unlock later.
Sent from my Pixel using Tapatalk
newbienic said:
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
Click to expand...
Click to collapse
Contrary to what people are saying. You CAN relock your bootloader and then unlock it again later. However, keep in mind that at some point there will likely be an update that blocks the use of dePixel8 and you will no longer be able to unlock the bootloader unless someone writes another exploit.
I would like to find a way to permanently unlock VZW Pixels but until I get one from the Google Store to compare with my Verizon one I don't think I will make much progress.
Relocking your bootloader is as simple as running the "fastboot oem lock" command from the terminal window.
Lastly. If you want to relock the bootloader, make sure your phone is 100% stock image or you risk bricking the phone
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
b316kane said:
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
Click to expand...
Click to collapse
This is exactly what I did, and I am curious as well... We'll see next month I guess, but I'm guessing it will take the OTA just fine. My wife has a Pixel from the Google store, and mine is from Verizon. I've compared everything (including booloaders) since flashing the Google store Pixel image, and every informational detail is identical. Not sure if there is some other place hidden to me that might indicate a difference, but I'm thinking that Verizon's Pixel is only different in its official software image... And, that may be it. Please don't take my word for it, I'm no developer, and know very little about any of this, but in my comparisons, they are identical now since flashing Googles official (Non Verizon, Non European) image.
Sidenote, I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking. I think Verizon used Googles "Allow OEM Unlocking" software toggle in developer options as the only method to actually keep people from unlocking the bootloader (again speculative), and now that I'm on Googles image, that software "block" should no longer be present, so I should in theory, be free to lock/unlock the same as Pixels purchased from the Google store... Again, I've got no proof, or actual skill to back this up, but it's a theory I have, and if I end up locking my BL again, I'll post what I find...
newbienic said:
I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking.
Click to expand...
Click to collapse
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
alluringreality said:
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
newbienic said:
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
Click to expand...
Click to collapse
I forget where, but I saw written or implied that the "checking for updates" screen about third of way through initial setup of first boot uses WiFi AND sim carrier data to install Verizon custom restrictions and settings that among other effects make depixel8 required.
Even on "non Verizon phones" (which you are saying use the same build images byte to byte?)... You have to either use a SIM card or wifi and google account to allow the developer options to enable OEM unlock.
My theory: In other words, if you don't allow via SIM and a network wifi or data connect, for Verizon to mark your phone, or another carrier, then the phone can not be unlocked. So carrier models may indeed be differentiated from current factory images AFTER boot and setup.
There is a post in Q&A of someone trying to unlock bootloader without loading into the device, not having luck. This is why oem unlock toggle is so important and why people are bricking from locked bootloaders that won't unlock (so no wipe and factory images cannot be flashed.)
Another thing to consider: SIM network lock will not be flashed over.
Sent from my sailfish using XDA Labs
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
I have a A125U that I can't unlock the bootloader of. There's no OEM unlock option in the Developer Options, there's no way to unistall system updates to try the date/time thing to get OEM unlock, nothing else I've tried has worked at all. I even tried flashing A125F firmware to no avail, of course. I was thinking, the BL file is the bootloader, is there a way to flash a bootloader that's already unlocked? Or is that not how this works?
If not, does anyone know how to get OEM unlock to show on the A125U? It's been driving me insane.
Not possible unfortunately
no
LOOOOOOOL
This is the biggest lie I've ever seen in my life!!! of course it,s possible ddd. Everything is possible especially this. Trick to your issue, is just that you have to corssflash to the Canadian firmware on your A125U which is the US model. But that doesn't matter, that's nothing because those 2 phones run on the same hardware so the firmware operates with both. Even the SW_REV value doesn't do anything in that situation. You can take the U models and flash it to W(Canada) but that's useless because then you're locked out of natively unlocking the PBL. Just grab the Canadian firmware and crossflash it via heimdall or patched Odin which is the same thing. Erase old NAND.
Also don't think that stuff like this isn't possible, of course it is. You just have to try harder and harder until you get the result you're stasifed with. There is community with a bunch of us enthusiasts (discord server link is on my profile). Don't be scarred to ask here on xda and there in the server. Also you can dm me for help, I'll help you, don't worry.
Hope I helped, be sure to ask if misunderstood or need more help. Also check out some stuff i wrote on this forum. It's very helpful and interesting.
Stay safe,
Krypton