Database Develop

having issue with ota update after reflashing stock recovery

Hello,
Let me start by just saying that I'm very new to the whole rooting and android development scene and I'm.sorry in advance if this question is noobish. Anyway I have an at&t HTC one m7 that I unlocked the bootloader on, flashed twrp and rooted. The device was working fine no issues ,recently there was an ota update that my brother got for his all stock m7. So I flashed an img of the stock recovery and relocked the bootloader in hopes of having the update install. I know it would remove my root access but I didn't mind that .
Anyway now my device is telling me there is no more ota updates available.
This is odd because I tried to do the update before changing anything back a nd it got stuck when twrp launched .so there is an update available.
Is this normal or is something wrong? thanks!
Edit, i cant words

Stuck at " recovery not Seandroid enforcing" after root n9208

Hi guys I have the latest firmware installed ( see screenshot) whenever I try to obtain root via chain fires autoroot or through custom kernel for n9208 my phone gets stuck at bootloader. Is there any way to fix this.
Ps the crom services app always force closes . And I followed every step on root tutorials

Hi, i got same problem with new firmware update, lost my root and tried to root again with chainfire autoroot, but didnt work, tried a couple of times...no luck, at this step i still can boot android, then tried flash xiaolu kernel...at this step i got boot loop, both space kernel also failed to boot, so if you havent flash any kernel with odin, you still can boot after flashing twrp recovery, but if you already messed with kernel, there no way to to fix it...better flassh new firmware, and use stock until someone can find a way to root 5.1.1, hope its help...

Dyosr said:
Hi, i got same problem with new firmware update, lost my root and tried to root again with chainfire autoroot, but didnt work, tried a couple of times...no luck, at this step i still can boot android, then tried flash xiaolu kernel...at this step i got boot loop, both space kernel also failed to boot, so if you havent flash any kernel with odin, you still can boot after flashing twrp recovery, but if you already messed with kernel, there no way to to fix it...better flassh new firmware, and use stock until someone can find a way to root 5.1.1, hope its help...
Click to expand...
Click to collapse
Isn't there a way we can simply downgrade to the last rootable firmware?

if you're on the latest firmware, i recall having to install the AOK2 bootloader to root my N9208 using the original root methods (not the Systemlesss Root method). check the TWRP thread for details. The situation may have changed, but when i upgraded my firmware to AOL1, i had to downgrade the bootloader to AOK2 to regain root.

cortez.i said:
if you're on the latest firmware, i recall having to install the AOK2 bootloader to root my N9208 using the original root methods (not the Systemlesss Root method). check the TWRP thread for details. The situation may have changed, but when i upgraded my firmware to AOL1, i had to downgrade the bootloader to AOK2 to regain root.
Click to expand...
Click to collapse
How did you downgraded your boot loader? I am sorry but I'm really new to galaxy development.
PS is it safe to flash a firmware from December over my current version which is from march

Lucas Eugene said:
How did you downgraded your boot loader? I am sorry but I'm really new to galaxy development.
PS is it safe to flash a firmware from December over my current version which is from march
Click to expand...
Click to collapse
check the TWRP thread for details and links to downgrade the bootloader. please note/remember, i downgraded from AOL1 to AOK2. not sure if this works with any firmware newer than AOL1. in my case, i reflashed the AOL1 firmware, then downgraded/flashed the AOK2 bootloader and then rooted using the original 9208 root method.

cortez.i said:
check the TWRP thread for details and links to downgrade the bootloader. please note/remember, i downgraded from AOL1 to AOK2. not sure if this works with any firmware newer than AOL1. in my case, i reflashed the AOL1 firmware, then downgraded/flashed the AOK2 bootloader and then rooted using the original 9208 root method.
Click to expand...
Click to collapse
Thanks so much for your advice! I was finally able to roof my phone. Realised that I was being too noobish
Thanks for your time

Lucas Eugene said:
Thanks so much for your advice! I was finally able to roof my phone. Realised that I was being too noobish
Thanks for your time
Click to expand...
Click to collapse
Hi, how do you do it can explain step by step, thanks, i believed many N9208 user need it

Note 5 N9208 6.0.1 Root without Seandroid Error - https://androidmtk.com/root-samsung-galaxy-note-5-duos-sm-n9208

Moto G XT1064 Stock Marshmallow 6.0 Oct 2016 update help

