Can't install TWRP - LG V30 Questions & Answers

I unlocked bootloader long ago, however, it was with an older method I believe. The device appears to be unlocked (see below), but attempting to flash anything just freezes into eternity:
Any thoughts?
Code:
C:\platform-tools>adb devices
List of devices attached
LGUS9980af4c546 device
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot getvar all
(bootloader) eio_count:0
(bootloader) dm_count:0
(bootloader) lock_count:0
(bootloader) unlock_count:1
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4308
(bootloader) version-baseband:┼φ≈Qa⌡6C`⌡ⁿƒ
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x81800000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC92474000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x19F400000
(bootloader) secure:yes
(bootloader) serialno:LGUS9980af4c546
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.047s
C:\platform-tools>fastboot flash recovery TWRP.img
Sending 'recovery' (30860 KB)

betam4x said:
I unlocked bootloader long ago, however, it was with an older method I believe. The device appears to be unlocked (see below), but attempting to flash anything just freezes into eternity:
Any thoughts?
Code:
C:\platform-tools>adb devices
List of devices attached
LGUS9980af4c546 device
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot getvar all
(bootloader) eio_count:0
(bootloader) dm_count:0
(bootloader) lock_count:0
(bootloader) unlock_count:1
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4308
(bootloader) version-baseband:┼φ≈Qa⌡6C`⌡ⁿƒ
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x81800000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC92474000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x19F400000
(bootloader) secure:yes
(bootloader) serialno:LGUS9980af4c546
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.047s
C:\platform-tools>fastboot flash recovery TWRP.img
Sending 'recovery' (30860 KB)
Click to expand...
Click to collapse
Download both TWRP.zip on phone and TWRP.img to adb folder of PC. U then have to "fastboot boot TWRP.img" and once temp TWRP boots up, then use TWRP to install TWRP. ZIP as v30 does NOT have recovery partition.

HueyT said:
Download both TWRP.zip on phone and TWRP.img to adb folder of PC. U then have to "fastboot boot TWRP.img" and once temp TWRP boots up, then use TWRP to install TWRP. ZIP as v30 does NOT have recovery partition.
Click to expand...
Click to collapse
No luck so far, it just freezes on sending. Does the same thing if i try to re-unlock it as well.

betam4x said:
No luck so far, it just freezes on sending. Does the same thing if i try to re-unlock it as well.
Click to expand...
Click to collapse
Try another fresh laptop, cable, USB port, LG, Qualcomm drivers, latest minimal adb and fastboot

HueyT said:
Try another fresh laptop, cable, USB port, LG, Qualcomm drivers, latest minimal adb and fastboot
Click to expand...
Click to collapse
tried 3 different cables, multiple versions of the ports (1.1, 3.0, 3.1) and no dice on my main desktop, going to try another desktop in just a moment. Thanks!

