Database Info

Error Mali version register: 0x0

Hi
I update wince to Android but only a black screen after linux logo
( i download official firmware for tcc8902 HSG x5a my tablet is Hsg x5, my tablet cpu is tcc8901 only difference is 3d hardware accelerator).
I enter to device whit adb and see a problem to Mali driver
<4>Mali: ERR: /home/B090157/eclair_100628/hardware/telechips/opengles/src/devicedrv/mali/common/mali_kernel_GP2.c
<4> maligp_core_version_legal() 426
<4> Error: reading this from maligp version register: 0x0
<4>
<4>Mali: ERR: /home/B090157/eclair_100628/hardware/telechips/opengles/src/devicedrv/mali/common/mali_kernel_GP2.c
<4> maligp_renderunit_create() 370
<4> Renderunit NOT created.
It's possible whit adb / andorid tools correct this problem??
Best Regards

Lg p920 ressurection

you have soft bricked or hard your Phone its easy
Now just follow the Steps and do it properly
And one more essential step is to crack.lg flash tool by changing the system date and entering the serial key the key is present somewhere in the above post search it and enter it u will crack lg flash too
Tools and files needed :-
1-bootv21e.rar from here http://d-h.st/RC5 and after downloading this file unrar it by any unzip or unrar software
2- lg usb drivers and usb cable of LG from here http://csmg.lgmobile.com:9002/data/L...in7_LGEAll.zip
3-http://csmg.lgmobile.com:9002/data/S...shTool_1.1.zip is the LG FLASH tool
4-download the .dll file from here http://www.mediafire.com/?mc6ia9o8iqwqndw
5- Optional Smart flashtool if you get get through the KEy of LG flash tool but this would be hactic and you would also need lg support tool for imei fix download links
-https://docs.google.com/file/d/0B8IkQjiPjX_DS2s1NC1zVGtLWDQ/edit?pli=1 smartflash tool
-Google LG suppot tool
Before you start READ THE GUIDE once so you can understand it and then proceed with repair.
http://d-h.st/U08 omap4420 wkparks
and google omap flashinstaller
Step1.
Install LGflashtool (also copy/paste crack)
P920 users should run LG FlashTool and load BOOTV21E_AP.bin (ONLY THE AP.BIN FILE) and keep it open but NOT ready for flashing.
SU760 users should run LG FlashTool and load SU760V10GROM (ONLY THE AP.BIN FILE) and keep it open but NOT ready for flashing.
Step 2.
Extract WKPARKS omap4boot and follow installation steps:
Install OMAP4430 USB driver
Quote:
If you plug your Phone on PC without battery, OMAP4430 device appeared for seconds and then disappeared in your Windows Device Manager
(check arsen4oo photo guide in post #3)
On windows 7 sometimes OMAP4430 flashes too fast so you cant install driver.
There is a a windows feature that will help you install the driver easier.
To view devices that were once installed but are no longer attached to the computer, open a Command Prompt window using the Run As Administrator option and enter the command:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
Then, from the same command prompt, type devmgmt.msc to open Device Manager. Choose View, Show Hidden Devices. The new instance of Device Manager will show “ghosted” entries for devices that were once present. This technique is especially useful for fixing problems caused by leftover drivers after replacing a network card or video card—you can easily delete the ghosted device or update the OMAP4430 driver.
After driver installation ends remove usb cable BUT keep windows device manager open.
Step 3. Run start_fastboot.bat and select option 2
Step 4. Pull out battery
Step 5. Hold Vol+
Step 6. Connect USB cable, the usbboot will start
Step 7. Insert battery while the usbboot is waiting
Step 8. Script tells you to remove cable but i dont think it's necessary in this version
Step 9. Release Vol+ and look in your Windows Device manager
If everything worked ok your phone got recognised and now you are in downoad mode.
Step 10. Change LG USB Serial Port according to LG FlashTool Guide to port 41.
Step 11. Remove cable and battery from P920/SU760
Step 12. Set LG FlashTool ready for flashing.
Step 13. Run Steps 3-9 again and you will see your phone being flashed from LG FlashTool.
It will be stopped at 26-30% because phone will turn off on its own BUT the next time you try to enter NORMAL DOWNLOAD MODE it will be available again.
Step 14. Set LG FlashTool ready to flash your P920 with BOOTV21E_AP.bin again.
SU760 users should use SU760V10GROM bin .
Step 15. Put your phone in DOWNLOAD MODE without using omap4boot this time.
Step 16. LG FlashTool will recognise the phone and flash it completely this time.
P920 after reboot will go to CWM. You can flash your personal backup or reboot to STOCK V21E.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
5-Restoring IMEI
a.Connect phone by USB
b.Activate USB debug mode
c.Enter 3845#*920# in dialer if that doesn’t work try 3845#*925# or 3845#*720# if device is SU760
d.Select Port Settings -> Select CP Image Download
e.A new device should appear at let it install
f.Open Tutty (or hyperterminal) and select serial protocol. Click on open
g.Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
h.Type at%imei, it should display a dummy IMEI
i.Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x where x,x,x... is your orginal IMEI number (found under the battery of your phone). It should response IMEI WRITE OK
j.Reboot phone
if u dont understand it LG support tool will so
6-now open lg suppot tool and remove battery follow step 4 till u get the download mode with S/w and something written in chinese and wait till phone is detected now click customer Support and then recovery Phone then you will be asked for imei insert the imei and it will recognise ur pphone press ok depending on the speed of ur internet connection it will take the time to download the files and update ur phone let the whole procedure complete with me it took around one hour
7- after the process is completed disconnected the phone insert battery and boot ur phoen again it will boot and now again u will find the same issue but this time the trick is simple and easy ur internal memory curropted so format it u will get around 5.57gb and then .Enter 3845#*920# in dialer and do a factory reset or a normal factory reset after reset ur phone wll boot and display android and a package and the loading bar this means the phone is fixed with imei and u will get what you need have a look at the attachment and the vidoe on youtube i have posted [YOUTUBE]http://www.youtube.com/watch?v=BR1_jrsAibk[YOUTUBE]
the last step of factory reset is essential or you wont fix the imei
all the best
download reebooter utility from here http://d-h.st/24C
and do this
Info:
This utility will not work if you don't have Omap Drivers installed
Select task:
1. Flash ICS FastbootLoaders+Recovery
2. Flash V21E Loaders+Recovery
x. Exit
----------------------------------------
Please select 1,2 or exit(x): 2
Ready to Flash V21E+recovery
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x3
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 40a11fbe08c36fb34f6a113fc2516c63395c7947
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 0983f41c
CRC1: 139c4f4f
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-seconds...
[*] msg size = 4
usb_write 21504
[*] data size = 21504
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 232512
usb_write 4
usb_write 232512
** Done **
< waiting for device >
sending 'recovery' (5854 KB)...
OKAY [ 3.012s]
writing 'recovery'...
OKAY [ 1.230s]
finished. total time: 4.252s
sending 'u-boot' (512 KB)...
OKAY [ 0.268s]
writing 'u-boot'...
OKAY [ 0.355s]
finished. total time: 0.627s
sending 'x-loader' (128 KB)...
OKAY [ 0.070s]
writing 'x-loader'...
OKAY [ 0.051s]
finished. total time: 0.127s
Loaders have been flashed.
Your P920 is ready to boot into GB again. Reboot.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
GOOD LUCK and lets get those bricks fixed.
TROUBLESHOOTING
If you get the Silver LG Screen u are on Fastboot mode
if you get a message like usb not recognised then u probably have a faulty cable
all the Best f++k the Brick:good:
If something doesn't work for you make a post describing exactly what you did , your phone model and your operating system.
Before making pointless posts READ THE GUIDE.
If you don't know how to make one of the recovery programs work READ THEIR GUIDE .
You can find links in the end of this post.
http://forum.xda-developers.com/showthread.php?p=18134614
http://forum.xda-developers.com/showthread.php?t=1629307
http://forum.xda-developers.com/showthread.php?t=1244490
http://forum.xda-developers.com/showthread.php?t=1540163
Sent from my LG-P920 using xda premium
I will edit this thread for the atachments so wait for it

And one more essential step is to crack.lg flash tool by changing the system date and entering the serial key the key is present somewhere in the above post search it and enter it u will crack lg flash too
Sent from my LG-P920 using xda premium

This is more or less a duplicate of the thread below
http://forum.xda-developers.com/showthread.php?t=1942836&page=58
Thread Closed

[TOOL] [TISSOT] Low-level Backup/Restore/Unbrick toolkit for Mi A1

What?
A Windows (only) toolkit for making full backup/restore of all Mi A1 partitions to/from your PC.
Utilizes EMMCDL in Qualcomm EDL mode - only needs fastboot access (unlocked BL) or testpoint (for bricked devices, maybe locked ones too - not sure)
Backups create a rawprogram0.xml file which could also be restorable in MiFlash if you choose (untested - not part of toolkit goal).
See FAQ at bottom for details about how to use EDL mode.
--------------------------------
Why?
Mainly to...
...backup all your hidden/system partitions that TWRP cannot (e.g. persist) to keep them safe.
...recover your device in the event of a brick
--------------------------------
How?
Requirements
Windows PC ONLY
Qualcomm EDL drivers (can get them from here, among other places)
Fastboot access working with driver (generic binary and driver work fine, it's all over the place
If you're firm-bricked (stuck in Diagnostic mode) you need to disassemble and bridge the test-points to kick it out of diagnostic mode - but that's beyond the scope of this thread/tool.
Setup
Download the latest version from GitHub (link at bottom) and extract
Connect your device with a quality USB-C cable (original worked well). Some cheap cables, or USB2 > USB-C adapters can cause the process to fail.
Boot into fastboot and run the command...
Code:
fastboot oem edl
...you may see an error, that's normal. Device should now have blank screen and a white flashing light.
Install the QDLoader driver. You may see this in device manager if you've not installed it yet...
[Link because XDA forum keeps breaking my IMG tags whenever I edit]
...just right click > properties > update driver, the usual thing (if you downloaded the smaller driver pack ZIP from above). Then it should look like this...
[Link because XDA forum keeps breaking my IMG tags whenever I edit]
If your COM port in device manager (see above) is notCOM30, you need to-
Edit the config.ini in the toolkit folder
Replace com30 with whatever your port is
Now you're ready to use the tool.
Usage
The toolkit is pretty self-explanatory. But first you need to select which partitions you want to backup with option 1. Two partition lists are already included:
partition_list.all.txt - this list selects all partitions that exist on the Mi A1. Note that backing up system(_a/_b) and especially userdata will take a VERY LONG TIME. Also note that the backup images are NOT compressed; so expect to have 32GB space free for example (if you have a 32GB device).
partition_list.skip-systems-and-userdata.txt - this will backup all partitions except system(_a/_b) and userdata. More useful, since we backup system and userdata in TWRP anyway. All the other firmware partitions come to only about 500MB.
Once you select the list you want to use, you can run the backup with 2 - just enter a folder name and it'll go there.
Restore does not require a partition list to be loaded; since the partition table is stored inside the backup as rawpartition0.xml. You can manually edit this file if you want to selectively restore partitions - just delete the whole line of partitions you don't want to restore. Note that changing any of these values will NOT repartition the device - you'll only corrupt your partition table if you do this.
Well I guess that's it, I will update this guide after feedback (it's a bit rough, I am kind of rushing lol).
--------------------------------
Where?
Download the latest version on GitHub:
https://github.com/CosmicDan-Android/MiA1LowLevelBackupRestoreTool
... simply press the green 'Clone or download' button on the right, then 'Download ZIP'.
--------------------------------
Who?
Special thanks to @emuzychenko for his batch script wizardry which this is mostly based on. You can see his original tool and scripts here. I just re-wrote it all to be more user friendly and convenient for me and others.
--------------------------------
History
2022-03-04
Fix for systems with a GNU-like find executable in path
2018-05-23
Added config option to change transfer speed (reducing may help with freezes)
2018-05-15
Fixed crashing when path containing tool has spaces
Added a "debug mode" that won't instantly close the Window in event of a hard crash (why oh why did I ever use Batch again...)
Added a "persist-only" partition list
2018-05-14
Initial version
--------------------------------
FAQ
Q) EDL mode? Eh?
A) EDL mode, or "Emergency DownLoad" mode, is a low-level mode for flashing devices. It is entered by the command:
Code:
fastboot oem edl
EDL mode is used to read/write to the eMMC more directly. It is used by this tool, as well as flashing with MiFlash.
Other important notes:
You will need good QDLoader drivers. These drivers gave me the best results.
You can exit EDL mode by holding Power button for ~10 seconds. Hold with VolDn to reboot into fastboot again, as one might expect.
Make sure you use a good USB-C cable.
Sometimes the flashing process can freeze. It will always report success when done. If it freezes, you need to reboot EDL mode. Try a different USB port or cable if you keep experiencing freezes.
Q) I get a freeze or hang when trying backup/restore partitions
A) First, make sure it's actually frozen. Open log.txt in the tool folder, and then open it again to see if it's changed.
If not, make sure you're using the driver linked in this post, as it proved to be most reliable by myself and others. You can also try these things (recommended in this order):
Reboot to EDL mode again;
Use a different (better) cable;
Use a different USB port;
Reduce the transfer speed in config.ini (be sure to read the comments)
Use a different PC;
Of course all are welcome to post their questions/suggestions and so on. Happy flashing!

