Database Info

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

Hardbricked Mi4C, no fastboot or recovery + trouble with QFIL

I've managed to accidentally brick my MI4C while flashing recovery. There is no way to boot now, no fastboot either.
Phone doesn't respond to charging cable, but I'm able to connect it to the PC in the EDL mode (shows up as Qualcomm HS-USB QDLoader 9008).
I've downloaded the QPST package and used the QFIL emergency flashing utility following a guide from xiaomifirmware.com.
QFIL always finishes without any error (tried waiting for >45 mins), however the ROM doesn't seem to be installed - and the phone is still completely dead.
Is there any hope left? Here is the output log from QFIL:
Code:
Validating Application Configuration
Load APP Configuration
COM:5
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8992_ddr.mbn
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:\
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\
RAWPROGRAM file path: C:\rawprogram0.xml
PATCH file path:C:\patch0.xml
Programmer Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8992_ddr.mbn
Process Index:0
Start Download
Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8992_ddr.mbn
***** Working Folder:C:\Users\______\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\______\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8992_ddr.mbn
15:57:02: Requested ID 13, file: "C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8992_ddr.mbn"
15:57:02: 404664 bytes transferred in 0.094000 seconds (4.1055MBps)
15:57:02: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
15:57:02: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\______\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
The phones gets recognized by MiFlash, however any action results in ERROR 0x8000ffff: Receiving hello packet...
Any insight appreciated!

feek.404 said:
I've downloaded the QPST package and used the QFIL emergency flashing utility following a guide from xiaomifirmware.com. QFIL always finishes without any error (tried waiting for >45 mins), however the ROM doesn't seem to be installed - and the phone is still completely dead.
The phones gets recognized by MiFlash, however any action results in ERROR 0x8000ffff: Receiving hello packet...
Any insight appreciated!
Click to expand...
Click to collapse
With Xiaomi we generally use MiFlash rather than QPST/QFIL. I suppose you had tried the latest version of MiFlash but this device is old and an old version of MiFlash/MiPhone has to be used. Please get this 2015 version, it works for sure. Also for soft-brick recovery we use this old ROM "libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz" and then flash new stuff.
So, enter the EDL/9008 mode again and flash the old ROM with the old MiFlash.
Relax, it will be fixed :highfive:

k23m said:
With Xiaomi we generally use MiFlash rather than QPST/QFIL. I suppose you had tried the latest version of MiFlash but this device is old and an old version of MiFlash/MiPhone has to be used. Please get ..., it works for sure. Also for soft-brick recovery we use this old ROM "libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz" and then flash new stuff.
So, enter the EDL/9008 mode again and flash the old ROM with the old MiFlash.
Relax, it will be fixed :highfive:
Click to expand...
Click to collapse
Thank you, this version of MiFlash worked! :good:
I flashed the old 5.1 ROM with MiFlash, then the older TWRP version, then flashed the official 7.0 ROM, then unlocked bootloader, then the new TWRP, then my desired ROM and now I'm good to go again.
QFIL is such a finicky tool, I don't want to ever see that again haha

I got into a similar situation.
The device is bootlooping and does not have recovery or atleast it is not accessible. I can boot in fastboot mode. The bootloader is locked and it does not let me flash recovery or rom.
I have requested and got permision to unlock the phone but the unlocking fails at the second step (don't remember the mesaage right now, I'll try to update this response later).
I have tried flashing what is stated in this post but it did not work. If anyone could list the specific details required for each step I could give it a second try.
Anyone willing to help? Thanks

Nekronik said:
I got into a similar situation.
The device is bootlooping and does not have recovery or atleast it is not accessible. I can boot in fastboot mode. The bootloader is locked and it does not let me flash recovery or rom.
I have requested and got permision to unlock the phone but the unlocking fails at the second step (don't remember the mesaage right now, I'll try to update this response later).
I have tried flashing what is stated in this post but it did not work. If anyone could list the specific details required for each step I could give it a second try.
Anyone willing to help? Thanks
Click to expand...
Click to collapse
This is the output for the following commands:
$ fastboot getvar product:
product: MSM8992
finished. total time: 0.016s
$ fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: -0.000s
$ fastboot oem edl
< waiting for any device >
...
OKAY [ 0.000s]
finished. total time: 0.000s
The last command took some time to return even though it says 0.000.
I do see a 9008 in the devices admin.

