Related
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
The K-Zoo Kid said:
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
Click to expand...
Click to collapse
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
unremarked said:
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
Click to expand...
Click to collapse
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
The K-Zoo Kid said:
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
Click to expand...
Click to collapse
unlocking the bootloader and rooting are two different things
jblade1000 said:
unlocking the bootloader and rooting are two different things
Click to expand...
Click to collapse
Ahh i have no idea what unlocking the bootloader does then.
The K-Zoo Kid said:
Ahh i have no idea what unlocking the bootloader does then.
Click to expand...
Click to collapse
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
unremarked said:
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
Click to expand...
Click to collapse
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
The K-Zoo Kid said:
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
Click to expand...
Click to collapse
Yes, to mod/flash roms you need to unlock the bootloader. It's possible that sometime down the road someone may develop a method of gaining root access on the phone without touching it, but it's unlikely given the fact that we can both unlock and lock the bootloader very easily.
Right now, the answer is... more or less. If you make a NAND backup in Clockwork Recovery/Rom manager of your stock ROM, you can restore back to that, fastboot flash the closest thing we have currently to the stock recovery(check development section for this), then relock the bootloader. This will give the phone all appearances of being stock. Unless Samsung has something deep in the system files tracking the number of times you've unlocked/locked(which I doubt, since I'm sure such a system would have been found by now), you should be good to go.
Most people who have returned the phone to Best Buy have noted that they don't even power on the device or check to see if the bootloader is unlocked or if there's a custom recovery on there. But your mileage may vary.
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
I had clockworkmod installed but used rom manager to flash the 2.3.1 update and i've now got the stock bootloader back. I guess the ota update does the same? It would seem that getting back to stock is pretty easy.
Sent from my Nexus S using XDA App
xspyda said:
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
Click to expand...
Click to collapse
My apologies, I posted that before I came to the same understanding regarding the stock recovery.
Like the poster above me mentioned there is a NAND backup of stock 2.3.1 you could restore to which has the stock recovery.
Sent from my Nexus S using XDA App
Thanks for the clarification. I'll do some more reading in the dev section
Thanks a lot, this really helped me out a lot. I will proceed to rooting
So, just want to make sure I have this straight... You unlock the bootloader, load custom recovery, SU, and now phone is rooted. If you lock the bootloader, you lose root?
For me, I'm not big on custom roms since I just don't have time to keep things up to date or participate in the bug process, but I do like to maintain backups with Titanium (my primary reason for rooting). So by locking the bootloader down I will not be able to use Titanium. Furthermore, unlocking the bootloader wipes the device. So is there a reason one would not want to keep the bootloader unlocked? Have I completely misunderstood the system?
Hello everyone, Im new here so please dont kill me if this is a common question. I have searched all over but cant find the answer I need. Im excited to learn from all the wonderful information here and cant wait to get started.
Anyway, I had a Nexus S 4g flashed to work on Boost. I would like to root it so that I can change some things. However, I do not know if my phone was previously rooted. Is there anyway to find out? If it was, and I rooted it again, would that cause problems? Also, does rooting the phone cause problems with the flashing, or will it keep all of the necessary network information intact (so that it doesnt screw up my service)?
Rooting doesn't cause problems with the flashing, it just -potentially- opens up the system to damage. This is a user responsibility and not a fault of the rooting process; it's a possibility of having too much power over the system.
Most likely it would have had the bootloader unlocked and have been rooted. Turn off the phone and turn it on again by holding Vol. Up and Power simultaneously for a few seconds. If it was rooted, the best way to know is if it says "bootloader unlocked" in the upper half of the screen. If not, there is a high chance it isn't CURRENTLY rooted. If it is unlocked, the most work you need to give root access to android is going into recovery and installing a .zip file.
Exactly so after finding that out just look over one of the many guides we have here at XDA to flash the superuser package.
Sent from my Nexus S
I didnt see anything saying unlocked. I see 'Lock State - Locked', so Im assuming this means that it is not currently rooted. I guess now I will go through some guides and learn which method would be best for me. Thanks for the quick reply and help.
Most likely you aren't rooted either - you can test by typing "su" in terminal emulator.
Just remember if u unlock bootloader the internal data and sdcard will all be deleted.
Okay so I just have a few questions about rooting my phone before I do it, since I saw the root here that works for the most recent OTA update.
1) If someone happens with my phone (either bricking it from rooting or something inconsequential) will they not replace my phone due to it being rooted?
2) If they won't replace it due to being rooted (if it wasn't bricking), is there an easy way to unroot the phone?
3) I can't tell from the instructions, but I'm pretty sure some others have said that it might require you to restore factory settings, does this one require that?
4) The thread says that it is now impossible to unlock the bootloader, does this also mean that you can't use a custom ROM? How exactly do you add a ROM?
Sorry for all the questions, I've never rooted an android device before, and I don't have the time or energy to go running around Google/forums trying to find these answers.
Thanks in advance!
EDIT: yes I know i've already asked 2 of these questions, but I'm a stupid poop who needs validation.
wholocked10 said:
Okay so I just have a few questions about rooting my phone before I do it, since I saw the root here that works for the most recent OTA update.
1) If someone happens with my phone (either bricking it from rooting or something inconsequential) will they not replace my phone due to it being rooted?
2) If they won't replace it due to being rooted (if it wasn't bricking), is there an easy way to unroot the phone?
3) I can't tell from the instructions, but I'm pretty sure some others have said that it might require you to restore factory settings, does this one require that?
4) The thread says that it is now impossible to unlock the bootloader, does this also mean that you can't use a custom ROM? How exactly do you add a ROM?
Sorry for all the questions, I've never rooted an android device before, and I don't have the time or energy to go running around Google/forums trying to find these answers.
Thanks in advance!
EDIT: yes I know i've already asked 2 of these questions, but I'm a stupid poop who needs validation.
Click to expand...
Click to collapse
first, rooting your voids the warranty, so technically, they (either VZW or Motorola) are not obligated to replace it. that being said, you can always play dumb and say that you accepted some OTA install, and now the phone won't boot up. usually, VZW will try to restore the phone, and if not, they'll replace it - no worries.
2.) I believe there is an unroot method, but I have not explored this. try doing a search on this forum for "unroot razr m"
3.) restore factory settings could unroot - check the threads
4.) you can still install a custom ROM, but you'll need to install Safestrap first. however, the custom ROMs available for SS are out-dated, and I don't think that any devs will be providing any going forward. however, I would not be too discouraged by this, as the phone is very solid stock. so rooting is the key to remove the bloatware to help increase battery life, increase performance, and reduce excess data usage.
hope this helps.
While I am an advocate for device customization and modifications, I also believe there is an inherent need for locked bootloaders. When we unlock a BL and leave it that way so we can run custom ROMs, root etc, we sacrafice the security it provides allowing our devices to be tampered with or redistributed after a theft. I've seen the PSA advising people not relock their bootloaders on anything except stock. That is entirely true for Verizon and EE pixels that were never intended to be unlocked in first place. However I believe its entirely possible to boot properly self signed images on unlockable devices after re-locking.
Now, I'm not saying we should go around re-locking bootloaders with custom firmware installed there's a process. I've done a bit of reading on verified boot. I am interested in utilizing the "YELLOW STATE" so we can run self signed boot images using an "embedded certificate" along with dm-verity disabled. The problem is how can we self sign our boot images allowing boot to continue without compiling from source?
https://source.android.com/security/verifiedboot/verified-boot.html
https://mjg59.dreamwidth.org/31765.html
I found some information & maybe a more experienced DEV can shed some light on if its possible with our Pixel devices. That's really the goal of this thread, to start a discussion which I think is extremely important & hopefully turn into a guide or tool. We shouldn't completely sacrafice security to utilize root or custom ROMs. On my N5X I have a locked bootloader and modified boot/system with Allow OEM unlock disabled. Difference with our Pixels and Nougat BLs is verified boot is strictly enforced.
Please excuse me if this thread seems jumbled or all over the place. I really do want help with this idea tho to help inform and keep us secure. Any input is appreciated.
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
I still wouldn't do this. What's the point? You will still pass safety net with custom kernel.
As for security you, your device still needs to be decrypted to use TWRP. It should still be as secure. I guess someone can wipe your device if they get ahold of it but that's not really a security risk.
Risk is still huge locking your device with a custom OS.
Sent from my Pixel using Tapatalk
milan187 said:
I still wouldn't do this. What's the point? You will still pass safety net with custom kernel.
As for security you, your device still needs to be decrypted to use TWRP. It should still be as secure. I guess someone can wipe your device if they get ahold of it but that's not really a security risk.
Risk is still huge locking your device with a custom OS.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
It has nothing to do with passing safety net. TWRP can only access the data after the pin is input, true, but leaving a device with an unlocked boot loader leaves the ability to flash modified boot images (a huge attack vector). This is to keep your device yours if it falls into a theives hands. You can not have device protection features on a unlocked Allow OEM unlock device. You're right there is risk but being careful can alleviate the risk. I do this because I want my phone to be a trackable paper weight if somebody takes it. I have established my own chain of trust outside of googles. I have even modified my TWRP side of boot.img to only start with my PC using adb-keys.
Which risk is greater. The risk of losing an unlocked device and it falling into the hands of someone that knows what to do or bricking it relocking it.
I vote the latter.
Its not re-locking that bricks... Its disabling the allow OEM unlock in dev options & screwing with stuff afterwards that may cause a bootloop. As long as you have a signed boot image in place with TWRP or stock recovery that uses your own keys the risk is minimal.
Simple rule... With a locked boot loader on a device where verification is strictly enforced always leave that option ticked if modifying anything.
I'm sorry but people are misinformed. Locking the boot loader doesn't brick if you have a custom ROM in place any more than a stock ROM. Its screwing with things or using a poorly dev'd ROM. If you are like me and can set something up the way you like once and not screw with it you'll be fine. If you do wanna screw with something remember to check allow OEM unlock in dev opts. Don't uncheck until you're 100% sure. It really is that simple.
If you are leaving the toggle open what have you accomplished when it gets stolen? They just issue the fastboot command to unlock it. Yea, it wipes data at that point. But I honestly can't think of anything on my phone that is confidential.
When I'm out n about and using my phone normally (i.e. not modding, flashing etc) I put the toggle to off. If I'm planning on changing anything I toggle it back on & if something causes a bootloop (most probably user error) I can recover. I don't think most people who steal phones care about data either but I keep a lot of keys, passwords etc to networks in my devices storage. I admit its not for everybody, just a way to be more secure and protect a $700+ investment. My phones bootloader isn't just locked, its locked with a persistent root ssh backdoor integrated into system so I can maintain control in the event.
want to re-lock my boot loader ?
Geofferey said:
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
Click to expand...
Click to collapse
hey,
I as well as plenty of others thought I was clever unlocking it as I mainly wanted to unlock it from EE UK network , its not been touched since ,no custom rooms or root but after reading people are trying to Re-lock it and getting bricked im too scared too try lol its only phone ive got ? Appreciate any help please x
---------- Post added at 10:57 AM ---------- Previous post was at 10:21 AM ----------
sally76 said:
hey,
I as well as plenty of others thought I was clever unlocking it as I mainly wanted to unlock it from EE UK network , its not been touched since ,no custom rooms or root but after reading people are trying to Re-lock it and getting bricked im too scared too try lol its only phone ive got ? Appreciate any help please x
Click to expand...
Click to collapse
Sorry Duhhhh !! Custom u said lol
Geofferey said:
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
Click to expand...
Click to collapse
Geofferey, Do you happen to know if these commands are still right with LOS 17.1 / Android 10?
(Or does anyone else know?)
PS: Sorry everyone for pumping such an old thread
nullstring2 said:
Geofferey, Do you happen to know if these commands are still right with LOS 17.1 / Android 10
Click to expand...
Click to collapse
Unfortunately no. Now there is avbtool and the process is actually a bit more complicated. Somebody wrote a guide on how to use it externally for another device but I couldn't even follow. I actually find it easier to get the sources for whatever ROM it is I'm trying to sign and set the signing params in config before build.
Here is the guy who did it usually avbtool externally
https://forum.hovatek.com/thread-32664.html
Many instructions here
https://android.googlesource.com/platform/external/avb/+/master/README.md
Geofferey said:
...but I couldn't even follow. /QUOTE]
Well, thats an intimidating introduction, but I'll take look.
That guide appears to be talking about mediatek CPUs which makes it a little confusing.
Any hint on how to get the vbmeta signing key for the google pixel?
Click to expand...
Click to collapse
nullstring2 said:
Any hint on how to get the vbmeta signing key for the google pixel?
Click to expand...
Click to collapse
If you mean how to make your own key to perform signing then
Code:
openssl genrsa -des3 -out avb.pem 2048
If you're asking how to get the same key that Google used to sign vbmeta, it ain't ever gonna happen.
Geofferey said:
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
Click to expand...
Click to collapse
Is there ANY way to do this on Xperias or LGs?
Geofferey said:
It has nothing to do with passing safety net. TWRP can only access the data after the pin is input, true, but leaving a device with an unlocked boot loader leaves the ability to flash modified boot images (a huge attack vector). This is to keep your device yours if it falls into a theives hands. You can not have device protection features on a unlocked Allow OEM unlock device. You're right there is risk but being careful can alleviate the risk. I do this because I want my phone to be a trackable paper weight if somebody takes it. I have established my own chain of trust outside of googles. I have even modified my TWRP side of boot.img to only start with my PC using adb-keys.
Click to expand...
Click to collapse
It has ALL to do with safetynet/play integrity.
I wouldn't care to leave my bootloader unlocked otherwise.
But I want a rom that passes all security standards without "tricks".
Guys,
I have some very noob questions about flashing that I would like to solve :
1) is normal that fastboot connection works only after setting the device for "allow own unlock" and "USB debugging"?
2) I might flashing my devices without unlocking the bootloader? And what about flashing original firmwares from Motorola?
(I ask because my bootloader is locked under status "2")
2) I tried to flash my device and, despite of several "preflashing" errors, my device still showing status 2 on bootloader, but it started showing that "unlocked bootloader warning" when it starts, is that normal? How to solve it?
3) I might flashing an older firmware (update September ) than I already have in my device (December)?
4) what is the function of recovery mode on bootloader ? I
Sent from my XT1575 using Tapatalk
Belotto said:
Guys,
I have some very noob questions about flashing that I would like to solve :
1) is normal that fastboot connection works only after setting the device for "allow own unlock" and "USB debugging"?
2) I might flashing my devices without unlocking the bootloader? And what about flashing original firmwares from Motorola?
(I ask because my bootloader is locked under status "2")
2) I tried to flash my device and, despite of several "preflashing" errors, my device still showing status 2 on bootloader, but it started showing that "unlocked bootloader warning" when it starts, is that normal? How to solve it?
3) I might flashing an older firmware (update September ) than I already have in my device (December)?
4) what is the function of recovery mode on bootloader ? I
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
OK...My first and main recommendation is DO NOT start trying to flash, mod, or do anything outside of using the phone as intended yet. These questions show that you have very limited knowledge on these subjects and if you continue as is, you will most likely get yourself into a bind you can't get out of, such as hard bricking your device.
Questions 1 and 4 are Bootloader/Fastboot/Rooting 101 topics. Until you have read up thoroughly on these, please don't think about proceeding. The rest of your questions have been answered here in the forums. I can't stress this enough: RESEARCH, READING, AND READ SOME MORE!!! No one here is obligated to help you fix any mess you get into so you need to be able to help yourself first. If you have attempted to fix an issue, and can give some details on what has been tried, you will find that most likely, there will be some who will step forward to assist, but most will not rehash a full step by step of everything.
Please do not think I am trying to blow you off. I am merely trying to prevent you from creating a problem that cannot be fixed. Having at least a basic working knowledge of how FastBoot, Bootloader, and flashing ROMs work on this device is a must. But I will answer your question 3: Do not under any circumstances try to "downgrade" your stock rom on the phone to a previous security update. This does create major issues.
@Belotto
2. Only upper/the same version of stock rom.
Status code 2 - locked by user. Did you buy used phone?
4. Recovery mode(stock, 3e) is for factory reset f.e.
dzidexx said:
@Belotto
2. Only upper/the same version of stock rom.
Status code 2 - locked by user. Did you buy used phone?
4. Recovery mode(stock, 3e) is for factory reset f.e.
Click to expand...
Click to collapse
I haven't. I have unlocked , used custom roms for a time and flashed stock and locked again before. Did it just following to guides available here.
In that time I did not have any trouble doing that lol
Sent from my XT1575 using Tapatalk
Belotto said:
I haven't. I have unlocked , used custom roms for a time and flashed stock and locked again before. Did it just following to guides available here.
In that time I did not have any trouble doing that lol
Click to expand...
Click to collapse
Just in case you are not aware, having an unlocked bootloader does not prevent you from taking OTA updates. You can just leave it unlocked. The unlocked bootloader warning doesn't bother me so I just ignore it.
If you just wanna get rid of bootloader warning then look at
https://forum.xda-developers.com/mo...o-remove-unlocked-bootloader-warning-t3201141
Make sure you are on stock(software​ status: offical)
You will recieve the ota
Thanks all you guys.
Despite of some strange things, I could take out the warning logo.
Now, its "oficial", status "2" and no warning. So I can sell it without discussion.