Database Users

[Q] Question about downgrading from Lollipop to Kitkat

I am just not sure how an entire phone can be bricked just by trying to flash a 32 bit Kitkat over a phone with clean storage. Notice my stress on the word clean. By clean I meant a phone with /boot and /system partitions entirely wiped off. By wiping off /boot, I am essentially clearing off the kernel and ramdisk.
To explain what I am trying to say, I'll give an example:
Lets assume the phone has lollipop installed. Lets also assume that the phone has 64 bit TWRP installed as recovery. Now in the recovery mode, if I wipe off /boot and /system, I am essentially getting rid of the entire operating system, kernel and the ramdisk. Now if I switch to fastboot mode from inside TWRP and re-flash stock KitKat, my /boot and /system will be recreated. And I don't see any reason, why the phone will not be able to boot into Kitkat from there.
What do you say guys? Did I assume something wrong here? I need your opinion.

Go to this thread you will find answer there http://forum.xda-developers.com/yureka/general/cyanogen-12-lollipop-to-cyanogen-11-t3096587

If you clean flash on your phone, what about your firmware? Have you wiped it as well?

Wow, finally there is a person who ask the question
sanj_cm_fan said:
I am just not sure how an entire phone can be bricked just by trying to flash a 32 bit Kitkat over a phone with clean storage. Notice my stress on the word clean. By clean I meant a phone with /boot and /system partitions entirely wiped off. By wiping off /boot, I am essentially clearing off the kernel and ramdisk.
Click to expand...
Click to collapse
Wow at last, a person with good question. Well first I don't know what have change with the x64 edition of stock lollipop (currently downloading the fastboot rom and then will do some hex comparison between all the image listed in the zip), cos just for your info, changing boot.img and system.img will not put your phone unrecognizable by windows (see all post in my thread HERE). The worse case, it will put your phone directly to QDLoader (9008) mode.
If you ask why, here is the simple answer, qualcomm's phone first will boot the "Secondary Boot Loader" a.k.a sbl1.mbn (sbl1 partition), then your phone "eMMC Boot Loader" a.k.a emmc_appsboot.mbn a.k.a the fastboot mode (aboot partition), then your phone "Resource and Power Management" a.k.a rpm.mbn (rpm partition), then the Trust Zone a.k.a tz.mbn (tz partition), then the HYP (now I don't really no what this is, but through hex reading on hyp.mbn, it includes some new protocol like SBL, but shorter), see below diagrams:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, by just flashing wrong boot.img and system.img, will not make your phone unrecognisable by windows, unless somehow you manage to complete formatted your whole eMMC.
I just wonder, how did actually those people really make their phone unrecognizable by windows. The safest thing to do when you downgrading or upgrading your phone via fastboot is first by formatting and erasing all of the old files respective to their partitions, and then flashing the new images, such as below:
Code:
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf erase modem
fastboot -i 0x1ebf erase boot
fastboot -i 0x1ebf erase recovery
fastboot -i 0x1ebf erase aboot
fastboot -i 0x1ebf erase abootbak
fastboot -i 0x1ebf erase hyp
fastboot -i 0x1ebf erase hypbak
fastboot -i 0x1ebf erase rpm
fastboot -i 0x1ebf erase rpmbak
fastboot -i 0x1ebf erase sbl1
fastboot -i 0x1ebf erase sbl1bak
fastboot -i 0x1ebf erase tz
fastboot -i 0x1ebf erase tzbak
fastboot -i 0x1ebf format system
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf flash modem NON-HLOS.bin
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash sbl1bak sbl1.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash abootbak emmc_appsboot.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash rpmbak rpm.mbn
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash tzbak tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash hypbak hyp.mbn
fastboot -i 0x1ebf flash boot boot.img
fastboot -i 0x1ebf flash recovery recovery.img
fastboot -i 0x1ebf flash system system.img
fastboot -i 0x1ebf reboot-bootloader
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
Just do this code, and you will safely downgrade your phone to kitkat.

