[HELP!] Groundhog Day of my Defy - Defy General

I've buy used Defy. Seller say me:
Point -1 "I tried to update update it on my pc and I got stuck on bootloader with Code corrupt message".
Point 0 After 3 weeks delivery battery was full discharged, so I plug charger, and see battery's animation.
Point 1 Normal boot of Android. I see all previous users data: SMS, call log, photos, games, etc...
Ok! Reboot to stock recovery -> wipe data/factory reset -> wipe cash -> reboot.
And all exactly as befor a factory reset. Return to Point 1.
Point 2 Of course - RSDLite and stock.sbf - it can quick resolve of all problems, as I've think naively.
Code:
02:05:44, February 11, 2012
Line: 537
ERROR: AP Die ID: 15000109f11468010000dcff0200
02:05:44, February 11, 2012
Line: 544
ERROR: BP Die ID: 0000000000000000000000000000
02:05:45, February 11, 2012
Line: 551
ERROR: AP Public ID: d0e71bd823eaaf9db675d65371b6e26df979ea09
02:05:45, February 11, 2012
Line: 558
ERROR: BP Public ID: 0000000000000000000000000000000000000000
02:08:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x4805, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:12:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:12:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 33 checksums. File: 0x8BAC, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:16:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:16:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 34 checksums. File: 0xAB80, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:17:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:17:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 35 checksums. File: 0x100C, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:18:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:18:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 39 checksums. File: 0xC7E6, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:19:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:19:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 42 checksums. File: 0x4BB7, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:20:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:20:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 45 checksums. File: 0x738D, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:21:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:21:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 47 checksums. File: 0x45F0, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:22:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:22:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 53 checksums. File: 0xFDFF, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:23:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:23:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 61 checksums. File: 0x4A7C, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:24:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:24:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 64 checksums. File: 0x85D0, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:25:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:25:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 65 checksums. File: 0x2409, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:25:33, February 11, 2012
Line: 1194
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
02:25:33, February 11, 2012
Line: 610
ERROR: Flash failure: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x4805, Phone: 0x4A05 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=32
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
After flashing failed, phone start in bootloader only, and message "Code corrupt" below boot version. Return to Point -1.
Point 3 Short circuit of battery on motherboard was restore phone's normal boot, and now return to Point 1.
I've flash with about 10 different official .sbf, all with same result - Point -1.
I've get root, install 2ndInit - and reboot to Point 1.
I've get root and write CG47 directly to dev/block/mmcblk1p16, then reboot to recovery -> wipe data/factory reset -> wipe cash -> reboot... And return to Point 1 again.

Probably the flash memory is corrupted/damaged from wear and cannot be erased or something...

U can try sbf_flash on Linux...
Sent from my MB525 using xda premium

nogoodusername said:
U can try sbf_flash on Linux...
Click to expand...
Click to collapse
Already tried, same result as RSD Lite.
Good morning.
- You off to see the groundhog?
- I am.
Click to expand...
Click to collapse

TorAll said:
Already tried, same result as RSD Lite.
Click to expand...
Click to collapse
Same, but not at all!
I've tried sbf_flash --groupnane full.sbf step by step.
Succesfully flashed:
CG64 0xB0000000-0xB001FFFF mbr
CG65 0xB0180000-0xB01FFFFF ebr
CG31 0xB0280000-0xB02FFFFF cdt.bin
CG34 0xB0700000-0xB077FFFF lbl
CG61 0xB0B00000-0xB0B7FFFF devtree
CG53 0xB2F00000-0xB32FFFFF kpanic
What this mean, who can answer me?

on what sbf are you now? (in about screen on phone)

Could it be that it was flashed with some sbf that had version 6 or version 7 CG before it got to you? Have you tried flashing some DEFY+ ROM? Or maybe that version 6 Froyo?

But then he wouldn't be able to flash CG31 :s
Think there is really something wrong :/
I would try warranty?
Seems to be not the only one :
http://forum.xda-developers.com/showthread.php?t=1485289

