Hey Guys, I am curious as to if this device can be returned to stock after rooting / unlocking. I'm also wondering if we can root it and flash custom recovery without unlocking the boot loader. Also, once you have changed roms can you go back to the stock rom and ASUS not know?
pryorda said:
Hey Guys, I am curious as to if this device can be returned to stock after rooting / unlocking. I'm also wondering if we can root it and flash custom recovery without unlocking the boot loader. Also, once you have changed roms can you go back to the stock rom and ASUS not know?
Click to expand...
Click to collapse
Not sure I understand your first question. Rooting and/or unlocking does not remove your stock rom...
And no, you must be unlocked to flash custom recovery . And no, it is not possible to relock, so ASUS will know your device has been unlocked,
hmm.
bwiberg said:
Not sure I understand your first question. Rooting and/or unlocking does not remove your stock rom...
And no, you must be unlocked to flash custom recovery . And no, it is not possible to relock, so ASUS will know your device has been unlocked,
Click to expand...
Click to collapse
Lame Do you have to be unlocked to Root and Debloat?
no mate there is a way to root and keep you bootloader locked, its called motochopper and there is a guide on here
Rooting locked is sufficient to remove bloatware.
Sent from my GT-I9001 using xda app-developers app
Hi at all, if i unlock the BTL, i can lose the possibility of the OTA update ? also if i have the root and twrp ?
simo.scorpion said:
Hi at all, if i unlock the BTL, i can lose the possibility of the OTA update ? also if i have the root and twrp ?
Click to expand...
Click to collapse
No, you will not loose the OTA update. I did it and I got the first update.
after the ota update i lose root, twrp and BTL return locked ?
simo.scorpion said:
after the ota update i lose root, twrp and BTL return locked ?
Click to expand...
Click to collapse
You will most likely lose root and TWRP, but your bootloader should remain unlocked.
thanks guys, last question there is some risk to unlock the bootloader ?
simo.scorpion said:
thanks guys, last question there is some risk to unlock the bootloader ?
Click to expand...
Click to collapse
If you're worried about bricking the device, the risk is very low. All you are doing is simply typing "fastboot oem unlock". It isnt meant to be anything dangerous or risky.
In terms of security however, there are some risks. If your bootloader is unlocked, a thief can easily flash a recovery and pull your potentially important and private information/data. Although the likelihood of the thief knowing how to do this is very low.
Sir will this guide also work for Oneplusone on cm13-Incremental-OTA-Official?
searching everywhere but couldn't find any guide to unlock bootloader on official Cos13.If anybody has successfully unlocked his bootloader on official cm13 then kindly guide the same to me.
Thank You.
Regards,
Mr.Ak
What is a bootloader(tell me in simplest way)....Is unlocking the bootloader really required...? If not then please post another method for root......
ak_wolf007 said:
What is a bootloader(tell me in simplest way)....Is unlocking the bootloader really required...? If not then please post another method for root......
Click to expand...
Click to collapse
watch this video to unlock it https://www.youtube.com/watch?v=iIdJg7KNH3A
and a bootloader allows you to flash kernels/recovers/ and other custom things but only if it is unlocked.
with custom recovery you can install roms,make full system backup,and other things.
a custom kernel wil allow you to overclock cpu/gpu and more.
a custom recovery can be used to flash root.update zip.
but after unlocking bootloader you void your warranty . and your device got hard reset(factory reset)
it can be only unlocked if it is allowed to be unlocked.
android-vinay said:
and a bootloader allows you to flash kernels/recovers/ and other custom things but only if it is unlocked.
Click to expand...
Click to collapse
Not entirely true, at least to all devices. I have a Moto Defy which also has a locked bootloader, no way to unlock, running KK CM11. Developer @pedrodh has managed to create an app called "2ndinit" (1) which allows a second kernel to boot on top of the locked one, allowing to flash new builds despite the locked bootloader. Because of this, Defy is known as unbricable. Similar approach could be used on E3 if some devel take a look into this.
(1) http://forum.xda-developers.com/showthread.php?t=1032212
Regards,
mmerlone said:
Not entirely true, at least to all devices. I have a Moto Defy which also has a locked bootloader, no way to unlock, running KK CM11. Developer @pedrodh has managed to create an app called "2ndinit" (1) which allows a second kernel to boot on top of the locked one, allowing to flash new builds despite the locked bootloader. Because of this, Defy is known as unbricable. Similar approach could be used on E3 if some devel take a look into this.
(1) http://forum.xda-developers.com/showthread.php?t=1032212
Regards,
Click to expand...
Click to collapse
this required root.
for now you need to unlockbootloader to root xperia.
root ur device without unlocking
vinay said:
this required root.
for now you need to unlockbootloader to root xperia.
Click to expand...
Click to collapse
just use kingoroot or kingroot to root ur device no need to unlock boot loader for running those you will have root access but can't do the flashing part
I've a device that is S-ON , TWRP 3.0.2-0 recovery installed , unlocked USA. Was running CM13 and later a lineage build...i just wiped/ reflashed the stock boot and system image so i've got things more or less back to original. All's good. However my bootloader remains unlocked. Do i need to relock it to get Android Pay working again? I was able to add a card, but have not tested it in the real world yet. My understanding is locking the bootloader will erase my data. Given I'd like to try that Nougat flavor and I don't think that will come OTA with an unlocked bootloader, maybe now's the time sense I think i'll have to flash that manually
Sorry, still new to joy of working with these devices. Fun tho
mlecho said:
I've a device that is S-ON , TWRP 3.0.2-0 recovery installed , unlocked USA. Was running CM13 and later a lineage build...i just wiped/ reflashed the stock boot and system image so i've got things more or less back to original. All's good. However my bootloader remains unlocked. Do i need to relock it to get Android Pay working again? I was able to add a card, but have not tested it in the real world yet. My understanding is locking the bootloader will erase my data. Given I'd like to try that Nougat flavor and I don't think that will come OTA with an unlocked bootloader, maybe now's the time sense I think i'll have to flash that manually
Sorry, still new to joy of working with these devices. Fun tho
Click to expand...
Click to collapse
No, if Android pay has a problem, it will reject you DURING the process of adding a card, if you add a card sucussfully, your good to go.
If you want to try nougat, please note that that change is irreversible. The firmware is non-downgradeable. I don't think locking the bootloader will erase data, but if it does it PROBABLY will warn you.
The_scam said:
No, if Android pay has a problem, it will reject you DURING the process of adding a card, if you add a card sucussfully, your good to go.
If you want to try nougat, please note that that change is irreversible. The firmware is non-downgradeable. I don't think locking the bootloader will erase data, but if it does it PROBABLY will warn you.
Click to expand...
Click to collapse
Thanks for all that...just to be clear, the only way to get Nougat is to flash it ? or is it also OTA?
mlecho said:
Thanks for all that...just to be clear, the only way to get Nougat is to flash it ? or is it also OTA?
Click to expand...
Click to collapse
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
The_scam said:
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
Click to expand...
Click to collapse
Sorry I have a question, I have an A9 (European model) S-ON with CM 14.1 and I would like to get S-OFF in order to back to stock. The problem is that I have read that Sunshine only works with stock ROM and, out of the box, my phone came with vodafone uk ROM and I can't find, on the internet, the exact same ROM as mine ( I have found an older version but because I have S-ON I can't downgrade ). There is another way to make Sunshine works? Thanks in advance
Lolli26 said:
Sorry I have a question, I have an A9 (European model) S-ON with CM 14.1 and I would like to get S-OFF in order to back to stock. The problem is that I have read that Sunshine only works with stock ROM and, out of the box, my phone came with vodafone uk ROM and I can't find, on the internet, the exact same ROM as mine ( I have found an older version but because I have S-ON I can't downgrade ). There is another way to make Sunshine works? Thanks in advance
Click to expand...
Click to collapse
what is your rom version number/firmware version 1.57?
The_scam said:
what is your rom version number/firmware version 1.57?
Click to expand...
Click to collapse
No my firmware version is 1.62.161.2
Lolli26 said:
No my firmware version is 1.62.161.2
Click to expand...
Click to collapse
i cant find anything either, i guess you'll have to wait until the rom is released.
The_scam said:
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
Click to expand...
Click to collapse
ahh, so i will need to re-lock if i want this OTA.
And btw, Android Pay worked, just as you said it would!
mlecho said:
ahh, so i will need to re-lock if i want this OTA.
And btw, Android Pay worked, just as you said it would!
Click to expand...
Click to collapse
Good, I think you can download the ota and sideload it, should be in one of the general threads. Think it's called any news on 7.0
So, after all this, i had Android Pay (AP) working great w/ 1.57.617.60 flashed back to my phone. I never re-locked my bootloader. This a.m. i flashed nougat, both boot and system (RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.18.617.1) - All's great. However while shopping i was rejected by AP with the message in the attached screen shot. Is this because i never re-locked the bootloader? What are the consequences by doing so? Can I eventually re-unlock for future flashing?
NOTE - my device is not rooted, despite the accusations from the modal!
mlecho said:
So, after all this, i had Android Pay (AP) working great w/ 1.57.617.60 flashed back to my phone. I never re-locked my bootloader. This a.m. i flashed nougat, both boot and system (RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.18.617.1) - All's great. However while shopping i was rejected by AP with the message in the attached screen shot. Is this because i never re-locked the bootloader? What are the consequences by doing so? Can I eventually re-unlock for future flashing?
NOTE - my device is not rooted, despite the accusations from the modal!
Click to expand...
Click to collapse
In nougat, it checks for unlocked bootloaders sadly you can't relock bootloader in nougat.
The_scam said:
In nougat, it checks for unlocked bootloaders sadly you can't relock bootloader in nougat.
Click to expand...
Click to collapse
oh no...really? no 'fastboot oem lock'? crap. Perhaps the "upgrade" was a mistake. So i'm without?
mlecho said:
oh no...really? no 'fastboot oem lock'? crap. Perhaps the "upgrade" was a mistake. So i'm without?
Click to expand...
Click to collapse
Yep, looks like it unless you downgrade and relock bootloader, then upgrade back to nougat
MGfusion said:
Yep, looks like it unless you downgrade and relock bootloader, then upgrade back to nougat
Click to expand...
Click to collapse
My goal was keep su and also get nougat. A9 has the bug about OEM unlocking just like all other 7.0 devices. It will most likely get fixed at 7.1.1, the nexuses and all other devices running 7.0 seem to have this "bug"
The_scam said:
My goal was keep su and also get nougat. A9 has the bug about OEM unlocking just like all other 7.0 devices. It will most likely get fixed at 7.1.1, the nexuses and all other devices running 7.0 seem to have this "bug"
Click to expand...
Click to collapse
ahh, so that means, as i understand it, if all goes to plan, we should one day expect a 7.1.1 update that will allow me to finally get back to AP?
mlecho said:
ahh, so that means, as i understand it, if all goes to plan, we should one day expect a 7.1.1 update that will allow me to finally get back to AP?
Click to expand...
Click to collapse
As long as you don't care about root. You can always downgrade to mm, lock, and OTA back to nougat
The_scam said:
As long as you don't care about root. You can always downgrade to mm, lock, and OTA back to nougat
Click to expand...
Click to collapse
ok, but just so i am clear , if i lock while in nougat, there's no going back ? i can not then unlock and downgrade?
mlecho said:
ok, but just so i am clear , if i lock while in nougat, there's no going back ? i can not then unlock and downgrade?
Click to expand...
Click to collapse
No, you can only UNLOCK in nougat. If you want to relock the bootloader, you will have to downgrade to marshmallow and loose your root, or wait for Android 7.1.1
downgrade means i have to wipe data, right? The upgrade that was not the case. I am only assuming
Hello, not sure if someone has asked the same question before but is it possible to relock the bootloader with a custom ROM and not MIUI official ROM?
The main reason behind the question is I want a pure pixel experience ROM and due to an unlocked bootloader and root, I can't use some banking and company apps even with MagiskHide so I'm thinking of relocking the bootloader and unroot and at the same time maintaining the custom ROM.
I'm using a Pixel Experience ROM btw.
Thank you.
vibranze said:
Hello, not sure if someone has asked the same question before but is it possible to relock the bootloader with a custom ROM and not MIUI official ROM?
The main reason behind the question is I want a pure pixel experience ROM and due to an unlocked bootloader and root, I can't use some banking and company apps even with MagiskHide so I'm thinking of relocking the bootloader and unroot and at the same time maintaining the custom ROM.
I'm using a Pixel Experience ROM btw.
Thank you.
Click to expand...
Click to collapse
Afaik not possible..i mean if u lock bootloader on any custom rom or even official with modifications u will stuck at bootlooop. dm verity
As far as I know, relock the bootloader is not possible.
However, it's possible to hide the bootloader unlock status without installing magisk. For example, xiaomi.eu's ROM hides it, and SafetyNet passes without magisk. But I don't know how to do this.
Which version of magisk are you using, it should be better with hiding stuff in the latest verison
huyizheng said:
As far as I know, relock the bootloader is not possible.
However, it's possible to hide the bootloader unlock status without installing magisk. For example, xiaomi.eu's ROM hides it, and SafetyNet passes without magisk. But I don't know how to do this.
Click to expand...
Click to collapse
Interesting, I am wondering if it is MIUI thing.
malimukk said:
Which version of magisk are you using, it should be better with hiding stuff in the latest verison
Click to expand...
Click to collapse
Thank you, I am using Magisk 18. Some of my apps still force me to close even after I added it in MagiskHide.
huyizheng said:
As far as I know, relock the bootloader is not possible.
However, it's possible to hide the bootloader unlock status without installing magisk. For example, xiaomi.eu's ROM hides it, and SafetyNet passes without magisk. But I don't know how to do this.
Click to expand...
Click to collapse
You dont have to do anything. Simply Install their Rom and IT will Work directly. Used Banking Apps etc without a Problem on their Rom
vibranze said:
Interesting, I am wondering if it is MIUI thing.
Thank you, I am using Magisk 18. Some of my apps still force me to close even after I added it in MagiskHide.
Click to expand...
Click to collapse
I've found with a few apps that I had to turn off USB debugging as well, before it would let me use them. Maybe give that a try.