Related
1) Backup the current boot image
> adb shell "dd if=/dev/block/mmcblk0p22 of=/sdcard/originalBoot.img"
> adb pull /sdcard/originalBoot.img
2) Get the stock kernel sources from htcdev.com.
3) Go into the top kernel directory and pull the kernel config file from the device
> adb pull /proc/config.gz
> cat config.gz | gunzip > .config
4) Build kernel
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler"
5) The resulting kernel is in arch/arm/boot/zImage
6) Use the following command to pack kernel and ramdisk into a boot image
> mkbootimg --kernel My_zImage --ramdisk My_ramdisk.gz --cmdline "no_console_suspend=1" --base 14400000 --output MyBoot.img
7) Install boot image
> adb reboot bootloader
> fastboot flash boot MyBoot.img
> fastboot reboot
Here you can download a ramdisk for the Sensation XL
http://www.eidelen.ch/android/sensationXL-ramdisk.gz
If the device doesn't start anymore, go into the fastboot mode and install the backup of the original boot image.
> fastboot flash boot originalBoot.img
Good Luck!
Building Modules
Building:
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" modules
Installing:
> adb shell "mount -o remount,rw -t ext4 /dev/block/mmcblk0p25 /system"
> adb push drivers/net/wireless/bcm4330b2/bcm4330.ko /system/lib/modules/
> adb push drivers/net/kineto_gan.ko /system/lib/modules/
Note: If you don't have default root shell session (ro.secure=0 in file default.prop), you have to do the installing steps manually:
> adb shell
> su
> mount -o remount,rw -t ext4 /dev/block/mmcblk0p25 /system
> cp bcm4330.ko /system/lib/modules/
> ...
eidelen said:
1) Backup the current boot image
> adb shell "dd if=/dev/block/mmcblk0p22 of=/sdcard/originalBoot.img"
> adb pull /sdcard/originalBoot.img
2) Get the stock kernel sources from htcdev.com.
3) Go into the top kernel directory and pull the kernel config file from the device
> adb pull /proc/config.gz
> cat config.gz | gunzip > .config
4) Build kernel
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler"
5) The resulting kernel is in arch/arm/boot/zImage
6) Use the following command to pack kernel and ramdisk into a boot image
> mkbootimg --kernel My_zImage --ramdisk My_ramdisk.gz --cmdline "no_console_suspend=1" --base 14400000 --output MyBoot.img
7) Install boot image
> adb reboot bootloader
> fastboot flash boot MyBoot.img
> fastboot reboot
Here you can download a ramdisk for the Sensation XL
http://www.eidelen.ch/android/sensationXL-ramdisk.gz
If the device doesn't start anymore, go into the fastboot mode and install the backup of the original boot image.
> fastboot flash boot originalBoot.img
Good Luck!
Click to expand...
Click to collapse
If only did the backup bit, is it same as nandroid backup?
"dd if=/dev/block/mmcblk0p22 of=/sdcard/originalBoot.img" just backups the boot image (kernel), whereas nandroid backups probably also the system and data.
With above command, you could also backup the whole system
"dd if=/dev/block/mmcblk0p25 of=/sdcard/originalSystem.img".
You can get a list of partitions and their meaning with
> cat /proc/emmc (on some devices its mmc)
eidelen said:
"dd if=/dev/block/mmcblk0p22 of=/sdcard/originalBoot.img" just backups the boot image (kernel), whereas nandroid backups probably also the system and data.
With above command, you could also backup the whole system
"dd if=/dev/block/mmcblk0p25 of=/sdcard/originalSystem.img".
You can get a list of partitions and their meaning with
> cat /proc/emmc (on some devices its mmc)
Click to expand...
Click to collapse
So if I do system image backup will it also include backup of boot image as well or I need to do them separately. Thank you for your help.
You need to do them separately, since boot image and system are on different partitions.
I could make you a flashable.zip from Stock kernel..... Easy for all to use
DutchDanny said:
I could make you a flashable.zip from Stock kernel..... Easy for all to use
Click to expand...
Click to collapse
please make me one pls
DutchDanny said:
I could make you a flashable.zip from Stock kernel..... Easy for all to use
Click to expand...
Click to collapse
Please make this for all
I have a ridiculous question
if have stock kernel, can download any update from htc ?!
Or else the difference is ?!
Please explain what is difference stock kernel and custom kernel ?!
DutchDanny said:
I could make you a flashable.zip from Stock kernel..... Easy for all to use
Click to expand...
Click to collapse
It might be good for those which don't backup the kernel.
Anyway, this is about development and I strongly hope, that nobody is wasting time by installing his kernels with flashable zips when there exitsts 'fastboot'. One would get bloody fingers
nader1450 said:
Please make this for all
I have a ridiculous question
if have stock kernel, can download any update from htc ?!
Or else the difference is ?!
Please explain what is difference stock kernel and custom kernel ?!
Click to expand...
Click to collapse
The stock kernel is released by the manufacturer. The mobile is delivered with that kernel. A custom kernel may offer additional things like overclocking, etc. You have to inform you about the differences of that particular kernel.
If you have a custom kernel installed, a HTC update might install again the stock kernel.
I have made a flashable zip of the STOCK kernel
FIND IT HERE
There is a possibility from someone to have 2 cwm flashable zip file for the new img of bootloader "bootloader-tilapia-4.18.img" and radio "radio-tilapia-1231_0.17.0_1205.img".
I hope yes . Regards
manolohd said:
There is a possibility from someone to have 2 cwm flashable zip file for the new img of bootloader "bootloader-tilapia-4.18.img" and radio "radio-tilapia-1231_0.17.0_1205.img".
I hope yes . Regards
Click to expand...
Click to collapse
radio-tilapia-1231_0.17.0_1205.img
bootloader-tilapia-4.18.img
philos64 said:
radio-tilapia-1231_0.17.0_1205.img
bootloader-tilapia-4.18.img
Click to expand...
Click to collapse
.zip file for a flash with cwm recovery?
manolohd said:
.zip file for a flash with cwm recovery?
Click to expand...
Click to collapse
Not, but you can use my guide for flash to your N7
You don't need ADB, follow the guide and it will be good -
for the bootloader, just rename it bootloader and use this code
Code:
fastboot flash bootloader bootloader.img
and for the radio :
Code:
fastboot flash radio radio.img
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
thankyou, another question: now in my nexus i have a custom rom 4.2.2 "unofficial xylon 2.1" if i use fastboot metood to flash new bootlooader and new radio, i can loose my data my recoverymod cwm and my custom rom?
or i must do all with a stock rom and recovery stock?
Ty
manolohd said:
thankyou, another question: now in my nexus i have a custom rom 4.2.2 "unofficial xylon 2.1" if i use fastboot metood to flash new bootlooader and new radio, i can loose my data my recoverymod cwm and my custom rom?
or i must do all with a stock rom and recovery stock?
Ty
Click to expand...
Click to collapse
Go to see and apply my new guide : [GUIDE][BOOTLOADER][4.2.2] TILAPIA JDQ39 - 4.18 Flash Image Instructions
I wish to modify the system image on my Xperia Z3+. I seem to be having trouble creating a fastboot flashable .img file that allows the phone to boot.
To test, I extracted the .ext4 file from the stock firmware system.sin that is currently installed on my Z3+ using FlashTool's SIN extractor. I mounted the resulting ext4 image using the loopback filesystem, following which I executed the command
Code:
make_ext4fs -s -l 5513412608 -a /system system.img system
The partition size is taken directly from the AOSP BoardConfig.mk for this device. I made no modifications to the filesystem - it's stock. It flashes successfully with fastboot using the same command that successfully flashes a AOSP built system.img
Code:
fastboot flash -s 256M system system.img
The system won't boot when fastboot flashing the converted SIN to IMG. There's something wrong with the way I'm creating the system.img file. It makes no difference if I add the SELinux file_contexts with the -T option and the file_contexts located in the system image.
Anyone have any pointers?
give some extra blocks
I modified the system image of 28.0.A.27 to include the newer stagefright libs from .251 and a su executable (unsucsessful: RIC and maybe SELinux).
I checked the image and added some - rounded up - extra blocks for my modifications (ls -l).
The device (Tablet Z4) booted but the media server did not come up and the booting did not finish. I could adb shell but had no touch GUI.
Maybe yours is another problem. If you can adb shell I would check the log.
And I did it this way (no /):
Code:
make_ext4fs -s -l 5big_number8 -a system system.img system
DHGE said:
I modified the system image of 28.0.A.27 to include the newer stagefright libs from .251 and a su executable (unsucsessful: RIC and maybe SELinux).
I checked the image and added some - rounded up - extra blocks for my modifications (ls -l).
The device (Tablet Z4) booted but the media server did not come up and the booting did not finish. I could adb shell but had no touch GUI.
Maybe yours is another problem. If you can adb shell I would check the log.
And I did it this way (no /):
Code:
make_ext4fs -s -l 5big_number8 -a system system.img system
Click to expand...
Click to collapse
I tried with and without the / but same problem. I can't get an adb shell as the device doesn't even start booting - it sticks on the Sony logo.
This recovery has been superseded by Eliminater74's TWRP.
This post and its files remain for archival purposes.
-- Old OP --
Note: I no longer own this device. To help test, join my Testing Discord (Please read the rules presented when you join.)
Note: There is a known bug with restoring backups. If you need to use the backup/restore features, please do not use Melina TWRP until rel_o3 is released, which has no eta.
The following releases are unofficial and will always be due to dirty edits.
However, it offers the following features over the official release:
Oreo Only Features:
Integrated Melina Kernel (rel_o2) into TWRP build system (rel_o2 or newer)
Oreo kernel (nougat kernel cannot mount unencrypted /data for some reason) (rel_o1 or newer)
Disabled encryption (rel_o1 or newer) (Note: LGE uses forceencryption now, and also has a script to replace your custom recovery with their own. Please flash my anti-root removal tool, which will remove rctd, forceencrypt, and the anti-custom-recovery script)
Nougat/Oreo Features:
Integrated Melina Kernel (rel_nr2) into TWRP build system (rel_t2 or newer)
Integrated uber-toolchain 6.x for kernel compilation into TWRP build system (rel_t2 or newer)
Stability and performance increases over rel3 (rel_t1 or newer)
/vendor partition support (if you have not repartitioned, which at the time of this release, 99% of you haven't, then you may get an error in TWRP regarding mounting storage. This is safe to ignore) (rel_t1 or newer)
/misc bootloop fix (rel_t1 or newer)
Date and time fix (msm8996 workaround) (mixed reports, but works for me on US997 with Stock and Fulmics ROMs, see this post for more information)
Option to wipe LG lockscreen security settings when restoring data partition (workaround for known issue where sometimes you get locked out of restored stock ROMs)
NTFS support (untested, should allow NTFS USB-OTG for restoring backups and flashing zips, read-only)
SD-Ext support (including backing up and restoring, both ext4 and F2FS supported thanks to Melina)
Purple theme, because purple is cool
Based on J0SH1X's work.
Downloads (bold is current):
Oreo
rel_o2
US997
H870
rel_o1
US997
H870
Nougat
rel_t2
US997
H870
rel_t1
US997 (old)
H870 (old)
rel3
US997 (old)
H870 (old)
rel2
US997 (old)
H870 (old)
Usage:
Unzip file and flash recovery.img
Please keep in mind I only have the US997 so help test this for H870!
Current Known issues:
Restoring backups does not work, due to tar process terminating with error 255.
You must format data when coming from a stock ROM due to LG using forceencrypt.
Fixed issues:
Disabled encryption (fixed in rel_o1)
E:Unhandled flag: 'removeable' (fixed in rel_t2)
Slow SDCard Performance (fixed in rel_t1)
MTP reliability (fixed in rel_t1)
GPL (dev info):
Read the readme on the github.
If my releases help you, please leave a thanks. If you are able, please consider a tip (check the small link in my sig).
Prompt for password to decrypt data
I installed the 3.2.1 version by flashing the img from the older 3.1.1 version.
When I rebooted to recovery, it prompted me for a password to decrypt the data. I don't remember encrypting the data and I do not know the password. I was able to tap cancel and get to the main TWRP screen.
Should I be worried about this?
DonS said:
I installed the 3.2.1 version by flashing the img from the older 3.1.1 version.
When I rebooted to recovery, it prompted me for a password to decrypt the data. I don't remember encrypting the data and I do not know the password. I was able to tap cancel and get to the main TWRP screen.
Should I be worried about this?
Click to expand...
Click to collapse
That is strange, I don't use encryption and never had that. I guess if the data was accessible after hitting cancel, I wouldn't worry about it. Which device?
I have the US997 version.
I didn't try flashing anything from TWRP, I just booted to make sure it showed the new version number. I rebooted to the system and everything is working fine.
DonS said:
I have the US997 version.
I didn't try flashing anything from TWRP, I just booted to make sure it showed the new version number. I rebooted to the system and everything is working fine.
Click to expand...
Click to collapse
Try flashing the img through fastboot as per normal rather than through TWRP, then when you reboot into recovery, regardless if you get the message or not, go to the backup menu and be sure Data has more than (0 MB) next to it on the list.
Oh, also, the old 3.1.1 (the one I didn't make) had an issue where if you used "Format Data" (with yes option) it actually created a corrupt file system, so that could be it as well. To fix that, execute the following under adb shell:
umount /dev/block/sda19
e2fsck -f /dev/block/sda19
(Select y for yes to repair if prompted)
Then reboot recovery and try again. You shouldn't lose data using these commands. However, if it does find and repair errors, it is not out of the question, but is something you'll want to address.
@zefie flashed the H870 build (flashed the img trough official TWRP), no password, data in backup is 8893MB, time is working fine, if you have other things to check just tell me.
BTW no purple theme, don't know why
Killua96 said:
@zefie flashed the H870 build (flashed the img trough official TWRP), no password, data in backup is 8893MB, time is working fine, if you have other things to check just tell me.
BTW no purple theme, don't know why
Click to expand...
Click to collapse
Probably just the header, is the slider purple?
Edit: nevermind, I know why, didn't define my theme in the h870 config. Rebuilding.
Edit 2: Fix should be up. Also updated US997 since this is Melina rel6 now (previous release used a pre-release version of rel6)
hello and thank you for this
anyway, I wanted to flash it under twrp as an image
it asks me :
"select partition to flash image"
-boot
-recovery
-system image
-modem
-persist
also is it ok to flash this with Fulmics ROM?
dave_id said:
hello and thank you for this
anyway, I wanted to flash it under twrp as an image
it asks me :
"select partition to flash image"
-boot
-recovery
-system image
-modem
-persist
also is it ok to flash this with Fulmics ROM?
Click to expand...
Click to collapse
It's a recovery, so you need to choose "recovery".
Also is fine with Fulmics, i've tested it on H870
just wanted to be sure, so THANKS!
zefie said:
Try flashing the img through fastboot as per normal rather than through TWRP, then when you reboot into recovery, regardless if you get the message or not, go to the backup menu and be sure Data has more than (0 MB) next to it on the list.
Oh, also, the old 3.1.1 (the one I didn't make) had an issue where if you used "Format Data" (with yes option) it actually created a corrupt file system, so that could be it as well. To fix that, execute the following under adb shell:
umount /dev/block/sda19
e2fsck -f /dev/block/sda19
(Select y for yes to repair if prompted)
Then reboot recovery and try again. You shouldn't lose data using these commands. However, if it does find and repair errors, it is not out of the question, but is something you'll want to address.
Click to expand...
Click to collapse
I flashed from fastboot instead of TWRP and I get the same thing. I get prompted for a password to decrypt data. I flashed the old 3.1.1 TWRP and I don't get that error. If I go into backup with TWRP 3.2.1 data shows 0 MB. With 3.1.1 it shows the actual size.
I rebooted to the system and connected a USB cable and went into a ADB shell. the first command returns an error. I thought your first command had a typo and you mean unmount instead of umount. I'll paste the error below.
C:\ADB>adb shell
lucye:/ $ umount /dev/block/sda19
umount /dev/block/sda19
umount: bad /etc/fstab: No such file or directory
1|lucye:/ $ unmount /dev/block/sda19
unmount /dev/block/sda19
/system/bin/sh: unmount: not found
127|lucye:/ $
DonS said:
I flashed from fastboot instead of TWRP and I get the same thing. I get prompted for a password to decrypt data. I flashed the old 3.1.1 TWRP and I don't get that error. If I go into backup with TWRP 3.2.1 data shows 0 MB. With 3.1.1 it shows the actual size.
I rebooted to the system and connected a USB cable and went into a ADB shell. the first command returns an error. I thought your first command had a typo and you mean unmount instead of umount. I'll paste the error below.
C:\ADB>adb shell
lucye:/ $ umount /dev/block/sda19
umount /dev/block/sda19
umount: bad /etc/fstab: No such file or directory
1|lucye:/ $ unmount /dev/block/sda19
unmount /dev/block/sda19
/system/bin/sh: unmount: not found
127|lucye:/ $
Click to expand...
Click to collapse
The error is because it's not mounted at all (since it sees 0 MB), so just skip to the second command.
zefie said:
The error is because it's not mounted at all (since it sees 0 MB), so just skip to the second command.
Click to expand...
Click to collapse
Here is what I get when running the second command:
C:\ADB>adb shell
lucye:/ $ e2fsck -f /dev/block/sda19
e2fsck -f /dev/block/sda19
/system/bin/sh: e2fsck: can't execute: Permission denied
126|lucye:/ $
I have gone back to TWRP 3.1.1 and in the backup screen it does show the proper size for the data volume.
DonS said:
Here is what I get when running the second command:
C:\ADB>adb shell
lucye:/ $ e2fsck -f /dev/block/sda19
e2fsck -f /dev/block/sda19
/system/bin/sh: e2fsck: can't execute: Permission denied
126|lucye:/ $
I have gone back to TWRP 3.1.1 and in the backup screen it does show the proper size for the data volume.
Click to expand...
Click to collapse
Run it in either TWRP, not under Android.
zefie said:
Run it in either TWRP, not under Android.
Click to expand...
Click to collapse
OK, here are the results from TWRP 3.1.1 terminal
umount /dev/block/sda19 returns an error
umount: can't umount /dev/block/sda19: invalid argument
e2fsck -f /dev/block/sda19 returns an error:
/dev/block/sda19 is in use.
e2fsck: cannot continue, aborting.
DonS said:
OK, here are the results from TWRP 3.1.1 terminal
umount /dev/block/sda19 returns an error
umount: can't umount /dev/block/sda19: invalid argument
e2fsck -f /dev/block/sda19 returns an error:
/dev/block/sda19 is in use.
e2fsck: cannot continue, aborting.
Click to expand...
Click to collapse
Invalid argument should not happen. Personally I'd make a back and reformat data. You say everything works but it's only a matter of time before the corruption catches you off guard. You could try the two commands on my TWRP, but if it's still saying invalid argument, back up and reformat. (With yes screen format option not just wipe data)
Thank you so much for your work. It is the only version which is working on mine.
@zefie is it somehow possible to convert ext4 to f2fs without loosing data?
Thanks for your strike work! [emoji4]
Gesendet von meinem LG-H870 mit Tapatalk
saenta said:
@zefie is it somehow possible to convert ext4 to f2fs without loosing data?
Thanks for your strike work! [emoji4]
Gesendet von meinem LG-H870 mit Tapatalk
Click to expand...
Click to collapse
Not conventionally. You could let TWRP back up sd-ext while ext4, and reformat it f2fs, but if you try to restore it in the TWRP GUI I think it'll format it back to the original format. That said, you could then manually extract the twrp backup files (they are just tar files, so something like tar -C /sd-ext -xf /path/to/sd-ext.ext4.win000 or whatever.) Extract them in numerical order.
If you are talking about built-in partitions like /data or /cache, don't do it, as ROMs have to be configured specifically to support f2fs, so it wouldn't work anyway.
bump for rel3
New Features:
Updated and Integrated Melina Kernel (rel7) into TWRP build system
Option to wipe LG lockscreen security settings when restoring data partition (workaround for known issue where sometimes you get locked out)
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7 Pro in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
FLASHER ADVANCED GUIDE
flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=294300
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro
OnePlus 7 Pro Persist: https://androidfilehost.com/?fid=6006931924117929081
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (you need to extract images.zip before proceed)
Fastboot Partitions:
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
If you need also persist partition, this is the command:
Code:
fastboot flash persist persist.img
Criticals Partitions, for these you need to boot the TWRP:
Code:
fastboot boot TWRP.img
When you are in TWRP you need to run these commands to push and flash all criticals partitions:
Code:
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
adb push odm.img /sdcard/odm.img
adb shell dd if=/sdcard/odm.img of=/dev/block/bootdevice/by-name/odm_a
adb shell dd if=/sdcard/odm_config.img of=/dev/block/bootdevice/by-name/odm_b
adb push tz.img /sdcard/tz.img
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_a
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_b
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
Thanks to @SaiBork for first time tested
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
I know you said not for branded devices, are the partitions different for these devices?
Just wondering if this could be what we need to convert the T-Mobile version and if so if you need tester.
criptix said:
I know you said not for branded devices, are the partitions different for these devices?
Click to expand...
Click to collapse
Yes, sometimes also the rom is different. Actually the branded devices can't use this rom also if they want, because to use this rom you need to have an unlocked bootloader
Yeah figured bootloader would need to be unlocked as well.
If you happen to need testers for the conversion ( if your working on it) let me know.
I just SIM unlocked my T-Mobile variant today, and also applied for my unlock .bin on the OnePlus site!
Thank you! You revived my phone!
zzs001 said:
Thank you! You revived my phone!
Click to expand...
Click to collapse
Perfect, like for others oneplus devices i will continue to support them, if you want to contribute and help me, please consider making a donation, thanks.
I've F-ed my international 7 Pro up, used your flash all, seemed to have work, but stuck in a loop now... Anyone got any suggestions, please?
I was so happy when I found this post, I thought my problems were over, but yeah... apparently not
posedatull said:
I've F-ed my international 7 Pro up, used your flash all, seemed to have work, but stuck in a loop now... Anyone got any suggestions, please?
I was so happy when I found this post, I thought my problems were over, but yeah... apparently not
Click to expand...
Click to collapse
which version you had before use fastboot rom? which fastboot rom did you used?
I was on stock, tried to install twrp, didnt go well (wouldn't mount), and i wanted to wipe data/cache, and mistakenly wiped system as well because i wasnt paying attention. Tried putting the stock recovery, still wouldnt boot due to obvious reasons.... then I found this
Basically I had the 9.5.4 with deleted system when I attempted to use the flash all bat.
GM21BA, european 12gb one, if it makes any difference...
posedatull said:
I was on stock, tried to install twrp, didnt go well (wouldn't mount), and i wanted to wipe data/cache, and mistakenly wiped system as well because i wasnt paying attention. Tried putting the stock recovery, still wouldnt boot due to obvious reasons.... then I found this
Basically I had the 9.5.4 with deleted system when I attempted to use the flash all bat.
GM21BA, european 12gb one, if it makes any difference...
Click to expand...
Click to collapse
So you should use the 9.5.4 fastboot rom, have you used it?
of course.
I am hoping maybe a failed download, so I just redownloaded it and trying again now
posedatull said:
of course.
I am hoping maybe a failed download, so I just redownloaded it and trying again now
Click to expand...
Click to collapse
The process can take a lot of time, just wait until you see something like "presse a key to proceed"
also:
"extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.386s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk..."
tose missing files, is that normal?
downloaded your zip, extracted it, started flash-all.bat, no modifications done whatsoever
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
the zip finishes, no problem,ends with
"writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 153.005s
Press any key to exit..."
and then the phone tries to boot, i get to the spinning 1+ logo, and it stays there for even an hour if i let it...
posedatull said:
also:
"extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.386s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk..."
tose missing files, is that normal?
downloaded your zip, extracted it, started flash-all.bat, no modifications done whatsoever
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
the zip finishes, no problem,ends with
"writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 153.005s
Press any key to exit..."
and then the phone tries to boot, i get to the spinning 1+ logo, and it stays there for even an hour if i let it...
Click to expand...
Click to collapse
so i don't know, try to use the other flashall, you should unpack image.zip and other flashall in the main folder and then you should run the flash-all-fastboot.bat.
If you want you can try to flash the twrp in the boot partition and then try to flash the stock rom through sideload
i've just tried all of them one by one... still bootloop every time
posedatull said:
i've just tried all of them one by one... still bootloop every time
Click to expand...
Click to collapse
do you want to contact me on telegram? Maybe i can help you better
i'm struggling this at work, but i'll be home in about 2hours.
if you could help then, i would seriously appreciate it
posedatull said:
i'm struggling this at work, but i'll be home in about 2hours.
if you could help then, i would seriously appreciate it
Click to expand...
Click to collapse
Yes yes, write me on telegram, the nick is always the same: mauronofrio
hello, how long should it take to first boot after flashing all? I'm waiting for so long...