Very good job man tnx

First of all it doesn't work for me with a locked bootloader, I had to unlock the bootloader and followed the instructions, after opening the program and selecting any option in the tool simply closes the window and nothing happens. I tried it 4 times but no use, it just closes the command prompt window

rubenswing said:
First of all it doesn't work for me with a locked bootloader, I had to unlock the bootloader and followed the instructions, after opening the program and selecting any option in the tool simply closes the window and nothing happens. I tried it 4 times but no use, it just closes the command prompt window
Click to expand...
Click to collapse
Oh derp to me; of course locked bootloader can't access fastboot at all can it! Shows how experienced I am with locked devices thanks - updated thread with statement of unlocked BL requirement.
Re: Your crash, I realized right away that that is very likely because the program path has spaces in it. I fixed that now, just download the tool again and it should work. If not though, there is now a _debug tool that will show you the error instead of instantly closing. But I'm 90% sure that the problem you had is now fixed.

So you mention that all partition. Mean I can make persist and IMEI partition (I don't know whatever it called in our device in Samsung it's called efs) backup to. I did backup of IMEI partition via qpst tool (it's .qcnfile) but I wanted to make more backup. My WiFi is broken since I installed custom rom so I restored it via persist resurrect tool.
Thanks for your hardwork making thing easy for us.

cherryb8844 said:
So you mention that all partition. Mean I can make persist and IMEI partition (I don't know whatever it called in our device in Samsung it's called efs) backup to. I did backup of IMEI partition via qpst tool (it's .qcnfile) but I wanted to make more backup. My WiFi is broken since I installed custom rom so I restored it via persist resurrect tool.
Thanks for your hardwork making thing easy for us.
Click to expand...
Click to collapse
If IMEI is on EFS, yes it will do that but TWRP also has EFS backup/restore.
This tool will do absolutely every partition, there is literally nothing else on the storage that needs to be backed up. Only thing it can't do is repartition device, that has to be done manually (I have another thread about that).

CosmicDan said:
Oh derp to me; of course locked bootloader can't access fastboot at all can it! Shows how experienced I am with locked devices thanks - updated thread with statement of unlocked BL requirement.
Re: Your crash, I realized right away that that is very likely because the program path has spaces in it. I fixed that now, just download the tool again and it should work. If not though, there is now a _debug tool that will show you the error instead of instantly closing. But I'm 90% sure that the problem you had is now fixed.
Click to expand...
Click to collapse
Yep it's working very much now as expected and a big thank you :good: I now could backup up all the partitions on my device

flash_factory.bat
Which are the files that are nuked when you do a flash_factory? I know modemst1, modemst2 and persist are the important ones that are mentioned in the threads. There's any other data you should backup? I see there's a lot more partitions other than the usual ones, they hold irrecoverable data too? Also I'have seen that to recover IMEI people use a qualcomm tool, do you need that process or you can just flash modemst1 and modemst2 to recover IMEI?

ekistece said:
Which are the files that are nuked when you do a flash_factory? I know modemst1, modemst2 and persist are the important ones that are mentioned in the threads. There's any other data you should backup? I see there's a lot more partitions other than the usual ones, they hold irrecoverable data too? Also I'have seen that to recover IMEI people use a qualcomm tool, do you need that process or you can just flash modemst1 and modemst2 to recover IMEI?
Click to expand...
Click to collapse
Check the factory_flash.bat, it flashes everything. Also the rawpartition0.xml (which is used in edl mode, factory_flash.bat is only for fastboot mode). So backup everything.
I don't know where Imei is stores, so just backup everything.
Qualcomm tool IMEI recovery is for injecting IMEI into existing partition somewhere. Not necessary if you already have full IMG backups.

Noob Questions
1. Ok, so consider i have used your tool and worked as intended. so currently the Phone will be in 'edl mode' how can i reboot it back to system (i guess fastboot commands wont work in edl mode).
2. After creating backup, How should i restore partions ?...
using twrp or CMD....?
(Does Tool backup Partitions as img or zip file....?)
3. Does this tool allows user to restore partition individually or one has restore all the backup data as a whole (i.e all backup partions)
Thanks again for the amazing tool :angel: :good:

thepandas said:
Noob Questions
1. Ok, so consider i have used your tool and worked as intended. so currently the Phone will be in 'edl mode' how can i reboot it back to system (i guess fastboot commands wont work in edl mode).
2. After creating backup, How should i restore partions ?...
using twrp or CMD....?
(Does Tool backup Partitions as img or zip file....?)
3. Does this tool allows user to restore partition individually or one has restore all the backup data as a whole (i.e all backup partions)
Thanks again for the amazing tool :angel: :good:
Click to expand...
Click to collapse
1) Hold power button for 10+ seconds to reboot
2) You restore them with the same tool, there is a restore option in the menu, it's right there ?
3) The restore will restore everything listed in rawpartitions0.xml inside the IMG backup folder. If you want to exclude some partitions in restore, delete the corresponding XML line. This is already explained in the OP.

