Related
Hello all,
Just a quick rooting question. Is there any reason to unlock the bootloader when rooting? According to some stickies, we can root without unlocking and I was able to root my friend's Captivate without unlocking anything. I am assuming we're unlocking the bootloader since it makes the rooting process easier as a hack isn't required? Thanks!
Sent from my Nexus S using XDA Premium App
It allows you to flash a custom recovery image to go ahead and flash a custom rom and radio
Sent from my HTC HD2 using XDA Premium App
Hi Dave,
Thanks for the info, but why didn't I need to unlock my friend's Captivate? We were able to get Clockworkmod Recovery on it without unlocking anything. Thanks!
Sent from my Nexus S using XDA Premium App
BlindWolf8 said:
Hi Dave,
Thanks for the info, but why didn't I need to unlock my friend's Captivate? We were able to get Clockworkmod Recovery on it without unlocking anything. Thanks!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
http://www.androidcentral.com/bootloaders-all-you-ever-wanted-know
The TL;DR of that article is that,
Every phone has a bootloader. The Nexus series (and now Sony Ericcson after filing out a form on their website) has a unlockable bootloader without the usage of any exploits. Phones such as the Galaxy S series (Vibrant, Captivate, Epic 4G, etc) -- mainly Samsung phones have weak bootloader protection.
HOWEVER, all of the other phones' bootloaders are unlocked due to a exploit. So yes, your friend did unlock the bootloader without actually knowing it.
The only phones that are unable to unlock the bootloader are Motorola phones because of the bootloader being signed.
But if you really want to know about bootloaders, read that article.
@dave: there is no such thing as a custom radio. The radio itself is not open sourced. But it allows you to flash a older version of the radio since results of radios vary between user. Some people may experience better connection with KB3 than KD1 and etc.
Thanks! It was as I thought.
Sent from my Nexus S using XDA Premium App
BlindWolf8 said:
I am assuming we're unlocking the bootloader since it makes the rooting process easier as a hack isn't required?
Click to expand...
Click to collapse
Correct. Most other phones require an exploit to root, the Nexus S does not - if you unlock the bootloader. Conversely, you might still be able to root the Nexus using an exploit, even if you want to keep the bootloader locked.
fallenguru said:
Correct. Most other phones require an exploit to root, the Nexus S does not - if you unlock the bootloader. Conversely, you might still be able to root the Nexus using an exploit, even if you want to keep the bootloader locked.
Click to expand...
Click to collapse
....? You just paraphrased what i said.
Sent from my Transformer TF101 using XDA Premium App
I have a related question. I relocked my bootloader after rooting. What exactly can I not do with it locked?
Maximilian Mary said:
I have a related question. I relocked my bootloader after rooting. What exactly can I not do with it locked?
Click to expand...
Click to collapse
It's kind of a PITA to flash an updated Clockworkmod Recovery. That's all I've found out.
BlindWolf8 said:
It's kind of a PITA to flash an updated Clockworkmod Recovery. That's all I've found out.
Click to expand...
Click to collapse
^ but to be honest, not to many things get changed within the recovery. Sure the modified Clockwork recovery gets updated. But the original clockwork from ROM Manager doesn't.. it'll work, but I don't see a reason on keeping the bootloader locked. No security is ever compromised.
zephiK said:
....? You just paraphrased what i said.
Click to expand...
Click to collapse
Funny, I actually paraphrased the OP. He was on the right track anyway, just needed some confirmation, not a whole paper Also there's a lot of stuff in there I don't really agree with all that much.
Maximilian Mary said:
I relocked my bootloader after rooting. What exactly can I not do with it locked?
Click to expand...
Click to collapse
Flash (and probably boot) stuff via fastboot.
Is there any way to root my phone.
The system version is 183.46.15.
If your boot loader is locked, no.
Sent from my HTC6525LVW using Tapatalk
Nope. Sorry. Both bootloader and root are patched.
RikRong said:
If your boot loader is locked, no.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Is there any guru working on the root? thinking about selling the phone if no hope
everseen said:
Is there any guru working on the root? thinking about selling the phone if no hope
Click to expand...
Click to collapse
Not gonna come as far as I can see from now. Just go ahead and sell it. Plenty of alternatives on the market.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
There are some RAZR M that are unlocked on Swappa as well.
tianor said:
Is there any way to root my phone.
The system version is 183.46.15.
Click to expand...
Click to collapse
Did u get unlocked, i am also stricken with it
Love Cyaan said:
Did u get unlocked, i am also stricken with it
Click to expand...
Click to collapse
No luck yet.
root and unlock 183.46.15
everseen said:
No luck yet.
Click to expand...
Click to collapse
Me too, me too!
Googleing this search daily " unlock 183.46.15 site:forum[.]xda-developers[.]com"
Checked ever corner of XDA, alas no solution on how to root and unlock 183.46.15
Devs @ XDA, come on champs gave us something, so can we also enjoy the privilege of CM12. Many are waiting for it fingers crossed
Mods/all, its only a humble request to Dev & not that if being annoyed.
Qualcomm patched the second layer (sbl2) of the second-stage bootloader, to take care of possible exploitation, effectively making it impenetrable. So for some individuals, we're pretty much out of luck. I wouldn't be sure of the possible exploits (the problem is, after that patch, it makes it even harder, although not impossible). Previous Kit Kat rooting exploitation relies on the permission requestion layer (futex) of the Linux kernel, as discovered by the former PS3 hacker, GeoHot, while it's patched by now. It's possible there is already a new rooting exploit by now, just don't hold the breath.
It's possible there is already a new rooting exploit by now, just don't hold the breath.
Click to expand...
Click to collapse
Can you please be more concretely?
I may not be up to date, been out of town for a bit, and figuring out a way to unbrick a few RAZR Ms.
However, the reason I said not to hold the breath is because of Verizon demanding a hard fix for rooting so that way almost any root exploits simply fail on arrival. This phone company also WANTS locked BIOS so no one can install custom recovery and OS "just because it put customer services in jeopardy".
That's really bad, can't believe that there is no chance to root or bootunlock this device.
By the way, do you know any way to disable/delete/freeze modem fast dormancy service without rooting phone? Or to made some changes in build.prop file?
Simply force close Modem fastdormancy first then disable it in app manager, it will then quit. And, editing build.prop requires root (write protection).
Force close works but disable button is inactive.
Sent from my XT907 using XDA Free mobile app
Ah, right.... I wonder why Verizon would disable some app manager features.
I'm outside of us, my carrier operates in gsm network and does not support fast dormancy, therefore phone reboots and can't wake up on power button when using h+. Thats why I need to edit build.prop and to dothis I need root access to file system.
Sent from my XT907 using XDA Free mobile app
Makes sense. However, I may look for new exploit, but since Futex is removed, it is not so simple.
Dr. Mario, are you developer?
Sent from my XT907 using XDA Free mobile app
Not officially, yet. But I know how the software works underneath the pretty UI, even down to the machine codes. I have been modding Android for 3 years.
I am little shocked to see nothing has come out yet on root for OE1. What are your guys thoughts? Is there any hope us on OE1 will ever get root back?
XNO said:
I am little shocked to see nothing has come out yet on root for OE1. What are your guys thoughts? Is there any hope the us on OE1 will ever get root back?
Click to expand...
Click to collapse
It's actually not Verizon, mostly. It's Samsung. I've seen the security on the Galaxy series grow since my GSIII.
Sent from my SM-G900V using Tapatalk
kfres39389 said:
It's actually not Verizon, mostly. It's Samsung. I've seen the security on the Galaxy series grow since my GSIII.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
No, it's Verizon...they blocked HTC from root and access to the HTC unlock option. There are no issues rooting T-Mobile or Sprint S5s.
And no one should ever say never. Exploits just appear...like Towel Root, Kingo Root and KingRoot in the past...no one is aware of their creation...they just show up and work. So one never never knows (seewhatIdidthere) :silly:
KennyG123 said:
No, it's Verizon...they blocked HTC from root and access to the HTC unlock option. There are no issues rooting T-Mobile or Sprint S5s.
And no one should ever say never. Exploits just appear...like Towel Root, Kingo Root and KingRoot in the past...no one is aware of their creation...they just show up and work. So one never never knows (seewhatIdidthere) :silly:
Click to expand...
Click to collapse
...but we can assume no one is working on rooting specifically the Verizon S5 with OE1 firmware.
Hmm, that's interesting. Thanks for the update. I used to be a serial flasher, but haven't quite kept up with the S5. Checking only now and then if any progress has been made on the latest update because I want to root because I miss some of those functions.
Sent from my SM-G900V using Tapatalk
XNO said:
I am little shocked to see nothing has come out yet on root for OE1. What are your guys thoughts? Is there any hope us on OE1 will ever get root back?
Click to expand...
Click to collapse
ldeveraux said:
...but we can assume no one is working on rooting specifically the Verizon S5 with OE1 firmware.
Click to expand...
Click to collapse
It is more that it is not a rushed thing, most people have a rooted version of OE1 that uses OD5 bootloader. So fewer people are without root. It is just a way to directly root OE1 that is not available yet.
kfres39389 said:
Hmm, that's interesting. Thanks for the update. I used to be a serial flasher, but haven't quite kept up with the S5. Checking only now and then if any progress has been made on the latest update because I want to root because I miss some of those functions.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
If you had not taken the OTA update or otherwise installed stock OE1 then you could have gotten a version of rooted OE1. It may be a while before people find anything to directly root OE1 or later, just because there are fewer people who need that, so not as much effort is being put into it.
Kaliaila said:
It is more that it is not a rushed thing, most people have a rooted version of OE1 that uses OD5 bootloader. So fewer people are without root. It is just a way to directly root OE1 that is not available yet.
Click to expand...
Click to collapse
yeah, thanks, I already knew that. There's still most likely no way to root stock OE1 in the future. :good:
KennyG123 said:
No, it's Verizon...they blocked HTC from root and access to the HTC unlock option. There are no issues rooting T-Mobile or Sprint S5s.
And no one should ever say never. Exploits just appear...like Towel Root, Kingo Root and KingRoot in the past...no one is aware of their creation...they just show up and work. So one never never knows (seewhatIdidthere) :silly:
Click to expand...
Click to collapse
I just upgraded to the S5 from Verizon. Will I be able to root? Will it do an automatic update when I turn it on?
So there is no way to root of you did update on your s5 for verizon?
It will come....we just gotta wait it out, or do it ourselves.
Sent from my SM-P905V using my telekinesis and long Johnson.
jtguldner said:
I just upgraded to the S5 from Verizon. Will I be able to root? Will it do an automatic update when I turn it on?
Click to expand...
Click to collapse
Got my new s5 2 weeks ago... it came with it already installed.
Does anyone know if this is legit and fully working?
http://www.xda-developers.com/galaxy-s7-root/
And can someone confirm it's not full of spyware etc. I've never heard of them before.
Supposedly Kingoroot & Framaroot are risky to use, so I would wait a bit more for a more "official" way to root it
MouldingClay said:
Does anyone know if this is legit and fully working?
http://www.xda-developers.com/galaxy-s7-root/
And can someone confirm it's not full of spyware etc. I've never heard of them before.
Click to expand...
Click to collapse
Stay away from that stuff...
If I see another kingo root post.... ????
Sent from my SM-N920W8 using Tapatalk
So is the link an advertisement that the Kingo people sponsored? I don't see the ability to comment on that page so if its not legit there's no way to know (except for posts like this in a separate part of the site) which would then beg the question, why was it allowed to be posted?
I have tried this three times on my Verizon Galaxy s7 edge, and it failed all three times. First time it froze at about 20% and the other 2 times it got to 100% but said it failed at the end.
Naw dawg. Wait for the devs to release a legit root method. Stay away from this noise.
But the advantages of Kingroot are plentiful.
According to the OP here on XDA, "KingRoot is an amazing tool for 'lazy people'"
It sends unspecified information from your device to a Chinese server
It roots your device using exploits potentially making it more vulnerable
It makes changes to /system and allows you to make further changes to /system, sometimes putting noobs in really awkward situations that are hard to get out of--they get de-noobified
Edit:
XDA finally took down the link to the Kingroot guide that didn't work:
http://www.xda-developers.com/galaxy-s7-root/
[/THREAD]
The XDA guide for root which was false, has now been removed
Sent from my SM-G935F using Tapatalk
CafeKampuchia said:
But the advantages of Kingroot are plentiful.
According to the OP here on XDA, "KingRoot is an amazing tool for 'lazy people'"
It sends unspecified information from your device to a Chinese server
It roots your device using exploits potentially making it more vulnerable
It makes changes to /system and allows you to make further changes to /system, sometimes putting noobs in really awkward situations that are hard to get out of--they get de-noobified
Edit:
XDA finally took down the link to the Kingroot guide that didn't work:
http://www.xda-developers.com/galaxy-s7-root/
[/THREAD]
Click to expand...
Click to collapse
My replÿ in response to kingroot. I have used it to root Samsung tab s and blu life xl using the app it's quick and it's easy to use as described I tried to root using kingroot on European s7 with app and did not work I'll try on computer next then use kingorooy
Good day all,
I noticed several cluttered threads in Q&A that are becoming more of a discussion than question and answer format.
I wanted to make this thread as a one stop shop for all things Root and Bootloader related for the G-930T (Tmobile Galaxy Note 7).
Please discuss root, bootloader and work with each other in here.
Please do not discuss the bounty in here, and do not clutter the bounty thread with casual conversation about root.
Cheers,
Baja
Sent from my SM-N930T using XDA-Developers mobile app
Well we know the Bootloader is locked and can only be unlocked by Samsung( That's not gonna happen).
Based on what happened and is continuing to happen with the S7 there is a possibility of achieving Root on the N7(ENG) which I will not be a guinea pig and try. I'm sure others will if and when it's available.
SBERG117 said:
Well we know the Bootloader is locked and can only be unlocked by Samsung( That's not gonna happen).
Based on what happened and is continuing to happen with the S7 there is a possibility of achieving Root on the N7(ENG) which I will not be a guinea pig and try. I'm sure others will if and when it's available.
Click to expand...
Click to collapse
I second this. Just wish we could keep samsung pay after root. Not gonna happen but wishful thinking.
Sent from my SM-N910T3 using Tapatalk
Just want to note that you may not want to take any updates if you plan on rooting in the future (if an exploit is available).
dirtymindedx said:
I second this. Just wish we could keep samsung pay after root. Not gonna happen but wishful thinking.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Not true on my Nexus 6 we could not use Android pay with root. But someone came up with a walk around systemless root and it worked.
Sent from my SM-N930T using Tapatalk
jason504 said:
Not true on my Nexus 6 we could not use Android pay with root. But someone came up with a walk around systemless root and it worked.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
he said Samsung pay...two separate paying system
Chord_Hugo87 said:
he said Samsung pay...two separate paying system
Click to expand...
Click to collapse
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
jason504 said:
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
not possible if you trip knox and in order to get root you need to trip knox.
jason504 said:
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
One of them is from Google and doesn't care about Knoxx and the other is from Samsung and does care about Knoxx. Two completely different things. The Samsung Pay not working after Knoxx is tripped has been going on for a year as of tomorrow. The systemless root that doesn't trip Knoxx is one thing but as soon as you start flashing, kiss Samsung Pay goodbye.
Yep, and worst of all. Once it's tripped, Samsung pay will never work again on that device
Sent from my SM-N930T using XDA-Developers mobile app
Luckily for me, if root becomes available its a no-brainer. Samsung pay doesn't support my bank, and I won't have a credit card. Even if Samsung Pay would work for me, it would still be an easy choice to have root instead. I would like to play around with altering the speaker volume, deleting bloatware, making tweaks, ad blocking, etc.
Did anyone ever get the files that Beans asked for over to him?
Why can't those of us with t variants just flash the unlocked w8 bootloader? Seems like we've been left an out? Yes?
Sent from my SM-N920T using Tapatalk
Rx8Driver said:
Why can't those of us with t variants just flash the unlocked w8 bootloader? Seems like we've been left an out? Yes?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
In order for you to flash anything to any bootloader, it needs to be unlocked. With it locked Odin says it can't. So till the note 7 gets unlocked (in time) we have to wait. Phone only few days old, be work around soon.
drum747 said:
Did anyone ever get the files that Beans asked for over to him?
Click to expand...
Click to collapse
Good question
@BeansTown106 did you ever get a Tar?
Sent from my SM-N930T using XDA-Developers mobile app
It appears this guy is in the process of getting the stock firmware uploaded
http://forum.xda-developers.com/showthread.php?t=3444003
Sent from my SM-N930T using XDA-Developers mobile app
ethanscooter said:
Just want to note that you may not want to take any updates if you plan on rooting in the future (if an exploit is available).
Click to expand...
Click to collapse
That is true. Android 7 Nougat will have more security features that Samsung is going to take advantage of with the Galaxy Note 7. That may make unlocking bootloader and rooting even more difficult.
-
It looks like the sprint guys have obtained an engineering bootloader/kernel. Someone may be able to do something with this for us..
Sent from my SM-N930T using XDA-Developers mobile app
I got the stock n930t boot.img but im wondering is how would i go by making a kernel "engboot". I also removed dm-verity but that didn't work. All i get is a failed message through odin. Another testing i have done is I even just modified one simple thing in the stock kernel say in default.prop ro.secure=1 to =0 and i still get a failed messsge. Once i flashed the stock unmodified version of the kernel i would get a success message and works which means any modification to the kernel will cause it to fail i just have to see what in the kernel checks for md5 changes or it may be something else if more devs can help together, then we can get this working.
jovy23 said:
I got the stock n930t boot.img but im wondering is how would i go by making a kernel "engboot". I also removed dm-verity but that didn't work. All i get is a failed message through odin. Another testing i have done is I even just modified one simple thing in the stock kernel say in default.prop ro.secure=1 to =0 and i still get a failed messsge. Once i flashed the stock unmodified version of the kernel i would get a success message and works which means any modification to the kernel will cause it to fail i just have to see what in the kernel checks for md5 changes or it may be something else if more devs can help together, then we can get this working.
Click to expand...
Click to collapse
Bro, please stop trying. This is obviously far above your skill level.
1. There is no way to convert a kernel to an "engboot."
2. The bootloader is LOCKED, so anything you do to the kernel's ramdisk will obviously not work because the whole point of dm-verity and a locked bootloader, among other things, is to stop the modification of system images, including the kernel ramdisk. Surely you didn't think it would be as easy as unpacking the boot.img, changing the ro.secure value from 1 to 0, then repacking..... did you?
3. The kernel doesn't "check" for anything MD5 related.
4. The bootloader is rejecting your changes, not the kernel.
5. Nothing you do to the boot.img, no matter how many devs you have, will do any good.
Hang tight, guys. We're trying everything we can.