labsin said:
on what sbf are you now? (in about screen on phone)
Click to expand...
Click to collapse
3.4.2-107_jdn-9
labsin said:
I would try warranty?
Seems to be not the only one
http://forum.xda-developers.com/showthread.php?t=1485289
Click to expand...
Click to collapse
Warranty... too sweet for me Motorola fell out of love Russia.
I've searched too, and find couple peaples, who had troubles like me. As far as I know, they dont resolved it.

I have the same problem you have found a solution?

Related

HTC 7 Pro, share some thoughts on solving this bootloader problem.

I have a HTC 7 Pro:
7.10.7720.68
2250.10.10701.207
0002
3.2.2250.0
Ever since I have the tri color single line brick I have been trying to fix it. Just now I finally found a working 7008 backup from zune. And I succesfully restored it to my phone. But that didnt fix the bootloader.
What I have tried:
wp7 cab sender:
I get 80180048, 81030120 or 801812E0 trying to use the cab sender to force the O2ODEHTGoldHTCOEMUpdate2011.cab for instance. Every cab I try failed to update.
The only working cab was this one:
diff-7.10.7720.68-7.10.7740.16-armv7-retail-microsoft.pks_2cb1bfdd82133914239b8ee1a78e61e9000d124a.cab
So what can I do? I can restore a 7008 backup succesfully.
I can restore my 7.10.7720.68 backup succesfully.
However all Zune updates, or HTC OEM Updates fail when I have 7.10.7720.68 restored on my phone.
And bootloader is stuck at 3.2.2250.0
Is there anyway I can repair my SPL/Bootloader? Goldcard needs to have a USB Host mode right? But since I have the tri color one line screen, a goldcard would not fix my problem, can someone confirm this?
I am currently updating thru zune from my working 7008 backup. 7392 has been succesful, at this very moment 7.0.7403 is installing. I hope it complete.
How do I downgrade from bootloader 3.2.2250.0? Any Idea? Help me fix please. Share your thoughts.
Thank you
Luca+
UPDATE:
Update: 7403 update also worked thru zune. bootloader still 3.2.2250 and it will stay. It will update the OS but the bootloader will stay .
Update:
Yesterday I was able to revert to 7008 the first time and I was happy cause I thought now I can fix it somehow.
Problem as I expected is: I cant go past update 7403 thru tune. When trying to install Update 7.10.7720.68 thru zune this happens:
Zune downloads Updates, Transfers them, then restarts my phone to the connect-to-pc screen and then it sais installing update 0%. It will remain in this state for about 2 minutes and then restarts and I get error 0x80180048. Here is the log:
================================================
START OF UPDATEVALIDATOR ERROR MESSAGES
================================================
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\QC_8x50_ULDR_BOOT.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {DE19F4CF-9586-45CF-B803-CC4BA0313E12}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: QC_8x50_ULDR_BOOT cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\QC_8x50_ULDR.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {6939BB9F-56E4-47F3-AF2A-01DDFB414825}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: QC_8x50_ULDR cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_ULDR_GOLD.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {AE4DA1E8-3522-4302-9FD3-1F9F042C9B52}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_ULDR_GOLD cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_ULDR_BOOT_SURF.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {DD824642-CB6C-4801-806C-B6AF8F46B4BE}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_ULDR_BOOT_SURF cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_ULDR.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {E090DA69-D370-45D2-AC98-388576C8625F}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_ULDR cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_ULDR_BOOT.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {BE1A39E2-C197-44BE-80F9-D3F33649F520}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_ULDR_BOOT cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\HTC_8x50_ULDR_UI.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {AF4607D-5A02-45DD-BF58-58CC6E29C4A0}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_8x50_ULDR_UI cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: UpdateOrderFromFileList: ULDR Update: ULDR Update Failed with HRESULT : 0x80180048
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\QC_8x50_NK.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {9B696E96-49E9-44C7-BB3D-B2BD1C833920}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: QC_8x50_NK cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_NK_GOLD.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {1A76BBCD-1005-475E-849C-BC16FEF739A0}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_NK_GOLD cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\HTC_NKDrivers.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {EE52C775-D0EA-49B1-BFED-CC1F0351EA0C}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_NKDrivers cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_NK_SURF.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {23668647-E6FF-4DD1-AC15-C53AF46B3D67}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_NK_SURF cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\HTC_Flashlight.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {7F974147-2C11-438E-808D-F01890CE42E9}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_Flashlight cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\QC_8x50_NK_PMEM_CFG_2.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {49439A2C-D5C8-4CC0-AA42-63828307B1CA}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: QC_8x50_NK_PMEM_CFG_2 cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\QC_8x50_OS.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {C7A5B7A5-BBF6-49F6-AA76-36A581FA92AD}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: QC_8x50_OS cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\HTC_Global_Customization.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {38603AE6-281C-4015-8243-8343C3A9C61A}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_Global_Customization cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\HTC_8x50_OS_WIRELESS.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {A2A5F44F-FE02-496E-8926-6EDDC8CF9B44}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_8x50_OS_WIRELESS cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\HTC_OEMAPPS.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {47C557C0-08B2-493C-A380-08C72D78E3BA}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_OEMAPPS cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_OS_SURF.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {880E6B3C-1DF0-4C83-A820-C36DD6A9560A}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_OS_SURF cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\HTC_8x50_OS_UI_COMMON.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {5180F0DC-9ECB-4422-A250-212959EBD147}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_8x50_OS_UI_COMMON cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\HTC_AppDrivers.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {FA96EAAF-C79F-4F59-AD9C-21435347E9FC}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_AppDrivers cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\QC_8x50_OS_MMRIL.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {569ADD71-2080-405D-A718-923A7A2AF490}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: QC_8x50_OS_MMRIL cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\HTC_OSDrivers.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {8832CC7E-2E59-4DBA-8C93-9FEF47A1E390}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_OSDrivers cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_OS_CAMERA.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {C6158F86-EF71-4A8B-8C04-0CF57C158B2F}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_OS_CAMERA cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\QC_8x50_OS_GPS.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {F0FF42A5-5093-496B-8B2F-38B63870278A}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: QC_8x50_OS_GPS cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_OS.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {2E754FF0-EFF9-4889-BBF7-5AEE67424523}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_OS cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\HTC_8x50_OS_UI_GOLD.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {796FBEF3-ACAF-451C-A591-087D03F0ED05}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_8x50_OS_UI_GOLD cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\QC_8x50_OS_MM_CFG_2.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {A3573D54-12B2-4A91-84F6-C572F7703393}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: QC_8x50_OS_MM_CFG_2 cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_MODEM.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {15B74B9D-D86C-4E9E-967E-11BFEAAD51E3}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_MODEM cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_LOGO.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {3C224231-CA68-4B7A-ABA7-63DC88EDA715}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_LOGO cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_BLDR.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {828A5FA1-00B2-408A-9026-5302DE54E402}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_BLDR cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\OEM_8x50_BSP.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {3EDB4086-7899-474A-AA93-28BA766DA2CB}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: OEM_8x50_BSP cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: UpdateOrderFromFileList: MAIN OS Update: MAIN OS Update Failed with HRESULT : 0x80180048
=====================================================================
GOOD PACKAGES AND BAD PACKAGES LIST
=====================================================================
UpdateOrderFromFileList failed with code 0x80180048
BAD PACKAGE 1 : QC_8x50_ULDR_BOOT.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 2 : QC_8x50_ULDR.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 3 : OEM_8x50_ULDR_GOLD.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 4 : OEM_8x50_ULDR_BOOT_SURF.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 5 : OEM_8x50_ULDR.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 6 : OEM_8x50_ULDR_BOOT.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 7 : HTC_8x50_ULDR_UI.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 8 : QC_8x50_NK.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 9 : OEM_8x50_NK_GOLD.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 10 : HTC_NKDrivers.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 11 : OEM_8x50_NK_SURF.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 12 : HTC_Flashlight.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 13 : QC_8x50_NK_PMEM_CFG_2.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 14 : QC_8x50_OS.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 15 : HTC_Global_Customization.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 16 : HTC_8x50_OS_WIRELESS.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 17 : HTC_OEMAPPS.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 18 : OEM_8x50_OS_SURF.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 19 : HTC_8x50_OS_UI_COMMON.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 20 : HTC_AppDrivers.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 21 : QC_8x50_OS_MMRIL.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 22 : HTC_OSDrivers.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 23 : OEM_8x50_OS_CAMERA.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 24 : QC_8x50_OS_GPS.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 25 : OEM_8x50_OS.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 26 : HTC_8x50_OS_UI_GOLD.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 27 : QC_8x50_OS_MM_CFG_2.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 28 : OEM_8x50_MODEM.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 29 : OEM_8x50_LOGO.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 30 : OEM_8x50_BLDR.cab.pkg ERROR CODE: 0x80180008
BAD PACKAGE 31 : OEM_8x50_BSP.cab.pkg ERROR CODE: 0x80180008
Total number of Bad Packages: 31
Process Failed with code 0x80180048
UpdateValidator finished at 08:02:22 01/06/1980 <----------- Why is the date wrong here?
Any ideas? Martin7pro said
See full update log, if possible. May be, only a part of update want missing certificates. Only MODEM.cab from pkg is really needed for unbrick. Ask somebody in UpdateCabSender thread, I do not understand to certificates magement. Try Windows Phone Support Tool (MS solution for 80180048 error). M.
Click to expand...
Click to collapse
Support Tool sais: The tool cannot recover this phone. Please contact technical support.
Reverting back to 7008 has been a downstep now. I have spent so many hours trying to solve this...
What happens if I take out the SD card and format it. is there a internal backup on the rom to solve this issue?
I am no pro, but the log file shows that there are things missing that the 7.10.7720 needs to have have in order to update.
Bring some light into my darkness ^^
Is there a way to deploy these files into the directory manually? WHat do these logs mean? Are there certain files missing, resulting in this update disaster?
Please could someone just tell me wether there is a possibility to fix this OR tell me that its not possible so I can finally give it back to the shop and have experts at HTC fix it.
Here are some more logs:
================================================
START OF UPDATEAPP INFO MESSAGES
================================================
Setting the installing update state.
ERROR: 0x80180048 : Updatevalidator in ULDR reported this error. Update cannot continue.
Error during update: Function: UpdateMain::StartUpdate, Line: 1346, Hr: 0x80180048, GetLastError: 0
Update failed. hr = 0x80180048
Update Application - Completed Post Update @ 00:00:46
Update Application - Returning 0x80180048
Attempting to clear the 'installing IU' update state
succeeded
Clearing the persistent update flag.
succeeded
=====================================================================
ULDR OS UPDATE START
=====================================================================
=====================================================================
FOLLOWING PACKAGES ARE ALREADY PART OF THE BASE IMAGE ON THE DEVICE: Searching \ULDR2
=====================================================================
Found Base Package \ULDR2\3bed3629-af98-4f2a-8274-a225d203c9b1.dsm.
Adding Package: MSXIPKERNEL_uldr
Package GUID = {3BED3629-AF98-4F2A-8274-A225D203C9B1} Package Version: 7.10.7720.68
Interface GUID = {0000-0000-0000-0000-000000000000} Interface Version: 0.0.0.0
Found Base Package \ULDR2\65827abb-b824-4994-bd6d-6a4657482987.dsm.
Adding Package: IUCORE
Package GUID = {65827ABB-B824-4994-BD6D-6A4657482987} Package Version: 7.10.7720.68
Interface GUID = {CD1A0DBC-51AE-4AAE-B308-CAA46A0DB74B} Interface Version: 0.0.0.0
Found Base Package \ULDR2\233078d8-5dfe-4cb4-990e-7c883968ce03.dsm.
Adding Package: BaseDrivers_ULDR_OS
Package GUID = {233078D8-5DFE-4CB4-990E-7C883968CE03} Package Version: 7.10.7720.68
Interface GUID = {18ED86C7-88D8-4A50-85CF-8920BF01CA81} Interface Version: 0.0.0.0
Found Base Package \ULDR2\596c1c95-b566-4918-8d66-c420b54174ec.dsm.
Adding Package: ULDRCRYPTO
Package GUID = {596C1C95-B566-4918-8D66-C420B54174EC} Package Version: 7.10.7720.68
Interface GUID = {7304A89A-1CDF-4DE7-ADCF-F85592F8203D} Interface Version: 7.0.0.0
VerifySignatures failed for graph with base name of HTC_8x50_ULDR_UI. Trying to find another path.
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_8x50_ULDR_UI cannot find a path to highest expected version of: 2250.21.30201.207
BuildReturnValues: Returning HRESULT 0x80180048
ERROR: UpdateOrderFromFileList: ULDR Update: ULDR Update Failed with HRESULT : 0x80180048
=====================================================================
MAIN OS UPDATE START
=====================================================================
MESSAGE: 15 RESERVED Section(s) found on this Device
=====================================================================
FOLLOWING PACKAGES ARE ALREADY PART OF THE BASE IMAGE ON THE DEVICE: Searching \NK
=====================================================================
Found Base Package \NK\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm.
Adding Package: MSXIPKERNEL
Package GUID = {B5332311-48F1-4B76-AD70-8EFA5DB8FA3A} Package Version: 7.10.7720.68
Interface GUID = {0000-0000-0000-0000-000000000000} Interface Version: 0.0.0.0
Found Base Package \NK\eebbabb2-0689-4692-9e80-5eb9a62126d1.dsm.
Adding Package: BaseDrivers_NK
Package GUID = {EEBBABB2-0689-4692-9E80-5EB9A62126D1} Package Version: 7.10.7720.68
Interface GUID = {96B1E6DD-B30E-42C6-85E9-233CB33E6BD2} Interface Version: 0.0.0.0
Can anyone provide me with links to Htc 7 Pro cabs, files? If I format the SD, and boot the phone with cleared SD, will it work at all anymore?
There must be a way to fix this damn bootloader....
goldcard?
Have you unlocked OS?
How have you downgrade to 7008?
Have you dev-unlocked OS now?
If yes, you can do anything manually (files and registry changing).
If not, I am not sure, but I mean Chevron old version can work also on 7008 (7004 certainly).
OK martin, but how can I fix my bootloader if files are missing?
can you help me with a short tutorial?
After many tries I managed to restore 7008 with zune.
ok got regedit working. I managed to update to 7740. however bootloader still at 3.xx
how can I fix the reg so the oemupdate with SPL bootloader will work?
See my translated unbrick manual. BEFORE mango update try change registry values, which are changed by U2M7720, to MS original, or try use "DoNot U2B2" feature. If no success, write me, we will try more.

