Related
Hi I just wanted some confirmation that unlocking bootloader doesn't block me from getting OTA updates from Google, since I haven't gotten an OTA for the latest build yet (The May update). I'm hoping this is only cause I'm in India and it hasn't pushed to us yet. I've enrolled in the Android Beta Program to test if OTA is really broken (since it sends an OTA with the Android N image.)
I haven't modified anything, I tried flashing TWRP but it didn't stick cause I didn't know I had to go into the recovery and modify the system/boot, so I still have the stock android recovery.
Any confirmation will give me a lot of peace of mind, cause I value getting OTAs and not having to manually flash it. If it has indeed been broken, I want to know if relocking would fix it and if relocking would wipe data again. Thanks for your help
EDIT: Just got the OTA for the N preview, so I guess it's just a roll out thing then. Just want to leave this here for anyone else who's new to nexus devices and was wondering the same.
AnrgKrshn said:
Hi I just wanted some confirmation that unlocking bootloader doesn't block me from getting OTA updates from Google, since I haven't gotten an OTA for the latest build yet (The May update). I'm hoping this is only cause I'm in India and it hasn't pushed to us yet. I've enrolled in the Android Beta Program to test if OTA is really broken (since it sends an OTA with the Android N image.
I haven't modified anything, I tried flashing TWRP but it didn't stick cause I didn't know I had to go into the recovery and modify the system/boot, so I still have the stock android recovery.
Any confirmation will give me a lot of peace of mind, cause I value getting OTAs and not having to manually flash it. If it has indeed been broken, I want to know if relocking would fix it and if relocking would wipe data again. Thanks for your help
Click to expand...
Click to collapse
Simply having an unlocked bootloader won't stop you from receiving OTAs. I don't believe they've even began pushing the OTA for the May update.
brholt6 said:
Simply having an unlocked bootloader won't stop you from receiving OTAs. I don't believe they've even began pushing the OTA for the May update.
Click to expand...
Click to collapse
Just saw this after I posted my edit lol. Thanks for the confirmation
Will the ota work with systemless root?
94SupraTT said:
Will the ota work with systemless root?
Click to expand...
Click to collapse
You need to flash stock boot and recovery images to receive it or alternatively use chainfires flashfire app.
So, I just installed the May 2017 security update on my Pixel XL. Now, when I go to re-root it after applying the update, I get a boot loop.
I have to reflash both boot slots with stock and boot back in to android without rooting/installing the root files.
Is anyone else having trouble rooting with the May 2017 security update? If not, how'd you do it?
NWolf said:
So, I just installed the May 2017 security update on my Pixel XL. Now, when I go to re-root it after applying the update, I get a boot loop.
I have to reflash both boot slots with stock and boot back in to android without rooting/installing the root files.
Is anyone else having trouble rooting with the May 2017 security update? If not, how'd you do it?
Click to expand...
Click to collapse
Lots of us, its all blown up. Thread in the news and guide section. You can reflash the April boot image and it will work.
Oops, Toni beat me to it.
oh i am not alone...
glad that i see this post before looping for 100 times more...
Hello All!
I'm sorry if this has been asked before but I'm trying to install nougat on my phone and having some great difficulty.
So far my phone is flashed and I was running TWRP 3.0.2 however every time i try to flash a lineage 14.1 based rom it would never work. (tried straight lineage 14.1, nutOS, DOT) none of them worked (wiped the phone clean, then received error 7, removed the assert lines that let in install but just perpetually boot looped) . My many a google searches makes me believe that that particular version of TWRP does not work with nougat. but that's the only version I am able to get working. any newer version of TWRP gets stuck in a perpetual boot loop.
So with that said, if my suspicious are correct and i need a newer version is there anything I'm missing to install a newer version of TWRP? if 3.0.2 is a good enough version to install nougat based rom's what am I missing on that end?
Any help at all would be greatly appreciated! and Thanks in advance!
Ninja edit: I'm runnnig the Z00A (Z551ML) and i've been using using roms/images meant for Z00A
I'm actually not yet used to these kind of stuffs but I guess your problem has something to do with either your twrp version or the bootloader version, this link might help you. http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
Slent said:
I'm actually not yet used to these kind of stuffs but I guess your problem has something to do with either your twrp version or the bootloader version, this link might help you. http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
Click to expand...
Click to collapse
Yup that was it. My google-fu is off as i found my answer from a reddit post (5 seconds after asking this question in reddit...) My issue was that i was still on lolipop, the last OTA update and had no idea asus put out a manual update. worst part is, after unlocking the bootloader installing twrp, THEN installing that oem update, that might have cause my phone to crash mid update so it ended up bricking the phone...
I was able to Frankenstein it back together with old parts that I thought were no good, right now I'm on that last manual update and I gotta fight through a few issues preventing the boot loader from being unlocked.
Anyway you were correct, using the last OTA update updates the bootloader so I was stuck cause of that.
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.
Not yet available on my nokia 6.1. I think we are a couple of weeks away from the update.
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Which TA....?
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
EricH7001 said:
Which TA....?
Click to expand...
Click to collapse
TA-1045
prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I'm on the June 1st level
prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?
Mobe1969 said:
Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.
Click to expand...
Click to collapse
That makes sense cause I keep getting installation failure and not sure if it even downloaded.
Ozonethegreat said:
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?
Click to expand...
Click to collapse
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way
prg318 said:
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way
Click to expand...
Click to collapse
Are the WW images the chinese version I seen floating around here? If not, where did you get them?
Ozonethegreat said:
Are the WW images the chinese version I seen floating around here? If not, where did you get them?
Click to expand...
Click to collapse
Nope - don't think its Chinse - it appears to be a "global" or international version. I don't really notice a difference from my original stock.
I got it from here: https://forum.xda-developers.com/no...-to-flash-global-firmware-pl2-222e-0-t3831764
And was able to flash the "extracted version" with fastboot. I used some fastboot instructions that I found for a chinese rom and changed the filenames to match the worldwide filenames and it worked without the OST tool
Ozonethegreat said:
That makes sense cause I keep getting installation failure and not sure if it even downloaded.
Click to expand...
Click to collapse
Can you locate the downloaded OTA and post it here?
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Were you able to update to Android pie?
Danny1976 said:
Were you able to update to Android pie?
Click to expand...
Click to collapse
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Can you check under system partition and look for Data/OTA
---------- Post added at 04:37 PM ---------- Previous post was at 04:14 PM ----------
Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
Check system partition under data/ota.
Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
You should have pulled the OTA link from a logcat so the rest of us can download the update files and upgrade ourselves :/
I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.
Danny1976 said:
I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.
Click to expand...
Click to collapse
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?
neowlchaz said:
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?
Click to expand...
Click to collapse
I got the July update in July and then I got the August update on August. I don't know why yours took a while to update. Mine and other that I know, get the update for the month the same month.
SM-G960F/DS
RMM State: Prenormal
OEM LOCK: OFF
FRP LOCK: OFF
KNOX tripped: 1
Current binary: Custom
I just flashed TWRP, Magisk, no-verity, and the samsung root preventer disabler following the guide here. I used Magisk 16.6 (supposedly S9 is officially supported now, but it's still in beta).
Everything was going fine, then after an hour or two it froze on the lock screen, and would NOT come out of it. After a couple minutes, I held volume down and power to reboot, and it went into a soft brick.
I can't flash via download mode as it gives the error "Only official released binaries are allowed to be flashed". It gives that error when I try to start the phone or boot into TWRP as well.
So what are my options to fix this, and is it possible to prevent this in the future?
you must flash the latest firmware, yesterday I happened the same.
angel8502 said:
you must flash the latest firmware, yesterday I happened the same.
Click to expand...
Click to collapse
Man, I was hopeful ng that wasn't the case. I've already started downloading from sammobile.
So what are you going to do from here? Try rooting again? Is there a more up-to-date RMM disabler?
Any one else have any ideas about why this happens ? I just flashed EdyoBlue ROM after being on Soldier ROM --- all was uneventful
Upon first reboot I came to the screen about Custom Binaries --- seemed to have lost TWRP etc.
Only way out was to flash stock, lose root and I assume WAIT ANOTHER 7 DAYS !!!
Any other ideas ? Or ideas on how to prevent in the future?
jcrompton said:
Any one else have any ideas about why this happens ? I just flashed EdyoBlue ROM after being on Soldier ROM --- all was uneventful
Upon first reboot I came to the screen about Custom Binaries --- seemed to have lost TWRP etc.
Only way out was to flash stock, lose root and I assume WAIT ANOTHER 7 DAYS !!!
Any other ideas ? Or ideas on how to prevent in the future?
Click to expand...
Click to collapse
Did you also flash the rmm state bypass? I did, and I'm going to try again with v2.
LysolPionex said:
Did you also flash the rmm state bypass? I did, and I'm going to try again with v2.
Click to expand...
Click to collapse
Well I didn't flash anything prior to EdYoBlue ROM -- I had been running Soldier ROM for a while and it was my understanding that the RMM bypass was included in those custom ROMs and or kernels
Obviously I did something wrong
jcrompton said:
Well I didn't flash anything prior to EdYoBlue ROM -- I had been running Soldier ROM for a while and it was my understanding that the RMM bypass was included in those custom ROMs and or kernels
Obviously I did something wrong
Click to expand...
Click to collapse
Oh... Yeah I don't know about that.
Same problem. Samsung Galaxy S9+ (SM-G965F)
I rooted my Samsung Galaxy S9+ (SM-G965) yesterday with
Odin, Magisk (modified version as official verson doesn't work apparently) and TWRP.
Took about 10 minutes to do all up, and root was successful!!! 20 minutes later it turned itself off!! No matter what i did or tried.....I couldn't turn it back on nor get into recovery (TWRP). All while it was constantly flashing........ (ONLY OFFICIAL RELEASE BINARIES TO BE FLASHED)
Figured it was somehow a soft brick. So i flashed original firmware back onto phone with Odin and all was well. ILL BE TRYING A NEW WAY AND WILL POST RESULTS.
1AussieTradie said:
I rooted my Samsung Galaxy S9+ (SM-G965) yesterday with
Odin, Magisk (modified version as official verson doesn't work apparently) and TWRP.
Took about 10 minutes to do all up, and root was successful!!! 20 minutes later it turned itself off!! No matter what i did or tried.....I couldn't turn it back on nor get into recovery (TWRP). All while it was constantly flashing........ (ONLY OFFICIAL RELEASE BINARIES TO BE FLASHED)
Figured it was somehow a soft brick. So i flashed original firmware back onto phone with Odin and all was well. ILL BE TRYING A NEW WAY AND WILL POST RESULTS.
Click to expand...
Click to collapse
What's the new way? Are you able to flash again already, or do you have to wait 7 days again?
same issue i had to re flash the stock OS & wait for 7 days for OEM unlock now i have that option but i am not sure which method should i use.
RMM STATE PRENORMAL is also what blocks custom binaries from being flashed
Check the TWRP guide on how to deal with that too
LysolPionex said:
What's the new way? Are you able to flash again already, or do you have to wait 7 days again?
Click to expand...
Click to collapse
Unfortunately no success. Have to wait the 7 days . Currently trying to find a work around. Will keep informed.
Any news I got my OEM unlock back any way to root the phone and get a custom firmware to work
rockykv2 said:
Any news I got my OEM unlock back any way to root the phone and get a custom firmware to work
Click to expand...
Click to collapse
Once my RMM status is normal, I'm going to try Soldier's Rom. I've heard good things about it.
You'll need to follow the official TWRP guide first. Both in this S9 forum.
I already tested that It gets stuck on welcome screen it will not go forward
rockykv2 said:
I already tested that It gets stuck on welcome screen it will not go forward
Click to expand...
Click to collapse
I'd ask about that in the soldier Rom thread; sounds like it might be a wipe issue (really not sure), but a ton of people love the Rom, so it's probably something random on your end.
I'd stick with a stock-based rom, as they're usually more stable.
That Max Lee tutorial about s9+ root is outdated. He is a ****ing bull****. He did not even cared to update his post that magisk root method always freeze. And also his rmm unlock fix is not updated too. Did you guys have the august 1 security update? I guess that was the cause of this "Only official binaries allowed" after rebooting. Here's hoping somebody here got an answer for that RMM.
jonathan_moreno91 said:
That Max Lee tutorial about s9+ root is outdated. He is a ****ing bull****. He did not even cared to update his post that magisk root method always freeze. And also his rmm unlock fix is not updated too. Did you guys have the august 1 security update? I guess that was the cause of this "Only official binaries allowed" after rebooting. Here's hoping somebody here got an answer for that RMM.
Click to expand...
Click to collapse
That's kinda the general consensus I've gotten about that tutorial.
I was using the August 1 security update, but I was using v1 of Mesa's RMM bypass. I downloaded v2, and downgraded my Rom to like April or March or something and will try it again, once the prenormal clears.
RMM v2 is here:
https://forum.xda-developers.com/sa...nuary-security-patch-sm-t3739225/post75360965
LysolPionex said:
That's kinda the general consensus I've gotten about that tutorial.
I was using the August 1 security update, but I was using v1 of Mesa's RMM bypass. I downloaded v2, and downgraded my Rom to like April or March or something and will try it again, once the prenormal clears.
RMM v2 is here:
https://forum.xda-developers.com/sa...nuary-security-patch-sm-t3739225/post75360965
Click to expand...
Click to collapse
Bro if you are on august 1 security update too then you are in xu2 bootloader... you cannot downgrade to xu1 bootloader which was before august..
jonathan_moreno91 said:
Bro if you are on august 1 security update too then you are in xu2 bootloader... you cannot downgrade to xu1 bootloader which was before august..
Click to expand...
Click to collapse
Really?! This is literally the first I've heard of this. Do you know if there's a thread discussing this?