Hi everyone,
Noticed today, there was a system update prompt on my Moto G 2nd gen XT1064. The update is 24.201.4.en.US. Of course I can't install it, because I'm rooted and unlocked. So I went about the procedure of flashing the stock Lollipop image, and relocking the boat loader, so I can get the update. No matter what I try, I can't seem to re-lock the bootloader. I tried the stock Lollipop image, it flashes fine, but when I go to relock the bootloader, I keep getting the error, image not properly signed. I tried this command "mfastboot oem lock" nothing works. I was able to flash TWRP recovery, and load my 6.0 image back up. So I'm back to where I was, but I would like to get the security update. Can someone recommend the best procedure for getting it?
Thanks much!

DaveImagery said:
Hi everyone,
Noticed today, there was a system update prompt on my Moto G 2nd gen XT1064. The update is 24.201.4.en.US. Of course I can't install it, because I'm rooted and unlocked. So I went about the procedure of flashing the stock Lollipop image, and relocking the boat loader, so I can get the update. No matter what I try, I can't seem to re-lock the bootloader. I tried the stock Lollipop image, it flashes fine, but when I go to relock the bootloader, I keep getting the error, image not properly signed. I tried this command "mfastboot oem lock" nothing works. I was able to flash TWRP recovery, and load my 6.0 image back up. So I'm back to where I was, but I would like to get the security update. Can someone recommend the best procedure for getting it?
Thanks much!
Click to expand...
Click to collapse
just flash stock 6.0 firmware, search on the general thread, it will flash stock 6.0 along with stock recovery, there is no problem if you have unlocked bootloader, you only need stock rom, stock recovery and non-rooted

maximuns said:
there is no problem if you have unlocked bootloader,
Click to expand...
Click to collapse
I'm such a noob, I didn't know that. Thanks very much for your help.

Is the complete 6.0 rom not available? I can't find it, just the OTA update.

DaveImagery said:
Hi everyone,
Noticed today, there was a system update prompt on my Moto G 2nd gen XT1064. The update is 24.201.4.en.US. Of course I can't install it, because I'm rooted and unlocked. So I went about the procedure of flashing the stock Lollipop image, and relocking the boat loader, so I can get the update. No matter what I try, I can't seem to re-lock the bootloader. I tried the stock Lollipop image, it flashes fine, but when I go to relock the bootloader, I keep getting the error, image not properly signed. I tried this command "mfastboot oem lock" nothing works. I was able to flash TWRP recovery, and load my 6.0 image back up. So I'm back to where I was, but I would like to get the security update. Can someone recommend the best procedure for getting it?
Thanks much!
Click to expand...
Click to collapse
As your bootloader is updated to 48.86 you cannot downgrade to lollipop and relock the bootloader.Only way to relock is to flash marshamallow update.then you can relock the bootloader

Impossible to put Huawei P9 in stock rom

Hi everybody
Wishing to sell my Huawei P9 I wanted to return it as it came out of the factory but impossible.
It has the bootloader unblock, FRP lock at one time it was unlock and since I tried to make an update it went into lock and the TWRP recovery of installed.
It is under 5.0.1 and android 7 and the number of buils is EVA-L09C530B284.
I tried the 3 methods to install an original ROM of my operator but nothing to do that does not.
- The DLOAD method: it restarts in the recovery twrp there are steps that are done and then it failed all in 2 minutes.
- The forced update method: that's 5% and installation failed.
- With hi suite: everything is going well and said that such is up to date and restart nothing I'm still in the old versions.
I did the 3 methods with the unrooted phone.
I feel that it is the recovery twrp that blocks the installation.
How to install the original recovery and install the official updates?
Thank you in advance for your assistance.

https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849

thank you very much it worked me remains more than re-blocked the bootloader.
How do you do it?
thank you

jerome8 said:
thank you very much it worked me remains more than re-blocked the bootloader.
How do you do it?
thank you
Click to expand...
Click to collapse
Sorry, I don't understand your question.
For both HWOTA (first link) or HWOTA7 (second link) you need to unlock Bootloader first - but you wrote above that previously you had unlocked Bootl8ader, hence you can use the same Bootloader code - it is bound to your eevice.
Asvdescribed in HWOTA instructions, installation of some stock ROMs will automatically relock your Bootloader (it-sa flag in the update.zip, out of your control) - hut you can always unlock it again.

ok it's good I just made an update and everything is back in order it is as if he came out of the box
thank you very much

Can't update to August SP on TA-1004

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?