Hi,
I followed @nooted1's advice in Question on A12 and rooting. I understood that upgrading from A11 to A12 includes a factory reset. Now I'm on A12 and wanted to update from T870XXU2CULC to T870XXU2CVCD (patch level Decmber 21 to April 22). I Odin'd AP, then a tar archive containing boot.img.lz4 and vbmeta.img.lz4, patched by Magisk. Both Odin uploads ended in the tablet demanding a factory reset.
Is there a way to update A12 without losing all data yet?
There are two correct ways, and the key is never flash stock AP without patching vbmeta at the same time. Never let the stock vbmeta.img flash to your device. The stock vbmeta.img in stock AP will enable Android verified boot and will lead to factory reset in the next boot.
First and preferred method:
1. use magisk to patch the whole AP file and magisk will patch both boot.img and vbmeta.img.
2. Flash magisk patched AP in AP slot and BL and HOME_CSC, and done.
Second method:
1. Download vbmeta_disabled.tar from https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. Patch boot.img using magisk.
3. Uncheck auto reboot in ODIN, flash stock AP in AP, BL in BL and HOME_CSC in CSC slot, and vbmeta_disabled.tar in USERDATA slot at the same time. With the vbmeta_disabled.tar, the stock vbmeta.img won't be flashed to your device. Remember to flash them at the same time in ODIN. If you flash vbmeta_disabled.tar after flashing stock AP, it will ask for factory reset.
4. Check auto reboot in ODIN, flash magisk patched boot.img in AP slot.
googlephoneFKLenAsh said:
1. use magisk to patch the whole AP file and magisk will patch both boot.img and vbmeta.img.
2. Flash magisk patched AP in AP slot and BL and HOME_CSC, and done.
Click to expand...
Click to collapse
That worked for me. Thank you!
Related
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Spocki990 said:
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Click to expand...
Click to collapse
You've got the kernel and recovery messed up on your device from the failed flash of twrp and magisk. I would start over by flashing the factory image using the flash all batch file with the -w edited out of it. Then try again booting twrp, not flashing it. Once you try to flash the twrp image file you pretty much have to start over with the stock boot image. When you boot into twrp you'll want to allow modifications. You also need to setup a pin or pattern security for your system so twrp will decrypt your device.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Spocki990 said:
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Click to expand...
Click to collapse
you are my hero. My phone was stuck in the situation you describe after installing active edge. I was thinking about wipe my pixel 3 until I saw your post. Thank you !:good:
Hi, I'm having trouble with Magisk re-installation.
First I installed Magisk using the flashing boot.img method, it was working correctly but I tried to remove the youtube vanced module, when it asked for a reboot it went straight to the bootloader, I just re-flashed the original boot.img to the phone and got it working again. the issue came when I tried to reinstall Magisk from scratch again. Whenever I tried to install it the process would go without any issue but when I tried to start the system it is going to the bootloader again.
I tried installing twrp using this guide and got the custom recovery working on both slots, then I tried to flash magisk using the zip file, the installer ran without throwing any issues but when I tried to reboot again to the system it still goes to fastboot, this time not only corrupting the system start but also the twrp recovery. I haded to reflash the stock boot.img image on slot A and the twrp image on slot B to re install twrp on both slots.
Also using the TWRP tried running the uninstall magisk zip but whenever I try to run it it just fails because it cannot find the magisk.img file and exits by telling that I have not installed magisk.
Tried erasing the folders inside of /data/adb but its the same issue all over again.
Does anyone has any idea or suggestion on what could I try to fix the issue?
Thanks
Try flashing patched boot image (the same version as your system) and boot into the system, go into magisk manager and do complete uninstall. Or download the latest Magisk uninstaller and try from TWRP again. Recent versions of Magisk ditched magisk.img, so you might be using old version of the uninstaller.
_mysiak_ said:
Try flashing patched boot image (the same version as your system) and boot into the system, go into magisk manager and do complete uninstall. Or download the latest Magisk uninstaller and try from TWRP again. Recent versions of Magisk ditched magisk.img, so you might be using old version of the uninstaller.
Click to expand...
Click to collapse
Tried using the lastest uninstaller found on the topjohnwu/Magisk repository, which did not show any error but after installing magisk the phone still goes to bootloader, then tried to run the uninstaller again but it only works on the b slot and to run it on the a slot I have to reflash boot.img and then install twrp on both slots.
But thanks for the sugestion.
jtcp2703 said:
Tried using the lastest uninstaller found on the topjohnwu/Magisk repository, which did not show any error but after installing magisk the phone still goes to bootloader, then tried to run the uninstaller again but it only works on the b slot and to run it on the a slot I have to reflash boot.img and then install twrp on both slots.
But thanks for the sugestion.
Click to expand...
Click to collapse
I would restore stock ROM, skip TWRP installation and flash just correct patched boot image.
_mysiak_ said:
I would restore stock ROM, skip TWRP installation and flash just correct patched boot image.
Click to expand...
Click to collapse
Do you know where can I find the lastest stock rom? Right now I'm on 10.3.9.0 PFQEUXM, or if the lastest is not possible, could I flash a older version of the rom without any trouble?
jtcp2703 said:
Do you know where can I find the lastest stock rom? Right now I'm on 10.3.9.0 PFQEUXM, or if the lastest is not possible, could I flash a older version of the rom without any trouble?
Click to expand...
Click to collapse
Try to find the full OTA zip for the latest version (or at least the same you have) and extract it with this tool https://github.com/cyxx/extract_android_ota_payload
Xiaomi hasn't released the fastboot rom for the recent updates yet.
So far I was able to find only global links here (they should work too, but rather backup your data first). http://4pda.ru/forum/index.php?showtopic=962154
You might have luck installing older fastboot EU ROM, but again, backup your data first.
If you did not enable "allow system modifications" in TWRP, it should be enough to flash only stock boot image (there are links to them somewhere on this forum).
Also I would avoid installing TWRP.
Sapper Morton said:
The complete firmware images, can only be found in .tgz archives, payload.bin OTAs only contains incremental firmware updates; thus you won't be able to successfully restore, system, vendor, boot, critical partitions and etc; the recommended method is to restore to either 10.3.4.0 PFQMIXM or 10.3.7.0 PFQEUXM, both .tgz archives, complete firmware inside. @_mysiak_
Click to expand...
Click to collapse
There are usually two types of OTA zip files, small incremental ones (which you described) - for monthly updates and full OTA (1-2gb in size) - for direct update across several versions. You can create all needed fastboot images from the full OTA payload.bin with before mentioned python extractor script.
Sapper Morton said:
You can try for yourself, I wasn't able to restore using this images (assuming of course you have a corrupt, system, vendor, boot, ... partition): https://bigota.d.miui.com/V10.3.6.0...UTGlobal_V10.3.6.0.PFQMIXM_00713c5a1d_9.0.zip
I was only able to return to global channel, by using 10.3.4.0 PFQMIXM firmware, .tgz archive.
Click to expand...
Click to collapse
By wasn't able to restore you mean that you couldn't convert payload.bin to fastboot images, or that converted fastboot images were not working?
I've just extracted these files from payload.bin from the link you provided (with this app). I don't have a phone to test them though (I did the same thing a few times on Mi A1 and flashing, phone and OTA worked afterwards).
Code:
abl.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
hyp.img
imagefv.img
keymaster.img
modem.img
product.img
qupfw.img
rpm.img
storsec.img
system.img
tz.img
uefisecapp.img
vbmeta.img
vendor.img
xbl.img
xbl_config.img
Hi all,. for a friend I am trying to root a G398FN (PHN) with Magisk and a patched boot file. I went thru the unlocking process at the bootloader, I took the latest android Q firmware and with 7Zip Zs I unzipped the AP file, and then I got the boot.img.
Magisk says it is patched, then I use ADB to GET the file back on my PC, and then I flash it with Odin.
I have tried all sorts of combinations, flashing the patched boot alone, flashing the enitre AP file, flashing the patched AP file alone, and the complete firmware, but in any case I end up with a phone that should have a patched boot, but doesn't. Magisk is not a stub, and Magisk asks for the original rooting method.
Does anybody know what I am doing wrong here ? The patched boot is downloaded via ADB, then flashed with the latest Odin but the phone is not accepting the changes.
So i Have a Xcover 4s G398FN with android Q latest firmware, latest Odin, unlocked bootloader and I have tried almost every combination there is to make the phone work with the patched boot. What is happening here? Any help would be greatly apreciated.
Hi,
coming from BTF2 with TWRP and Magisk, updated and rooted the device according to current guides:
- Download ROM with Frija (SM-T865, DBT, T865XXU4BTI1/T865OXM4BTI1/T865XXU4BTI1)
- Unpack it
- Magisk-patch the AP file using Canary manager and magisk zip
- Flash AP, BL, CP, CSC with Odin 3.14.4 (after testing HOME_CSC without success)
- Wipe the device
Magisk works fine until I reboot.
No matter how long I hold the VolUp button (until the unlocked bootloader screen, until the "not running original software" screen), Magisk Manager returns that Magisk is not installed and Root Checker returns that the root installation is broken.
Flashing the AP, BL, CP, HOME_CSC again, Magisk works again, until the next reboot.
Current workaround for me would thus be to reinstall Magisk directly after every reboot to make sure it sticks for the next reboot.
Anyone got an idea what's wrong here?
Edit: I just noticed my 256GB LTE tablet only has 32GB of storage after flashing??
Edit: Reflashed all stock files, device is back to 256GB storage. Now trying again with magisk patching...
Thanks and regards,
sub
Lots of re-flashes and playing around later, it works.
magisk manager canary, installing the canary magisk build.
patched with preserve force encryption and recovery mode.
after flash, reboot, go to sys recovery (hold up all the time), wipe.
reboot, hold up until bootloader warning.
install magisk manager canary, connect internet.
run manager, it asks for an installation.
do that, during reboot hold VolUp until bootloader warning just to be safe.
i hate samsung, again
I can't flash TWRP or Magisk Manually i keep getting this message.
Anyway to fix this?
Tabs7+ T970 Wifi
Bootloader Unlocked.
Edit:
Fixed: Installed Magisk Canary and Patched AP file was able to flash It with odin.