Does PAC man rom work with safestrap? - Moto X Q&A

I would ask in the thread but I don't have enough posts to ask in there. I have the verizon version, by the way.

Polasja said:
I would ask in the thread but I don't have enough posts to ask in there. I have the verizon version, by the way.
Click to expand...
Click to collapse
Not sure what you mean by that.
And no, PAC works on unlocked BLs only. Unless someone makes it SS compatible

Well ****. I can't unlock my bootloader, unfortunately. Do you think that motorola will allow all phones to unlock the bootloader later on?

Polasja said:
Well ****. I can't unlock my bootloader, unfortunately. Do you think that motorola will allow all phones to unlock the bootloader later on?
Click to expand...
Click to collapse
Unfortunately, its not up to Motorola alone. BL unlock has to be granted by the carrier too. And I dont see VZ doing it anytime soon. Then again, with the Moto X, it doesnt matter all that much. You loose stuff like Active Notification and Touchless Control when you flash AOSP. So, not sure why anyone would want that. Some of the customization that ROMs offer can be had through XPosed Framework.
Someone please feel to correct me if I am wrong.

That would make sense as to why the bootloader hasn't been unlocked yet. I am not really familiar with how all of this stuff works. One of the main reasons why I root my phone is so I can mess with the kernels and achieve better battery life and performance, but I can see why people wouldn't want to switch to AOSP or AOKP because of that Active Notification. Thanks for the helpful information and the quick replies.

Related

T-Mobile c6606 owners

We need a dev to figure out how to unlock our bootloaders!!! I know its possible but I dont have the knowledge or the tools to get it done, but I know there is someone out there that does. We need to find that person
I also read that you will lost Bravia Engine 2 and void warranty.
yes, but you could always just relock. i mean isnt that what android is all about... customization and options
skinsfanbdh said:
We need a dev to figure out how to unlock our bootloaders!!! I know its possible but I dont have the knowledge or the tools to get it done, but I know there is someone out there that does. We need to find that person
Click to expand...
Click to collapse
Its still early days. I think its only a matter of time before someone figures this out :beer:

[Q] Enable root & free tether on VZW Dev Ed?

I've got the phone on the way, would like to figure out what I need to do ahead of time. I would rather not add a custom ROM if I don't need to, wouldn't even mind keeping the stock recovery.
Can I simply run an .apk to get root, or do I need to do something fancy? Please let me know. I've looked around quite a bit and haven't found many resources for DevEd phones.
Dev Ed >= Consumer Ed. If it works on the consumer edition it will work on the dev edition. You ought to be able to figure the rest out on your own.
Sent from my Moto X.
mentose457 said:
Dev Ed >= Consumer Ed. If it works on the consumer edition it will work on the dev edition. You ought to be able to figure the rest out on your own.
Sent from my Moto X.
Click to expand...
Click to collapse
Well I've been reading quite a few people having difficulty getting tether on their VZW Moto X's. Hence the question.
Dude you have the Dev edition so you can do anything. It's just like a nexus. I've got the vzw dev edition too. I unlocked through the website, used fastboot to flash twrp by dhacker, look for the thread in development, then flash a rom. I flashed the T-Mobile updated camera rom, and upon booting any rom, twrp will ask if you want su and install it for you, then i slapped the vzw build.prop on top, and then in every boot I have to use an app called 4g LTE switch to get to phone info so I can change to lte/CDMA auto (prl) so that the phone can still get phone calls and txts over CDMA. This way you can get quicker updates than Verizon and you have native free tethering and don't have to worry about what you're worried about. Just freeze the motorolaOTA app so u don't get the wrong update trying to install and mess up ur phone. There's also a rom with verizons latest update which is the same as the tmobile one only with verizons bloatware. You can run that too without having to mess with the build.prop or network setting. Check the threads in android development and check p3's Google+. He has a lot of good info too.
I use xposed and gravitybox for all my mods. I did not like motoxposed at all compared to gravitybox. Just search for gravitybox on xda as its not in the moto x section but works perfect
Mercutio5 said:
Well I've been reading quite a few people having difficulty getting tether on their VZW Moto X's. Hence the question.
Click to expand...
Click to collapse
The threads about tethering you posted about, that's where you should have posted the original question.
Sent from my Moto X.
jimmypop13 said:
Dude you have the Dev edition so you can do anything. It's just like a nexus. I've got the vzw dev edition too. I unlocked through the website, used fastboot to flash twrp by dhacker, look for the thread in development, then flash a rom. I flashed the T-Mobile updated camera rom, and upon booting any rom, twrp will ask if you want su and install it for you, then i slapped the vzw build.prop on top, and then in every boot I have to use an app called 4g LTE switch to get to phone info so I can change to lte/CDMA auto (prl) so that the phone can still get phone calls and txts over CDMA. This way you can get quicker updates than Verizon and you have native free tethering and don't have to worry about what you're worried about. Just freeze the motorolaOTA app so u don't get the wrong update trying to install and mess up ur phone. There's also a rom with verizons latest update which is the same as the tmobile one only with verizons bloatware. You can run that too without having to mess with the build.prop or network setting. Check the threads in android development and check p3's Google+. He has a lot of good info too.
I use xposed and gravitybox for all my mods. I did not like motoxposed at all compared to gravitybox. Just search for gravitybox on xda as its not in the moto x section but works perfect
Click to expand...
Click to collapse
That is extremely reassuring and informative. Thank you! So looking forward to this phone, it just looks beautiful.
Mercutio5 said:
I've got the phone on the way, would like to figure out what I need to do ahead of time. I would rather not add a custom ROM if I don't need to, wouldn't even mind keeping the stock recovery.
Can I simply run an .apk to get root, or do I need to do something fancy? Please let me know. I've looked around quite a bit and haven't found many resources for DevEd phones.
Click to expand...
Click to collapse
I have a VZW Developer Edition. This works great for me.