Great job. Was just wondering if is everything going well if is this error displayed in the log:
Code:
Version 2.15
PblHack: Error - 1836597052
Did not receive Sahara hello packet from device
!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!
Dumping data to file RR-FULL\system_b.img
Dumping at start sector: 0 for sectors: 0 to file: RR-FULL\system_b.img
.0" encoding="UTF-8" ?><data><log value="XML (0 bytes) not validated" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" /></data>
Programming device using SECTOR_SIZE=512
<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="16384"/></data>
<?xml version="1.0" encoding="UTF-8" ?><data><log value="[email protected] [email protected]" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="16384" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8953" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="16384" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8953" /></data>
Connected to flash programmer, starting dump
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="1" physical_partition_number="0" start_sector="1"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 1
Downloaded raw image at speed 30 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 0" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="32" physical_partition_number="0" start_sector="2"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 32
Downloaded raw image at speed 16384 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 0" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="6291456" physical_partition_number="0" start_sector="7477248"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
hRead = INVALID_HANDLE_VALUE, zeroing input buffer
Should I leave it and let it continue? Because it's been frozen for some time now.

SmallTarzan said:
Great job. Was just wondering if is everything going well if is this error displayed in the log:
Code:
Version 2.15
PblHack: Error - 1836597052
Did not receive Sahara hello packet from device
!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!
Dumping data to file RR-FULL\system_b.img
Dumping at start sector: 0 for sectors: 0 to file: RR-FULL\system_b.img
.0" encoding="UTF-8" ?><data><log value="XML (0 bytes) not validated" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" /></data>
Programming device using SECTOR_SIZE=512
<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="16384"/></data>
<?xml version="1.0" encoding="UTF-8" ?><data><log value="[email protected] [email protected]" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="16384" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8953" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="16384" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8953" /></data>
Connected to flash programmer, starting dump
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="1" physical_partition_number="0" start_sector="1"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 1
Downloaded raw image at speed 30 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 0" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="32" physical_partition_number="0" start_sector="2"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 32
Downloaded raw image at speed 16384 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 0" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="6291456" physical_partition_number="0" start_sector="7477248"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
hRead = INVALID_HANDLE_VALUE, zeroing input buffer
Should I leave it and let it continue? Because it's been frozen for some time now.
Click to expand...
Click to collapse
At the very end of the log file does it give a status?

