Related
I understand instructions have been given for going to color OS to CM11S but this update has a few extra files. Please tell me which ones I need to flash in fastboot from the following and in which order?
FIles:
boot.img
cache.img
emmc_appsboot.mbn
filesmap
flash-radio.sh
logo.bin
md5sum-fastboot.md5
NON-HILOS.bin
recovery.img
rpm.mbn
sbl1.mbn
sdi,mbn
system.img
tz.mbn
userdata.img
userdata_64.img
Umair Kamil said:
I understand instructions have been given for going to color OS to CM11S but this update has a few extra files. Please tell me which ones I need to flash in fastboot from the following and in which order?
FIles:
boot.img
cache.img
emmc_appsboot.mbn
filesmap
flash-radio.sh
logo.bin
md5sum-fastboot.md5
NON-HILOS.bin
recovery.img
rpm.mbn
sbl1.mbn
sdi,mbn
system.img
tz.mbn
userdata.img
userdata_64.img
Click to expand...
Click to collapse
Why don't you use the command fastboot update <filename.zip>
I've just downloaded ruu (.exe) file . but it didn't find my phone so i extracted rom.zip which contain following images . now i don't know where to flash them. can you help me pls??
android-info.txt
boot_signed.img
dzdata_4g.hdr
dzdata_4g.img
hboot_2.02.0002_90dc471e_0720.img
lib.img
radio.img
ramdisk.img
rcdata.img
recovery_signed.img
splash1.nb0
system.img
tp_atmelc12_20aa.img
Our old twrp have been great compared to nothing but it isn't exactly fully working and freezes a lot on splash screen.
Thanks to @Stricted and @deadman96385 we now have a more functional twrp.
Support for A/B slots.
ADB working.
No need to flash full firmware. Just flash the vbmeta_patch.img and boot twrp.
!!BOOTLOADER MUST BE UNLOCKED!!
YOUR DATA WILL BE WIPED!!
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Now that we booted to TWRP it's time to format data.
Go to wipe -> format data -> type yes.
"Permanent" install of TWRP (optional):
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot and go to advanced settings.
Use the option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings so that it won't reboot to recovery instead of system..
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
This must be done every time you update your boot.img.
-------------------------------------------------------------------------------------------------------------------------------------------------------
# ROOT:
-----------
# First time:
# Method 1: Root, forced encryption disabled. Full access to data from twrp:
Flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
# Method 2: Root only. Device still encrypted and won't be able to decrypt / mount data in twrp.
Magisk modules through Magisk manager still works:
Flash only Magisk.
----------------------------------------------------------------------------------------------------
# Fastboot flash update without loosing root or data:
----------------------------------------------------------------------------------------
# Already rooted with encryption disabled:
Extract the firmware zip to your adb/fastboot folder.
You already have the patched vbmeta flashed so just remove the stock vbmeta.img from the folder after extraction to avoid flashing it by mistake.
Flash full firmware without wipe. (Use cmds from below. Save as .bat to make it more simple.)
Boot twrp and then install it, fix recovery bootloop.
Reboot recovery, flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
Boot system.
Code:
echo off
echo - UPDATE AND PRESERV ROOT -
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
fastboot reboot bootloader
pause 10
fastboot boot twrp-3.3.1-test3.img
echo TWRP is booting..
echo - install recovery ramdisk, fix bootloop, flash magisk & dm-verity zip.
echo - alternatively flash only magisk and Disable_Dm-Verity_ForceEncrypt.zip if you want to keep stock recovery.
pause
# Already rooted with device still encrypted:
Flash firmware update, except vbmeta.
Boot twrp and flash Magisk with adb sideload.
(alternative method: boot twrp and flash magisk patched boot.img)
Download TWRP: https://images.stricted.net/test/troika/twrp-3.3.1-test3.img
Download Magisk: https://github.com/topjohnwu/Magisk/releases
Download vbmeta_patch.img & Disable_Dm-Verity_ForceEncrypt.zip attached below.
PLEASE, DON't QUOTE THE WHOLE OP.
Can I flash this image from inside existing twrp to update?
wolf45801 said:
Can I flash this image from inside existing twrp to update?
Click to expand...
Click to collapse
Not really. A/B devices doens't have recovery partition to flash the whole img to it's own partition.
Instead we have to install recovery ramdisk in to our boot.img but that option is missing in the old twrp.
I guess you could take the twrp installer zip for the old twrp and replace ramdisk-twrp.cpio in that zip to the ramdisk from new twrp, but I guess it's just easier to fastboot boot the new version and from there choose to install recovery ramdisk.
tys0n said:
Not really. A/B devices doens't have recovery partition to flash the whole img to it's own partition.
Instead we have to install recovery ramdisk in to our boot.img but that option is missing in the old twrp.
I guess you could take the twrp installer zip for the old twrp and replace ramdisk-twrp.cpio in that zip to the ramdisk from new twrp, but I guess it's just easier to fastboot boot the new version and from there choose to install recovery ramdisk.
Click to expand...
Click to collapse
Ok I'll do that thank you
Can't seem to find the download links for the vbmeta en Disable_Dm-Verity_ForceEncrypt.zip
nickholtus said:
Can't seem to find the download links for the vbmeta en Disable_Dm-Verity_ForceEncrypt.zip
Click to expand...
Click to collapse
Ah you're right. I made threads in both action and vision forum but apparently I forgot to add the files here. Sorry about that.
They've been added now.
Reprinted to China xpeira Forum: GFan Author: machao44.Just reproduced, irresponsible
http://bbs.gfan.com/android-9634387-1-1.html
http://bbs.gfan.com/android-9634397-1-1.html
http://bbs.gfan.com/android-9634405-1-1.html
Download Links:
https://drive.google.com/drive/folders/1V11_CgbmDJucoSkD_yyyRqqZuWm-uCGP?usp=sharing
Flash steps:
1.Flash STOCK 52.1.A.2.1 firmware, do not start the device
2.Open the adb folder
XZ2:
fastboot flash boot twrp-xz2.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
XZ2P:
fastboot flash boot twrp-xz2p.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
XZ2C:
fastboot flash boot twrp-xz2c.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
XZ3:
fastboot flash boot twrp-xz3.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
3.Drag boot_X-FLASH-ALL-B6B5.sin in the firmware to UnSIN.exe to decrypt it, and then rename it to kernel.img.
4.Put kernel.img in the boot folder, and then compress it to boot.zip(The correct way is to choose META-INF + kernel.img for compression)
5.Press and hold the volume down and power buttons to enter twrp, connect to the phone and enable MTP mode.
6.Copy boot.zip, twrp-installer-xz2-2c-3.3.x.zip, Magisk-v20.3.zip, fstab.zip to the phone storage, and then refresh. (XZ3 only needs to copy boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip)
7.7.Carry out
Hi all, just received and updated the 11.1.6.6 via OTA... but after reboot I'm locked on the two white dots around the one red icons, and the phone doesn't start anymore.. so it's NOT a bootloop, but just blocked situation..
I'm rooted... what can I do to exit from this situation as well?
Just tried with VOL UP + POWER combo, but this casue only a power off, or a new reboot, but the situation doesn't change and the screen still stuck on the dots animation..
EDIT:
Had to resolve with a full wipe factory reset, no other way.
There was another way. You could've downloaded the latest update package onto your PC, used PayloadDumper to extract the payload.bin file found inside the zip file, extracted Android's 'Platform tools' into the output folder of the payload dump and then ran these commands without wiping while your phone is connected in fastboot:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
You'd lose root but your phone would be updated to the latest OS and your data would hold.
You can then follow the root guide to patch the boot.img extracted from the payload file and let magisk do its thing.