Database Develop

Are Custom Roms secure?

I have been wondering, how secure are android roms? What I mean is, if I should be worried about getting personal data stolen or any such thing concerning web surfing, online purchases, etc? Which is more secure? Stock Roms or cusom Roms? Any help would be greatly appreciated! Thanks!

Supermannypr said:
I have been wondering, how secure are android roms? What I mean is, if I should be worried about getting personal data stolen or any such thing concerning web surfing, online purchases, etc? Which is more secure? Stock Roms or cusom Roms? Any help would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
Grow up mate... :laugh:
There are thousands of user who are enjoying custom roms and still you think it insecure...

erpurohit said:
Grow up mate... :laugh:
There are thousands of user who are enjoying custom roms and still you think it insecure...
Click to expand...
Click to collapse
This is a harsh response to what I believe is a very valid question by the original poster. People ask questions because they have concerns or simply do not know the answer. They do not need people like you having a shot at them simply because they asked a question.
To the OP: The people who put together the custom ROMs you find on XDA are mostly genuine people looking to share their knowledge and experience by building ROMs that make our devices operate faster, smoother, and feature enhanced. They are not out to load them with malware to scam you and suck your credit and identity dry.
Having said that however, it could be done if the wrong person or group of people starting building ROMs with that purpose.
I personally will only ever download a ROM from a builder or group of builders who have a credible reputation here in the Forums to be sure.
I hope that eases you mind a little.
Take care.

I didnt meant to be harsh... Sry if it feel so...

Thankyou.
Trinnity66 said:
This is a harsh response to what I believe is a very valid question by the original poster. People ask questions because they have concerns or simply do not know the answer. They do not need people like you having a shot at them simply because they asked a question.
To the OP: The people who put together the custom ROMs you find on XDA are mostly genuine people looking to share their knowledge and experience by building ROMs that make our devices operate faster, smoother, and feature enhanced. They are not out to load them with malware to scam you and suck your credit and identity dry.
Having said that however, it could be done if the wrong person or group of people starting building ROMs with that purpose.
I personally will only ever download a ROM from a builder or group of builders who have a credible reputation here in the Forums to be sure.
I hope that eases you mind a little.
Take care.
Click to expand...
Click to collapse
I have always had that question. I have to agree on only installing roms from devs with a credible reputation, at the end of the day this is what I would use for everything and I need to feel ane be sure I am secure. Thanks for your answere, I can keep my peace in that aspect.
Thanks to all the devs that dedicate there time with their amazing Rom projects!! Keep up the great work!!!

Allmost every "custom" roms include a rooted kernel and CWM recovery. That will give anyone who can do "adb" operations the option to reboot your phone to recovery. Sim,pattern or pin lock doesn't matter as long as phone is in their hand.
Battery off - reboot to CWM, connect usb, and everything on your phone is available to copy to computer using adb commands.
The only way to secure custom ROM run by a rooted kernel with CWM is to ENCRYPT all files on your phone.

As a ROM Maker, I always care about every permissions for every single file. I everytime match everything true permissions but not 777 even if I fail 999 times.
Sent from my GT-I9000 using xda app-developers app

Think about this. Someone finds your phone, you had lost it. Turns off pulls out sim so you can't find its location, reboots into recovery, connects to computer, then adb shell and do the command dd /data. Dumps all the data into a .IMG file. Repacks it into an Odin flash able tar. Flashes to his phone. Has all your info.
I wouldn't worry though, most people know nothing of this. I don't worry
Sent from my GT-I9000 using xda premium

O-T and AlwaysDroid, you guys are absolutely right, but the OP still raises a legitimate concern. There's lots of other threat assessments that will rule out physical access. It's a matter of practicality. In some places, traditional martial arts self-defense training can help or save you, in others most clashes do not involve hand-to-hand fighting.
I'm typing on xda app, do forgive Mr for forgetting names, but others here are right, too. A developer's reputation goes a long way, and these teams also put their code out for others to see. I can't tell what's inside, but rely on the fact that others look at it to learn, compile themselves, cherry pick, etc. Also, I do prefer when devs post MD5s.
Back to OP, which primarily asked about data leakage, is there an android equivalent of Little Snitch on Macs?
sent from a telephonic device

