Extract stock Recoveries, system img, vendor etc by own....
Follow the link
https://forum.xda-developers.com/honor-6x/how-to/extract-stock-recovery-img-boot-img-img-t3676880
Related
I don't feel like downloading 1.6GB just for 60M update, so this is partial OxygenOS OTA update converted into file based patch using xdelta3 so that it works with modified system partition. Every file is checked by its md5 first before patching to prevent incorrect update.
Notes
the stock recovery (recovery-from-boot.p & bin/install-recovery.sh) is not included in this recovery, so it will not overwrite your TWRP and there is not need to reboot to TWRP after appying the update
text files are not patched but installed full
files in lib/modules are installed full
first boot will takes longer time than usual
Requirements
You should be on stock OxygenOS 4.5.13
Download
https://drive.google.com/open?id=0BwihXEEuntymZERzaGJSZmFVZEE
How to install
reboot to recovery
backup boot, system, data
install firmware.zip
install system.zip
install boot.img
install any custom kernel
install any mods that modifies the ramdisk e.g. magisk, supersu, dm-no-verity.zip
reboot
Hey guys,
I followed a guide I found to root my G6 (ALI): https://forum.xda-developers.com/moto-g6/how-to/guide-twrp-root-magisk-installation-t3816569 and now have an unlocked bootloader, magisk installed and TWRP as my recovery.
I have flashed TWRP to recovery on my g6. Whenever I try to flash a custom system image I made (I wipe cache and data), or modify /system in TWRP, everything looks fine in the TWRP file manager. However, when I go to boot my phone it takes longer than usual to boot, encrypts my files and all the changes I made are undone.
The only thing that has successfully modified /system was the magisk manager when it patched my boot image.
What is going on?
Thanks.
Welcome​First of all make sure You know the Basics which are:
-You need to have a unlocked Bootloader
-You need to have the Orange Fox Recovery installed
-You need to have a Kernel and a Vendor Image
-You need to have a Treble A-Only Generic System Image (GSI)
-(Optional) A actual Magisk Installer zip File
-(Optional) A actual Open GApps Installer zip File
(Just use Google and You will find everything)
Alright. Now to the flashing!
-Make sure You have the needed Basics on Your Device including the Files You want to flash
-Wipe everything including data, caches, system, vendor
-Now flash a Vendor and Kernel Image to Your Device
-(You can download My "Vendor Installer" or)
-Flash a Treble AOSP ROM for Your Device and wipe System again
-Flash the Generic System Image using the Image Install from TWRP
DONE!
If You want to install Root and GApps on Your Device:
-Reboot to the Recovery and wipe Data/Caches again
-Install Magisk and GApps (Nothing else yet)
-Reboot to the System
DONE!
This Thread will be updated from Time to Time with new Vendor Installers and better Instructions. Feel free to talk about GSI ROMs in this Thread. I will keep it moderated as good as i can!
Download Links:
https://sourceforge.net/projects/orangefox/files
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Vendor Installer from Me: https://drive.google.com/drive/folders/1onzbCmoy18WlNDNFpq67z0Bv7QHB1d-b?usp=sharing
Actual Vendor: OMNI with EAS Kernel
Hello, I can not flash this vendor file. The orange fox returns ERROR7
q13017 said:
Hello, I can not flash this vendor file. The orange fox returns ERROR7
Click to expand...
Click to collapse
There is a more actual thread around the Mix 2 Forum. Try to search for it over Google, it provides more actual Vendors if i'm not wrong
Hi all! has someone managed to install and use the Pixel experience GSI image? It's stuck on the google logo loading screen for me, maybe i need another vendor?
Atcastells said:
Hi all! has someone managed to install and use the Pixel experience GSI image? It's stuck on the google logo loading screen for me, maybe i need another vendor?
Click to expand...
Click to collapse
Same issue here - the last working version is from March 2019.
If I put a gsi with a vendor from custom firmware, will my phone die?
Hello, last night I have unlocked the bootloader flashed twrp -0 official build and magisk it was all good and was working then i wanted to install the last eu beta and flashed but flashing it always corrupting the file system, to solve it I have flashed stock rom via fastboot
Problem here I do not wipe /system directory but whenever I try to flash a custom rom the file system directory is corrupting and consequently the device is stucking on twrp. Is there an idea?
MertFatih said:
Hello, last night I have unlocked the bootloader flashed twrp -0 official build and magisk it was all good and was working then i wanted to install the last eu beta and flashed but flashing it always corrupting the file system, to solve it I have flashed stock rom via fastboot
Problem here I do not wipe /system directory but whenever I try to flash a custom rom the file system directory is corrupting and consequently the device is stucking on twrp. Is there an idea?
Click to expand...
Click to collapse
1. It must to be in QUESTIONS & ANSWERS and not in GUIDES, NEWS, & DISCUSSION.
2. What exactly corrupted? There is system partition which is not file system And there is a data partition which you can call a file system
3. If the problem was in system partition you would be stuck in fastboot.
4. What steps did you make after flashing stock rom via fastboot?
For flashing eu beta ROM after flashing stock rom via fastboot, the steps are:
1. FORMAT (not wipe) data.
2.Wipe cache/dalvik cache (don't wipe system or flash a ROM without reboot).
3.Flash eu ROM.
You can try another TWRP for example: https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825 , official TWRP is based on it or from Chines team: http://files.mi-room.ru/files/twrp/cepheus/3.3.1-1030/recovery.img . Both very good.
g_seva said:
1. It must to be in QUESTIONS & ANSWERS and not in GUIDES, NEWS, & DISCUSSION.
2. What exactly corrupted? There is system partition which is not file system And there is a data partition which you can call a file system
3. If the problem was in system partition you would be stuck in fastboot.
4. What steps did you make after flashing stock rom via fastboot?
For flashing eu beta ROM after flashing stock rom via fastboot, the steps are:
1. FORMAT (not wipe) data.
2.Wipe cache/dalvik cache (don't wipe system or flash a ROM without reboot).
3.Flash eu ROM.
You can try another TWRP for example: https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825 , official TWRP is based on it or from Chines team: http://files.mi-room.ru/files/twrp/cepheus/3.3.1-1030/recovery.img . Both very good.
Click to expand...
Click to collapse
Update: after format, it stucks on twrp(directories are not encrypted), and rom is not flashing at all I mean it is not writing to /sdcard (loading screen says it successfully flashed but not in the reality )and there are only 'obb' and 'TWRP' directories in the /sdcard also the twrp version is not even change by fastboot or flashing img after a reboot it recovers itself to build -0
I will try it with the Chinese teams's twrp build for this time
Solved with another twrp version
I was able to compile the realme X2 Pro's official kernel release from https://github.com/realme-kernel-opensource/realmeX2pro-X3-AndroidR-kernel-source and I got 3 files generated in arch/arm64/boot folder.
They are:
Image
Image-dtb
Image-dtb-hdr
I just wanted to know how to move further to be able to flash just this kernel (I have a GSI image flashed on /system from TWRP).
Based on the partitions I saw from TWRP, the ones I feel relevant are: Boot partition, Dtbo partition, Vendor Image partition. Which one is it and how do I package the kernel/device tree blob file above to be able to flash to one of these via fastboot? Is that even a valid operation?
I don't want to risk a trial and error approach and possibly screw up further (I have backups of these partitions, but still I'd love to get some insights from the community who might've done this before)
Thanks!