Related
Hello everyone!
About a week ago, I went and bought the S3, my first Android phone. The sales guy told me that the phone is sim free but a Samsung's firmware update caused a bug, and that the phone needed to be sim unlocked because of Samsung's error. Needless to say I knew nothing about the phone (or Android).
After a few days of learning about it, I ended up seeing there is a Voodoo app in the file manager, CWM and SuperSU apps in the app drawer.
I came here to check what that was all about.
After reading extensively I now know that the phone is rooted and was sim unlocked with Voodoo app.
I red all about Voodoo and was impressed that it works with the fix, yet another user said this will cause problems in the future, and I already see some users complaining about their phones not working.
My question is, was the sales person lied to me about the Samsung firmware bug? And also, is the Voodoo app + fix is legit, and I can rest my worries aside?
I wouldn't like to have problems and having to wait for some (wonderful and admirable) dev to fix it, every time there is a firmware update.
Thanks in advance, excuse my noobishness.
If its unlocked.....ITS UNLOCKED
reboot, if its still unlocked then you are good. as far as the problems........i dont know of some sort of samsung bug that would f up a phone.
what are you really asking? will your phone all of sudden brick on you and become useless? i dont think so
In fact, there is no Samsung "bug": Samsung has just improve is Lock system which now break voodoo unlock (on purpose or not...)
In theory, it should only relock phones that had been unlock with voodoo app but here is the tricky thing: some shop sell "fake" unlocked phones!
-they took carrier locked phone
-they flash a stock rom
-they change the EFS file in the same way voodoo app would have done
-they sell it as unlocked
the old lock system do not break this and buyers will probably never see the trick but the new lock system just relock the phone and left people with a locked phone even if they think they have bought an unlocked phone
Just look at this post which is an answer to someone who had a relock on an "unlocked" phone with XXBLG8 firmware
Mopral said:
the old lock system do not break this and buyers will probably never see the trick but the new lock system just relock the phone and left people with a locked phone even if they think they have bought an unlocked phone
Click to expand...
Click to collapse
So in fact, from now on, every time I flash an updated rom, I need to pray that samsung didn't (intentionally or not) break the voodoo unlock? Sort of like the Apple's cat and mouse game after the unlocks? Cause I'm not going through that again.
Here is a patch for preventing the sim to be locked after a update http://forum.xda-developers.com/showthread.php?t=1802951, need root and flash with CWM.
gee2012 said:
Here is a patch for preventing the sim to be locked after a update http://forum.xda-developers.com/showthread.php?t=1802951, need root and flash with CWM.
Click to expand...
Click to collapse
Thank you for the reply.
It seems as though the fix is allready applied, the thing that bother me is that
I will need to wait for a fix every time there is an update.
It's just that i'm afraid after owning a locked iphone, that was a nightmare.
Let's say that it is much better and more comfterbale to have an unlocked phone, am i right?
shermenz said:
Thank you for the reply.
It seems as though the fix is allready applied, the thing that bother me is that
I will need to wait for a fix every time there is an update.
It's just that i'm afraid after owning a locked iphone, that was a nightmare.
Let's say that it is much better and more comfterbale to have an unlocked phone, am i right?
Click to expand...
Click to collapse
Go back to the shop and request a original simlock free phone then. if it bothers you that much!
shermenz said:
Hello everyone!
About a week ago, I went and bought the S3, my first Android phone. The sales guy told me that the phone is sim free but a Samsung's firmware update caused a bug, and that the phone needed to be sim unlocked because of Samsung's error. Needless to say I knew nothing about the phone (or Android).
After a few days of learning about it, I ended up seeing there is a Voodoo app in the file manager, CWM and SuperSU apps in the app drawer.
You have bought a second hand phone . Its been used rooted voids warranty and apps installed return it .
jje
Click to expand...
Click to collapse
gee2012 said:
Go back to the shop and request a original simlock free phone then. if it bothers you that much!
Click to expand...
Click to collapse
Well since I'm new to Android I don't know if it should bother me, with Apple it was horrible, my question essentially is should it bother me?
Does sim locked phones Known to cause problems down the road?
Thank you for spendig the time!
shermenz said:
Well since I'm new to Android I don't know if it should bother me, with Apple it was horrible, my question essentially is should it bother me?
Does sim locked phones Known to cause problems down the road?
Thank you for spendig the time!
Click to expand...
Click to collapse
As you are rooted, it is better not to update through Kies or OTA. Kies updates will break root and thus voodoo sim unlock and OTA`s will not be installed as you have a custom recovery. Download future new roms from www.sammobile.com/firmware and flash it with (Mobile) Odin (Pro). See my signature for the procedure. With Mobile Odin Pro you keep root and with pc Odin you will loose root. If in the future you have to send it in for repair warranty can be denied because you are rooted.
Stock Pixel/Pixel XL Kernel + SafetyNet Patch
Current version: android-9.0.0_r0.111
Suitable for build(s): August 2019
Suitable for devices(s): Pixel XL (marlin) | Pixel (sailfish)
I compiled the stock kernel for the Pixel/Pixel XL and applied the SafetyNet patch by sultanxda. The kernel name says marlin, but this also works on sailfish. Google just created one kernel that works on both sailfish (Pixel) and marlin (Pixel XL) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay and Netflix.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is only for the builds listed above!!!! This will not work on any prior build.
- All stock features will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the stock kernel, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Be prepared with backups or the factory image from Google in case you do something wrong
- Extract kernel from zip file
- Test with command: fastboot boot <filename>
- Flash with command: fastboot flash kernel <filename>
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
The current version will always be attached to this post. Older versions can be found HERE.
(shamelessly copied from Sakete's kernel for the Pixel/Pixel XL, which is no longer being maintained. Thanks for the inspiration, Sakete!)
Wow. I literally just compiled the patched kernel myself just now. What a ninja! While I'll be running my own, thanks for posting this so I didn't have to
For those who already downloaded the kernel, I checked and saw a new mr2.1 update so I've attached an updated kernel.
iissmart said:
For those who already downloaded the kernel, I checked and saw a new mr2.1 update so I've attached an updated kernel.
Click to expand...
Click to collapse
Mine is based on that but mr2 and mr2.1 have the same commit so I'm pretty sure it's the same kernel.
Cheers
I'm running a pixel on the nof27b build I don't really want to flash a new kernel would it be possible for you to make the patch a flashable zip
Cardflip said:
Mine is based on that but mr2 and mr2.1 have the same commit so I'm pretty sure it's the same kernel.
Cheers
Click to expand...
Click to collapse
Good catch, I didn't look that closely before recompiling but they are indeed the same. Oh well! Maybe I'll start going off of tag names instead of branches...
ipeedalil said:
I'm running a pixel on the nof27b build I don't really want to flash a new kernel would it be possible for you to make the patch a flashable zip
Click to expand...
Click to collapse
Curious - what difference is there between flashing a kernel using fastboot and using a flashable zip? Isn't the end result the same?
iissmart said:
Curious - what difference is there between flashing a kernel using fastboot and using a flashable zip? Isn't the end result the same?
Click to expand...
Click to collapse
I think he's asking for the patch itself to be a flashable zip so he can patch the boot image while it's already compiled and on the phone. Which AFAIK is impossible
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I was thinking the same thing, That K is for the Verizon model. good to know.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I'll look into it tomorrow!
Thank you.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I believe the kernel would still work.
It looks like the same kernel is used among NHG47K, N2G47J, and N2G47E, so my patched one should work for all of them. I'll update the post.
I'm just curious... So assuming you have the Google version and the oem unlock switch is fuctional and turned on, if you are not intending to root the device why would you unlock the bootloader? I mean you can always unlock it if you want or need to root, right?
bobby janow said:
I'm just curious... So assuming you have the Google version and the oem unlock switch is fuctional and turned on, if you are not intending to root the device why would you unlock the bootloader? I mean you can always unlock it if you want or need to root, right?
Click to expand...
Click to collapse
In the past I would always root or install a custom ROM on my phone. I would like to with the Pixel, but I want to keep Android Pay since I use it almost daily and I haven't been satisfied with the root solutions I've seen for the Pixel so far. It seems like Google is doing a good job of making it difficult to root, given the three or four different ways to root a Pixel that I've seen. Also, with the advent of monthly security patches I would imagine it is a growing headache to unroot, flash the update, then re-root each month. Google has also done a great job with the stock experience on the Pixel that the reasons I'd root are fairly minor.
It's also just been a habit of mine that the first thing I do with a phone is to unlock the bootloader. I don't like the idea of artificially restricting full access to a device, whether it's software or hardware. Plus I don't have to deal with the silly anti-theft checks that people encounter when they wipe the phone and sell it legitimately (like with Swappa or eBay). There was also a time when Nexus phones would bootloop after receiving an OTA, and if you weren't already unlocked before the OTA hit you'd be stuck with a bricked phone.
iissmart said:
In the past I would always root or install a custom ROM on my phone. I would like to with the Pixel, but I want to keep Android Pay since I use it almost daily and I haven't been satisfied with the root solutions I've seen for the Pixel so far. It seems like Google is doing a good job of making it difficult to root, given the three or four different ways to root a Pixel that I've seen. Also, with the advent of monthly security patches I would imagine it is a growing headache to unroot, flash the update, then re-root each month. Google has also done a great job with the stock experience on the Pixel that the reasons I'd root are fairly minor.
It's also just been a habit of mine that the first thing I do with a phone is to unlock the bootloader. I don't like the idea of artificially restricting full access to a device, whether it's software or hardware. Plus I don't have to deal with the silly anti-theft checks that people encounter when they wipe the phone and sell it legitimately (like with Swappa or eBay). There was also a time when Nexus phones would bootloop after receiving an OTA, and if you weren't already unlocked before the OTA hit you'd be stuck with a bricked phone.
Click to expand...
Click to collapse
Ok, fair enough. As I said I was just curious as to the reasoning. But what do you mean by anti-theft checks? I've never sold a phone so I don't really run into anything like that. But if you ever did need to sell it and you could unlock it at a moment notice wouldn't that suffice? I have a Verizon model locked bl so this is all rather moot to my situation, but I do have a 5x that I can unlock if I had to. I like the idea of being able to toggle the oem switch even though I would still remain locked. Something about being able to flash a factory image that I like. Thanks for your reasoning. Not that I agree or disagree with you entirely hehe. Personally, I just like the security of not being able to access my data if it's ever lost or stolen, but I suppose a concerted effort would get in.
bobby janow said:
Ok, fair enough. As I said I was just curious as to the reasoning. But what do you mean by anti-theft checks? I've never sold a phone so I don't really run into anything like that. But if you ever did need to sell it and you could unlock it at a moment notice wouldn't that suffice? I have a Verizon model locked bl so this is all rather moot to my situation, but I do have a 5x that I can unlock if I had to. I like the idea of being able to toggle the oem switch even though I would still remain locked. Something about being able to flash a factory image that I like. Thanks for your reasoning. Not that I agree or disagree with you entirely hehe. Personally, I just like the security of not being able to access my data if it's ever lost or stolen, but I suppose a concerted effort would get in.
Click to expand...
Click to collapse
If a locked phone is wiped/factory reset then only the Google account that was previously on the phone is allowed to be added back to the device. Tons of people were selling Nexus phones when this change rolled out, and the people that bought the phones were unable to add their accounts even after factory resetting. By unlocking the bootloader it disables this restriction. Yeah, I could do it at the time of selling the phone but there's always a chance I'd forget if I got out of the habit of unlocking the bootloader.
I thought about it a lot - and I've never lost a phone before so I'm OK with having my phone accessible in that regard. If I lose my phone I'll have bigger issues (like 2FA locking me out of my accounts) anyway.
I'm on Verizon, but I intentionally bought the phone from Google just to be able to unlock the bootloader .
iissmart said:
If a locked phone is wiped/factory reset then only the Google account that was previously on the phone is allowed to be added back to the device. Tons of people were selling Nexus phones when this change rolled out, and the people that bought the phones were unable to add their accounts even after factory resetting. By unlocking the bootloader it disables this restriction. Yeah, I could do it at the time of selling the phone but there's always a chance I'd forget if I got out of the habit of unlocking the bootloader.
I thought about it a lot - and I've never lost a phone before so I'm OK with having my phone accessible in that regard. If I lose my phone I'll have bigger issues (like 2FA locking me out of my accounts) anyway.
I'm on Verizon, but I intentionally bought the phone from Google just to be able to unlock the bootloader .
Click to expand...
Click to collapse
I've seen the term 2FA bandied about. I presume that's what you're talking about regarding the lockout. So to clarify, if you don't have an unlocked bootloader you can't sell the device? That seems weird. How do you get your account off? If I gave the phone to my wife she can't add her account?
I've never lost a device either although I have smashed one of them disastrously. But now I have a lot more stuff on the device including some personal pics and videos, password files, banking app and of course AP. I actually think my reasoning was more of like there is so much hacking and theft going on that rather than take a chance let me see what it's like being locked like normal people. It's hasn't been bad at all so far as I'm sure you know since you're not really modded either. I get the OTA on another slot and while it's updating I can use the device and a simple reboot updates it. But the bigger reason is that I got a Verizon model (Pixel 32gb) for $240 and not the $650 the Google one would have cost. I'm not sorry although I will revisit that once the Pixel 2 is released. Black Friday is your friend. I would even have bought the Google Pixel for $350 if they had a deal but they didn't. With a fully functioning 5X I just couldn't justify the full price.
Hmm I extracted the file and used fastboot flash kernel kernel_marlin-3.18-nougat-mr2.img and it gives me an error "error: cannot load 'kernel_marlin-3.18-nougat-mr2.img"
coldconfession13 said:
Hmm I extracted the file and used fastboot flash kernel kernel_marlin-3.18-nougat-mr2.img and it gives me an error "error: cannot load 'kernel_marlin-3.18-nougat-mr2.img"
Click to expand...
Click to collapse
After extracting the file I just renamed it to sailfish-image and used that in the command fastboot flash kernel sailfish-image. Flashed fine.
Sent from my Pixel using XDA-Developers Legacy app
Will it work?
PuffDaddy_d said:
Will it work?
Click to expand...
Click to collapse
Most probably. The dev has one on order.
May not on day one, but I'd expect it very soon.
The question is how long will Magisk continue to work. According to an XDA:
Full documentation on the Titan Security Module is not yet available, but a few Google engineers have posted Tweets that give us some information. First, in response to a tweet by Dees_Troy, lead developer of TWRP, Google’s tech lead for Android hardware-backed security subsystems, Shawn Willden, states that the new security module will not be used for runtime system analysis. This is important for Magisk users because hardware-backed runtime system analysis would make systemless-root much more difficult. However, Google already opened up an API for the Trusted Execution Environment (TEE), so runtime system analysis could still happen in the future (in other words, there could still be bad news for Magisk.)
Click to expand...
Click to collapse
mycall0 said:
The question is how long will Magisk continue to work. According to an XDA:
Click to expand...
Click to collapse
I wouldn't expect Google to purposely use it to kill Magisk... however I would expect them to make it difficult to be rooted and still pass the SafetyNet check.
I'm just surprised that nobody has confirmed that Magisk works on the P3 yet.
I mean, my phone was delivered this morning, so I assumed that tons of people all over the country were eagerly unlocking bootloaders and flashing away.
But still all quiet here on this thread?
From what I understand, that's because the factory image is only out since a few hours...
Someone on the Xl forum tried and the phone didnt boot so he had to factory flash the image. So looks like its the waiting game for root.
TopJohnWu will have his pixel Friday. He is excited about it, I bet we have root by Monday.
I tried to patch the boot.img through the magisk app and then flash that through fastboot. Flashed successfully but would not boot.
I have noticed that as soon as I unlocked the bootloader I fail safety net. Has that always been the case even without any system modifications?
jsauder2 said:
I tried to patch the boot.img through the magisk app and then flash that through fastboot. Flashed successfully but would not boot.
I have noticed that as soon as I unlocked the bootloader I fail safety net. Has that always been the case even without any system modifications?
Click to expand...
Click to collapse
From what I understand that is the case, unless you use Magisk to "cloak" and "fool" the apps into thinking it isn't.
Eudeferrer said:
From what I understand that is the case, unless you use Magisk to "cloak" and "fool" the apps into thinking it isn't.
Click to expand...
Click to collapse
Guess I've not tried using my phone unlocked without magisk in awhile...
jsauder2 said:
I have noticed that as soon as I unlocked the bootloader I fail safety net. Has that always been the case even without any system modifications?
Click to expand...
Click to collapse
No, my Nexus 5 running LineageOS has always passed with Magisk and unlocked bootloader (and Pay, etc. works).
CSX321 said:
No, my Nexus 5 running LineageOS has always passed with Magisk and unlocked bootloader (and Pay, etc. works).
Click to expand...
Click to collapse
Does it pass when it's unlocked but doesn't have magisk though? That's what I was wondering. This is really the first time I've had a phone unlocked without root (since it doesn't work yet), so I've never actually thought about that until now.
jsauder2 said:
Does it pass when it's unlocked but doesn't have magisk though? That's what I was wondering. This is really the first time I've had a phone unlocked without root (since it doesn't work yet), so I've never actually thought about that until now.
Click to expand...
Click to collapse
Ah, good question. I don't know. I've always had my phone unlocked and rooted.
jsauder2 said:
Does it pass when it's unlocked but doesn't have magisk though? That's what I was wondering. This is really the first time I've had a phone unlocked without root (since it doesn't work yet), so I've never actually thought about that until now.
Click to expand...
Click to collapse
I want to say that it was relatively recently (maybe in the last 2-2.5 years) where if you only unlocked the bootloader, it would fail SafetyNet. For a while, you had to flash a kernel on top of unlocking the bootloader to pass SafetyNet.
tysj said:
I want to say that it was relatively recently (maybe in the last 2-2.5 years) where if you only unlocked the bootloader, it would fail SafetyNet. For a while, you had to flash a kernel on top of unlocking the bootloader to pass SafetyNet.
Click to expand...
Click to collapse
My experience is if I unlock bootloader, I fail SafetyNet unless Magisk is installed. Sometimes after a reboot, I still fail until I load the Magisk app and have it check once. Then the phone is fine again.
As to the original question: I installed the newest beta of Magisk on my Pixel 3 XL, downloaded the factory boot.img from Google and patched it using the app. Flashing to my active boot slot caused fastboot to complain about no valid boot images. Flashing the original boot.img allowed the phone to start normally again.
imsaguy said:
My experience is if I unlock bootloader, I fail SafetyNet unless Magisk is installed. Sometimes after a reboot, I still fail until I load the Magisk app and have it check once. Then the phone is fine again.
As to the original question: I installed the newest beta of Magisk on my Pixel 3 XL, downloaded the factory boot.img from Google and patched it using the app. Flashing to my active boot slot caused fastboot to complain about no valid boot images. Flashing the original boot.img allowed the phone to start normally again.
Click to expand...
Click to collapse
confirmed same results on Pixel 3 (non XL)
jsauder2 said:
I tried to patch the boot.img through the magisk app and then flash that through fastboot. Flashed successfully but would not boot.
I have noticed that as soon as I unlocked the bootloader I fail safety net. Has that always been the case even without any system modifications?
Click to expand...
Click to collapse
Yeah that's always been the case with unlocked bootloader
He just rooted the 3XL according to his Twitter. Release this weekend maybe?... Dude wasted no time, absolute machine.
I've read that some devices (have just ordered a multi-language one from Aliexpress, yet to arrive) come with the bootloader already unlocked. How would I go about checking this?
Thanks
Never mind, apparently it obvious, if there's a little unlocked key sign at bootup, it's unlocked!
I ordered one on eBay a few weeks ago amd it came in today. Should I/we be concerned if our tablet comes unlocked with the Google play store already installed? From what I had read, we should need to request an unlock and go through some steps to get Google play working, no?
Dannyboy3210 said:
I ordered one on eBay a few weeks ago amd it came in today. Should I/we be concerned if our tablet comes unlocked with the Google play store already installed? From what I had read, we should need to request an unlock and go through some steps to get Google play working, no?
Click to expand...
Click to collapse
as far as i've read, some are being shipped with bootloader unlocked (and some even with mokee installed from aliexpress), it may be just to install EU or global rom for the masses. nothing definite tho.
are you planning to flash anyway? if so, then i shouldn't be a problem at all, there'll be no worries at all with a fresh rom install. if you are keeping the existing rom, wipe it, once up and running install malwarebytes and an anti virus just to give it a scan. then uninstall them again
reg66 said:
as far as i've read, some are being shipped with bootloader unlocked (and some even with mokee installed from aliexpress), it may be just to install EU or global rom for the masses. nothing definite tho.
are you planning to flash anyway? if so, then i shouldn't be a problem at all, there'll be no worries at all with a fresh rom install. if you are keeping the existing rom, wipe it, once up and running install malwarebytes and an anti virus just to give it a scan. then uninstall them again
Click to expand...
Click to collapse
Thanks. I backed it up (just in case), factory reset it and ran a scan with avast and malwarebytes with nothing found.
God, this thing is fast compared to my Samsung Tab E 9.6 that this beast is replacing! :good::good::good:
Cool, I've got an asus that's ancient, hope I'll be impressed with the speed when it arrives
reg66 said:
Never mind, apparently it obvious, if there's a little unlocked key sign at bootup, it's unlocked!
Click to expand...
Click to collapse
Where will the sign show up? Which part of the booting screen?
Found it, @ the bottom centre
So, I voided my warranty by unlocking my bootloader now I don't know what the hell to do next. I wanted to start with a simple ROM pref. one that was very similar to the stock that came this device and right now I'm putting a nice image of my face in my drywall- I'm thinking of calling it "frustrations of ruined expectations".
ANY-WAYS, I was wondering if anyone knows of some good or ok ROMs that would suffice, before I forget why the heck I wanted root in the first place?
Since TWRP hasn't created one that I've been considering unlocking my one action but all my crap is on that.
How about just using root with the stock Rom, with magisk and exposed offering plenty of tools and customizations that would come with a 3rd party rom.
TaZeR369 said:
How about just using root with the stock Rom, with magisk and exposed offering plenty of tools and customizations that would come with a 3rd party rom.
Click to expand...
Click to collapse
I thought I had to have an already rooted device to instal Magisk. Is there a guide for it?
RimWulf said:
I thought I had to have an already rooted device to instal Magisk. Is there a guide for it?
Click to expand...
Click to collapse
This is the guide for rooting.
note that you should avoid OTA updates while rooted on stock. lenovo are ****ing assholes.
read that part again
what happened to me was when the android 10 update came out on the moto g7 play (from android 9), it just completely bricked the phone. not even fail gracefully and go back to the previous slot, it just stopped at the bootloader screen. that's very annoying when you need the phone and you're just stuck there and you need to use the lenovo's stupid asshole tool which requires an account that is not the same account you used to root your device. infuriating!
dandu3 said:
note that you should avoid OTA updates while rooted on stock. lenovo are ****ing assholes.
read that part again
what happened to me was when the android 10 update came out on the moto g7 play (from android 9), it just completely bricked the phone. not even fail gracefully and go back to the previous slot, it just stopped at the bootloader screen. that's very annoying when you need the phone and you're just stuck there and you need to use the lenovo's stupid asshole tool which requires an account that is not the same account you used to root your device. infuriating!
Click to expand...
Click to collapse
Are you sure? Then again I was thinking of using RR if I can find the site.
I'm happy to say my phone is rooted (Motorola One action)
Sorry for the late message, thanks for the help.