tirta.agung said:
Wow at last, a person with good question. Well first I don't know what have change with the x64 edition of stock lollipop (currently downloading the fastboot rom and then will do some hex comparison between all the image listed in the zip), cos just for your info, changing boot.img and system.img will not put your phone unrecognizable by windows (see all post in my thread HERE). The worse case, it will put your phone directly to QDLoader (9008) mode.
If you ask why, here is the simple answer, qualcomm's phone first will boot the "Secondary Boot Loader" a.k.a sbl1.mbn (sbl1 partition), then your phone "eMMC Boot Loader" a.k.a emmc_appsboot.mbn a.k.a the fastboot mode (aboot partition), then your phone "Resource and Power Management" a.k.a rpm.mbn (rpm partition), then the Trust Zone a.k.a tz.mbn (tz partition), then the HYP (now I don't really no what this is, but through hex reading on hyp.mbn, it includes some new protocol like SBL, but shorter), see below diagrams:
So, by just flashing wrong boot.img and system.img, will not make your phone unrecognisable by windows, unless somehow you manage to complete formatted your whole eMMC.
I just wonder, how did actually those people really make their phone unrecognizable by windows. The safest thing to do when you downgrading or upgrading your phone via fastboot is first by formatting and erasing all of the old files respective to their partitions, and then flashing the new images, such as below:
Code:
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf erase modem
fastboot -i 0x1ebf erase boot
fastboot -i 0x1ebf erase recovery
fastboot -i 0x1ebf erase aboot
fastboot -i 0x1ebf erase abootbak
fastboot -i 0x1ebf erase hyp
fastboot -i 0x1ebf erase hypbak
fastboot -i 0x1ebf erase rpm
fastboot -i 0x1ebf erase rpmbak
fastboot -i 0x1ebf erase sbl1
fastboot -i 0x1ebf erase sbl1bak
fastboot -i 0x1ebf erase tz
fastboot -i 0x1ebf erase tzbak
fastboot -i 0x1ebf format system
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf flash modem NON-HLOS.bin
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash sbl1bak sbl1.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash abootbak emmc_appsboot.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash rpmbak rpm.mbn
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash tzbak tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash hypbak hyp.mbn
fastboot -i 0x1ebf flash boot boot.img
fastboot -i 0x1ebf flash recovery recovery.img
fastboot -i 0x1ebf flash system system.img
fastboot -i 0x1ebf reboot-bootloader
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
Just do this code, and you will safely downgrade your phone to kitkat.
Click to expand...
Click to collapse
Thanks a lot Tirta. Finally someone answered my query in such vivid details. So what it boils down to is to delete the firmware specific stuff: secondary boot loader, eMMC boot loader, resource and power management, trust zone and hyp (whatever that is). Then flash the old firmware (sbl1, aboot, rpm, tz, hyp and offcourse the modem) that came with cm11 fastboot package. This is just awesome. Can you tell me something? I don't see any sbl1, aboot, rpm, tz, hyp and modem partitions in the phone. This is what my phone's partition table looks like:
Code:
Filesystem Size Used Free Blksize
/dev 930.0M 56.0K 930.0M 4096
/sys/fs/cgroup 930.0M 12.0K 930.0M 4096
/mnt/asec 930.0M 0.0K 930.0M 4096
/mnt/obb 930.0M 0.0K 930.0M 4096
/system 1.1G 1.1G 76.6M 4096
/data 12.8G 3.0G 9.8G 4096
/cache 122.0M 100.0K 121.9M 4096
/persist 5.8M 96.0K 5.7M 4096
/firmware 64.0M 45.1M 18.9M 16384
/mnt/shell/emulated 12.8G 3.0G 9.8G 4096
/storage/emulated 930.0M 0.0K 930.0M 4096
/mnt/media_rw/sdcard1 29.5G 23.1G 6.4G 32768
/mnt/secure/asec 29.5G 23.1G 6.4G 32768
/storage/sdcard1 29.5G 23.1G 6.4G 32768
/storage/emulated/0 12.8G 3.0G 9.8G 4096
/storage/emulated/0/Android/obb 12.8G 3.0G 9.8G 4096
/storage/emulated/legacy 12.8G 3.0G 9.8G 4096
/storage/emulated/legacy/Android/obb 12.8G 3.0G 9.8G 4096
In the firmware partition (in /firmware/image directory), I do see files that may be related with sbl1, aboot, tz, rpm, hyp and modem.
So the partition names which are mentioned while flashing through fastboot, are more logical than physical? Or is it that you need to use some other executable to find out the entire partition table in Android?
Can I assume that on flashing cm11 fastboot package directly on top of the cm12s installation, it will screw sbl1 and aboot partitions and hence the brick?
Thanks,
Sanjay