rubenswing said:
At the very end of the log file does it give a status?
Click to expand...
Click to collapse
No, it doesn't.
Code:
Sectors remaining 1792
Sectors remaining 1760
Sectors remaining 1728
Sectors remaining 1696
Sectors remaining 1664
Sectors remaining 1632
Sectors remaining 1600
Sectors remaining 1568
Sectors remaining 1536
Sectors remaining 1504
Sectors remaining 1472
Sectors remaining 1440
Sectors remaining 1408
Sectors remaining 1376
Sectors remaining 1344
Sectors remaining 1312
Sectors remaining 1280
Sectors remaining 1248
Sectors remaining 1216
Sectors remaining 1184
Sectors remaining 1152
Sectors remaining 1120
Sectors remaining 1088
Sectors remaining 105
It's been stuck at this for like 30 minutes now, I've closed it.

SmallTarzan said:
No, it doesn't.
Code:
Sectors remaining 1792
Sectors remaining 1760
Sectors remaining 1728
Sectors remaining 1696
Sectors remaining 1664
Sectors remaining 1632
Sectors remaining 1600
Sectors remaining 1568
Sectors remaining 1536
Sectors remaining 1504
Sectors remaining 1472
Sectors remaining 1440
Sectors remaining 1408
Sectors remaining 1376
Sectors remaining 1344
Sectors remaining 1312
Sectors remaining 1280
Sectors remaining 1248
Sectors remaining 1216
Sectors remaining 1184
Sectors remaining 1152
Sectors remaining 1120
Sectors remaining 1088
Sectors remaining 105
It's been stuck at this for like 30 minutes now, I've closed it.
Click to expand...
Click to collapse
Could you upload the log file

