Related
Hi, Guys.
I have the following problem:
My watch is with stock international 2.3.9.0.
I've tried to install STRATOSfied v28, but the recovery file from https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/permanent-install isn't working as it is expected.
The watch reboots, but the "#" sign is not available in the adb shell.
Also it gaves an error in fastboot mode (fastboot boot recovery.img(whatever the name is).
too many links, FAILED etc...
So i have Ubuntu18.10 and windows10 - no difference in both OS. Also I've tried on separated laptop (windows 10 again) with no positive effect.
Before 2.3.9.0 i was with version 26 and some previous ones (by permanent install, not only update via "sh" script in the shell) - No problems with all previous versions i've tested
So.. maybe there is a new bootloader and it needs a new recovery to temporary root the device. I don't know, but the normal installation isn't working anymore, so I've flashed clean 2.3.9.0 via Fastboot and I am staying in Stock ROM until something is changed.
Thank you if you have solution of this. I'll try it
post your fastboot getvar all output
1immortal said:
post your fastboot getvar all output
Click to expand...
Click to collapse
(bootloader) version-bootloader: U-Boot 2013.07-00146-g43d9f8c
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 16191828090306
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
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.
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!
So I tried to flash a custom recovery and rom but when I flashed my rom it booted to boot loader and it said oem_locked when I had it unlocked 2 minutes ago. So I try to go into twrp and I can’t, says start up failed. I tried using the software but it said it can’t identify my device and it can’t fix anything. I also tried to flash stock rom via and but it said it can’t find and can’t mount any partitions. This leads me to believe that my partitions are gone or corrupt. Can anyone help? Im not sure the model number but I know the phone is a Moto g7 Power from t-mobile that was completely unlocked, boot loader and all.
Can you get into fastboot mode? Try using the command, fastboot getvar all, it should give you information about partitions available.
Try flashing one image at a time.
You probably need to use an unbrick firmware and (100)% the correct driver.
An unbrick software will format your device ssd and create all the partitions again.
JonasHS said:
Can you get into fastboot mode? Try using the command, fastboot getvar all, it should give you information about partitions available.
Try flashing one image at a time.
You probably need to use an unbrick firmware and (100)% the correct driver.
An unbrick software will format your device ssd and create all the partitions again.
Click to expand...
Click to collapse
I ran getvar and it spat out this.
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_t-16222030b3b-210202
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 751d40d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ocean_t-16222030b3b-210202
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
Also when I try to run Motorola's software it does this
The second picture is what it says when I try to use manual. I click use anyway and it just goes back to saying not appropriate firmware.
Also trying to install the images one by one also didnt work.
Unbrick tools
Have your phone edl mode? Snapdragon =Qualcomm?
Once you have installed custom ROM, your partition should not be the same a / b order.
You are need to use moto's unbrick tool in edl.
JonasHS said:
Once you have installed custom ROM, your partition should not be the same a / b order.
You are need to use moto's unbrick tool in edl.
Click to expand...
Click to collapse
I tried to get into Edl mode but my phone doesn't have Edl mode
also that was Motorola's unbrick tool and it didn't work.
Your CPU is Qualcomm Snapdragon. You have it. Edl is same some bios on PC. Is built in your phone. Try to boot into it, your are need PC and USB and driver for edl.
I hope you know then you are in edl mode have your phone black screen.
JonasHS said:
Your CPU is Qualcomm Snapdragon. You have it. Edl is same some bios on PC. Is built in your phone. Try to boot into it, your are need PC and USB and driver for edl.
I hope you know then you are in edl mode have your phone black screen.
Click to expand...
Click to collapse
I tried. It said unknown command. I patched the fastboot exe to tell it to go to edl mode and it says unknown command.
that_one_gamer said:
I tried. It said unknown command. I patched the fastboot exe to tell it to go to edl mode and it says unknown command.
Click to expand...
Click to collapse
I have the driver and everything. Doesn’t work.
Fastboot can't reboot you into edl, you are need to connect phone to USB to PC and hold vol - and vol+ and power on same time and see device on PC
Have you never used del before?
JonasHS said:
Have you never used del before?
Click to expand...
Click to collapse
I tried doing that and it just goes to the boot loader.
JonasHS said:
Click to expand...
Click to collapse
That’s not edl mode. That’s bootloader. Plus that’s what I did and the software didn’t work. I included screenshots in one of the other reply’s.
You don't understand How did you think android come on SSD. Factory install it with download mode.
JonasHS said:
You don't understand How did you think android come on SSD. Factory install it with download mode.
Click to expand...
Click to collapse
I do understand, the software does not allow me to reflash with download mode. If I try to reflash manually it fails because partitions cannot be mounted.
This is what the software says
that_one_gamer said:
This is what the software says
Click to expand...
Click to collapse
Look at the screenshots. And I also cannot access recovery mode.
Edit 1/31/2023: Was able to get this sorted out. Explanation is on post #29.
Edited on 8/26/2022:
Cannot boot the phone into fastboot which I believe is because I turned off OEM unlocking then unrooted the phone. Now OEM unlocking is off and greyed out probably because the magisk safetynet fix module is gone. Deep testing app didn't help it just tells me to run fastboot flashing lock. Factory defaulting or flashing with the MSM tool didn't help either. Everything else works fine, the bootloader is still unlocked, recovery mode works and I can get into the system just cannot get into fastboot mode.
Edit 12/13: Was able to get the phone rooted again from fastbootD mode and turn OEM unlocking back on but this did not fix the main issue - fastboot still wont boot meaning I still cannot relock the bootloader.. The phone makes a short attempt then boots right back into the system. Tried flashing but bootloader was still unlocked after a full MSM flash and USB debugging was still turned on as well. Any suggestions?
can you try the below
open the dialer and type code *#899# then choose SoftwareVersion and take a screenshot and post it here.
zorbakun said:
can you try the below
open the dialer and type code *#899# then choose SoftwareVersion and take a screenshot and post it here.
Click to expand...
Click to collapse
Here is what I got.
{
"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"
}
I think I figured out what I did wrong to end up here. I had it magisk rooted with the safetynet fix module and while messing with the phone I think I clicked off "OEM unlocking" in dev options then I uninstalled magisk without clicking it back on. Now "OEM unlocking" is turned off and is greyed out so I cant turn it back on. At least the bootloader is still unlocked but no matter what I do I cannot get into fastboot mode. Have already tried factory reset and flashing the stock rom back with the MSM tool and that did not work. So I need to find a way to root or temporarily root the phone without using fastboot, or somehow ungrey/turn back on "OEM unlocking," or find a way to replace the boot.img of the stock firmware with a magisk patched image then either use local system update, the MSM tool or QFIL to install it. Does someone have any ideas on how to do this?
Or is there a way to force the phone to go back to the inactive slot where I have a magisk patched boot image installed, as in mess up slot _b to force it back to slot _a? What if I were to flash with the MSM tool to slot _b but unplug the cable before it finished to mess it up, could that make the phone revert back to slot _a?
GIutton said:
I think I figured out what I did wrong to end up here. I had it magisk rooted with the safetynet fix module and while messing with the phone I think I clicked off "OEM unlocking" in dev options then I uninstalled magisk without clicking it back on. Now "OEM unlocking" is turned off and is greyed out so I cant turn it back on. At least the bootloader is still unlocked but no matter what I do I cannot get into fastboot mode. Have already tried factory reset and flashing the stock rom back with the MSM tool and that did not work. So I need to find a way to root or temporarily root the phone without using fastboot, or somehow ungrey/turn back on "OEM unlocking," or find a way to replace the boot.img of the stock firmware with a magisk patched image then either use local system update, the MSM tool or QFIL to install it. Does someone have any ideas on how to do this?
Or is there a way to force the phone to go back to the inactive slot where I have a magisk patched boot image installed, as in mess up slot _b to force it back to slot _a? What if I were to flash with the MSM tool to slot _b but unplug the cable before it finished to mess it up, could that make the phone revert back to slot _a?
Click to expand...
Click to collapse
try using the testing apk used to unlock the bootloader, it may help you access fastboot again
zorbakun said:
try using the testing apk used to unlock the bootloader, it may help you access fastboot again
Click to expand...
Click to collapse
Right that was the first thing I tried. It just tells me to run "fastboot flashing lock" but can't access fastboot to do it. Will the MSM tool only work with an ofp file or is there a way to use it with extracted firmware?
Here are some ideas:
- What happens when you run adb reboot bootloader?
- Cache and userdata wipe?
- Read through this, maybe helpful:
[Q] ANY way to toggle Allow OEM Unlock via Fastboot?
I sold my N9 on eBay and the buyer requested a refund claiming it wouldn't boot. I got it back and found this person had somehow relocked the bootloader [improperly] and now I can only get into Fastboot mode...but I can't flash anything because...
forum.xda-developers.com
- Do you have root access? If so, you could maybe try
GitHub - gibcheesepuffs/Switch-My-Slot-Android: Switch My Slot Android app helps you switch between android A & B slots
Switch My Slot Android app helps you switch between android A & B slots - GitHub - gibcheesepuffs/Switch-My-Slot-Android: Switch My Slot Android app helps you switch between android A & B s...
github.com
- Going to system - upgrade - local update, and feeding it A.18.
Here is a stock 300mb a.17 - a.18 update file, I don't have the 5GB one unfortunately.
my_manifest_RMX3301_11.A.18_0180_202207251111.1A.82076da7_patch.zip
drive.google.com
-In addition to above, maybe you could extract it and replace boot.img with a patched one, and pack back up as update file. Although this may throw out a checksum error when attempting to install..
Quake94 said:
Here are some ideas:
- What happens when you run adb reboot bootloader?
- Cache and userdata wipe?
- Read through this, maybe helpful:
[Q] ANY way to toggle Allow OEM Unlock via Fastboot?
I sold my N9 on eBay and the buyer requested a refund claiming it wouldn't boot. I got it back and found this person had somehow relocked the bootloader [improperly] and now I can only get into Fastboot mode...but I can't flash anything because...
forum.xda-developers.com
- Do you have root access? If so, you could maybe try
GitHub - gibcheesepuffs/Switch-My-Slot-Android: Switch My Slot Android app helps you switch between android A & B slots
Switch My Slot Android app helps you switch between android A & B slots - GitHub - gibcheesepuffs/Switch-My-Slot-Android: Switch My Slot Android app helps you switch between android A & B s...
github.com
- Going to system - upgrade - local update, and feeding it A.18.
Here is a stock 300mb a.17 - a.18 update file, I don't have the 5GB one unfortunately.
my_manifest_RMX3301_11.A.18_0180_202207251111.1A.82076da7_patch.zip
drive.google.com
-In addition to above, maybe you could extract it and replace boot.img with a patched one, and pack back up as update file. Although this may throw out a checksum error when attempting to install..
Click to expand...
Click to collapse
When I run adb reboot bootloader the phone tries but then the screen glitches for a second then reboots into the system. I get the same result when I hold power and volume down buttons. Have tried factory defaulting from the settings menu and also tried wiping data from the recovery.
I do not have root access but the bootloader is unlocked. I tried using the exploit shared by Rapper_Skull to get temporary root access and it said it had worked but the magisk app does not recognize it as rooted and "adb shell su" is not recognized either. Rapper_Skull explained it was not within the scope of the exploit. Maybe it could be modified to do it somehow but that is beyond me.
I would love to try a local update with a patched boot image but I can't seem to find the proper OTA for my nv_id 10100110 MEA and because of the nv_id the Android 13 beta and rollback packages wont work either. Not too hopeful on this though as you said it will likely give a checksum error. From what I have read the MSM or QFIL tools should be able to do it, but would need to repack the ofp file with a patched boot for the MSM tool and nodoby has gotten QFIL to work that I have seen.
I will definitely read through the URLs you posted but turning on OEM unlocking from fastboot wont be an option for me since I can't get into it. In desperation I also scrolled through every single adb shell list settings <system/secure/global> output on this phone and my old OP 8T looking for a line item for OEM unlocking I could modify or add but alas there isn't one. Also tried talking to realme and they basically told me to go kick rocks because I am in the US so no support or warranty. They wouldn't even sell me a motherboard!
I have tried the MSM tool a couple times but it never worked. I am like 80% sure the tool kept flashing to active _b slot so I think my inactive _a slot should still contain my patched A.17 boot.img. I am very tempted to try flashing with the MSM tool again but unplugging the cable when it goes to clear/write the boot partition to mess it up. My thinking being that it would force the phone back onto slot _a just like it would do if an update fails, but that just sounds like such a dumb idea that it couldn't possibly work lol. Even if I do it and mess something up I should still be able to flash it with MSM again to fix it right? EDIT: Never mind my active slot is _a. When I took the A.18 update it went into slot _b meaning A.17 with my patched boot was on slot _a so the MSM tool must have been writing to the inactive slot and I only paid attention on the second flash to slot _b.
Try this
1. Run: adb shell pm disable-user com.qualcomm.qti.uim
2. Go to Developer Options and flip the OEM Unlock toggle
3. Now run: adb shell pm enable com.qualcomm.qti.uim
4. From now on the toggle will be disabled again, but now in "on" mode
5. Reboot to fastboot
Quake94 said:
Try this
1. Run: adb shell pm disable-user com.qualcomm.qti.uim
2. Go to Developer Options and flip the OEM Unlock toggle
3. Now run: adb shell pm enable com.qualcomm.qti.uim
4. From now on the toggle will be disabled again, but now in "on" mode
5. Reboot to fastboot
Click to expand...
Click to collapse
I gave it a try but OEM unlocking remained greyed out.
GIutton said:
I gave it a try but OEM unlocking remained greyed out.
Click to expand...
Click to collapse
From what I seen you should try pressing OEM unlock toggle with the qualcomm service disabled, despite ithe toggle being greyed out, have you tried that?
I found this method in OnePlus forums, since OnePlus/Oppo/Realme it's all the same.
OEM unlocking T-Mobile
My unlocking is greyed out. Is there a way to get the bootloader unlocked? I really want to get a pixel style rom and get rid of T-Mobile crap
forum.xda-developers.com
Quake94 said:
From what I seen you should try pressing OEM unlock toggle with the qualcomm service disabled, despite ithe toggle being greyed out, have you tried that?
I found this method in OnePlus forums, since OnePlus/Oppo/Realme it's all the same.
OEM unlocking T-Mobile
My unlocking is greyed out. Is there a way to get the bootloader unlocked? I really want to get a pixel style rom and get rid of T-Mobile crap
forum.xda-developers.com
Click to expand...
Click to collapse
I just tried it but still can't get into fastboot mode. Thank you for suggestion though I really appreciate your help.
Someone suggested I try adb shell reboot fastboot and that booted the phone into fastbootd mode but I get no output from "fastboot devices". As far as I can tell it looks just like recovery only the title says Fastbootd Mode instead of "RECOVERY".
GIutton said:
Someone suggested I try adb shell reboot fastboot and that booted the phone into fastbootd mode but I get no output from "fastboot devices". As far as I can tell it looks just like recovery only the title says Fastbootd Mode instead of "RECOVERY".
Click to expand...
Click to collapse
Update your fastboot drivers.
Well I updated my drivers and that got the phone recognized in fastbootd mode. I tried fastboot boot magisk-patched-boot.img but that failed, however, fastboot flash boot magisk-patched-boot.img did work so I was finally able to root the phone and apply the safetynet fix which ungreyed OEM unlocking and allowed me to flip it back on. Unfortunately that did not fix the bootloader/fastboot issue. No matter what I still cannot get into fastboot mode.
I was thinking of trying fastboot flashing lock to see if I can relock the bootloader from fastbootd mode but I would rather not make things worse by doing something I shouldn't be doing in fastbootd mode.
GIutton said:
Well I updated my drivers and that got the phone recognized in fastbootd mode. I tried fastboot boot magisk-patched-boot.img but that failed, however, fastboot flash boot magisk-patched-boot.img did work so I was finally able to root the phone and apply the safetynet fix which ungreyed OEM unlocking and allowed me to flip it back on. Unfortunately that did not fix the bootloader/fastboot issue. No matter what I still cannot get into fastboot mode.
I was thinking of trying fastboot flashing lock to see if I can relock the bootloader from fastbootd mode but I would rather not make things worse by doing something I shouldn't be doing in fastbootd mode.
Click to expand...
Click to collapse
Have you tried EDL flash? It should be able to restore it back to stock.
bubundas17 said:
Have you tried EDL flash? It should be able to restore it back to stock.
Click to expand...
Click to collapse
By EDL flash do you mean flashing with the MSM tool? I have tried it several times and it did not help. The bootloader remained unlocked and still cannot boot the phone to fastboot mode.
I replied in the other thread already, but from what it appears, there is a lot of confusion with the boot modes.
bootloader/fastboot -> adb reboot bootloader (or the key combo) -> This is the mode with the green START button on top
fastbootd - adb reboot fastboot, or fastboot reboot fastboot (from being already in bootloader/fastboot) ->This is the mode with selection of "Wipe Data", "Reboot" and "Power Off", same as Recovery but the label is "Fastbootd"
recovery - adb reboot recovery (or the key combo) -> Shows "Wipe Data", "Reboot" and "Power Off", label is "Recovery"
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry -> This is for QCIL / MSM or any other Qualcomm firehose flashing.
So can you confirm:
When I run adb reboot bootloader the phone tries but then the screen glitches for a second then reboots into the system.
Click to expand...
Click to collapse
When you ran adb reboot bootloader, did you see a "mascot", or did it look like a screen glitch?
adb reboot bootloader should get you to the regular fastboot with green START
The "mascot" would show only when the phone was starting fastboot
The "glitch" happened to me when I've installed OTA and then I tried to boot to second slot via Magisk or "set_active" command. And what fixed it was selecting "Install" in OEM updater.
Quake94 said:
I replied in the other thread already, but from what it appears, there is a lot of confusion with the boot modes.
bootloader/fastboot -> adb reboot bootloader (or the key combo) -> This is the mode with the green START button on top
fastbootd - adb reboot fastboot, or fastboot reboot fastboot (from being already in bootloader/fastboot) ->This is the mode with selection of "Wipe Data", "Reboot" and "Power Off", same as Recovery but the label is "Fastbootd"
recovery - adb reboot recovery (or the key combo) -> Shows "Wipe Data", "Reboot" and "Power Off", label is "Recovery"
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry -> This is for QCIL / MSM or any other Qualcomm firehose flashing.
So can you confirm:
When you ran adb reboot bootloader, did you see a "mascot", or did it look like a screen glitch?
adb reboot bootloader should get you to the regular fastboot with green START
The "mascot" would show only when the phone was starting fastboot
The "glitch" happened to me when I've installed OTA and then I tried to boot to second slot via Magisk or "set_active" command. And what fixed it was selecting "Install" in OEM updater.
Click to expand...
Click to collapse
When I try the button combo the screen shows the realme logo then glitches and reboots to the system and from there if I try adb reboot bootloader I get a mascot looking thing with chinese letters then the screen glitches and it reboots right back into the system.
So you are calling the button combo "fastboot mode" and adb reboot bootloader/fastboot reboot bootloader the "bootloader" but both of these show the same start menu?
GIutton said:
When I try the button combo the screen shows the realme logo then glitches and reboots to the system and from there if I try adb reboot bootloader I get a mascot looking thing with chinese letters then it reboots right back into the system.
So you are calling the button combo "fastboot mode" and adb reboot bootloader/fastboot reboot bootloader the "bootloader" but both of these show the same start menu?
Click to expand...
Click to collapse
Holding Volume Down + Power button starts the "fastboot mode", same mode as the command adb reboot bootloader.
My understanding is that bootloader mode is same as fastboot mode.
On a side note, when I run fastboot oem device-info, I have the following: information
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
Click to expand...
Click to collapse
Also, running fastboot getvar all:
platform-tools>fastboot getvar all
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:20002
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:7904
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:SM_ UFS
(bootloader) partition-typeplusreserve5:raw
(bootloader) partition-sizeplusreserve5: 0x4000000
(bootloader) partition-typeplusreserve4:raw
(bootloader) partition-sizeplusreserve4: 0x2000000
(bootloader) partition-typeplusreserve3:raw
(bootloader) partition-sizeplusreserve3: 0x4000000
(bootloader) partition-typeplusreserve2:raw
(bootloader) partition-sizeplusreserve2: 0x10000000
(bootloader) partition-typeplusreserve1:raw
(bootloader) partition-sizeplusreserve1: 0x800000
(bootloader) partition-type:mdm1oemnvbktmp:raw
(bootloader) partition-size:mdm1oemnvbktmp: 0x200000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x20000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x300000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x300000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x300000
(bootloader) partition-typeplusstanvbk_a:raw
(bootloader) partition-sizeplusstanvbk_a: 0x1400000
(bootloader) partition-typeplusdycnvbk:raw
(bootloader) partition-sizeplusdycnvbk: 0x1400000
(bootloader) partition-type:ALIGN_TO_128K_2:raw
(bootloader) partition-size:ALIGN_TO_128K_2: 0x1A000
(bootloader) partition-type:apdp_full:raw
(bootloader) partition-size:apdp_full: 0x40000
(bootloader) partition-type:xbl_sc_logs:raw
(bootloader) partition-size:xbl_sc_logs: 0x20000
(bootloader) partition-type:xbl_sc_test_mode:raw
(bootloader) partition-size:xbl_sc_test_mode: 0x10000
(bootloader) partition-type:rtice:raw
(bootloader) partition-size:rtice: 0x80000
(bootloader) partition-type:spunvm:raw
(bootloader) partition-size:spunvm: 0x2000000
(bootloader) partition-type:tzsc:raw
(bootloader) partition-size:tzsc: 0x20000
(bootloader) partition-type:connsec:raw
(bootloader) partition-size:connsec: 0x20000
(bootloader) partition-type:mdcompress:raw
(bootloader) partition-size:mdcompress: 0x1400000
(bootloader) partition-type:vm-data:raw
(bootloader) partition-size:vm-data: 0x20A4000
(bootloader) partition-type:secdata:raw
(bootloader) partition-size:secdata: 0x7000
(bootloader) partition-type:uefivarstore:raw
(bootloader) partition-size:uefivarstore: 0x80000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x20000000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits-cdsp:raw
(bootloader) partition-size:limits-cdsp: 0x1000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:xbl_ramdump_b:raw
(bootloader) partition-size:xbl_ramdump_b: 0x200000
(bootloader) partition-type:splash_b:raw
(bootloader) partition-size:splash_b: 0x20A4000
(bootloader) partition-type:recovery_b:raw
(bootloader) partition-size:recovery_b: 0x6400000
(bootloader) partition-typeplus_sec_b:raw
(bootloader) partition-sizeplus_sec_b: 0xA00000
(bootloader) partition-type:qweslicstore_b:raw
(bootloader) partition-size:qweslicstore_b: 0x40000
(bootloader) partition-type:vendor_boot_b:raw
(bootloader) partition-size:vendor_boot_b: 0xC000000
(bootloader) partition-type:featenabler_b:raw
(bootloader) partition-size:featenabler_b: 0x20000
(bootloader) partition-type:cpucp_b:raw
(bootloader) partition-size:cpucp_b: 0x100000
(bootloader) partition-type:vm-bootsys_b:raw
(bootloader) partition-size:vm-bootsys_b: 0x10625000
(bootloader) partition-type:shrm_b:raw
(bootloader) partition-size:shrm_b: 0x20000
(bootloader) partition-type:imagefv_b:raw
(bootloader) partition-size:imagefv_b: 0x200000
(bootloader) partition-type:uefisecapp_b:raw
(bootloader) partition-size:uefisecapp_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:qupfw_b:raw
(bootloader) partition-size:qupfw_b: 0x14000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x20000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0xC000000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x80000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x4000000
(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: 0x400000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0x12C00000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b: 0x800000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x400000
(bootloader) partition-type:aop_config_b:raw
(bootloader) partition-size:aop_config_b: 0x80000
(bootloader) partition-type:aop_b:raw
(bootloader) partition-size:aop_b: 0x80000
(bootloader) partition-type:uefi_b:raw
(bootloader) partition-size:uefi_b: 0x500000
(bootloader) partition-type:xbl_ramdump_a:raw
(bootloader) partition-size:xbl_ramdump_a: 0x200000
(bootloader) partition-type:splash_a:raw
(bootloader) partition-size:splash_a: 0x20A4000
(bootloader) partition-type:recovery_a:raw
(bootloader) partition-size:recovery_a: 0x6400000
(bootloader) partition-typeplus_sec_a:raw
(bootloader) partition-sizeplus_sec_a: 0xA00000
(bootloader) partition-type:qweslicstore_a:raw
(bootloader) partition-size:qweslicstore_a: 0x40000
(bootloader) partition-type:qmcs:raw
(bootloader) partition-size:qmcs: 0x1E00000
(bootloader) partition-type:vendor_boot_a:raw
(bootloader) partition-size:vendor_boot_a: 0xC000000
(bootloader) partition-type:featenabler_a:raw
(bootloader) partition-size:featenabler_a: 0x20000
(bootloader) partition-type:cpucp_a:raw
(bootloader) partition-size:cpucp_a: 0x100000
(bootloader) partition-type:vm-bootsys_a:raw
(bootloader) partition-size:vm-bootsys_a: 0x10625000
(bootloader) partition-type:shrm_a:raw
(bootloader) partition-size:shrm_a: 0x20000
(bootloader) partition-type:imagefv_a:raw
(bootloader) partition-size:imagefv_a: 0x200000
(bootloader) partition-type:uefisecapp_a:raw
(bootloader) partition-size:uefisecapp_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:qupfw_a:raw
(bootloader) partition-size:qupfw_a: 0x14000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x20000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0xC000000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x80000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x4000000
(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: 0x400000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0x12C00000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a: 0x800000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x400000
(bootloader) partition-type:aop_config_a:raw
(bootloader) partition-size:aop_config_a: 0x80000
(bootloader) partition-type:aop_a:raw
(bootloader) partition-size:aop_a: 0x80000
(bootloader) partition-type:uefi_a:raw
(bootloader) partition-size:uefi_a: 0x500000
(bootloader) partition-type:engineering_cdt_b:raw
(bootloader) partition-size:engineering_cdt_b: 0x100000
(bootloader) partition-type:dinfo:raw
(bootloader) partition-size:dinfo: 0x4000
(bootloader) partition-typecdt:raw
(bootloader) partition-sizecdt: 0x20000
(bootloader) partition-type:engineering_cdt_a:raw
(bootloader) partition-size:engineering_cdt_a: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(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:apdpb:raw
(bootloader) partition-size:apdpb: 0x40000
(bootloader) partition-type:multiimgoem_b:raw
(bootloader) partition-size:multiimgoem_b: 0x8000
(bootloader) partition-type:multiimgqti_b:raw
(bootloader) partition-size:multiimgqti_b: 0x8000
(bootloader) partition-type:xbl_config_b:raw
(bootloader) partition-size:xbl_config_b: 0x35000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b: 0x600000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:multiimgoem_a:raw
(bootloader) partition-size:multiimgoem_a: 0x8000
(bootloader) partition-type:multiimgqti_a:raw
(bootloader) partition-size:multiimgqti_a: 0x8000
(bootloader) partition-type:xbl_config_a:raw
(bootloader) partition-size:xbl_config_a: 0x35000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a: 0x600000
(bootloader) partition-type:userdata:f2fs
(bootloader) partition-size:userdata: 0x37F450F000
(bootloader) partition-type:splash_odm:raw
(bootloader) partition-size:splash_odm: 0x20A4000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x10000000
(bootloader) partition-type:metadata:raw
(bootloader) partition-size:metadata: 0x1000000
(bootloader) partition-type:vbmeta_vendor_b:raw
(bootloader) partition-size:vbmeta_vendor_b: 0x10000
(bootloader) partition-type:vbmeta_vendor_a:raw
(bootloader) partition-size:vbmeta_vendor_a: 0x10000
(bootloader) partition-type:vbmeta_system_b:raw
(bootloader) partition-size:vbmeta_system_b: 0x10000
(bootloader) partition-type:vbmeta_system_a:raw
(bootloader) partition-size:vbmeta_system_a: 0x10000
(bootloader) partition-type:super:raw
(bootloader) partition-size:super: 0x2A0000000
(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:no
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:58e3XXXX
(bootloader) product:taro
(bootloader) snapshot-update-status:none
(bootloader) is-userspace:no
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
Finished. Total time: 0.561s
Click to expand...
Click to collapse
Not sure if useful...