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
Related
It started when I tried to install a CM11 update. I did not see that was only for KK BL, then I tried to revert to stock rom(using RSD lite) and install the old version for the JB BL again, but my wifi still not working(or working only when it wants lol).
Anyone could help me?
I tried to flash a lot of different roms, even reset with RSD, but the issue stills. I don't know what more I can do
Thx for the att and sorry for my horrible english...
Carcass.br said:
It started when I tried to install a CM11 update. I did not see that was only for KK BL, then I tried to revert to stock rom(using RSD lite) and install the old version for the JB BL again, but my wifi still not working(or working only when it wants lol).
Anyone could help me?
I tried to flash a lot of different roms, even reset with RSD, but the issue stills. I don't know what more I can do
Thx for the att and sorry for my horrible english...
Click to expand...
Click to collapse
im having the same issue... my step dad said there was a patch somewhere but i think its a patch from verizon thats going to be an ota so... we will lose root
derpyherp said:
im having the same issue... my step dad said there was a patch somewhere but i think its a patch from verizon thats going to be an ota so... we will lose root
Click to expand...
Click to collapse
lose root? your bootloader is not unlocked?
ncsuwolfs said:
lose root? your bootloader is not unlocked?
Click to expand...
Click to collapse
I thought you loose root when you take ota's??
derpyherp said:
I thought you loose root when you take ota's??
Click to expand...
Click to collapse
If you are rooted, the OTA will fail, so you have to flash back to stock before taking OTAs.
If you are locked and you take an OTA, you will lose access to whatever exploit was patched. In the case of going from JB to KK, the original root (Saferoot I believe) won't work. However, Towelroot will work for those that have locked bootloaders.
However, if you are rooted and on the latest official KK, then you can unlock your bootloader and then, no matter what OTA comes out after that, you will still be able to root your phone without the use of an exploit like Towelroot. Instead, you take .zip image of the SU app you are using and flash it in TWRP or CWM recovery. No exploit needed.
Towelroot is only for those that don't have an unlocked bootloader and it's an exploit (a security issue) within the specific version of the Android OS. OTAs patch these as they are released, which means another exploit has to be discovered in order to achieve root for locked bootloaders.
So, right now, if you are not unlocked, you better unlock on the initial KK release because the latest soak test does patch Towelroot and the bootloader exploit. You've been warned.
Hi,
I have an LG Nexus 5 (KTU84P, or "hammerhead") running Android KitKat 4.4.4. It is rooted using Chainfire's AutoRoot for the Nexus 5 for Android 4.4.4, and I have no custom ROM, simply Vanilla Android but with SuperSU. I am looking to update to Android L, version 5, and I have received a notification for the OTA update.
I understand that with OTA updates, your data will not be wiped, but you will lose root access. I have researched ways to keep the root, but they only appear to be for older versions of Android. I understand that I will lose root.
My question is, will I have to run the "oem unlock" (which I understand is the part of the whole rooting process which actually wipes your device), or will I just have to load Chainfire's AutoRoot? If I go through with it, I will use his AutoRoot for hammerhead for Android L, but basically my end goal is to root and update and not lose any data.
Thanks, if you need more info, let me know?
Autoroot will not wipe your data if your bootloader is already unlocked. Only if your bootloader was locked to begin with.
Nope. Once unlocked it stays unlocked unless you lock it yourself
frenziedfemale said:
Autoroot will not wipe your data if your bootloader is already unlocked. Only if your bootloader was locked to begin with.
Click to expand...
Click to collapse
musclehead84 said:
Nope. Once unlocked it stays unlocked unless you lock it yourself
Click to expand...
Click to collapse
Thank you both very much!
Of course with L you can no longer get the OTA if you have custom recovery. Just incase you weren't aware
rootSU said:
Of course with L you can no longer get the OTA if you have custom recovery. Just incase you weren't aware
Click to expand...
Click to collapse
I have updated OTA, and I kept EVERYTHING, even my root apps, but when I open up SuperSU I get a notification explaining that the Su binary is not installed, which is obviously removed when updating. Now, I'm just backing up my data. Another thing I would like to confirm is, if I use Chainfire's Auto Root for the Nexus 5 running Android 5.0, will it run OEM unlock again, and if it does, will I be affected considering my bootloader is already unlocked?
AudaxNovus said:
I have updated OTA, and I kept EVERYTHING, even my root apps, but when I open up SuperSU I get a notification explaining that the Su binary is not installed, which is obviously removed when updating. Now, I'm just backing up my data. Another thing I would like to confirm is, if I use Chainfire's Auto Root for the Nexus 5 running Android 5.0, will it run OEM unlock again, and if it does, will I be affected considering my bootloader is already unlocked?
Click to expand...
Click to collapse
If its unlocked, it can't be unlocked again.
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
D3abL3 said:
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
Click to expand...
Click to collapse
Odd. Hasn't locked for anyone else afaik
D3abL3 said:
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
Click to expand...
Click to collapse
There's a REALLY easy way to test that theory.
Open the factory image archives and check the script. Unless it runs 'fastboot oem lock' it isn't relocking it.
#stayparanoid
Don't you think this makes the trick?
"fastboot flash bootloader bootloader-hammerhead-hhz12d.img"
I was running cm12 on my nexus 5 and I had unlocked the boot loader and was asking xposed framework aplha version .
But then I decided to go back to stock android and I flashed the flashed the factory image of android 5.1 build number lmy47I . I wiped the data and even relocked the boot loader and now my phone is running smoothly and is on stock android.
But is there a way by which I can check if I flashed it correctly or not?
I mean nothing is broken but I heard android 5.1.1 update is around the corner so I was worried will I be able to apply the ota
Huh what? If it booted and is running smoothly its fine. If you didnt mod anything you'll get the ota
Sent from my Nexus 5 using Tapatalk
If you've flashed the factory image and everything is stock you should be fine for the OTA!
Thanks for the help
Lol....
You didn't need to relock the bootloader though. I tend to not ever want to relock it after unlocking it since that's about he only way you could potentially brick the device I think (Like if you relocked the bootloader and then for some reason the phone would not boot or something I am not sure how you'd unlock the bootloader again but whatever)
Evo_Shift said:
... I am not sure how you'd unlock the bootloader again but whatever)
Click to expand...
Click to collapse
Good to know. Btw, can you tell me, I'm on stock 5.1 unlocked bl, twrp, rooted. Will I be able to apply 5.1.1 over OTA when it comes out ?
jazzh said:
Good to know. Btw, can you tell me, I'm on stock 5.1 unlocked bl, twrp, rooted. Will I be able to apply 5.1.1 over OTA when it comes out ?
Click to expand...
Click to collapse
No, you're rooted.
Will I be able to flash the 5.1.1 image ?
jazzh said:
Will I be able to flash the 5.1.1 image ?
Click to expand...
Click to collapse
Yes
Someone will make a zip file of the update
SENT BY ENTANGLEMENT
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
????.?? said:
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
Click to expand...
Click to collapse
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Droidriven said:
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Click to expand...
Click to collapse
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
????.?? said:
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
Click to expand...
Click to collapse
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Droidriven said:
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Click to expand...
Click to collapse
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
I dont know guys with that phone but there should be a tool that bypass auth and unlock the bootloader in any case. I ONLY knows MTK devices, not sure about that samsung i use a .Bat file.
????.?? said:
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
Click to expand...
Click to collapse
No, I said that after the update, it could cause the bootloader to be locked and then may not be unlockable from that point on. It depends on the bootloader in the update. If this happens, you will be unable to install TWRP or root via Magisk. That is why you need to confirm whether or not flashing the update will relock the bootloader during the flashing process and, if it does, whether or not it can be unlocked again after the update.
In other words, look at exactly what you are about to jump into before you make the jump because you might land in the one place that you absolutely do not want to land.
Hello.
I have a bootloader locked Pixel 7 Pro with the April 2023 stock build.
I would like to downgrade to the October or November 2022 build.
Is there any way I can accomplish this?.
Thank you.
EDIT: Got an OTA build, but recovery is saying downgrades are not allowed.
Any other way?
Unless you unlock the bootloader, you cannot downgrade using an OTA. How you tried to flash the full firmware? Why are you trying to downgrade to a firmware that far behind anyways?
schmeggy929 said:
Unless you unlock the bootloader, you cannot downgrade using an OTA. How you tried to flash the full firmware? Why are you trying to downgrade to a firmware that far behind anyways?
Click to expand...
Click to collapse
Reason, because on Pixel 7 and 7 Pro, firmwares from October and November, deleting an app, you can carrier unlock them, so I am trying to do that. I did it already with a 7 Pro which had the October firmware, obviously, if there is a reset on the phone, it gets locked again, but at least it's something.
I tried using the flashme.bat script, PixelFlasher, used OTA and Full firmwares, Fastboot and Recovery, nothing.
You cannot downgrade to a lower security patch without wiping data. Unlocked bootloader has the same behaviour.
Lossyx said:
You cannot downgrade to a lower security patch without wiping data. Unlocked bootloader has the same behaviour.
Click to expand...
Click to collapse
The phone is clean, so no data on it.
SirRhor said:
The phone is clean, so no data on it.
Click to expand...
Click to collapse
Oh my bad. Then I am not so sure ,sorry. This is my first Pixel.