rubenswing said:
Could you upload the log file
Click to expand...
Click to collapse
Where should I upload it? I can't upload it here, it's over the size limit. Pastebin doesn't work either.

You need a better USB cable or try a different port.
It will report success if it finishes OK. But that is a communication error when it freezes.
Also reboot EDL mode. And keep the window active, don't go play a game while it's doing stuff

CosmicDan said:
You need a better USB cable or try a different port.
It will report success if it finishes OK. But that is a communication error when it freezes.
Also reboot EDL mode. And keep the window active, don't go play a game while it's doing stuff
Click to expand...
Click to collapse
I am using an USB-C cable I bought from a shop the other day, and I was in the EDL mode. I wasn't playing a game during the backup either!

SmallTarzan said:
I am using an USB-C cable I bought from a shop the other day, and I was in the EDL mode. I wasn't playing a game during the backup either!
Click to expand...
Click to collapse
Then as Cosmic Dan said try a different port and check

Thanks for the tool! Was able to backup everything except userdata and system since i don't have the time yet. I'll be preparing for treble.
Sent from my Xiaomi Mi A1 using XDA Labs

rockchip 3229 android box.

i am using rockchip 3229 android box (version 5.0). box not booting and "rockchip" screen is displaying. please help.
tryed to short 7'and 8 pins but no use.
the follwing error is displaying.
21:55:25 261 <Layer 2-1-6> Test Device Start
21:55:25 261 Error:RKU_Write-->WriteFile failed,bRet=0,err=6,size=31,write=0
21:55:25 483 Error:RKU_ClearBuffer-->ReadFile failed,bRet=0,err=6,size=512,read=0
21:55:25 514 <LAYER 2-1-6> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_320B#6&8CA65F9&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
21:55:26 543 Error:RKU_Write-->WriteFile failed,bRet=0,err=6,size=31,write=0
21:55:26 777 Error:RKU_ClearBuffer-->ReadFile failed,bRet=0,err=6,size=512,read=0
21:55:26 793 <LAYER 2-1-6> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_320B#6&8CA65F9&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
21:55:27 813 Error:RKU_Write-->WriteFile failed,bRet=0,err=6,size=31,write=0
21:55:28 044 Error:RKU_ClearBuffer-->ReadFile failed,bRet=0,err=6,size=512,read=0
21:55:28 094 <LAYER 2-1-6> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_320B#6&8CA65F9&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
21:55:29 123 <Layer 2-1-6> Test Device Fail
21:55:29 123 **********Upgrade Done Success<0> Fail<1> Time<3891>ms**********

