Develop Bugs

PCIbus!PCIEnum error with WINCE7 on Virtual CEPC

(Corecon) Download initiated...
(Corecon) Waiting to begin download...
(Corecon) Download complete.
(Corecon) Download complete.
0 PID:0 TID:2 Bootloader reported 511MB
0 PID:0 TID:2 RAM reported to kernel 511MB
9 PID:400002 TID:5c0002 WARNING: COM1: has been reserved exclusively for Debug Messages.
6103 PID:400002 TID:ae0006 PCIbus!PCIEnum: WARNING: Resource request for device 0:10:0 failed
after fixing the network error i get this and the system stuck
====================================
i made bin file with Platform builder
and i got same error with loadcepc.exe
Jumping to 0xXXXXXX
and the system halted
here in the picture is the error i get when doing download to RAM via etho
solution : disable crc udp in network card
===================================

Unrevoked problems with Linux x86_64 (SOLVED)

Hi all,
I was trying to root with unrEVOked 3.1 on a 64bit Ubuntu installation and hit this problem and found a solution so I thought I'd post it up here to help any other newbies like me
Problem (running from terminal)
Code:
unrEVOked recovery reflash tool
git 7bb95e5
/usr/lib/gio/modules/libgioremote-volume-monitor.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgioremote-volume-monitor.so
/usr/lib/gio/modules/libgiogconf.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgiogconf.so
/usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
I assume the problem is that reflash is 32 bit and my libs are 64, so install
frozenfox.freehostia.com/cappy/getlibs-all.deb
then
Code:
getlibs libgioremote-volume-monitor.so
This will install the 32 libs / gvfs and reflash is happy.

not solved for me
Unfortunately, this doesn't solve the problem for me:
Code:
[email protected]:~/Downloads$ sudo ./reflash
unrEVOked recovery reflash tool
git version: 4f78f67
/usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
This was my first attempt. unrevoked reported "done" in the end, but it didn't work. Now I followed your suggestion:
Code:
[email protected]:~/Downloads$ getlibs libgioremote-volume-monitor.so
libgioremote-volume-monitor.so: gvfs
The following i386 packages will be installed:
gvfs
Continue [Y/n]? y
Downloading ...
Installing libraries ...
[email protected]:~/Downloads$ sudo ./reflash
unrEVOked recovery reflash tool
git version: 4f78f67
/usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
Same error messages. And again it didn't work although unrevoked reported "done".
This is on Ubuntu 10.04 64bit. Any help appreciated.

Sorry, apparently it DID work. Titanium Backup was reporting a failure with root access, but that was down to a not-working BusyBox. Titanium downloaded an alternative, crashed with force close on restart but after a second restart it worked.
So potentially the first rooting without the 32bit libraries might have worked as well?

need to:
Code:
sudo apt-get install lib32ncurses5 libgtk2.0-0 ia32-libs-gtk

blankblash for moto z play (full brick) help

my motorcycle z play has an unbrick
I tried to revive it with the blank-flash and it marks this error
C: \ Users \ towers \ Desktop \ blankflash (3) \ blankflash>. \ Qboot.exe blank-flash
Motorola qboot utility version 3.40
[-0.000] Opening device: \\. \ COM4
[0.002] Detecting device
[0.005] ... cpu.id = 70 (0x46)
[0.005] ... cpu.sn = 3380452123 (0xc97d9b1b)
[0.005] Opening singleimage
[0.006] Loading package
[0.009] ... filename = singleimage.pkg.xml
[0.011] Loading programmer
[0.012] ... filename = programmer.mbn
[0.012] Sending programmer
[0.230] Handling things over to programmer
[0.231] Identifying CPU version
[0.237] Waiting for firehose to get ready
[30.597] ReadFile () failed, GetLastError () = 0
[60.443] Waiting for firehose to get ready
[120,558] ... MSM8953 unknown
[120.558] Determining target secure state
[120.566] Waiting for firehose to get ready
[180.704] ... secure = no
[180.741] Waiting for firehose to get ready
[240.865] Configuring device ...
[240.867] Waiting for firehose to get ready
[300.972] Waiting for firehose to get ready
[361.108] Waiting for firehose to get ready
[421.240] Waiting for firehose to get ready
[481.361] ERROR: do_package () -> do_recipe () -> do_configure () -> buffer_read () -> device_read () -> IO error
[481.362] Check qboot_log.txt for more details
[481.363] Total time: 481.366s
FAILED: qb_flash_singleimage () -> do_package () -> do_recipe () -> do_configure () -> buffer_read () -> device_read () -> IO error
C: \ Users \ towers \ Desktop \ blankflash (3) \ blankflash> pause
Press a key to continue . . .
can anybody help me......

exu8 said:
my motorcycle z play has an unbrick
I tried to revive it with the blank-flash and it marks this error
C: \ Users \ towers \ Desktop \ blankflash (3) \ blankflash>. \ Qboot.exe blank-flash
Motorola qboot utility version 3.40
[-0.000] Opening device: \\. \ COM4
[0.002] Detecting device
[0.005] ... cpu.id = 70 (0x46)
[0.005] ... cpu.sn = 3380452123 (0xc97d9b1b)
[0.005] Opening singleimage
[0.006] Loading package
[0.009] ... filename = singleimage.pkg.xml
[0.011] Loading programmer
[0.012] ... filename = programmer.mbn
[0.012] Sending programmer
[0.230] Handling things over to programmer
[0.231] Identifying CPU version
[0.237] Waiting for firehose to get ready
[30.597] ReadFile () failed, GetLastError () = 0
[60.443] Waiting for firehose to get ready
[120,558] ... MSM8953 unknown
[120.558] Determining target secure state
[120.566] Waiting for firehose to get ready
[180.704] ... secure = no
[180.741] Waiting for firehose to get ready
[240.865] Configuring device ...
[240.867] Waiting for firehose to get ready
[300.972] Waiting for firehose to get ready
[361.108] Waiting for firehose to get ready
[421.240] Waiting for firehose to get ready
[481.361] ERROR: do_package () -> do_recipe () -> do_configure () -> buffer_read () -> device_read () -> IO error
[481.362] Check qboot_log.txt for more details
[481.363] Total time: 481.366s
FAILED: qb_flash_singleimage () -> do_package () -> do_recipe () -> do_configure () -> buffer_read () -> device_read () -> IO error
C: \ Users \ towers \ Desktop \ blankflash (3) \ blankflash> pause
Press a key to continue . . .
can anybody help me......
Click to expand...
Click to collapse
Do you have brick version in Android?

