I currently have 5.6.4.0 on my tablet, want to upgrade to 5.6.9.0. TWRP and latest magisk are installed. Will the renaming of the stock firmware .bin to .zip install method wipe TWRP or does it protect itself?
For anyone interested, flashing the firmware renamed to .zip works fine, TWRP and bootloader remain usable.
Related
Okay, folks. I need some help. I was not able to flash new Cyanogen ROM's so I tried updating my TF300T to the latest US firmware. Here are the results and where I stand now.
1. TWRP 2.5 is loaded in recovery.
2. Latest ASUS firmware is installed.
3. Lost root.
4. Tried to re-root and cannot. SuperSU fails every time I try to update the binary.
5. I wipe everything and can boot into recovery.
6. I tell TWRP to flash the latest ASUS firmware zip file.
7. Firmware flashes but then when I go to reboot in TWRP it says that no OS is available!!
8. I can swipe the lock and reboot into 4.2.1 but obviously no root.
9. I have tried flashing the signed superuser file and it flashes and says successful.
10. When I use root checker pro to see if I have root it tells me that I do not have root.
What in the hell is going on????????? Any help or outline of steps would be appreciated.
bshpmark said:
Okay, folks. I need some help. I was not able to flash new Cyanogen ROM's so I tried updating my TF300T to the latest US firmware. Here are the results and where I stand now.
1. TWRP 2.5 is loaded in recovery.
2. Latest ASUS firmware is installed.
3. Lost root.
4. Tried to re-root and cannot. SuperSU fails every time I try to update the binary.
5. I wipe everything and can boot into recovery.
6. I tell TWRP to flash the latest ASUS firmware zip file.
7. Firmware flashes but then when I go to reboot in TWRP it says that no OS is available!!
8. I can swipe the lock and reboot into 4.2.1 but obviously no root.
9. I have tried flashing the signed superuser file and it flashes and says successful.
10. When I use root checker pro to see if I have root it tells me that I do not have root.
What in the hell is going on????????? Any help or outline of steps would be appreciated.
Click to expand...
Click to collapse
Bootloader info plz. Unless you were using the experimental CM10.1 build (or a select few others), it sounds like you tried to flash a ROM compatible only with an older bootloader onto the "latest" build (from your description).
I have an Xperia Z5 with a custom bootloader and a TWRP recovery (obviously rooted and has the Xposed binaries installed). I've tried installing the OTA update for Android 6.0.1 but it keeps failing to install (re-downloaded it over 7 times).
I was wondering if anyone knew where the temporary folder is where the OTA update is stored before installation?
That way, I could download the OTA update again, move it to another folder and install it via the TWRP recovery.
I'm running stock ROM on unlocked bootloader with root through Magisk. I've been using TWRP, but changed over to Blu_spark TWRP recently.
Every time I update my OS Ota, I lose TWRP and Magisk. The Magisk app is installed, but the ROM is not rooted. If course, if I try to install patch the system so it's rooted through the Magisk app, it says that it can't unpack the file. If I reboot to recovery to install from there, I get the stock recovery, not TWRP.
I tried to re-install TWRP and Magisk once before, and borked my phone. I had to quote and start from scratch. I lost all data since I wasn't rooted and Titanium Backup would not run.
What is the proper way to get TWRP and Magisk back after an OTA update?
Flash them after you flash update zip. If you don't you will lose recovery and root every time. Gets overwritten by stock recovery. Normal behavior
Sent from my ONEPLUS A6003 using Tapatalk
So you're saying that instead of doing the OTA update, I should download the update from here, and manually update it ? Can I just install the update? I'm rooted, (well, I was) so the OTA will only download the full update. Is that required instead of the update?
I really have to do a full re-install for every update? That sucks. A lot.
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
MickyFoley said:
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
Click to expand...
Click to collapse
Ok. Cool. I tried that last time, but it failed. As a result, I'm a bit anxious about doing it again. Hopefully, I won't have any problems this time.
Thanks for the info.
I have had similar troubles as you, here's an overview of how to solve those problems.
OTA through OS:
Download and install OTA
Use Magisk Manager to download the TWRP A/B retention script and install it
Install Magisk to current and inactive slot
Reboot
Guys I am using latest blu_spark twrp. my bootloader is unlocked and I am running oxygenOS openbeta23. Following is my problem.
My flash order: (Note: already I have bue_spark twrp recovery running without issues)
1. Flash the full OTA(openbeta)
2. Flash the blu_spark twrp zip file on both active and non active slots.
3. Flash the latest magisk zip file. If step 3 is not successful means I will try to reboot in to recovery and again flash the magisk installer zip.
Until some time back all this worked fine. But for last 2-3 times although the flashing process of twrp zip on both slots ends with success message, when I reboot to recovery from twrp in order to flash magisk, the device boots in to stock recovery. I don't know how even after flashing twrp zip on both slots successfully why the devices bootbback to stock recovery. Then to have blu_spark twrp I have to connect my device to a computer in fastboot mode and then boot in to custom recovery using the blu_spark twrp image file and again flash the blu_spark twrp zip file which is inconvenient and also requires a computer.
Am I missing anything here?? If yes why this method was working perfectly before? Please somebody help.
Regards,
Sivabalan K
I flash in following order my stable updates
Flash full rom zip
Flash bluespark recovery
Restart into bluespark recovery
Flash magisk
Restart into Android
Everything works flawless. Magisk installed with all the modules running
Hi guys,
Don't you need to disable lock pattern/PIN or fingerprint/face ID? And don't need to uninstall magisk modules?
I never update my OP6 from my initial unlock/twrp/magisk and I'm a bit anxious to do it now...
Thanks
PS : I'm using original twrp (3.2.3-1), is this a problem?
Hey everyone, I messed up today trying to root with Magisk using a firmware zip with a different incremental version (but same OOS version) as my device. After flashing the patched boot.img my device is stuck in a bootloop. Unable to boot into system (the text "turn off" with a progress/loading bar shown on my wallpaper), fastboot is still available.
Firmware version before flashing: IN2013_11.C.36_1360_202210310935
Firmware version that the wrong boot.img was extracted from: IN2013_11.C.36_1360_202210171428 (from this thread, under "signed flashable zips>Europe")
Magisk version: 25.2
Recovery: stock
TWRP?: no
I would rather not have to go through the MSM route/fully restore to stock firmware as I am under the impression that these will wipe my data.
I'm now looking for anyone who has the full firmware zip for OOS 12 incremental version (IN2013_11.C.36_1360_202210310935) so that I can extract the stock boot.img file myself. I'm hoping that this manages to fix my mistake.
If anyone is currently running this version and also has TWRP it would also be great if you can follow this guide to extract your boot.img directly from your device.
Another option I am looking into is to flash a stock ROM (with a different build number but the same OOS version: IN2013_11.C.36_1360_202210171428) into my inactive slot without wiping data, I'm not sure if that's wise. Does anyone know if that will work?
update:
- tried booting into older versions of IN2013 firmware using fastboot boot boot.img to no avail.
- Based on the fact that I definitely did an OTA incremental update after upgrading to OOS 12 before, maybe the boot.img was tied to the incremental update zips instead. So, I tried extracting boot.img from incremental update zips (from here, importantly did not have C.36 incremental zips yet) using the FastbootEnhance payload dumping tool, but got the error "multiple dst in one operation" and was unable to continue with this idea.
possible solutions:
1. Flash a full stock firmware to partition A and boot to that. Will this wipe my data?
2. Wait for a full stock firmware zip of IN2013_11.C.36_1360_202210310935 and extract the boot.img myself to flash.
3. Wait for an incremental update zip for C.36 to be uploaded.
4. Somehow find and transfer the stock boot.img that Magisk supposedly makes a backup of when you patch boot.img with the app.
update 2: FIXED
Tried IN2015_11.C.36_1360_202210310935 from this thread for fun. Extracted the boot.img from this one and flashed it. It somehow worked even though it's for a different version????
Doubled checked Oxygen Updater and I am indeed running OTA version IN2013_11.C.36_1360_202210310935.
So, I rooted my phone, for which I needed to unlock the bootloader and install TWRP. Now, when I want to install an update on my phone, it downloads and when I want to install it, it jumps to TWRP recovery instead of the phone's recovery, so I can't update my phone. Does anyone know how can I install the updates from TWRP?
Else, reinstall the default recovery. (Only the recovery, not the entire OS since that would un-root my phone)
Thanks.
Edit: After it boots to TWRP, it apparently tries to install the update, since I can see it on the log, but when I reboot my phone it has not installed. It errors: "E3994: This package is for "2169B" devices; this is a "". Updater process ended with ERROR: 1. Error installing zip file '/data/ota_package/OTA/.otaPackage/my_manifest_RMX3370_11.F.04_3040_202302282047.44.36402b59_all.zip'
Edit 2: After failing to install it, it prompts me to re-download it and re-install it, but it jumped from ~500MB update to 4.76GB update.
( may loose data)
I read in telegram channels, this twrp: https://www.pling.com/p/1922292 support installation latest zip. but I haven't tried.
one more thing you can do is ( may loose data)
1. restore twrp backup for recovery partition ( if you don't have backup. search recovery.img in upgrade zip )
2. reboot to recovery to check stock recovery is installed
3. install update
4. then follow steps to install twrp and magisk ( root again )
SanOne+1 said:
( may loose data)
I read in telegram channels, this twrp: https://www.pling.com/p/1922292 support installation latest zip. but I haven't tried.
one more thing you can do is ( may loose data)
1. restore twrp backup for recovery partition ( if you don't have backup. search recovery.img in upgrade zip )
2. reboot to recovery to check stock recovery is installed
3. install update
4. then follow steps to install twrp and magisk ( root again )
Click to expand...
Click to collapse
Your guide is incorrect and will definitely put the device into bootloop.
** The twrp link that you shared doesn't allow system updates to install, it is just a A13 compatable twrp recovery.
1) What if that person has not created any twrp backup of all system partitions? According to his explanation, I'm pretty sure he has not created any backup of the partitions.
2) only flashing recovery image and installing the update will again put the device into bootloop because as confirmed by the OP that his device is rooted and due to root the boot image of the device gets modified so it will put the device into bootloop.
3) unless the OP has stock boot and recovery images at his disposal he should not attempt to install the update to avoid bootloop.
** Kindly avoid sharing incorrect information you aren't sure about the correct procedure.
procedure that I follow to flash updates :
1) in magisk - uninstall magisk - restore images
2) boot device into bootloader and flash stock boot and recovery.
3) boot device and install update.
4) put device again in bootloader and flash twrp and within twrp flash magisk and reboot.
I haven't found any easier way than this. If anyone has, kindly put it below.
There's a way
Rui 4.0 Android 13 f.02
So, any verdict on this new update for the people that did update to it?
forum.xda-developers.com
Recetly I succesfully updated my Realme GT Neo 2 5G via TWRP recovery, the latest version support OTA.
Attention! After update TWPR and Magisk gone. Just reflash twrp and flash magisk normally. No need to reflash modules etc. (Just update from settings, no need to manually flash ota package from TWRP)
Hello mate can u help me with something real quick. Y are there no recent updates for gt neo 2 and if u r using a custom rom based gt neo 2 hows ur experience so far. Thanks in advance
Xemi_KryTeT.pl said:
Recetly I succesfully updated my Realme GT Neo 2 5G via TWRP recovery, the latest version support OTA.
Attention! After update TWPR and Magisk gone. Just reflash twrp and flash magisk normally. No need to reflash modules etc. (Just update from settings, no need to manually flash ota package from TWRP)
Click to expand...
Click to collapse
Which rom r u running and is it good?
Sabirsayed09 said:
Hello mate can u help me with something real quick. Y are there no recent updates for gt neo 2 and if u r using a custom rom based gt neo 2 hows ur experience so far. Thanks in advance
Which rom r u running and is it good?
Click to expand...
Click to collapse
Latest stock (4.0), I'm not going to flash custom roms for now