Asus Zenfone Max Plus M1 [X018D] bricked - some advice to recover data ?

Hello XDA community !
To be honest I'm a newbie here, and not really experienced on mobile phone technical stuff
My Zenfone suddenly stopped working last week, without any particular reason.
The only thing I can see when I on the device is the "Powered by Android" logo. But nothing else happens after.
Then I wanted to start the recovery menu, but even when I select "recovery mode" or "fastboot" nothing happens, it's still showing "Powered by Android" logo and no more
See this screenshot :
{
"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 tried to plug the device with USB to my linux laptop with android studio installed, but adb devices show nothing
I also tried to create a microSD card, bootable, with exFAT partition and put the phone firmware on the root of the card (as described https://www.asus.com/supportonly/zenfone max plus (m1)(zb570tl)/helpdesk_download/). Even with it, recovery or fastboot options give the same screen as above
My idea was to be able to boot from sd card and be able to "revive" somehow the phone, and at least being able to download user data from it with the help of adb
I'm not sure if it's possible of if I should prepare the microsd with another format or partition layout
Any idea to guide me ?

Don't think you can recover any user-data this because probably bootloader completely got corrupted. Re-flash Stock ROM.

Thanks for your answer.
Sorry also because I made a mistake : I think fastboot mode is active
What I did : In the menu above, I selected "Fastboot mode"
then I got an output : "CSC FASTBOOT mode"
Then I plugged the phone on my laptop USB
The "lsusb" command returned an additionnal device :
Code:
Bus 001 Device 004: ID 0bb4:0c01 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo / FP1
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bb4 HTC (High Tech Computer Corp.)
idProduct 0x0c01 Dream / ADP1 / G1 / Magic / Tattoo / FP1
bcdDevice 1.00
iManufacturer 1 MediaTek
iProduct 2 Android
iSerial 3 J1AXJR04D658EJ6
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 256mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 3
iInterface 4 fastboot
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Status: 0x0001
Self Powered
"adb devices" still returns nothing but "fastboot devices" does :
J1AXJR04D658EJ6 fastboot
"fastboot reboot" does also reboot the phone ...
From there I guess at least I can do something. I don't know if I'll be able to recover some data, but anyway if I can recover my phone that would be fine too.

you can unlock bootloader with mtkclient (do a backup beforehand) and flash TWRP from fastboot, to see if that leads to something.

ok thanks a lot. I'll have a look to mtkclient / TWRP and try to manage !
Will let you know soon.

keep in mind unlocking from fastboot forces factory reset. It will flush keystore in TEE, don't try this even with full backup. TEE can't backed up.
unlocking from mtkclient afaik does not wipe userdata. but do a backup of userdata + metadata + seccfg (or even better full dump) just in case.
you can try to boot into EDL mode with both vol keys + usb, modified fastboot, DIY deep flash cable or test point method.
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo] Reboot to EDL mode from FASTBOOT! No more Test Point Method needed ;) Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot...
forum.xda-developers.com
also please note TWRP is maybe not able to decrypt, because encryption keys are bonded to bootloader lock state.
however some people claim it's possible, maybe due the fact that seccfg is patched in way to circumvent this (untested).
if you can't boot into recovery from bootloader, you can boot into file from fastboot (requires bootable slot)
Code:
fastboot boot twrp.img