It was my desktop. again. Managed to get TWRP on there, now just trying to get LineageOS to boot (right now it's showing the startup screen. Hoping it just takes a while on first boot). Thanks for your help! I should know better by now.

Related

Borked Razer 1 badly, device does not accept slot settings, need to reformat fstab...

Long story short, I softbricked a Razer 1 by using Razer's own flash_all batch/shell script. At this point I can't determine exactly when the "oh ****" happened, but I've tried a lot of things and have been asking in the Newbie sticky post as well. Basically, I have the OEM factory defaults archive which supposedly will at least get a recovery partition and image back so I can move forward, but I only have fastboot/Download Mode. I can issue nearly any command I've tried to it, but the biggest issue right now is that it won't recognize or respond or accept any slot changes and a "fastboot getvar slot" returns an empty field. When I try setting the slot to a or b, or when I just do --set-active=other, I get an error that this device does not support slots. Obviously that's bad because this device does indeed us slot partitioning and has no true recovery partition.
What should I try? I have mkbootimg, abootimg, a Windows or Linux box with each able to manipulate Android devices and I even have Android Studio setup on my Windows PC. Magisk looks promising since I understand the concepts of tar and cpio as a linux admin, but obviously that's meaningless until I can boot into some kind of recovery. The device does still know its serial number, so I'm assuming the firmware flashed manufacturer stuff and hopefully any kind of PGP or cert or key is all still intact and untouched.
EDIT UPDATE:
< waiting for any device >
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4127
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC72DD7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xE0000000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:181812V00402779
(bootloader) product:cheryl
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
all:
Finished. Total time: 0.032s
That is now my current getvar output, and it looks fine, but now I cannot set_active to _b and after the reboot, it seems to revert back to slot a automatically, like it is trying to enter recovery, but cannot.
Replying to bump and update:
Several attempts at running flash_all.bat from Razer, I can get as far as the first reboot in the script before it hangs and no longer takes input. I think that's because the stupid script isn't properly setting the active slot and it tries to flash partitions on the active slot (slot a in this case). So I am now going to manually run each command, but alternate active slots each time and see. This is new output of "getvar all"
< waiting for any device >
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4127
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC72DD7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xE0000000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:181812V00402779
(bootloader) product:cheryl
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
all:
Finished. Total time: 0.032s

Can't install TWRP

I unlocked bootloader long ago, however, it was with an older method I believe. The device appears to be unlocked (see below), but attempting to flash anything just freezes into eternity:
Any thoughts?
Code:
C:\platform-tools>adb devices
List of devices attached
LGUS998xxxxxxx device
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot getvar all
(bootloader) eio_count:0
(bootloader) dm_count:0
(bootloader) lock_count:0
(bootloader) unlock_count:1
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4308
(bootloader) version-baseband:┼φ≈Qa⌡6C`⌡ⁿƒ
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x81800000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC92474000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x19F400000
(bootloader) secure:yes
(bootloader) serialno:LGUS9980xxxxxxx
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.047s
C:\platform-tools>fastboot flash recovery TWRP.img
Sending 'recovery' (30860 KB)

fastboot not responding

Hello to everyone, i have a lot of problems with my mi a3 but lets take it from what is the most important now....i was on stock rom and i try to install twrp so when i flash the zip for some reason after the zip flashing i reboot in to twrp but the phone instead twrp went to fastboot and stuck there. Then i tried to flash the twrp via fastboot and i boot to slot b erase the boot again to slot a erase boot and after i flash the twrp.img and then reboot but nothing happens, i was again after android logo , in fastboot. Now i try to do the same and i have that results...
I'm presuming you were on the android 10 update? Twrp cannot be flashed with the android 10 update yet
garylawwd said:
I'm presuming you were on the android 10 update? Twrp cannot be flashed with the android 10 update yet
Click to expand...
Click to collapse
No i was on android 9 , you have something to suggest?
What's the output of these commands?
fastboot --version
fastboot getvar all
adb
(just first two lines with version info)
_mysiak_ said:
What's the output of these commands?
fastboot --version
fastboot getvar all
adb
(just first two lines with version info)
Click to expand...
Click to collapse
[email protected]:~/Desktop/platform-tools$ fastboot --version
fastboot version 1:8.1.0+r23-5~18.04
[email protected]:~/Desktop/platform-tools$ fastboot getvar all
getvar:all FAILED (remote: unknown command)
[email protected]:~/Desktop/platform-tools$ adb
Android Debug Bridge version 1.0.39
Version 1:8.1.0+r23-5~18.04
kirki f said:
[email protected]:~/Desktop/platform-tools$ fastboot --version
fastboot version 1:8.1.0+r23-5~18.04
[email protected]:~/Desktop/platform-tools$ fastboot getvar all
getvar:all FAILED (remote: unknown command)
[email protected]:~/Desktop/platform-tools$ adb
Android Debug Bridge version 1.0.39
Version 1:8.1.0+r23-5~18.04
Click to expand...
Click to collapse
1. try to update fastboot/adb to the latest version https://developer.android.com/studio/releases/platform-tools
2. why do you reboot via fastboot if you're already in fastboot mode? (fastboot reboot bootloader is just unnecessary)
3. what's the output of "fastboot devices"?
_mysiak_ said:
1. try to update fastboot/adb to the latest version https://developer.android.com/studio/releases/platform-tools
2. why do you reboot via fastboot if you're already in fastboot mode? (fastboot reboot bootloader is just unnecessary)
3. what's the output of "fastboot devices"?
Click to expand...
Click to collapse
ok i try to update fastboot . i reboot via fastboot to check if i have a respond because is not always respond .
give me some time for the output because i try to update platform tools, before it wasn't respond.
​
_mysiak_ said:
1. try to update fastboot/adb to the latest version https://developer.android.com/studio/releases/platform-tools
2. why do you reboot via fastboot if you're already in fastboot mode? (fastboot reboot bootloader is just unnecessary)
3. what's the output of "fastboot devices"?
Click to expand...
Click to collapse
thats the output from fastboot devices
kirki f said:
​
thats the output from fastboot devices
Click to expand...
Click to collapse
"Fastboot getvar all" still doesn't work, even with updated fastboot binary?
kirki f said:
​
thats the output from fastboot devices
Click to expand...
Click to collapse
i install the latest version of fastboot but i have the same problems, you have to saggest something?
_mysiak_ said:
"Fastboot getvar all" still doesn't work, even with updated fastboot binary?
Click to expand...
Click to collapse
[email protected]:~/Desktop/platform-tools$ Fastboot getvar all
Command 'Fastboot' not found, did you mean:
command 'fastboot' from deb fastboot
Try: sudo apt install <deb name>
thats wat i take buck..
kirki f said:
[email protected]:~/Desktop/platform-tools$ Fastboot getvar all
Command 'Fastboot' not found, did you mean:
command 'fastboot' from deb fastboot
Try: sudo apt install <deb name>
thats wat i take buck..
Click to expand...
Click to collapse
Mac/Linux is case sensitive..type fastboot in lower case.
[email protected]:~/Desktop/platform-tools$ fastboot getvar all
(bootloader) crc:1
(bootloader) DP:0x0
(bootloader) hw-revision:10000
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4378
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) anti:0
(bootloader) variant:SM_ UFS
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x79BF000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x200000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x200000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x200000
(bootloader) partition-type:ALIGN_TO_128K_2:raw
(bootloader) partition-size:ALIGN_TO_128K_2: 0x1A000
(bootloader) partition-type:gsort:raw
(bootloader) partition-size:gsort: 0x44EBC000
(bootloader) partition-type:catecontentfv:raw
(bootloader) partition-size:catecontentfv: 0x100000
(bootloader) partition-type:catefv:raw
(bootloader) partition-size:catefv: 0x80000
(bootloader) partition-type:secdata:raw
(bootloader) partition-size:secdata: 0x7000
(bootloader) partition-type:uefivarstore:raw
(bootloader) partition-size:uefivarstore: 0x80000
(bootloader) partition-type:multiimgqti:raw
(bootloader) partition-size:multiimgqti: 0x8000
(bootloader) partition-type:multiimgoem:raw
(bootloader) partition-size:multiimgoem: 0x8000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:bk03:raw
(bootloader) partition-size:bk03: 0x40000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:cateloader:raw
(bootloader) partition-size:cateloader: 0x200000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x20A4000
(bootloader) partition-type:spunvm:raw
(bootloader) partition-size:spunvm: 0x800000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:storsec_b:raw
(bootloader) partition-size:storsec_b: 0x20000
(bootloader) partition-type:uefisecapp_b:raw
(bootloader) partition-size:uefisecapp_b: 0x200000
(bootloader) partition-type:imagefv_b:raw
(bootloader) partition-size:imagefv_b: 0x200000
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-size:dtbo_b: 0x1800000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-size:vendor_b: 0x40000000
(bootloader) partition-type:qupfw_b:raw
(bootloader) partition-size:qupfw_b: 0x10000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x20000
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-size:cmnlib64_b: 0x80000
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-size:cmnlib_b: 0x80000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x4000000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x80000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x2000000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b: 0x100000
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-size:mdtp_b: 0x2000000
(bootloader) partition-type:mdtpsecapp_b:raw
(bootloader) partition-size:mdtpsecapp_b: 0x400000
(bootloader) partition-type:bluetooth_b:raw
(bootloader) partition-size:bluetooth_b: 0x100000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0xB400000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b: 0x80000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x400000
(bootloader) partition-type:rpm_b:raw
(bootloader) partition-size:rpm_b: 0x80000
(bootloader) partition-type:storsec_a:raw
(bootloader) partition-size:storsec_a: 0x20000
(bootloader) partition-type:uefisecapp_a:raw
(bootloader) partition-size:uefisecapp_a: 0x200000
(bootloader) partition-type:imagefv_a:raw
(bootloader) partition-size:imagefv_a: 0x200000
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-size:dtbo_a: 0x1800000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-size:vendor_a: 0x40000000
(bootloader) partition-type:qupfw_a:raw
(bootloader) partition-size:qupfw_a: 0x10000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x20000
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-size:cmnlib64_a: 0x80000
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-size:cmnlib_a: 0x80000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x4000000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x80000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x2000000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a: 0x100000
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-size:mdtp_a: 0x2000000
(bootloader) partition-type:mdtpsecapp_a:raw
(bootloader) partition-size:mdtpsecapp_a: 0x400000
(bootloader) partition-type:bluetooth_a:raw
(bootloader) partition-size:bluetooth_a: 0x100000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0xB400000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a: 0x80000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x400000
(bootloader) partition-type:rpm_a:raw
(bootloader) partition-size:rpm_a: 0x80000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x7F9F000
(bootloader) partition-type:cdt:raw
(bootloader) partition-size:cdt: 0x20000
(bootloader) partition-type:ALIGN_TO_128K_1:raw
(bootloader) partition-size:ALIGN_TO_128K_1: 0x1A000
(bootloader) partition-type:xbl_config_b:raw
(bootloader) partition-size:xbl_config_b: 0x459000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b: 0x380000
(bootloader) partition-type:xbl_config_a:raw
(bootloader) partition-size:xbl_config_a: 0x459000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a: 0x380000
(bootloader) partition-type:userdata:f2fs
(bootloader) partition-size:userdata: 0xC155D7000
(bootloader) partition-type:metadata:raw
(bootloader) partition-size:metadata: 0x1000000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xC0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xC0000000
(bootloader) partition-type:minidump:raw
(bootloader) partition-size:minidump: 0x8000000
(bootloader) partition-typeem:raw
(bootloader) partition-sizeem: 0x4000000
(bootloader) partition-typedm_b:raw
(bootloader) partition-sizedm_b: 0x8000000
(bootloader) partition-typedm_a:raw
(bootloader) partition-sizedm_a: 0x8000000
(bootloader) partition-typeroduct_b:raw
(bootloader) partition-sizeroduct_b: 0x10000000
(bootloader) partition-typeroduct_a:raw
(bootloader) partition-sizeroduct_a: 0x10000000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:7307b8a6c69b
(bootloader) product:laurel_sprout
(bootloader) max-download-size:804261888
(bootloader) kernel:uefi
all:
finished. total time: 0.027s
[email protected]:~/Desktop/platform-tools$
seems that it works! and now what?
Now you can do what you wanted with fastboot. [emoji846]
_mysiak_ said:
Now you can do what you wanted with fastboot. [emoji846]
Click to expand...
Click to collapse
sorry but i am in the same situation as before..
and also before that in the top right site of the screen "press any cay to shut down" or power off , i dont remember exactly , appears!
ok after a lot of fastboot getvar all i have this.....
[email protected]:~/Desktop/platform-tools$ fastboot getvar current-slot
current-slot: b
finished. total time: 0.002s
[email protected]:~/Desktop/platform-tools$ fastboot set_active a
Setting current slot to 'a'...
OKAY [ 0.035s]
finished. total time: 0.035s
[email protected]:~/Desktop/platform-tools$ fastboot erase boot
erasing 'boot_a'...
OKAY [ 0.023s]
finished. total time: 0.023s
[email protected]:~/Desktop/platform-tools$ fastboot flash boot twrp.img
target reported max download size of 804261888 bytes
sending 'boot_a' (39780 KB)...
OKAY [ 1.470s]
writing 'boot_a'...
OKAY [ 0.208s]
finished. total time: 1.678s
[email protected]:~/Desktop/platform-tools$ fastboot reboot
rebooting...
finished. total time: 0.050s
[email protected]:~/Desktop/platform-tools$
its looks good but it isn't because when i press volume up for rebooting the recovery i am again in the bootloader!!!!:crying:
Finally i brink my phone buck!!
i use the commands :
fastboot erase userdata
fastboot getvar all
fastboot erase boot
fastboot set_active b
fastboot erase boot
fastboot flash boot twrp.img
fastboot reboot
I dont now how it works but i have my phone buck , i used twrp to flash stock rom and i dident install it as zip (the twrp) .
Now that i am in the rom i try to flash twrp but it wasnt able but thats a problem for another day!!!:laugh:
Just wondering - why do you even want to install TWRP? I see no point in all the hassle. I'm sorry to say this, but you have no idea what you're doing (looking at the commands you used), so either follow one of the guides step by step, or study more so you understand which commands to use and when.

Rooting Black Shark 2 / 2 Pro the Correct & Easy Way with Video Guide, TWRP & OTA Fix

Rooting Black Shark 2 / 2 Pro the Correct & Easy Way with Video Guide, TWRP & OTA Fix
Happy Ramadan everyone! I wanted to do this tutorial for sometime, and now I finally made it.
This guide made for Black Shark 2 / 2 Pro Global version, but in theory it should work with any version if the bootloader is unlocked. (ANDROID 9 ONLY)
Warning: Before you start, backup your phone data as this would wipe your phone!
Do this at your own risk, I'm not responsible if you break your phone!
Prerequisites:
- Update your phone to the latest version possible.
- Download ADB & TWRP Installer from here.
- Download latest Magisk Manager from here.
You can find the video guide here, however please note that this video is not a complete tutorial you would need to follow the written guide.
On Phone:
1- Enable Developer Options. (Go to Settings, then System, then About Phone, then Tap on Build number 7 times, then enter your password if needed)
2- Enable OEM unlocking. (Go to Settings, then System, then Developer Options, then enable OEM unlocking option, then enter your password if needed)
3- Enable USB Debugging. (Go to Settings, then System, then Developer Options, then enable USB Debugging option)
On PC:
4- Run ADB+TWRP Installer. (On driver installation popup click Next, then Install and Finish)
5- Connect your Phone to PC using USB cable.
On Phone:
6- When Allow USB debugging popup, tap OK. (Tick Always allow from this computer)
On PC:
7- Make sure google drivers installed correctly and that your PC can see your Phone. (Android ADB Interface)
8- Open Command Prompt as administrator. (Type CMD in Windows search bar, then right click on Command Prompt ‘cmd’ and click on Run as administrator)
9- In CMD type:
Code:
cd c:\adb
Then press Enter key.
10- In CMD type:
Code:
adb devices
Then press Enter key. (If you can see a Device ID with ‘device’ written on its right, then continue to next step, if not then recheck your drivers. If you see a Device ID with ‘unauthorized’ written on its right, then go back to step 6)
11- In CMD type:
Code:
adb reboot bootloader
Then press Enter key. (To enter Fastboot mode)
On Phone:
12- Make sure you see Fastboot mode on your phone screen. (With big green START on top)
On PC:
13- Disconnect and reconnect your Phone to PC using USB cable then make sure google drivers installed correctly and that your PC can see your Phone. (Android Bootloader Interface)
14- In CMD type:
Code:
fastboot devices
Then press Enter key. (If you can see a Device ID, then continue to next step, if not then recheck your driver setup)
15- In CMD type:
Code:
fastboot oem bs_unlock
Then press Enter key. (This will unlock the bootloader, if you see an error make sure that your model is supporter)
16- In CMD type:
Code:
fastboot getvar current-slot
Then press Enter key. (This will show you which slot you’re currently using, noted it down)
17- In CMD type:
Code:
fastboot boot twrp.img
Then press Enter key. (This will boot TWRP, if it doesn’t work the first time, then force reboot your phone and repeat steps 11-17, you can skip step 15-16 if you already performed them)
On Phone:
18- Make sure TWRP is booted on your phone.
On PC:
19- In CMD type:
Code:
adb pull /dev/block/bootdevice/by-name/boot_a stock_boot_a.img
Then press Enter key. (This will copy the stock boot_a.img to your current directory)
20- In CMD type:
Code:
adb pull /dev/block/bootdevice/by-name/boot_b stock_boot_b.img
Then press Enter key. (This will copy the stock boot_b.img to your current directory)
On Phone:
21- In TWRP, go to Reboot, then system.
22- Download and install Magisk Manager APK. (Once the phone booted correctly)
On PC:
23- In CMD type:
Code:
adb push stock_boot_X.img /sdcard/Download
Then press Enter key. Change ‘X’ to your current slot from step 16, mine was ‘stock_boot_a.img’. (This will copy your stock boot.img to your phone’s Downloads directory)
On Phone:
24- Run Magisk Manager, tap on the first INSTALL button on the top right, when it asks you to Install Magisk tap INSTALL, then tap on Select and Patch a File, and choose your stock_boot_X.img from ‘Download’ directory. When it’s done it will create a new file in your ‘Download’ directory named magisk_patch.img. (Don’t tap Reboot, just tap back and close the App)
On PC:
25- In CMD type:
Code:
adb pull /sdcard/Download/magisk_patched.img
Then press Enter key. (This will copy the patched boot.img to your current ‘adb’ directory)
26- In CMD type:
Code:
adb reboot bootloader
Then press Enter key. (To enter Fastboot mode)
27- In CMD type:
Code:
fastboot flash boot_x magisk_patched.img
Then press Enter key. Change ‘X’ to your current slot from step 16, mine was ‘boot_a’. (This will flash Magisk to your boot)
28- In CMD type:
Code:
fastboot reboot
Then press Enter key. (This will reboot your phone)
On Phone:
29- Run Magisk Manager, check if Magisk is installed and you have two green ticks on the left.
Congratulations! Now you have successfully rooted your Black Shark 2 / 2 Pro !
Full Restore for Black Shark 2 Pro Global "DLT-H0" Fix most phone's issues and restore it to factory state. This also fixes OTA updating issues. (ONLY WORKS IF THE BOOTLOADER IS UNLOCKABLE / ANDROID 9 BOOTLOADER ONLY)
Download this zip file DLTR1908193OS00MP2, extract it and run flash_all.bat as administrator while your phone is connected to your PC and you must have USB Debugging enabled. (Right mouse click on 'flash_all.bat', then run as Administrator)
This can be done on a phone while on OS or Fastboot mode, and therefore this assumes that you followed steps 1-10 above.
Full OTA Global Factory Image for Black Shark 2 Global "SKW-H0" - Fix most phone's issues and restore it to factory state. This also fixes OTA updating issues. (make sure you choose the correct version 'OS00 or OS01')
1- If you have one of these versions 'SKYW1907040OS01MP3 -> SKYW1909192OS01MP4 -> SKYW1911121OS01MP5 -> SKYW2003090OS01MP6' then download this zip file SKYW2003090OS01MP6. If it doesn't work for some reason then download this file instead SKYW1907040OS01MP3.
If you have one of these versions 'SKYW1907031OS00MP3 -> SKYW1909192OS00MP4 -> SKYW1911010OS00MP5 -> SKYW2003090OS00MP6' then download this zip file SKYW2003090OS00MP6.
2- Rename km_update.zip to update.zip and move it to “ota” directory in your phone.
3- Dial this from your phone
Code:
*#*#1027#*#*
Then press "LOCAL UPDATE" and start updating your device. (You might need to do this twice)
Special thanks to:
Bave Lee for Bootloader Unlocking Code.
wzsx150 for BS2 TWRP.
topjohnwu for Magisk.
Snoop05 for ADB Installer Code.
wga0 for his great work for Black Shark community.
ripiad for providing Black Shark 2 firmwares.
PS: I put a lot of time and effort in making this guide, if you want to copy it to somewhere else, then at least give credit!
Great guide! Haven't tried it yet as I have my laptop at home. Can this be used with the Android 10 update?
starboi4eva said:
Great guide! Haven't yet as I have my laptop at home. Can this be used with the Android 10 update?
Click to expand...
Click to collapse
Thank you., I haven't test Android 10 as there are no official Android 10 release for global version yet, so I don't know for sure.
Great guide! :good:
In some cases, writing to root dir could touch the system images. It doesn't do any harm to system, but leaves a write-deleted trace and could block new update in rare cases. When backup the boot image, it could be safer to use the data(sdcard) partition.
From Android 10, this could be occurred always along their design.
{
"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"
}
wga0 said:
Great guide! :good:
In some cases, writing to root dir could touch the system images. It doesn't do any harm to system, but leaves a write-deleted trace and could block new update in rare cases. When backup the boot image, it could be safer to use the data(sdcard) partition.
From Android 10, this could be occurred always along their design.
Click to expand...
Click to collapse
I see, if so then we need to wipe data so we can write to data(sdcard) partition. I will edit this part of the guide, thanks a lot wag. By the way, I just received an email from Black Shark, they're pushing Android 10 updates "JOYUI 11" to Black Shark 2 / 2 Pro.
We have just announced that the Black Shark 2 and Black Shark 2 Pro models will both receive an update pack that will include JOYUI11. Users will be expected to receive an update notification between the dates of 27th April to 6th May 2020. For the owners of either of these phone models who are eagerly awaiting this update, your time has nearly come.
So, what will you all benefit from by having this new update? Here is a list of performances that you will come to expect from JOYUI11:
Key System Apps Improvements
Advanced experience with JOYUI > All Screen Gestures
IoT Capability
Natural Dynamic Sound System and Always on Display
Richer Tools
Click to expand...
Click to collapse
KM7 said:
I see, if so then we need to wipe data so we can write to data(sdcard) partition. I will edit this part of the guide, thanks a lot wag. By the way, I just received an email from Black Shark, they're pushing Android 10 updates "JOYUI 11" to Black Shark 2 / 2 Pro.
Click to expand...
Click to collapse
Thank you for your great works. It maybe be because of the different region of the TWRP ported and data partition is encrypted differently.
I received the global JoyUI 11 from ripiad, and uploaded it. If you could share me the global EEA, i will upload it also. Thanks again
Hi! Instruction is not working on BS2Pro Chinese version. The comand "fastboot oem bs_unlock" is not working=(
wga0 said:
Thank you for your great works. It maybe be because of the different region of the TWRP ported and data partition is encrypted differently.
I received the global JoyUI 11 from ripiad, and uploaded it. If you could share me the global EEA, i will upload it also. Thanks again
Click to expand...
Click to collapse
Nice work. I'm afraid I can't help you with that as I don't own BS2 anymore, I only have BS2 Pro now. However, I will let you know if I found something.
BuXLoW said:
Hi! Instruction is not working on BS2Pro Chinese version. The comand "fastboot oem bs_unlock" is not working=(
Click to expand...
Click to collapse
I thought so, that's why I said that this guide is for "Global version" and other versions should work too if the Bootloader is "unlocked".
I will try to find a way to unlock chinese version bootloader, the main problem is that I don't have a chinese phone sadly.
- Download ADB & TWRP Installer from here.
Click to expand...
Click to collapse
Well Yes, would like to believe it... but.... in bootloader each partition type and size.
I can imagine how many devices are already lying in boxes and waiting for the firmware and the method of restoring brick devices.
Are you suggesting that we send recovery and boot to space.
Code:
(bootloader) hw-revision:
(bootloader) unlocked:
(bootloader) off-mode-charge:
(bootloader) charger-screen-enabled:
(bootloader) battery-soc-ok:
(bootloader) battery-voltage:
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) app-install:
(bootloader) EWPDebugConfig:
(bootloader) erase-block-size:
(bootloader) logical-block-size:
(bootloader) variant:
(bootloader) partition-type:fsc:
(bootloader) partition-size:fsc:
(bootloader) partition-type:fsg:
(bootloader) partition-size:fsg:
(bootloader) partition-type:modemst2:
(bootloader) partition-size:modemst2:
(bootloader) partition-type:modemst1:
(bootloader) partition-size:modemst1:
(bootloader) partition-type:ALIGN_TO_128K_2:
(bootloader) partition-size:ALIGN_TO_128K_2:
(bootloader) partition-type:catecontentfv:
(bootloader) partition-size:catecontentfv:
(bootloader) partition-type:catefv:
(bootloader) partition-size:catefv:
(bootloader) partition-type:secdata:
(bootloader) partition-size:secdata:
(bootloader) partition-type:uefivarstore:
(bootloader) partition-size:uefivarstore:
(bootloader) partition-type:multiimgqti:
(bootloader) partition-size:multiimgqti:
(bootloader) partition-type:multiimgoem:
(bootloader) partition-size:multiimgoem:
(bootloader) partition-type:storsec:
(bootloader) partition-size:storsec:
(bootloader) partition-type:logdump:
(bootloader) partition-size:logdump:
(bootloader) partition-type:cateloader:
(bootloader) partition-size:cateloader:
(bootloader) partition-type:logfs:
(bootloader) partition-size:logfs:
(bootloader) partition-type:toolsfv:
(bootloader) partition-size:toolsfv:
(bootloader) partition-type:limits:
(bootloader) partition-size:limits:
(bootloader) partition-type:splash:
(bootloader) partition-size:splash:
(bootloader) partition-type:spunvm:
(bootloader) partition-size:spunvm:
(bootloader) partition-type:msadp:
(bootloader) partition-size:msadp:
(bootloader) partition-type:apdp:
(bootloader) partition-size:apdp:
(bootloader) partition-type:dip:
(bootloader) partition-size:dip:
(bootloader) partition-type:devinfo:
(bootloader) partition-size:devinfo:
(bootloader) partition-type:core_nhlos_b:
(bootloader) partition-size:core_nhlos_b:
(bootloader) partition-type:imagefv_b:
(bootloader) partition-size:imagefv_b:
(bootloader) partition-type:uefisecapp_b:
(bootloader) partition-size:uefisecapp_b:
(bootloader) partition-type:dtbo_b:
(bootloader) partition-size:dtbo_b:
(bootloader) partition-type:vbmeta_b:
(bootloader) partition-size:vbmeta_b:
(bootloader) partition-type:qupfw_b:
(bootloader) partition-size:qupfw_b:
(bootloader) partition-type:devcfg_b:
(bootloader) partition-size:devcfg_b:
(bootloader) partition-type:cmnlib64_b:
(bootloader) partition-size:cmnlib64_b:
(bootloader) partition-type:cmnlib_b:
(bootloader) partition-size:cmnlib_b:
(bootloader) partition-type:boot_b:
(bootloader) partition-size:boot_b:
(bootloader) partition-type:keymaster_b:
(bootloader) partition-size:keymaster_b:
(bootloader) partition-type:dsp_b:
(bootloader) partition-size:dsp_b:
(bootloader) partition-type:abl_b:
(bootloader) partition-size:abl_b:
(bootloader) partition-type:mdtp_b:
(bootloader) partition-size:mdtp_b:
(bootloader) partition-type:mdtpsecapp_b:
(bootloader) partition-size:mdtpsecapp_b:
(bootloader) partition-type:bluetooth_b:
(bootloader) partition-size:bluetooth_b:
(bootloader) partition-type:modem_b:
(bootloader) partition-size:modem_b:
(bootloader) partition-type:hyp_b:
(bootloader) partition-size:hyp_b:
(bootloader) partition-type:tz_b:
(bootloader) partition-size:tz_b:
(bootloader) partition-type:aop_b:
(bootloader) partition-size:aop_b:
(bootloader) partition-type:core_nhlos_a:
(bootloader) partition-size:core_nhlos_a:
(bootloader) partition-type:imagefv_a:
(bootloader) partition-size:imagefv_a:
(bootloader) partition-type:uefisecapp_a:
(bootloader) partition-size:uefisecapp_a:
(bootloader) partition-type:dtbo_a:
(bootloader) partition-size:dtbo_a:
(bootloader) partition-type:vbmeta_a:
(bootloader) partition-size:vbmeta_a:
(bootloader) partition-type:qupfw_a:
(bootloader) partition-size:qupfw_a:
(bootloader) partition-type:devcfg_a:
(bootloader) partition-size:devcfg_a:
(bootloader) partition-type:cmnlib64_a:
(bootloader) partition-size:cmnlib64_a:
(bootloader) partition-type:cmnlib_a:
(bootloader) partition-size:cmnlib_a:
(bootloader) partition-type:boot_a:
(bootloader) partition-size:boot_a:
(bootloader) partition-type:keymaster_a:
(bootloader) partition-size:keymaster_a:
(bootloader) partition-type:dsp_a:
(bootloader) partition-size:dsp_a:
(bootloader) partition-type:abl_a:
(bootloader) partition-size:abl_a:
(bootloader) partition-type:mdtp_a:
(bootloader) partition-size:mdtp_a:
(bootloader) partition-type:mdtpsecapp_a:
(bootloader) partition-size:mdtpsecapp_a:
(bootloader) partition-type:bluetooth_a:
(bootloader) partition-size:bluetooth_a:
(bootloader) partition-type:modem_a:
(bootloader) partition-size:modem_a:
(bootloader) partition-type:hyp_a:
(bootloader) partition-size:hyp_a:
(bootloader) partition-type:tz_a:
(bootloader) partition-size:tz_a:
(bootloader) partition-type:aop_a:
(bootloader) partition-size:aop_a:
(bootloader) partition-type:ddr:
(bootloader) partition-size:ddr:
(bootloader) partition-type:cdt:
(bootloader) partition-size:cdt:
(bootloader) partition-type:ALIGN_TO_128K_1:
(bootloader) partition-size:ALIGN_TO_128K_1:
(bootloader) partition-type:xbl_config_b:
(bootloader) partition-size:xbl_config_b:
(bootloader) partition-type:xbl_b:
(bootloader) partition-size:xbl_b:
(bootloader) partition-type:xbl_config_a:
(bootloader) partition-size:xbl_config_a:
(bootloader) partition-type:xbl_a:
(bootloader) partition-size:xbl_a:
(bootloader) partition-type:userdata:
(bootloader) partition-size:userdata:
(bootloader) partition-type:rawdump:
(bootloader) partition-size:rawdump:
(bootloader) partition-type:custom_b:
(bootloader) partition-size:custom_b:
(bootloader) partition-type:custom_a:
(bootloader) partition-size:custom_a:
(bootloader) partition-type:metadata:
(bootloader) partition-size:metadata:
(bootloader) partition-type:junklog:
(bootloader) partition-size:junklog:
(bootloader) partition-type:pstore:
(bootloader) partition-size:pstore:
(bootloader) partition-type:oeminfo:
(bootloader) partition-size:oeminfo:
(bootloader) partition-type:vendor_b:
(bootloader) partition-size:vendor_b:
(bootloader) partition-type:vendor_a:
(bootloader) partition-size:vendor_a:
(bootloader) partition-type:system_b:
(bootloader) partition-size:system_b:
(bootloader) partition-type:system_a:
(bootloader) partition-size:system_a:
(bootloader) partition-type:frp:
(bootloader) partition-size:frp:
(bootloader) partition-type:keystore:
(bootloader) partition-size:keystore:
(bootloader) partition-type:misc:
(bootloader) partition-size:misc:
(bootloader) partition-type:persist:
(bootloader) partition-size:persist:
(bootloader) partition-type:ssd:
(bootloader) partition-size:ssd:
(bootloader) has-slot:modem:
(bootloader) has-slot:system:
(bootloader) current-slot:
(bootloader) has-slot:boot:
(bootloader) slot-retry-count:b:
(bootloader) slot-unbootable:b:
(bootloader) slot-successful:b:
(bootloader) slot-retry-count:a:
(bootloader) slot-unbootable:a:
(bootloader) slot-successful:a:
(bootloader) slot-count:
(bootloader) secure:
(bootloader) stage:
(bootloader) product:
(bootloader) serialno:
(bootloader) product:
(bootloader) max-download-size:
(bootloader) kernel:
It will simply wipe the partition that cannot be flashed due to the multi-installer bootloader.
MCT_ said:
Well Yes, would like to believe it... but.... in bootloader each partition type and size.
I can imagine how many devices are already lying in boxes and waiting for the firmware and the method of restoring brick devices.
Are you suggesting that we send recovery and boot to space.
Code:
(bootloader) hw-revision:
(bootloader) unlocked:
(bootloader) off-mode-charge:
(bootloader) charger-screen-enabled:
(bootloader) battery-soc-ok:
(bootloader) battery-voltage:
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) app-install:
(bootloader) EWPDebugConfig:
(bootloader) erase-block-size:
(bootloader) logical-block-size:
(bootloader) variant:
(bootloader) partition-type:fsc:
(bootloader) partition-size:fsc:
(bootloader) partition-type:fsg:
(bootloader) partition-size:fsg:
(bootloader) partition-type:modemst2:
(bootloader) partition-size:modemst2:
(bootloader) partition-type:modemst1:
(bootloader) partition-size:modemst1:
(bootloader) partition-type:ALIGN_TO_128K_2:
(bootloader) partition-size:ALIGN_TO_128K_2:
(bootloader) partition-type:catecontentfv:
(bootloader) partition-size:catecontentfv:
(bootloader) partition-type:catefv:
(bootloader) partition-size:catefv:
(bootloader) partition-type:secdata:
(bootloader) partition-size:secdata:
(bootloader) partition-type:uefivarstore:
(bootloader) partition-size:uefivarstore:
(bootloader) partition-type:multiimgqti:
(bootloader) partition-size:multiimgqti:
(bootloader) partition-type:multiimgoem:
(bootloader) partition-size:multiimgoem:
(bootloader) partition-type:storsec:
(bootloader) partition-size:storsec:
(bootloader) partition-type:logdump:
(bootloader) partition-size:logdump:
(bootloader) partition-type:cateloader:
(bootloader) partition-size:cateloader:
(bootloader) partition-type:logfs:
(bootloader) partition-size:logfs:
(bootloader) partition-type:toolsfv:
(bootloader) partition-size:toolsfv:
(bootloader) partition-type:limits:
(bootloader) partition-size:limits:
(bootloader) partition-type:splash:
(bootloader) partition-size:splash:
(bootloader) partition-type:spunvm:
(bootloader) partition-size:spunvm:
(bootloader) partition-type:msadp:
(bootloader) partition-size:msadp:
(bootloader) partition-type:apdp:
(bootloader) partition-size:apdp:
(bootloader) partition-type:dip:
(bootloader) partition-size:dip:
(bootloader) partition-type:devinfo:
(bootloader) partition-size:devinfo:
(bootloader) partition-type:core_nhlos_b:
(bootloader) partition-size:core_nhlos_b:
(bootloader) partition-type:imagefv_b:
(bootloader) partition-size:imagefv_b:
(bootloader) partition-type:uefisecapp_b:
(bootloader) partition-size:uefisecapp_b:
(bootloader) partition-type:dtbo_b:
(bootloader) partition-size:dtbo_b:
(bootloader) partition-type:vbmeta_b:
(bootloader) partition-size:vbmeta_b:
(bootloader) partition-type:qupfw_b:
(bootloader) partition-size:qupfw_b:
(bootloader) partition-type:devcfg_b:
(bootloader) partition-size:devcfg_b:
(bootloader) partition-type:cmnlib64_b:
(bootloader) partition-size:cmnlib64_b:
(bootloader) partition-type:cmnlib_b:
(bootloader) partition-size:cmnlib_b:
(bootloader) partition-type:boot_b:
(bootloader) partition-size:boot_b:
(bootloader) partition-type:keymaster_b:
(bootloader) partition-size:keymaster_b:
(bootloader) partition-type:dsp_b:
(bootloader) partition-size:dsp_b:
(bootloader) partition-type:abl_b:
(bootloader) partition-size:abl_b:
(bootloader) partition-type:mdtp_b:
(bootloader) partition-size:mdtp_b:
(bootloader) partition-type:mdtpsecapp_b:
(bootloader) partition-size:mdtpsecapp_b:
(bootloader) partition-type:bluetooth_b:
(bootloader) partition-size:bluetooth_b:
(bootloader) partition-type:modem_b:
(bootloader) partition-size:modem_b:
(bootloader) partition-type:hyp_b:
(bootloader) partition-size:hyp_b:
(bootloader) partition-type:tz_b:
(bootloader) partition-size:tz_b:
(bootloader) partition-type:aop_b:
(bootloader) partition-size:aop_b:
(bootloader) partition-type:core_nhlos_a:
(bootloader) partition-size:core_nhlos_a:
(bootloader) partition-type:imagefv_a:
(bootloader) partition-size:imagefv_a:
(bootloader) partition-type:uefisecapp_a:
(bootloader) partition-size:uefisecapp_a:
(bootloader) partition-type:dtbo_a:
(bootloader) partition-size:dtbo_a:
(bootloader) partition-type:vbmeta_a:
(bootloader) partition-size:vbmeta_a:
(bootloader) partition-type:qupfw_a:
(bootloader) partition-size:qupfw_a:
(bootloader) partition-type:devcfg_a:
(bootloader) partition-size:devcfg_a:
(bootloader) partition-type:cmnlib64_a:
(bootloader) partition-size:cmnlib64_a:
(bootloader) partition-type:cmnlib_a:
(bootloader) partition-size:cmnlib_a:
(bootloader) partition-type:boot_a:
(bootloader) partition-size:boot_a:
(bootloader) partition-type:keymaster_a:
(bootloader) partition-size:keymaster_a:
(bootloader) partition-type:dsp_a:
(bootloader) partition-size:dsp_a:
(bootloader) partition-type:abl_a:
(bootloader) partition-size:abl_a:
(bootloader) partition-type:mdtp_a:
(bootloader) partition-size:mdtp_a:
(bootloader) partition-type:mdtpsecapp_a:
(bootloader) partition-size:mdtpsecapp_a:
(bootloader) partition-type:bluetooth_a:
(bootloader) partition-size:bluetooth_a:
(bootloader) partition-type:modem_a:
(bootloader) partition-size:modem_a:
(bootloader) partition-type:hyp_a:
(bootloader) partition-size:hyp_a:
(bootloader) partition-type:tz_a:
(bootloader) partition-size:tz_a:
(bootloader) partition-type:aop_a:
(bootloader) partition-size:aop_a:
(bootloader) partition-type:ddr:
(bootloader) partition-size:ddr:
(bootloader) partition-type:cdt:
(bootloader) partition-size:cdt:
(bootloader) partition-type:ALIGN_TO_128K_1:
(bootloader) partition-size:ALIGN_TO_128K_1:
(bootloader) partition-type:xbl_config_b:
(bootloader) partition-size:xbl_config_b:
(bootloader) partition-type:xbl_b:
(bootloader) partition-size:xbl_b:
(bootloader) partition-type:xbl_config_a:
(bootloader) partition-size:xbl_config_a:
(bootloader) partition-type:xbl_a:
(bootloader) partition-size:xbl_a:
(bootloader) partition-type:userdata:
(bootloader) partition-size:userdata:
(bootloader) partition-type:rawdump:
(bootloader) partition-size:rawdump:
(bootloader) partition-type:custom_b:
(bootloader) partition-size:custom_b:
(bootloader) partition-type:custom_a:
(bootloader) partition-size:custom_a:
(bootloader) partition-type:metadata:
(bootloader) partition-size:metadata:
(bootloader) partition-type:junklog:
(bootloader) partition-size:junklog:
(bootloader) partition-type:pstore:
(bootloader) partition-size:pstore:
(bootloader) partition-type:oeminfo:
(bootloader) partition-size:oeminfo:
(bootloader) partition-type:vendor_b:
(bootloader) partition-size:vendor_b:
(bootloader) partition-type:vendor_a:
(bootloader) partition-size:vendor_a:
(bootloader) partition-type:system_b:
(bootloader) partition-size:system_b:
(bootloader) partition-type:system_a:
(bootloader) partition-size:system_a:
(bootloader) partition-type:frp:
(bootloader) partition-size:frp:
(bootloader) partition-type:keystore:
(bootloader) partition-size:keystore:
(bootloader) partition-type:misc:
(bootloader) partition-size:misc:
(bootloader) partition-type:persist:
(bootloader) partition-size:persist:
(bootloader) partition-type:ssd:
(bootloader) partition-size:ssd:
(bootloader) has-slot:modem:
(bootloader) has-slot:system:
(bootloader) current-slot:
(bootloader) has-slot:boot:
(bootloader) slot-retry-count:b:
(bootloader) slot-unbootable:b:
(bootloader) slot-successful:b:
(bootloader) slot-retry-count:a:
(bootloader) slot-unbootable:a:
(bootloader) slot-successful:a:
(bootloader) slot-count:
(bootloader) secure:
(bootloader) stage:
(bootloader) product:
(bootloader) serialno:
(bootloader) product:
(bootloader) max-download-size:
(bootloader) kernel:
It will simply wipe the partition that cannot be flashed due to the multi-installer bootloader.
Click to expand...
Click to collapse
Could you explain more clearly as I couldn't understand what you are talking about. If your phone is brick and some partitions are wiped out you can fix it by flashing the correct full firmware file. @wga0 posted many of these firmware you can check them if you need, I also prepared a custom full firmware flasher for my Black Shark 2 Pro global to fix any issue that might happen to my phone in future.
This guide is for people who have a fully functional phones and want to root them. If your phone is bricked then this guide is not for you.
KM7 said:
Could you explain more clearly as I couldn't understand what you are talking about. If your phone is brick and some partitions are wiped out you can fix it by flashing the correct full firmware file. @wga0 posted many of these firmware you can check them if you need, I also prepared a custom full firmware flasher for my Black Shark 2 Pro global to fix any issue that might happen to my phone in future.
This guide is for people who have a fully functional phones and want to root them. If your phone is bricked then this guide is not for you.
Click to expand...
Click to collapse
My device can't be a brick by definition. You are checking it incorrectly.
fastboot set_active other If it shows that you are in sector A, then you must flash in sector B.
fastboot set_active other b = fastboot flash boot_a boot.img
Secondly, where you flash the recovery is not clear.
==============================================
The entire firmware process takes a few minutes. To restore your device completely. You need to back up your partitions or you won't find them anywhere else.
cd C://ADB
fastboot set_active other
Code:
set fd=%CD%
cd C:\ADB
// If B
fastboot flash system_a %fd%\system
fastboot flash vendor_a %fd%\vendor
fastboot flash boot_a %fd%\boot
fastboot flash custom_a %fd%\custom
fastboot flash vbmeta_a %fd%\vbmeta
fastboot flash modem_a %fd%\modem
// If A
fastboot flash system_b %fd%\system
fastboot flash vendor_b %fd%\vendor
fastboot flash boot_b %fd%\boot
fastboot flash custom_b %fd%\custom
fastboot flash vbmeta_b %fd%\vbmeta
fastboot flash modem_b %fd%\modem
fastboot format userdata
fastboot reboot
===============================
If B
fastboot flash system_a system.img
fastboot flash vendor_a vendor.img
fastboot flash boot_a boot.img
fastboot flash custom_a custom.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash modem_a modem.img
If A
fastboot flash system_b system.img
fastboot flash vendor_b vendor.img
fastboot flash boot_b boot.img
fastboot flash custom_b custom.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_b modem.img
For a General understanding of the process.
....By the way, I am currently on the Pro version firmware.
My phone was completely dead for some time, 5-10 minutes at most. I was erasing everything that was in the loader at the time. It is not so easy to turn it into a brick. If you know what you're doing. Your only problem is that there is no backup of partitions, they have not been publicly uploaded anywhere else. All that I have been able to find on the Internet so far is the same Pie 9 on which I have now flashed my device. Corny, but no Rom... not because of the brick.
MCT_ said:
My device can't be a brick by definition. You are checking it incorrectly.
fastboot set_active other If it shows that you are in sector A, then you must flash in sector B.
fastboot set_active other b = fastboot flash boot_a boot.img
Secondly, where you flash the recovery is not clear.
==============================================
The entire firmware process takes a few minutes. To restore your device completely. You need to back up your partitions or you won't find them anywhere else.
cd C://ADB
fastboot set_active other
Code:
set fd=%CD%
cd C:\ADB
If B
fastboot flash system_a %fd%\system
fastboot flash vendor_a %fd%\vendor
fastboot flash boot_a %fd%\boot
fastboot flash custom_a %fd%\custom
fastboot flash vbmeta_a %fd%\vbmeta
fastboot flash modem_a %fd%\modem
If A
fastboot flash system_b %fd%\system
fastboot flash vendor_b %fd%\vendor
fastboot flash boot_b %fd%\boot
fastboot flash custom_b %fd%\custom
fastboot flash vbmeta_b %fd%\vbmeta
fastboot flash modem_b %fd%\modem
fastboot format userdata
fastboot reboot
===============================
If B
fastboot flash system_a system.img
fastboot flash vendor_a vendor.img
fastboot flash boot_a boot.img
fastboot flash custom_a custom.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash modem_a modem.img
If A
fastboot flash system_b system.img
fastboot flash vendor_b vendor.img
fastboot flash boot_b boot.img
fastboot flash custom_b custom.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_b modem.img
For a General understanding of the process.
....By the way, I am currently on the Pro version firmware.
My phone was completely dead for some time, 5-10 minutes at most. I was erasing everything that was in the loader at the time. It is not so easy to turn it into a brick. If you know what you're doing. Your only problem is that there is no backup of partitions, they have not been publicly uploaded anywhere else. All that I have been able to find on the Internet so far is the same Pie 9 on which I have now flashed my device. Corny, but no Rom... not because of the brick.
Click to expand...
Click to collapse
Man, I guess we are lost in translation. let's do this one by one.
1- What's your phone model? (Black shark 2 or 2 Pro)
2- What's your phone version? (Global or Chinese)
3- What is you last working firmware number. (If Global)
4- Can you boot normally to OS?
5- Can you access Fastboot mode?
6- Do you want to Root your phone or only want to flash a firmware to fix a problem?
Answer those questions and I will try to help you out.
KM7 said:
Man, I guess we are lost in translation. let's do this one by one.
1- What's your phone model? (Black shark 2 or 2 Pro)
2- What's your phone version? (Global or Chinese)
3- What is you last working firmware number. (If Global)
4- Can you boot normally to OS?
5- Can you access Fastboot mode?
6- Do you want to Root your phone or only want to flash a firmware to fix a problem?
Answer those questions and I will try to help you out.
Click to expand...
Click to collapse
You can help everyone if you make img copies of partitions from the global build of one of the very first ROMs, so that a person can restore the entire operating system. I gave an example of how to do this above. How can you help me if you can't help yourself ?
MCT_ said:
You can help everyone if you make img copies of partitions from the global build of one of the very first ROMs, so that a person can restore the entire operating system. I gave an example of how to do this above. How can you help me if you can't help yourself ?
Click to expand...
Click to collapse
lol, I already made my own copy of partitions img and made my own flashing script to fix any bricks I could face on my phone "BS 2 Pro" using fastboot, and I'm willing to share it if someone needs it. So don't talk about me like you know me and you know what I have or what I can do. I believe you're the one who needs help here, as my phone is still working flawlessly.
I guess @wga0 can easily help you if you ask politely.
Please i need help
I root my BS2P (DLT-H0) it worked, but im facing issues like wifi wont on, no sound, can't play video, . Please help I don't know what to do. ???.
---------- Post added at 07:21 PM ---------- Previous post was at 07:14 PM ----------
KM7 said:
lol, I already made my own copy of partitions img and made my own flashing script to fix any bricks I could face on my phone "BS 2 Pro" using fastboot, and I'm willing to share it if someone needs it. So don't talk about me like you know me and you know what I have or what I can do. I believe you're the one who needs help here, as my phone is still working flawlessly.
I guess @wga0 can easily help you if you ask politely.
Click to expand...
Click to collapse
I root my BS2P (DLT-H0) it worked, but im facing issues like wifi wont on, no sound, can't play video, . Please help I don't know what to do. ??
kiemitbalfru said:
I root my BS2P (DLT-H0) it worked, but im facing issues like wifi wont on, no sound, can't play video, . Please help I don't know what to do. .
---------- Post added at 07:21 PM ---------- Previous post was at 07:14 PM ----------
I root my BS2P (DLT-H0) it worked, but im facing issues like wifi wont on, no sound, can't play video, . Please help I don't know what to do.
Click to expand...
Click to collapse
how did you root it? with my guide or other?
KM7 said:
how did you root it? with my guide or other?
Click to expand...
Click to collapse
I did it with other tutorial . I wish ive seen your tutorial before ?. All i want to do now is bring my phone back to normal. I know that your the only one that can help me. Thanknyou so much.
kiemitbalfru said:
I did it with other tutorial . I wish ive seen your tutorial before . All i want to do now is bring my phone back to normal. I know that your the only one that can help me. Thanknyou so much.
Click to expand...
Click to collapse
No worries, I will help you fixing those issues.
First do you have a backup of your stock boot.img?
If so, then determine what slot you're using, by booting to Fastboot then type this in CMD:
Code:
fastboot getvar current-slot
if it is slot "A" then:
fastboot flash boot_a "your stock boot.img path"
Click to expand...
Click to collapse
if it is slot "B" then:
fastboot flash boot_b "your stock boot.img path"
Click to expand...
Click to collapse
This will restore you phone to original status.
If however you don't have the stock boot.img, then find your firmware "software version" and post it and I will try to find you the correct stock boot.img.
Then, If you want to root it correctly, follow my guide from step 30 and onward.
KM7 said:
No worries, I will help you fixing those issues.
First do you have a backup of your stock boot.img?
If so, then determine what slot you're using, by booting to Fastboot then type this in CMD:
Code:
fastboot getvar current-slot
if it is slot "A" then:
if it is slot "B" then:
This will restore you phone to original status.
If however you don't have the stock boot.img, then find your firmware "software version" and post it and I will try to find you the correct stock boot.img.
Then, If you want to root it correctly, follow my guide from step 30 and onward.
Click to expand...
Click to collapse
i don't know how to back up the boot.img , here my joyui version : DLTR1911250OS00MP1
kiemitbalfru said:
i don't know how to back up the boot.img , here my joyui version : DLTR1911250OS00MP1
Click to expand...
Click to collapse
Luckily I've backed up all the boot.img I used to have. Here you go!

Hard brick Mi 8 Lite.

Hi,
I bricked the Mi 8 Lite (platina)
I had Rom Lineage 20 and TRWP 3.7.0_12 uploaded.
I wanted to flash back the MIUI ROM so I did a wipe in recovery and flash new rom. After reboot the system booted but there was no recovery. Fastboot only. I wanted to upload a new recovery (fastboot flash recovery recovery.img) but I get the error:
FAILED (Write to device failed (Invalid argument))
---------------------------------------------------------------------------------
When trying to:
fastboot devices
4fa7e5b9 fastboot
-------------------------------------------------------------------------------
When trying to:
fastboot getvar all
---------------------------------------------------------------------------------
<waiting for any device>
(bootloader) DP:0x0
(bootloader) token:VQEBIQEQnmryIh8fcJ8Ox+x507NtFwMHcGxhdGluYQIE+x0CYg==
(bootloader) crc:1
(bootloader) cpuid:0xfb1d0262
(bootloader) board_version:2.19.0
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4326
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC7F7FBE00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xC0000000
(bootloader) secure:yes
(bootloader) serialno:4fa7e5b9
(bootloader) productlatina
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.003s
----------------------------------------------------------------------
The MIUI system booted normally, but I did factory reset, because I thought it would enter recovery and now only fastboot
I tested fastboot on Windows 11 and Fedora. The same all the time.
EDIT:
-------------------------------------------------------------------------------------------------
When i try "fastboot continue"
Resuming boot FAILED (Status read failed (No such device))
------------------------------------------------------------------------------------------------
But system MIUI booted.
sudo adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
4fa7e5b9 device
Question: Howto flash recovery ? Or fix that ?

Categories

Resources