Okay,
So I suspect a few of you are going to want to jump on the NVFlash train that Paul is easing out of the station at the moment. NVFLash is the Nvidia utility for writing to the ROM on your Tegra2 phone, reading details and otherwise critical low level functions. For all intents and purposes this is akin to fastboot for many devices (although not the same as).
Whilst I'm not 100% certain I believe this is the only way to install a custom recovery on your Optimus 2x (when one is released) and therefore, if you hope to install a custom ROM, you will need to get NVFlash up and running.
Below are the simple instructions and links to the necessary files.
** WARNING **
NVFlash is a powerful utility that works at a very low level on your phone. There are few safety mechanisms built into a tool like this because it is intended for use by people with suitable training. NVFlash can not physically damage your phone but it can render it inoperable. It is unlikely to create an irrecoverable situation but it does have the power to create a situation that you can not recover from yourself requiring factory maintenance. Warranty coverage for your phone is not assured after using NVFlash. Please proceed with the use of the tool carefully and at your own risk. Neither myself nor XDA-Developers can be held accountable for any consequences from the use of NVFlash on your phone.
Click to expand...
Click to collapse
Get Software
Grab the NFVlash utility from here: http://djmcnz.batteryboss.org/stuff/NVFlash.zip
Extract the contents of that archive to a single directory
Grab the NVidia boot-recovery driver from here: http://djmcnz.batteryboss.org/stuff/nvmobileboot.rar
Extract the contents of that archive to a different directory
Prepare Phone
Power down phone
Remove battery
Hold VOL_DWN+VOL_UP & plug in USB connection from computer (note, your phone will not visibly respond but it will boot to APX mode quickly)
Open Device Manager in Windows and you should see "APX Device" listed with an error
If not, rinse and repeat
Install Driver
Right click on the APX device
Select 'Update driver software'
Select 'Browse my computer...'
Select 'Let me pick...'
Select 'Have disk'
Browse to directory to extracted the *driver* software to above
Select 'NVIDIA USB Boot-recovery driver for mobile devices'
Accept any warnings, including the big red alert (you may need to disable UAC)
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'
If not, uninstall the driver, reboot rinse and repeat
Testing
Navigate the the directory you extracted the NVFlash archive to
Run a harmless command such as "nvflash --sync"
You should get something back like:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x0280404444803457
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
If so, you're good to go, now just be patient...
Helped you? Hit 'Thanks' below...
thx for the info
Sent from my LG-P990 using Tapatalk
WOW great so fast already !!!
Thanks m8, now just waiting for interesting Roms
I got rcm version 0x4
then device disapear from list. What It's means?
Can some one explain the testing part how to I navigate and enter command
EDITED: What am I doing wrong
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x0428000543a15057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
command failure: no bootloader was specified
It says that you didn't specify/ provide bootloader.bin file in the command line. Find nvflash ROMs thread and compare the command lines.
This nvflash dotn work on win7 64bit..any solution?
ravenoss said:
This nvflash dotn work on win7 64bit..any solution?
Click to expand...
Click to collapse
Yes it does, used it on saturday on a win7 64bit computer.
Only difference is that i followed this guid:
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
It works with Win7 64 bit. I'm using it.:good:
-
-
WORKING IN ALL VARIANT NOTE 5
-
-
Flashing your smartphone via Odin ,
But ODIN could Not recognize the phone and the blue box doesnt appear
-
-
-
Unlock the boot loader you need to have the ADT with all the packages installed and configured.
Later once the configuration is done properly then you can connect your device and enable USB Debugging under the options.
Download Modaco’s Superboot files and save them to your computer.
Once downloaded, extract it by right clicking and extract all.
On your phone, click on Settings > Developer Options > Turn USB Debugging On.
Plug the device in to your computer via USB cable.
Open the superboot folder that we just extracted (until you see the folder with fastboot-windows inside it), then hold the shift key down on your computer and right click any blank area.
Now, select open command window here.
In the command prompt, type the following with hitting enter at the end of each line.
-
-
Copy and page in cmd:
adb-windows reboot bootloader
fastboot-windows oem unlock and wait for the device to reboot (no necesary)
In case you phone not restart : reboot....
Then you turn on the phone
Then you power off on the phone
Then install your current firmware: .md5
optional: Galaxy Note Series Firmware
and enjoy
LINK : https://mega.nz/#F!iIE0yYqQ!2nskXbsvwWMn1OBM1LXm8A
-
-
VIDEO TUTORIAL
-
-
Credits: @Adil_mac
wow thanks ... is this means I can downgrade to 5.1.1 ?
when i type in cmd adb-windows reboot bootloader the phone reboots on normal user
and the tut video not available can u make one please
Vídeo not reproducing.
{
"cpn": "eqo_KnbfUuNy8rKd",
"vct": "0.000",
"vd": "NaN",
"vpl": "",
"vbu": "",
"vpa": true,
"vsk": false,
"ven": false,
"vpr": 1,
"vrs": 0,
"vns": 0,
"vec": null,
"vvol": 1,
"state": "80",
"debug_error": {
"errorCode": "api.invalidparam",
"errorDetail": "invalidVideodata.1",
"message": "Se produjo un error. Vuelve a intentarlo más tarde.",
"messageKey": "YTP_ERROR_GENERIC_WITHOUT_LINK"
},
"relative_loudness": "0.000",
"0sz": false,
"op": "",
"yof": false,
"dis": "",
"gpu": "Mali-T760",
"cgr": true,
"debug_playbackQuality": "unknown",
"debug_date": "Mon Apr 03 2017 20:11:07 GMT-0600 (CST)"
}
Link is broken
[WIP]Dissecting the bootloader aka: get rid of annoying "Your device is corrupt"
This is WIP (work in progress) ... posting this as a separate thread to get other people involved so we can try to get rid of the annoying "Your device is corrupt" thing.
On the back of my thread on the splash screen (see https://forum.xda-developers.com/oneplus-6t/development/tool-splash-screen-modification-t3874158), @AnoopKumar and I started checking the bootloader.
The bootloader is in the partition called: abl_a (and/or abl_b) depending on whether you boot from A or B slot.
(https://forum.xda-developers.com/showpost.php?p=78409574&postcount=28)
All below is on Linux ... I am not a Windows guru ...
Take a raw dump of the abl_a partition. Reboot into TWRP, once there do: "adb shell".
Code:
> adb shell
# dd if=/dev/block/bootdevice/by-name/abl_b of=/sdcard/img.abl_a
# <ctrl-D>
> adb pull /sdcard/img.abl_a
You will now have the dump of the bootloader partition in the file
Then, use "binwalk" to see what is inside the abl_a image:
Code:
> binwalk -e img.abl_a
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 ELF, 32-bit LSB executable, ARM, version 1 (SYSV)
4488 0x1188 Certificate in DER format (x509 v3), header length: 4, sequence length: 1279
5771 0x168B Certificate in DER format (x509 v3), header length: 4, sequence length: 1133
6908 0x1AFC Certificate in DER format (x509 v3), header length: 4, sequence length: 1149
12408 0x3078 LZMA compressed data, properties: 0x5D, dictionary size: 16777216 bytes, uncompressed size: 487624 bytes
I am thinking that bytes 0...4487 is the real bootloader code, so:
Code:
> head --bytes=4488 img.abl_b > abc
> file abc
abc: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, corrupted section header size
Not sure why it says "corrupt section header size".
Then check the detail of the ELF file:
Code:
> readelf abc
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: EXEC (Executable file)
Machine: ARM
Version: 0x1
Entry point address: 0x9fa00000
Start of program headers: 52 (bytes into file)
Start of section headers: 0 (bytes into file)
Flags: 0x0
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 3
Size of section headers: 0 (bytes)
Number of section headers: 0
Section header string table index: 0
There are no sections in this file.
There are no sections to group in this file.
Program Headers:
Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
NULL 0x000000 0x00000000 0x00000000 0x00094 0x00000 0
NULL 0x001000 0x9fa30000 0x9fa30000 0x01988 0x02000 0x1000
LOAD 0x003000 0x9fa00000 0x9fa00000 0x30000 0x30000 RWE 0x1000
There is no dynamic section in this file.
There are no relocations in this file.
Dynamic symbol information is not available for displaying symbols.
No version information found in this file.
Elf file type is EXEC (Executable file)
Entry point 0x9fa00000
There are 3 program headers, starting at offset 52
The bootloader binary code is in the LOAD segment
More to follow later ... have to catch some sleep now ...
foobar66 said:
This is WIP (work in progress) ... posting this as a separate thread to get other people involved so we can try to get rid of the annoying "Your device is corrupt" thing.
On the back of my thread on the splash screen (see https://forum.xda-developers.com/oneplus-6t/development/tool-splash-screen-modification-t3874158), @AnoopKumar and I started checking the bootloader.
The bootloader is in the partition called: abl_a (and/or abl_b) depending on whether you boot from A or B slot.
(https://forum.xda-developers.com/showpost.php?p=78409574&postcount=28)
All below is on Linux ... I am not a Windows guru ...
Take a raw dump of the abl_a partition. Reboot into TWRP, once there do: "adb shell".
You will now have the dump of the bootloader partition in the file
Then, use "binwalk" to see what is inside the abl_a image:
I am thinking that bytes 0...4487 is the real bootloader code, so:
Not sure why it says "corrupt section header size".
Then check the detail of the ELF file:
The bootloader binary code is in the LOAD segment
More to follow later ... have to catch some sleep now ...
Click to expand...
Click to collapse
Wow! Excited to see this! Thanks
It doesn't matter if you find it.
I don't think you can flash a modified BL partition and have the device boot.
This is part of secure boot. The notice will always be there with an unlocked BL.
It's on all devices that have ARM trust zone and secure boot, if they run Android.
This is part of Google's requirements.
foobar66 said:
This is WIP (work in progress) ... posting this as a separate thread to get other people involved so we can try to get rid of the annoying "Your device is corrupt" thing.
On the back of my thread on the splash screen (see https://forum.xda-developers.com/oneplus-6t/development/tool-splash-screen-modification-t3874158), @AnoopKumar and I started checking the bootloader.
The bootloader is in the partition called: abl_a (and/or abl_b) depending on whether you boot from A or B slot.
(https://forum.xda-developers.com/showpost.php?p=78409574&postcount=28)
All below is on Linux ... I am not a Windows guru ...
Take a raw dump of the abl_a partition. Reboot into TWRP, once there do: "adb shell".
Code:
> adb shell
# dd if=/dev/block/bootdevice/by-name/abl_b of=/sdcard/img.abl_a
# <ctrl-D>
> adb pull /sdcard/img.abl_a
You will now have the dump of the bootloader partition in the file
Then, use "binwalk" to see what is inside the abl_a image:
Code:
> binwalk -e img.abl_a
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 ELF, 32-bit LSB executable, ARM, version 1 (SYSV)
4488 0x1188 Certificate in DER format (x509 v3), header length: 4, sequence length: 1279
5771 0x168B Certificate in DER format (x509 v3), header length: 4, sequence length: 1133
6908 0x1AFC Certificate in DER format (x509 v3), header length: 4, sequence length: 1149
12408 0x3078 LZMA compressed data, properties: 0x5D, dictionary size: 16777216 bytes, uncompressed size: 487624 bytes
I am thinking that bytes 0...4487 is the real bootloader code, so:
Code:
> head --bytes=4488 img.abl_b > abc
> file abc
abc: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, corrupted section header size
Not sure why it says "corrupt section header size".
Then check the detail of the ELF file:
Code:
> readelf abc
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: EXEC (Executable file)
Machine: ARM
Version: 0x1
Entry point address: 0x9fa00000
Start of program headers: 52 (bytes into file)
Start of section headers: 0 (bytes into file)
Flags: 0x0
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 3
Size of section headers: 0 (bytes)
Number of section headers: 0
Section header string table index: 0
There are no sections in this file.
There are no sections to group in this file.
Program Headers:
Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
NULL 0x000000 0x00000000 0x00000000 0x00094 0x00000 0
NULL 0x001000 0x9fa30000 0x9fa30000 0x01988 0x02000 0x1000
LOAD 0x003000 0x9fa00000 0x9fa00000 0x30000 0x30000 RWE 0x1000
There is no dynamic section in this file.
There are no relocations in this file.
Dynamic symbol information is not available for displaying symbols.
No version information found in this file.
Elf file type is EXEC (Executable file)
Entry point 0x9fa00000
There are 3 program headers, starting at offset 52
The bootloader binary code is in the LOAD segment
More to follow later ... have to catch some sleep now ...
Click to expand...
Click to collapse
Good job, if needed i can help with the checking
tech_head said:
It doesn't matter if you find it.
I don't think you can flash a modified BL partition and have the device boot.
This is part of secure boot. The notice will always be there with an unlocked BL.
It's on all devices that have ARM trust zone and secure boot, if they run Android.
This is part of Google's requirements.
Click to expand...
Click to collapse
abl.img is not the bootloader i guess.
tech_head said:
It doesn't matter if you find it.
I don't think you can flash a modified BL partition and have the device boot.
This is part of secure boot. The notice will always be there with an unlocked BL.
It's on all devices that have ARM trust zone and secure boot, if they run Android.
This is part of Google's requirements.
Click to expand...
Click to collapse
On other devices they've been able to swap this image with another one to "hide" the message, to "get rid of it".
Would we sweet if we could get rid of the unlocked bootloader message too.
dennisbednarz said:
Would we sweet if we could get rid of the unlocked bootloader message too.
Click to expand...
Click to collapse
+1
U guys should talk [email protected] We had this issue of broken verity with the essential phone and he came up with a redboot.img that u flash and it bootloops the phone and fixes verity. It keeps bootlooping till.it fixes it, then u flash a proper kernel and you are good. Cuz as It stands one can only resolve this properly with the tool
jacksummers said:
U guys should talk [email protected] We had this issue of broken verity with the essential phone and he came up with a redboot.img that u flash and it bootloops the phone and fixes verity. It keeps bootlooping till.it fixes it, then u flash a proper kernel and you are good. Cuz as It stands one can only resolve this properly with the tool
Click to expand...
Click to collapse
Different issue.
They are not trying to get rid of the red warning but the yellow warning for an unlocked BL.
On this phone, if you have a "red" warning you use the MSMDownload tool and go back factory including locking the BL.
This is a different case.
Well ... bad luck ... I tried to change abl_b and reflash it ... phone is sort of *dead* now.
Does no longer boot at all.
However, when I plug it into the PC, I can see:
Code:
> lsusb
Bus 001 Device 034: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
And then:
Code:
> dmesg
[ 9395.999112] usb 1-1: new high-speed USB device number 34 using xhci_hcd
[ 9396.149376] usb 1-1: New USB device found, idVendor=05c6, idProduct=9008
[ 9396.149380] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9396.149383] usb 1-1: Product: QUSB_BULK_CID:0402_SN:33B9DDAC
[ 9396.149386] usb 1-1: Manufacturer: Qualcomm CDMA Technologies MSM
[ 9396.150184] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[ 9396.150372] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
So it is not completely *dead* but in some sort of Qualcomm low level mode. I found some info here: https://together.jolla.com/question...ss-modem-any-chance-to-bring-it-back-to-life/ but did not make any progress yet.
EDIT: looking at MsmDownloadTool to debrick the phone ...
foobar66 said:
Well ... bad luck ... I tried to change abl_b and reflash it ... phone is sort of *dead* now.
Does no longer boot at all.
However, when I plug it into the PC, I can see:
Code:
> lsusb
Bus 001 Device 034: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
And then:
Code:
> dmesg
[ 9395.999112] usb 1-1: new high-speed USB device number 34 using xhci_hcd
[ 9396.149376] usb 1-1: New USB device found, idVendor=05c6, idProduct=9008
[ 9396.149380] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9396.149383] usb 1-1: Product: QUSB_BULK_CID:0402_SN:33B9DDAC
[ 9396.149386] usb 1-1: Manufacturer: Qualcomm CDMA Technologies MSM
[ 9396.150184] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[ 9396.150372] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
So it is not completely *dead* but in some sort of Qualcomm low level mode. I found some info here: https://together.jolla.com/question...ss-modem-any-chance-to-bring-it-back-to-life/ but did not make any progress yet.
EDIT: looking at MsmDownloadTool to debrick the phone ...
Click to expand...
Click to collapse
Use this https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Should try for several times with instruction here
Question - when does device show red warning? When u disable dm verity?
I unlocked and rooted but only had yellow warning, but when i installed aosp gsi i had a red warning. Once of the step to install the rom was flashing vbmeta and disabling dm verity.
patelparth120595 said:
Question - when does device show red warning? When u disable dm verity?
I unlocked and rooted but only had yellow warning, but when i installed aosp gsi i had a red warning. Once of the step to install the rom was flashing vbmeta and disabling dm verity.
Click to expand...
Click to collapse
Disabled dm-verity caused red warning, i guess.
---------- Post added at 10:01 AM ---------- Previous post was at 09:58 AM ----------
foobar66 said:
Well ... bad luck ... I tried to change abl_b and reflash it ... phone is sort of *dead* now.
Does no longer boot at all.
However, when I plug it into the PC, I can see:
And then:
So it is not completely *dead* but in some sort of Qualcomm low level mode. I found some info here: https://together.jolla.com/question...ss-modem-any-chance-to-bring-it-back-to-life/ but did not make any progress yet.
EDIT: looking at MsmDownloadTool to debrick the phone ...
Click to expand...
Click to collapse
Edited abl.img ? and flashed via recovery/fastboot ?
AnoopKumar said:
Edited abl.img ? and flashed via recovery/fastboot ?
Click to expand...
Click to collapse
No, just flashed using dd command in TWRP shell.
foobar66 said:
No, just flashed using dd command in TWRP shell.
Click to expand...
Click to collapse
Phone still dead ?
OK ... I managed to recover my phone !
A windows PC with the MSM program did the trick.
I am now back to stock 9.0.5
foobar66 said:
OK ... I managed to recover my phone !
A windows PC with the MSM program did the trick.
I am now back to stock 9.0.5
Click to expand...
Click to collapse
I assume that, there is nothing to do with the abl.img. Only thing we can do with it is change the default strings to a song lyric or something. abl.img is the uefi firmware i guess. Bootloader is using the images stored in the logo partition.
Gsi's flash without breaking verity if u flash to both slots. And totally format. Fastboot -w. The phone sees any changes to partitions as corruption and breaks verity, hence red warning.. if someone would be inclined to talk to invisiblek from the essential threads, he could tell u of a fix. The solution is not in abl. It's in the stock boot.img. if I had more time, I would help
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
tech_head said:
Different issue.
They are not trying to get rid of the red warning but the yellow warning for an unlocked BL.
On this phone, if you have a "red" warning you use the MSMDownload tool and go back factory including locking the BL.
This is a different case.
Click to expand...
Click to collapse
No, they are talking about breaking verity also. Seems to be both messages, but more recently the broken verity message. Which there is two types, one u can boot from, one u cannot.
jacksummers said:
U guys should talk [email protected] We had this issue of broken verity with the essential phone and he came up with a redboot.img that u flash and it bootloops the phone and fixes verity. It keeps bootlooping till.it fixes it, then u flash a proper kernel and you are good. Cuz as It stands one can only resolve this properly with the tool
Click to expand...
Click to collapse
I would love that idea. That would be really nice to have on our device
Hello i have problem with the mi9 of my friend
her phone seems to be block in boot process...we can see the Mi logo and the android power up with 3 points moving like if it is starting but nothing happens...
we let it starting for one complete night nothing has changed.
I can access to recovery mode pushing volume up + start button...i could do swap data but she doesn't want to loose some phone call records cause their is the voice of her last chat with her mum passed away some months ago...
for now what i know :
- her phone doesn't have the usb debugging options activated ;(
- when i connect the phone to my pc it doesn't recognized and appears on my pc
- i tried the miassitsant option in the recovery mode but mipcsuite doesn't see it too...
- not sure a mi account was created on her phone...she said she think we did one but the infos( id andpass was kept on a sms on her phone LOL)
so for now the only thing i see is that, in adb, when i typed .\adb devices i can see a number with "sideload" written beside it....does it help to find a way to modify the boot.img for an update or to transferts files from the phone to my pc?
question more : what is the path for phone calls recorded in a MI9? maybe i could use a push or pull option in adb?
i thought aboput contacting xiaomi for unlock the phone but as it seems to be blocked in boot mode i don't now if it would change something
i hope you understood well my poor english
please help ...
If it can help here is what i have when i used the miflash program
""""""""""""""""""""""""""""""""""""""
AGMService.exe AGSService.exe Adobe CEF Helper.exe Adobe Desktop Service.exe AdobeIPCBroker.exe AdobeUpdateService.exe ApplicationFrameHost.exe AudialsNotifier.exe BdVpnService.exe CCXProcess.exe CCleaner64.exe CCleanerBrowserCrashHandler.exe CCleanerBrowserCrashHandler64.exe Calculator.exe CefSharp.BrowserSubprocess.exe Creative Cloud.exe Dashboard.Service.exe Dashboard.exe DiscoverySrv.exe EpicGamesLauncher.exe EpicWebHelper.exe HPPrintScanDoctorService.exe LockApp.exe Memory Compression MiPhoneHelper.exe MoUsoCoreWorker.exe Music.UI.exe NVDisplay.Container.exe OfficeClickToRun.exe OneDrive.exe ProductAgentService.exe Registry RtkNGUI64.exe RuntimeBroker.exe ScanToPCActivationApp.exe Scheduler.exe ScpService.exe ScpTrayApp.exe SearchApp.exe SearchFilterHost.exe SearchIndexer.exe SearchProtocolHost.exe SecurityHealthService.exe SecurityHealthSystray.exe SettingSyncHost.exe SgrmBroker.exe ShellExperienceHost.exe StartMenuExperienceHost.exe SwUSB.exe System SystemSettings.exe TextInputHost.exe UserOOBEBroker.exe Video.UI.exe WUDFHost.exe WmiPrvSE.exe YourPhone.exe [System Process] adb.exe armsvc.exe audiodg.exe bdagent.exe bdntwrk.exe bdredline.exe bdservicehost.exe bdvpnapp.exe conhost.exe csrss.exe ctfmon.exe dasHost.exe dllhost.exe dwm.exe ensserver.exe explorer.exe fontdrvhost.exe lsass.exe lync.exe miflash_unlock.exe node.exe runSW.exe services.exe sihost.exe smartscreen.exe smss.exe spoolsv.exe svchost.exe taskhostw.exe unsecapp.exe updatesrv.exe wininit.exe winlogon.exe
DEBUG <10:37:18.136,T:16292> : miflash_unlock start
DEBUG <10:37:18.684,T:13176> : auto refresh device list
DEBUG <10:37:18.699,T:13176> : use bus desp:MI 9 instead of Android ADB Interface
DEBUG <10:37:18.715,T:13176> : new usb\vid_18d1&pid_4e11\d9995836
INFO <10:37:18.715,T:13176> : fastboot devices
WARNING<10:37:24.212,T:16292> : account loading error:-21
DEBUG <10:37:24.946,T:16292> : [0]End: data:text/html,chromewebdata
DEBUG <10:37:25.261,T:13176> : auto refresh device list
DEBUG <10:37:25.268,T:13176> : use bus desp:MI 9 instead of Android ADB Interface
INFO <10:37:25.272,T:13176> : fastboot devices
ERROR <10:37:31.387,T:13168> : http get error code[curl]:6
INFO <10:37:48.319,T:1116> : new app version:6.5.406.31 url:http://miuirom.xiaomi.com/rom/u1106245679/6.5.406.31/miflash_unlock-en-6.5.406.31.zip
DEBUG <10:37:50.540,T:13176> : auto refresh device list
DEBUG <10:37:50.556,T:13176> : use desp:Android Bootloader Interface instead of Android
DEBUG <10:37:50.571,T:13176> : remove usb\vid_18d1&pid_4e11\d9995836
DEBUG <10:37:50.571,T:13176> : new usb\vid_18d1&pid_d00d\d9995836
INFO <10:37:50.571,T:13176> : fastboot devices
DEBUG <10:37:50.656,T:15372> : -s d9995836 oem device-info
DEBUG <10:37:50.756,T:15372> : ...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
DEBUG <10:37:50.756,T:15372> : getvar product -s d9995836
DEBUG <10:37:50.841,T:15372> : product: cepheus
finished. total time: 0.000s
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""
i tried to download files from devices but not sure of the path where the voice records are saved :
adb pull [-l] /internal share storage/MIUI/sound_recorder/call_rec/
adb pull [-l] /MIUI/sound_recorder/call_rec/
is the path correct?