thanks Alecxs for all the information. I'll take some time to read carefully everything.
In the meantime, I installed successfully mtkclient on my laptop. I didn't know about this tool before
I used first the read partition tool, which went fine for almost all partitions except userdata :-(
it started but stopped after 9 GB (over 52) with the following message
Failed to dump sector 12517376 with sector count 109592543 as MyZenfone-partition dump/userdata.bin
18.0% Read (Sector 0x12D6C80 of 0x6883FDF, 42m:19s left) 18.67 MB/sDAXFlash
DAXFlash - [LIB]: Error on reading data: MMC error (0xc0040030)
looks like game over ...

well.. if this is game over, then you have nothing to lose I guess? so backup all partitions excluding userdata (--skip=userdata) then only try to unlock seccfg (do not erase any partition ignore instructions) then boot into fastboot and check if TWRP can boot
TRY AT OWN RISK YOU MAY CORRUPT USERDATA ENCRYPTION OR ERASE USERDATA​
Code:
python3 mtk da seccfg unlock
python3 mtk payload --metamode FASTBOOT
fastboot boot path/to/twrp.img

might be possible to dump userdata excluding unreadable sectors. but you need to read the instructions. nevertheless the dump (even if healthy) is impossible to decrypt on PC, can only be decrypted on the origin phone itself...

thanks alecxs, I think I'll try to boot into twrp
My concern is to find a suitable twrp for my device. There is no official port for Asus X018D
I tried to find it by googling and found this on "unofficial twrp" site
twrp 3.2.3 For Mediatek MT6750 Phone
which could be ok for mine maybe except they it's for android 8 and 8.1, while I was still on Nougat 7
I don't know if trying this could work or not ?

you need TWRP for the Plus variant. can you share boot.img + recovery.img read off device?

yes I can share the dumped partitions from mtkclient (the extension is .bin)
boot.bin :
boot.bin
drive.google.com
recovery.bin
recovery.bin
drive.google.com

okay let me try to port generic TWRP. you can meanwhile try that Oreo+recovery+tested.img (login required)
edit: X018D_TWRP.img for android 9 (no login required)

So I tried to unlock bootloader from mtkclient, which resulted in :
sej - HACC init
sej - HACC run
sej - HACC terminate
sej - HACC init
sej - HACC run
sej - HACC terminate
Done |--------------------------------------------------| 0.0% Write (Sector 0x0 of 0x1) 0.00 MB/sDAXFlash
DAXFlash - [LIB]: Error on writeflash: MMC error (0xc0040030)
and then after (maybe I shouldn't have ...)
python3 mtk payload --metamode FASTBOOT
I think I did something wrong, because now I cannot list GPT
python mtk printgpt
gives
Code:
Port - Device detected :)
Preloader - CPU: MT6755/MT6750/M/T/S(Helio P10/P15/P18)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212c00
Preloader - Var1: 0xa
Preloader - Disabling Watchdog...
Preloader - HW code: 0x326
Preloader - Target config: 0x5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xcb00
Preloader - SW Ver: 0x1
Preloader - ME_ID: 10A8E97D4708BDEB74D8D7B3C7E0EBFA
PLTools - Loading payload from mt6755_payload.bin, 0x258 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: /home/laurent/Applications/DevOps/Android/mtkclient/mtkclient/payloads/mt6755_payload.bin
Port - Device detected :)
DA_handler - Device is protected.
DA_handler - Device is in BROM mode. Trying to dump preloader.
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2136.bin
xflashext - Patching da1 ...
Mtk - Patched "Patched loader msg" in preloader
xflashext
xflashext - [LIB]: Error on patching da1 version check...
Mtk - Patched "Patched loader msg" in preloader
xflashext - Patching da2 ...
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash
DAXFlash - [LIB]: xread error: unpack requires a buffer of 12 bytes
DAXFlash
DAXFlash - [LIB]: Error jumping to DA: -1