Yes they are
use basic custom roms if u wish. . which r stable..
dont prefer nightlies/ alpha if u r a starter
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
burakgon said:
As a ROM Maker, I always care about every permissions for every single file. I everytime match everything true permissions but not 777 even if I fail 999 times.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Nobody like frequent force closes.. do they ?

AlwaysDroid said:
Think about this. Someone finds your phone, you had lost it. Turns off pulls out sim so you can't find its location, reboots into recovery, connects to computer, then adb shell and do the command dd /data. Dumps all the data into a .IMG file. Repacks it into an Odin flash able tar. Flashes to his phone. Has all your info.
I wouldn't worry though, most people know nothing of this. I don't worry
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Wow! I had no idea that someone could do that... I know that this has a very slim chance of happening, but is there anyway to avoid it?

Yes, they are.

since the source is open to all
and anyone could examine it
i would say they are somewhat secure

Supermannypr said:
Wow! I had no idea that someone could do that... I know that this has a very slim chance of happening, but is there anyway to avoid it?
Click to expand...
Click to collapse
Not really :/ almost no one can do this, I mean unless the guy that finds your phone is a resident here or at roots wiki and even then, I doubt it. The thing is, as long as your rooted, your data just isn't as safe. You couldn't do that on stock, cause its not rooted. The only thing I could imagine for the future would be a recovery that asks for a pin code before allowing you to enter. Its unavoidable, and really nothing to worry about. Just turn off USB debugging when not in use, use dev options to only give apps root access and not adb (not sure if it stops it in recovery as well) and don't lose your phone.
Sent from my GT-I9000 using xda premium

Apropos encryption
O-T said:
Allmost every "custom" roms include a rooted kernel and CWM recovery. That will give anyone who can do "adb" operations the option to reboot your phone to recovery. Sim,pattern or pin lock doesn't matter as long as phone is in their hand.
Battery off - reboot to CWM, connect usb, and everything on your phone is available to copy to computer using adb commands.
The only way to secure custom ROM run by a rooted kernel with CWM is to ENCRYPT all files on your phone.
Click to expand...
Click to collapse
Is there a way to enable file system encryption in Cyanogenmod 7?

AW: Are Custom Roms secure?
de333 said:
Is there a way to enable file system encryption in Cyanogenmod 7?
Click to expand...
Click to collapse
System encryption is a 4.1 feature; not with cm 7
Sent from my Nexus 7

