|
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 | Mark Forums Read |
| LinkBack | Thread Tools | Display Modes |
09-18-2018, 09:52 | #1 (permalink) | |
No Life Poster Join Date: Apr 2003 Location: Torun, Poland Age: 40
Posts: 1,195
Member: 25996 Status: Offline Thanks Meter: 253 | DC-Phoenix PRA-LXA1 flashing PRA-LX1C432B211,PRA-L11C432B211,PRA-L31C432B211.zip PRA-LX1C432B385 (8.0.0.385),PRA-L31C432B385 (8.0.0.385),PRA-L11C432B385 (8.0.0.385),PRA-LX1C432B383 (8.0.0.383),PRA-L31C432B383 (8.0.0.383),PRA-L11C432B383 (8.0.0.383).zip PRA-LX1C432B195,PRA-L11C432B195,PRA-L31C432B195,PRA-LX1C432B196,PRA-L11C432B196,PRA-L31C432B196.zip PRA-LX1C432B370 (8.0.0.370).zip etc. I tried with board software Prague-AL00A_HL1PRAMAA001036_Board Software_general_Android 7.0_EMUI 5.0_05022DCA.dgtks following by Prague-L31_C432B164_Firmware_Germany_Portugal_Switzerland _France_Spain_Netherlands_Belg.APP and PRA-L31_C432B164_update_data_customization_hw_eu.APP but still nothing. Essentially phone boots either to logo and hangs there or directly boots into erecovery only. I can't seem to be able to flash it fully in upgrade mode. I immediatelly see 5%, then it reboots after a while mid-flashing each time. It looks like there might be a software package somewhere that's being used rather than via cable. I don't have microSD card inside, i tried factory reset but still the same. Quote:
| |
09-18-2018, 10:58 | #2 (permalink) |
Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas
Posts: 4,690
Member: 2023196 Status: Offline Thanks Meter: 1,891 | You need to flash board software alone in advanced mode, and then you need to see if phone boots up, if it does then it's still repairable, if it isn't then it's only main board replacement for it. |
09-18-2018, 11:08 | #3 (permalink) | |
No Life Poster Join Date: Apr 2003 Location: Torun, Poland Age: 40
Posts: 1,195
Member: 25996 Status: Offline Thanks Meter: 253 | OK. I flashed board software (for P8 Lite 2017) - Prague-AL00A_HL1PRAMAA001036_Board Software_general_Android 7.0_EMUI 5.0_05022DCA.dgtks from support. Seems it was flashed fine, but phone did not reboot automatically, it stayed in fastboot with bootloader locked. Aftere rebooting it (fastboo reboot) it automatically boots into fastboot with "ap_s_panic, data is invalid, reboot_panic_and_wdt_process_func" reboot reason and bootloader is unlocked. Quote:
| |
09-18-2018, 12:50 | #4 (permalink) |
No Life Poster Join Date: Feb 2003 Location: Hungary Age: 40
Posts: 524
Member: 22869 Status: Offline Thanks Meter: 132 | I think original android was 8.0, thats why you cannot finish because different partitions on the phone. Probably with an 8.0 dktks file we could revive the phone (I have similar problem with one) |
09-18-2018, 13:08 | #5 (permalink) | ||
No Life Poster Join Date: Apr 2003 Location: Torun, Poland Age: 40
Posts: 1,195
Member: 25996 Status: Offline Thanks Meter: 253 | I tried fullota-mf with Android 8 and it still doesn't help. Plus, it is rebooting in factory mode. It looks like like there is an update file somewhere that it is trying to use instead but i'm no expert here. Quote:
Quote:
| ||
09-18-2018, 17:01 | #7 (permalink) |
No Life Poster Join Date: Apr 2003 Location: Torun, Poland Age: 40
Posts: 1,195
Member: 25996 Status: Offline Thanks Meter: 253 | @Namelocked, any other suggestion regarding that phone or there nothing more that can be done? This is a common issue with this model from what i noticed. Any idea what can be the source of the problem? |
09-19-2018, 08:03 | #8 (permalink) |
Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas
Posts: 4,690
Member: 2023196 Status: Offline Thanks Meter: 1,891 | If board software flashing alone does not revive phone, then there is a high chance that problem now lies in device's hardware, other than that, do not know what other issues may be reason of this. |
09-19-2018, 10:03 | #9 (permalink) | |
No Life Poster Join Date: Feb 2003 Location: Hungary Age: 40
Posts: 524
Member: 22869 Status: Offline Thanks Meter: 132 | Quote:
Guys have no idea for oreo support ever be added or not, seems they selling as many activations as possible and its already a dead product since no new phones released with nougat. Game over for now | |
09-19-2018, 17:01 | #10 (permalink) | ||
No Life Poster Join Date: Apr 2003 Location: Torun, Poland Age: 40
Posts: 1,195
Member: 25996 Status: Offline Thanks Meter: 253 | Quote:
I don't see such partition being flashed in my case. Downgrading might be an issue here, but it's hard to say. From what customer told me, phone "bricked" itself during OTA update and in erocovery it tried to download C432B211 firmware - this is rather old one. I had couple other PRA-LX1 phones with same issue in the past and all ended in up Huawei service center with swapped boards. This one has cracked back so this won't be an option. I'm wondering what's the real source of the problem and if this can be verified somehow. I tried flashing TWRP since bootloader is currently unlocked, but most likely due to OEM lock not being enabled (userlock is active in fastboot) this is not possible. I tried swapping recovery for TWRP during flash with DC-Unlocker but it's still the same so i guess dc-unlocker doesn't allow to flash any firmware and it has to be a signed one to flash. Quote:
| ||
09-19-2018, 18:32 | #11 (permalink) |
No Life Poster Join Date: Feb 2003 Location: Hungary Age: 40
Posts: 524
Member: 22869 Status: Offline Thanks Meter: 132 | finally I done it! Flashed factory 7.0 fw, no bootup Flashed APP file, exactly same version which displayed in the read info (or on fastboot info) - got erecovery, but still failed Put update.app to the sdcard's dload folder Flashed again dgtks + app + custom - still not booting up BUT erecovery started, and somehow flashed the files put on the SD card (not the latest version available!) after phone boot up, repaired everything and now testing |
09-20-2018, 09:17 | #13 (permalink) |
No Life Poster Join Date: Feb 2003 Location: Hungary Age: 40
Posts: 524
Member: 22869 Status: Offline Thanks Meter: 132 | it was PRA-LX1C02B365 fullota but its not relevant for your case, you should use the same as the phone displays on fastboot: Code: fastboot oem get-build-number |
The Following User Says Thank You to fofesz For This Useful Post: |
09-20-2018, 14:29 | #14 (permalink) | ||
No Life Poster Join Date: Apr 2003 Location: Torun, Poland Age: 40
Posts: 1,195
Member: 25996 Status: Offline Thanks Meter: 253 | Quote:
Currently, in fastboot after flashing board firmware i only get Quote:
Which seems to be a board firmware version. Even if i flash another firmware on top of it, version still stays the same. | ||
09-20-2018, 19:35 | #15 (permalink) |
No Life Poster Join Date: Feb 2003 Location: Hungary Age: 40
Posts: 524
Member: 22869 Status: Offline Thanks Meter: 132 | I was trying to debrand after repair, and didnt succeed Seems on 8.0 android the repair of vendor & country not works, after repair I got build number seem strange (8.0.0.045 0EN4 instead ....365) What can change this is TWRP restore of backup (oeminfo, vendor, etc) And still, somehow the flash file put on sdcard's dload version is what the erecovery downloads but only the original oeminfo works. You should check by IMEI what was the original operator and try flashing that |
The Following User Says Thank You to fofesz For This Useful Post: |
Bookmarks |
Thread Tools | |
Display Modes | |
| |
|