Related
Hi,
I'm considering purchasing the android dev phone since I'm not on the t-mobile network and need the phone w/o a contract. I'm aware that the latest version of the dev phone allows you to install paid apps, but not locked apps.
My question is, is there any way to convert my dev phone to an (unlocked) t-mobile image so that it will support paid and locked apps?
Please excuse me in case my question hasn't been framed properly or if it has been asked before, I'm new to these forums and the whole G1 bit.
Thanks in advance.
I'm also curious about a similar question, which is precisely the opposite:
I have a Tmobile phone, running JF1.42. If I change my firmware to ADP1.1, is that going to cause me to not be able to view locked apps on the market?
If you purchase the Android Developer Phone, yes you can flash it to the T-Mobile firmware (search forums for downgrading to RC29 using DREAIMG.NBH and etc) and no, this will not affect your unlock. The unlock is at a separate level (research baseband, and cellphone unlocking).
If you change your T-Mobile G1 to the ADP1 image, yes, you will lose paid apps in the market. Google is blocking the ADP images from accessing the paid apps. (from what i've been told this is done through a user-agent check, and not device id, although i could be wrong).
Hope this helps you guys out
Only protected Apps are not accessible by Dev phones.
Not all paid Apps are protected, only few paid Apps are protected.
As you can see from my sign., I have a T-Mobile G1 phone with a mod Dev firmware. I can buy applications, however, I can't even see protected Apps.
One more question based on this. I've been reading through the forums and I've read that the dev phone comes with a DEV SPL. So basically I wanted to clarify that, the SPL doesn't matter if it is DEV/HARD. I can install the RC33 image by doing the whole RC29 downgrade, etc?
Probably way off here, but if anyone can point me in the right direction. Basically what I'm trying to do is, purchase a dev phone, get the latest rc series on it (and hopefully receive OTA updates). Or is getting OTA updates a bad idea? and I should continue to manually update the image as and when new ones are released?
Thanks in advance.
I don't want to know how to root, I can find my answer for that on Google, however what I don't get is what it does...
I know it unlocks the device somehow, but can't I simply access everything in the system if I compile android from source and install it on the device?
I have downloaded the android source and I believe I can access every possible thing, so why is rooting needed?
If I install an app as a system app, won't it automatically have the permissions to do what I need it to do?
AFAIK rooting is for the people you'd call the end user/consumer or whatever.
If you have a new phone and want to install one of the many custom ROMs around, you simply need a rooted phone.
A custom ROM is in easy terms a custom made User Interface for the phone.
There is lot more complicated stuff going on under the hood, but in general you change the look and feel of you phone's UI.
The phone has to be rooted, because the manufacturers and net providers around pack a lot of useless crap called "bloatware" (like Samsung Shop and Samsung Play and Samsung Sing and Dance and Music and whatnot) on your phone, which often makes it slower than it can be without it.
But naturally the big corps don't want you to be able to get rid of that **** too easily, which is why you don't have access to the system folders as a normal user.
I guess in your case it's possible that you (if you compiled android from source and installed it on your device) so to say have an already rooted phone, since Android itself is rooted by default. Like I said, the manufacturers are the ones to unroot Android in order to dictate which apps their customers might or might not use.
But I'm a noob and am not sure how you would install Android on your phone if it's new (and unrooted by default?) if you haven't rooted it before?
meh, hope that helped a bit at least...
root- you would love to do it after reading this..
Root? what is it?
it is what i call full access to our phone, flash new roms, have dual boot (example- you can have to os like ics and JB), can access the evasive /data folder which holdes the apk/setups of apps installed from playstore and many other things..
If you are concerned about warranty you can unroot your phone and give in your phone for warranty. i have given my phone for warranty like this.
The most important thing i like about root is that i can fix my phone myself (if it is a software problem). any other question please ask, and i will answer it.
Thanks if helped!
I don't have the time for development anymore. I used to play with stuff like that years ago, but life has taken me away from it. I'd still like to be able to access everything on my phone and play with custom roms, and root lets me do that. The end consumer comment is a good one.
As for to root or not root, I tell most people who ask me to root for them what they use their phone for and explain what they would get out of rooting, and explain the risks involved. Seems that people who understand what rooting does are able to do it themselves, and the ones that ask you to do it for them usually decide against it after hearing "there is a tiny chance that your phone could get bricked" lol
If you just want to play emulators etc, how would you benefit from rooting?
IMO rooting is very useful if you want to keep touching system things in a stock rom, optimizing and debloating it, installing other people ROMs, etc... I believe that if you compile your own flavour of android and find no restriction doing whatever you want, you don't need to.
Android phone without root is nothing
McFex said:
AFAIK rooting is for the people you'd call the end user/consumer or whatever.
Click to expand...
Click to collapse
:good:
McFex said:
But I'm a noob and am not sure how you would install Android on your phone if it's new (and unrooted by default?) if you haven't rooted it before?
Click to expand...
Click to collapse
Some phones can just be flashed (for example via usb) which gives you full control, others can be cracked.
Hey guys, new here, sorry can't post in recoveries section.
I recently bought a Pixel off ebay and the guy that sold it to me bought it off Gumtree. The original seller left all his stuff on it and the guy i bought it off couldn't even access the phone because it had a passcode lock on it. He tried contacting the owner but he never responded (yayyy).
Then there's me, because I'm smart and was like I CAN JUST FACTORY RESET IT, which kicked in the FRP. Unfortunately Google has had fun developing this phone to be super secure and although I no longer have a passcode to worry about, I can't bypass the FRP and I don't know the original owner's account details.
Here's some details:
USB Debugging is OFF
Only option I have on ADB is sideload
Bootloader is LOCKED
Phone is NOT ROOTED
Currently running 7.1.1
Phone is CARRIER unlocked (I can receive calls and use my data when trying to log into my gmail, which doesnt work because I have to use original account).
Is there any solution to bypass this? Much appreciated. I tried to go through google because I bought the phone off ebay and so the FRP prevents them as I didn't buy it directly off google. Am trying to track down the original owners details via my ebay seller to hopefully force the owner to comply. Any way I can get around this would be amazing.
josiedalek said:
Hey guys, new here, sorry can't post in recoveries section.
I recently bought a Pixel off ebay and the guy that sold it to me bought it off Gumtree. The original seller left all his stuff on it and the guy i bought it off couldn't even access the phone because it had a passcode lock on it. He tried contacting the owner but he never responded (yayyy).
Then there's me, because I'm smart and was like I CAN JUST FACTORY RESET IT, which kicked in the FRP. Unfortunately Google has had fun developing this phone to be super secure and although I no longer have a passcode to worry about, I can't bypass the FRP and I don't know the original owner's account details.
Here's some details:
USB Debugging is OFF
Only option I have on ADB is sideload
Bootloader is LOCKED
Phone is NOT ROOTED
Currently running 7.1.1
Phone is CARRIER unlocked (I can receive calls and use my data when trying to log into my gmail, which doesnt work because I have to use original account).
Is there any solution to bypass this? Much appreciated. I tried to go through google because I bought the phone off ebay and so the FRP prevents them as I didn't buy it directly off google. Am trying to track down the original owners details via my ebay seller to hopefully force the owner to comply. Any way I can get around this would be amazing.
Click to expand...
Click to collapse
If I understand your situation correctly, you have e a rough road ahead of you. The Google kill switch can only be disabled by the legitimate Google account holder, before the phone was reset.
If this was easily unlocked, it wouldn't be an option worthwhile. Basically, if you get it unlocked then Google has wasted their time on developing that feature.
I don't think you'll be getting into that phone and honestly, I hope you don't because then that means mine is less likely to be stolen since it is worthless without my credentials
For years, we've all learned to disable Find My iPhone before we sell an IOS device. Similarly, we have to deactivate Google's kill switch prior to factory reset a Marshmallow or Nougat device. It's really a good anti-theft implementation by Google. It's too bad that many sellers, for whatever reason, don't do it before selling.
I can enter the full OS, but can not enable ADB nor add a new account. Any insight?
Bypass tut not tested on Android 7 but works on marshmallow
https://www.youtube.com/watch?v=7OldC6kzuYk
http://rootjunkysdl.com/files/Apps/FRP/com.rootjunky.frpbypass-1.0.apk
*$M3RT$* said:
Bypass tut not tested on Android 7
https://www.youtube.com/watch?v=7OldC6kzuYk
http://rootjunkysdl.com/files/Apps/FRP/com.rootjunky.frpbypass-1.0.apk
Click to expand...
Click to collapse
Scary, but the logic makes perfect sense. I can see it being very useful for honest people.
josiedalek said:
Hey guys, new here, sorry can't post in recoveries section.
I recently bought a Pixel off ebay and the guy that sold it to me bought it off Gumtree. The original seller left all his stuff on it and the guy i bought it off couldn't even access the phone because it had a passcode lock on it. He tried contacting the owner but he never responded (yayyy).
Then there's me, because I'm smart and was like I CAN JUST FACTORY RESET IT, which kicked in the FRP. Unfortunately Google has had fun developing this phone to be super secure and although I no longer have a passcode to worry about, I can't bypass the FRP and I don't know the original owner's account details.
Here's some details:
USB Debugging is OFF
Only option I have on ADB is sideload
Bootloader is LOCKED
Phone is NOT ROOTED
Currently running 7.1.1
Phone is CARRIER unlocked (I can receive calls and use my data when trying to log into my gmail, which doesnt work because I have to use original account).
Is there any solution to bypass this? Much appreciated. I tried to go through google because I bought the phone off ebay and so the FRP prevents them as I didn't buy it directly off google. Am trying to track down the original owners details via my ebay seller to hopefully force the owner to comply. Any way I can get around this would be amazing.
Click to expand...
Click to collapse
I came up with a way to remove FRP for this device. I currently have the only video up on youtube so it should be easy to find. I cant post links yet so just search google or youtube for "google pixel frp bypass" and it will come up. It involves the use of a USB-C OTG adapter and the dirtycow exploit. It actually works for a truly universal frp bypass for every device vulnerable to the device. The entire process is done on a bootloader locked, usb debugging off, no internet connection and no other device (besides the usb). Enjoy, it took me weeks to figure it out lol.
trjv said:
I came up with a way to remove FRP for this device. I currently have the only video up on youtube so it should be easy to find. I cant post links yet so just search google or youtube for "google pixel frp bypass" and it will come up. It involves the use of a USB-C OTG adapter and the dirtycow exploit. It actually works for a truly universal frp bypass for every device vulnerable to the device. The entire process is done on a bootloader locked, usb debugging off, no internet connection and no other device (besides the usb). Enjoy, it took me weeks to figure it out lol.
Click to expand...
Click to collapse
I'm curious to see if the OP will have luck with this
magnumtripod said:
I'm curious to see if the OP will have luck with this
Click to expand...
Click to collapse
I posted this in the dirtycow forums section but I figure it has relevance here as well. Sorry if this is considered double posting.
This method wont help you to root the device, just to bypass FRP. Since dirtycow doesn't persist after a reboot (I think) it wont help as far as gaining root. However it will help you to modify files on the device. I also realized that it only has the power to overwrite files that the current user has read access to, despite whether the filesystem is mounted read-only. With this in mind I was looking over my Nexus 6P and checking to see which files had read access as user and realized that GoogleLoginService.apk and GoogleLoginService.odex both fall under this category. The files are located at /system/priv-app/GoogleLoginService and associate with Google Account Manager when installed as a system app. When the data is corrupted you can install Google Account Manager as a user app, which changes the location and file names to /data/app/com.google.gsf.login-1/base.apk and base.odex. If you corrupt these files at this point then try to disable and uninstall and select replace with the factory version it wont have anything to "replace with the factory version" and tell you that uninstall failed. Once this happens you can reinstall GoogleAccountManager.apk which will again install as a user app, which will then let you perform a full successful uninstall of Google Account Manager. At this point you have full control to be able to downgrade to a previous version of Google Account Manager without it telling you that "data is corrupted" and from there perform the web sign in activity. I've tested on multiple devices and multiple versions and this works on every single device on every version of Android including the latest 7.1.1 as long as it is not on the most recent December 5 2016 security patch since dirtycow was removed with those updates.
trjv said:
I posted this in the dirtycow forums section but I figure it has relevance here as well. Sorry if this is considered double posting.
This method wont help you to root the device, just to bypass FRP. Since dirtycow doesn't persist after a reboot (I think) it wont help as far as gaining root. However it will help you to modify files on the device. I also realized that it only has the power to overwrite files that the current user has read access to, despite whether the filesystem is mounted read-only. With this in mind I was looking over my Nexus 6P and checking to see which files had read access as user and realized that GoogleLoginService.apk and GoogleLoginService.odex both fall under this category. The files are located at /system/priv-app/GoogleLoginService and associate with Google Account Manager when installed as a system app. When the data is corrupted you can install Google Account Manager as a user app, which changes the location and file names to /data/app/com.google.gsf.login-1/base.apk and base.odex. If you corrupt these files at this point then try to disable and uninstall and select replace with the factory version it wont have anything to "replace with the factory version" and tell you that uninstall failed. Once this happens you can reinstall GoogleAccountManager.apk which will again install as a user app, which will then let you perform a full successful uninstall of Google Account Manager. At this point you have full control to be able to downgrade to a previous version of Google Account Manager without it telling you that "data is corrupted" and from there perform the web sign in activity. I've tested on multiple devices and multiple versions and this works on every single device on every version of Android including the latest 7.1.1 as long as it is not on the most recent December 5 2016 security patch since dirtycow was removed with those updates.
Click to expand...
Click to collapse
Yeah so I'm Zhythe on YouTube I was actually already talking to you on there before I checked this thread. I have Dec 5 security patch is there anything you can do to get around it that doesn't involve dirtycow? :/
josiedalek said:
Yeah so I'm Zhythe on YouTube I was actually already talking to you on there before I checked this thread. I have Dec 5 security patch is there anything you can do to get around it that doesn't involve dirtycow? :/
Click to expand...
Click to collapse
oh hey whats up! nice to see you here as well im still trying to fix my pixel since it bricked when trying to update it haha. Been a little distracted though this morning since phonlab hase stolen my method and now he and rootjunky are passing it off as if they found it first without giving me credit for it and charging to teach the method. serious backstabbing right there. but once i get this pixel up and running again i'll find a method and host it from my website so no copycats rip me off.
trjv said:
oh hey whats up! nice to see you here as well im still trying to fix my pixel since it bricked when trying to update it haha. Been a little distracted though this morning since phonlab hase stolen my method and now he and rootjunky are passing it off as if they found it first without giving me credit for it and charging to teach the method. serious backstabbing right there. but once i get this pixel up and running again i'll find a method and host it from my website so no copycats rip me off.
Click to expand...
Click to collapse
Hey! Yeah that's such a dog move by both of them seriously... not cool. No worries I'll keep an eye on your website for updates Best of luck!
Check this out!!
See what I mean? Haha idk why I ever wanted to be a part of this place anyways lol. Nothin but disrespect since the moment I posted the method.
trjv said:
See what I mean? Haha idk why I ever wanted to be a part of this place anyways lol. Nothin but disrespect since the moment I posted the method.
Click to expand...
Click to collapse
Yeah I totally ignored it :/ dw you're so much better and obviously smarter cause you did it before them
NBreunig3 said:
Check this out!!
Click to expand...
Click to collapse
Hi @NBreunig3!
trjv said:
See what I mean? Haha idk why I ever wanted to be a part of this place anyways lol. Nothin but disrespect since the moment I posted the method.
Click to expand...
Click to collapse
You could report that YouTube video and show/link to your source of where you first posted the method. Get them to take them down!
Frp google pixel
can be reseted with XTC2CLIP if u have unlocked bootloader i tested on my device.
warrior26ro said:
can be reseted with XTC2CLIP if u have unlocked bootloader i tested on my device.
Click to expand...
Click to collapse
@warrior26ro I stated clearly the bootloader was locked. XTC2CLIP is also for HTCs. Please don't post unless you've read the question properly.
Technically the Google Pixel is an HTC device since they are the manufacturers of them. Not that that helps the situation any more or less to know just figured I'd mention it lol. You can even issue some proprietary HTC fastboot commands on Pixel devices, but I haven't gotten them to do anything special from using them. Commands such as fastboot oem rebootRUU makes the phone reboot but not into anything special that I've noticed, just reboots the phone. I'm sure there are others but that one in particular is definitely HTC only lol.
On a side note I'm still diligently working on a method for the newer devices every day. It's only a matter of time before I get it lol. While on the subject at least here's a couple thoughts if anybody has any insight...
I've been looking at other binary commands to gain a foothold of, sort of like the whole idea behind run-as that the dirtycow peeps use. After installing Nethunter on my 6P I noticed that there is another command with potential privilege abuse called "procmem". It doesn't need superuser privileges to use nor does it only respond to ROOT or SHELL users, so its basically universally allowed from "untrusted app" users (i.e. termux, terminal emulator, material terminal, etc.). The only thing is that I'm pretty sure that command is only installed with a proper busybox installation, and further it only has the proper setuid bit needed + standard user permissions (that I've seen) when installed into /system/xbin. So basically my idea is to leverage a modified procmem binary to gain (insert something here) that might lead to (insert something else here) lol. Not really a whole plan but I figure if I can find a way to get procmem into /system/xbin on a non-rooted device then at least I have something to work with lol. Otherwise I've also been looking into a way to become SHELL user without using "adb shell". I know that with the Moto 360 there was some fancy adb command to enable native adb support but I can't seem to remember how to go about it. So yeah, thats all I've got so far lol.
Ok, so I'm a little new to this. I am pretty much unfamiliar with root (I've only done it once, a few years ago, on a completely different kind of device, via KingoRoot without even having to plug in to a PC), but I am very good at following directions/making sense of tutorials . But recently I have have become very aware of privacy concerns, and I realize that the form my phone is in now is very insecure.
But I'm a little confused by "rootable" vs "unlocked bootloader"
So, I though I understood these terms, but apparently I don't. I thought that *root access* was an admin level (the highest), and that it required an unlocked bootloader to achieve it. However, my device, Galaxy S7 US version, is supposedly rootable(https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502), but does not have an unlocked boot-loader, like the international/Exynos version, that would allow you to install a custom ROM. How is this possible?
Either way, I cannot use a custom ROM, since none of the even remotely trustworthy ones (Copperhead, Lineage, Replicant) work on the US version.
So, if I am stuck with Samsung version android, what else can I do (If any of these are possible, a little direction or at least a link to a good guide would be very helpful)?
- Without an unlocked boot loader, can I still remove all GAPPS and bloatware?
- Can I remove Googe Play Services and replace it with MicroG, and still use the apps with the Play dependency?
- Is Xposed/Xprivacy an option? (Are these still considered safe?).
- If not, how can I get the most specific control over device processes: being able to see and control permissions for each app, moniter all incoming/outgoing data stream (everything apps send to other parties/devices and what they receive),
- Any possibility for a firewall?
I realize that this is asking a lot, but Reddit was thoroughly unhelpful, so I throw myself at your charity.
Hi all,
I'm a bit confused at the moment.
My mum dropped her phone and needs a new one. I was able to retrieve all her data and would also like to set up a device for her with a minimal custom rom, etc.
Now, she doesn't have a lot to spend on a phone, so the logical decision would be to get a good used device. That's when I learned of FRP. However, I'm unsure how exactly it works.
Is there any way to get around it, at all, without having the Google account data? (And without sending it to the manufacturer, as that would surely raise the costs, making it pointless.)
I've read on a few threads that it's possible to re-flash the stock firmware, but then someone wrote that the account still was needed to install custom roms.
Is this heavily dependent on the device or are there some general rules to follow?
NovusDeus said:
Hi all,
I'm a bit confused at the moment.
My mum dropped her phone and needs a new one. I was able to retrieve all her data and would also like to set up a device for her with a minimal custom rom, etc.
Now, she doesn't have a lot to spend on a phone, so the logical decision would be to get a good used device. That's when I learned of FRP. However, I'm unsure how exactly it works.
Is there any way to get around it, at all, without having the Google account data? (And without sending it to the manufacturer, as that would surely raise the costs, making it pointless.)
I've read on a few threads that it's possible to re-flash the stock firmware, but then someone wrote that the account still was needed to install custom roms.
Is this heavily dependent on the device or are there some general rules to follow?
Click to expand...
Click to collapse
FRP isn't an issue if the device is properly reset, many people don't.
FRP on most Android devices can be bypassed, just do a search on YouTube for FRP, the device and current Android version.
Best to ask the seller if the device is FRP locked before buying.
Sent from my Moto E (4) using Tapatalk
The problem is that most sellers don't seem to even know about this, as it's done automatically opt-out (I didn't either, but my phone is already older than Android 5 and I've just used it with Lineage all the time and didn't bother).
I've talked to a handful of sellers online now and asked them if their accounts were removed, but they always just reply with "sure, the phone is factory reset", then you have to explain to them what FRP even is and why they need to check manually. Some didn't even respond after that yet, one still didn't fully get my issue. It's a complete mess, I just wanted to buy a used phone for my mum.
sd_shadow said:
FRP on most Android devices can be bypassed, just do a search on YouTube for FRP, the device and current Android version.
Click to expand...
Click to collapse
Thanks for the hint, I didn't even consider looking on Youtube. I've had a quick search and I can see that it's easier to show the instructions that way, so no wonder I haven't found much concrete info.
However most I've seen just replace the Google account with their own one. I presume you would swap out the account with your own, then disable FRP and delete the account? Does that work?
My mum doesn't have a Google account, I have one, but I don't really want it sitting on there. I didn't even plan on installing any Google services to begin with..