Related
I just had a quick questions about rooting.
I rooted my phone with motorchopper and things have been working great. Got rid of all the bloatware I didn't need as well as gave my device a quick clean. I've had little to no signs of lag(made in Korea). I'm new to the whole customization route. This is my first smartphone and I couldn't be happier with it
1. I rooted my phone successfully, however, I have heard somewhere else that the device needed to be bootloader unlocked before it is rooted. Now, motochopper, allowed it to find an exploit in the device. Is this, in any way, harmful for the phone if it finds an exploit? Most likely not, just curious. Dumb question
2. Does the device need to be bootloader unlocked before I am able to flash a custom recovery, ROM ect.? If the device turns out to be bootloader unlocked later on and released can I flash custom recoveries, make backups and use most tools successfully through ROM Manager? Or would it be best to do it through Odin and do things manually? Where would I be able to find essential files? Is odin specified for a specific device? Just curious
3.What ROM's would you recommend. Cynogenmod? I just want something that is lightweight, stable and functions well throughout the device. Where would be a good source to find good roms?
4. If the device is already rooted can I just start flashing custom recoveries, ROMs ect? Or would someone need to release an unlocked bootloader? How does unlocking the bootloader work? What are ways to do it? Flashing a file or doing something else. Idk..just curious I may be wrong.
I just want to know some good methods to make sure I don't brick this device. Of course backing up and recovering would do well. I've heard clockworkmod is one of the best custom recoveries you can use.
Thanks, in advance, for you help.
Hello parallel universe of Android tweakers. I have done a good hour's worth of searching and reading and just want to make sure I know what I'm getting into here. I would just do it all without asking for what I'm sure will be redundant confirmations from you, but it's not my phone (see sig).. it's for a friend who thinks my custom ROM is the shiz.
So, I just wanted to make sure I understand what I'll need to do in order to root her phone, install a custom recovery, custom rom and possible restore to stock if needed.
My friend has the SGS4 with AT&T and has the MF3 update.
1. Root via this method: http://forum.xda-developers.com/showthread.php?t=2387577
2. Install recovery via the Safestrap method: http://forum.xda-developers.com/showthread.php?t=2448925
3. Install custom ROMs via TWRP after using Safestrap method to install it
Coming from the Nexus 4 side, I'm finding I have it much easier than you guys, or though it seems. If you wouldn't mind, may I ask a few questions about the differences between the N4 and this, in regards to rooting/recoveries, custom roms and kernels, etc?
A. I think I understand, from my readings so far, that there is some importance of showing the bootloader as 'official' or something? Can someone explain?
B. As of now, there is no way to return to stock once a custom recovery is installed?
C. What is the kernel module zip that has to be flashed after a custom ROM? Does it mean I can't flash a custom kernel on her device?
D. Once the steps outlined in 1-3 above are done, should she ignore all OTA updates, and if she doesn't, what may happen to her phone, or the state of it (root access/recovery, etc.)?
Thanks for any help. If you guys have gotten these questions a hundred times, I'll apologize ahead of time. I'm only asking because I've actually done a lot of reading and am about to proceed. Hopefully what I've posted above is evidence of that.
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".
Hi there,
I found there is a thread describing how to root the US/Chinese model without unlocking the bootloader -
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
However it mentions that this'll brick the European model because of the included TWRP version and unfortunately I'm on a ZTE A2017GV1.0.0B08 (Android 6.0.1, Kernel 3.18.20).
Is there any news if this can be done now with the international variant -
I'm not interested in a custom ROM or updating Android, I'm happy at the moment with the 6.0.1 version I have, but really would like root for xposed framework, Titanium, Tasker ...
Is there a different TWRP version that can be used or is it not working due to the ZTE's signature key used?
Alternatively is there a way for the A2017G to re-lock the bootloader that's 100% working/safe, if you don't apply a custom ROM?
Thanks a lot for your help!
The answer you will find here
https://forum.xda-developers.com/showthread.php?t=3441204
This is the way I did it with my first A7
sent from zte axon 7 with tapatalk
Hi.
It didn't really answer the question : Is unlocking necessary to root, or can we root without unlocking ?
Every tutorials founds all follows the same paths : Unlock first, then root. But why ? is there a reason for that, or is it just a "since i'm rooting, let's unlock it while i'm at it" thing ?
(edit : Sorry 4 my english ... i hope i've been clear enough)
marcus.linkenbach said:
The answer you will find here
https://forum.xda-developers.com/showthread.php?t=3441204
This is the way I did it with my first A7
sent from zte axon 7 with tapatalk
Click to expand...
Click to collapse
Hallo Marcus
Danke fuer die Antwort -
Maybe I didn't fully comprehend the thread - I was under the impression that it bricked some A2017G, while not others and didn't want to take the risk.
Reading through the instructions - which of these steps did you take (and in what order)?
I read it that you do not need to flash TWRP? So can I just root the phone without bricking it and all is good as long as I stay with my 6.0.1 B08 version?
I understand the instructions as
- boot into edl
- install Qualcomm driver
- run axon7root to already root the device (backup seems to be done in the next step?! according to instructions).
However there is no axon7root version for the A2017G (B08) as it was removed due to TWRP?!
All I can find is the axon7backup tool (would you actually do this before you run the axon7root the first time?)
If you run the axon7root, did you do 'axon7root.exe -p 4 -b'
so that it only flashes the boot.img (not TWRP recovery) and therefore this is safe?
Sorry for the long essay, help is really appreciated!
Hey, sorry for the delay.
I am quite busy. I really don't know the procedere anymore. It is a long time ago. But if you would give me some time, I will have a look on it and will let you know. But why won't you unlock your bootloader? Without unlocking not everything runs as it should with unlocked BL.
OK. I will let you know.
Marcus
Sn8K said:
Hi.
It didn't really answer the question : Is unlocking necessary to root, or can we root without unlocking ?
Every tutorials founds all follows the same paths : Unlock first, then root. But why ? is there a reason for that, or is it just a "since i'm rooting, let's unlock it while i'm at it" thing ?
(edit : Sorry 4 my english ... i hope i've been clear enough)
Click to expand...
Click to collapse
Theoretically, yes, you can root w/o unlocking the bootloader. This is how things are done typically with certain manufacturers (LG, Samsung) that rarely offer BL unlocking. To be able to flash TWRP on a locked BL is even more difficult, as it would require a BL-level exploit. The reason that's not an option here is the ability to unlock, which precludes such development.
Hi Marcus,
Thanks a lot, that would be really great.
Regarding Bootloader unlock - I didn't buy the phone in the EU, hence my warranty would be void if I unlock it. And my warranty even comes with screen replacement (not that I ever cracked a screen, but there's always a first).
I have to admit that I'm tempted by Lineage OS, but for now (as I just bought the phone) - if there's a reasonably safe way to root without unlock, I'd prefer to just root and then maybe in a year's time or so switch to Lineage OS...
For now I managed to have my phone recognized as QUSB_BULK and I can boot into edl.
I was trying to use the axon7toolkit (1.1.1), but for whatever reason I cannot use it in commandline mode (maybe as there seem to be different versions, or maybe cause I am on Win7 32bit, no idea).
Any help would be really great!
Hi jeboo, Hi Sn8k,
Hope above explained my motivation, regarding root without unlocking - there's a thread about this
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
HOWEVER there are two problems:
1) The bootloader can stay locked as it's using a signed version of TWRP, which can brick your device (A2017G)
2) The linked axon7root.exe is not for my device (A2017G B08).
Having said that, some users have been successful with rooting this version, so there seems to be a way, if you get the steps right.
Whoooo? said:
Hi Marcus,
Thanks a lot, that would be really great.
Regarding Bootloader unlock - I didn't buy the phone in the EU, hence my warranty would be void if I unlock it. And my warranty even comes with screen replacement (not that I ever cracked a screen, but there's always a first).
I have to admit that I'm tempted by Lineage OS, but for now (as I just bought the phone) - if there's a reasonably safe way to root without unlock, I'd prefer to just root and then maybe in a year's time or so switch to Lineage OS...
For now I managed to have my phone recognized as QUSB_BULK and I can boot into edl.
I was trying to use the axon7toolkit (1.1.1), but for whatever reason I cannot use it in commandline mode (maybe as there seem to be different versions, or maybe cause I am on Win7 32bit, no idea).
Any help would be really great!
Hi jeboo, Hi Sn8k,
Hope above explained my motivation, regarding root without unlocking - there's a thread about this
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
HOWEVER there are two problems:
1) The bootloader can stay locked as it's using a signed version of TWRP, which can brick your device (A2017G)
2) The linked axon7root.exe is not for my device (A2017G B08).
Having said that, some users have been successful with rooting this version, so there seems to be a way, if you get the steps right.
Click to expand...
Click to collapse
Did you figured out a method to root the A2017G without unlocking?
I just got mine and need root for transferring all the apps from my old Nubia Z7....
Thx.
catadoxy said:
Did you figured out a method to root the A2017G without unlocking?
I just got mine and need root for transferring all the apps from my old Nubia Z7....
Thx.
Click to expand...
Click to collapse
You can't. Don't even try it if you don't want to face DFU...
Just use the same app that the phone comes with, I think it's WeShare or something like that. It should let you transfer all of your crap via a LAN wifi transmission (If you use a 5GHz hotspot it'll be fast as heck).
Or just unlock the phone. But don't relock it if you do, because you can make a huge mess
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.