|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
| LinkBack | Thread Tools | Display Modes |
03-13-2019, 16:08 | #1 (permalink) |
No Life Poster Join Date: Aug 2012 Location: under pross
Posts: 2,469
Member: 1798174 Status: Offline Sonork: 100.114149 Thanks Meter: 1,048 | ALE-L21 flash error 13/03/2019 15:48:22 Starting to write device in FASTBOOT mode... File to update: ALE-L21_ALE-L02_ALE-L23__MAA001078_Board Software_inc_testpoint.dgtks Device detected: COM68: HUAWEI USB COM 1.0 (COM68) Writing bootloader... Writing ALE-L21_ALE-L02_ALE-L23__MAA001078_Board Software_inc_testpoint_4.dtwork... Writing ALE-L21_ALE-L02_ALE-L23__MAA001078_Board Software_inc_testpoint_5.dtwork... Waiting for fastboot device... Device found: QLF7N15618013873 Looking for a device in fastboot mode Device found: QLF7N15618013873 SN:QLF7N15618013873 Build number: :ALE-L21C02B589 Model: :ALE-L21 Battery state: 2191mv Erasing nvme partition ERASE partition nvme : FAIL partition does not exist Erasing cust partition ERASE partition cust : FAIL partition does not exist Writing ptable partition ptable partition UPDATE ...OK Writing fastboot1 partition fastboot1 partition UPDATE :FAIL flash write prim vrl failure Trying to unlock device... Writing fastboot1 partition fastboot1 partition UPDATE :FAIL flash write prim vrl failure Writing fastboot partition fastboot partition UPDATE :FAIL flash write prim vrl failure Writing mcuimage partition mcuimage partition UPDATE :FAIL flash write prim vrl failure Writing nvme partition nvme partition UPDATE ...OK Writing modemimage partition modemimage partition UPDATE :FAIL flash write prim vrl failure Writing dsp partition dsp partition UPDATE :FAIL flash write prim vrl failure Writing hifi partition hifi partition UPDATE :FAIL flash write prim vrl failure Writing recovery partition recovery partition UPDATE :FAIL flash write prim vrl failure Writing splash2 partition splash2 partition UPDATE ...OK Writing boot partition boot partition UPDATE :FAIL flash write prim vrl failure Writing dtimage partition dtimage partition UPDATE :FAIL flash write prim vrl failure Erasing cache partition Partition cache erased Writing cache partition cache partition UPDATE ...OK Writing system partition sending sparse file 469762048 bytes send sparse file OK sending sparse file 469762048 bytes send sparse file OK sending sparse file 213188724 bytes send sparse file OK system partition UPDATE ...OK Erasing userdata partition Partition userdata erased Writing userdata partition userdata partition UPDATE ...OK Writing trustfirmware partition trustfirmware partition UPDATE :FAIL flash write prim vrl failure Writing teeos partition teeos partition UPDATE :FAIL flash write prim vrl failure Writing securetystorage partition securetystorage partition UPDATE ...OK Software written 13/03/2019 15:52:54 Writing device finished - INCOMPLETE thanks in advance |
03-13-2019, 17:25 | #2 (permalink) |
Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas
Posts: 4,690
Member: 2023196 Status: Offline Thanks Meter: 1,891 | Which dc-phoenix version you are using and what android version your phone ran when it got broken? |
The Following User Says Thank You to Namelocked For This Useful Post: |
03-14-2019, 10:27 | #4 (permalink) |
Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas
Posts: 4,690
Member: 2023196 Status: Offline Thanks Meter: 1,891 | Ok, try to use loader + oeminfo solution for now, and see if phone remain in fastboot after that. If it does try to flash full stock rom matching that oeminfo data that you wrote. |
The Following User Says Thank You to Namelocked For This Useful Post: |
03-15-2019, 11:38 | #6 (permalink) |
Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas
Posts: 4,690
Member: 2023196 Status: Offline Thanks Meter: 1,891 | Which full stock rom you trying to flash and what oeminfo data you wrote in when you flashed loader + oeminfo? |
The Following User Says Thank You to Namelocked For This Useful Post: |
03-15-2019, 13:18 | #7 (permalink) | |
No Life Poster Join Date: Aug 2012 Location: under pross
Posts: 2,469
Member: 1798174 Status: Offline Sonork: 100.114149 Thanks Meter: 1,048 | Quote:
ALE-L21_C432B605_Firmware_Italy_Netherlands_Nonspecifi c_Nonspecific_Android_6.0_EMUI_4.0.3.APP update OEMINFO +LOADER also not accepted i try with this loader Kirin658_T0_A7 V1 & 659 | |
03-15-2019, 17:16 | #8 (permalink) |
Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas
Posts: 4,690
Member: 2023196 Status: Offline Thanks Meter: 1,891 | If it does not flash board software and loader + oeminfo flashing also not successful then no way to repair. |
The Following User Says Thank You to Namelocked For This Useful Post: |
Bookmarks |
| |
|