Need help for fixing these errors occurred during compiling cm 14

I am compiling cm 14 for core prime ve 3g (sm-g361h).
i am getting these error after executing mka bacon command (i have skipped all log above errors). I am building rom from source first time so i ain't got any clue what this error says (maybe a little bit but that ain't helping).
Code:
device/samsung/coreprimeve3g/ril/SamsungSPRDRIL.java:276: error: method does not override or implement a method from a supertype
@Override
^
device/samsung/coreprimeve3g/ril/SamsungSPRDRIL.java:314: error: method processSolicited in class RIL cannot be applied to given types;
return super.processSolicited(p);
^
required: Parcel,int
found: Parcel
reason: actual and formal argument lists differ in length
device/samsung/coreprimeve3g/ril/SamsungSPRDRIL.java:366: error: method does not override or implement a method from a supertype
@Override
^
device/samsung/coreprimeve3g/ril/SamsungSPRDRIL.java:422: error: method processUnsolicited in class RIL cannot be applied to given types;
super.processUnsolicited(p);
^
required: Parcel,int
found: Parcel
reason: actual and formal argument lists differ in length
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
4 errors
[ 3% 1018/28725] host C++: libLLVMCor...2 <= external/llvm/lib/IR/Function.cpp
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/hamza/cm14'
#### make failed to build some targets (27:37 (mm:ss)) ####
bump

