Hi, I've been a lurker here for quite some time but this is my first post.
I just tried to upgrade my Verizon XV6700 from AKU2.2 to AKU3.3 using the RUU I downloaded from the pcdphones.com web site (APA_Verizon_31430_314208_14300_WWE_Ship_2.exe). The RUU correctly identified my current radio, CE and Extended firmware versions but failed during the upgrade with error 116 (General Error). Doing a hard reset on the phone brings up the reset screen but after clearing the memory the phone just displays a blank screen. I can manually get into the bootloader (USB v2.05) and I tried re-running the AKU3.3 RUU again but now it says that my model ID is incorrect. I also tried running the AKU2.2 RUU (APA_VZW_20720_206_11000_WWE_Ship.exe) to get back to my original state but it doesn't work either (Error 101 Connection Error).
I downloaded Newbootloader_RUU and tried copying the 3 .nbf files for AKU3.3 into the directory and it seems to upgrade but it only runs for a short time (less than a minute) before saying the upgrade is complete and after doing a hard reset I still get a blank screen. I suspect that the ROM was not actually upgraded.
I downloaded mtty1.43 and I can get to a USB> prompt and have tried a few of the suggestions I found on the forums here but none have helped. I suspect that the model ID and possibly other information may have been corrupted by my first upgrade attempt. Here's some of the info I've recorded:
USB>info 1
2.05
USB>info 2
VZW__001 9ÿmïHTCE
USB>info 3
PA10A1ä TÝHTCE
USB>info 4
[email protected]ๆHTCE
USB>info 5
USB>info 6
T ÚÈÒHTCE
USB>info 7
HTC Integrated Re-Flash Utility for bootloader Version : 1.50a, APACHE HW Version : 2.05
Built at: Sep 18 2007 21:54:57
Copyright (c) 1998-2005 High Tech Computer Corporation
Turbo = 312 MHz, Run = 208 Mhz
Memory Frequency = 208 MHz
SDRAM Frequency = 104 MHz
Board ID is 2, Display is 0 (0=Ty,1=Sg)
USB>info 8
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2840000
All Size: 0x7340000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000
USB>info 9
USB>
Before I attempted the upgrade I recorded some information from the phone. I don't know how useful it might be but here it is:
Verizon XV6700 Startup Splash Screen:
H/W = 2
M = 12
U = 4
P SNAZ-40306
R 1.10.00
D 2.07.20 WWE
Device Information, Version:
ROM version 2.07.20 WWE
ROM date 02/24/06
Radio version 1.10.00
Protocol version SNAZ-40306
ExtROM version 2.07.200 WWE
Hardware version 0041
PRL version 51344
PRI version 1.14_002
Browser version MSIE 4.01
ESN 3674D2B4
Device Information, Hardware:
CPU Intel(R) PXA270
Speed 416 MHz
RAM size 64 MB
Flash size 128 MB
Flash chip type M-Systems
Data bus 32 bits
Storage size 39.59 MB
LCD 240 x 320 TFT
Colors 65536
Device Information, Identity:
Model No. PA10A1
Platform PocketPC
About, Version:
Microsoft Windows Mobile Version 5.0
OS 5.1.195 (Build 14928.2.2.0)
Processor: PXA270-416MHz
Memory: 49.23 MB
At this point I would welcome any suggestions. I've searched through the forums here but I haven't come up with anything else to try.
Thanks for your help.
Hi Everyone,
At the moment, I cannot get my LG G2X to boot into Cyanogen Mod. I cannot get it to boot into recovery mode. I cannot get it to do anything but sit at the second LG logo. This is a problem.
If I allow it to boot with no special button-pressing, it will get to the second LG logo, and stall there until the battery runs out. If I hold the VOLUME DOWN and POWER buttons, it will get as far as the first (white) LG logo and stall there (holding VOLUME DOWN and POWER for a full 60 seconds).
History:
A few weeks ago, I had flashed my G2X and installed CyanogenMod 7 (specifically 7.2.0) from here: http://download.cyanogenmod.com/?type=stable&device=p999. I accomplished this through the excellent One-Click NvFlasher ClockWorkMod provided by TGA_Gunnman (found here: http://forum.xda-developers.com/showthread.php?t=1056847). Once in a while, I would have to clear the caches after a reboot, but that was my biggest problem, and one I was prepared to live with. Until now.
Things I've tried:
Most fixes start with reflashing CWM. I did that, using the aforementioned One-Click NvFlasher ClockWorkMod tool. It stalls as follows:
Code:
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c20824360c4d7
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
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
- 65536/3563520 bytes sent
-------------------------------------------------------------------------------------
...and won't do anything else.
So, for whatever reasons, it will not send CWM-5020.img. To check, I tried nvflash.exe directly. Same general result. I tried with a different file (recovery-clockwork-5.0.2.0-p999.img), same result. I also tried the advice here: http://forum.xda-developers.com/showthread.php?t=1590523&highlight=bricked+help and tried to wipe out my partitions. While that tool runs successfully, it does not change the results with One-Click NvFlasher ClockWorkMod
Summary:
Can't boot. Can't boot into recovery. Can't flash the ROM.
Any ideas? Anyone?
Thanks!
I forgot to add: when I unplug from the one-click updater, I get the following error message:
Code:
sending file: CWM-5020.img
- 65536/3563520 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
===============================================================
===============================================================
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
For when my partitions are messed up
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using Tapatalk 2
djvoleur said:
For when my partitions are messed up
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, djvoleur, but when I try that, I get this:
Code:
.\nvflash.exe
--bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --setbct --odm
data 0xC8000 --configfile android_fastboot_emmc_full.cfg --create --bl fastboot.
bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c20824360c4d7
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
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
\ 888548/888548 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: UDA
creating partition: EB4
creating partition: UDB
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x42008 (0x19042008) flags: 0
So it seems that this doesn't help. I scanned through the thread and didn't see anything that seemed like it might address this issue.
It may be driver related. Reinstall drivers then follow the instructions to resurrect your phone.
Core Memory said:
It may be driver related. Reinstall drivers then follow the instructions to resurrect your phone.
Click to expand...
Click to collapse
Would you recommend reinstalling both the LG USB drivers and the ATX drivers for nVidia? (I'm probably going to do both anyway.)
I've forced a reinstall of the NVIDIA USB Boot-recovery driver, using the same files included in the one-click recovery tool. After that, I attempted to run the tool and had the same failure listed above (command failure: partition download failed). For laughs, I tried djvoleur's solution as well, and got the same error again. So it doesn't seem to be a driver issue.
When you do the NVFlash recovery, did you take out the battery, hold the up and down volume buttons in, while holding the buttons in plug in the usb cable, while holding the buttons in run the recovery until it is completed.
Just for ****s, try flashing twrp. I also have another idea, but I can't get it set-up tonight.
Sent from my LG-P999 using xda premium
Core Memory said:
When you do the NVFlash recovery, did you take out the battery, hold the up and down volume buttons in, while holding the buttons in plug in the usb cable, while holding the buttons in run the recovery until it is completed.
Click to expand...
Click to collapse
Yes. The battery was out the whole time. Held the buttons down, plugged in the USB cable, ran recovery, recovery stalls at 65536 bytes. Held it for about five minutes, just to make sure.
Волк said:
Just for ****s, try flashing twrp. I also have another idea, but I can't get it set-up tonight.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Same result as each of the others: stalls at 65536 bytes sent. I don't think it's an issue with any of the actual recovery mods, at this point. I think it's something wrong with getting data onto my phone, perhaps?
How about trying to update the phone with one of the KDZ updates? Use Emergency mode. There's an offline updater which uses an http server to fool the LG updater into not accessing the LG update website then doing the update. It runs with a VB script which does everything. I once used that with the V21Y_00.kdz file when my phone wouldn't restore.
http://forum.xda-developers.com/showthread.php?t=1601918
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
Core Memory said:
How about trying to update the phone with one of the KDZ updates? Use Emergency mode. There's an offline updater which uses an http server to fool the LG updater into not accessing the LG update website then doing the update. It runs with a VB script which does everything. I once used that with the V21Y_00.kdz file when my phone wouldn't restore.
http://forum.xda-developers.com/showthread.php?t=1601918
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
Click to expand...
Click to collapse
Tried this. First tried the second link (the all in one with the offline web server). That didn't work because the zipfile with the webserver and other software had a virus which specifically infected the web server.
Followed the directions in the first post, then. These seem to presume that you can get to USB debugging mode (which I can't, because the phone won't boot). Got as far as Step 3 in that post. When I click on "Upgrade Start" I should get a pop-up for "Select Country & Language". I do not. Instead, it starts the LG Mobile Support Tool directly. (I should mention at this point that I'm on WIndows 7, if it matters). The updater checks the connection with the phone, and finds an acceptable connection. Since it was supposed to go into the Updater anyway, I hit "Start Updating". After a while, this fails with some sort of connection problem with the phone. I've tried re-running the LG Updater under several conditions (in Upgrade mode, not in Upgrade mode, etc.). No luck.
Doesn't seem like this is a solution I can get to work. Should I try something else?
The virus warning is false. Disconnect from the internet and/or turn off your wireless connection then run it. Also, if it stalls, let it wait.
If it doesn't continue within 10 minutes, try it again.
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
Also, I made sure that all of the applications in the substitute web-server update package were allowed to run as administrator before I ran the script. If that doesn't work, try running the apps individually without the script in the order they're required to be initiated which is in the instructions that come with that package.
Core Memory said:
The virus warning is false. Disconnect from the internet and/or turn off your wireless connection then run it. Also, if it stalls, let it wait.
If it doesn't continue within 10 minutes, try it again.
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
Also, I made sure that all of the applications in the substitute web-server update package were allowed to run as administrator before I ran the script. If that doesn't work, try running the apps individually without the script in the order they're required to be initiated which is in the instructions that come with that package.
Click to expand...
Click to collapse
I'm having exactly the same problem as that person right now. Using the offline update, I got up to "Normal MTK Upgrade start" but then the program crashed right afterwards. It also doesn't help that the phone keeps on rebooting. For the online update, I can get up to 32% before the phone reboots and I have to restart the update process.
mbamg said:
I'm having exactly the same problem as that person right now. Using the offline update, I got up to "Normal MTK Upgrade start" but then the program crashed right afterwards. It also doesn't help that the phone keeps on rebooting. For the online update, I can get up to 32% before the phone reboots and I have to restart the update process.
Click to expand...
Click to collapse
If it got to 32%, it has installed the baseband, that gets installed first then the Android. Try doing a restore/recovery of just Android that's compatible with the baseband.
Have you tried running the flash with the battery in? I know all the instructions say take the battery out, but im having similar issues with my phone, and once the phone is recognized in Device manager in APX mode, insert the battery, then run the flash. That seemed to work for me.
Core Memory said:
How about trying to update the phone with one of the KDZ updates? Use Emergency mode. There's an offline updater which uses an http server to fool the LG updater into not accessing the LG update website then doing the update. It runs with a VB script which does everything. I once used that with the V21Y_00.kdz file when my phone wouldn't restore.
http://forum.xda-developers.com/showthread.php?t=1601918
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
Click to expand...
Click to collapse
Nothing will work in this Case i try all most everything. I thnk 99% Partition or Flash Chip is Damaged
See Reports:
While try with KDZ File
Trying to Flash Recovery
Code:
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208240ff9497
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
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
- 65536/3563520 bytes sent
Recovery Stock
Code:
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208240ff9497
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
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
- 65536/3563520 bytes sent
Phone Information
Code:
Nvflash started
rcm version 0X20001
System Information:
[COLOR="Red"] [B]chip name: unknown[/B][/COLOR]
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208240ff9497
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
Rad Flash
Code:
[R&D Test Tools Log File]
00:54:52 : Start fn_StartUpgrade
00:54:52 : Extract kdz file
00:55:01 : kdz decrypt Success
00:55:05 : Extract file Success.
00:55:05 : LGMobileDL Load.
00:55:05 : Port = -1
00:55:05 : Connection check start.
00:55:05 : Port(or Device) Not Found!
00:55:07 : Finish All test
So to Flash with KDZ ect u need phone on Recovery mode and phone will not steep into recovery mode with vol - + Power
All we have is boot Recovery mode and phone hang on SW Upgrade Please Wait
I Try to Format partition manually via NVFlash but same thing its hang
Best Regards from me i am giving up after 2 days working on it, For me its simply Hardware Problem
In my experience when that happened to me.... It was my firewall/virus scanner. Try disabling those before attempting another flash.
Hello i have A8 2018 sm-a530f which has the emmc files corrupted , i need to revive and when i connect to the Easy Jtag Plus i get the error Partition info not found ,guide repair procedures and below is the log data
Setting interface to EasyJtag2/ISP
Setting bus width to 1 Bit
Setting frequence to 36 MHz
CMD Pullup Level: 445 mV
CMD Active Level: 1192 mV
EMMC Device Information :
EMMC CID: 150100424A5444345200523F424BB5A7
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: BJTD4R , HEX: 424A544434xx , S/N: 523F42xx , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2018
EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 0 , Response: Maybe not clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x01 , width 4bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: BJTD4R_523F424B_20210404_201644.extcsd
EMMC Init completed.
Scanning soft partitions
Partition table not found
Get firmware version
Firmware info not found
NOTE: I HAVE THE BACK UP FILE BUT I DO NOT KNOW WHICH FILES TO LOAD , MAY SOMEONE CHECK THE ATTACHMENT AND TELL ME WHICH FILES TO LOAD LIKE (Select eMMC Image file *.bin) from THIS BACK UP.MAY SOMEONE TELL ME FROM THE BACK UP WHICH ONE IS ( eMMC ROM1 Image file, eMMC ROM2 Image file, eMMC ROM3 Image file, eMMC GP1 Image file, eMMC ExtCSD file. IN THEIR ORDER.
gruka said:
Hello i have A8 2018 sm-a530f which has the emmc files corrupted , i need to revive and when i connect to the Easy Jtag Plus i get the error Partition info not found ,guide repair procedures and below is the log data
Setting interface to EasyJtag2/ISP
Setting bus width to 1 Bit
Setting frequence to 36 MHz
CMD Pullup Level: 445 mV
CMD Active Level: 1192 mV
EMMC Device Information :
EMMC CID: 150100424A5444345200523F424BB5A7
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: BJTD4R , HEX: 424A544434xx , S/N: 523F42xx , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2018
EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 0 , Response: Maybe not clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x01 , width 4bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: BJTD4R_523F424B_20210404_201644.extcsd
EMMC Init completed.
Scanning soft partitions
Partition table not found
Get firmware version
Firmware info not found
NOTE: I HAVE THE BACK UP FILE BUT I DO NOT KNOW WHICH FILES TO LOAD , MAY SOMEONE CHECK THE ATTACHMENT AND TELL ME WHICH FILES TO LOAD LIKE (Select eMMC Image file *.bin) from THIS BACK UP.MAY SOMEONE TELL ME FROM THE BACK UP WHICH ONE IS ( eMMC ROM1 Image file, eMMC ROM2 Image file, eMMC ROM3 Image file, eMMC GP1 Image file, eMMC ExtCSD file. IN THEIR ORDER.
Click to expand...
Click to collapse
I think there are not many users who are able to help in your case.
I only found this thread about emmc repair for your device:
Samsung A520f ,A530f Dead boot repair direct emmc file download
gsm flash,gsm flash file,gsm crack,combine file,easy firmware,frp file,gsm firmware,gsm file,samsung firmware,samsung dump,all android flashing tool,
www.awaismobile.com
Yes i downloaded the file ,how do i know this file is rom 1 ,Rom2,Rom 3, and ex PLEASE I DENTIFY FOR ME
hey guys..
i have a module which called bus multimedia.. i need root or read full backup of this device.. but there is no usb socket only exist RX TX pinout and i cannot connect it to pc over putty.. is anyone help me to read backup.?
t-mobile_mda said:
hey guys..
i have a module which called bus multimedia.. i need root or read full backup of this device.. but there is no usb socket only exist RX TX pinout and i cannot connect it to pc over putty.. is anyone help me to read backup.?
Click to expand...
Click to collapse
hey.. i removed the emmc and info..do u think that this device is android based..?
HiPower mode is On
Setting Interface to EasyJtag1/ISP_HiPower
Setting IO Levels to 3.3V
Setting Frequence to 21 Mhz
Setting BusWidth to 1 Bit
CMD Pullup Level: 2134 mV
CMD Active Level: 2609 mV
Setting HS Timing to Enabled
EMMC Device Information :
EMMC CID: 7001004D3732383038801500009374CA
EMMC CSD: D04F01320F5903FFFFFFFFEF8A400060
Manufacturer: KINGSTONE , NAME: M72808 , HEX: 4D3732383038 , S/N: 15000093 , Rev: 80
Manufacturer ID: 70 , OEM ID: 00 , Device Type: BGA (Discrete embedded) , Date: 7/2017
EMMC ROM 1 (Main User Data) Capacity: 7296 MB (0x0001C8000000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (0x000000400000)
EMMC RPMB Capacity: 4096 KB (0x000000400000) , Counter: 0 , Response: Clean
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x00 , Device not boot enabled
Boot Bus Config: 0x00 , x1 (sdr) or x4 (ddr) bus width in boot operation mode
H/W Reset Function [RST_N_FUNCTION]: 0x00 , RST_n signal is temporarily disabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition settings [PARTITION_SETTING_COMPLETED]: 0x00
EMMC Init completed
Backup saved: M72808_15000093_20220611_141710.extcsd (new backup)
Connected successfully
Operation: Scan PartitionTable from Source (Vendor: Binary Read/Write)
Scanning soft partitions from ROM2
GPT header is not found
Scanning soft partitions from ROM3
GPT header is not found
Scanning soft partitions from ROM1
GPT header is not found
MBR header is not found
You need a usb to uart device to get started on that board. You can find one online for about 3 dollars.