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.
whatever TWRP version I tried to flash recovery on my MiPad (newly bought from aliexpress), I'm getting errors. (and show 'press any key to shutdown)
when it boot, it's showing "Unlocked" below
Code:
$ fastboot devices
8XXXXXX3 fastboot
$ fastboot getvar all
(bootloader) crc:1
(bootloader) anti:1
(bootloader) token:VQ[.......]QhBhu
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4371
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:vendor:ext4
(bootloader) partition-size:vendor: 0x80000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xCAD753E00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xC0000000
(bootloader) secure:yes
(bootloader) serialno: 8XXXXXX3
(bootloader) product:clover
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.109s
Code:
$ fastboot boot twrp_clover-3.3.1-recommand.img
Sending 'boot.img' (34680 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
Code:
$ fastboot flash recovery recovery-33.img
Sending 'recovery' (64644 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
Code:
$ fastboot flash recovery recovery-33.img
Sending 'recovery' (64644 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Code:
$ fastboot --version
fastboot version 29.0.1-5644136
can anyone help me?
Yes, just get a USB 2.0 HUB.
Fastboot does NOT work with USB 3.0 with this device. That's it.
I just used an old notebook that is USB2 only.
Same problem.
*Le sigh*
Can 100% confirm this is the problem and solution. Used an ancient laptop I had lying around just to flash TWRP. Rest is gravy.
I just flahsed & rooted my MI PAD 4 bought from China a while ago yesterday for the very first time and I concurred, using an older USB port (2.0) is the right way to deal with this problem, otherwise you will see "press any key to shut down" message no matter what you do, and you can't go beyond this page.
Maybe it's late, but for the best result, try windows 7 too. I plug the tab into the usb 2.0 port on my win 10 pc and the dreaded "press any key to shutdown" button still appear.
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!