Well, Samsung stopped updating this capable phone which is similar to the nexus s(they claimed it can't handle ICS or jb while nexus s gets the latest firmware) Custom ROMs especially jb ROMs make your phone feel new unlike stock which are outdated. Just flash one from a credible developer & u won't regret

There is no motive from the developers. What should they get? Your FB passwords? And sell them to your girlfriend?

Agree
Supermannypr said:
I have always had that question. I have to agree on only installing roms from devs with a credible reputation, at the end of the day this is what I would use for everything and I need to feel ane be sure I am secure. Thanks for your answere, I can keep my peace in that aspect.
Thanks to all the devs that dedicate there time with their amazing Rom projects!! Keep up the great work!!!
Click to expand...
Click to collapse
I am 100% agree, with the your comment bro. We should install the ROM from recognized and good reputed developers.
:good::good::good::good:

Eirwn said:
There is no motive from the developers. What should they get? Your FB passwords? And sell them to your girlfriend?
Click to expand...
Click to collapse
Really? So if there was - just for the sake of argument - a backdoor or a keylogger on your phone that was placed there by a dev, you're saying they would get nothing out of that? Is a bit naive dont you think?

[Q] Toolkit Questions

Hello people,
I am fairly new to this forum and I have the following questions that I would appreciate help for.
1. Has any one rooted the I9305, HongKong ( ZHBLJ1 ) Build using the Toolkit? This build is not there in the Toolkit model selection options for I9305.
2. Can we flash the CWM intended for I9300 on our I9305 ?
Thanks in advance!
--
Pradeep

pai.pradeep said:
Hello people,
I am fairly new to this forum and I have the following questions that I would appreciate help for.
1. Has any one rooted the I9305, HongKong ( ZHBLJ1 ) Build using the Toolkit? This build is not there in the Toolkit model selection options for I9305.
2. Can we flash the CWM intended for I9300 on our I9305 ?
Thanks in advance!
--
Pradeep
Click to expand...
Click to collapse
The most simpler way to root at the moment is this:forum.xda-developers.com/showthread.php?t=2050297
As an extra you'll get a patch to security hole of exsynos syst3m.
Regarding recovery dont know for cwm but you can use goo manager from the market to flash TWRP. Just open the optios and choose something like 'install the open recovery script'.
For the case yiu are wondering, yes I am using GS3 LTE I9305.

!crazy said:
Regarding recovery dont know for cwm but you can use goo manager from the market to flash TWRP. Just open the optios and choose something like 'install the open recovery script'.
Click to expand...
Click to collapse
TWRP works for the i9305? I don't think so, the official site doesn't state it and I have not seen anywhere else that it has been ported. Then again, I haven't tried it myself

Vipeout said:
TWRP works for the i9305? I don't think so, the official site doesn't state it and I have not seen anywhere else that it has been ported. Then again, I haven't tried it myself
Click to expand...
Click to collapse
I am terribly sorry. You are right. The problem was I have both GN 2 and SG3, was tired and so mixed the devices...
Regarding root method, that works on both devices.
Here is a link for the case OP wants to install CWM:
www.androidauthority.com/galaxy-s3-gt-i9305-root-clockworkmod-recovery-126605/
Here is the direct link to xda thread in dev section;
forum.xda-developers.com/showthread.php?t=1914394
I will also try flashing twrp later when i find time and report back.
Regarding the toolkit, that's actually a question for the dev. I am going to ask him that by myself, I have donated version and since he has a thread in dev section of I9305 he should have some knowledge about this and what for his toolkit can actually be used with LTE SG3.

!crazy said:
I am terribly sorry. You are right. The problem was I have both GN 2 and SG3, was tired and so mixed the devices...
Regarding root method, that works on both devices.
Here is a link for the case OP wants to install CWM:
www.androidauthority.com/galaxy-s3-gt-i9305-root-clockworkmod-recovery-126605/
Here is the direct link to xda thread in dev section;
forum.xda-developers.com/showthread.php?t=1914394
I will also try flashing twrp later when i find time and report back.
Regarding the toolkit, that's actually a question for the dev. I am going to ask him that by myself, I have donated version and since he has a thread in dev section of I9305 he should have some knowledge about this and what for his toolkit can actually be used with LTE SG3.
Click to expand...
Click to collapse
Is there anything I need to take care of before rooting using the first method? Apart from the usual backup of data? Any issues with the Camera as mentioned in that thread? (this is pertaining to our I9305 specifically).
Thank you, I will track that Toolkit thread for I9305 as well!

Managed to root it using the app by Chainfire,
still for CWM

pai.pradeep said:
Managed to root it using the app by Chainfire,
still for CWM
Click to expand...
Click to collapse
You got link for CWM? Regarding camera problem, it doesn't have anything to do with rooting. It happens on some devices if one ticks 'patch hole' or whatever. I personally didn't have that problem but another one which maybe isn't related to the patch. It happened only once, a day ago, couldn't hear anything when calling someone or when someone was calling me. Reboot 'solved' it.
To bad that the best SG3 edition receives so little support from devs. It is probably Samsung's fault. They even change encryption method, or some parts of it, so for example with note 2 I am not able to use twrp when encrypted. In feature I am going to buy probably only nexus devices even galaxy note feature editions could pose a temptation. Bit soon we will be getting devices with 1080 resolution and hopefully there will be nexuses with bigger screen.

!crazy said:
You got link for CWM? Regarding camera problem, it doesn't have anything to do with rooting. It happens on some devices if one ticks 'patch hole' or whatever. I personally didn't have that problem but another one which maybe isn't related to the patch. It happened only once, a day ago, couldn't hear anything when calling someone or when someone was calling me. Reboot 'solved' it.
To bad that the best SG3 edition receives so little support from devs. It is probably Samsung's fault. They even change encryption method, or some parts of it, so for example with note 2 I am not able to use twrp when encrypted. In feature I am going to buy probably only nexus devices even galaxy note feature editions could pose a temptation. Bit soon we will be getting devices with 1080 resolution and hopefully there will be nexuses with bigger screen.
Click to expand...
Click to collapse
Yes from the link you gave, Thanks. I am having the problem that the CWM doesn't stick and I get the stock recovery back after the reboot.. They are talking about the /system/boot-recovery.p file which isn't on my phone. It has the /system/recovery-from-boot.p file. Are they the same file ?
Even I am surprised that our S3 model has such little support here. I am hoping that it will only get better as many people get their hands on this!! :good:

A issue with flash tool thats iratating the life outa me not wiping the phone

I did the simunlock the other day ive been expiermenting on my g4 and i restored tot method with flashtool like i have in the past. Well internal sd and unlock stuck. When phone booted up it was still unlocked and intern sd data was still there in the past flash tool wipes everything why not this time

androidddaaron said:
Why play with your device if you don't know to expect issues. Guess this one bit you in the ~ too when you can't even run or know what to expect from a flash tool either .So don't ask questions if you can't find your own answers
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
You are missing the point of XDA! Of course he expects issues if he's modding stuff. XDA is all about trial and error. It's also about helping people to not make mistakes, and to help them fix mistakes they made. It's about sharing information and asking for help. XDA may have orignally only been for developers, but not that is not the case anymore. Even when it was, developers ask for help too! To not ask for help is egotistical and foolish. Intelligent people ask questions.

tabp0le said:
Hey no worries man. There is a big difference with CDMA and GSM. GSM is so much easier to work with. Sprint needs to get with the program lol
Click to expand...
Click to collapse
I havnt had a sprint phone since my g2 even then i was runnin the tmobile rom on it on straight talk on att network

Thread cleaned
Please read forum rules before posting
Rudeness as well as condescension is not allowed
We are here to help each other

[ROM][Stable]Stock Debloated 1.23.1550.3 MetroPCS

This Is My First Shot at making something for this device,so please bear with me.
This Is A Custom Stock ROM that has been debloated and slimmed down a bit to my personal liking.
ive used SuperR's Kitchen on Ubuntu to bring this to you guys.
i used Captain_Throwbacks Metro Base ROM as a starting point.
i will include my list of apps that i have removed in the second post.
i would suggest a factory reset and dalvik/ART wipe
as always,if your device explodes or stops working,i assume no responsibility for any damages or data loss.
flash at your own risk.
if anyone has any suggestions and/or input,please feel free.
im no developer,just taking a shot at this.
the goal is to remove as much bloatware as possible,whilst maintaining stability.
:highfive:
i added /data/app support as well as busybox & deodexed the ROM.
im currently uploading my first build to google drive and will share links shortly.
bear with me as i dont have the best internet connection.
DeZiREv5K
OP Updated with newer build.
Code:
6-14-16 build changelog
--Removed HTC Launcher(replaced with google now launcher)
--updated play store to latest version
--updated HTC Service pack to latest and integrated back into ROM(no longer needs Seperate download)
--attempted to add back the official metropcs device unlock app(Thanks [user=3100103]@sandix[/user] !)
6-16-16 build changelog
---removed google play launcher & replaced with nova launcher(issue with installment on first boot)
6-19-16 build changelog
-- changed ZIP compression method(v3 was too large)
This is A Flashable Zip,should flash in TWRP.
Special Thanks to the following folks:
@sandix for the continuous hard work in the forums here
@Captain_Throwback for his stock rooted metroPCS ROM.
@SuperR. for his Excellent Kitchen!!!
@nightbreed813 for his thread layout & list of modifications to his ROM

This Is My Bloat_Custom File that i edited by hand to suppliment in the kitchen.
these are all the apps/folders that were removed prior to building.
Code:
system/app/BasicDream*
system/app/Calculator*
system/app/CalculatorWidget*
system/app/Chrome*
system/app/Cloudex*
system/app/CloudPrint*
system/app/Drive*
system/app/DriveActivator*
system/app/Exchange3Google*
system/app/FaceLock*
system/app/Font_Helvetica*
system/app/Font_XinGothic*
system/app/Font_Yuen*
system/app/Gmail2*
system/app/GoogleTTS*
system/app/Hangouts*
system/app/HoloSpiralWallpaper*
system/app/HtcCarGps*
system/app/HtcBackupReset*
system/app/LiveWallpapaers*
system/app/HtcLogLevel*
system/app/HTC_Connect*
system/app/HTCZero*
system/app/IMEMurasuIndic*
system/app/IMEMurasuViet*
system/app/IME_TP_Basic*
system/app/IME_TP_ValueAdd*
system/app/Kidmode-google*
system/app/Maps*
system/app/MPCS_Blockit*
system/app/MPCS_Metro411*
system/app/MPCS_MyMetro*
system/app/NoiseField*
system/app/PhaseBeam*
system/app/Photos*
system/app/PrintStudio*
system/app/talkback*
system/app/YouTube*
system/priv-app/HtcDotMatrix*
system/priv-app/HtcFileManager*
system/priv-app/HtcDLNAMiddleLayer*
system/priv-app/MPCS_MetroAppStore*
system/priv-app/iCloudTransfer*
system/priv-app/MPCS_MetroZONE*
system/priv-app/MPCS_RSU*
system/priv-app/LMIRescue*
system/priv-app/Velvet*
system/priv-app/LMIRescueSecurity*
system/priv-app/HtcSoundrecorder*
system/priv-app/Twitter*
system/priv-app/MirrorLink_MirrorLinkService*
system/priv-app/MPCS_Lookout*
system/priv-app/PolarisOffice*
system/priv-app/Mail*
system/priv-app/HTCSpeakCyberon*
system/priv-app/Facebook*
system/media/audio/notifications*
system/media/audio/ringtones*
system/media/audio/alarms*

TO DO List:
edit updater script to change out rom title
check what works and what does not
(Possibly) remove More files/Free up more space
upload newer build as first one fail with status 7 in recovery.(assert error)

Check my build and compare to yours to see what can be removed. I'm sure you will find a lot more that can be done.

when will a working link be available? very excited for this rom

talking_llama said:
when will a working link be available? very excited for this rom
Click to expand...
Click to collapse
i already uploaded a newer build,will update OP with working link.
@sandix ,thank you very much i definitely will do that!

worked for me, thank you!

sweet. finally a flashable rom for our metro variant. was debating on trying nightbreed's rom, as someone mentioned in that thread that they tried it and it worked. didn't want to kill the phone though as it is a daily driver. will report after using.

Ipoke Smot said:
sweet. finally a flashable rom for our metro variant. was debating on trying nightbreed's rom, as someone mentioned in that thread that they tried it and it worked. didn't want to kill the phone though as it is a daily driver. will report after using.
Click to expand...
Click to collapse
Let me know how it works out.also,if you have any suggestions feel free to throw them out here.

so i assume i have to install TWRP and flash this?

corrado85 said:
so i assume i have to install TWRP and flash this?
Click to expand...
Click to collapse
Yeah it's required

Just looking at channel log I'm assuming this is still relevant. I'm on V3 and with some frustration (I don't have Wi-Fi and had to trick my 6yr old laptop to boot up) I got it running well.
As someone who has hard bricked smart phones since the xv6800, this is a first good go. Inspires me to start cooking my own roms.
Suggestion: A file browser would have made it so much smoother. No one with half a brain will ***** about es file explorer or root browser being cooked in. Fortunately bad habits inspired me to always backup original stock. Most people would've been screwed there. Dirty flash. Pdanet. Got it all up and going.
Keep up the good work. Look forward to any tweakings you find out of my league
Sincerely,
Satisfied end user
Sent from my HTC Desire 626s using Tapatalk

trekie4ever said:
Just looking at channel log I'm assuming this is still relevant. I'm on V3 and with some frustration (I don't have Wi-Fi and had to trick my 6yr old laptop to boot up) I got it running well.
As someone who has hard bricked smart phones since the xv6800, this is a first good go. Inspires me to start cooking my own roms.
Suggestion: A file browser would have made it so much smoother. No one with half a brain will ***** about es file explorer or root browser being cooked in. Fortunately bad habits inspired me to always backup original stock. Most people would've been screwed there. Dirty flash. Pdanet. Got it all up and going.
Keep up the good work. Look forward to any tweakings you find out of my league
Sincerely,
Satisfied end user
Sent from my HTC Desire 626s using Tapatalk
Click to expand...
Click to collapse
Thank you for the input,much appreciated.also,i updated OP with a newer build that uses nova launcher as default and puts back a few apks that got cutout by mistake.

My phone got simlocked after trying this ROM. It's still locked even after restoring the nanodroid backup I made prior to flasing this ROM.
I'm not in the US sooo I am not using sprint.
Any advice?
Thanks

sgeto said:
My phone got simlocked after trying this ROM. It's still locked even after restoring the nanodroid backup I made prior to flasing this ROM.
I'm not in the US sooo I am not using sprint.
Any advice?
Thanks
Click to expand...
Click to collapse
This ROM is based off of the original Stock MetroPCS USA variant,i didnt add anything that would potentially affect your simlock status.ive only removed stuff that was already there.
If youre not in the US and youre not using MetroPCS Variant of the phone,you shouldnt be flashing this ROM to be 100% honest.flashing incompatable firmwares across devices can sometimes lead to bricks.whats your Carrier and device?

sgeto said:
My phone got simlocked after trying this ROM. It's still locked even after restoring the nanodroid backup I made prior to flasing this ROM.
I'm not in the US sooo I am not using sprint.
Any advice?
Thanks
Click to expand...
Click to collapse
https://www.mediafire.com/?451vq4nmp7paz2a

i2andog said:
https://www.mediafire.com/?451vq4nmp7paz2a
Click to expand...
Click to collapse
That APK will just crash,as the required lib files etc to accompany the APK are missing.

GotHeart said:
This ROM is based off of the original Stock MetroPCS USA variant,i didnt add anything that would potentially affect your simlock status.ive only removed stuff that was already there.
If youre not in the US and youre not using MetroPCS Variant of the phone,you shouldnt be flashing this ROM to be 100% honest.flashing incompatable firmwares across devices can sometimes lead to bricks.whats your Carrier and device?
Click to expand...
Click to collapse
I agree. It's very unusual.
I got this phone from a local phone shop. The owner seem to have unlocked the phone with some kind of service. I contacted my carrier who wrote down a couple of numbers from inside the phone (including the original phone number) and boom, I was able to use the phone with my number.
I have a theory about the error. Maybe you could see if that makes sense:
Maybe the phone isn't locked. But after a factory reset it keeps trying to "activate" the phone using the methods given by sprint.
There's this one step during the initial setup (right after factory resetting the phone) where it tries to register the phone, and fails. This step takes at least tem minutes and returns an error that locks up the phone.
I think the phone assumes that it's locked because it's not able to "reach" sprint servers and denies all incoming and outgoing calls/messages because of this.
If you know a way out of this please let me know.
Another user also provided me with an app that seems to be solving the issue. But it's not marshmallow compatible. Any ideas on that one as well?
Thanks a lot. And great debloating work you did there
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
GotHeart said:
That APK will just crash,as the required lib files etc to accompany the APK are missing.
Click to expand...
Click to collapse
Please tell me more about this app. Cam it solve my issue?
Thx

sgeto said:
I agree. It's very unusual.
I got this phone from a local phone shop. The owner seem to have unlocked the phone with some kind of service. I contacted my carrier who wrote down a couple of numbers from inside the phone (including the original phone number) and boom, I was able to use the phone with my number.
I have a theory about the error. Maybe you could see if that makes sense:
Maybe the phone isn't locked. But after a factory reset it keeps trying to "activate" the phone using the methods given by sprint.
There's this one step during the initial setup (right after factory resetting the phone) where it tries to register the phone, and fails. This step takes at least tem minutes and returns an error that locks up the phone.
I think the phone assumes that it's locked because it's not able to "reach" sprint servers and denies all incoming and outgoing calls/messages because of this.
If you know a way out of this please let me know.
Another user also provided me with an app that seems to be solving the issue. But it's not marshmallow compatible. Any ideas on that one as well?
Thanks a lot. And great debloating work you did there
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
Please tell me more about this app. Cam it solve my issue?
Thx
Click to expand...
Click to collapse
Again,what is your Carrier?if youre using anything other than MetroPCS USA,you should not use this ROM.thats #1.#2 is if youre using sprint,you should get the RUU to return the phone to factory software,and i assume youre using sprint because our Metro devices havent gotten MM yet,and you mentioned it.
And yes,CDMA/Sprint phones will not work correctly if theyre not provisioned from the carrier correctly.so if the activation is failing,then youre not going to be able to use the device to send messages etc until its activated correctly.
Suggestion,try using nightbreeds MM ROM thats for those kinds of carriers.

GotHeart said:
Again,what is your Carrier?if youre using anything other than MetroPCS USA,you should not use this ROM.thats #1.#2 is if youre using sprint,you should get the RUU to return the phone to factory software,and i assume youre using sprint because our Metro devices havent gotten MM yet,and you mentioned it.
And yes,CDMA/Sprint phones will not work correctly if theyre not provisioned from the carrier correctly.so if the activation is failing,then youre not going to be able to use the device to send messages etc until its activated correctly.
Suggestion,try using nightbreeds MM ROM thats for those kinds of carriers.
Click to expand...
Click to collapse
Oh lesson learned. I'm from Yemen and my carrier is YemenMobile (CDMA). I don't know why but I assumed that the phone won't mind the ROM since it was kinda unlocked. SORRY.
The phone was saying Sprint when I bought it. I think I'm going to get back to factory and see if that does the trick. :-/
My extended apologies

How to root Pixel / XL on 7.1?

I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.

sturmeh said:
I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.
Click to expand...
Click to collapse
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220

mattzeller said:
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220
Click to expand...
Click to collapse
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.

sturmeh said:
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.
Click to expand...
Click to collapse
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out

eatsleep said:
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out
Click to expand...
Click to collapse
Buy it directly from Google and the bootloader won't be locked, only if you buy it through a carrier like Verizon will the bootloader be locked
Sent from my SCH-R220

This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.

Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done

fkofilee said:
Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done
Click to expand...
Click to collapse
The worst possible thing you could write...

ldeveraux said:
The worst possible thing you could write...
Click to expand...
Click to collapse
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it

fkofilee said:
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it
Click to expand...
Click to collapse
If your intent was truly altruistic, you wouldn't feel the "burden" of stating it publicly. So no, it doesn't matter.

Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Confirmation number: 57C48888US937054E

Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Appreciate all you do Chainfire, seriously. Can't wait for you to work your magic

Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.

Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...

hutzdani said:
Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.
Click to expand...
Click to collapse
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Ker~Man said:
Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...
Click to expand...
Click to collapse
Totally agree. Thanks for speaking up!

Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Sent from my Pixel XL using Tapatalk

tveith said:
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Totally agree. Thanks for speaking up!
Click to expand...
Click to collapse
What ever but tour the same guys who's going to be asking for OTAs and asking devs to do this that and the other as fast as humanly possible.
If you want it that bad do it your self or sit and wait like a good little child.
No dev is going to rush something because of some people in a forum get a grip, like I said it's their time and it will be ready when it's ready.
You might think I'm going off on one but read the rules page for Christ's sakes.

sionicion said:
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Click to expand...
Click to collapse
The chance you'll have to erase is always present when rooting. Even when your device is fully prepared something may go wrong. At least you have already unlocked your bootloader, which reduces that chance.
File-based encryption will probably not be a reason to for wiping, though. It works fine in the dev version of SuperSU with Android 7.0 on a 5X.

Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app

mrnovanova said:
Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks interesting, but without twrp you sure are taking a big chance if something goes wrong.
Sent from my Pixel using Tapatalk