Hi all,
I'm trying to install a ROM that I built on my device, but what I did it didn't work.
I downloaded RUU (exe) file, extracted it, found the file rom.zip, and extracted the file system.img from this zip.
When I try with fastboot (fastboot flash system system.img) I get the error:
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
When I build update.zip with dsixda kitchen, put it in /sdcard, and go to receovery, I get various errors.
What can I do?
Huawei NXT-L09 (Messi Edition)
I was on EMUI 4.1, decided to root and install Link2SD, could not write to 2nd partition (Mount scripts) so I tried App2SD, after an error I tried on of the option to edit something in the system to possibly fix the mounting script issue.
Anyway, rebooting into bootloop and tried to flash one of the Stock Roms I found on the forums, started with L09-B321 Stock-Rooted. Got to the Booting... screen and it just sits there for hours. Probably messed up my attempting to place another rom L29-B180, same deal stuck on the text that says Booting...
Tried Italian Knife (Decrypted Boot), did not try unbrick as I cannot find the files that it requests (.img's)
I still have TWRP 3.0.2, Fastboot worked, Bootloader Unlocked.
Not sure how to proceed, I have no idea what version I was on.
Marshmallow
EMUI 4.1 (95% sure it was 4.1)
Open to recommendations, thanks!
Update: I thought I installed TWRP 3.0.2 (Name of the file I have), however UI in Recovery says TWRP Mate 8 v2.8.7.0
Can no longer boot into TWRP Recovery, it stays on booting now....
Followed this link:
http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934
Proceeded to Flashed the .img from the UPDATE.APP (Cust, Recovery, System and Boot) [I ripped with the Huawei Update Extractor] from a NXT-L09C636B170 stock rom found here: http://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727 via ItalianKnife (Unbrick option)
Everything went Okay, and phone has rebooted and still on : "...device has been unlocked..... Your device is booting now", will leave it on this screen overnight and see if by morning it loaded.
Additional Information:
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : HUAWEI NXT-L09
Model : Huawei phone in fastboot mode
IMEI : 86XXXXXXXXX7
Serial NR. : AXXXXXXXXXXX66
Firmware : NXT-L09C605B100
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 2978mv
Solved - Sort of...
RECOVERED from Soft Brick with the DC_Phoenix software (EUR 15.00)
Only thing available to me before brick was Bootloader
No Recovery
No eRecovery (Huawei 3 button press or Vol Up for 3 seconds on Prompt
Maybe this helps someone, these are the files that were used, with this following Stock ROM:
NXT-L09C605B100 from the XDA Stock Rom post.
I erased IMEI, SN, Directories from Code.
Code:
Current version: NextL09C999B100
Extracting partitions
Cannot create extract directory: D:\X\DC_Phoenix\tmp\20160804_104858_UPDATE\
Extract files to directory: D:\X\Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM OK
Extracting partition: MODEM_DSP OK
Extracting partition: 3RDMODEM OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Extracting partition: MODEM_DTB OK
Device found: AXXXXXXXXXXXXXXXX6
IMEI: 8XXXXXXXXXXXXXXXX7
Build number: :NXT-L09C605B100
Product model: HUAWEI NXT-L09
Writing XLOADER partition with file D:\X\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file D:\X\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file D:\UX\DC_Phoenix\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file D:\X\DC_Phoenix\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file D:\X\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file D:\X\DC_Phoenix\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file D:\X\DC_Phoenix\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file D:\X\DC_Phoenix\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file D:\X\DC_Phoenix\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file D:\X\DC_Phoenix\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file D:\X\DC_Phoenix\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file D:\X\DC_Phoenix\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file D:\X\DC_Phoenix\DTS.img
DTS partition UPDATE ...OK
Writing MODEM partition with file D:\X\DC_Phoenix\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file D:\X\DC_Phoenix\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file D:\X\DC_Phoenix\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Writing SYSTEM partition with file D:\X\DC_Phoenix\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file D:\X\DC_Phoenix\CUST.img
CUST partition UPDATE ...OK
Writing MODEM_DTB partition with file D:\X\DC_Phoenix\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Software written
8/4/2016 10:56:16 AM Writing device finished OK
Hi all.
I somehow managed to get my LG-P505R in what I believe to be a soft-bricked state.
I can access fastboot mode as well as emergency mode. I have tried to flash the stock kdz file following probably just about all guides I could locate here. I have also tried to flash recovery.img (clockworkmod image also), boot.img and system.mbn via fastboot but am still unable to boot into either system or recovery. I have all of the .mbn files extracted from the original kdz file and I would like to try to flash them through fastboot. My issue is that I do not know which mbn file goes to which partition. I also am not too sure of the exact partition names to flash.
I have tried the obvious ones like, fastboot flash amss amss.mbn. The result is
sending 'partition' (0 KB)...
OKAY [ 0.046s]
writing 'partition'...
FAILED (remote: unknown partition name)
finished. total time: 0.096s
same result with all except for recovery, boot, system and splash.
Here is a list of the files extracted from kdz if the info can help.
amss.mbn
amsshd.mbn
appsboot.mbn
appsboothd.mbn
boot.img
oemsbl.mbn
oemsblhd.mbn
partition.mbn
qcsbl.mbn
qcsblhd_cfgdata.mbn
recovery.img
splash.img
system.mbn
the system.mbn is originally extracted in 3 different files, system.mbn.0, system.mbn.1 and system.mbn.2
Does anyone have any insight on how I might be able to recover?
When me flash system.img than this error show
Invaild sparse file format at header magic
Do a Google search for "Invaild sparse file format at header magic": hundreds of results will be shown.
here the error:
error validating footer and error verifying vbmeta image:: invaild vbmeta header (6) CUSTOM RECOVERY VBMETA A515FXXU5FVD2, 507061148
benhur1123 said:
here the error:
error validating footer and error verifying vbmeta image:: invaild vbmeta header (6) CUSTOM RECOVERY VBMETA A515FXXU5FVD2, 507061148
Click to expand...
Click to collapse
Flash new firmware