[SOLVED] Installing a custom ROM on Xperia Z1 using XZDualRecovery

Hello guys. I'm new to the community, but I did my homework and I can honestly say I've spent a good +40 hours on this site in the past month, and it paid off since I'm now the proud owner of a rooted Xperia Z1 running 4.4.2 KitKat with XZdualrecovery which is something I tought I would never do out of fear of bricking my device and the lack of information and support for my rather "slightly rare" C6906 model with annoyances like a non-unlockable bootloader , where the C6903 and C6902 models get all the attention. Anyway guys, I rooted my phone, awesome...but for me, the next step is installing a custom rom, because I feel that the stock xperia Z1 firmware is not enough for my customizing needs, plus I also envy the stock like experience it provides, even more than my Z1. I read up on a few guides for installing cyanogenmod on the Z1, but they all seem to be only supported for the C6903 and C6902 models. Plus, it doesn't help to motivate myself knowing that my C6906 model still has a locked bootloader (apparently) and I've read unlocking the bootloader is a requirement for installing custom ROMs. So, my questions are:
Is XZDualRecovery enough to install custom ROMs? Specially the version with the locked bootloader? Could I run into any issues?
If the answer to the previous question is yes, Are there any good guides concerning the C6906 model on how to install custom roms? (Or more importantly, cyanogenmod? [preferably versions that have been tested on the C6906])
You cannot install anything like Cyanogenmod as it needs an unlocked bootloader
You can install any rom from the development section, just follow the locked bootloader instructions
Now that you have recovery, make a backup and follow the instructions in the thread.
Thanks!
gregbradley said:
You cannot install anything like Cyanogenmod as it needs an unlocked bootloader
You can install any rom from the development section, just follow the locked bootloader instructions
Now that you have recovery, make a backup and follow the instructions in the thread.
Click to expand...
Click to collapse
Thank you! You saved me a lot of time so I can stop searching for a way to install CM. I will look into the development section them. Any recommendations on what's a good/stable/popular ROM I can install then?
sarxion said:
Thank you! You saved me a lot of time so I can stop searching for a way to install CM. I will look into the development section them. Any recommendations on what's a good/stable/popular ROM I can install then?
Click to expand...
Click to collapse
No, and xda mods don't like that question being asked. Best ROM and asking for best ROM threads get closed quickly. Here is why..
If you ask someone which pizza they should buy then people give their own favourites as a recommendation. I like hot, spicy and meaty ones, but if recommend that to you may say "That's disgusting!" you may be one of those people who like anchovies and sweetcorn on their pizza. That may be perfect for you, but I will hate it
In short, you have to try them yourself and see which one suits you best. One bit of advice though, even if someone recommends a ROM to you, its no guarantee you will like it.
Part of the appeal of android is that we can customise so much, so try, test for a week (It takes that long to get an idea of performance and battery) then move on and try another.
Once you have done that, flash your favourite.
gregbradley said:
No, and xda mods don't like that question being asked. Best ROM and asking for best ROM threads get closed quickly. Here is why..
If you ask someone which pizza they should buy then people give their own favourites as a recommendation. I like hot, spicy and meaty ones, but if recommend that to you may say "That's disgusting!" you may be one of those people who like anchovies and sweetcorn on their pizza. That may be perfect for you, but I will hate it
In short, you have to try them yourself and see which one suits you best. One bit of advice though, even if someone recommends a ROM to you, its no guarantee you will like it.
Part of the appeal of android is that we can customise so much, so try, test for a week (It takes that long to get an idea of performance and battery) then move on and try another.
Once you have done that, flash your favourite.
Click to expand...
Click to collapse
Oh ok...sorry, didn't know that...So, should I close this thread then? or is there a way to mark my questions as answered?
sarxion said:
Oh ok...sorry, didn't know that...So, should I close this thread then? or is there a way to mark my questions as answered?
Click to expand...
Click to collapse
click on edit in your first post, then click on advanced
Change the title to say
[Solved] at the front of it

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