sanj_cm_fan said:
Can you tell me something? I don't see any sbl1, aboot, rpm, tz, hyp and modem partitions in the phone.
Click to expand...
Click to collapse
Use this command to see those partitions:
Code:
adb shell
ls -al /dev/block/bootdevice/by-name/
sanj_cm_fan said:
Can I assume that on flashing cm11 fastboot package directly on top of the cm12s installation, it will screw sbl1 and aboot partitions and hence the brick?
Click to expand...
Click to collapse
You need first to empty those partitions, either by erasing the content of the partitions (sbl1, tz,rpm, and hyp) or formatting the partitions (cache, userdata, and system). I used to have "Nexus 4", and experience problem downgrading because the flash.bat does not erase or format previous partitions.

tirta.agung said:
I just wonder, how did actually those people really make their phone unrecognizable by windows.
Click to expand...
Click to collapse
@tirta.agung, having done just that to my Dad's YU Yureka last weekend, I can tell you it actually is fairly easy - how I wish it wasn't :crying:
All I did was to flash official CM11 rom using official an older copy of linux flash tools I had with me (they have removed the linux flashtools from YUPlayGod on github now, and I didn't bother to check any changes made to Windows tools - I now wish I had), powered-off the phone, never to see it wake it's beautiful screen again
I think one of the reasons (besides not erasing/formatting existing partitions) so many hard-bricked YU Yurekas (esp while downgrading to CM11) find a mention in these forums could be that "official" flash-all.bat at YUPlayGod github didn't flash 'hyp' partition till it was update on 21st Apr (please search for "commit 80dcc59d76 YUPlayGod" - I'm not allowed to post URLs yet). Missing an (apparently) critical partition while downgrading might make the kernel panic during boot-up.
Whether that has any direct bearing on the device being unrecognizable in Windows is something I wouldn't know yet - but surely my device is not getting recognized at all. No logs in "Device Remover" for Windows while connecting the device, no logs in 'dmesg' for Linux either. Only the red LED is lit (no continuous vibration as you've mentioned for a tell-tale sign of a device in QLoader 9008 Mode)
I also saw elsewhere you've recommended shorting some pins in the battery enclosure on handset to get Windows to detect the phone - if you can explain why you believe shorting them will help and then I'd attempt that as well.
Also, what's you opinion on the "theory" which says "partition sizes have been modified across CM11 and CM12"; ergo hence "the zip method" to downgrade is safer then flashboot because
Abhiram Shibu said:
When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone.
Click to expand...
Click to collapse
IMHO, if partition have really been re-sized, then there's not much you can achieve with either method (using 'zip' and 'flashboot' both shall be equally useless) unless there's some re-partitioning step/tool employed beforehand (quite like PIT files for Samsung devices). What is your opinion on this?

Need help..
I wiped all the 29 partitions that are present on Yu Yureka and now when I flash new ROM WiFi on my phone doesn't work also IMEI are wiped but I am.able to fix the IMEIs but not the WiFi and Hotspot issue. By 29 partitions I meant partitions including - sec, fsg, modemst1 modems2, ssd, panic, param etc . Guys help how can I fix my phone ?

