Hi,
i did hear around that an new exploit was found for unlocking our kindle fire HDX, but this exploit would not work anymore on latest update ( 13.3.2.4 ). I can not confirm this news but you are now warned in case it's real.
Cpasjuste said:
Hi,
i did hear around that an new exploit was found for unlocking our kindle fire HDX, but this exploit would not work anymore on latest update ( 13.3.2.4 ). I can not confirm this news but you are now warned in case it's real.
Click to expand...
Click to collapse
But I can downgrade by editing build.prop, isn't it?
Cpasjuste said:
Hi,
i did hear around that an new exploit was found for unlocking our kindle fire HDX, but this exploit would not work anymore on latest update ( 13.3.2.4 ). I can not confirm this news but you are now warned in case it's real.
Click to expand...
Click to collapse
newest towelroot version (download from towelroot.com) can root this version. I have tried on my HDX 7 successfully.
Are you talking about root? Or are you talking about something more serious?
Cpasjuste said:
Hi,
i did hear around that an new exploit was found for unlocking our kindle fire HDX, but this exploit would not work anymore on latest update ( 13.3.2.4 ). I can not confirm this news but you are now warned in case it's real.
Click to expand...
Click to collapse
The same towelroot that worked for previous versions works fine to root 13.3.2.4
What do you mean by "unlocking"?
It's not about root, it's about unlock the boot loader
Without unlocked bootloader, we will never have customs roms , kernel, recovery, etc
Sj12345 said:
It's not about root, it's about unlock the boot loader
Without unlocked bootloader, we will never have customs roms , kernel, recovery, etc
Click to expand...
Click to collapse
Yep i'm talking about an unlock method but i have no more information. But i think it's important to share ...
Has anyone tried to downgrade from the latest version?
I've seen one other person mention an unlock exploit. I have searched and searched and can't find any information on it. Where did you hear about it from?
DarkenedMatter said:
I've seen one other person mention an unlock exploit. I have searched and searched and can't find any information on it. Where did you hear about it from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2760912&page=7
S_transform said:
http://forum.xda-developers.com/showthread.php?t=2760912&page=7
Click to expand...
Click to collapse
Thanks, i didn't actually search Xda but used Google. My mistake haha
DarkenedMatter said:
Thanks, i didn't actually search Xda but used Google. My mistake haha
Click to expand...
Click to collapse
Its all good man, its like the 7th page of an unrelated thread. I only found it because I lurk too much, haha.
So... Does anybody know what happend with this information?
edwin0394 said:
So... Does anybody know what happend with this information?
Click to expand...
Click to collapse
looks kinda hokey to me... ive found info on theunlockr's site talking about safestrap working, which is what ive used on all the verizon devices ive rooted that also have locked bootloaders. I have a GS3 thats currently ROMmed and rooted which has a locked bootloader, also a RAzR, a Bionic, Droid 3 (sold)... and.... thint might be it for locked bootloader devices. But i have quite the bevvy if Androids and have never run into such an issue. There is almost ALWAYS a workaround, such as safestrap. Read more guys, there is a solution
edit: there is an issue with flashing AOSP/AOKP ROMs with safestrap on some devices, but the RAzR is running SLIMKAT right this very moment, and its working perfectly fine. Seems to be an issue with access to a partition that i cant recall the name of offhand. Sorry, too much hands off time since i got my S5
Related
I wake up everyday looking for news about 2.3 getting released. I am on 2.2.1 so I lost the ability to root. So i hope this comes out soon and if anyone has any info please post.
Officially it should come out in "coming weeks" as this tweet suggests - http://twitter.com/googlenexus/status/16974464310845440.
But there's a way to root your 2.2.1 anyways. Follow this guide:
http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
KROMO50 said:
I wake up everyday looking for news about 2.3 getting released. I am on 2.2.1 so I lost the ability to root. So i hope this comes out soon and if anyone has any info please post.
Click to expand...
Click to collapse
SuperOneClick works great if you still want root.
KROMO50 said:
I wake up everyday looking for news about 2.3 getting released. I am on 2.2.1 so I lost the ability to root. So i hope this comes out soon and if anyone has any info please post.
Click to expand...
Click to collapse
Just unlock your bootloader.
I have tried the super one click no luck
Other than unlocking, which is the preferred and safest way to do it. You could just follow the guide that was linked here. I did it for my friend just last week because he was afraid of the official way to root for some reason. It worked perfectly.
Yeah I did it the rageagainstthecage way.
Sent from my Nexus One using XDA App
nope but i read about 2.4 just google for:
google-ice-cream-android-2-4
cant post links
My sig says it all...
KROMO50 said:
I have tried the super one click no luck
Click to expand...
Click to collapse
Odd, are you sure you have the latest Super One Click? It worked fine for me 2.2.1 N1 on T-Mobile.
KROMO50 said:
I have tried the super one click no luck
Click to expand...
Click to collapse
Works fine for me. Did you get stuck at the looping problem after following the steps in the OP?
The way around that, as many of us have discovered, is to turn the phone off then run SuperOneClick and select 'root'. Turn the phone back on once 'waiting for device..' is shown in the program and then just leave it until it finishes.
Ensure USB debugging is enabled before you get started and that your PC has the required drivers installed. (Check Device Manager).
To be fair the Original Post needs updating as the instructions aren't very good without the above being mentioned.
DirkGently1 said:
SuperOneClick works great if you still want root.
Click to expand...
Click to collapse
Dumb question but, does that method allow you to install custom roms (e.g. CM7) without unlocking the bootloader, thus keeping the warranty?
frandavid100 said:
Dumb question but, does that method allow you to install custom roms (e.g. CM7) without unlocking the bootloader, thus keeping the warranty?
Click to expand...
Click to collapse
Using exploit to root allows you to get rooted device without unlocking the bootloader. However, I cannot tell you 'your warranty is kept' for certain(as long as bootloader is locked and you can revert to stock, I think it's okay).
frandavid100 said:
Dumb question but, does that method allow you to install custom roms (e.g. CM7) without unlocking the bootloader, thus keeping the warranty?
Click to expand...
Click to collapse
This does not unlock the boot loader....... and, yes you can flash roms once rooted.
Good luck on that warrenty buisness.
LFact said:
However, I cannot tell you 'your warranty is kept' for certain(as long as bootloader is locked and you can revert to stock, I think it's okay).
Click to expand...
Click to collapse
If you do revert to stock there should be no way to tell you ever modified the rom, isn't that right?
frandavid100 said:
If you do revert to stock there should be no way to tell you ever modified the rom, isn't that right?
Click to expand...
Click to collapse
Unfortunately you can only relock the bootloader on Nexus S, according to a Google Android developer
rcknr said:
Officially it should come out in "coming weeks" as this tweet suggests - http://twitter.com/googlenexus/status/16974464310845440
Click to expand...
Click to collapse
Is this "official" though? It's been 23 days since that post.
We'll get it, but I'm just bored of waiting. With so much anticipation, we'll probably be disappointed. Hope not.
Sent from my Nexus One using XDA App
hircus said:
Unfortunately you can only relock the bootloader on Nexus S, according to a Google Android developer
Click to expand...
Click to collapse
His question isn't about relocking the bootloader. But as long as you reflash the stock ROM and recovery, then I don't think there would be a way to tell without further examination. Regardless, HTC isn't too strict with the warranty claims, as many members on this forum have claimed warranty and sent back rooted phones to HTC. You should be fine.
andynx1 said:
Is this "official" though? It's been 23 days since that post.
We'll get it, but I'm just bored of waiting. With so much anticipation, we'll probably be disappointed. Hope not.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
that's 3 weeks. "coming weeks" being a PR equivalent of more than a month, we should be waiting for gb another 2 weeks at least...
It's only 5% of GB, but you can have the keyboard from it. A definite improvement and works perfectly on my N1 with 2.2.1 (no root needed):
http://www.appbrain.com/app/keyboard-from-android-2-3/com.moo.android.inputmethod.latin.free
Back in old days when i had a HTC Wildfire with a few clicks i rooted it and started installing new ROMS on to it
But since i got this New Xperia Play : R800i Build NO. 3.0.1.a.0.146 {UK}
I got no clue how to do anything on it. Let me be honest here... I updated my phone using the option under the settings menu in About my phone and seems to be on 2.3.3 and look all my friends have rooted their phones but i got no clue if its even possible . Mabey im not such a noob or something but i would be really greatfull if anyoen could point me atleast to the right direction. Mabey some helpfull links to help a fellow noob
Is your phone sim locked?
Sent from my R800i using Tapatalk
Nope... Well not that i know of, because i got my phone from vodafone and once i inserted a sim card from another operator i made a few calls and i could recieve calls too without any problems.
arian009 said:
Nope... Well not that i know of, because i got my phone from vodafone and once i inserted a sim card from another operator i made a few calls and i could recieve calls too without any problems.
Click to expand...
Click to collapse
Mine was from vodafone and wasnt sim locked either. Ok you have two choices for root. You can either unlock your bootloader (there are many downsides and advantages to this so you should research it) or downgrade to 2.3.2, root using gingerbreak then OTA update to latest version. That way you will not loose root while updating.
Sent from my R800i using Tapatalk
Seems like ol' Freddy is right after all:
http://en.wikipedia.org/wiki/Eternal_return
What OTA Update Means? And please can you give some links on how to downgrade and root it please?
And btw if i use the method of downgrading my phone first will i be able to flash custom ROMs?
Logseman said:
Seems like ol' Freddy is right after all:
http://en.wikipedia.org/wiki/Eternal_return
Click to expand...
Click to collapse
Lmao
Sent from my R800i using Tapatalk
arian009 said:
What OTA Update Means? And please can you give some links on how to downgrade and root it please?
Click to expand...
Click to collapse
Im on my phone so i can't really link. Look in the android development section, there is a thread all about rooting 2.3.3 with a locked bootloader. OTA means over the air. Basically thats when you download and install an update using just your phone.
Sent from my R800i using Tapatalk
arian009 said:
And btw if i use the method of downgrading my phone first will i be able to flash custom ROMs?
Click to expand...
Click to collapse
No you need an unlocked bootloader to flash custom roms. But please read the pros and cons of unlocking your bootloader first. And understand what you can and can't do
Sent from my R800i using Tapatalk
Ok mate just wanna say thanks a lot for your help and i really appreciate it. You really helped me out here. also just one more thing i need to know. By the looks of it the only cons in unlocking your bootloader seems to be that you will lose warranty and that your phone or your radio may get bricked which apparently can be fixed with restoring a backed up data using a program named omnius for se which i'm actually working on... however my only other concern is if there are any other disadvantages regarding the unblocking the bootloader that you happned to know of and be kind to share it with me Also just wanna say that i can see many tutorials as you said in the development section and i quite frankly i don't know which one applies to me since i realized one of the tutorials are for models with build number .184 where as mine is 3.0.1.a.0.145 AND I HAVE NO CLUE WHICH TUTORIAL TO FOLLOW. So i would be greatfull if you could lend me link to a right tutorial whenever you get free time on the PC
If all you want is root you can do that with a locked bootloader. You will have to downgrade to 2.3.2 (.184) then root then ota to get the latest firmware rooted. Follow the guide here. Or see this post i made here for easier instuctions on downgrading and rooting.
If you want to flash custom roms then you do need an unlocked bootloader like AndroHero has said. You dont need a specific guide to unlock your bootloader. Just go too the SE bootloader unlocking site (it gives you all the instructions you need) http://unlockbootloader.sonyericsson.com/. Then just flash doomlords kernel (which autoroots) or anything really from the development section (since i think anything can be rooted with one click with an unlocked bootloader) you will then have root and the ability to flash cutom roms.
Oh btw build number .184 = 2.3.2, build number 3.0.1.a.0.145 = 2.3.3 and build number 4.0.a = 2.3.3 (xloud version, the latest update)
+
If you unlock your bootloader OTA, Pc Companion + SEUS are off limits use any of them after unlocking your bootloader and you will brick your phone. Go to the dev section for the latest updates.
Logseman said:
Seems like ol' Freddy is right after all:
http://en.wikipedia.org/wiki/Eternal_return
Click to expand...
Click to collapse
Looks like I've overseen your sense of humor... Very subtle... Wicked
Regards Dousan...
You won't allow me to get rowdy and yell at folks, so I have to resort to good old snark. Caveat emptor.
Dousan said:
Looks like I've overseen your sense of humor... Very subtle... Wicked
Regards Dousan...
Click to expand...
Click to collapse
Logseman said:
You won't allow me to get rowdy and yell at folks, so I have to resort to good old snark. Caveat emptor.
Click to expand...
Click to collapse
I got it straight away
Logseman said:
You won't allow me to get rowdy and yell at folks, so I have to resort to good old snark. Caveat emptor.
Click to expand...
Click to collapse
Lmao I can't argue with that, althoug it's sneaky to post a link like that, still hilarious
Regards Dousan...
I have a Droid Maxx, and Razr Maxx HD and perhaps some beer cash for the answer to root...
I was thinking flashing twrp, then let it root, or am i way off or require an unlocked bootloader? I tried sunshine, but no go as it requires root.
So if i understand, you can get root without an unlocked bootloader, or is an unlocked bootloader a prerequisite of root? I am thinking not, but i am a Windows/SharePoint guy and pretty dumb to linux...
wrecklesswun said:
I have a Droid Maxx, and Razr Maxx HD and perhaps some beer cash for the answer to root...
I was thinking flashing twrp, then let it root, or am i way off or require an unlocked bootloader? I tried sunshine, but no go as it requires root.
So if i understand, you can get root without an unlocked bootloader, or is an unlocked bootloader a prerequisite of root? I am thinking not, but i am a Windows/SharePoint guy and pretty dumb to linux...
Click to expand...
Click to collapse
You need an unlocked bootloader to flash TWRP (which flashes SuperSU). There is no known root method available yet because the phone has only been out for about 8 hours.
The Sunshine team has apparently said they will not be supporting Motorola devices for 4.4.4 in their 3.0 release, only HTC, so unlikely it will work there.
Has anyone tried Towelroot?
amebiasis said:
Has anyone tried Towelroot?
Click to expand...
Click to collapse
"this phone is not currently supported"
fury683 said:
(...)The Sunshine team has apparently said they will not be supporting Motorola devices for 4.4.4 in their 3.0 release, only HTC, so unlikely it will work there.
Click to expand...
Click to collapse
I think they said the opposite: "Verizon users on 4.4.4 you will have to wait for the 3.0 release."
timeToy said:
I think they said the opposite: "Verizon users on 4.4.4 you will have to wait for the 3.0 release."
Click to expand...
Click to collapse
Yes, that is in the website. Someone posted this in another thread here. There's no link to the OP so I'm not sure beyond what it says.
http://forum.xda-developers.com/showpost.php?p=56389152&postcount=83
fury683 said:
Yes, that is in the website. Someone posted this in another thread here. There's no link to the OP so I'm not sure beyond what it says.
http://forum.xda-developers.com/showpost.php?p=56389152&postcount=83
Click to expand...
Click to collapse
Yeah, I found it in the meantime...
AndyMan386 said:
Quote:
Originally Posted by jcase
3.0 is ONLY addressing HTC devices at this time, we have no plans, at this time, to include Motorola for technical reasons
Click to expand...
Click to collapse
timeToy said:
I think they said the opposite: "Verizon users on 4.4.4 you will have to wait for the 3.0 release."
Click to expand...
Click to collapse
Edit: here's the post from today. No dice.
http://forum.xda-developers.com/showpost.php?p=56383217&postcount=1445
Yeah, I didn't think I'd need root but the dpi on this thing is just way too high. For being such a great display it's hindered by the scaling. Easily fixed with root though!!
Found this on some Chinese site. If I had a backup phone I'd try it. But I don't. So can't risk bricking. Anyone else want to take a leap of faith? Ummm... Won't let me post the link because I'm still a noob apparently... So gonna try breaking it up. Just remove the line returns and spaces.
H t t p : //
m. romjd. com/
jiaocheng/
content/
10837
Sent from my XT1254 using XDA Free mobile app
cmchance said:
Found this on some Chinese site. If I had a backup phone I'd try it. But I don't. So can't risk bricking. Anyone else want to take a leap of faith? Ummm... Won't let me post the link because I'm still a noob apparently... So gonna try breaking it up. Just remove the line returns and spaces.
H t t p : //
m. romjd. com/
jiaocheng/
content/
10837
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Don't know if I'm brave enough since I just picked mine up earlier today
Just got mine today so im hesitant to try it. Itching to get root and get a free wifi tether though. Ill think it over.
Here's the un-broken-up link just to make it easier.
http://m.romjd.com/jiaocheng/content/10837
Tempting.... Only issue I have is if it works, I have no way to unroot lol
man waiting for someone to try this and I will be first in line at my store to pick this phone up
Who will be the first brave soul?
Phone comes in tomorrow. I will try it then.
chriskader said:
Phone comes in tomorrow. I will try it then.
Click to expand...
Click to collapse
Didn't work for me. Too be safe I used a virtual machine with a snap shot taken before installing so I can revert back without the risk of spyware. Also tried Kingo but no luck with either.
---------- Post added at 06:39 AM ---------- Previous post was at 06:20 AM ----------
Also vroot during the root attempt installs 2 apps on your phone and who knows what it installs on Windows without running a regmon, if you do decide to try it make sure you uninstall the 2 chinese apps when your done trying. Also like I mentioned above I would highly not to install vroot or Kingo on your daily driver windows machine. Leave the testing to people who have virtual machines they can install these apps on.
I have used vroot and kingo in the past to successfully root so I know they do/can work, they just haven't been updated yet to work on the Droid Turbo. Hopefully they will.
kremer4 said:
Didn't work for me. Too be safe I used a virtual machine with a snap shot taken before installing so I can revert back without the risk of spyware. Also tried Kingo but no luck with either.
---------- Post added at 06:39 AM ---------- Previous post was at 06:20 AM ----------
Also vroot during the root attempt installs 2 apps on your phone and who knows what it installs on Windows without running a regmon, if you do decide to try it make sure you uninstall the 2 chinese apps when your done trying. Also like I mentioned above I would highly not to install vroot or Kingo on your daily driver windows machine. Leave the testing to people who have virtual machines they can install these apps on.
I have used vroot and kingo in the past to successfully root so I know they do/can work, they just haven't been updated yet to work on the Droid Turbo. Hopefully they will.
Click to expand...
Click to collapse
Thanks for saving me the effort. I was just about to try it on a VM....
coreywallen said:
Just got mine today so im hesitant to try it. Itching to get root and get a free wifi tether though. Ill think it over.
Here's the un-broken-up link just to make it easier.
http://m.romjd.com/jiaocheng/content/10837
Click to expand...
Click to collapse
Thanks for posting the unbroken link for me
Dang, you guys got my hopes up reading through this.
I keep checking the other Moto forums for root options. I'm banking on anything that will root a Moto 4.4.4 phone will work on ours. The Moto G 4.4.4 update has a later build date than our version.
Ok so my whole problem is that im on system version 183.46.15.XT907 when its supposed to be 183.46.10.XT907. My question is that is there a way to get to 183.46.10.XT907. again? I've been at this for hours and i'm in desperate need for help.
If you would like to see a picture of exactly please PM it will not let me place a picture as i am a new user
rockketman123 said:
Ok so my whole problem is that im on system version 183.46.15.XT907 when its supposed to be 183.46.10.XT907. My question is that is there a way to get to 183.46.10.XT907. again? I've been at this for hours and i'm in desperate need for help.
If you would like to see a picture of exactly please PM it will not let me place a picture as i am a new user
Click to expand...
Click to collapse
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini
That's a bummer, but for root part, maybe or maybe not. I don't think it's possible as Motorola took out some vital codes from Kit Kat ROM which allows root.
ATTACK said:
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini[/QUOTEO
I was able to flash it down to .10 but my kernel was after June 3rd, something like July 27th or whatever and yeah this doesnt allow it to work. Oh well, I'm switching to an S3 In less than a month.
Click to expand...
Click to collapse
rockketman123 said:
ATTACK said:
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini[/QUOTEO
I was able to flash it down to .10 but my kernel was after June 3rd, something like July 27th or whatever and yeah this doesnt allow it to work. Oh well, I'm switching to an S3 In less than a month.
Click to expand...
Click to collapse
Unlocked or locked? Kernel date and screenshot as proof please, including the AP Fastboot screen.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
I suspect it's already unlocked as it's impossible to downgrade the kernel on a locked RAZR M (OEM signatures, you know).
AndyYan said:
rockketman123 said:
Unlocked or locked? Kernel date and screenshot as proof please, including the AP Fastboot screen.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
as I'm a new user I cant post a screen shot but the imgur link is i(.)imgur(.)com/xiZuIyq(.)jpg and i(.)imgur(.)com/cA6W6Oi(.)jpg
I went from 4.1.2 Rooted and was never able to unlock the bootloader then flashed to 4.4.2 on the .15 then flashed to .10
Click to expand...
Click to collapse
You're outta luck. You ahould have flashed .10 first and unlocked the bootloader before you hop between the ROM version... .15 version permanently lock the bootloader.
EDIT: I looked at the pictures, however, I am suspicious of the claim. The reason being, the bootloader will check the kernel version, and if it's not agreed with the bootloader security key file (tz.mbn), the bootloader will refuse to touch it. If anyone else with the locked phone tries this harebrained experiment and come out without a softbrick, I may have to eat my sock.
Dr. Mario said:
You're outta luck. You ahould have flashed .10 first and unlocked the bootloader before you hop between the ROM version... .15 version permanently lock the bootloader.
Click to expand...
Click to collapse
yeah when i flashed over i "accidentally" did the wrong version (tut linked me to a wrong version I suppose) and now im piss out of luck, but like i said im not worrying about it since s3 within a few weeks or so. Hopefully one day it's able to Root though B)
EDIT: what exactly are you suspicious of? The claim that I went from 4.1.2 flashed to 4.4.2 but on .15 then down to .10?
If the eventual RAZR M update gets screwed up like the first one, it may get unlocked but I have grave doubt because Verizon have learned their lesson on this one: root = bootloader unlock, at least in the case of early Kit Kat update.
fellas i have received two moto M today and seems like this cant either root because this stupid 9mb of .15 update, since the kernal is after jun 3
towelroot
well any new exploit around the coner to try?
No root exploits right now, unfortunately. It's getting harder and harder to exploit the Kit Kat.
It appears that real soon we may have root for locked bootloader devices running Lollipop.
Read here for more info.
zoid_99 said:
It appears that real soon we may have root for locked bootloader devices running Lollipop.
Read here for more info.
Click to expand...
Click to collapse
One thing has nothing to do with the other.
Lollipop requires some changes to have root access and that was only possible with a modified kernel.
Now Chainfire managed to root the Lollipop without a custom kernel.
But installing ZIP file of root need a custom recovery , so still need to have the device with unlocked bootloader .
I've done the root Lollipop using this new root method of Chainfire.
Junior Passos said:
One thing has nothing to do with the other.
Lollipop requires some changes to have root access and that was only possible with a modified kernel.
Now Chainfire managed to root the Lollipop without a custom kernel.
But installing ZIP file of root need a custom recovery , so still need to have the device with unlocked bootloader .
I've done the root Lollipop using this new root method of Chainfire.
Click to expand...
Click to collapse
If you read the article it appears that there is no need to install a zip in a custom recovery to get root with this method.
" the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here"
zoid_99 said:
If you read the article it appears that there is no need to install a zip in a custom recovery to get root with this method.
" the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here"
Click to expand...
Click to collapse
Hmmm interesting.
Then the process should be with CF-Auto-Root .
I used one of those before when I first root in Lollipop.
But thought the command "mfastboot boot cf-auto-root.img" only work with unlocked bootloader and not the locked too.
Amazing.
Me excite!
You can only flash signed zips, so this only makes it easier because you dont need a device specific package for rooting
godutch said:
You can only flash signed zips, so this only makes it easier because you dont need a device specific package for rooting
Click to expand...
Click to collapse
Translated... Will it work on moto x vzw?
GatorsUF said:
Translated... Will it work on moto x vzw?
Click to expand...
Click to collapse
No.
cam30era said:
No.
Click to expand...
Click to collapse
OF course
This revelation means that Android 5.0 users*no longer need to run a modified kernel to gain root access via SuperSU (or other root solutions). While not a huge problem on Nexus devices with unlockable bootloaders, the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here, and we can present an exclusive explanation of the changes needed. At least for now (until/unless Google patch this), it is possible to gain root access and then install and use SuperSU on a stock Android 5.0 device, without any kernel ramdisk tweaking. The reason for this is the need for SuperSU to run a service as root, to allow for unconstrained root access on SELinux-protected devices.
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
neh4pres said:
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
Click to expand...
Click to collapse
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
neh4pres said:
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
Click to expand...
Click to collapse
Thanks Motorola -_-
Buy a nexus 6. That's what I did. Still have the moto x for my wife so I can play with it
Can't afford it right now. If I knew programming, you bet I would be working on it. God I hate Verizon, but been here so long it's my cheapest option.
matt99017d said:
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
Click to expand...
Click to collapse
Will the pure edition work on Verizon?
GrandMstrBud said:
Will the pure edition work on Verizon?
Click to expand...
Click to collapse
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
GreenMunky said:
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
Click to expand...
Click to collapse
LTE should work but what about CDMA side of it?
GreenMunky said:
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
Click to expand...
Click to collapse
GrandMstrBud said:
LTE should work but what about CDMA side of it?
Click to expand...
Click to collapse
No, CDMA will not work, nor 3G. So you will be confined only to LTE service and Google Voice (or similar).
matt99017d said:
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
Click to expand...
Click to collapse
Looks like your idea will not work and maybe that's the reason for this thread? Pure Edition won't work on VZW