vzw g950u roms

I hate to sound so new build asking this question but with all the variants and threads kind of combining I'm a little confused. I'm not new to xda or rooting or installing ROMs to Samsung devices and have searched but am not getting quite the confirmation I'm looking for.
I see that anyone with the g950u can get root now and that's awesome but are ROMs device specific between all the different variants? I see there is atleast one room that's says g950u in the title of the thread can anyone clear this up for me please?
goddi2010 said:
I hate to sound so new build asking this question but with all the variants and threads kind of combining I'm a little confused. I'm not new to xda or rooting or installing ROMs to Samsung devices and have searched but am not getting quite the confirmation I'm looking for.
I see that anyone with the g950u can get root now and that's awesome but are ROMs device specific between all the different variants? I see there is atleast one room that's says g950u in the title of the thread can anyone clear this up for me please?
Click to expand...
Click to collapse
The U.S. devices (g950u) still have a locked bootloader - the first piece of software executed when you power on. Being locked means that it (the CPU) is looking for a specific key (the public signature) embedded in that code before it continues loading the code _ one that only Samsung/Verizon has authorized. To change that public signature yourself, you need the other half of the key (the private key) and that is akin to asking Samsung for all its source code to every device it makes -- never going to happen!
It will only continue the boot process if the signatures match for the next part (basically the ROM) of the code. A custom ROM won't match that signature, so the bootloader won't execute the ROM code. Having 'root' means you have control over everything software related in the ROM *after* it is booted into the ROM - meaning you're already past the whole signature part.
Unless someone finds a backdoor or security flaw that can be exploited on the bootloader (unlikely), or Samsung (or more likely Verizon) gives us a program to unlock the bootloader (even less of a chance), we won't be seeing any ROMs for the g950u. So, do like I did and shut off all the Samsung gunk (I use all of Google's apps because they behave the same way on every device I own - I can't stand Samsung apps or TouchWiz!) that you can, load Nova and set it up to behave the way YOU want it to work. Then just enjoy what you have!
Thank you for your answer I will root and try to make it more like Google
Great post rhricik! Best explanation I've heard in a while.
From what rhricik posted, it sounds like one can't root because the bootloader is locked in the Verizon version?
Are the bootloaders locked on the AT&T and T-Mobile versions?
charter3554 said:
Great post rhricik! Best explanation I've heard in a while.
From what rhricik posted, it sounds like one can't root because the bootloader is locked in the Verizon version?
Are the bootloaders locked on the AT&T and T-Mobile versions?
Click to expand...
Click to collapse
Yes, all US variants have a locked bootloader.
charter3554 said:
Great post rhricik! Best explanation I've heard in a while.
From what rhricik posted, it sounds like one can't root because the bootloader is locked in the Verizon version?
Are the bootloaders locked on the AT&T and T-Mobile versions?
Click to expand...
Click to collapse
All snapdragons are bootloader locked. Except the Chinese model
goddi2010 said:
I hate to sound so new build asking this question but with all the variants and threads kind of combining I'm a little confused. I'm not new to xda or rooting or installing ROMs to Samsung devices and have searched but am not getting quite the confirmation I'm looking for.
I see that anyone with the g950u can get root now and that's awesome but are ROMs device specific between all the different variants? I see there is atleast one room that's says g950u in the title of the thread can anyone clear this up for me please?[/QUOT
Click to expand...
Click to collapse
goddi2010 said:
I hate to sound so new build asking this question but with all the variants and threads kind of combining I'm a little confused. I'm not new to xda or rooting or installing ROMs to Samsung devices and have searched but am not getting quite the confirmation I'm looking for.
I see that anyone with the g950u can get root now and that's awesome but are ROMs device specific between all the different variants? I see there is atleast one room that's says g950u in the title of the thread can anyone clear this up for me please?
Click to expand...
Click to collapse
goddi2010 said:
Thank you for your answer I will root and try to make it more like Google
Click to expand...
Click to collapse
Cyclone Emperor said:
Yes, all US variants have a locked bootloader.
Click to expand...
Click to collapse
TheMadScientist said:
All snapdragons are bootloader locked. Except the Chinese model
Click to expand...
Click to collapse
dfoley45066 said:
goddi2010 said:
I hate to sound so new build asking this question but with all the variants and threads kind of combining I'm a little confused. I'm not new to xda or rooting or installing ROMs to Samsung devices and have searched but am not getting quite the confirmation I'm looking for.
I see that anyone with the g950u can get root now and that's awesome but are ROMs device specific between all the different variants? I see there is atleast one room that's says g950u in the title of the thread can anyone clear this up for me please?[/QUOT
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Categories

Resources