Related
Let me explain: So I got the OTA overnight, and when I woke up (to my alarm clock) I accidentally accepted the update. I had planned to root my phone and looked into keeping root through the OTA. I postponed it for the last two days, trying to figure out how to root/keep root through OTA. I've been busy with work and had to put it aside until I had a day off. To get to my question, am I screwed or will there be a way to root this phone after the update? This is my first Motorola phone, so pardon me if this is a dumb question. Thanks for any and all comments.
Sent from my XT1060 using xda app -developers app
pborner said:
Let me explain: So I got the OTA overnight, and when I woke up (to my alarm clock) I accidentally accepted the update. I had planned to root my phone and looked into keeping root through the OTA. I postponed it for the last two days, trying to figure out how to root/keep root through OTA. I've been busy with work and had to put it aside until I had a day off. To get to my question, am I screwed or will there be a way to root this phone after the update? This is my first Motorola phone, so pardon me if this is a dumb question. Thanks for any and all comments.
Sent from my XT1060 using xda app -developers app
Click to expand...
Click to collapse
screwed for the time being. jcase already verified there's other ways to root the update but won't release them yet. in due time I'm sure someone will release something. I'm patiently waiting too.. bought a used moto x with the update already applied. sucks.
If its still within the return time, shoot compressed air in the ear piece and speakers. It'll screw it up, take it in and get a replacement. Then don't screw up the next time around.
gokart2 said:
If its still within the return time, shoot compressed air in the ear piece and speakers. It'll screw it up, take it in and get a replacement. Then don't screw up the next time around.
Click to expand...
Click to collapse
Um... As much as I'm in favor of screwing Verizon (and all other multi-national corporations), why not just search the threads for how to use RSDLite to reflash the original stock firmware, then don't accept the OTA until you've waded through the process for keeping root? Or, you can destroy a perfectly good piece of technology for no reason.
hazenberger said:
Um... As much as I'm in favor of screwing Verizon (and all other multi-national corporations), why not just search the threads for how to use RSDLite to reflash the original stock firmware, then don't accept the OTA until you've waded through the process for keeping root? Or, you can destroy a perfectly good piece of technology for no reason.
Click to expand...
Click to collapse
You cannot downgrade firmware.
mandrsn1 said:
You cannot downgrade firmware.
Click to expand...
Click to collapse
I'm pretty sure you can:
http://forum.xda-developers.com/showthread.php?t=2446515
hazenberger said:
I'm pretty sure you can:
http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
Nope. When you bootloader updates as part of the camera update, it prevents firmware downgrades. That link is just for restoring to stock if you haven't updated.
mandrsn1 said:
Nope. When you bootloader updates as part of the camera update, it prevents firmware downgrades. That link is just for restoring to stock if you haven't updated.
Click to expand...
Click to collapse
Sorry. You're right.
So go ahead and screw Verizon using the air trick. Or wait until someone finds a new root exploit for this firmware.
hazenberger said:
Sorry. You're right.
So go ahead and screw Verizon using the air trick. Or wait until someone finds a new root exploit for this firmware.
Click to expand...
Click to collapse
There are other known, but unreleased, root exploits. They aren't going to be released until another major firmware upgrade (e.g., 4.4).
Thanks for the heads up guys. Not really in favor of the air method. There's nothing wrong with this phone unrooted, actually the first phone I can say that about. Just wanna tweak some things, preferably a CM MOD. Will wait for a new method.
Sent from my XT1060 using xda app-developers app
pborner said:
Thanks for the heads up guys. Not really in favor of the air method. There's nothing wrong with this phone unrooted, actually the first phone I can say that about. Just wanna tweak some things, preferably a CM MOD. Will wait for a new method.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
if you are on verizon and you go to a verizon store, they are typically pretty nice there. Basically, you could walk in say that you accidentally took the OTA and you wanted to root so can give you me a new one. They will probably say yes. Or you can just say your battery drain is really bad and you have spent hours trying to fix it but people on forums said you needed to return it. The guy at my store doesn't even ask or look at my phone anymore if i bring it in...
mandrsn1 said:
There are other known, but unreleased, root exploits. They aren't going to be released until another major firmware upgrade (e.g., 4.4).
Click to expand...
Click to collapse
This is good to hear... Do you happen to know if there's been any solid progress made on a bootloader unlock for Verizon? I wish I knew the first thing about Android programming so I could help out in this effort. I love my Moto X as is, but would love to see permanent root methods so we could have access to custom kernels (and so I can try to get rid of the damn NLP wakelocks).
I tried all known methods for rooting but all failed.
Even when you unlock it there is still no TWRP available for the 701.
I asked the devs of twrp on their website to take a look at the 701.
If anyone has more knowledge about progress made on this subject please react here.
Sent from my superfast Asus Infinity TF701with Dock
Knock it Off Please
Ok, forum just opened and;
1. Posted in the development forum instead of General or Q & A (shame shame)
2. Flaming already starts
Knock it off people. Jeeze..... Things will come in good time. Unless of course you want to rush things and brick yer tabs
Keep it clean people.
MD
Now, if you have fastboot OEM unlock,
,
Then perhaps you can pull your boot.img, separate zImage from Ramdisk, modify ro.secure=0, add RW comments, repack your boot.img, fastboot flash boot boot.img, then install BB and SU.
Just a thought.
MD
Moscow Desire said:
Now, if you have fastboot OEM unlock,
,
Then perhaps you can pull your boot.img, separate zImage from Ramdisk, modify ro.secure=0, add RW comments, repack your boot.img, fastboot flash boot boot.img, then install BB and SU.
Just a thought.
MD
Click to expand...
Click to collapse
Sad part the "Fastboot OEM unlock" won't work cause Asus has theirs encrypted. You have to use their unlocking tool to unlock your bootloader. Given fact it can work, been trying it for 2 days now and stupid app won't unlock my bootloader. Read my S/N may not be registered in their database so emailed them complaining about another service that doesn't work.
Tiger62651 said:
Sad part the "Fastboot OEM unlock" won't work cause Asus has theirs encrypted. You have to use their unlocking tool to unlock your bootloader. Given fact it can work, been trying it for 2 days now and stupid app won't unlock my bootloader. Read my S/N may not be registered in their database so emailed them complaining about another service that doesn't work.
Click to expand...
Click to collapse
They'll get around to it. Heck, when I had to turn in my A701 to service center, they didn't even know it had been released Tried telling me it was a "leaked and illegal" tablet.
Good luck with the bootloader mate, but root after that should be pretty straight forward. (fingers crossed)
I think that unlocking bootloader is bad idea. After that the warranty will be void...
Moscow Desire said:
They'll get around to it. Heck, when I had to turn in my A701 to service center, they didn't even know it had been released Tried telling me it was a "leaked and illegal" tablet.
Good luck with the bootloader mate, but root after that should be pretty straight forward. (fingers crossed)
Click to expand...
Click to collapse
Yeah well tried to call them and got the usual "just send it back" well not waiting 2-3 weeks just get to get it back. Since there is something wrong with the charge port anyways just gonna send it back to amazon to have new one in couple days. Gotta love the return policy.
HaPe000 said:
I think that unlocking bootloader is bad idea. After that the warranty will be void...
Click to expand...
Click to collapse
Um thats just lame excuse from companies to force us to keep their crap on the devices we purchase. All my devices are rooted and unlocked and not one has died yet. After going through and disabling 2/3rds of crap on this tablet now I want that few hundred megabytes back in space. For as much crap I disabled I wouldn't be surprised im more close to 1gb back.
Moscow Desire said:
They'll get around to it. Heck, when I had to turn in my A701 to service center, they didn't even know it had been released Tried telling me it was a "leaked and illegal" tablet.
Good luck with the bootloader mate, but root after that should be pretty straight forward. (fingers crossed)
Click to expand...
Click to collapse
What a morons sometimes. Strange because I had the issue with the connection between dock and tablet where the connection between the 2 for a split moment was gone when adjusting the tilt angle, I got an immediate replacement. This problem I guarantee you we will see more often showing up here.
And what the rooting concerns: when the TWRP devs have their version for the 701 finished, it will be not that hard anymore. Just takes some time before that is done.
And for the flaming thing sorry, but I don't like to get hit by childish behavior when just reporting and next to that by a guy that is probably half my age and just comes looking in here (look @ date I joined xda lol)
Thanks for removing that post.
Snah001 said:
What a morons sometimes. Strange because I had the issue with the connection between dock and tablet where the connection between the 2 for a split moment was gone when adjusting the tilt angle, I got an immediate replacement. This problem I guarantee you we will see more often showing up here.
And what the rooting concerns: when the TWRP devs have their version for the 701 finished, it will be not that hard anymore. Just takes some time before that is done.
And for the flaming thing sorry, but I don't like to get hit by childish behavior when just reporting and next to that by a guy that is probably half my age and just comes looking in here (look @ date I joined xda lol)
Thanks for removing that post.
Click to expand...
Click to collapse
Hate returns. Took 3 months to get a refund. (welcome to Russia). Honestly, it was all due to rush jobs on CWM for the 510 and 700's. Bozos were in a rush to be the first, and used the "fstab's" from the wrong device. Bricked several tabs before I put a stop to it. Basically ruined the emmc memory. Mainboard replacements.
Well, I know folks are itchy to get things going. What starts as a joke, turns into flaming.
You folks always remember, takes 2 people for an argument. You all have the "Report Post" button on the toolbar. Please use it.
Honestly, I expect you folks to help each other out. Makes for a better forum.
Carry On!
MD
Snah001 said:
What a morons sometimes. Strange because I had the issue with the connection between dock and tablet where the connection between the 2 for a split moment was gone when adjusting the tilt angle, I got an immediate replacement. This problem I guarantee you we will see more often showing up here.
And what the rooting concerns: when the TWRP devs have their version for the 701 finished, it will be not that hard anymore. Just takes some time before that is done.
And for the flaming thing sorry, but I don't like to get hit by childish behavior when just reporting and next to that by a guy that is probably half my age and just comes looking in here (look @ date I joined xda lol)
Thanks for removing that post.
Click to expand...
Click to collapse
well next time you may want to think twice before asuming someone younger than you. guess i am to young to know where the movie that reference came from. i already have the boot.img altered and ready to try. also dont ask for it, havent tested it yet so going to have to wait till amazon gives me new one. it really isnt hard to alter, moscow already gave instructions.
Update Amazon has shipped my new tablet so may be here tomorrow (i hope) if my new boot.img works and gives me root then I will pass it on, sadly though it won't be in a format in which you can just use a custom recovery, you have to flash it manually but if it works I will post how to flash it (all i need to remember is which tools to zip up in the entire SDK) LOL.
Interesting discussion..
Sent from my New Asus Transformer Pad TF701T using Tapatalk HD
Tiger62651 said:
Um thats just lame excuse from companies to force us to keep their crap on the devices we purchase. All my devices are rooted and unlocked and not one has died yet. After going through and disabling 2/3rds of crap on this tablet now I want that few hundred megabytes back in space. For as much crap I disabled I wouldn't be surprised im more close to 1gb back.
Click to expand...
Click to collapse
It is VERY lame. I sold my TF700 because of the slow I/O causing lag that I couldn't live with. Of course I had the bootloader unlocked, so the warranty was void. I divulged that info in the eBay auction for the most part (I didn't say the warranty was void because I didn't know that was the case. Ignorant, I know). Anyway, the new owner of my TF700 emailed me after a couple months asking me why ASUS was charging them $280 for fixing the faulty touchscreen. They said ASUS says it's not under warranty because of the unlocked bootloader. I felt bad for the new owners, having to fork out the money. They're $800 into the TF700 w/dock at this point.
So I would say: Think twice before unlocking the bootloader on the TF701, when custom-recovery even comes out for it.
Personally, with my TF701 that I ordered on newgg today, I am going to leave the bootloader locked for awhile. I can live with the stock ROM, hopefully with root access. Maybe after a few months I'll unlock the bootloader. It would be nice to do it in a way that didn't void the warranty. What an asinine policy by ASUS. There is no way the unlocked bootloader led to the touchscreen failing on my old TF700....no way!
snake2332 said:
It is VERY lame. I sold my TF700 because of the slow I/O causing lag that I couldn't live with. Of course I had the bootloader unlocked, so the warranty was void. I divulged that info in the eBay auction for the most part (I didn't say the warranty was void because I didn't know that was the case. Ignorant, I know). Anyway, the new owner of my TF700 emailed me after a couple months asking me why ASUS was charging them $280 for fixing the faulty touchscreen. They said ASUS says it's not under warranty because of the unlocked bootloader. I felt bad for the new owners, having to fork out the money. They're $800 into the TF700 w/dock at this point.
So I would say: Think twice before unlocking the bootloader on the TF701, when custom-recovery even comes out for it.
Personally, with my TF701 that I ordered on newgg today, I am going to leave the bootloader locked for awhile. I can live with the stock ROM, hopefully with root access. Maybe after a few months I'll unlock the bootloader. It would be nice to do it in a way that didn't void the warranty. What an asinine policy by ASUS. There is no way the unlocked bootloader led to the touchscreen failing on my old TF700....no way!
Click to expand...
Click to collapse
Gee thanks for the advice. Lets just say for practicality so you know when I got my Xoom 2 days later I rooted it. Couple years later works fine just slow now so time for new one. I have 701 right now and its blazing fast.
2nd let me shine some advise for you. For starters you can't "root" a device with a locked bootloader. Requires altering the boot.img to tell system to boot up differently and allow you access to the "restricted" file system. To access the flash portion of that requires you to open it up. One way or another you will have to unlock the bootloader to root the device. I myself just want root, I want to just remove the unwanted junk and free up that wasted space and install ad blocking software.
What each person chooses to do with the root is up to them, regardless if Asus wants to void the warranty or not. Just need little common sense and know how to use google to figure what you want to do. If your to cautious to do that then I highly suggest not touching it and leave it as is. To me its never a "think twice" once you root and have full access to the product you bought, it makes the device so much better to use and gets rid of unwanted bloatware. Especially the ad blocking apps which helps on phone contracts with capped data helps keep your data way down since ads use a lot of data.
Tiger62651 said:
2nd let me shine some advise for you. For starters you can't "root" a device with a locked bootloader. Requires altering the boot.img to tell system to boot up differently and allow you access to the "restricted" file system. To access the flash portion of that requires you to open it up. One way or another you will have to unlock the bootloader to root the device. I myself just want root, I want to just remove the unwanted junk and free up that wasted space and install ad blocking software.
Click to expand...
Click to collapse
Your statements sound completely wrong to me. Of course you can root without unlocking the bootloader. I have rooted two phones and my TF201, all without unlocking; I rooted the TF201 soon after buying it, and only unlocked the bootloader more than a year later.
Rooting doesn't force you to forfeit warranty service, but unlocking does. (Note that you can unroot a device before sending it in for service, but you can't "relock" an unlocked device.) So it makes perfect sense as Snake suggests to hold off on unlocking, at least until you are sure all the hardware in your device is working perfectly.
Tiger62651 said:
Update Amazon has shipped my new tablet so may be here tomorrow (i hope) if my new boot.img works and gives me root then I will pass it on, sadly though it won't be in a format in which you can just use a custom recovery, you have to flash it manually but if it works I will post how to flash it (all i need to remember is which tools to zip up in the entire SDK) LOL.
Click to expand...
Click to collapse
You can use a windows app called Virtuous Ten Studio (created by Diamondback ) Senior Mod and RD. It'll unpack your boot.img to allow editing ramdisk. Heck, it'll also de-odex, decompile apks with built in support for most API levels in a windows UI. No need to mess with apktools and such.
Free version in the XDA forums. Think you have to install latest MS .Net though. Can't remember. Give it a go. If you're a ROM cooker, it's a must.
An unlocked bootloader is usually 90% of the battle when getting full root (full means system RW access). Locked bootloaders is why rooting can involve finding exploits, which is why so many root apps are out there. Not saying what worked on the Acer 500/501, 510/511 and 700/701 tabs will work for the TF701, but it's worth investigating.
Moscow Desire said:
You can use a windows app called Virtuous Ten Studio (created by Diamondback ) Senior Mod and RD. It'll unpack your boot.img to allow editing ramdisk. Heck, it'll also de-odex, decompile apks with built in support for most API levels in a windows UI. No need to mess with apktools and such.
Free version in the XDA forums. Think you have to install latest MS .Net though. Can't remember. Give it a go. If you're a ROM cooker, it's a must.
An unlocked bootloader is usually 90% of the battle when getting full root (full means system RW access). Locked bootloaders is why rooting can involve finding exploits, which is why so many root apps are out there. Not saying what worked on the Acer 500/501, 510/511 and 700/701 tabs will work for the TF701, but it's worth investigating.
Click to expand...
Click to collapse
Thanks for the windows tip but I use VMware with Ubuntu installed and have my harddrive mapped as network drive to transfer files between. Much easier this way. I will check out the program though may need it for some APK altering of certain app (I hope).
Tiger62651 said:
Thanks for the windows tip but I use VMware with Ubuntu installed and have my harddrive mapped as network drive to transfer files between. Much easier this way. I will check out the program though may need it for some APK altering of certain app (I hope).
Click to expand...
Click to collapse
Ha, I use a dual boot (win7 and Ubuntu). Old lappy didn't run too well with VM. Need any help, shoot me a PM. Will share what I know.
There's a few other things you can do im Ramdisk, like increase read ahead cache, run a service to update lto.dat automatically (GPS) and a few others.
I only boot to win7 when I want to unpack/repack and boot images when I do kernel builds. (I'm lazy)
MD
Moscow Desire said:
Ha, I use a dual boot (win7 and Ubuntu). Old lappy didn't run too well with VM. Need any help, shoot me a PM. Will share what I know.
There's a few other things you can do im Ramdisk, like increase read ahead cache, run a service to update lto.dat automatically (GPS) and a few others.
I only boot to win7 when I want to unpack/repack and boot images when I do kernel builds. (I'm lazy)
MD
Click to expand...
Click to collapse
Yeah that works just pain to have to shut down windows to boot ubuntu. My PC is a power house, set VMware with 4gb of RAM and still not slowing my PC down LOL.
well new tablet in and little troubleshooting seems problem is bad charge cable, new one starts to charge 1/2 way in, other little flaky. but even new tablet fresh out of box wont let me unlock it so asus tw asked for screen shot of my ids, waiting reply.
I'm about to get a Moto X on Tuesday. I wondered if there are any dangers of rooting the device? I am not interested (at least not right now) in running a custom ROM on it since it runs so close to AOSP anyway. But I would like to be able to use Titanium Backup with it and a few other things that require root.
I've read there are ways to do it, just not sure if they are safe or not.
As long as you can read and follow directions, there isn't anything to worry about.
Rooting your device void warranty and can brick your device if you don't follow the directions correctly or if you play with something you don't understand. But if you follow directions then you will be fine with nothing to worry about.
Sent from my XT1056 using XDA Premium 4 mobile app
I was in the same boat, wanting to use root only for TBU, Tasker, and the occasional wifi tether.
Don't be in a rush, the phone works pretty good in stock form. When you're ready, read the forums, follow directions, and you'll be fine. There are a couple threads devoted to the topic, I used Hashcode's TWRP method for unlocked bootloaders without problem (after unlocking which was a little bit of a PITA).
I'm no stranger to rooting and flashing roms. I'll admit to being intimidated a little by the Moto X forum posts since it seems that our phone is a little trickier than what I'm familiar with.
FWIW, battery life on this phone is awesome compared to my Gnex and it seemed to get even better when unlocked and rooted. Also, Xposed is awesome.
Good luck!
The real danger of rooting (other than voiding warranty, etc.) is potential user stupidity.
Root access still requires the user's permission. Whenever root access is requested by an app you will be prompted to grant access. If you get reputable apps from the play store this usually won't be an issue. If you are downloading APKs from less trustworthy sources all bets are off.
Malware often runs without root, and it's usually better this way because requesting root access without an obvious need is a big warning sign.
brian Marshall said:
The real danger of rooting (other than voiding warranty, etc.) is potential user stupidity.
Root access still requires the user's permission. Whenever root access is requested by an app you will be prompted to grant access. If you get reputable apps from the play store this usually won't be an issue. If you are downloading APKs from less trustworthy sources all bets are off.
Malware often runs without root, and it's usually better this way because requesting root access without an obvious need is a big warning sign.
Click to expand...
Click to collapse
I completely agree with this. Personally, I have rooted all of my previous phones (Droid 2, HTC Rezound) but have not done so for this one. With the speed in which updates are released, and the fact that the phone is basically stock Android, I haven't felt the need to root it.
Also, you might find this post by me interesting: How to backup and restore app data without Root. The only real root feature I typically used was for backing up, but Helium + ADB can do all of this for you.
DogzOfWar said:
I completely agree with this. Personally, I have rooted all of my previous phones (Droid 2, HTC Rezound) but have not done so for this one. With the speed in which updates are released, and the fact that the phone is basically stock Android, I haven't felt the need to root it.
Also, you might find this post by me interesting: How to backup and restore app data without Root. The only real root feature I typically used was for backing up, but Helium + ADB can do all of this for you.
Click to expand...
Click to collapse
Yeah, I run LookOut for one but for another I never grant root access unless I specifically want it to DO something that requires it.
DogzOfWar said:
the phone is basically stock Android, I haven't felt the need to root it.
Click to expand...
Click to collapse
Agreed. Occasionally I'll think to my self that I'll get around to rooting it, but honestly I don't feel like I need to.
I kinda want to try out xposed, but there's almost zero motivation otherwise.
Thanks everyone for the replies, I appreciate it.
What are we needing in order to figure out how to unlock or bypass the AT&T Bootloader?
I downloaded the stock files and have the aboot.mbn and the sbl1/sdi.mdn files. I have never worked on bootloader files before, but have some experience modding kernel and ROM level code.
This may be ignorant on my part - but since we have the files, couldn't we open and manipulate the code that is currently restricting 3rd party recoveries, kernels and ROMS?
What is needed? And/or, could we not utilize the modified bootloaders from another device with similar architecture? Perhaps like the Note 3 or even the S4; not to mention the T-Mobile S5? Since the T-Mobile and AT&T versions of all Samsung phones are almost identical, I would assume that would be the easist route - at least to help determine the differences that are restricting our device.....
Let me know if anyone needs these files or has info on what to look for within them.... I'm happy to mod anything on my end.
Thanks !
Because it is locked we can't just flash over it with another one due to signatures and miss match.
Need to research into the os and associated code to find an exploit that can be used like safestrap.
Sent from my SGH-M919 using XDA Premium 4 mobile app
TheArtiszan said:
Because it is locked we can't just flash over it with another one due to signatures and miss match.
Need to research into the os and associated code to find an exploit that can be used like safestrap.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Or if someone that works at AT&T or Samsung would be nice enough to leak a signing key or a signed unlocked bootloader.
Key from Tmobile S5
T-mobile S5 is rooted. Can we find the signing key used for Tmobile phones? Is there is a remote chance keys are same?
Will recoveries on Tmobile and ATT phone be same?
yoonus said:
T-mobile S5 is rooted. Can we find the signing key used for Tmobile phones? Is there is a remote chance keys are same?
Will recoveries on Tmobile and ATT phone be same?
Click to expand...
Click to collapse
Thats a good question. I wonder if we know how many keys the S5 will accept for signed updates? I.e. Is there a Samsung and a AT&T key for all S5's or is it per model or is it derived somehow from the IEMI.
Why would the developers even waste their time on the AT&T S5? They know the story behind it. Same ol' thing. I would rather have them actually develop roms on the T-Mobile S5, which we all can use btw, instead of wasting time on trying to unlock the bootloader. If it could be hacked, it would have, LONG AGO!
yoonus said:
T-mobile S5 is rooted. Can we find the signing key used for Tmobile phones? Is there is a remote chance keys are same?
Will recoveries on Tmobile and ATT phone be same?
Click to expand...
Click to collapse
How would the key used for the G900T be helpful? Its not like the key is on some partition somewhere
MattMJB0188 said:
Why would the developers even waste their time on the AT&T S5? They know the story behind it. Same ol' thing. I would rather have them actually develop roms on the T-Mobile S5, which we all can use btw, instead of wasting time on trying to unlock the bootloader. If it could be hacked, it would have, LONG AGO!
Click to expand...
Click to collapse
Well to be fair, if you took the best developers and hardware/software hackers in the world and put them in a room with an amazing salary.. it would be hacked..
So lets not say that its impossible. It is just extremely difficult and beyond the scope of the few developers (if any) that are still around trying to crack into it. The problem is that there aren't that many people that just want to sit around trying to figure out a way to make it work, they would rather move to different phones and carriers instead, because its just overall easier.
MattMJB0188 said:
Why would the developers even waste their time on the AT&T S5? They know the story behind it. Same ol' thing. I would rather have them actually develop roms on the T-Mobile S5, which we all can use btw, instead of wasting time on trying to unlock the bootloader. If it could be hacked, it would have, LONG AGO!
Click to expand...
Click to collapse
Yep, hate to burst anyone's bubble who has a G900A, but it's not going to happen... EVER. Options are to hold out for a developer edition phone from Samsung or get a T-mobile version... which is exactly the same thing minus the restrictions. Or if you are pissed at AT&T, just find another carrier. Maybe if there was enough churn from this, they would stop doing it.
enigma99a said:
Yep, hate to burst anyone's bubble who has a G900A, but it's not going to happen... EVER. Options are to hold out for a developer edition phone from Samsung or get a T-mobile version... which is exactly the same thing minus the restrictions. Or if you are pissed at AT&T, just find another carrier. Maybe if there was enough churn from this, they would stop doing it.
Click to expand...
Click to collapse
The s5 will get root same as the s4 did. People just need to be patient. There is definitely a dev that is working to unlock this thing. Everyone said the same thing about the s4 and now look
enigma99a said:
Yep, hate to burst anyone's bubble who has a G900A, but it's not going to happen... EVER. Options are to hold out for a developer edition phone from Samsung or get a T-mobile version... which is exactly the same thing minus the restrictions. Or if you are pissed at AT&T, just find another carrier. Maybe if there was enough churn from this, they would stop doing it.
Click to expand...
Click to collapse
People like you make me laugh. Not even 2 weeks after release and you're already declaring the device will NEVER get root. Lol.
karmuh said:
People like you make me laugh. Not even 2 weeks after release and you're already declaring the device will NEVER get root. Lol.
Click to expand...
Click to collapse
Yea I don't think its fair to say it "will never" or "cannot be" done.
PunchLick said:
Yea I don't think its fair to say it "will never" or "cannot be" done.
Click to expand...
Click to collapse
Exactly. It can be done and it will be done. Anyone thinking otherwise is pretty naive. But then again, it's expected from those who don't even have the AT&T model, but continue to post in the AT&T section.
nbrent1007 said:
The s5 will get root same as the s4 did. People just need to be patient. There is definitely a dev that is working to unlock this thing. Everyone said the same thing about the s4 and now look
Click to expand...
Click to collapse
This thread is about the boot loader, not getting root.
---------- Post added at 09:09 PM ---------- Previous post was at 09:04 PM ----------
PunchLick said:
Yea I don't think its fair to say it "will never" or "cannot be" done.
Click to expand...
Click to collapse
No. Again, there is a difference from root and unlocking the bootloader. I was referring to the bootloader as that's what this thread is discussing. I never said it was impossible, it is quite possible just takes a lot of hard work. My prediction is that it will never be fully unlocked.
enigma99a said:
This thread is about the boot loader, not getting root.
---------- Post added at 09:09 PM ---------- Previous post was at 09:04 PM ----------
No. Again, there is a difference from root and unlocking the bootloader. I was referring to the bootloader as that's what this thread is discussing. I never said it was impossible, it is quite possible just takes a lot of hard work. My prediction is that it will never be fully unlocked.
Click to expand...
Click to collapse
I don't want to even have to worry about if it will or not, because I don't know who or how many are working on an exploit..
That's why I am switching to the One M8, but either way if/when something does change I may switch back.. I just would rather have fun now!
PunchLick said:
I don't want to even have to worry about if it will or not, because I don't know who or how many are working on an exploit..
That's why I am switching to the One M8, but either way if/when something does change I may switch back.. I just would rather have fun now!
Click to expand...
Click to collapse
You can always put in a bounty in the Verizon thread. So devs like myself who have experience cracking and exploiting might show some interest
enigma99a said:
You can always put in a bounty in the Verizon thread. So devs like myself who have experience cracking and exploiting might show some interest
Click to expand...
Click to collapse
Id rather just not worry about it.
I do love Samsung, but HTC is the ethical choice.
Another one might be moving to TMO, but we shall seeee.......
PunchLick said:
Id rather just not worry about it.
I do love Samsung, but HTC is the ethical choice.
Another one might be moving to TMO, but we shall seeee.......
Click to expand...
Click to collapse
+1. Loved Sammy but went to M8.
Sent from my HTC One_M8 using xda app-developers app
enigma99a said:
You can always put in a bounty in the Verizon thread. So devs like myself who have experience cracking and exploiting might show some interest
Click to expand...
Click to collapse
that bounty is up there pretty high already just sayin
cyberace1985 said:
that bounty is up there pretty high already just sayin
Click to expand...
Click to collapse
I think the problem is SELinux is an extremely tough nut to crack(and I'm guessing you could easily get a six figure payday for an unknown SELinux/PaX kernel exploit in the black market at this point). Pretty much every linux kernel vulnerability exploit code I've seen fails on all of my boxes with SELinux, PAX and hardened GCC(one of these protection mechanisms always ends up killing the exploit before it can deliver its payload). Do we know exactly what SELinux and PAX(if any) features were enabled in the .config that Samsung used to compile the kernel (and if a hardened toolchain was used for the userland)? At least from what I've seen a properly configured SELinux box with Pax and hardened GCC is one of the toughest boxes to crack. I guess what we can hope for is that someone at Samsung did something stupid otherwise its quite possible we could be waiting for awhile(unless a key or signed unlocked bootloader leaks).
(edit: This applies to getting root through a kernel exploit.(Although with SELinux that isn't enough you need to not only be UID0 root but you also have to switch the role to sysadm_r. The bootloader I'm not 100 percent sure on the secure boot process but my understanding from reading other dev's threads is that this will be even harder than getting a root escalation in the SELinux kernel). Although if we could crack the bl we could just inject root easily.
So I dropped my Galaxy S4 and destroyed the display, rendering it useless. Then I ordered a Nexus 6 and its amazing! I love it. I had rooted my S4 successfully and I had some root apps running, which I came to love and now I'm having trouble to live without them.
I want to root my Nexus 6, but my mom won't let me. She says she wants to learn more about the risks.
I don't understand her reasoning because rooting a Samsung on Verizon is extremely tricky compared to a Nexus, and I was able to do that without any problems. From what I can tell the risk is very low for a Nexus, and it's hard to completely brick as long as you don't go flashing the wrong stuff and I probably won't go flashing anything fancy until there are some more ROMs for Marshmallow. And if I ever do physically break it, its really easy to go back to stock and make it like it was never even messed with. I've tried to tell her this but she won't listen.
If anyone has a minute, can someone confirm and possibly reinforce my statement? I'd love to root this baby in the next few days. Thanks!
zfrnz said:
So I dropped my Galaxy S4 and destroyed the display, rendering it useless. Then I ordered a Nexus 6 and its amazing! I love it. I had rooted my S4 successfully and I had some root apps running, which I came to love and now I'm having trouble to live without them.
I want to root my Nexus 6, but my mom won't let me. She says she wants to learn more about the risks.
I don't understand her reasoning because rooting a Samsung on Verizon is extremely tricky compared to a Nexus, and I was able to do that without any problems. From what I can tell the risk is very low for a Nexus, and it's hard to completely brick as long as you don't go flashing the wrong stuff and I probably won't go flashing anything fancy until there are some more ROMs for Marshmallow. And if I ever do physically break it, its really easy to go back to stock and make it like it was never even messed with. I've tried to tell her this but she won't listen.
If anyone has a minute, can someone confirm and possibly reinforce my statement? I'd love to root this baby in the next few days. Thanks!
Click to expand...
Click to collapse
Tell her that you won't use a phone with restrictions. Give the phone back. Be strong, don't complain. Just leave the phone alone.
zfrnz said:
So I dropped my Galaxy S4 and destroyed the display, rendering it useless. Then I ordered a Nexus 6 and its amazing! I love it. I had rooted my S4 successfully and I had some root apps running, which I came to love and now I'm having trouble to live without them.
I want to root my Nexus 6, but my mom won't let me. She says she wants to learn more about the risks.
I don't understand her reasoning because rooting a Samsung on Verizon is extremely tricky compared to a Nexus, and I was able to do that without any problems. From what I can tell the risk is very low for a Nexus, and it's hard to completely brick as long as you don't go flashing the wrong stuff and I probably won't go flashing anything fancy until there are some more ROMs for Marshmallow. And if I ever do physically break it, its really easy to go back to stock and make it like it was never even messed with. I've tried to tell her this but she won't listen.
If anyone has a minute, can someone confirm and possibly reinforce my statement? I'd love to root this baby in the next few days. Thanks!
Click to expand...
Click to collapse
Just tell her your grandma`s phone is rooted too
NLBeev said:
Tell her that you won't use a phone with restrictions. Give the phone back. Be strong, don't complain. Just leave the phone alone.
Click to expand...
Click to collapse
If I did that then she would get pissed and just take the phone away... Stock is better than no phone at all. If I give her some evidence then that would most likely do the trick. I've learned that if I go about things in smart ways and don't get angry, I get what I want more often. Thanks though
gee2012 said:
Just tell her your grandma`s phone is rooted too
Click to expand...
Click to collapse
Lol... My grandfather's phone actually is rooted. He's got sprint though and they're better when it comes to fixing rooting.
Your mother is just being cautious. Yeah, the chances of brick on nexus phones are slim, but that depends on how much you know about rooting and such; or how well you can follow instructions to the letter. And, like any other phone, Nexus' can be very expensive to fix if damaged too much (hard brick). Especially with the Marshmallow update, anything can go wrong. If you're confident in what you're doing, go for it. Otherwise, listen to your mother.
zfrnz said:
If I did that then she would get pissed and just take the phone away... Stock is better than no phone at all. If I give her some evidence then that would most likely do the trick. I've learned that if I go about things in smart ways and don't get angry, I get what I want more often. Thanks though
Click to expand...
Click to collapse
No, be consequent, the phone is yours or not. You can not change the idea that there risks. Because there is a risk.
You could change the strategy. The risk is not the rooting process. The risk is the person that roots the phone. Show/tell her that you know all the howto's. You must give the impression you are an expert.
toledodj said:
Your mother is just being cautious. Yeah, the chances of brick on nexus phones are slim, but that depends on how much you know about rooting and such; or how well you can follow instructions to the letter. And, like any other phone, Nexus' can be very expensive to fix if damaged too much (hard brick). Especially with the Marshmallow update, anything can go wrong. If you're confident in what you're doing, go for it. Otherwise, listen to your mother.
Click to expand...
Click to collapse
Yeah but compared to rooting an S4 a nexus is not risky at all... And wugfresh toolkit works on Marshmallow so that makes it even easier
zfrnz said:
Yeah but compared to rooting an S4 a nexus is not risky at all... And wugfresh toolkit works on Marshmallow so that makes it even easier
Click to expand...
Click to collapse
I didn't know the toolkit could now root Marshmallow. I could've sworn using it would brick the phone. If the root toolkit can do it, by all means go for it
toledodj said:
I didn't know the toolkit could now root Marshmallow. I could've sworn using it would brick the phone. If the root toolkit can do it, by all means go for it
Click to expand...
Click to collapse
This page has mixed answers... One guy said it worked but another got bootloop. But a boot loop is easy to get out of and that seems like the worst thing that happened
zfrnz said:
Yeah but compared to rooting an S4 a nexus is not risky at all... And wugfresh toolkit works on Marshmallow so that makes it even easier
Click to expand...
Click to collapse
Last remark. Arguments won't change the idea's of your mother. Tell her you should be very happy when your phone is rooted. Because of the customizing possibilities, like the use of layers.
Happiness is a state of mind and you will remember many many years later the fun of using a smartphone that was rooted. Thanks to your mother.
first off, it is EASY to brick a nexus, especially if you go the toolkit route. why? because when you use a toolkit you never learn how to do anything, like fixing your device, or how to actually root properly. that said, if you do decide to go that way, ill expect to see a thread titled.. "my mom was right about me bricking my n6".
zfrnz said:
This page has mixed answers... But a boot loop is easy to get out of and that seems like the worst thing that happened
Click to expand...
Click to collapse
Still a hassle though. Luckily, I've never heard of anyone hard-bricking a nexus
---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------
simms22 said:
first off, it is EASY to brick a nexus, especially if you go the toolkit route. why? because when you use a toolkit you never learn how to do anything, like fixing your device, or how to actually root properly. that said, if you do decide to go that way, ill expect to see a thread titled.. "my mom was right about me bricking my n6".
Click to expand...
Click to collapse
In that case, it's always wise to learn both methods. From my experience, as long as you unlock the bootloader and enable USB debugging, the root kit is foolproof
It's possible her concern isn't about bricking but data security risks?
Sent from my P01MA using Tapatalk
toledodj said:
Still a hassle though. Luckily, I've never heard of anyone hard-bricking a nexus
---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------
In that case, it's always wise to learn both methods. From my experience, as long as you unlock the bootloader and enable USB debugging, the root kit is foolproof
Click to expand...
Click to collapse
both methods? theres is only one right method, pressing a button isnt a method. but, once you learn the proper method, feel free to use a toolkit. the problem is that a lot of newbies use toolkits, then run into easily fixable problems that they cant solve.
and it appears that you dont read much, as very many have bricked their nexus. most common way recently is by running into a bootloop without having your bootloader unlocked nor the option to unlock it enabled. thats a 100% brick, and its happened to very many people.
Not that I'm condoning defying your mom's explicit wishes, but she's not even going to know if you root it. Better to ask forgiveness after than permission before...
If you learn to do everything manually and not use a toolkit then it is quite hard to brick a Nexus device. BUT, I've not rooted my last two (N5 and this N6) as there's no point these days.
Bricking will occur if you try and take a short cut or don't follow instructions.
simms22 said:
both methods? theres is only one right method, pressing a button isnt a method. but, once you learn the proper method, feel free to use a toolkit. the problem is that a lot of newbies use toolkits, then run into easily fixable problems that they cant solve.
and it appears that you dont read much, as very many have bricked their nexus. most common way recently is by running into a bootloop without having your bootloader unlocked nor the option to unlock it enabled. thats a 100% brick, and its happened to very many people.
Click to expand...
Click to collapse
I mentioned unlocking the bootloader and enabling USB debugging when using the root kit
toledodj said:
I mentioned unlocking the bootloader and enabling USB debugging when using the root kit
Click to expand...
Click to collapse
id even unlock my bootloader even if i never rooted.
simms22 said:
id even unlock my bootloader even if i never rooted.
Click to expand...
Click to collapse
Mine is always unlocked also