actually, the second command was just to exit preloader mode and switch into fastboot... sorry for the confusion. I have also attached the android 7 version of twrp for testing.. (see above)
If I got this right, unlocking was trying to write Sector 0x0 of 0x1 but it deny writing anything because eMMC is not writeable at 0xc0040030. But isn't that in userdata area?
however, on android 7 for some mediatek devices it's possible to boot into TWRP on locked bootloader. but needs flashing. you can try another flash tool, but it requires windows
edit:
@arthur.levene I got it wrong, seems there is also linux version. Anyway, please read golden rules for SP Flash Tool.
I recommend to create your own scatter file based on the current partition table, either with mtkclient or with WwR MTK v2.51 (most likely you can use the one that already comes with that twrp as the recovery start address is at 0x8000 on many devices, but I personally generally don't trust any scatter file just random downloaded).

lol thought 0xc0040030 was the address of the unreadable sector. turns out it is a fault code. so that could mean eMMC error (most likely) or insufficient permissions.
So any flashing attempts will probably fail no matter what tool used. maybe there is a cheat with heating gun or refrigerator (just guesswork, beware of condensating water)

thanks again alecxs for your time and advice.
I will continue my investigations based on your informations. If i understand your comment about eMMC error, this is not good news.
I will try also the flashing solution in case it could work, though not very skilled on that part too

actually I have never used mtkclient myself but according to documention flashing looks quite easy.
Code:
python3 mtk w recovery twrp.img
However, as you stated in OP you can't enter recovery mode from bootloader menu, so this could be bigger challenge.

I tried but currently I have an error
DAXFlash - Upload data was accepted. Jumping to stage 2...
DAXFlash - DA Extensions successfully added
Done |--------------------------------------------------| 0.0% Write (Sector 0x0Progress: |███████-------------------------------------------| 14.0% Write (SectProgress: |██████████████------------------------------------| 28.0% Write (Sector 0x2000 of 0x7254, 01s left) 6.74 MB/s
DAXFlash
DAXFlash - [LIB]: unpack requires a buffer of 12 bytes

quick search gives hint is might be driver issue. but you're on linux right? you could try again with libusb-1.0-0-dev_1.0.26-1_amd64.deb
https://github.com/bkerler/mtkclient/issues/192