I used to have root on my phone but decided to flash stock rom again. then while on stock rom, software update popped up. my software was updated to july patch CRG1. Then i want to root again. But when i flash Twrp using odin, it failed and shows on my note 8 with a red marking "only official released binaries are allowed to be flashed. I cannot downgrade to lower software version . it shows Device 4 Binary 3
ajdeleon123 said:
I used to have root on my phone but decided to flash stock rom again. then while on stock rom, software update popped up. my software was updated to july patch CRG1. Then i want to root again. But when i flash Twrp using odin, it failed and shows on my note 8 with a red marking "only official released binaries are allowed to be flashed. I cannot downgrade to lower software version . it shows Device 4 Binary 3
Click to expand...
Click to collapse
When you flashed stock rom and it updated did you check to see if OEM unlock toggle was available in developer options?
Might now have to wait 7 days or try the trick that's been posted somewhere on xda.... think has something to do with changing the system time and checking for update (I think).
Yep once upgraded to bootloader v4 No More going back to bl.v3 v2 or v1 bootloaders.
I tried the trick of setting the date 7 days or even 1 month backwards. OEM is ticked already. and if i go to Download mode , OEM IS OFF. the last time i flashed stock rom, even without waiting for 7 days i can flash twrp without any problem. And now even OEM is already unlocked, cant install twrp
ajdeleon123 said:
I tried the trick of setting the date 7 days or even 1 month backwards. OEM is ticked already. and if i go to Download mode , OEM IS OFF. the last time i flashed stock rom, even without waiting for 7 days i can flash twrp without any problem. And now even OEM is already unlocked, cant install twrp
Click to expand...
Click to collapse
Maybe try the latest twrp? Maybe bl v4 prevents it and twrp needs to be updated? Check the twrp thread.
im using updated twrp
uisng twrp v3.1.1.0
Fix already. Thanks seems my downloaded rmm bypass doesnt work at all on new BL. download a new OEM PATCH and now working Currently rooted with repulsa rom. Thanks
Is this the OEM patch you used? RMM-State_Bypass_Mesa_v2
No. i used the patch by dr.ketan
please tell me the steps and the files you used, thank you very much.
I have the binary 7 August update and I can't root the mobile
Related
Good Morning all,
When I first time received my Nexus 6, unlocked the bootloader and Rooted with the app for windows Nexus Root Toolkit by Wugfresh, I did not change it to any custom recovery, I left it on stock the rom and I did not install any custom recovery as well., everything is on stock, I just I rooted it.
I've read a lot of things about partitions, downgrades, even OEM Locks and OEM Unlock Bootloaders and people have bricked many devices that I'm afraid to brick it, I'm confused know what steps to follow in order to properly update from lollipop 5.01 to 5.1
I'm on Android 5.01 and received the OTA to update to 5.1, but afraid to press the button in my nexus 6 where it says System Update Available
Should I continue to update with the OTA that I received even if I'm rooted? or should I do it manually with the Nexus Root Toolkit?
What do I need exactly to check / verify before I try to update my device and not brick it?
Please advise
rayosx said:
Good Morning all,
When I first time received my Nexus 6, unlocked the bootloader and Rooted with the app for windows Nexus Root Toolkit by Wugfresh, I did not change it to any custom recovery, I left it on stock the rom and I did not install any custom recovery as well., everything is on stock, I just I rooted it.
I've read a lot of things about partitions, downgrades, even OEM Locks and OEM Unlock Bootloaders and people have bricked many devices that I'm afraid to brick it, I'm confused know what steps to follow in order to properly update from lollipop 5.01 to 5.1
I'm on Android 5.01 and received the OTA to update to 5.1, but afraid to press the button in my nexus 6 where it says System Update Available
Should I continue to update with the OTA that I received even if I'm rooted? or should I do it manually with the Nexus Root Toolkit?
What do I need exactly to check / verify before I try to update my device and not brick it?
Please advise
Click to expand...
Click to collapse
Do not re-lock the bootloader, do not try to downgrade the bootloader. Do not Flash CM12 from the 3/13/2015(not available to download anyways). You should be ok.
If you have stock recovery, sounds like you can flash the OTA...but that is up to you.
Can you describer your system. You said it is STOCK rooted. Did you unlock bootloader? Never flashed anything before?
idtheftvictim said:
Do not re-lock the bootloader, do not try to downgrade the bootloader. Do not Flash CM12 from the 3/13/2015(not available to download anyways). You should be ok.
If you have stock recovery, sounds like you can flash the OTA...but that is up to you.
Can you describer your system. You said it is STOCK rooted. Did you unlock bootloader? Never flashed anything before?
Click to expand...
Click to collapse
Thanks on helping me out,
I'm attaching two shots so you can see all what I have, I have never flashed a custom ROM, just rooted using the wugfresh app for windows,
Also I have in developer options usb debug on and unlocked oem with a check mark.
Again, if you check everything above, I'm on 5.01 and I don't know if just pressing OTA system update button to update from the phone shall brick my phone whether I am rooted, or do I have to be with no root to proceed from there?
Please advice
Sent from my Nexus 6 using XDA Free mobile app
rayosx said:
Thanks on helping me out,
I'm attaching two shots so you can see all what I have, I have never flashed a custom ROM, just rooted using the wugfresh app for windows,
Also I have in developer options usb debug on and unlocked oem with a check mark.
Again, if you check everything above, I'm on 5.01 and I don't know if just pressing OTA system update button to update from the phone shall brick my phone whether I am rooted, or do I have to be with no root to proceed from there?
Please advice
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Looks like you should be fine to install the OTA with no worries.
Please note: I in NO WAY take responsibility for anything that happens to your phone though....sorry...have to put disclaimer
idtheftvictim said:
Looks like you should be fine to install the OTA with no worries.
Please note: I in NO WAY take responsibility for anything that happens to your phone though....sorry...have to put disclaimer
Click to expand...
Click to collapse
Lucky me that I did not press the button to do it through OTA, read below
Can I still take an OTA after I unlock and root?
Answer: On Lollipop, No. On KitKat, yes (sometimes) – if you haven’t made any other system level modifications.
With Lollipop, the OTA update process checks the entire system blob. That means if just one small thing is different about the system partition the OTA will fail. Since rooting itself (regardless of the method: manual/toolkit) installs Superuser as a system app and su binaries to the system partition it inherently breaks OTA’s.
So how should you update a rooted Lollipop device?
1. Wait for the official factory package from google to be released for the build you would like to update to.
2. Backup your apps + data, as a safe measure – in case you end up having to wipe data.
3. Use “Flash Stock + Unroot” and check “No-wipe mode” (to avoid a data wipe).
That’s it. Afterwards you can re-root.
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Brick
abhigamez said:
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Click to expand...
Click to collapse
This could end up in hard brick also if OTA detects other system modifications. You should just edit the OP with a warning.
abhigamez said:
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Click to expand...
Click to collapse
Couldn't one just install it from this link?
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
This is basically all of the stock firmware (Including the recovery), correct?
CasinovaRoyale said:
This could end up in hard brick also if OTA detects other system modifications. You should just edit the OP with a warning.
Click to expand...
Click to collapse
i don't think so abt hard brick
as when i was updating i simply came with error while updating that can't update
and i also tried updating after flashing custom rom [which is available online] and i was successfully updated
smokinjoe2122 said:
Couldn't one just install it from this link?
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
This is basically all of the stock firmware (Including the recovery), correct?
Click to expand...
Click to collapse
I don't think it's a useful thread as there is a specific thread to give information about installing Official firmware and relocking the bootloader.!
Please moderator check this once.
This might damage the devices if anyone tries to update the ROM through OTA, by just changing the recovery being the variety ,oem and bootloader status changed.
thippu46 said:
I don't think it's a useful thread as there is a specific thread to give information about installing Official firmware and relocking the bootloader.!
Please moderator check this once.
This might damage the devices if anyone tries to update the ROM through OTA, by just changing the recovery being the variety ,oem and bootloader status changed.
Click to expand...
Click to collapse
i hv checkd it, but my device didn't hard broke, but i want to make my device dead to get new motherboard in warranty
yograjfire18 said:
i hv checkd it, but my device didn't hard broke, but i want to make my device dead to get new motherboard in warranty
Click to expand...
Click to collapse
:angel:lol
Does someone has tried this successfully?
mabvmet said:
Does someone has tried this successfully?
Click to expand...
Click to collapse
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Could always just do "fastboot boot" instead of "fastboot flash". It will allow you to then boot twrp, install what you want, and not touch the stock recovery.
pratham.kamath said:
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Click to expand...
Click to collapse
What are the steps I need to follow to install this file? (SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
---------
Edit: Solved
---------
I followed the code section steps on this post:
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
pratham.kamath said:
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Click to expand...
Click to collapse
Hey! I Finally did this, I removed the twrp and the root, I Just installed this stock (?) rom through the "adb fastboot". Now when I look for OTA updates it appears a message that indicates that the latest security update is installed, it's the one of December 2017...
Why doesn't it appear the last one (april's or so)?
What I have to do in order to have or reactivate the OTA updates?
Thanks in advance!
Make sure the correct stock rom is installed. (Cross check the name word to word) I too tried a few different stock ROMs and only the above version worked and updated till April security patch. Rest versions didn't update for some reason.
pratham.kamath said:
Make sure the correct stock rom is installed. (Cross check the name word to word) I too tried a few different stock ROMs and only the above version worked and updated till April security patch. Rest versions didn't update for some reason.
Click to expand...
Click to collapse
How can I know what is the correct stock rom?
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/
This one worked for me.
pratham.kamath said:
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/
This one worked for me.
Click to expand...
Click to collapse
My current file >>
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml_1
This rom left me with the December security patch and no OTA updates available
This time I will download the same one, but the most recent (February, according with the web)
Next download >>
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip 03/02/2018 06:35
I followed this steps in code section to flash it... any suggest?
Steps >> https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
Don't go by date go by exact name and number of rom as I mentioned. I tried almost all the firmwares listed and only the one that I mentioned updated to latest april security patch. Matter of fact i just restored phone to stock yesterday and it worked again. Also copy all the commands to a notepad and save the same as .bat file so that way you can just run the file and it will automatically install stock rom and reboot phone.
---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
Check software channel name in settings. Mine is listed as retin. I read that there are other software channels too for which updates security patch has not been released yet. I may be wrong though.
pratham.kamath said:
Don't go by date go by exact name and number of rom as I mentioned. I tried almost all the firmwares listed and only the one that I mentioned updated to latest april security patch. Matter of fact i just restored phone to stock yesterday and it worked again. Also copy all the commands to a notepad and save the same as .bat file so that way you can just run the file and it will automatically install stock rom and reboot phone.
---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
Check software channel name in settings. Mine is listed as retin. I read that there are other software channels too for which updates security patch has not been released yet. I may be wrong though.
Click to expand...
Click to collapse
Sorry, how do I run the bat file? The last time I entered the commands one by one.
My software chanel is "openmx" the sameone that I had when the phone was rooted (and with the updates available).
I need help
I need the recovery.img for the device moto g5s plus xt1806:llorando:
Title says all. This is for the American Retail variant. Does not include Oreo.
Glad to see that Moto is being consistent with Security patches though!
Edit:. I meant April 1st 2018!
This is for all varients
reteu,retbr,Retin also got updates
Sent from my Moto G5S Plus using XDA Labs
Yet to be seen in retapac though
Adi5 said:
This is for all varients
reteu,retbr,Retin also got updates
Click to expand...
Click to collapse
The day before I saw the update notification, but didn't update as I wanted to backup some of my files. Later when I checked for update the notification was gone. Says phone is upto date with March patch.
JaggedPill said:
The day before I saw the update notification, but didn't update as I wanted to backup some of my files. Later when I checked for update the notification was gone. Says phone is upto date with March patch.
Click to expand...
Click to collapse
I didn't had notification,now flashed custom rom
Flash full firmware for ur software channel
Retid here, still no updates
Got it..retin software channel.
In retla was not released
April Patch also released for retapac ?
I only just got 116-48-12 yesterday on retus, so I'm not gonna hold my breath.
you can edit the thread title by editing your post and pressing "go advanced"
Meanwhile retgb is still on October 2017. This is the last time I buy Motorola.
Hi all,
I've just applied the 01 April Security Patch and my phone has rebooted into TWRP. If I select to reboot, it starts to reboot and goes back into TWRP. Any ideas as to how I can get it to reboot back to normal ?
So I'm basically stuck in a TWRP Bootloop
Thanks in advance
championc said:
Hi all,
I've just applied the 01 April Security Patch and my phone has rebooted into TWRP. If I select to reboot, it starts to reboot and goes back into TWRP. Any ideas as to how I can get it to reboot back to normal ?
So I'm basically stuck in a TWRP Bootloop
Thanks in advance
Click to expand...
Click to collapse
Hi, you should know that you can't get updates via OTA once you have modified system, and unlocking bootloader and flashing TWRP is certainly a system modification, so I really hope that you made a TWRP backup before trying to update. In case you didn't, try flashing official firmware using fastboot, also there is one post in XDA with a TWRP backup in case you messed up, if you can't use fastboot or don't have a backup, try using that one. Remember to NEVER update via OTA unless your phone is fully unmodified.
Juancasa14 said:
Hi, you should know that you can't get updates via OTA once you have modified system, and unlocking bootloader and flashing TWRP is certainly a system modification, so I really hope that you made a TWRP backup before trying to update. In case you didn't, try flashing official firmware using fastboot, also there is one post in XDA with a TWRP backup in case you messed up, if you can't use fastboot or don't have a backup, try using that one. Remember to NEVER update via OTA unless your phone is fully unmodified.
Click to expand...
Click to collapse
U can update with unlocked bootloader. Only without mods like root or twrp
Adi5 said:
U can update with unlocked bootloader. Only without mods like root or twrp
Click to expand...
Click to collapse
Yeah I know, sorry if I didn't make myself clear, thanks for explaining
Championc were you able to recover your phone?
Hi everyone;
I have a rooted and unlocked Nokia 8 TA-1004 (Security Patch 1 July 2018; 00WW_4_88B_SP02).
I followed the guides on this very forum on how to root and unlock (first) and then how to put TWRP (after I already had rooted and unlocked).
The problem I'm having is exactly what the title says:
I have the possibility to update to SP of August but I just can't; it gives me an installation error as soon as it finishes downloading.
I already tried to Factory Reset the phone and when that didn't solve anything I tried (and succeded) putting TWRP hoping it would solve (hope never dies) the problem but it didn't.
I'm at a loss here, can anyone help me?
Xayar said:
Hi everyone;
I have a rooted and unlocked Nokia 8 TA-1004 (Security Patch 1 July 2018; 00WW_4_88B_SP02).
I followed the guides on this very forum on how to root and unlock (first) and then how to put TWRP (after I already had rooted and unlocked).
The problem I'm having is exactly what the title says:
I have the possibility to update to SP of August but I just can't; it gives me an installation error as soon as it finishes downloading.
I already tried to Factory Reset the phone and when that didn't solve anything I tried (and succeded) putting TWRP hoping it would solve (hope never dies) the problem but it didn't.
I'm at a loss here, can anyone help me?
Click to expand...
Click to collapse
This "problem" happens because the Android OS only updates the other partition set (A/B) when it's all stock and to achieve root thru Magisk we must patch the bootloader, making it unsuitable for the process.
You need to revert back to the official bootloader and then you'll be able to get it updated. After that just apply the patched bootloader to regain root/twrp and unfortunately that's what you gotta do on every update.
So uhhh how and where do I get the stock bootloader?
If I flash the magisk uninstaller I should get the stock boot image back because Magisk backs it up but I don't thing that alone does the trick.
What else do I need and where do I get it?
That's not an issue related to bootloader but rather to the patched boot.img existing on both paritions A/B. You'll have to restore Magisk backup image or reflash official June OTA and start updating the system without Magisk.
So if I just flash the Magisk uninstaller I will regain the ability to update?
Xayar said:
So if I just flash the Magisk uninstaller I will regain the ability to update?
Click to expand...
Click to collapse
Either you'll have ability to update or soft brick 50/50 odds
I don't like those odds ?
I tried restoring the boot image using Magisk's tool (since the version 17 there's the option of restoring the boot.img without actually uninstalling everything but it says it doesn't have any boot.img backed up...
I guess I'm back to square one and need to downgrade to the June update... Can I just flash it?
Is there any guide on how to update a (magisk) rooted pixel 4?
My case:
I unlocked my bootloader when I received the phone, as usual
I used magisk manager to modify the boot.img from my fw-image. I flashed it with fastboot and so had root.
Later, I used a custom kernel.
As far as I know, I did not do any changes except boot.img
When the Update hit me early December, I was not able to update. "Update failed" it told me. I managed to flash the original boot.img a short while after. I still could not update my pixel.
Now I do a factory reset while flashing the original fw image again. (I flashed the wrong one and got face-unlock to not work at all. I hope I am downloading the right one right now and can use face unlock again)
mad-murdock said:
Is there any guide on how to update a (magisk) rooted pixel 4?
My case:
I unlocked my bootloader when I received the phone, as usual
I used magisk manager to modify the boot.img from my fw-image. I flashed it with fastboot and so had root.
Later, I used a custom kernel.
As far as I know, I did not do any changes except boot.img
When the Update hit me early December, I was not able to update. "Update failed" it told me. I managed to flash the original boot.img a short while after. I still could not update my pixel.
Now I do a factory reset while flashing the original fw image again. (I flashed the wrong one and got face-unlock to not work at all. I hope I am downloading the right one right now and can use face unlock again)
Click to expand...
Click to collapse
Check the Guides sections, you'll find one there.
mad-murdock said:
Is there any guide on how to update a (magisk) rooted pixel 4?
My case:
I unlocked my bootloader when I received the phone, as usual
I used magisk manager to modify the boot.img from my fw-image. I flashed it with fastboot and so had root.
Later, I used a custom kernel.
As far as I know, I did not do any changes except boot.img
When the Update hit me early December, I was not able to update. "Update failed" it told me. I managed to flash the original boot.img a short while after. I still could not update my pixel.
Now I do a factory reset while flashing the original fw image again. (I flashed the wrong one and got face-unlock to not work at all. I hope I am downloading the right one right now and can use face unlock again)
Click to expand...
Click to collapse
Here ya go :good:
https://forum.xda-developers.com/pi...-4-xl-android-10-q-root-t3996969/post80774791