Related
I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
mark1holland1 said:
I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
Click to expand...
Click to collapse
I didn't know that was ever possible on the Nexus 7. I bought one of the first available, and from the moment I got it I had to unlock the BL to root. Thought it was always like that. Nothing's changed as far as I can tell. On other devices, sure you can root with a locked BL, but for the N7, you've always had to unlock first, and with it being so easy, I don't think anyone's motivated enough to cook up a workaround.
absinthesummer said:
I didn't know that was ever possible on the Nexus 7. I bought one of the first available, and from the moment I got it I had to unlock the BL to root. Thought it was always like that. Nothing's changed as far as I can tell. On other devices, sure you can root with a locked BL, but for the N7, you've always had to unlock first, and with it being so easy, I don't think anyone's motivated enough to cook up a workaround.
Click to expand...
Click to collapse
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
mark1holland1 said:
I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
Click to expand...
Click to collapse
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
GedBlake said:
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
Click to expand...
Click to collapse
Many thanks for a recent concise and informative post!
I was mainly being lazy with regards to not wanting to wipe everything and start again! I have helium installed to back everything up, guess Ill try to get a clear day to do it all........
GedBlake said:
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hmm, wow thanks for the info. I never knew that! I just remember my first N7 every post said Step 1:Unlock your bootloader... lol had I known there was a way around it I might have tried it! But my first 16gb and my later 32gb were both unlocked and rooted within hours of buying them, so perhaps I just wasn't motivated enough to look for it.
I could see how or why that would be desirable though I guess... before I bought my S3, I had an LG L9 that the only way you could unlock the BL was to root then flash/update (LG Update tool hack) the firmware meant for the international version of the phone, which mirrored(!!!) the entire display both horizontally and vertically. Then fastboot the oem unlock and unlock the best way you could with that kind of touch screen lol, THEN re-flash standard rooted firmware for the US back over it... Seriously NOT worth it! Because even if the mirroring went away with the right firmware, the boot logo would still be mirrored and it was possible your screen would not return to normal. So forget about any warranty at that point. But, I gotta hand it to the devs on that device- now they were some motivated folks. They went to a lot of trouble to unlock that BL. You could root and install CWM without unlocking, but if you flashed CM and it was buggy or something, there was no turning back to stock. We were left with mods only unless we wanted to do alll that work.
That just reminds me how thankful I am for my S3 and N7s.
This question's bothering me a lot lately. I used to have a Nexus 4 and it was easy to flash a ROM without all that Knox eFuse flag thing. If you got in trouble with a specific ROM, you just ran that batch file that came with the factory image zip. Everything was fine. Chances of hardbricking it: 1:10²³. Pretty straight forwad. But what about the Note 3, specificly the n9005? What are the odds of actually fullbricking this device? What is it, that one individual must do to irrecoverably brick it?
I'm also asking because I feel an intense urge to play with AOSP ROMs as I did with my Nexus 4. Since the Note 3 has that Knox flag and costs up to 600€, I just wan't to make sure there's not much that I could do wrong. I'm aware that once I flash unsigned data, the Knox flag will change to 0x1.
The only full bricks I have seen were people who flashed the wrong ROM version on their Hong Kong devices. Those appear to have a different partition structure. Flashing the wrong pit file on those rendered their devices hardbricked. I didn't follow through on those threads so not sure if they found a fix.
I would say the most likely "hard brick" is your EFS. its not a hard brick by definition, but once you lose the imei and have no backup its pretty much game over for phone functionality. A phone that can't connect to mobile networks is a hard brick in my book.
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Scyntherei said:
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Click to expand...
Click to collapse
+1 the QFuse status didn't change when unlocking the bootloader. The media exaggerated about the qfuse and nothing has happened. Everything about the phone still works properly.
Thanks very much, I wasn't aware of this, I should read more. Awesome news.
But to answer the first question.
Very few people put in effort to root a phone with an unlocked bootloader, not matter what fuses are blown.
A phone with an unlocked bootloader has root by default.
Swatto86 said:
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
Click to expand...
Click to collapse
last i read you have to flash a kernel in order to root the phone therefore you need to unlock the bootloader to do so, i would like to just root myself but i don't know if you can.
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Why people are afraid to unlock the bootloader? Nexus devices don't lose the warranty when you unlock it, you can also lock it again.
Enviado desde mi Nexus 7 mediante Tapatalk
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
No
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
The answer is no.
To do what you want, someone would need to develop and exploit.
There is no motivation to do that when all one has to do is unlock the bootloader.
On phones where a bootloader unlock exists, root methods require unlocking the bootloader.
This is to install a custom recovery so yiou can flash SU.
Unlocked bootloader = root, no matter what.
You will need to invest the time and backup your device.
@TS, did you read the unlock/root guide in general section? It clearly states you need an unlocked bootloader + custom recovery to root your device..
Sent from my Nexus 5X using XDA-Developers mobile app
I think this should be possible now with Quadrooter vulnerabilities?
sushah23 said:
I think this should be possible now with Quadrooter vulnerabilities?
Click to expand...
Click to collapse
DOA.
But nobody is going to put in time and effort.
What is the point? Unlock the bootloader and flash. It does not void the warranty.
There is even a defined method to get the monthly security update.
With the exploit, it will only work until the next OTA patches it.
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
LiquidAlloy said:
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
Click to expand...
Click to collapse
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Jammol said:
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Click to expand...
Click to collapse
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
LiquidAlloy said:
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
Click to expand...
Click to collapse
In all honesty it's not even more convenient. Once you've used the command line you'll never go back to a toolkit. It's actually easier, much faster and you have way more control over what you do.
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
Use Helium app for individual apps backup. Worked great to backup a few apps/data when I changed from one Nexus 6P to another. Might be a bit buggy to get working to get the backup, but after that everything is fine.
you can do it with KINGROOT
Hello,
A few months ago, I was able to successfully root my AT&T S4 (SGH-I337, builld LRX22C.I337UCSGOK3) using KingRoot. The KNOX warranty bit was not set at the conclusion of the root process.
After wrestling with storage problems, including the "system memory" taking up 6.29 GB out of the meager 16 GB that is on this phone (preventing practically any Google Play updates from occurring, as the available space would always dip below 500 MB periodically), as well as performance problems (very long delays for some touch events and a general resentment of TouchWiz), I decided that enough was enough, and I decided to change my ROM/OS out for LineageOS.
LineageOS offers builds for jfltexx, which is reported to work for jflteatt since they are similar enough. I am not really willing to try "older" builds, as one of my goals is also to bring the security of the operating system up to date, so I am not exactly inclined to go for old CyanogenMod builds. The LineageOS install guide stipulates that I install TWRP to successfully install the OS via a supported recovery; however, the message SECURE MAGICCODE FAIL: recovery appears, as the upgrade process seems to be expecting something signed by Samsung (right?). Other guides warn that the stock recovery only allows stock OS installation and not custom operating systems, so I decided not to try that route. This effectively prevents me from installing LineageOS due to a problem that is inherent in OK3.
Why did I make the mistake to install OK3? More than a year ago, I decided to do the final update that AT&T pushed out for this phone. Thinking that it would be something significant, I went for it, only to find out months later that it was a minor update whose purpose was also to add an additional lock to the bootloader. As this phone is "fairly old" (is 2013 already considered ancient times?), I have not found many guides that cover OK3, and those that do pertain to either rooting the S4 (already done) or something about downgrading (but I can't really do that, seemingly due to the OK3 lock-in). Oops.
That said, is there any hope to bring more life out of my phone, or is it time to throw the phone out and buy a Pixel or related product like any typical consumerist would do? My goal is to move to another OS to end the storage problems and other quirks of this phone that I have grown to deplore; that is all I wish to attain.
The phone is relatively reliable: it had ~1200 hours of uptime before I had to reboot it a few days ago to fix a data connectivity problem. The battery is also very manageable and can last a day and a half in regular use, but it can last 2-3 days under maximum power-saving mode.
I have read the rules and done some research on this forum, among some others. Thank you for your assistance.
Upgrading the phone to 4.3 locked the boot loader which prevents the installation of TWRP.
audit13 said:
Upgrading the phone to 4.3 locked the boot loader which prevents the installation of TWRP.
Click to expand...
Click to collapse
I see; so I was already screwed when I had OK2?
oldmud0 said:
I see; so I was already screwed when I had OK2?
Click to expand...
Click to collapse
Yes, anything past MDL has the bootloader flaw patched. MDL firmware and below have a flaw in the bootloader that allows loki doki to be installed bypassing the bootloader lock so you can install TWRP recovery and custom AOSP ROMs.
Since you're on OK3, you're forced to use safe strap recovery and can only install custom touchwiz ROMs like golden eye and albe95.
If you want to read up on the MDL bootloader, I have written a guide here: https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
My wish is to escape TouchWiz, so I suppose I have hit a dead end.
Thank you for your help anyway.
oldmud0 said:
My wish is to escape TouchWiz, so I suppose I have hit a dead end.
Thank you for your help anyway.
Click to expand...
Click to collapse
If you want away from touch wiz, I think there's a Google play edition ROM for the galaxy s4 that you can use with OK3, but I am not too sure. I would just check the galaxy s4 ROM section for it. I'm on the MDL bootloader which allows me to use TWRP, so I don't know too much about safe strap recovery.
Even if one wanted to do a TouchWiz-based ROM, I don't think we on OK2/OK3 even have the option to install SafeStrap, so far as I can gather
Hold the phone, I think I've found something. Evidently we can Odin back down to NB1 and go from there! Experiments, here we come.
Yes, NB1 is as far back you can go I believe without bricking your phone.
I've been combing the forums for a couple of weeks trying to get information about upgrading my old note 4 (Verizon, MarshMellow). I wanted to use the Lineage OS 18.1 but I can't find a way to unlock the bootloader. I've tried every method without success. None of the temp root programs seem to work. Odin gets close and then fails at the end. Same for ADB. I can't seem to get a clear answer to a question: Do you have to downgrade to 5.11 before attempting any of this? If so, how is that done on this phone? It is alluded to but not clearly stated anywhere. I'm willing to do the legwork, I just need a clear starting point.
Thanks
To unlock a device's bootloader it's NOT required device's Android is got rooted.
To flash a custom ROM like LOS you have to find a suitable custom Recovery for your device and flash this as 1st thing of all things.
Thanks for the response. That's what has been confusing. Most of the procedures I've read (some of them older) state the the first step is to temp root with Kingroot or similar. These don't work on my phone so I haven't gotten very far. Others want you to unlock the bootloader first. Same problem, can't find a way to to that in this phone that works. I'm pretty OCD so I'll keep searching.
@docsquic
[Official] Note 4 Verizon Bootloader Unlock
Enjoy. Don't forget to thank beaups too, he discovered the eMMC backdoor and exploited it! UPDATE: [8/2/16] I have recompiled the binary to fix issues with older ROMs like 4.4. This should fix all the issues with "This is for samsung device...
forum.xda-developers.com
If you are using an SM-910 with a locked bootloader, like the 910V, then the answer is an unequivocal YES you must first unlock the bootloader before you can accomplish anything substantive with it, and to do that YES you must also downgrade to 5.1.1 to root it and unlock the bootloader. And your device must have a CID 15 eMMC chip to achieve any of this.