recovering zuk z1

so I accidentally wipe everything including internal storage from TWRP. now everytime my device boot up it directly goes to the TWRP recovery. how can i flash rom again? :v

nelson_k said:
so I accidentally wipe everything including internal storage from TWRP. now everytime my device boot up it directly goes to the TWRP recovery. how can i flash rom again? :v
Click to expand...
Click to collapse
You connect to PC, mount sdcard with twrp and copy a rom from pc to your sdcard. Then install the rom within twrp.

strongst said:
You connect to PC, mount sdcard with twrp and copy a rom from pc to your sdcard. Then install the rom within twrp.
Click to expand...
Click to collapse
Helloo. I don't have sdcard neither otg. is there any other option? I've tried using adb sideload but still only boot to TWRP.

Go to twrp> Reboot> Bootloader
You'll then reboot into the fastboot mode.
Connect your USB-C Type cable and make sure that the device is connected.
Make sure that you have the stock COS 12.1 ROM in your adb folder and use these commands-
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c flash persist persist.img
fastboot -i 0x2b4c flash system system.img -S 1G
fastboot -i 0x2b4c reboot

Take a otg and copy ROM and select file from twrp

moriyaprateek said:
Go to twrp> Reboot> Bootloader
You'll then reboot into the fastboot mode.
Connect your USB-C Type cable and make sure that the device is connected.
Make sure that you have the stock COS 12.1 ROM in your adb folder and use these commands-
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c flash persist persist.img
fastboot -i 0x2b4c flash system system.img -S 1G
fastboot -i 0x2b4c reboot
Click to expand...
Click to collapse
Can someone please share system.img from the stock ROM for Zuk Z1? Thanks,

fastboot mode started

when i fix fastboot mode started with command:
fastboot flash aboot aboot.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase dbi
fastboot flash dbi dbi.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase rpm
fastboot flash rpm rpm.img
fastboot erase sbl1
fastboot flash sbl1 sbl1.img
fastboot erase tz
fastboot flash tz tz.img
fastboot reboot
i get "flash write failure"or failed to erase partition
why
can samone help me pls

[Kinda Solved] Flashing is not allowed for Critical Partitions. But I've unlocked.

It seems that
Code:
fastboot flashing unlock
and
Code:
fastboot flashing unlock_critical
are the same command.
I've tried wiping all data, using MsmDownloadTool and re-doing every steps, but there's only two options: Unlock or Lock Bootloader.
I want flash some images into some critical partitions, it always says Flashing is not allowed for Critical Partitions. Has anyone succeed unlocking the Critical Partitions on OnePlus 6T?

vungsung said:
It seems that
Code:
fastboot flashing unlock
and
Code:
fastboot flashing unlock_critical
are the same command.
I've tried wiping all data, using MsmDownloadTool and re-doing every steps, but there's only two options: Unlock or Lock Bootloader.
I want flash some images into some critical partitions, it always says Flashing is not allowed for Critical Partitions. Has anyone succeed unlocking the Critical Partitions on OnePlus 6T?
Click to expand...
Click to collapse
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.

tech_head said:
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
Click to expand...
Click to collapse
Is there any up-to-dated NetHunter kernal for Oneplus6T?

vungsung said:
I'm trying to flash NetHunter kernel: https://forum.xda-developers.com/oneplus-6t/development/oneplus6-6t-nethunter-kernel-t3900105, which lead me to a github page: https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel. I followed the tutorial in the github page. They say you have to flash patched imgaes list in https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel/blob/master/flash.bat. I run flash.bat, and saw the errors.
Click to expand...
Click to collapse
When I flash ElementalX the boot image is patched via the install.
On this phone, if you have a patched boot image it's not a critical partition.
fastboot flash boot_a/b boot.img (the boot_a/b is for which partition you are flashing).

