Related
Hello,
I'm planing to test Magisk for a temporary Root on device.
Can I test a patched_boot.img with "fastboot boot patched_boot.img" CMD.
Will the result be the same as if I directly flash with "fastboot flash boot /path/to/patched_boot.img" CMD until I restart my device ?
As I hope, Is there less risk with this method ?
No. You can't boot a boot image the same way you can with a recovery image.
The nature of Magisk makes it very safe though. The only modification to your device is the boot image, so if anything goes wrong you can simply flash the stock boot image (a compressed copy is saved in /data) or dirty flash your ROM.
Actually, In 5.1 I was able to gain temporary root or test my magisk patched boot.img. upon reboot magisk manager did not detect magisk install. I now pan to test disabling dm-verity in this same manner. I hope this helped.
I have was trying to flash the TWRP recovery in my phone (Redmi 4a), but the recovery always got replaced after every reboot with the STOCK recovery.
I am now going to show how to flash this, beside the command line technique......(Although, some command line is necessary).....
1. Set adb and fastboot files in your Windows pc, fine
2. Now download the required twrp on to your pc and place it in adb-fastboot's folder.... or techies could path to that ****....
3. Enter bootloader with.....
adb reboot bootloader4. Now boot to twrp using......
fastboot boot recovery.img(I have named that twrp file as recovery)
5. Download super su zip, move it in phone, root your device....... reboot your device.......Now the second phase of process comes
6. Install twrp app in your phone, open it, copy the twrp image file to phone, tap on flash recovery
7. Select your twrp recovery in the phone and boom....... you have done it...... reboot to recovery by adb reboot recovery
I FORGOT TO MENTION, you should have your device unlocked, and I AM NOT RESPONSIBLE FOR ANY MISHAP and FOR THE STATE TO PLAY CRICKET WITH YOUR PHONE...... I am honest ....... IT WORKED FOR ME......
any tester n confirmed worked ?
No reason to do all those, you can flash recovery directly from fastboot with one command. The command:
Code:
fastboot boot recovery.img
just boot to that recovery one time. This is good for testing a recovery or use it for one time without install it.
If you want to flash a recovery you just need to use:
Code:
fastboot flash recovery recovery.img
Also for both commands isn't necessary to rename the recovery file or to put it adb folder, or root the device. Just need to specify the path and filename in place of "recovery.img". For e.g:
Code:
fastboot flash recovery C:\Phone\Recoveries\twrp_3.2.1.img
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) 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 6T in fastboot mode (Power and volume-);
Connect the OnePlus 6T 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=284914
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 6T
BRANDED PHONE
GUIDE: https://forum.xda-developers.com/on...-t-mobile-oneplus-6t-to-t3865966/post78131430
T-Mobile OnePlus 6T Internationa ROM: https://www.androidfilehost.com/?fid=11410963190603845445
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 fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash fw_4u1ea_b fw_4u1ea.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
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 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
Thanks to @Dark Nightmare for T-Mobile Rom Version
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
If you are unable to use pools or moneybox, you can also make a normal donation, all private donations will be added in the moneybox:
Thanks Mister :good:
Great work, thx
This is great work. Thanks!
If anyone has the T-Mobile firmware or OTA captured, please post it.
Would it be wise to extract the zip to the 6T prior to rooting just in case something goes wrong?
shizat63 said:
Would it be wise to extract the zip to the 6T prior to rooting just in case something goes wrong?
Click to expand...
Click to collapse
This fastboot rom are completely stock rom, not modified
mauronofrio said:
This fastboot rom are completely stock rom, not modified
Click to expand...
Click to collapse
Right.
So before rooting the device, would it be good to copy the images from this zip to a dir on the 6T in case something goes wrong with the rooting process? For example if Magisk or TWRP mess something up, and the 6T is in a bootloop.
Or are the images in the zip only for flashing from your PC to the 6T? So it would be of no use to have the images sitting on the 6T as a backup.
Hello. after flashing with flash-all.bat, my 6T just boots to the bootloader unlocked warning and stays there. I don't know what to do next.
EDIT: Nevermind, after trying again it worked.
shizat63 said:
Right.
So before rooting the device, would it be good to copy the images from this zip to a dir on the 6T in case something goes wrong with the rooting process? For example if Magisk or TWRP mess something up, and the 6T is in a bootloop.
Or are the images in the zip only for flashing from your PC to the 6T? So it would be of no use to have the images sitting on the 6T as a backup.
Click to expand...
Click to collapse
Actually there is not a twrp that support decryption so if you also have the images on the phone you can't flash it in twrp mode. At this moment these roms can be only flashed through fastboot with a pc
Seoyoon said:
Hello. after flashing with flash-all.bat, my 6T just boots to the bootloader unlocked warning and stays there. I don't know what to do next.
EDIT: Nevermind, after trying again it worked.
Click to expand...
Click to collapse
Perfect:good:
thank you thank you thank you OP! Nearly bricked my phone while trying to install root (something got messed up with TWRP) and I couldn't even get out of bootloader into recovery. I just got my phone a few hours ago, that would have been sad
nhshah7 said:
thank you thank you thank you OP! Nearly bricked my phone while trying to install root (something got messed up with TWRP) and I couldn't even get out of bootloader into recovery. I just got my phone a few hours ago, that would have been sad
Click to expand...
Click to collapse
Perfect:good:
If you want to support this and others my projects please consider making a donation, thanks.
After using flash-all.bat I'm getting the "Your device is corrupt" red error message on boot. I can skip by pressing power twice and phone boots normally.
I see people with 6 had to use MSM download tool to get rid of the error.
Is there any solution for 6T?
nhshah7 said:
thank you thank you thank you OP! Nearly bricked my phone while trying to install root (something got messed up with TWRP) and I couldn't even get out of bootloader into recovery. I just got my phone a few hours ago, that would have been sad
Click to expand...
Click to collapse
Just for the sake of your sanity in the future, if you can get to bootloader and device files are available, you can always get it up and running. I learned that very quickly way back in the day
iaTa said:
After using flash-all.bat I'm getting the "Your device is corrupt" red error message on boot. I can skip by pressing power twice and phone boots normally.
I see people with 6 had to use MSM download tool to get rid of the error.
Is there any solution for 6T?
Click to expand...
Click to collapse
Only msm tool i think
Well same situation here got boot loop trying to root then after install using flashall.bat now I can't get a VOLTE and now I complete lost signal but when I swap my sim card to sim slot 2 everything work...kinda weir but does anyone know how to fix it?
_BГ@ckθut said:
Well same situation here got boot loop trying to root then after install using flashall.bat now I can't get a VOLTE and now I complete lost signal but when I swap my sim card to sim slot 2 everything work...kinda weir but does anyone know how to fix it?
Click to expand...
Click to collapse
Did you have a branded version?
mauronofrio said:
Did you have a branded version?
Click to expand...
Click to collapse
Oh I has unlock one from on plus website and use it on Verizon...is that what u mean...sorry I'm new to OP device
Edit: I try to do fastboot flash modem A and B also factory reset but seem not work...
_BГ@ckθut said:
Oh I has unlock one from on plus website and use it on Verizon...is that what u mean...sorry I'm new to OP device
Click to expand...
Click to collapse
Branded version are different, they have a particoular partitions for volte, i think the only.method to solve your problem is to find another person with the same branded device and make a partitions backup that you can restore
mauronofrio said:
Branded version are different, they have a particoular partitions for volte, i think the only.method to solve your problem is to find another person with the same branded device and make a partitions backup that you can restore
Click to expand...
Click to collapse
So how do I make that? Do I need provide any information or anything?
[GUIDE][HOW TO] Flashing with care & Surviving soft bricks with fastboot [CMD] [TIPS]
Hello guys, some of us are new to the A/B partitions. Flashing on wrong partition may end up in soft bricks. This is not a rooting guide, here I'm explaining how to handle flashing A/B partitions properly and survive soft bricks using fastboot . Always backup your data before flashing anything.
Those who still don't know about the A/B partitions, please take a look at this thread https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Prerequisites:
OnePlus 6T with unlocked or locked bootloader
A computer for running fastboot commands
You :laugh:
Rebooting
Rebooting your device via adb and fastboot
Code:
adb reboot //normal reboot
adb reboot recovery //reboot to recovery
adb reboot bootloader //reboot to fastboot (bootloader)
Code:
fastboot reboot //normal reboot
fastboot reboot bootloader //reboot to fastboot (bootloader)
Unlocking the Bootloader
Bootloader can be unlocked via fastboot
Code:
fastboot oem unlock
WARNING THIS WILL WIPE YOUR DATA
Working with A/B Partitions
There are two boot partitions on this device, named boot_a and boot_b respectively, they are not the “traditional” boot partitions. Both of these partitions contain a kernel and ramdisk like you are probably used to. The difference is that there is no recovery partition and the boot partition is new recovery partition. The A/B partitioning scheme can be quite confusing to users. There are actually two copies of many of the partitions. There is only one data (userdata) partition.
Slots
The concept of ‘slots’ comes into play to determine whether you are booting ‘slot A’ or ‘slot B’. We can determine which slot is ‘active’ or marked for booting via adb and fastboot:
Code:
adb shell getprop ro.boot.slot_suffix
Code:
fastboot getvar current-slot
Switching Slots
We can switch between slots via fastboot:
Code:
fastboot set_active other //switch to inactive slot
Code:
fastboot set_active (a or b) //switch to specified slot
Flashing/Booting
We can flash/boot (temporary flash) recovery/kernel via fastboot. To boot (what we call temporary flash) a kernel/recovery there is no need to switch/select any slot. Keep in mind that when we run the flash command instead of boot, it will wipe the specified partiton (you may lose your root & custom kernel)
Code:
fastboot boot boot.img or twrp_recovery.img
To flash permanently, first switch/select any slot you want or it will automatically flashed to the active slot. This may cause boot loop, always proceed with caution.
Code:
fastboot flash boot boot.img or twrp_recovery.img
Code:
fastboot flash recovery twrp_recovery.img
If your testing something, always use the inactive slot. Eg: if you want to test a custom rom, first back up your data then switch to the inactive slot and flash the custom rom, this will save your time (no need restore full backup only data).
Surviving Soft Bricks
Some possible simple solution we can try rather than using MSMTool or flashing the full rom.
When causing boot loops, try these:
Flash Magisk via recovery
Switch to the other slot via fastboot
Wipe data partiton via fastboot -w
When causing Bootloader crash, try these:
Turn off the phone by holding the power button (release after power off)
Hold both volume buttons
Now press power button
Phone will boot to fastboot
Now switch the other slot via fastboot
To be continued....
Just in case
This is my first A/B device so forgive my ignorance, I was wondering if its possible to flash two different roms on to different slots...like oxygen on one partition and lineage on other?
Also why twrp has two buttons 'slot a' and 'slot b' in reboot section?
The phone doesn't have recovery partition, so what happens on typing 'Fastboot flash recovery' command?
Thanks again for this tutorials. That's really helpful in understanding of the new Android features.
What'd be your advice on instructions to get stock kernel back? I couldn't find an appropriate command on how to do it
patelparth120595 said:
This is my first A/B device so forgive my ignorance, I was wondering if its possible to flash two different roms on to different slots...like oxygen on one partition and lineage on other?
Also why twrp has two buttons 'slot a' and 'slot b' in reboot section?
The phone doesn't have recovery partition, so what happens on typing 'Fastboot flash recovery' command?
Click to expand...
Click to collapse
You can install any rom on both slot, there is no problem. There is only one userdata partiton. The two buttons are for switching between slots, if you press slot a button, the recovery will mark slot a as bootable or active partition. On next boot or reboot rom from slot a will boot, this same thing is applied for slot b too. There is no dedicated partition for recovery , files for recovery are stored in system_root.
geminium said:
Thanks again for this tutorials. That's really helpful in understanding of the new Android features.
What'd be your advice on instructions to get stock kernel back? I couldn't find an appropriate command on how to do it
Click to expand...
Click to collapse
Get stock boot.img file and flash using fastboot
Code:
fastboot flash boot boot.img
AnoopKumar said:
You can install any rom on both slot, there is no problem. There is only one userdata partiton. The two buttons are for switching between slots, if you press slot a button, the recovery will mark slot a as bootable or active partition. On next boot or reboot rom from slot a will boot, this same thing is applied for slot b too. There is no dedicated partition for recovery , files for recovery are stored in system_root.
Click to expand...
Click to collapse
Thanks for the reply. Cleared all my doubts.
So could we have two ROMs and switch back and forth between on one device in this case?
geminium said:
So could we have two ROMs and switch back and forth between on one device in this case?
Click to expand...
Click to collapse
Because of one userdata partition, there will be some issues. If wipe data when switching roms, no issues then.
Man i could use some help patched the file moved it to harddrive tried fastboot flash boot boot.img (the patched one) and all i get is
C:\Users\seang\OneDrive\Desktop\Moto G Stylus 2021>fastboot flash boot boot.img
error: cannot open 'boot.img' Could you please make a guide with some pics or at least a step by step cause nothing i have tried has gotten root yet. Thanks!
Thanks to the OP.
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Screenshots of Havoc OS gsi running on my zte axon 10:
Android Q Gsi works too
you can also use the zte android 9 stock kernel and vendor
That all is great news.....bravooo
Any issues with the havoc gsi?
blcistheking said:
Any issues with the havoc gsi?
Click to expand...
Click to collapse
Only the Fingerprint is broken
noobstyle1337 said:
Only the Fingerprint is broken
Click to expand...
Click to collapse
its only broken if you have a a2020g, works fine if you have a a2020u, current los kernel is missing a2020g fingerprint firmware from what i can gather.
Bliss 12.7 Android 10 gsi on a2020u.
rafyvitto said:
Follow these easy steps
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
==
Click to expand...
Click to collapse
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Mr. DR. Professor Electro said:
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Click to expand...
Click to collapse
Skip that step not needed, just flahs the disable encryption zip file in twrp to disable encryption.
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
honestly i cant even flash any rom zip i have i just get error 1s , i even wipe data/format before flashing am i doing something wrong am i supposed to be on a or b while doing this or what
Futility's Forgotten Soldier said:
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
Click to expand...
Click to collapse
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
cant escape bootloop hell and error 255
rafyvitto said:
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Click to expand...
Click to collapse
rafyvitto said:
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
Click to expand...
Click to collapse
having trouble
Steps I followed:
(bootloader been unlocked but double checked to be sure)
Started from LineageOS 16 clean flashed based
booted rom made sure Debug was enable in settings did nothing else
booted to bootloader
>fastboot set_active a
>fastboot boot "D:\Android\Flash\Recovery.img"
In Recovery:
Installed Twrp zip
install zip DisableForcedEncryption.zip
-reboot bootloader
>fastboot flash vbmeta "C:\Users\chris\Downloads\ZTE_Flash\vbmeta.img"
>fastboot format userdata
boot to recovery:
Installed GSI Image of Havoc OS to System image
Flashing system image......
simg2ing '/sdcard1/Havoc-OS-v2.9-20190914-phhgsi_arm64_ab-offical.img' 'dev/block/bootdevice/by-name/system_a'process
ended with ERROR: 255
got creative because nothing i was doing was fixing the problem so i went into fast boot and
>fastboot flash system "location/of/Havoc.img"
now no longer can acess the recovery not even but fastboot boot img command and back in a bootloop hell
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "D:\Android\Flash\Recovery.img"
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.640s
also i have no way to return to the original 10 pro rom whenever i flash it via the EDL tool with one of the US edl
Zips you provided i have boot loop but it gives me enough so i can have bootloader mode accessible but i have to rerun
the bootloader unlock. but flashing Lineage 16 seems to be the only thing to make my phone functional without giving it boot loop hell
ill try do it with bliss later but if there's anywhere i went wrong or how to solve the 255 let me know i really want to try out one of those GSIs
but im running on the US rom and using the TWRP for my pro from the fourms so i just really confused here idk if i could possibly give you anymore details
ok update i got it working
1. the 255 i fixed by
"
Reboot into recovery, TWRP
Go to the terminal in "Advanced"
Type cd /system to change the path to the system folder
Type rm addon.d to remove the addon file
Type exit to quit from the terminal
Now back to TWRP home, try backup/restore again, it should works.
Further adjustment: do check the use rm -f to format disk settings of TWRP, to make sure TWRP won't mess up the filesystem."
secondly what was ruining me was a big dumb mistake on my part you HAVE to do " --disable-verity --disable-verification flash vbmeta vbmeta.img" with the latest ADB tool kit I was using minimal adb and fastboot then got it to work
In step 5,i can not boot into TWRP and phone displays ZTE crashdump mode.
Please help.
Thanks.
Edit: I fixed it and can flashed this rom but it has some bugs.