Jaderalves said:
Do you have brick version in Android?
Click to expand...
Click to collapse
I had the android 7.1.1

exu8 said:
I had the android 7.1.1
Click to expand...
Click to collapse
no solution for now we are waiting for the oreo to get the blankflash

Jaderalves said:
no solution for now we are waiting for the oreo to get the blankflash
Click to expand...
Click to collapse
how many time ? did you know??

pedro1520 said:
how many time ? did you know??
Click to expand...
Click to collapse
when launching the oreo it probably leaves a blankflash

Good afternoon, any news?

exu8 said:
my motorcycle z play has an unbrick
I tried to revive it with the blank-flash and it marks this error
[120,558] ... MSM8953 unknown
can anybody help me......
Click to expand...
Click to collapse
The blankflash you used is an old one - doesn't recognize the 625.
AFAIK there is no blankflash for the MZP.
Probably only path is to send it to Moto or get another phone.

Problem rooting with XiaoMiTool V2

Hello everyone,
I tried to root my Mi Mix 2 with XiaoMiTool V2 but I have got a problem during the step of pushing file magisk_20.4.zip.
In the log, I can see :
[10:07:04][PSTA ][70c729f4] Start process (781): "C:\Xiaomi\XiaomiTool2\res\tools\adb.exe" "-s" "ebf1f094" "push" "C:\Xiaomi\XiaomiTool2\res\tmp\magisk_20.4.zip" "/sdcard/magisk_20.4.zip"
[10:07:05][PROC ][55e63029] Process (781) output: adb: error: failed to copy 'C:\Xiaomi\XiaomiTool2\res\tmp\magisk_20.4.zip' to '/sdcard/magisk_20.4.zip': remote couldn't create file: No such file or directory
[10:07:05][PROC ][55e63029] Process (781) output: C:\Xiaomi\XiaomiTool2\res\tmp\magisk_20.4.zip: 1 file pushed, 0 skipped. 48.9 MB/s (5942417 bytes in 0.116s)
[10:07:05][INFO ][70c729f4] Process (781) ended with exit code: 1, output len: 268
[10:07:05][ERROR ][70c729f4] Task error: exception: Failed to push file to the device: adb: error: failed to copy 'C:\Xiaomi\XiaomiTool2\res\tmp\magisk_20.4.zip' to '/sdcard/magisk_20.4.zip': remote couldn't create file: No such file or directory : AdbPushTask -> status: RUNNING
Can you help me ??
Thanks by advance !

Do you know an other way to root it easily ?
Thanks by advance.

''TID should not be 0'' error while flashing using SMT mode..

I accidently messed up the dynamic partition now the boot menu stuck at "SMT download failed' and whenever I try to use SMT mode in MSM it gets stuck in ''TID should not be 0" screen, Do anyone know the fix of it, any help is appreciated.
tried with MSM hotdogb_14_O.22_210127 and hotdogb_14_O.05_191012_repack (both are of oos10).
OOS10 boots fine but with the SMT error boot screen.
OOS11 seems impossible to boot
The error screen image is attached below (Not my image but it shows exactly like that)
log:
IA V1.0
FCL V1.0
========================================================
MetadataVersion=2,CryptVersion=1,m_bIsPackImage=1
Project Name: 18865
Image Version: hotdogb_14_O.05_191012
Skip SHA256 Check: No
HW CHK: No
RF CHK: No
PRJ CHK: No
MDL CHK: Yes
Tool version verified! (V5.0.15)
project 18865 not support boot mode feature
project 18865 enable fuse
MVL V1.2
[1] dwMajorVersion=6,dwMinorVersion=2,is_win7_system=0te123
Use Lite Firehose
Use DDR Firehose
Dialog selection = 4
Device Arrival: \\?\USB#VID_05C6&PID_9008#5&32cc216f&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[2] Set device as UFS
[2] [CSerialCommHelper] Buf: 0 (21/10)
[2] [CSerialCommHelper] No data in buffer to be sent 0
[2] [SP][193] Check cmd done status failed. 1
[2] [SP][206] Reset Sahara
[2] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 0400
[2] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[2] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[2] Memory size:256G
[2] provision file: samsung
Device Remove: \\?\USB#VID_05C6&PID_9008#5&32cc216f&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
Device Arrival: \\?\USB#VID_05C6&PID_9008#5&32cc216f&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[2] [CSerialCommHelper] Buf: 0 (14/10)
[2] [CSerialCommHelper] No data in buffer to be sent 0
[2] [SP][193] Check cmd done status failed. 1
[2] [SP][206] Reset Sahara
[2] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 0400
[2] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[2] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[2] Memory size:256G
[2] [Firehose] HwVersion = 14
[2] [Firehose] RfVersion = 3
[2] [Firehose] PrjVersion = 4
[2] HANDSET_TYPE_256G:
[2] Target ID should not be default in SMT mode
Device Remove: \\?\USB#VID_05C6&PID_9008#5&32cc216f&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}