tech_head said:
When I flash ElementalX the boot image is patched via the install.
On this phone, if you have a patched boot image it's not a critical partition.
fastboot flash boot_a/b boot.img (the boot_a/b is for which partition you are flashing).
Click to expand...
Click to collapse
I don't get it. I do have to flash boot.img, which is not critical, AND below, that some of them are critical.
Code:
fastboot erase boot_a
fastboot erase boot_b
fastboot erase system_a
fastboot erase system_b
fastboot erase radio
fastboot erase radio_a
fastboot erase radio_b
fastboot erase recovery
fastboot erase recovery_a
fastboot erase recovery_b
fastboot erase userdata
fastboot erase userdata_a
fastboot erase userdata_b
fastboot flash abl_a abl.img
fastboot flash aop_a aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash boot_a boot.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash devcfg_a devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash hyp_a hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash modem_a modem.img
fastboot flash oem_stanvbk_a oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash tz_a tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_a xbl.img
fastboot flash abl_b abl.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_b boot.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk_b oem_stanvbk.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_b system.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash xbl_b xbl.img
Or it won't boot...

vungsung said:
I don't get it. I do have to flash boot.img, which is not critical, AND below, that some of them are critical.
Code:
fastboot erase boot_a
fastboot erase boot_b
fastboot erase system_a
fastboot erase system_b
fastboot erase radio
fastboot erase radio_a
fastboot erase radio_b
fastboot erase recovery
fastboot erase recovery_a
fastboot erase recovery_b
fastboot erase userdata
fastboot erase userdata_a
fastboot erase userdata_b
fastboot flash abl_a abl.img
fastboot flash aop_a aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash boot_a boot.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash devcfg_a devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash hyp_a hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash modem_a modem.img
fastboot flash oem_stanvbk_a oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash tz_a tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_a xbl.img
fastboot flash abl_b abl.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_b boot.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk_b oem_stanvbk.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_b system.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash xbl_b xbl.img
Or it won't boot...
Click to expand...
Click to collapse
That is a complete wipe and install.
If you are only installing a kernel and NOT a ROM then that is not correct.

tech_head said:
That is a complete wipe and install.
If you are only installing a kernel and NOT a ROM then that is not correct.
Click to expand...
Click to collapse
I know the correct steps to install kernels or ROMS. The problem is I tried to install OOS official ROM, and install the Nethunter kernel, the kernel won't work at all. So I have to install the patched ROM by flash the patched images inside the ROM one-by-one and then install kernel.

vungsung said:
I know the correct steps to install kernels or ROMS. The problem is I tried to install OOS official ROM, and install the Nethunter kernel, the kernel won't work at all. So I have to install the patched ROM by flash the patched images inside the ROM one-by-one and then install kernel.
Click to expand...
Click to collapse
You indicated you were trying to flash a kernel which is why I said that. Had you said you were trying to flash a complete ROM then I would have said something else.

tech_head said:
You indicated you were trying to flash a kernel which is why I said that. Had you said you were trying to flash a complete ROM then I would have said something else.
Click to expand...
Click to collapse
Sorry, I didn't mean to make you misunderstood. For those find this thread with the same problem, I'd say trying to flash OOS by normal way. Thanks for your help, tech_head!

i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....

sadatkabir55 said:
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
Click to expand...
Click to collapse
Wrong thread there Glenda. This is the 6T forum.

I got same problem how to fix this???????

vungsung said:
I'm trying to flash NetHunter kernel: https://forum.xda-developers.com/oneplus-6t/development/oneplus6-6t-nethunter-kernel-t3900105, which lead me to a github page: https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel. I followed the tutorial in the github page. They say you have to flash patched imgaes list in https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel/blob/master/flash.bat. I run flash.bat, and saw the errors.
Click to expand...
Click to collapse
That's a pretty old version of that kernel. Here's the up to date version, and you can flash it from recovery without any issues
http://www.mediafire.com/file/fue9i4pzbcp4x6w/NHKernel.zip/file