Build ResurrectionRemix V5.8.0 - Nougat for D855

Hi everyone !
I try to build RR from myself for the D855. The nougat version : V5.8.0 !
I followed the guide in RR android_manifest github : https://github.com/ResurrectionRemix/platform_manifest.
I build with Archlinux.
The process fail because of the prebuid package Gello. I don't know why, maven cannot download the apk.
Code:
FAILED: /home/julian/android/RR/out/target/common/obj/APPS/Gello_intermediates/org.cyanogenmod.gello-40.apk
/bin/bash -c "(mvn -q org.apache.maven.plugins:maven-dependency-plugin:2.10:get org.apache.maven.plugins:maven-dependency-plugin:2.10:copy -DremoteRepositories=central::::https://maven.cyanogenmod.org/artifactory/gello_prebuilds -Dartifact=org.cyanogenmod:gello:40:apk -Dmdep.prependGroupId=true -Dmdep.overWriteSnapshots=true -Dmdep.overWriteReleases=true -Dtransitive=false -DoutputDirectory=/home/julian/android/RR/out/target/common/obj/APPS/Gello_intermediates/ )"
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:get (default-cli) on project standalone-pom: Couldn't download artifact: Could not transfer artifact org.cyanogenmod:gello:apk:40 from/to central (https://maven.cyanogenmod.org/artifactory/gello_prebuilds): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[ERROR] org.cyanogenmod:gello:apk:40
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false),
[ERROR] central (https://maven.cyanogenmod.org/artifactory/gello_prebuilds, releases=true, snapshots=true)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ 52% 17961/34013] target Package: Eleven (/home/julian/android/RR/out/target/product/d855/obj/APPS/Eleven_intermediates/package.apk)
Warning: AndroidManifest.xml already defines versionCode (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines versionName (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines minSdkVersion (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines targetSdkVersion (in http://schemas.android.com/apk/res/android); using existing value in manifest.
[ 52% 17961/34013] Building with Jack: /home/julian/android/RR/out/target/common/obj/APPS/Exchange2_intermediates/with-local/classes.dex
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
make: Leaving directory `/home/julian/android/RR'
[COLOR="Red"]#### make failed to build some targets (19:06 (mm:ss)) ####[/COLOR]
Why are there some prebuild packages ?
How can I build them from source ? Or how can I remove then from my build ?
I did not find information on cynogenmod wiki (archive.org). Maybe because of the cyanogen shutdown, there is no way to build CM.
Thanks !
Julian

I cant make kernel

when i try make kernel
i have this problem
arch/arm64/kernel/entry-fpsimd.S: Assembler messages:
arch/arm64/kernel/entry-fpsimd.S:53: Error: unexpected end of file in irp or irpc
/tmp/ccm5MNfe.s: Error: local label `"0" (instance number 1 of a fb label)' is not defined
scripts/Makefile.build:294: recipe for target 'arch/arm64/kernel/entry-fpsimd.o' failed
make[1]: *** [arch/arm64/kernel/entry-fpsimd.o] Error 1
Makefile:974: recipe for target 'arch/arm64/kernel' failed
make: *** [arch/arm64/kernel] Error 2
mi a2 lite daisy-p-oss
Which toolchain u use?
Ahmed Hady said:
Which toolchain u use?
Click to expand...
Click to collapse
i use UBERTC aarch64-linux-android-4.9 toolchain
mrfirt said:
i use UBERTC aarch64-linux-android-4.9 toolchain
Click to expand...
Click to collapse
Try google aarch64 4.9 first
https://android.googlesource.com/pl...nux-android-4.9/+/refs/tags/android-9.0.0_r32
i do that but i have now that problem
Android GCC has been deprecated in favor of Clang, and will be removed from
Android in 2020-01 as per the deprecation plan in:
https://android.googlesource.com/pl...ost/linux-x86/+/master/GCC_4_9_DEPRECATION.md
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: Android: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: GCC: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: has: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: been: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: deprecated: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: in: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: favor: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: of: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: Clang,: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: and: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: will: No such file or directory
Android GCC has been deprecated in favor of Clang, and will be removed from
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: be: No such file or directory
Android in 2020-01 as per the deprecation plan in:
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: removed: No such file or directory
https://android.googlesource.com/pl...ost/linux-x86/+/master/GCC_4_9_DEPRECATION.md
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: from: No such file or directory
make[2]: *** Waiting for unfinished jobs....
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: the: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: deprecation: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: plan: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: in:: No such file or directory
921d9846-a815-11e9-84ea-ff8bce1b90b6: error: https://android.googlesource.com/pl...st/linux-x86/+/master/GCC_4_9_DEPRECATION.md: No such file or directory
scripts/Makefile.build:154: recipe for target 'scripts/mod/devicetable-offsets.s' failed
make[2]: *** [scripts/mod/devicetable-offsets.s] Error 1
scripts/Makefile.build:403: recipe for target 'scripts/mod' failed
make[1]: *** [scripts/mod] Error 2
Makefile:560: recipe for target 'scripts' failed
make: *** [scripts] Error 2
make: *** Waiting for unfinished jobs....
Ahmed Hady said:
Try google aarch64 4.9 first
https://android.googlesource.com/pl...nux-android-4.9/+/refs/tags/android-9.0.0_r32
Click to expand...
Click to collapse
Ahmed Give me any way to get in touch with you and thanks in advance

ninja: build stopped: subcommand failed.

I have been building LineageOS 15.1 for Samsung S6 and S6 Edge for a while without any real issues.
I am using my own 'zero' repo's that are duplicates of the ones available on the official LineageOS github repo with a few local fixes.
My build environment is an Ubuntu 16.04 VM. The build tools recently forced me to upgrade to Python 3.6.3 which I had to install manually.
Since then the build fails whilst compiling the Exynos7420 Kernel. The error message seems to vary but its always at the Exynos7420 kernel part.
I am building with my own certificates so the script is a little different from a standard LineageOS build:
Code:
source build/envsetup.sh
breakfast zeroltexx
mka target-files-package dist otatools
The last lines of the output and the error I got the last time:
Code:
[ 0% 2/93156] Generated: (/home/andy/android...ut/target/product/zeroltexx/android-info.txt)
FAILED: /home/andy/android/lineage/out/target/product/zeroltexx/android-info.txt
/bin/bash -c "(build/tools/check_radio_versions.py ) && (echo \"board=universal7420\" > /home/andy/android/lineage/out/target/product/zeroltexx/android-info.txt )"
File "build/tools/check_radio_versions.py", line 56
print "*** Error opening \"%s.sha1\"; can't verify %s" % (fn, key)
^
SyntaxError: invalid syntax
[ 0% 7/93156] Building Kernel Config
make: Entering directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
GEN /home/andy/android/lineage/out/target/product/zeroltexx/obj/KERNEL_OBJ/Makefile
Kconfig:15:warning: environment variable ANDROID_MAJOR_VERSION undefined
arch/arm64/configs/lineageos_zeroltexx_defconfig:624:warning: override: reassigning to symbol INET_DIAG
#
# configuration written to .config
#
make: Leaving directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
make: Entering directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
GEN /home/andy/android/lineage/out/target/product/zeroltexx/obj/KERNEL_OBJ/Makefile
scripts/kconfig/conf --savedefconfig=defconfig Kconfig
Kconfig:15:warning: environment variable ANDROID_MAJOR_VERSION undefined
make: Leaving directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
ninja: build stopped: subcommand failed.
19:27:22 ninja failed with: exit status 1
#### failed to build some targets (08:22 (mm:ss)) ####
Any pointers as to how I debug this? It must be something to do with the upgrade to python 3.6.3, however I am not skilled in the arts of scripting...
Cheers
Andy
If I clean everything out of the /out folder and re-run the commands it always fails at the same point:
Code:
FIPS : Generating hmac of fmp and updating vmlinux...
HMAC-SHA256(builtime_bytes.bin)= 5d384fe6b55f757aa0ef31391e8cbb5ffb947cd886235203f2690988f879aec8
FIPS : Generating hmac of crypto and updating vmlinux...
HMAC-SHA256(builtime_bytes.bin)= d6e18e7da3d688cd63ab5598991c05bd4c538f71d383fbe7e9f668f23d1e040a
OBJCOPY arch/arm64/boot/Image
make: Leaving directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
Building DTBs
make: Entering directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
CC scripts/mod/devicetable-offsets.s
GEN scripts/mod/devicetable-offsets.h
HOSTCC scripts/mod/file2alias.o
HOSTLD scripts/mod/modpost
make[2]: Nothing to be done for 'dtbs'.
make: Leaving directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
Building Kernel Modules
make: Entering directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
GEN /home/andy/android/lineage/out/target/product/zeroltexx/obj/KERNEL_OBJ/Makefile
CHK include/generated/uapi/linux/version.h
Using /home/andy/android/lineage/kernel/samsung/exynos7420 as source for kernel
CHK include/generated/utsrelease.h
CC scripts/mod/devicetable-offsets.s
GEN scripts/mod/devicetable-offsets.h
HOSTCC scripts/mod/file2alias.o
CALL /home/andy/android/lineage/kernel/samsung/exynos7420/scripts/checksyscalls.sh
HOSTLD scripts/mod/modpost
Building modules, stage 2.
MODPOST 0 modules
/home/andy/android/lineage/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule
/home/andy/android/lineage/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '/lib/firmware/abov/abov_valley.fw' given more than once in the same rule
make: Leaving directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
ninja: build stopped: subcommand failed.
23:05:52 ninja failed with: exit status 1
#### failed to build some targets (17:53 (mm:ss)) ####
Anyone?
ADB100 said:
If I clean everything out of the /out folder and re-run the commands it always fails at the same point:
Code:
FIPS : Generating hmac of fmp and updating vmlinux...
HMAC-SHA256(builtime_bytes.bin)= 5d384fe6b55f757aa0ef31391e8cbb5ffb947cd886235203f2690988f879aec8
FIPS : Generating hmac of crypto and updating vmlinux...
HMAC-SHA256(builtime_bytes.bin)= d6e18e7da3d688cd63ab5598991c05bd4c538f71d383fbe7e9f668f23d1e040a
OBJCOPY arch/arm64/boot/Image
make: Leaving directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
Building DTBs
make: Entering directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
CC scripts/mod/devicetable-offsets.s
GEN scripts/mod/devicetable-offsets.h
HOSTCC scripts/mod/file2alias.o
HOSTLD scripts/mod/modpost
make[2]: Nothing to be done for 'dtbs'.
make: Leaving directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
Building Kernel Modules
make: Entering directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
GEN /home/andy/android/lineage/out/target/product/zeroltexx/obj/KERNEL_OBJ/Makefile
CHK include/generated/uapi/linux/version.h
Using /home/andy/android/lineage/kernel/samsung/exynos7420 as source for kernel
CHK include/generated/utsrelease.h
CC scripts/mod/devicetable-offsets.s
GEN scripts/mod/devicetable-offsets.h
HOSTCC scripts/mod/file2alias.o
CALL /home/andy/android/lineage/kernel/samsung/exynos7420/scripts/checksyscalls.sh
HOSTLD scripts/mod/modpost
Building modules, stage 2.
MODPOST 0 modules
/home/andy/android/lineage/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule
/home/andy/android/lineage/kernel/samsung/exynos7420/scripts/Makefile.fwinst:45: target '/lib/firmware/abov/abov_valley.fw' given more than once in the same rule
make: Leaving directory '/home/andy/android/lineage/kernel/samsung/exynos7420'
ninja: build stopped: subcommand failed.
23:05:52 ninja failed with: exit status 1
#### failed to build some targets (17:53 (mm:ss)) ####
Anyone?
Click to expand...
Click to collapse
I know it's old, but did you manage to solve it?
I have the same problem

Categories

Resources