Related
Ok, so I have been scouring the interwebs for 4 hours now, and I am getting 100 conflicting stories. I am not sure if I can post youtube links, but one says That I can use Kingo (didn't work for me) another was from FrenchGrape100 Neither worked for me, downloaded everything they said, did it all OTA. If anyone has any information, please reply.
Thank you in advance!
~Kevin D.
Okay, here's a TL;DR on the Droid lineup root situation. Essentially, you're out of luck at this point. No root for you! (Or for me, or for a lot of other annoyed users out there. You're not alone.)
Let me reiterate: if you currently have a brand new Droid running 4.4, no root is possible at the moment.
That being said, you're probably getting mixed accounts of this because of the following. Droid Maxx/Ultra/Mini sounds a lot like the Moto X--and they're very similar phones. However, the Moto X DOES have root on 4.4. It's a complicated process that involves downgrading to 4.2, installing a backdoor, and upgrading again to 4.4, then using the backdoor to regain root access. However, as the Droid Maxx/Ultra/Mini have locked bootloaders, it is not possible to downgrade after accepting the OTA upgrade to KitKat 4.4, and most new phones in the lineup are being shipped out with 4.4 already installed.
The first inkling of possible root was when noted dev and exploit-master jcase mentioned, tangentially and on twitter, that he HAD found an exploit for our phones. However, the exploit is not suitable for casual user usage, and still doesn't unlock write protection on the phone, making it essentially useless. Oh, and as a result of the locked write protection, root would be lost any time you restarted the phone. Jcase will be revealing the exploit at the blackhat conference this coming August as a teaching tool, but don't expect it to turn into anything we'll be seeing a solution out of.
The next glimmer of hope came a few weeks ago; remember how I said we couldn't downgrade because of our locked bootloaders? Some Motorola employee started selling bootloader unlock codes for the Droid lineup. You could send the guy 40 bucks and your IMEI number and he'd send you back a device-specific code to unlock your bootloader. Which through an even more complicated process, does eventually allow for root. However, as of about 2ish (?) weeks, the guy selling the codes has stopped; it seems like he/she/them/it/whatever no longer has access to the database containing the unlock codes. A few lucky people got codes before that happened--the process seemed sketchy, and those of us like myself who hesitated are now left with locked down phones.
So yeah, at various points, it's been possible to get root--which, when trying to read up on this stuff, makes it a tad hard to follow.
No root now, though, not if you're already on KitKat 4.4.
Sorry for the disappointment. Keep your ear to the ground in case someone offering codes pops up again and is legit--but I wouldn't hope too hard.
I am one among those few lucky people who got code and unlocked the BL and enjoying root now in 4.4.
@Jumnhy
However, the Moto X DOES have root on 4.4. It's a complicated process that involves downgrading to 4.2, installing a backdoor, and upgrading again to 4.4, then using the backdoor to regain root access. However, as the Droid Maxx/Ultra/Mini have locked bootloaders, it is not possible to downgrade after accepting the OTA upgrade to KitKat 4.4,
Click to expand...
Click to collapse
I want to add only one extra info to make things more clear. Actually BigRed's Moto X is also coming with locked / encrypted BootLoaders like DroidMini/Maxx/Ultra, but since its 4.4 update came first and without signature verification / check and hence downgrading was possible in its case. But in 4.4 of Droid series, the mistake was corrected and downgrade was IMPOSSIBLE.
So Droid users with 4.4 and NO root has to live without root in the future, unless any wonder occurs (like the earlier code purchase).
Moral of the Story:
If you want root access in Droid or other BigRed's phones, buy their Dev edition in future.
Good clarification. Missed that point myself!
This is really disheartening. I had one Droid Maxx back before the update and like an idiot, I updated without researching first. Now I got my insurance to replace the phone hoping that they'd send me one which hasn't been updated yet and instead they sent me one with 4.4 pre-installed. So I started researching and I thought it was possible because I saw a thread where an XDA user... Einstein something or other... said he got the downgrade to work. I think I'm just going to sell the phone and either try to buy one without the update or get a different phone.
ThunderWulf said:
This is really disheartening. I had one Droid Maxx back before the update and like an idiot, I updated without researching first.
Click to expand...
Click to collapse
my dear thunder, you are not alone.... i miss tethering my internet....
nerdyplayer said:
my dear thunder, you are not alone.... i miss tethering my internet....
Click to expand...
Click to collapse
Tethering does not require root. Now if you want wireless hotspot no frills then yes you need root.
You could use easy tether pro to tether just fine without root. But if you wanted to share that connection with more devices the first one would have to remain on. You can bridge the connection to your wireless card and share it.
Sent from my Nexus 7 using Tapatalk
kanagadeepan said:
I am one among those few lucky people who got code and unlocked the BL and enjoying root now in 4.4.
@JumnhyI want to add only one extra info to make things more clear. Actually BigRed's Moto X is also coming with locked / encrypted BootLoaders like DroidMini/Maxx/Ultra, but since its 4.4 update came first and without signature verification / check and hence downgrading was possible in its case. But in 4.4 of Droid series, the mistake was corrected and downgrade was IMPOSSIBLE.
So Droid users with 4.4 and NO root has to live without root in the future, unless any wonder occurs (like the earlier code purchase).
Moral of the Story:
If you want root access in Droid or other BigRed's phones, buy their Dev edition in future.
Click to expand...
Click to collapse
Do you mind sort of breaking down the process you did once you got the code and how the code was styled. Alpha-numeric? 10 digits? Things like that. I am considering that since there is a code and method for unlocking the device in an offline setting, that could be bruteforced using strong hardware GPU. (Which I tend to have these days thanks to virtual currencies.)
I am going to run on the assumption Motorola won't lock out a user for multiple incorrect attempts but who knows.
netuoso said:
Do you mind sort of breaking down the process you did once you got the code and how the code was styled. Alpha-numeric? 10 digits? Things like that. I am considering that since there is a code and method for unlocking the device in an offline setting, that could be bruteforced using strong hardware GPU. (Which I tend to have these days thanks to virtual currencies.)
I am going to run on the assumption Motorola won't lock out a user for multiple incorrect attempts but who knows.
Click to expand...
Click to collapse
It's a 20 digit Alpha numeric code. You enter the code in fastboot mode using the command fastboot oem unlock <code> Since there are 36^20 possible combinations good luck bruteforcing THAT
I think the BL unlock is no longer available from what I have been reading. If anyone has had success lately please correct me.
Sent from my DROID MAXX using Tapatalk
BladeRunner said:
It's a 20 digit Alpha numeric code. You enter the code in fastboot mode using the command fastboot oem unlock <code> Since there are 36^20 possible combinations good luck bruteforcing THAT
Click to expand...
Click to collapse
I know that this question is rhetorical, as reverse engineering this is probably not possible, but is it full alphabet, or only the hex characters a-f for the alpha characters? That's a smaller alphabet. (Also, if it is upper and lower case letters, that's at least a 62 character alphabet, so 62^20. If they are just hex digits, that's "just" 16^20.)
doogald said:
I know that this question is rhetorical, as reverse engineering this is probably not possible, but is it full alphabet, or only the hex characters a-f for the alpha characters? That's a smaller alphabet. (Also, if it is upper and lower case letters, that's at least a 62 character alphabet, so 62^20. If they are just hex digits, that's "just" 16^20.)
Click to expand...
Click to collapse
full alphabet and I have only seen upper case letters
unlock code
an21281 said:
I think the BL unlock is no longer available from what I have been reading. If anyone has had success lately please correct me.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
I just tried to purchase the code. Be guy says no more 2013 codes. Only 2014 production
JarMagic said:
I just tried to purchase the code. Be guy says no more 2013 codes. Only 2014 production
Click to expand...
Click to collapse
Very interesting...
JarMagic said:
I just tried to purchase the code. Be guy says no more 2013 codes. Only 2014 production
Click to expand...
Click to collapse
Some late '13 are getting it anyway...
Very tempted to purchase one now with the android l beta out. A few questions (as I'm sure many have who are in the same predicament) before I do:
1. Since I'm purchasing one from Google play and it comes pre loaded with latest kit kat version, can this device's boot loader be unlocked and rooted using various all in one toolkits that are currently out there?
2. For those of you who are currently using it have you noticed any issues with battery life? Any difference with connectivity to mobile data.
I look forward to hearing from you guys before I make my purchase and thank you in advance.
ThatArchVillan said:
Very tempted to purchase one now with the android l beta out. A few questions (as I'm sure many have who are in the same predicament) before I do:
1. Since I'm purchasing one from Google play and it comes pre loaded with latest kit kat version, can this device's boot loader be unlocked and rooted using various all in one toolkits that are currently out there?
2. For those of you who are currently using it have you noticed any issues with battery life? Any difference with connectivity to mobile data.
I look forward to hearing from you guys before I make my purchase and thank you in advance.
Click to expand...
Click to collapse
well if you have made up your mind to get into the party then
1.Yes, it can be rooted fine with toolkit, but still advisable to do it the adb way but toolkit works fine for many who dont want to get into hassle of learning adb stuff
2.for battery it will easily last a day though significant drainage was there with earlier builts on 3g data but it has been solved to some extent now and if you are on wifi no worries
3.if you are not aware of the fact that the next nexus device is there,and expected to release oct/nov so if you want to wait as it comes pre loaded with android L which will get a better name rather than L soon
make your choice :good:
shhbz said:
well if you have made up your mind to get into the party then
1.Yes, it can be rooted fine with toolkit, but still advisable to do it the adb way but toolkit works fine for many who dont want to get into hassle of learning adb stuff
2.for battery it will easily last a day though significant drainage was there with earlier builts on 3g data but it has been solved to some extent now and if you are on wifi no worries
3.if you are not aware of the fact that the next nexus device is there,and expected to release oct/nov so if you want to wait as it comes pre loaded with android L which will get a better name rather than L soon
make your choice :good:
Click to expand...
Click to collapse
Thank you so much for your quick reply. If a new nexus will be releasing in 4-5 months and it will have the new android os then I guess I can wait. I hope it stays at the $350 price point. For my personal device I use a galaxy s4 running slimkat and it works fine with slight damage around the edges with the battery lasting an easily 15+ hours with moderate to high use. Again thank you because you saved me $350+ dollars but I'm sure you made it a lot easier for the people who are on the fence still and are looking to get a new phone (who actually need a new device) who were looking to do the same thing.
ThatArchVillan said:
Thank you so much for your quick reply. If a new nexus will be releasing in 4-5 months and it will have the new android os then I guess I can wait. I hope it stays at the $350 price point. For my personal device I use a galaxy s4 running slimkat and it works fine with slight damage around the edges with the battery lasting an easily 15+ hours with moderate to high use. Again thank you because you saved me $350+ dollars but I'm sure you made it a lot easier for the people who are on the fence still and are looking to get a new phone (who actually need a new device) who were looking to do the same thing.
Click to expand...
Click to collapse
well a s4 is a good enough phone to spend this 4to 5 months of wait till the next beast is release and whatever drawbacks we can conclude from nexus5 though its a user expectation stuff, still expecting few things after the google I/O and expected to sweep all other phone by large
expected:
64bit snapdragon 810/808 render 4K video,/3gb ram/13mega pixel camera/a larger battery
ThatArchVillan said:
Very tempted to purchase one now with the android l beta out. A few questions (as I'm sure many have who are in the same predicament) before I do:
1. Since I'm purchasing one from Google play and it comes pre loaded with latest kit kat version, can this device's boot loader be unlocked and rooted using various all in one toolkits that are currently out there?
Click to expand...
Click to collapse
Please do not use a toolkit. If you use a toolkit, you wont learn anything about fastboot. Unlocking the bootloader and flashing a recovery via fastboot is ridiculously easy on this phone. If you don't take the time to learn fastboot now, when you get into trouble later on - you wont know what you're doing and when we try to give you instructions if you need to use fastboot to recover, it makes it much more difficult for us to help you fix it.
It's like turning up to a creative writing course, but expecting us to teach you to read first,
Please click the link in my signature and look at section 1a and 1b. To root an unlock your bootloader, section 1b has all you need to know.
It really is as simple as installing fastboot and drivers then running a couple of fastboot commands. Very easy and worth learning.
rootSU said:
Please do not use a toolkit. If you use a toolkit, you wont learn anything about fastboot. Unlocking the bootloader and flashing a recovery via fastboot is ridiculously easy on this phone. If you don't take the time to learn fastboot now, when you get into trouble later on - you wont know what you're doing and when we try to give you instructions if you need to use fastboot to recover, it makes it much more difficult for us to help you fix it.
It's like turning up to a creative writing course, but expecting us to teach you to read first,
Please click the link in my signature and look at section 1a and 1b. To root an unlock your bootloader, section 1b has all you need to know.
It really is as simple as installing fastboot and drivers then running a couple of fastboot commands. Very easy and worth learning.
Click to expand...
Click to collapse
Thank you for linking that guide. This will be most helpful to those looking to purchase that nexus 5 in the near future. I could go either way at this point. I'd feel real salty if I got it and the nexus 6 comes out a as early as mentioned above. Any set release date on that yet?
ThatArchVillan said:
Any set release date on that yet?
Click to expand...
Click to collapse
Anything anyone here says about the Nexus 6 is a guess. We do not even know if there will be a Nexus 6 at this point, let alone a release date. If you're concerned about that, wait until November and see what happens. If no Nexus 6 has been announced, get something else.
rootSU said:
Anything anyone here says about the Nexus 6 is a guess. We do not even know if there will be a Nexus 6 at this point, let alone a release date. If you're concerned about that, wait until November and see what happens. If no Nexus 6 has been announced, get something else.
Click to expand...
Click to collapse
So I bit and purchased a white 16gig nexus 5. I look forward to doing things properly. I must ask though, is Franco kernel compatible with android L? Also can L be rooted on the nexus 5? I could have sworn there's already a thread created for this question already
L is a preview. It isn't an official release. No source code has been released so no one can develop a kernel for it.
Click the link in my signature. It contains all the important threads including rooting L
Sent from my Nexus 5 using Tapatalk
rootSU said:
L is a preview. It isn't an official release. No source code has been released so no one can develop a kernel for it.
Click the link in my signature. It contains all the important threads including rooting L
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have all the guides open so I'll refer to that when the phone comes in later on in the week. I guess I could use cpu tuner after I gain root access. Hows L been working out for you so far on your device?
Don't buy a Nexus 5 just because the developer preview for L is here.
too late lol. and my GS4 is really beat up so I was looking to try out a nexus phone anyway. Thanks rootSU for including guides in the sig. they really helped and made the process really smooth and easy. going to be using this for awhile. hopefully battery isnt too bad on L. if so prolly put that slimrom on there
Few apps don't work presently but that goes without saying. Battery life is not bad at all. Sure do miss pie launcher and changing icon size from slimkat but I'll manage
Sent from my Nexus 5 using XDA-FORUM, powered by appyet.com
I've not tried L. I'll just wait for the slim release most likely.
Sent from my Nexus 5 using Tapatalk
HTC One M8 on Verizon. Android version 5.0.1. I did a lot of research yesterday, and could not find any working solution to root the phone. It's hard to find anything on Google because generally the information will be outdated (from last year or the year before). So can someone fill me in on what exactly I'd need to do? This is my first smartphone and I've never rooted an Android device before.
ziddy5 said:
HTC One M8 on Verizon. Android version 5.0.1. I did a lot of research yesterday, and could not find any working solution to root the phone. It's hard to find anything on Google because generally the information will be outdated (from last year or the year before). So can someone fill me in on what exactly I'd need to do? This is my first smartphone and I've never rooted an Android device before.
Click to expand...
Click to collapse
Assuming you are still S-On and locked then you are stuck without root for now.
BladeRunner said:
Assuming you are still S-On and locked then you are stuck without root for now.
Click to expand...
Click to collapse
This is what I was afraid of. How can I keep track of when there is an update to the situation?
ziddy5 said:
This is what I was afraid of. How can I keep track of when there is an update to the situation?
Click to expand...
Click to collapse
keep checking these forums and/or follow @teamandIRC on twitter
Rooting the already updated HTC One M8
It's going to be difficult. I've been scouring the webs for weeks looking for the answer to that one. The Sunshine S-off didn't work for me. The only way I can find right now to do this requires finding somone that has purchaced the elusive "HTC java card" sometimes called the HTC S-off card. They can s-off your phone in a heartbeat. Wish I had one, I just can't see forking over 375.00 to get one.
So if your S-off there is a root method available ? I haven't found it if there is.
I'm running 5.0.1 Verizon S-off
Thanks in advance
jjmstang said:
So if your S-off there is a root method available ? I haven't found it if there is.
I'm running 5.0.1 Verizon S-off
Thanks in advance
Click to expand...
Click to collapse
If you're already s-off then just install twrp and flash, reboot recovery and it should ask you if you want to install root
BladeRunner said:
If you're already s-off then just install twrp and flash, reboot recovery and it should ask you if you want to install root
Click to expand...
Click to collapse
It seems you have to be rooted to install TWRP........at least what found
You only have to be rooted to install it with their app. If you are s-off you can download it from their site and flash it with fastboot.
mpappas87 said:
You only have to be rooted to install it with their app. If you are s-off you can download it from their site and flash it with fastboot.
Click to expand...
Click to collapse
I followed this method and I have re-gained root
http://forum.xda-developers.com/ver...ow-to-root-ota-pc-s-off-t3048604#post59750567
Now I'm going to try and flash the Dragon ROM with Sense 7
Thanks again for the help
same boat ; old filmware?
just received this HTC One M8 thru verizon, lollipop 5.0.1 after day 2 OTA update. I've been rooting every device i've owned since 08. Busy with daily tasks I haven't had a chance to sit and try unlocking bootloader until this weekend. I hit a wall when HTCdev returned an error after entering the identifier token \(^~^)/ . I did some reading, couldn't find anything.
I'm coming from a xt912 I've pretty much squeezed all I can get out of it since I got that brand new. I put CM12 on that just recently this HTC makes that the moto seem primitive. After bricking that (moto)spyder a few times flashing bad zips or doing things out of sequence I've put it thru the ringer and used RSDlite to just start from scratch. I have also found these device can put up with a lot and still bounce back. Geeze, I have three years of continuous text and data backed up on SD, lol . Something I haven't tried and wonder, does anyone know, is there any old VZW filmware for this M8 maybe 4.4.2 and try un locking from that point or Does the token id stay the same no matter what filmware?
Htcdev won't work on our phone because it's blocked by Verizon. Also, it's not possible to downgrade firmware or the OS without having s-off. At this time there's no way to get s-off on lollipop so you're pretty much stuck where you're at until an exploit is found by someone. Sunshine works for anything up to 4.4.4 but it won't work on a Verizon phone that's running 5.0.1. About all you can do right now is wait to see if Jcase and Beaups come up with a way to make it work on a Verizon phone too. I know that's not what you want to hear but that's how it is at the moment.
benjdevel said:
I've been rooting every device i've owned since 08. weekend. I hit a wall
Click to expand...
Click to collapse
Okay, glad I didn't spend too much time trying to figure this out, never rooted a device before
Gotcha . ...Stupid vzw ? I glanced at a procedure to unlock SIM. Have no idea if that would help anything. Havent tried it. Ill have to keep a watch out for something. Really compaired to that spider this thing is like a ferrari. Not too much bloatware. Lollipop rocks and knowing Im up to date for the most part calms me a little. I still dont like the idea of not having complete control of my device. I've already received a few notification marketing related from verizon that i could not close unless i looked at it. I did notice control over saving things to my ext sd i do like. I am a student just getting into the ist world.wish there was something i could help with. 5 classes is killing me at the moment though. I did also try to install an imsi catcher apk updates version and it seemed like it ran fine. I could of swore that app needed root access. I could be wrong with the newest version though.
Joint Java Card?
Same boat (Verizon, htc one m8) . . . For some reason I was thinking Lollipop was the update which was still able to be handled by Weaksauce 2. So I accepted the OTA, without thinking. -hadn't gotten around to s-off, etc., before this time around.
So, in some 2013 posts, I saw that some people had tried to pool resources and share a Java Card, etc. But sending phones to a "card keeper", is expensive, and unsafe (besides having to live without your phone for a few days.). jcase, on their company's IRC support channel, indicates that the card is more than just a simple microSD card, which one might be able to dd a filesystem image from (i.e. copy it for distribution). That's entirely possible, since all SD cards have micro-controllers for dealing with failed sectors, etc (check out "Bunnie's Blog"). Basically, the controller could make it tough/impossible to access part of the card, and can take care of decrimenting credits, encryption, signing, etc. Even if it were a basic SD card, the use of signed binaries, and external license/resource server, etc. could still make it tough . . . -although the card I found states it needs no internet connection. It would be much cheaper to send the card, rather than phones. But how to coordinate and pool the cost seems like it could be a pain?
So here's what I'm thinking about:
Someone (me?) could purchase a legit, new htc Java Card. After I use my 2 or 3 credits to s-off/unlock my phone, I could put the card on, say, ebay for maybe $5 less than what I bought it for. Then, another person could use some credits, then sell it again, for a little cheaper, etc. If we want to keep it "in-house", we could just send to each other and pay with PayPal or Google Wallet. But, with e-bay, one could just copy/build on the ad the first person started. Take a picture of your phone's screen, when the remaining credits are shown, and put it on the ad. With 2000 credits, my conservative estimate is that it could cost less than 72 cents, for each unlock. The $5 incremental discount might be close enough to cover re-shipping costs.
The Sunshine guys have, for free, helped many of us over the years. So I was planning to purchase their solution, if it worked for this situation. But their download page states that "Verizon 5.0.x users will have to wait until we update.". They indicate they could get us supported soon, but they also indicate that Lollipop is much more secure, with SELinux updated and better enforced., etc. So I am a little concerned about when that will actually happen. I see they've been posting updates for Motorola, and making sure people are able to pay them via PayPal, etc. But nothing yet for Verizon 5.0.x.
Does anyone know/recall how long after the last android update, someone came up with a root exploit? I'm just trying to get a rough guesstimate about the minimum time people will have to wait this time. -then add time because Lollipop is apparently significantly more secure. I guess I don't completely mind that my phone might be secure enough to not make it tougher for someone to get into the deepest parts of it, without specialized hardware (Java Card), if I were to lose it.
But, really, what Verizon and htc and others have done to these devices . . . They are, essentially, specialized computers. It would be like if Dell or another computer manufacturer sold you a computer, without allowing you access to your administrator account (and no clear/easy way to boot from another drive, to recover/fix things, etc.). That's crap.
I dunno. What do people think? I suppose I could just try it, and see.
Are new devices updated already? If I were to get a phone from verizon today will it already have the Lollipop update or would I get a still root-able device that I can deny the update?
libredroid said:
But, really, what Verizon and htc and others have done to these devices . . . They are, essentially, specialized computers. It would be like if Dell or another computer manufacturer sold you a computer, without allowing you access to your administrator account (and no clear/easy way to boot from another drive, to recover/fix things, etc.). That's crap.
I dunno. What do people think? I suppose I could just try it, and see.
Click to expand...
Click to collapse
I like the idea of that Java card:good: and I completely agree with you on how wrong it is restricting administrative rights, especially considering these things are comparable to a new computer.
dimsumx said:
Are new devices updated already? If I were to get a phone from verizon today will it already have the Lollipop update or would I get a still root-able device that I can deny the update?
Click to expand...
Click to collapse
No guarantees either way.
What is the status on SunShine for our device?
I got the Java Card.
@vazersecurity: still "Verizon 5.0.x users will have to wait until we update.", as of today.
I got the card, as previously proposed, and was able to get S-Off on my USA-Verizon HTC One M8 with the Lollipop OTA.
I needed to download and place two files in the root of the card (now done).
I then (CID changed) was able to use htcdev.com to unlock my bootloader, and ultimately gain root. I'm now happily running a current Cyanogenmod ROM. To regain some functionality from my camera, etc., I installed the htc camera, HTC Gallery, and Zoe apps from the Play store.
So I've already created a listing for the card on eBay. I assume the forum rules won't allow me to post the link. But I, honestly, always intended to use that as a way to make it more convenient to share with a community of people who wish to join in. -not to try and make any money off the card. Again, rather than have people ship phones to one person (with the shipping cost, and being without their phone), if figured it would be cheaper, and less disruptive, to ship the actual card. So, you'd purchase the card from the previous user, then re-list it for a bit less than what you paid for it. With the starting cost and credits, S-Off is about 30 cents, each. As the card credits get used up, it gets cheaper. Maybe each person would end up paying a few dollars for S-Off, when you factor in the shipping.
Maybe a moderator could chime in about whether it might be OK to post a link to this "community-intended" listing. -or suggest a better contribution/distribution method.
Also, since many users in our situations have been out of luck regarding S-Off, for a few months now, might a moderator or someone suggest/implement a way to post/place this information more prominently, in the forums?
Thanks.
THE POLL IS CLOSED BECAUSE OPTION #2 REACHED 90%
Now I've found a way to hide apps without root, and when I publish it, how would you want it? I'm helping @LoneFlux with his new "Amazon Fire Utility" and I can add the hide feature there, or open source the method.
But open sourcing the method will cause Amazon to patch this in a whiz, and embedding this in the utility will take time maybe up to a month. So what will you like?
(Hiding is not just hiding from Launcher, it's more like disabling, the app never opens, and doesn't hog up the memory, and almost nothing in the system knows that the app is there.)
About the time and effort, the utility does this in ~1.5 seconds per app, when manually it will take 1 to 5 minutes of work per app.
PS. He is currently encrypting the utility so heavily, even Amazon will have a very hard time if they were to decrypt it. He used the powers of Visual Studio Enterprise to its full extent.
Supersonic27543 said:
Now I've found a way to hide apps without root, and when I publish it, how would you want it? I'm helping @LoneFlux with his new "Amazon Fire Utility" and I can add the hide feature there, or open source the method.
But open sourcing the method will cause Amazon to patch this in a whiz, and embedding this in the utility will take time maybe up to a month. So what will you like?
(Hiding is not just hiding from Launcher, it's more like disabling, the app never opens, and doesn't hog up the memory, and almost nothing in the system knows that the app is there.)
About the time and effort, the utility does this in ~1.5 seconds per app, when manually it will take 1 to 5 minutes of work per app.
PS. He is currently encrypting the utility so heavily, even Amazon will have a very hard time if they were to decrypt it. He used the powers of Visual Studio Enterprise to its full extent.
Click to expand...
Click to collapse
Take the extra time. The longer we cause a headache for Amazon, the longer they take to patch things. Though given the fact they can't seem to fix the rootability of the HD 10, I think we've got plenty of time, regardless of how long you guys wait. How many versions have they gone through already?
Sent from my Moto E4 using XDA Labs
DragonFire1024 said:
Take the extra time. The longer we cause a headache for Amazon, the longer they take to patch things. Though given the fact they can't seem to fix the rootability of the HD 10, I think we've got plenty of time, regardless of how long you guys wait. How many versions have they gone through already?
Sent from my Moto E4 using XDA Labs
Click to expand...
Click to collapse
I don't think they will EVER patch it. As a matter of fact they have already patched it. No one knows the reason for it to still work, including Amazon.
all HD8 and 10 devices are currently rootable so I don't see a need to publish this yet
Legitsu said:
all HD8 and 10 devices are currently rootable so I don't see a need to publish this yet
Click to expand...
Click to collapse
What? Only the Fire devices before Fire OS 5.3.1 are rootable, with the exception of HD 10. For example no one has rooted a HD 7 or 8 2017 yet, because they arrive with an unrootable version.
Supersonic27543 said:
What? Only the Fire devices before Fire OS 5.3.1 are rootable, with the exception of HD 10. For example no one has rooted a HD 7 or 8 2017 yet, because they arrive with an unrootable version.
Click to expand...
Click to collapse
I suspect it's to do with the kernels. I almost want to say Amazon threw an unpatched kernel onto the tablet or removed patches for whatever reason. I don't find it a coincidence this happened right after they patched 5.4.0.0-0.1. you can only patch or block so much of android before stuff breaks, at least when you butcher an Android OS like Amazon does. Same goes for us when we debloat...we can get so far before we reboot and the logo never ends. But on my HD 10, I have debloated beyond any debloat I've ever done and am still going. I might be writing a thread on this.
Sent from my Moto E4 using XDA Labs
IIRC, the fire 7 (2015) was easily rootable on 5.1.1 (ADB command). They blocked this with 5.1.2 and instigated anti-rollback, but this version could be rooted with Kingroot. Amazon blocked this quickly, but up to 5.1.4 you could still rollback to 5.1.2 and root. They then updated to 5.3.1.0 which was unrootable at the time and could not be rolled back. However, after a couple of months, Kingroot found a new exploit to root 5.3.1.0. This vulnerability must have been introduced by Amazon in the update as 5.1.2.1, 5.1.3 and 5.1.4 versions were unrootable at that time, and still may be. There is always a slim hope that Amazon will **** up at some point and release a rootable update for a currently unrootable tablet.
my bad I figured same software base it should work
its probly down to the SOC and as dragon said the kernel
the 8 runs a MT8163V/B Which is older and has a more mature kernel tree to pull from
but offtopic:
why has nobody unlocked the bootloader yet its mediatek its nowhere near as secure as a qualcomm SOC there isn't even any android verified boot to deal with
I been out of the game for awhile but theoretically it should't be to terrible to figure out how to generate the oem unlock 16digit code
Legitsu said:
my bad I figured same software base it should work
its probly down to the SOC and as dragon said the kernel
the 8 runs a MT8163V/B Which is older and has a more mature kernel tree to pull from
but offtopic:
why has nobody unlocked the bootloader yet its mediatek its nowhere near as secure as a qualcomm SOC there isn't even any android verified boot to deal with
I been out of the game for awhile but theoretically it should't be to terrible to figure out how to generate the oem unlock 16digit code
Click to expand...
Click to collapse
Hi,
It may be MediaTek, but we have some major problems with that,
1.) Obvoiusly, I don't think any developer in this forum is familiar with boot loader exploitation.
2.) The unlock code is already known, but the boot loader only accepts unlock.bins signed by Amazon.
3.) I think Android verified boot is implemented, we can't replace boot.img, or any boot-related partition, results in a bootloop.
Anyway, good luck to anyone trying to fight with that! :laugh:
DragonFire1024 said:
I suspect it's to do with the kernels. I almost want to say Amazon threw an unpatched kernel onto the tablet or removed patches for whatever reason. I don't find it a coincidence this happened right after they patched 5.4.0.0-0.1. you can only patch or block so much of android before stuff breaks, at least when you butcher an Android OS like Amazon does. Same goes for us when we debloat...we can get so far before we reboot and the logo never ends. But on my HD 10, I have debloated beyond any debloat I've ever done and am still going. I might be writing a thread on this.
Sent from my Moto E4 using XDA Labs
Click to expand...
Click to collapse
Yes, DirtyCOW is a kernel issue.
Supersonic27543 said:
Hi,
It may be MediaTek, but we have some major problems with that,
1.) Obvoiusly, I don't think any developer in this forum is familiar with boot loader exploitation.
2.) The unlock code is already known, but the boot loader only accepts unlock.bins signed by Amazon.
3.) I think Android verified boot is implemented, we can't replace boot.img, or any boot-related partition, results in a bootloop.
Anyway, good luck to anyone trying to fight with that! :laugh:
Click to expand...
Click to collapse
1. incorrect
2. care to share other devices have had there unlockbins brute forced the security on them isn't exactly milspec
3. no it isn't Verified boot is only on 6.0+
whats causing the bootloader is it failing the signature check which is not the same as verified boot
Legitsu said:
1. incorrect
2. care to share other devices have had there unlockbins brute forced the security on them isn't exactly milspec
3. no it isn't Verified boot is only on 6.0+
whats causing the bootloader is it failing the signature check which is not the same as verified boot
Click to expand...
Click to collapse
Thanks for explaining! If you have any ideas that maybe useful, please help with this,
I was able to pick up a 4G/LTE-enabled Galaxy NotePRO (SM-P905V) with official Samsung keyboard case and book cover, 64 GB SD card, and two chargers and USB cables on Craig's List for $200. Pretty good price.
Anyway, I'm excited to try out this tablet, particularly the S Pen features.
The latest Android version for this tablet is 5.1.1, which is a bit old. I believe I read somewhere on this forum that the specific SM-P905V model (Verizon) can now be rooted, and I may install a custom ROM based on Android 7.x or even 8.x, if available. A couple of questions:
1) Can anyone confirm that it is indeed possible to install custom ROMs on the SM-P905V?
2) If I install a custom ROM (say, LineageOS), do I lose any of the specific S Pen capabilities provided by the stock ROM?
3) I'm not on Verizon, and I currently have no plans to use the 4G/LTE capabilities (wifi only). However, if I did, can this tablet be used with a GSM provider, such as AT&T? Is this tablet unlocked and does it support both CDMA and GSM?
4) Anything else I should think of before I dive into this tablet?
Thanks!
--Ron
Still locked bootloader...for now!
Unfortunately, this device still has a locked bootloader. I am NOT a developer, but I am looking into trying to figure out how to take care of that.
I HAVE been able to achieve root on the latest build (basically the last official firmware released -- 5.1.1 P905VVRUBOH1 -- I have been stuck without root since I bought this thing a coupla years back as that update ruined the previous exploit).
To get root, I used a paid windoze app (after trying a bunch of other stuff and other free exploits, like towelrooot, kingroot, and kingoroot and a couple other paid ones) by iSkysoft which ran me about 30-35 bux for a "lifetime" (root 5 device) membership. To me that cost is worth it for root alone (even having to boot into windows....long time linux user). My long term goal is indeed to unlock the bootloader so I can build AOSP for this thing. To my knowledge I am the first to get root on that firmware (at least I haven't seen any other posts about it here) -- not that I consider this a real contribution, just found a method that worked for me and should work for others.
Bootloader unlock has been achieved on the Galaxy S5 which is a device contemporary to this one, so it should THEORETICALLY be possible. Thread on that is here: https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Creator of the above thread, xda user @beaups has hosted the files for S5 bootloader unlock here: https://github.com/beaups/SamsungCID
He indicates somewhere that this should work for other CID 15 devices (my P905V is indeed CID 15 EMMC...your mileage may vary -- check out his S5 unlock thread to find out how to verify what EMMC your tablet has once you have achieved root)
Aside from that all that remains is to build a version of TWRP for this thing and the ROM development can finally get rolling.
I look forward to seeing AOSP on this thing, but I am a grad student and don't have too much time to truly knock this thing out...perhaps you (or someone else) wants to take a crack at it now that root is back.
SM
SurfRodder said:
Unfortunately, this device still has a locked bootloader. I am NOT a developer, but I am looking into trying to figure out how to take care of that.
I HAVE been able to achieve root on the latest build (basically the last official firmware released -- 5.1.1 P905VVRUBOH1 -- I have been stuck without root since I bought this thing a coupla years back as that update ruined the previous exploit).
To get root, I used a paid windoze app (after trying a bunch of other stuff and other free exploits, like towelrooot, kingroot, and kingoroot and a couple other paid ones) by iSkysoft which ran me about 30-35 bux for a "lifetime" (root 5 device) membership. To me that cost is worth it for root alone (even having to boot into windows....long time linux user). My long term goal is indeed to unlock the bootloader so I can build AOSP for this thing. To my knowledge I am the first to get root on that firmware (at least I haven't seen any other posts about it here) -- not that I consider this a real contribution, just found a method that worked for me and should work for others.
Bootloader unlock has been achieved on the Galaxy S5 which is a device contemporary to this one, so it should THEORETICALLY be possible. Thread on that is here: https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Creator of the above thread, xda user @beaups has hosted the files for S5 bootloader unlock here: https://github.com/beaups/SamsungCID
He indicates somewhere that this should work for other CID 15 devices (my P905V is indeed CID 15 EMMC...your mileage may vary -- check out his S5 unlock thread to find out how to verify what EMMC your tablet has once you have achieved root)
Aside from that all that remains is to build a version of TWRP for this thing and the ROM development can finally get rolling.
I look forward to seeing AOSP on this thing, but I am a grad student and don't have too much time to truly knock this thing out...perhaps you (or someone else) wants to take a crack at it now that root is back.
Click to expand...
Click to collapse
……………………………
i have also SM-P905V and i live in Germany. Rooting with iSkysoft can help to make call and use the Note.???
SurfRodder said:
To get root, I used a paid windoze app (after trying a bunch of other stuff and other free exploits, like towelrooot, kingroot, and kingoroot and a couple other paid ones) by iSkysoft which ran me about 30-35 bux for a "lifetime" (root 5 device) membership.
Click to expand...
Click to collapse
I'm trying to find the software that you used to get root. I've googled iSkysoft, but they don't show any rooting software. Can you be more specific about what Windows app you used? Can you link to it?
I'll have to double check when I get home to that machine, but I'm pretty sure this is it:
https://toolbox.iskysoft.com/android-root.html
IIRC, it was ~30 bux to get credits to root 1-5 devices..
Thanks! I'll give it a shot.
SurfRodder said:
I'll have to double check when I get home to that machine, but I'm pretty sure this is it:
https://toolbox.iskysoft.com/android-root.html
IIRC, it was ~30 bux to get credits to root 1-5 devices..
Click to expand...
Click to collapse
Tom2112 said:
Thanks! I'll give it a shot.
Click to expand...
Click to collapse
Any luck with this if you tried it? I'm really looking to just enable more apps in the multi-window split screen app drawer so i can use any app in split screen mode, some aren't available when only stock.
dmxoneIuv said:
Any luck with this if you tried it? I'm really looking to just enable more apps in the multi-window split screen app drawer so i can use any app in split screen mode, some aren't available when only stock.
Click to expand...
Click to collapse
Sorry, I did not try it.