Jfoster1234 said:
That's a pretty old version of that kernel. Here's the up to date version, and you can flash it from recovery without any issues
http://www.mediafire.com/file/fue9i4pzbcp4x6w/NHKernel.zip/file
Click to expand...
Click to collapse
Alright, thank you for the resource!

have you fixed already bro?
sadatkabir55 said:
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
Click to expand...
Click to collapse
have you fixed?

sadatkabir55 said:
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
Click to expand...
Click to collapse
gazitonmoy said:
have you fixed?
Click to expand...
Click to collapse
[CLOSED] Same here, no Idea what to do? Phone bricked and dead. PLEASE HELP US, GUYS
--
EDIT: *lol - I did a "oem lock" and a "oem unlock" again... and suddenly my device behaves as expected again, without needing to "flash-all.bat". Perhaps sometimes I will understand this stuff... :/

tech_head said:
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
Click to expand...
Click to collapse
What does "dd" stand for?

Did you solve this? I have the same issue. Oneplus 8 Pro, got it and installed LineageOS right away which worked, but just wasn't useable, lots of gps stuff not working. So, I wanted to restore the factory ROM. I followed this:
How to Create Fastboot-flashable Factory Image for Any OnePlus Phone
Learn how to create a factory image for any OnePlus phone and flash it using Fastboot. Useful for restoring stock OxygenOS software and unbricking.
www.thecustomdroid.com
Ran through everything fine as far as I could tell the first time, but it wouldn't boot, just kept going back to fastboot.
So, I tried to re-do the steps but upon trying to go through them again, as soon as I get to about the 5th command where I reboot before continuing to flash, it reboots with a Qualcom crash screen. I can still power off and get to fastboot, but if I try to continue the flash steps i get this same error on any of them.
PLEASE HELP! I just got this phone and paid a ton I am going to loose it if I bricked it already.
UPDATE: Forget this. I didn't solve it, but I did manage to at least restore A rom.

tech_head said:
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
Click to expand...
Click to collapse
may i know how? i want to flash persist.im for oneplus6t

"(command write failed (Invalid argument))" error while flashing system.img

Hello experts, i'm diving directly into main problem. My phone directly powered off when i using phone. when i try to open, stuck on android one logo.
i tried to flash new rom via MiFlash. But its giving strange errors.
Also i tried to format data via twrp, but it stucks after i swipe. i tried also wipe system,dalvik, cache, but same thing happened. stucking after i swipe.
I think phone bricked.
Today i tried to flash all img files via fastboot like this;
Code:
fastboot erase boot_a
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash sec sec.dat
fastboot flash splash splash.img
fastboot flash misc misc.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system_other.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot flash userdata userdata.img
fastboot set_active a
fastboot reboot
I moved my tissot images to adb folder and started.
But after i tried whole codes in powershell with copy paste, giving "(command write failed (Invalid argument))" error in 2nd img file. Thats really interesting. first img file transfered succesfully but 2nd one is giving error.
And i decided to flash step by step, aand BUM. i dont getting any error while flashing step by step. But if i try to flash for example 2 img file, its giving error.
I moved forward like this until system.img file give me error again.
Code:
fastboot flash system_a system.img
target reported max download size of 534773760 bytes
erasing 'system_a'...
OKAY [ 0.096s]
sending sparse 'system_a' 1/5 (522236 KB)...
OKAY [ 11.986s]
writing 'system_a' 1/5...
OKAY [ 3.926s]
sending sparse 'system_a' 2/5 (521866 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 16.308s
I flashed all img files except system.img and system_other.img. only this 2 files giving error.
And i realized that 2 file sizes are big and fastboot trying to parse files while flashing. 1st parsed file transfering succesfully but after it goes to 2nd parsed file its giving "(command write failed (Invalid argument))" error. My fastboot has some strange problem about 2nd flash code lines. I dont know why.
What can i do to flash this 2 system img file via fastboot?

my problem solved after i break apart my phone. no need help now.