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
Related
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?
my p2 got hard brick, no way to enter to fastboot and recovery, even with any configuration button, when connected to pc i only get red blinking led, screen show blank, and in pc device manager just show Qualcomm HS-USB QDLoader 9008, no solution how to Resurrected from death even with qfil tool or miflash tool, luckily now back to live after 3 month death, here what i did:
before all started, first recharge your p2 for 1/2 an hour to make sure enough battery more than 20%,
install lenovo p2 usb driver: https://mega.nz/#!rQgjACaJ!-ZVi7TDUgtVaUVEe7yGZ-jr4ijarO704T7x2IQdVjeU,
install qualcomm usb driver:
https://mega.nz/#!GNRWiQrJ!ASpU78MPYzh-I4EUiK_ba5YtlZUTQHP_r_P4Dd7hSZg
reboot your pc,
connect your p2 to pc,
go to pc device manager, you will see in pc device manager like in screenshot, if you didn't see like that press vol +and- togather with power button, hold all of them till appear like screenshoot
now download zip file blankflash tool https://mega.nz/#!PIZ0GChJ!3RhdFN38IajIVYQT_5ppZGxcconOntG1-d75vNK1Vg8, extract it, and place it in c folder your pc,
open folder and run blank-flash.bat,
automaticly your p2 will start reboot to fastboot,
or if your rom still intack p2 will reboot to system os,
Or if no os, now you can flash rom from fastboot
congratulation now your p2 back to live.
hendibudi said:
my p2 got hard brick, no way to enter to fastboot and recovery, even with any configuration button, when connected to pc i only get red blinking led, screen show blank, and in pc device manager just show Qualcomm HS-USB QDLoader 9008, no solution how to Resurrected from death even with qfil tool or miflash tool, luckily now back to live after 3 month death, here what i did:
before all started, first recharge your p2 for 1/2 an hour to make sure enough battery more than 20%,
install lenovo p2 driver,
reboot your pc,
connect your p2 to pc,
go to pc device manager,
you will see in pc device manager like in screenshot,
now download zip file blankflash tool, extract it, and place it in c folder your pc,
open folder and run blank-flash.bat,
automaticly your p2 will start reboot to fastboot,
or if your rom still intack p2 will reboot to system os,
congratulation now your p2 back to live
Click to expand...
Click to collapse
Thanks! Please post a link to download that BlankFlash Tool.
kermex said:
Thanks! Please post a link to download that BlankFlash Tool.
Click to expand...
Click to collapse
When upload finished there is link
hendibudi said:
When upload finished there is link
Click to expand...
Click to collapse
Great! Thanks again!
hendibudi said:
my p2 got hard brick, no way to enter to fastboot and recovery, even with any configuration button, when connected to pc i only get red blinking led, screen show blank, and in pc device manager just show Qualcomm HS-USB QDLoader 9008, no solution how to Resurrected from death even with qfil tool or miflash tool, luckily now back to live after 3 month death, here what i did:
before all started, first recharge your p2 for 1/2 an hour to make sure enough battery more than 20%,
install lenovo p2 driver,
reboot your pc,
connect your p2 to pc,
go to pc device manager,
you will see in pc device manager like in screenshot,
now download zip file blankflash tool, extract it, and place it in c folder your pc,
open folder and run blank-flash.bat,
automaticly your p2 will start reboot to fastboot,
or if your rom still intack p2 will reboot to system os,
congratulation now your p2 back to live
Click to expand...
Click to collapse
Waiting for download link. Will this fix no signal issue? Does it have non-holos.bin? Also if my device is working can I use that tool?
Sent from my Lenovo P2 using Tapatalk
abhayruparel said:
Waiting for download link. Will this fix no signal issue? Does it have non-holos.bin? Also if my device is working can I use that tool?
Sent from my Lenovo P2 using Tapatalk
Click to expand...
Click to collapse
No download link. I'm waiting for it, too. Maybe he doesn't want to share this.
kermex said:
No download link. I'm waiting for it, too. Maybe he doesn't want to share this.
Click to expand...
Click to collapse
Be patients for couple of days, compare to me waiting 3 months my p2 death back to live, cause i have limited data
hendibudi said:
Be patients for couple of days, compare to me waiting 3 months my p2 death back to live, cause i have limited data
Click to expand...
Click to collapse
Why you don't use wifi?!
kermex said:
Why you don't use wifi?!
Click to expand...
Click to collapse
Where?
hendibudi said:
Where?
Click to expand...
Click to collapse
He meant that why don't you use Wi-Fi for uploading. Please reply to #5
OK, thanks! Just forgot about this.
the laptop loses the portconnection and I get
readfile() failed , getlastError()=31
anny idea how to fix this?
Datech2 said:
after identifying CPU I get
the laptop loses the portconnection and I get
readfile() failed , getlastError()=31
anny idea how to fix this?
Click to expand...
Click to collapse
How about p2
hendibudi said:
How about p2
Click to expand...
Click to collapse
no reaction , the red led keeps blinking ,
when push de power button and the volume + he reconnects
Datech2 said:
no reaction , the red led keeps blinking ,
when push de power button and the volume + he reconnects
Click to expand...
Click to collapse
Check first post step by step
Yes blankflash method works. But I must push VolDown + Power buttons in the right moment to done it properly.
So below are my instructions. I also put my log. Without pushing the buttons I have IOError.
1. Install Latest Qualcomm 9008 Driver from link below and restart PC:
androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
2. Download flashbank.zip from link below
mega.nz/#!PIZ0GChJ!3RhdFN38IajIVYQT_5ppZGxcconOntG1-d75vNK1Vg8
3. Unpack archive to C:\lenovo (or other directory if you are poweruser and you will know what to change in steps below)
4. Open cmd and go to C:\lenovo\
5. Turn off the phone, and connect to USB, in Device Manager you should see Qualcomm 9008 device in Ports (LPT & COMM) section (or something like this)
6. Push VolumeDown + Power buttons together
7. In cmd run command below
qboot blank-flash
8. When in cmd text below appear, release VolumeDown + Power buttons
Waiting for firehose to get ready ......
9. Now the phone should boot into Fastboot
My log:
C:\lenovo>qboot blank-flash
Opening device: \\.\COM3
OKAY [ 0.004s]
Detecting device
...cpu.id = 70 (0x46)
...cpu.sn = 2326272297 (0x8aa81929)
OKAY [ 7.010s]
Opening singleimage
OKAY [ 0.001s]
Loading package
...filename = bootloader.qboot.xml
OKAY [ 0.011s]
Loading programmer
...filename = programmer.mbn
OKAY [ 0.007s]
Sending programmer
OKAY [ 0.247s]
Handling things over to programmer
Waiting for firehose to get ready ......
Identifying CPU
...MSM8953 1.1
Storage Information
...physical partition number: 0
...num_partition_sectors=61071360
...SECTOR_SIZE_IN_BYTES=512
...num_physical_partitions=3
...MFR_ID=144
...OEM_ID=74
...Product name=HBG4a2
...{"storage_info": {"total_blocks":61071360, "block_size":512, "page_size":512, "num_physical":3, "mfr_id":144, "serial_num":574148832, "fw_version":"164","mem_type":"eMMC", "prod_name":"HBG4a2"}}
Flashing partition sbl1 with sbl1.mbn (375KB)
....100%
Flashing partition sbl1bak with sbl1.mbn (375KB)
....100%
Flashing partition rpm with rpm.mbn (170KB)
..100%
Flashing partition rpmbak with rpm.mbn (170KB)
..100%
Flashing partition tz with tz.mbn (1447KB)
.....100%
Flashing partition tzbak with tz.mbn (1447KB)
.....100%
Flashing partition devcfg with devcfg.mbn (36KB)
..100%
Flashing partition devcfgbak with devcfg.mbn (36KB)
..100%
Flashing partition aboot with emmc_appsboot.mbn (854KB)
....100%
Flashing partition abootbak with emmc_appsboot.mbn (854KB)
....100%
Flashing partition lksecapp with lksecapp.mbn (56KB)
....100%
Flashing partition lksecappbak with lksecapp.mbn (56KB)
....100%
Flashing partition cmnlib with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlibbak with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlib64 with cmnlib64.mbn (249KB)
..100%
Flashing partition cmnlib64bak with cmnlib64.mbn (249KB)
..100%
Flashing partition keymaster with keymaster.mbn (220KB)
..100%
Flashing partition keymasterbak with keymaster.mbn (220KB)
..100%
Flashing partition prov with prov32.mbn (64KB)
....100%
Flashing partition PrimaryGPT with gpt_main0.bin (17KB)
..100%
Flashing partition BackupGPT with gpt_backup0.bin (16KB)
....100%
Patching DISK -- Update last partition 56 'userdata' with actual size in Primary Header.
Patching DISK -- Update last partition 56 'userdata' with actual size in Backup Header.
Patching DISK -- Update Primary Header with LastUseableLBA.
Patching DISK -- Update Backup Header with LastUseableLBA.
Patching DISK -- Update Primary Header with BackupGPT Header Location.
Patching DISK -- Update Backup Header with CurrentLBA.
Patching DISK -- Update Backup Header with Partition Array Location.
Patching DISK -- Update Primary Header with CRC of Partition Array.
Patching DISK -- Update Backup Header with CRC of Partition Array.
Patching DISK -- Zero Out Header CRC in Primary Header.
Patching DISK -- Update Primary Header with CRC of Primary Header.
Patching DISK -- Zero Out Header CRC in Backup Header.
Patching DISK -- Update Backup Header with CRC of Backup Header.
OKAY [ 4.572s]
finished. total time: 11.861s
It worked like charm.[emoji106][emoji106][emoji106]
Sent from my Lenovo P2a42 using Tapatalk
I lost sim modem after flashing stock firmware
Anyway to restore it?
You'd only do this to restore fastboot or, if possible, boot into an existing OS, right? There's no way of recovering a lost signal by flashing modem?
slimok5 said:
Yes blankflash method works. But I must push VolDown + Power buttons in the right moment to done it properly.
So below are my instructions. I also put my log. Without pushing the buttons I have IOError.
1. Install Latest Qualcomm 9008 Driver from link below and restart PC:
androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
2. Download flashbank.zip from link below
mega.nz/#!PIZ0GChJ!3RhdFN38IajIVYQT_5ppZGxcconOntG1-d75vNK1Vg8
3. Unpack archive to C:\lenovo (or other directory if you are poweruser and you will know what to change in steps below)
4. Open cmd and go to C:\lenovo\
5. Turn off the phone, and connect to USB, in Device Manager you should see Qualcomm 9008 device in Ports (LPT & COMM) section (or something like this)
6. Push VolumeDown + Power buttons together
7. In cmd run command below
qboot blank-flash
8. When in cmd text below appear, release VolumeDown + Power buttons
Waiting for firehose to get ready ......
9. Now the phone should boot into Fastboot
My log:
C:\lenovo>qboot blank-flash
Opening device: \.\COM3
OKAY [ 0.004s]
Detecting device
...cpu.id = 70 (0x46)
...cpu.sn = 2326272297 (0x8aa81929)
OKAY [ 7.010s]
Opening singleimage
OKAY [ 0.001s]
Loading package
...filename = bootloader.qboot.xml
OKAY [ 0.011s]
Loading programmer
...filename = programmer.mbn
OKAY [ 0.007s]
Sending programmer
OKAY [ 0.247s]
Handling things over to programmer
Waiting for firehose to get ready ......
Identifying CPU
...MSM8953 1.1
Storage Information
...physical partition number: 0
...num_partition_sectors=61071360
...SECTOR_SIZE_IN_BYTES=512
...num_physical_partitions=3
...MFR_ID=144
...OEM_ID=74
...Product name=HBG4a2
...{"storage_info": {"total_blocks":61071360, "block_size":512, "page_size":512, "num_physical":3, "mfr_id":144, "serial_num":574148832, "fw_version":"164","mem_type":"eMMC", "prod_name":"HBG4a2"}}
Flashing partition sbl1 with sbl1.mbn (375KB)
....100%
Flashing partition sbl1bak with sbl1.mbn (375KB)
....100%
Flashing partition rpm with rpm.mbn (170KB)
..100%
Flashing partition rpmbak with rpm.mbn (170KB)
..100%
Flashing partition tz with tz.mbn (1447KB)
.....100%
Flashing partition tzbak with tz.mbn (1447KB)
.....100%
Flashing partition devcfg with devcfg.mbn (36KB)
..100%
Flashing partition devcfgbak with devcfg.mbn (36KB)
..100%
Flashing partition aboot with emmc_appsboot.mbn (854KB)
....100%
Flashing partition abootbak with emmc_appsboot.mbn (854KB)
....100%
Flashing partition lksecapp with lksecapp.mbn (56KB)
....100%
Flashing partition lksecappbak with lksecapp.mbn (56KB)
....100%
Flashing partition cmnlib with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlibbak with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlib64 with cmnlib64.mbn (249KB)
..100%
Flashing partition cmnlib64bak with cmnlib64.mbn (249KB)
..100%
Flashing partition keymaster with keymaster.mbn (220KB)
..100%
Flashing partition keymasterbak with keymaster.mbn (220KB)
..100%
Flashing partition prov with prov32.mbn (64KB)
....100%
Flashing partition PrimaryGPT with gpt_main0.bin (17KB)
..100%
Flashing partition BackupGPT with gpt_backup0.bin (16KB)
....100%
Patching DISK -- Update last partition 56 'userdata' with actual size in Primary Header.
Patching DISK -- Update last partition 56 'userdata' with actual size in Backup Header.
Patching DISK -- Update Primary Header with LastUseableLBA.
Patching DISK -- Update Backup Header with LastUseableLBA.
Patching DISK -- Update Primary Header with BackupGPT Header Location.
Patching DISK -- Update Backup Header with CurrentLBA.
Patching DISK -- Update Backup Header with Partition Array Location.
Patching DISK -- Update Primary Header with CRC of Partition Array.
Patching DISK -- Update Backup Header with CRC of Partition Array.
Patching DISK -- Zero Out Header CRC in Primary Header.
Patching DISK -- Update Primary Header with CRC of Primary Header.
Patching DISK -- Zero Out Header CRC in Backup Header.
Patching DISK -- Update Backup Header with CRC of Backup Header.
OKAY [ 4.572s]
finished. total time: 11.861s
Click to expand...
Click to collapse
Hey I am stack on identifying the cpu
---------- Post added at 01:43 PM ---------- Previous post was at 01:34 PM ----------
slimok5 said:
Yes blankflash method works. But I must push VolDown + Power buttons in the right moment to done it properly.
So below are my instructions. I also put my log. Without pushing the buttons I have IOError.
1. Install Latest Qualcomm 9008 Driver from link below and restart PC:
androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
2. Download flashbank.zip from link below
mega.nz/#!PIZ0GChJ!3RhdFN38IajIVYQT_5ppZGxcconOntG1-d75vNK1Vg8
3. Unpack archive to C:\lenovo (or other directory if you are poweruser and you will know what to change in steps below)
4. Open cmd and go to C:\lenovo\
5. Turn off the phone, and connect to USB, in Device Manager you should see Qualcomm 9008 device in Ports (LPT & COMM) section (or something like this)
6. Push VolumeDown + Power buttons together
7. In cmd run command below
qboot blank-flash
8. When in cmd text below appear, release VolumeDown + Power buttons
Waiting for firehose to get ready ......
9. Now the phone should boot into Fastboot
My log:
C:\lenovo>qboot blank-flash
Opening device: \.\COM3
OKAY [ 0.004s]
Detecting device
...cpu.id = 70 (0x46)
...cpu.sn = 2326272297 (0x8aa81929)
OKAY [ 7.010s]
Opening singleimage
OKAY [ 0.001s]
Loading package
...filename = bootloader.qboot.xml
OKAY [ 0.011s]
Loading programmer
...filename = programmer.mbn
OKAY [ 0.007s]
Sending programmer
OKAY [ 0.247s]
Handling things over to programmer
Waiting for firehose to get ready ......
Identifying CPU
...MSM8953 1.1
Storage Information
...physical partition number: 0
...num_partition_sectors=61071360
...SECTOR_SIZE_IN_BYTES=512
...num_physical_partitions=3
...MFR_ID=144
...OEM_ID=74
...Product name=HBG4a2
...{"storage_info": {"total_blocks":61071360, "block_size":512, "page_size":512, "num_physical":3, "mfr_id":144, "serial_num":574148832, "fw_version":"164","mem_type":"eMMC", "prod_name":"HBG4a2"}}
Flashing partition sbl1 with sbl1.mbn (375KB)
....100%
Flashing partition sbl1bak with sbl1.mbn (375KB)
....100%
Flashing partition rpm with rpm.mbn (170KB)
..100%
Flashing partition rpmbak with rpm.mbn (170KB)
..100%
Flashing partition tz with tz.mbn (1447KB)
.....100%
Flashing partition tzbak with tz.mbn (1447KB)
.....100%
Flashing partition devcfg with devcfg.mbn (36KB)
..100%
Flashing partition devcfgbak with devcfg.mbn (36KB)
..100%
Flashing partition aboot with emmc_appsboot.mbn (854KB)
....100%
Flashing partition abootbak with emmc_appsboot.mbn (854KB)
....100%
Flashing partition lksecapp with lksecapp.mbn (56KB)
....100%
Flashing partition lksecappbak with lksecapp.mbn (56KB)
....100%
Flashing partition cmnlib with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlibbak with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlib64 with cmnlib64.mbn (249KB)
..100%
Flashing partition cmnlib64bak with cmnlib64.mbn (249KB)
..100%
Flashing partition keymaster with keymaster.mbn (220KB)
..100%
Flashing partition keymasterbak with keymaster.mbn (220KB)
..100%
Flashing partition prov with prov32.mbn (64KB)
....100%
Flashing partition PrimaryGPT with gpt_main0.bin (17KB)
..100%
Flashing partition BackupGPT with gpt_backup0.bin (16KB)
....100%
Patching DISK -- Update last partition 56 'userdata' with actual size in Primary Header.
Patching DISK -- Update last partition 56 'userdata' with actual size in Backup Header.
Patching DISK -- Update Primary Header with LastUseableLBA.
Patching DISK -- Update Backup Header with LastUseableLBA.
Patching DISK -- Update Primary Header with BackupGPT Header Location.
Patching DISK -- Update Backup Header with CurrentLBA.
Patching DISK -- Update Backup Header with Partition Array Location.
Patching DISK -- Update Primary Header with CRC of Partition Array.
Patching DISK -- Update Backup Header with CRC of Partition Array.
Patching DISK -- Zero Out Header CRC in Primary Header.
Patching DISK -- Update Primary Header with CRC of Primary Header.
Patching DISK -- Zero Out Header CRC in Backup Header.
Patching DISK -- Update Backup Header with CRC of Backup Header.
OKAY [ 4.572s]
finished. total time: 11.861s
Click to expand...
Click to collapse
Phone boot into fastboot but no light
I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.
cmorin543 said:
I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.
Click to expand...
Click to collapse
Hello,
I wonder ? do you have pixel 3 phone?
I see that you have the bootloader of the crossheath for the google pixel 3 XL installed.
bootloader-crosshatch-b1c1-0.1-5191736.img
Maybe you should download the google pixel 3 OTA or Factory.img.
That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.
cmorin543 said:
That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.
Click to expand...
Click to collapse
Succes, and let me know if you succeeded flashing.
9.0.0 (PQ2A.190405.003, Apr 2019) Link c12f40f0b189eb2daa80d029917bc9a8841da89cfcafa21b8f61b0d9f90826e7
Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.
I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.
cmorin543 said:
Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.
Click to expand...
Click to collapse
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!
wangdaning said:
I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.
Click to expand...
Click to collapse
I should've mentioned that I did do the format of userdata at one point and it didn't make a difference.
sakerhetz said:
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!
Click to expand...
Click to collapse
I tried using the flash_all.bat with no joy and I also tried using twrp (when I was actually able to boot into it) to sideload the OTA zip still with no joy.
I think I'm just going to contact Google and see what they can do -- the phone is technically still under warranty and I am still able to re-lock the bootloader... I appreciate the help.
Maybe try:
1) fastboot erase userdata
2) flash-all.bat
If no good:
1) fastboot erase userdata
2) fastboot format userdata
3) flash-all.bat
Everything will be gone, but already is from what you have said.
if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.
SacredDeviL666 said:
if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.
Click to expand...
Click to collapse
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
I will double check that. Thanks!
cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
just to confirm.
a) you booted to bootloader using power + volume down key and then use volume down key to change it to bootloader and press power again (this reboots the bootloader)
b) while you are inside the ADB folder use shift + right click while you are inside the adb folder and then select the option -- open command window here.
c) considering that you have already connected your pixel to pc via usb type the command " fastboot devices " in the command prompt window to ensure that your device is detected.
d) once it has detected the device/s proceed to unzip the april factory image from https://dl.google.com/dl/android/aosp/blueline-pq2a.190405.003-factory-c12f40f0.zip in the same folder as ADB
e) Double click on flash.all bat file and let us know the result.
I am sure you might have followed above steps but just to make sure if everything is covered. as the above should actually fix all partition errors.
pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
You are a genius -- apparently I did have the newest version of ADB in my downloads folder, but I was so used to using a specific directory with platform-tools for my old phone, I didn't realize it was an old version -- tried it with the newest version of ADB and it worked like a charm... too bad I already contacted google and they're sending me a new phone.. :-\
Thanks again for all your help guys.
It seems my slot A is dead. No matter what I try I cannot boot to it.
I've tried flash.android.com to flash back to stock, even tried going back to Pie, and back to Q, but still Slot A is dead.
With stock Pie I flashed TWRP and tried flashing custom ROM to both slots, but slot A always fails.
Tried sideloading factory OTA and LineageOS, but it keeps failing.
Tried ./flash-all.sh using a few different ROMs, stock and CalyxOS, but it always fails with the following error.
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8537 KB)...
OKAY [ 0.340s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.2-6374987
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.279s]
finished. total time: 0.619s
rebooting into bootloader...
OKAY [ 0.060s]
finished. total time: 0.110s
target reported max download size of 268435456 bytes
sending 'radio_a' (71436 KB)...
OKAY [ 2.050s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00107-200409-B-6382632
(bootloader) Flashing partition modem_a
OKAY [ 0.418s]
finished. total time: 2.467s
rebooting into bootloader...
OKAY [ 0.060s]
finished. total time: 0.110s
extracting android-info.txt (0 MB)...
extracting boot.img (64 MB)...
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (787 MB)...
archive does not contain 'system.sig'
extracting system_other.img (152 MB)...
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (440 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6374987
Baseband Version.....: g845-00107-200409-B-6382632
Serial Number........: 96KX220PE
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
When slot A is active and I run fastboot flash boot boot.img for installing LineageOS, it will not boot to recovery, but if I set slot B active and do that then recovery works fine.
Do you have the most recent platform tools, and are you definitely launching the ./flash-all from the platform tools folder and not a path referencing an older version (AKA the version of fastboot and ADB that install from apt)?
sliding_billy said:
Do you have the most recent platform tools, and are you definitely launching the ./flash-all from the platform tools folder and not a path referencing an older version (AKA the version of fastboot and ADB that install from apt)?
Click to expand...
Click to collapse
Can you explain how to do that?
What I am doing is downloading the zip file from developer.google.com under Factory Images. Then I unzip that file open the folder and find the flash-all.sh file, open terminal in that folder and run the file using command ./flash-all.sh
Is there a way to run that file from somewhere other than where it is located?
The Lepricon said:
Can you explain how to do that?
What I am doing is downloading the zip file from developer.google.com under Factory Images. Then I unzip that file open the folder and find the flash-all.sh file, open terminal in that folder and run the file using command ./flash-all.sh
Is there a way to run that file from somewhere other than where it is located?
Click to expand...
Click to collapse
Extract the .zip directly into your platform tools folder and then with that folder open right click and open terminal from the folder. That is easier than changing your terminal path and should result in the ./ running directly from that place. Again, be sure you are running the current platform tools.
Hi, I'm not sure if you wrongly wrote the file extension, but shouldn't you run the flash-all.bat instead of the flash-all.sh?
Vanschtezla said:
Hi, I'm not sure if you wrongly wrote the file extension, but shouldn't you run the flash-all.bat instead of the flash-all.sh?
Click to expand...
Click to collapse
Clearly, he is not using Windows (the ./ command in the OP) so .bat file is not relevant.
sliding_billy said:
Clearly, he is not using Windows (the ./ command in the OP) so .bat file is not relevant.
Click to expand...
Click to collapse
I see. Thanks for clarifying that.
I'm running Ubuntu. I also tried Windows and ran the .bat file and got pretty well the same result.
@ sliding_billy I've been pretty busy the last couple days so haven't tried your advice yet. Hoping to get a chance tonight after work.
The Lepricon said:
I'm running Ubuntu. I also tried Windows and ran the .bat file and got pretty well the same result.
@ sliding_billy I've been pretty busy the last couple days so haven't tried your advice yet. Hoping to get a chance tonight after work.
Click to expand...
Click to collapse
One other thing... Have you tried a factory reset from recovery?
sliding_billy said:
One other thing... Have you tried a factory reset from recovery?
Click to expand...
Click to collapse
I believe I have. I'll try that tonight
Ok, so tonight I have tried the following:
Factory reset from recovery - that may have helped. I could then boot to both slots. slot a had lineage, slot b had factory image
unzipped factory image to latest platform tools folder and ran flash-all.sh - still getting same error and still had 2 different ROMs on slots
flashed using flash.android.com from chrome, then set other slot active and flashed again - tried this a few times. whichever slot I have active when I do this boots fine, but the other slot will not boot
So, to summarize, I now have both slots working, but only the slot I flash will boot. So, if I flash slot a, then it will boot, but slot b will not, and vice versa. And, yes I am flashing same ROM to both slots. And, flash-all.sh does not flash to either slot. It just gives met the error I posted in the OP.
Does anyone know why I am getting the error when running flash-all.sh?
The Lepricon said:
Ok, so tonight I have tried the following:
Factory reset from recovery - that may have helped. I could then boot to both slots. slot a had lineage, slot b had factory image
unzipped factory image to latest platform tools folder and ran flash-all.sh - still getting same error and still had 2 different ROMs on slots
flashed using flash.android.com from chrome, then set other slot active and flashed again - tried this a few times. whichever slot I have active when I do this boots fine, but the other slot will not boot
So, to summarize, I now have both slots working, but only the slot I flash will boot. So, if I flash slot a, then it will boot, but slot b will not, and vice versa. And, yes I am flashing same ROM to both slots. And, flash-all.sh does not flash to either slot. It just gives met the error I posted in the OP.
Does anyone know why I am getting the error when running flash-all.sh?
Click to expand...
Click to collapse
I still haven't seen that you are running the current planform tools, so that is my first suggestion. My second one is to sideload the OTA twice (including full boot after of course) so that it will install on both slots and swap. I suspect that you will then have it truly back to normal and can then do a flash-all including the -w to completely wipe.
I downloaded platform-tools_r30.0.4-linux.zip from developer.android.com yesterday and that is what I was using. And it was not working right. So, last night I downloaded it to my Windows machine and tried from there with the same results, only running flash-all.bat.
Late last night I tried your advice of sideloading factory OTA on both slots and that fixed it. Now I can boot to both slots just fine.
Thank you for all your help, sliding_billy
The Lepricon said:
I downloaded platform-tools_r30.0.4-linux.zip from developer.android.com yesterday and that is what I was using. And it was not working right. So, last night I downloaded it to my Windows machine and tried from there with the same results, only running flash-all.bat.
Late last night I tried your advice of sideloading factory OTA on both slots and that fixed it. Now I can boot to both slots just fine.
Thank you for all your help, sliding_billy
Click to expand...
Click to collapse
Great news, and you are quite welcome.
invalid sparse file format at header magic
[SOLVED] Invalid sparse file format at header magic
can someone help me, got this error when I flash GSI on fastbootD C:\adb2>fastboot flash system sys.img Invalid sparse file format at header magic after the flash continue, I reboot on BL, wipe data, reboot and go directly on standard...
forum.xda-developers.com