I extracted the boot.img from the latest factory Android 10 and made it into .tar. If I install it via Odin, would I then be able to downgrade to the Samsung factory firmware v10? If not, can I downgrade to Android 11?
boot.img is just the kernel, it's not really what's keeping you from downgrading. If you want to use something like Android 10 you're going to have to install custom recovery (root) and flash boot.img, system.img, vendor.img and a few things I may be missing. And even then, this isn't a guarantee that it'll boot.
Once bootloader updates there is no flashing backwards. The only way you can is if the firmware you are flashing to has same bootloader version that you are already on
idk if its even possible
because it'll cause a bootloop
my suggestion is - dont try it
Related
Hi All
I have a nexus 9 with an unlocked bootloader, root (from CF auto-root), and TWRP installed, currently on 5.0.1 LRX22C. I have read this means that I will not be able to complete an OTA due to lack of stock recovery and changes within the system files that the OTA will check.
So my question is how much of stock do I have to return to be able to do the OTA to 5.0.2 and 5.1 later today. I am hoping that I won't have to do a factory reset and wipe all the files and apps, but if so nevermind.
Do I have to relock the bootloader?
Do I have to flash back to stock completely or can I just flash a stock recovery?
If I wait will a flashable zip be created by someone, that would allow me to keep unlocked and rooted?
If this has been asked before, I am sorry, I have searched but couldn't find any clear answers that were related to lollypop.
I am used to samsung phones and the nexus ADB sideloading ect. is taking me a while to get used to, so any link to a guide would be very appreciated.
Thanks for any help,
OTA appears to checksum the entire partitions, so even remount RW could have an effect (with no intentional accesses, depending how the filesystem works). However, this doesn't make a lot of sense since any update is going to struggle to replicate the same raw filesystem data reliable - maybe this is why we are seeing 5.0.2 OTAs fail on 'stock' devices.
fallen2004 said:
Hi All
I have a nexus 9 with an unlocked bootloader, root (from CF auto-root), and TWRP installed, currently on 5.0.1 LRX22C. I have read this means that I will not be able to complete an OTA due to lack of stock recovery and changes within the system files that the OTA will check.
So my question is how much of stock do I have to return to be able to do the OTA to 5.0.2 and 5.1 later today. I am hoping that I won't have to do a factory reset and wipe all the files and apps, but if so nevermind.
Do I have to relock the bootloader?
Do I have to flash back to stock completely or can I just flash a stock recovery?
If I wait will a flashable zip be created by someone, that would allow me to keep unlocked and rooted?
If this has been asked before, I am sorry, I have searched but couldn't find any clear answers that were related to lollypop.
I am used to samsung phones and the nexus ADB sideloading ect. is taking me a while to get used to, so any link to a guide would be very appreciated.
Thanks for any help,
Click to expand...
Click to collapse
Do not relock your bootloader. It is not necessary.
Since you are rooted with a custom recovery, if you want to take the OTA, you will have to fastboot flash the stock 5.0.1 system.img, recovery.img, boot.img, and vendor.img.
IMHO, it's just as easy to fastboot flash the 5.0.2 factory images and forget about the OTA.
cam30era said:
Do not relock your bootloader. It is not necessary.
Since you are rooted with a custom recovery, if you want to take the OTA, you will have to fastboot flash the stock 5.0.1 system.img, recovery.img, boot.img, and vendor.img.
IMHO, it's just as easy to fastboot flash the 5.0.2 factory images and forget about the OTA.
Click to expand...
Click to collapse
Okay well I think I will wait until the 5.1 factory image is released, backup my phone, then fastboot flash it.
I guess I will then have to reroot and add TWRP again?
fallen2004 said:
Okay well I think I will wait until the 5.1 factory image is released, backup my phone, then fastboot flash it.
I guess I will then have to reroot and add TWRP again?
Click to expand...
Click to collapse
Do it in the other order. Fastboot flash TWRP, then flash SuperSU from inside TWRP. Very easy.
So if you've updated to the new security patch. It patches twrp. Meaning you can flash it. But it instantly get patched by the stock recovery. Im thinking if we can find a way to downgrade the firmware. We can get twrp and root and the custom roms :highfive: Bc
we can use the fastboot to get into twrp and flash something to downgrade us but thats about it. If you can Id really love the help of you guys! Just don't update to the new patch. I did with twrp causing this whole mess on my end .
anyone please dont let this thread die we need to get this fixed
RootMega said:
anyone please dont let this thread die we need to get this fixed
Click to expand...
Click to collapse
it's common sense you need stock recovery and stock system to use an OTA update.
And yes if you choose to install an OTA update with TWRP installed it will get replaced with stock recovery.
It's no big deal you can use the dload/update.app method to update the phone and then simply boot TWRP and Install the TWRP.img from TWRP
by using Install / Image / yourTWRP.IMG
idk i tried to flash the test build and it oem flashed and Now I need a puk code
Hi
First a little history...
I recently got an OPX with the intention of installing Sailfish OS on it. So first I need to get CM 12.1 installed. Following the instructions here I flashed TWRP using fastboot, but the version of TWRP provided at the link would not find any system partitions on my device and therefore could not be used to flash any images. Newer versions of TWRP would simply not load.
Eventually, using the stock OPX recovery, I managed to upgrade Oxygen OS to the latest version. I then flashed the latest version of TWRP (3.1.1-1) again and it worked! It found my devices partitions and I could flash ROMs with it. But, it wouldn't flash CM 12.1. Something about a trustzone incompatibility...
So I got the idea to try and downgrade Oxygen OS, which I did via TWRP. But then TWRP stopped working... and here is my problem.
I'm now stuck in a situation where:
- I can access fastboot
- The only versions of TWRP which work (e.g. 3.0.2-0) fail to find my system partitions, and therefore can't be used to flash ROMs
- The stock recovery also seems to fail to find the system partitions (clicking on "install locally" does nothing), so I can't use that to flash ROMs either
So I really need to get a working image on my phone somehow... but how?? Is it possible to do this via fastboot only?
Cheers!
Is your bootloader unlocked? TWRP cannot see system partitions if so.
I unlocked it originally... but since then I have installed a new ROM (Oxygen OS 2.x). Would this overwrite the bootloader? Do I need to unlock again? I think I must be using the old OOS bootloader now...
I think you can see if it's unlocked if you boot into bootloader, connect to pc and write on cmd "fastboot devices".
Whenever you switch between android 5.0 roms and 6.0 and further you have to first use the correct recovery from oneplus, only then you can flash the correct twrp and the adequate roms
My bootloader is unlocked. I cannot flash a new ROM via recovery, because none of the recovery images (stock, TWRP) can see my system partitions (I don't know why). At this stage I would just like to know if there is a way to flash a stock ROM/recovery/bootloader via some other method (fastboot, or a special tool), so I can restore my phone back to factory state. I don't care about losing data. Thanks.
EDIT: Just to clarify, I believe this is my current situation (please correct me if something doesn't make sense):
- OOS has two different bootloaders, 2.x and 3.x.
- The phone originally had OOS 2.x on it. None of the TWRP images I installed recognized my system partitions, so I couldn't flash with TWRP.
- After re-installing the stock recovery (which happened automatically when I booted to the stock ROM), I was able to upgrade to OOS 3.x via stock recovery. Now recent TWRP versions were working (I assume because upgrading to OOS 3.x updated the bootloader too), and were recognizing my system partitions.
- Using a new version of TWRP (3.1.1-1), I re-flashed an older version of OOS 2.x again. I think this was my mistake, because I think this downgraded the bootloader to 2.x again. Now none of the TWRP versions recognize my system partitions, so I cannot flash ROMs.
- I have re-flashed the stock recovery from the OnePlus website, but not even this allows me to flash ROMs. The symptoms look like in TWRP, i.e. that it fails to recognize my system partitions. So I am stuck with no way to flash ROMs, or upgrade the bootloader.
Desperate help needed to go back to stock (Mate 10 Pro EMUI 8 TWRP & MAGISK) BLA-L09
Hello there. I'm used to Samsung devices and the more I read about Huawei devices the more lost I feel about them.
So, my Mate 10 pro BLA-L09 is currently running Build Number 8.0.0.131(C782). It is rooted with Pretoriano's TWRP and Magisk (Using the All-In-One tool). Of course, I can't get any pending update installed. I would like to receive that EMUI 9 update. I've read people have been successful using HuRupdater and some others ended up with a hard bricked device. Some other people suggest the safest option is to uninstall Magisk, flash stock recovery and let the phone update itself.
So far, I've downloaded the same full 8.0.0.131(C782) firmware I'm on from Firmware Finder and downloaded Huawei Update extractor to extract the recovery from UPDATE.APP. However, instead of having one recovery file to extract, there are 3 Recoveries (named: RECOVERY_RAMDIS, RECOVERY_VBMETA, RECOVERY_VENDOR) and another 4 E-Recoveries.
Can anyone please give me some step by step guidance on what to do? I'll Paypal you a beer if I'm successful with the help.
Cheers!
May be you can simply dload the firmware and then it should be full stock if dload works. Dload guide is given in my signature
shashank1320 said:
May be you can simply dload the firmware and then it should be full stock if dload works. Dload guide is given in my signature
Click to expand...
Click to collapse
Thanks! But I think dload won't work with custom recovery, right? I'm on TWRP. And getting stock recovery is just what I'm trying to achieve.
93starletgt said:
Thanks! But I think dload won't work with custom recovery, right? I'm on TWRP. And getting stock recovery is just what I'm trying to achieve.
Click to expand...
Click to collapse
Dload replaces your twrp and custom boot both. It will bring back your phone to full stock. Else you could extract the images from your firmware and then flash. Let me give you the commands.
Thanks! I just fixed my issue by flashing this through TWRP: it Installs the Oreo stock recovery.
The procedure was:
-Booted into TWRP
-Uninstalled Magisk (by flashing Magisk Uninstall Zip)
-Flashed the stock recovery (from the link below) through TWRP
-Reboot
-Check for system updates, phone will install them with no problems
Phone will be unrooted and will have stock recovery. Don't know if this will work for every stock build, it worked with mine 8.0.0.131(C782).
Link:
https://mega.nz/#!8Swx3QaC!3JQ9imU70E9O1BxgO53Z754lGCZxCbKGgSHqvTEcXsQ
I was getting the command ready for you. Glad you fixed it yourself
[*]Run the command to boot to fastboot
Code:
adb reboot bootloader
[*]On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
[*]Flash the stock Recovery Ramdisk as
Code:
fastboot flash recovery_ramdisk <Recovery_File_Name>.img
[*]If you have installed magisk, flash the stock boot ramdisk.img as
Code:
fastboot flash ramdisk <ramdisk_File_Name>
so i think i bricked my phone.
i downloaded the ROM from https://miuirom.org/load?o=mi-10t-and-mi-10t-pro&v=13.0.8.0.SJDMIXM&l=en&t=Recovery
and then patched it with magisk
and followed the tutorial
i dont know what i did wrong
my phone is xioami 10t pro
tried flashing it back to the unpatched boot.img and it still got stuck in a boot loop
Please help me
should i try to wipe data im not sure if it will make it more complicated, sorry im a idiot when it comes to these things
i might know what the problem it
just now i realized that my phone is android 10 with miui 13,
cant find stock rom for anroid 10 miui 13 for my phone
when flashing magisk_patched.img it may break encryption depending on settings patched.
you can download stock ROM here
https://new.c.mi.com/global/miuidownload/index
or here
https://xiaomifirmwareupdater.com/archive/miui/apollo
aIecxs said:
when flashing magisk_patched.img it may break encryption depending on settings patched.
you can download stock ROM here
https://new.c.mi.com/global/miuidownload/index
or here
https://xiaomifirmwareupdater.com/archive/miui/apollo
Click to expand...
Click to collapse
already flashed my entire phone, i downloaded the rom for my phone but wrong verion of the android and miui, thx.