Nekronik said:
This is the output for the following commands:
$ fastboot getvar product:
product: MSM8992
finished. total time: 0.016s
$ fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: -0.000s
$ fastboot oem edl
< waiting for any device >
...
OKAY [ 0.000s]
finished. total time: 0.000s
The last command took some time to return even though it says 0.000.
I do see a 9008 in the devices admin.
Click to expand...
Click to collapse
My problem was that MiFlash2015 did not let me communicate with the phone under edl mode. It simply refused to connect.
I have managed to recover it by attempting the recover method described above after disabling "Driver Signature Verification".
To disable it under windows 10, the easiest way I have found is to restart with driver signature verification turned off.
To do so: Configuration > Updates and Security > Recover > Reset now
Once the blue menu appears: Solve problems > Advanced options > Configure start > Reset
Then you will be prompted to select an option. It is probably to "F7" to disable signature verification.
Big thanks to @k23m for helping me recover the phone.

[SOLVED] Bootloop/kernel panic in meminfo_proc_show() 3.10.65+ trying to port LOS12.1

Hello Android kernel hackers,
I am trying to port the current ASB-patched LOS12.1 (github "cm12-amami") to a Teclast 98 (M1E9) tablet for which kernel sources are missing. My build completes fine, however, I run into a boot loop due to kernel panic with an (at least for me) totally unhelpful stack trace:
During init.rc processing, the kernel panics on logd startup when logd tries to read from /proc/meminfo with the following stack trace:
Code:
[ 126.200788]00:02:29.656321 openat(AT_FDCWD, "/proc/meminfo", O_RDONLY) = 4
[ 126.200956]00:02:29.656496 fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
[ 126.201077]00:02:29.656614 mprotect(0x7faf52b000, 4096, PROT_READ|PROT_WRITE) = 0
[ 126.201187]00:02:29.656726 mprotect(0x7faf52b000, 4096, PROT_READ) = 0
[ 126.202709]00:02:29.656833 read(4,
* KERNEL PANIC HAPPENS HERE!!! *
Code:
[ 126.202739]<1> (1)[949:logd]<1>start....
[ 126.202805]<1> (1)[949:logd]Unable to handle kernel NULL pointer dereference at virtual address 00000016
[ 126.202817]<1> (1)[949:logd]pgd = ffffffc070dee000
[ 126.202828]<1> (1)[949:logd][00000016] *pgd=0000000000000000 (1)[949:logd]
[ 126.202846]<1> (1)[949:logd][KERN Warning] ERROR/WARN forces debug_lock off!
[ 126.202854]<1> (1)[949:logd][KERN Warning] check backtrace:
[ 126.202868]<1> (1)[949:logd]CPU: 1 PID: 949 Comm: logd Tainted: G W 3.10.65+ #1
[ 126.202878]<1> (1)[949:logd]Call trace:
[ 126.202899]<1> (1)[949:logd][<ffffffc000088f50>] dump_backtrace+0x0/0x16c
[ 126.202913]<1> (1)[949:logd][<ffffffc0000890cc>] show_stack+0x10/0x1c
[ 126.202931]<1> (1)[949:logd][<ffffffc0009a69a0>] dump_stack+0x1c/0x28
[ 126.202947]<1> (1)[949:logd][<ffffffc0002f7210>] debug_locks_off+0x40/0x5c
[ 126.202960]<1> (1)[949:logd][<ffffffc00009a260>] oops_enter+0xc/0x28
[ 126.202974]<1> (1)[949:logd][<ffffffc000089100>] die+0x28/0x1d8
[ 126.202989]<1> (1)[949:logd][<ffffffc0009a49ec>] __do_kernel_fault.part.5+0x70/0x84
[ 126.203003]<1> (1)[949:logd][<ffffffc000094260>] do_page_fault+0x348/0x34c
[ 126.203017]<1> (1)[949:logd][<ffffffc000094350>] do_translation_fault+0x40/0x4c
[ 126.203030]<1> (1)[949:logd][<ffffffc0000813fc>] do_mem_abort+0x38/0x98
which does not seem to uncover the root cause, but rather the root cause stack trace seems to be:
Code:
[ 133.341226]<1>-(1)[949:logd]Call trace:
[ 133.341239]<1>-(1)[949:logd][<ffffffc0001f37d8>] meminfo_proc_show+0x50/0x3c4
[ 133.341255]<1>-(1)[949:logd][<ffffffc0001aefb8>] seq_read+0x1a4/0x40c
[ 133.341271]<1>-(1)[949:logd][<ffffffc0001ebeec>] proc_reg_read+0x4c/0x7c
[ 133.341285]<1>-(1)[949:logd][<ffffffc00018e75c>] vfs_read+0x88/0x170
[ 133.341298]<1>-(1)[949:logd][<ffffffc00018ebf0>] SyS_read+0x40/0x8c
[ 133.341310]<1>-(1)[949:logd]Code: 52800001 91326000 97fe67c1 aa0003f3 (f9400c00)
[ 133.341322]<1>-(1)[949:logd]---[ end trace 1b75b31a2719ed20 ]---
[ 133.341332]<1>-(1)[949:logd]Kernel panic - not syncing: Fatal exception
[ 133.341423]<1>-(1)[949:logd]mrdump: cpu[1] tsk:ffffffc073a3e000 ti:ffffffc070e64000
[ 134.241428]<1>-(1)[949:logd]
Most interestingly, the exact same kernel blob can successfully boot stock Android 5.1 and successfully read from /proc/meminfo when booted from stock boot.img while it crashes with my LOS12.1 build boot.img.
bootimg.cfg (using abootimg) is identical in both cases (except the boot size):
Code:
bootsize = 0x780000
pagesize = 0x800
kerneladdr = 0x40080000
ramdiskaddr = 0x44000000
secondaddr = 0x40f00000
tagsaddr = 0x4e000000
name = 1513588375
cmdline = bootopt=64S3,32N2,64N2 androidboot.selinux=permissive
Thanks a million in advance for any ideas or pointers about what might be going wrong with this stock kernel blob and my LOS12.1 build with regards to meminfo_proc_show()! :highfive:
awl14

Issue resolved!
Finally resolved by making changes (a whole number of, so I haven't tracked it down to one particular change) to my CM12.1 build's system partition, making it resemble the stock image more closely.
I still don't have any clues why the kernel would crash on reading from /proc/meminfo due to "wrong"/buggy contents in the system partition (/system file system), but as the issue is resolved, this can be regarded as a proof that such content in system can indeed matter in a critical way for the behaviour of the kernel...
My custom ROM for Teclast 98 (M1E9) runs fine now, I will publish a download link soon on xda.

Panic caused by kernel reading file /system/bin/cpuinfo
I encountered the same issue and was able to find the root cause. The kernel I'm dealing with has been modified by Chinese crooks who fake the amount of memory in the device by intercepting meminfo_proc_show(). In this routine, they read the file /system/bin/cpuinfo, apparently extracting the value to be shown to the user as the memory size from that file. The code does not even test the return code from the file opening routine, and simply crashes the kernel if the file is not present.

Poco X3 Possibly Hardbricked after using Miflash

So I backed up all my stuff and unlocked my bootloader just today to downgrade MIUI back to Android 10. I did it before with this same device and it worked wonderfully, but it eventually updated again automatically after a few months.
I downloaded both mi unlock and miflash, latest versions, everything seemed to be working fine until the device started rebooting continuously and a series of errors started showing up in the miflash console.
Final bits from the log file reads:
[2022-02-17 11:41:59:951:951883 6d1b1987]:info2:Erasing 'multiimgoem' OKAY [ 33.690s]
[2022-02-17 11:41:59:952:952891 6d1b1987]:info2:Finished. Total time: 33.695s
[2022-02-17 11:41:59:959:959872 6d1b1987]:info1:$fastboot -s devicename reboot
[2022-02-17 11:42:00:023:023833 6d1b1987]:info2:Rebooting OKAY [ 0.000s]
[2022-02-17 11:42:00:024:024832 6d1b1987]:info2:Finished. Total time: 0.001s
[2022-02-17 11:42:00:035:035825 6d1b1987]:begin FlashDone
[2022-02-17 11:42:00:035:035825 6d1b1987]:errMsg is null
[2022-02-17 11:42:00:036:036824 6d1b1987]:begin checkPoint
[2022-02-17 11:42:00:037:037824 6d1b1987]:error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
[2022-02-17 11:42:00:037:037824 6d1b1987]:process exit.
[2022-02-17 11:42:03:741:741430 6d1b1987]:flashSuccess False
[2022-02-17 11:42:03:745:745427 6d1b1987]:isFactory False CheckCPUID False
[2022-02-17 11:42:03:746:746427 6d1b1987]:before:flashSuccess is False set IsUpdate:True set IsDone True
[2022-02-17 11:42:03:746:746427 6d1b1987]:after:flashSuccess is False set IsUpdate:false set IsDone true
After that the phone won't get powered on, not a sign of life. Won't go into recovery mode or fastboot, won't make any sign while connecting to the charger. When connecting to the PC it gives me a "windows turned off a malfunctioning device" error and the phone won't get recognized on fastboot.exe
What I trully don't understand is that the log supposedly shows that everything went just fine, a reboot was prompted by miflash itself after it finished it's business, but how come it ended up with such a colossal mess up? I don't even have a spare phone =(

[CLOSED] Flash fails due signature error

Hello all,
im trying to flash magisk to my android device. Therefore i only have the update function from the manufacturer inside the settings menu and wireless adb access with full root priveleges. No fastboot, no USB debug.
What i´ve tried yet: patching the boot.img from original update.zip on the device with magisk app. Than repack and sign with SignApkv2.jar and the testkeys. The device loads the update.zip and boot into recovery but than the update fails.
This is the log from the failed update:
Spoiler: Log
[ 0.401828] Verifying update package...
[ 0.424111] I:comment is 1840 bytes; signature is 1720 bytes from end
[ 9.515415] I:signature (offset: 71e19400, length: 6b2): 308206ae06092a864886f70d010702a082069f3082069b020101310b300906052b0e03021a0500300b06092a864886f70d010701a08204ac308204a830820390a003020102020900936eacbe07f201df300d06092a864886f70d0101050500308194310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e20566965773110300e060355040a1307416e64726f69643110300e060355040b1307416e64726f69643110300e06035504031307416e64726f69643122302006092a864886f70d0109011613616e64726f696440616e64726f69642e636f6d301e170d3038303232393031333334365a170d3335303731373031333334365a308194310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e20566965773110300e060355040a1307416e64726f69643110300e060355040b1307416e64726f69643110300e06035504031307416e64726f69643122302006092a864886f70d0109011613616e64726f696440616e64726f69642e636f6d30820120300d06092a864886f70d01010105000382010d00308201080282010100d6931904dec60b24b1edc762e0d9d8253e3ecd6ceb1de2ff068ca8e8bca8cd6bd3786ea70aa76ce60ebb0f993559ffd93e77a943e7e83d4b64b8e4fea2d3e656f1e267a81bbfb230b578c20443be4c7218b846f5211586f038a14e89c2be387f8ebecf8fcac3da1ee330c9ea93d0a7c3dc4af350220d50080732e0809717ee6a053359e6a694ec2cb3f284a0a466c87a94d83b31093a67372e2f6412c06e6d42f15818dffe0381cc0cd444da6cddc3b82458194801b32564134fbfde98c9287748dbf5676a540d8154c8bbca07b9e247553311c46b9af76fdeeccc8e69e7c8a2d08e782620943f99727d3c04fe72991d99df9bae38a0b2177fa31d5b6afee91f020103a381fc3081f9301d0603551d0e04160414485900563d272c46ae118605a47419ac09ca8c113081c90603551d230481c13081be8014485900563d272c46ae118605a47419ac09ca8c11a1819aa48197308194310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e20566965773110300e060355040a1307416e64726f69643110300e060355040b1307416e64726f69643110300e06035504031307416e64726f69643122302006092a864886f70d0109011613616e64726f696440616e64726f69642e636f6d820900936eacbe07f201df300c0603551d13040530030101ff300d06092a864886f70d010105050003820101007aaf968ceb50c441055118d0daabaf015b8a765a27a715a2c2b44f221415ffdace03095abfa42df70708726c2069e5c36eddae0400be29452c084bc27eb6a17eac9dbe182c204eb15311f455d824b656dbe4dc2240912d7586fe88951d01a8feb5ae5a4260535df83431052422468c36e22c2a5ef994d61dd7306ae4c9f6951ba3c12f1d1914ddc61f1a62da2df827f603fea5603b2c540dbd7c019c36bab29a4271c117df523cdbc5f3817a49e0efa60cbd7f74177e7a4f193d43f4220772666e4c4d83e1bd5a86087cf34f2dec21e245ca6c2bb016e683638050d2c430eea7c26a1c49d3760a58ab7f1a82cc938b4831384324bd0401fa12163a50570e684d318201ca308201c60201013081a2308194310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e20566965773110300e060355040a1307416e64726f69643110300e060355040b1307416e64726f69643110300e06035504031307416e64726f69643122302006092a864886f70d0109011613616e64726f696440616e64726f69642e636f6d020900936eacbe07f201df300906052b0e03021a0500300d06092a864886f70d01010105000482010099e456c0ecdb178abe470462040e5c0752f6fba4d888dcd95ab39b3a72c3a42d7627824d4ffea8830c3ad32c2739cb485826c4dbb4072c13013c23f05a2d3c5e213336be8e72eb33f452a3a96f7af9fa7233bc92af0bc2d5b9d521661d509c0e693e603cbdac5e58c00a01a27e05bdb6cec80fc9a8ce3de22ae1104f6308be8e06f7f9f00133c2738d8c268983da3b33c13efcd163aceb53656826f0b87b58059c0a383cb1651e00d4e90b354429789fbfbfc80f1824b90d249f0dc308f5f841a53d8d9b28b84712c4a4c0bffe2f40c111f237f1dddd0ac52f13178fc65c357cc4c8b033c3d44dffbf906d37cb827053017b99ffb696f15f8afd6e9519129cbf
[ 9.515704] I:failed to verify against RSA key 0
[ 9.515721] I:SHA-256 digest: 0af57a569628abf43e0cb2ba4316da9a0fb47150217255413d0574d3a10dafc6
[ 9.515729] E:failed to verify whole-file signature
[ 9.535726] Update package verification took 9.1 s (result 1).
[ 9.563312] E:Signature verification failed
[ 9.577467] E:error: 21
This is the log from a succesful update with the original update.zip:
Spoiler: Log
[ 0.350442] Finding update package...
[ 0.393154] I:Update location: @/cache/recovery/block.map
[ 0.393354] Opening update package...
[ 0.413638] I:mmapped 2 ranges
[ 0.414972] I:1 key(s) loaded from /system/etc/security/otacerts.zip
[ 0.414988] Verifying update package...
[ 0.436744] I:comment is 1578 bytes; signature is 1560 bytes from end
[ 9.442515] I:signature (offset: 71e1be37, length: 612): 3082060e06092a864886f70d010702a08205ff308205fb020101310f300d06096086480165030402010500300b06092a864886f70d010701a0820403308203ff308202e7a003020102020900e98c7b3de8706cb3300d06092a864886f70d01010b0500308195310b300906035504061302434e3112301006035504080c094775616e67446f6e673116301406035504070c0d5368656e5a68656e2056696577310b3009060355040a0c0251463111300f060355040b0c0852657365617263683114301206035504030c0b6c69756875616c69616e673124302206092a864886f70d01090116157169616e66656e67407169616e66656e672e636f6d301e170d3232303130383038333635325a170d3439303532363038333635325a308195310b300906035504061302434e3112301006035504080c094775616e67446f6e673116301406035504070c0d5368656e5a68656e2056696577310b3009060355040a0c0251463111300f060355040b0c0852657365617263683114301206035504030c0b6c69756875616c69616e673124302206092a864886f70d01090116157169616e66656e67407169616e66656e672e636f6d30820122300d06092a864886f70d01010105000382010f003082010a0282010100b29877a044433c5e55eef1d900b4ff257e7fc54ab7a4c7914837af0765f35c3db4f8de39831b9c76304f365f4537f5aec31f3ccf83f8744bcfcf9be4c40fe92e36edf4a0d50799e07cd3a3dfb17ce13e970de7b2d57aa1a5bc4109fe800c3f97976e077387a99cfa57a0f0252fa0fa4ef5203e098dbaf600fa5ded6e35eba8c2150ad858daf29dda5064ca881d46a2a20492258c4f20d26615f618aa334404a5198c4440292f751553eceb7cb3f0b4b7e4ddba4891f0ebfc1a7894f692300d1575ef4367f8508a24e72b6aaccd0dea8dbefb54e2b48658f939988a8bf117e3fa12d18971d48c8bcad9f80aa215602bd8dfc53946e320e32dbef09fe278a9bdbd0203010001a350304e301d0603551d0e04160414d9c898e436cc674380bf1eb3325629d87cd4eb81301f0603551d23041830168014d9c898e436cc674380bf1eb3325629d87cd4eb81300c0603551d13040530030101ff300d06092a864886f70d01010b0500038201010036bcd486a789ae6ab4d7166e50cfadcdcf6a0232e329f0b5117bda3f4ebd1b8e6d3fa7f37f7e25cdc830816b95b05b59f47c4db469af6741c0081e21f0033f74869bb2a34cac9364942cb8f7b0759f9b007aed92a655eb00fb1ba0bfa3ed663d80346417a4a96f56068d972e07fba6daee389bdbab0e46b88e9026eddce3c50dfb8f47a2f0604ebb4d0f8abe67673476303e3a4693a0db5ca1081c8c1179330cca5b01c7be0fd431bfa292ca9b6e1f56e6eea8a4aba1d43c71973b43bb82d9bff36d38413a45ae731286ba02aabe14cf5c0437b155b287d1623045df6cef6652347a252af4719b50da4b3d11ab7241c2a4b876043158c159271b5322c5a5eef9318201cf308201cb0201013081a3308195310b300906035504061302434e3112301006035504080c094775616e67446f6e673116301406035504070c0d5368656e5a68656e2056696577310b3009060355040a0c0251463111300f060355040b0c0852657365617263683114301206035504030c0b6c69756875616c69616e673124302206092a864886f70d01090116157169616e66656e67407169616e66656e672e636f6d020900e98c7b3de8706cb3300d06096086480165030402010500300d06092a864886f70d010101050004820100339e68dcbca8358da77d66f3431891c68e0600dbf95f0f609b7c3c1de7df356103c9fb3b1cda8596bd247339cef1c51abc912189bd662f8b79cfc46933b388f5a8d3e3216a89acd7cc09a9b5567547027eb7c75e63216ea4a9b1a72acdac49ca52c11461016ec275a551cda67944cb6de3d5274fccd33f21794181a22bfb1d58cc603f61603e416c9da99b8aae015d9747ee3a9265709e5236601ff0bd981cefb03f538ace162e10721d1bfbc2716c94b28e2f42b0ef9472f188929c7b4fa8625e7b1a4df35d267b6706f62d66ec0d55a2b7db8049065871720ba4ff0d98d829c09ecac2d4533d187f22f4523bddddf344f4524e1c57f447f44516c1d4a8b00d
[ 9.442825] I:whole-file signature verified against RSA key 0
[ 9.442863] Update package verification took 9.0 s (result 0).
[ 9.448867] I:Verifying package compatibility...
[ 9.466881] Installing update...
I also replaced the releasekey.x509.pem inside /system/etc/security/otacerts.zip with the testkey certificat from the signapkv2 folder. But that did not work too.
Any ideas how i can update my device with the modified update.zip?
Cheers
blue_one

Thread closed!
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com