Related
Hi all.
Last night, for an unknown reason (no flash, etc), my phone refused to boot. With a powered USB-Hub, I can access to fastboot, or SW Upgrade Mode (Phone screen keeps off in both, but is showed in Windows). I've setup OMAP4430 drivers (from Optimus 3D) and fastboot using OMAP4Boot. As I can read from Optimus 3D, my bootloader is corrupted.
I think I can revover my phone using fastboot, no ? SW Upgrade mode doesn't work ("Your phone doesn't support upgrade"), but maybe fastboot will working... ? How and where I can flash a new bootloader ?
Thx for help...
EDIT : I've tried a reflash of CWM, and this is what fastboot responds :
sending 'recovery' (5898 KB)...
OKAY [ 3.022s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.028s
Anyway to recover that ?
EDIT 2 :
A try with "fastboot boot cwmtouch.img" doesn't boot recovery... I need help ! Please !!
I've also tried with CyanogenMod boot.img (extracted from the RC5 zip), but no more success... Is my phone dead ? If I send it to LG, will them see the unlocked bootloader and other things ? If yes, they will refuse to repair my device ?
RL77LUC said:
Hi all.
Last night, for an unknown reason (no flash, etc), my phone refused to boot. With a powered USB-Hub, I can access to fastboot, or SW Upgrade Mode (Phone screen keeps off in both, but is showed in Windows). I've setup OMAP4430 drivers (from Optimus 3D) and fastboot using OMAP4Boot. As I can read from Optimus 3D, my bootloader is corrupted.
I think I can revover my phone using fastboot, no ? SW Upgrade mode doesn't work ("Your phone doesn't support upgrade"), but maybe fastboot will working... ? How and where I can flash a new bootloader ?
Thx for help...
EDIT : I've tried a reflash of CWM, and this is what fastboot responds :
sending 'recovery' (5898 KB)...
OKAY [ 3.022s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.028s
Anyway to recover that ?
EDIT 2 :
A try with "fastboot boot cwmtouch.img" doesn't boot recovery... I need help ! Please !!
I've also tried with CyanogenMod boot.img (extracted from the RC5 zip), but no more success... Is my phone dead ? If I send it to LG, will them see the unlocked bootloader and other things ? If yes, they will refuse to repair my device ?
Click to expand...
Click to collapse
Probably the nand is crapping out. Try refreshing xloader and uboot http://forum.xda-developers.com/showthread.php?p=41768774 or possibly see Kuma82s last post in the same thread.
LG will be able see that you've unlocked the bootloader but who knows if they check it.
Lelus said:
Probably the nand is crapping out. Try refreshing xloader and uboot http://forum.xda-developers.com/showthread.php?p=41768774 or possibly see Kumar82s last post in the same thread.
LG will be able see that you've unlocked the bootloader but who knows if they check it.
Click to expand...
Click to collapse
Thanks a lot for your help. I've tried, but I get that :
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 81eb9bc20de7a195ecaf96582c4197f74c1763
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.200s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.206s
sending 'u-boot' (1024 KB)...
OKAY [ 0.528s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.534s
Done
Click to expand...
Click to collapse
And, I've tried a "fastboot oem format", no more success :
...
FAILED (remote failure)
finished. total time: 0.001s
Click to expand...
Click to collapse
I think my phone's memory is dead, no ? But it's weird, I've purchased it two months ago...
RL77LUC said:
Thanks a lot for your help. I've tried, but I get that :
And, I've tried a "fastboot oem format", no more success :
I've think my phone's memory is dead, no ? But it's weird, I've purchased it two months ago...
Click to expand...
Click to collapse
Yes I think it is,
don't mention anything about the bootloader when you send it to LG
Lelus said:
Yes I think it is,
don't mention anything about the bootloader when you send it to LG
Click to expand...
Click to collapse
Thanks for your help, very appreciated. I will don't send it directly to LG but to my carrier (He do the work, according of documents), and they will send to LG.
Anyone have a last chance idea ?
Kumar lol =)
Once they see it's really a hardware failure, they shouldn't look any further (hopefully)
Good luck
Sent from my LG-P769 using xda app-developers app
kuma82 said:
Kumar lol =)
Once they see it's really a hardware failure, they shouldn't look any further (hopefully)
Good luck
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
I hope... Thx.
EDIT : I've gived it to my carrier. They will send my phone to LG. They will give me back in about 3 weeks...
Good afternoon. I have a big problem. I did root the HTC Hero (GSM) but we did not do and s-off. After several days of relatively normal thing to have restarted it starts but hangs with HTC logo screen and that.
combination works "vol-+ power". the combination "vol + + power" vibrates 3 times, and both green LED lights. combination "home + power" red triangle screen. followed by combination "vol + + power" is the "android system recovery <2e>".
I tried by renaming rom.zip in update.zip, heroboot.zip, etc.. I install the firmware manually, does not work. I tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe pc, RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6.35.15.11_release_signed.exe, RUU_Hero_HTC_WWE-AFK_3.39.421.3_Radio_63.18.55.06P_6.35.15.14_release_signed.exe etc., all give various error.
Phone features:
F: \ adt-bundle-x86-windows-20130729 \ sdk> fastboot oem boot
...
(Bootloader) setup_tag addr = 0xA0000100 cmdline add = 0x8F084058
(Bootloader) TAG: Ramdisk OK
(Bootloader) TAG: smi ok, size = 32
(Bootloader) TAG: 0x1 hwid
(Bootloader) TAG: 0x20800 skuid
(Bootloader) TAG: hero panel = 0x3
(Bootloader) TAG: engineerid = 0x3
(Bootloader) Device CID is not super CID
(Bootloader) CID is HTC__032
(Bootloader) setting.cid :: HTC__032
(Bootloader) serial number: HT9CRL900044
(Bootloader) commandline from head: no_console_suspend = 1 console = null
(Bootloader) command line length = 361
(Bootloader) active commandline: board_hero.disable_uart3 = 0 board_hero.us
(Bootloader) board_hero.disable_sdcard b_h2w_sw = 0 = 0 = 32 androidbo smisize
(Bootloader) ot.baseband = 6.35.15.11 androidboot.cid = HTC__032 androidboot.
(Bootloader) carrier = HTC-EastEurope androidboot.mid = HERO10000 androidboot
(Bootloader). Keycaps = qwerty androidboot.mode = normal androidboot.serialno
(Bootloader) = HT9CRL900044 androidboot.bootloader = 1.76.0013 no_console_su
(Bootloader) spend = 1 console = null
(Bootloader) aARM_Partion [0]. Name = misc
(Bootloader) aARM_Partion. [1] name = recovery
(Bootloader) aARM_Partion. [2] name = boot
(Bootloader) aARM_Partion. [3] name = system
(Bootloader) aARM_Partion. [4] name = cache
(Bootloader) aARM_Partion. [5] name = UserData
(Bootloader) partition number = 6
(Bootloader) Valid partition num = 6
(Bootloader) 0
(Bootloader) 0
(Bootloader) 69,466,957
(Bootloader) 69,784,520
(Bootloader) 69,007,473
(Bootloader) 7473
fimware 2.1-update1
baseband
63.18.15.06pu_6.35.15.11
kernel
6.2.29-7527f009
htc-kernel @ and18-2 # 1
build
Cl345049 3.36.405.2 release-keys
software
3.36.405.2
Browser
webkit 3.1
http://www.htcdev.com/bootloader/ and root after using the phone in HBOOT menu, prints:
*** UNLOCKED ***
HERO CVT SHIP S-ON
HBOOT-1.76.0013 (HERO10000)
Micropores-010F
PANEL-SYN0104 touc
RADIO-6.35.15.11
Jan 9 2012,15:39:56
anyone has solutions and proposals? I searched the internet similar problems without result
conectarenet said:
Good afternoon. I have a big problem. I did root the HTC Hero (GSM) but we did not do and s-off. After several days of relatively normal thing to have restarted it starts but hangs with HTC logo screen and that.
combination works "vol-+ power". the combination "vol + + power" vibrates 3 times, and both green LED lights. combination "home + power" red triangle screen. followed by combination "vol + + power" is the "android system recovery <2e>".
I tried by renaming rom.zip in update.zip, heroboot.zip, etc.. I install the firmware manually, does not work. I tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe pc, RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6.35.15.11_release_signed.exe, RUU_Hero_HTC_WWE-AFK_3.39.421.3_Radio_63.18.55.06P_6.35.15.14_release_signed.exe etc., all give various error.
Phone features:
F: \ adt-bundle-x86-windows-20130729 \ sdk> fastboot oem boot
...
(Bootloader) setup_tag addr = 0xA0000100 cmdline add = 0x8F084058
(Bootloader) TAG: Ramdisk OK
(Bootloader) TAG: smi ok, size = 32
(Bootloader) TAG: 0x1 hwid
(Bootloader) TAG: 0x20800 skuid
(Bootloader) TAG: hero panel = 0x3
(Bootloader) TAG: engineerid = 0x3
(Bootloader) Device CID is not super CID
(Bootloader) CID is HTC__032
(Bootloader) setting.cid :: HTC__032
(Bootloader) serial number: HT9CRL900044
(Bootloader) commandline from head: no_console_suspend = 1 console = null
(Bootloader) command line length = 361
(Bootloader) active commandline: board_hero.disable_uart3 = 0 board_hero.us
(Bootloader) board_hero.disable_sdcard b_h2w_sw = 0 = 0 = 32 androidbo smisize
(Bootloader) ot.baseband = 6.35.15.11 androidboot.cid = HTC__032 androidboot.
(Bootloader) carrier = HTC-EastEurope androidboot.mid = HERO10000 androidboot
(Bootloader). Keycaps = qwerty androidboot.mode = normal androidboot.serialno
(Bootloader) = HT9CRL900044 androidboot.bootloader = 1.76.0013 no_console_su
(Bootloader) spend = 1 console = null
(Bootloader) aARM_Partion [0]. Name = misc
(Bootloader) aARM_Partion. [1] name = recovery
(Bootloader) aARM_Partion. [2] name = boot
(Bootloader) aARM_Partion. [3] name = system
(Bootloader) aARM_Partion. [4] name = cache
(Bootloader) aARM_Partion. [5] name = UserData
(Bootloader) partition number = 6
(Bootloader) Valid partition num = 6
(Bootloader) 0
(Bootloader) 0
(Bootloader) 69,466,957
(Bootloader) 69,784,520
(Bootloader) 69,007,473
(Bootloader) 7473
fimware 2.1-update1
baseband
63.18.15.06pu_6.35.15.11
kernel
6.2.29-7527f009
htc-kernel @ and18-2 # 1
build
Cl345049 3.36.405.2 release-keys
software
3.36.405.2
Browser
webkit 3.1
http://www.htcdev.com/bootloader/ and root after using the phone in HBOOT menu, prints:
*** UNLOCKED ***
HERO CVT SHIP S-ON
HBOOT-1.76.0013 (HERO10000)
Micropores-010F
PANEL-SYN0104 touc
RADIO-6.35.15.11
Jan 9 2012,15:39:56
anyone has solutions and proposals? I searched the internet similar problems without result
Click to expand...
Click to collapse
if you want to "S-OFF"( Remove security and CID locks) follow these guide
http://forum.xda-developers.com/showpost.php?p=4529084&postcount=1
Hi I have a serious problem,
So the other day my lg l9 (P760) die completel. Ii try almost everything but my phone continue to had black screen, won't enter in s/w mode and won't hard reset.
Flash boot have this log at the end:
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.201s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.208s
sending 'u-boot' (1024 KB)...
OKAY [ 0.528s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.535s
Done
When i put it in usb the device connect and disconect continuosly. Only if i try to boot fastboot with vol+ pressed i can see the devices but the screen still black and after a couple of minute it disconnect. So i can't use the lg mobile tool. I try KDZ off-line and on-line procedure but the sw crah or do not recognize the phone.
Can someone help me please?
Flash with fastboot u-boot and x-loader there are some tutorials for fastboot for our device.
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Cytrus224 said:
Flash with fastboot u-boot and x-loader there are some tutorials for fastboot for our device.
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Click to expand...
Click to collapse
Thank you for your answer Cytrus224, but i try to flash with fastbot using this guide (http://forum.xda-developers.com/showthread.php?t=2411265) but flashbot log still the same as the post below.
Can you suggest me something or a better guide?
Thank you
Had same problem yesterday, after changing philz touch to new artas182x twrp by Flashify flashing. Phone stock on LG logo, s/w not working. I used this method found on polish forum
http://forum.android.com.pl/f764/re-lock-bootloader-l9-328381
1. Download omap4boot
2. Download ics u-boot and x-loader.
3. Install fastboot drivers(all tutorials linked in post #1 in upper link)
4. Flash u-boot and x-loader.
5. Now you can turn again phone into s/w and flash stock roms
Sorry for my bad English
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Cytrus224 said:
Had same problem yesterday, after changing philz touch to new artas182x twrp by Flashify flashing. Phone stock on LG logo, s/w not working. I used this method found on polish forum
1. Download omap4boot
2. Download ics u-boot and x-loader.
3. Install fastboot drivers(all tutorials linked in post #1 in upper link)
4. Flash u-boot and x-loader.
5. Now you can turn again phone into s/w and flash stock roms
Sorry for my bad English
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Click to expand...
Click to collapse
Doesn't work.. this is the result:
C:\omap4boot-for_optimus-v1.21>fastboot flash x-loader p1.bin
sending 'x-loader' (384 KB)...
OKAY [ 0.200s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.208s
C:\omap4boot-for_optimus-v1.21>fastboot flash u-boot p2.bin
sending 'u-boot' (1024 KB)...
OKAY [ 0.528s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.535s
Hello, I need help.
I have a Nexus 9 Wifi 16gb black. It was a gift from Google in USA, but I live in Uruguay.
THe problem is:
Yesterday I tried to install Android M (with unlocked bootloader).
Then, installed supersu..
After rebooted I was seeing "Your device is corrupt." and a bootloop.
So, I locked the bootloader, maybe that was the cause of bootloop (ofc no. I figured out it wasnt....)
And I can't do anythig, I can't access to Android to enable the oem unlock option.
I don't have a custom recovery..
I entered in "oem verified" mode, and was able to format userdata/cache partitions. But still the problem...
Here is what I've been trying to do
Code:
[email protected]:~/Descargas$ fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.007s]
finished. total time: 0.007s
[email protected]:~/Descargas$ fastboot flash recovery twrp-2.8.7.0-flounder.img
target reported max download size of 518205818 bytes
sending 'recovery' (13320 KB)...
OKAY [ 1.022s]
writing 'recovery'...
(bootloader) Device State : Locked
FAILED (remote: Can not flash any images while device state is locked!)
finished. total time: 1.161s
[email protected]:~/Descargas$ fastboot oem verified
...
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Device is in veified state!
OKAY [ 2.600s]
finished. total time: 2.600s
[email protected]:~/Descargas$ fastboot flash recovery twrp-2.8.7.0-flounder.img
target reported max download size of 518205818 bytes
sending 'recovery' (13320 KB)...
OKAY [ 1.017s]
writing 'recovery'...
(bootloader) Device State : Verified
FAILED (status read failed (Value too large for defined data type))
finished. total time: 6.447s
[email protected]:~/Descargas$ fastboot format userdat
Formatting is not supported for filesystem with type ''.
[email protected]:~/Descargas$ fastboot format userdata
Cannot generate image.
erasing 'userdata'...
OKAY [ 2.415s]
finished. total time: 2.415s
[email protected]:~/Descargas$ fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 518205818 bytes
erasing 'cache'...
OKAY [ 0.463s]
sending 'cache' (6248 KB)...
OKAY [ 0.482s]
writing 'cache'...
(bootloader) Device State : Verified
OKAY [ 0.637s]
finished. total time: 1.583s
[email protected]:~/Descargas$
:-/
And stil the problem.
Can someone help me?
-Sorry for my bad english-
Greetings
If no way, how to contact Google for reparation? Is there any email?
You should not have relocked bootloader. It needs to be unlocked to do anything if it will not boot. "Enable oem unlock" must be checked.
Need blankflash for moto z xt1650 OREO... please!!!! thx
I need it too
I need it too!
Here is the blank flash I used to solve my problem. I was on oreo but had bootloop issues, flashed gpt.bin then had the qusb issue.
Then I flashed blankflash_NCLS26.118-23-13-6-5_15.zip. This was blank flash worked for me, I hope it works for you.
Please do this at your own risk. After that, flash gpt.bin then use RSD Lite to flash full rom. Or download RSD_Lite_Motorola_XML_To_Batch_Script.zip for windows 8 and windows 10 users, to convert firmware to fastboot flashable file then run the flashfile.bat. adb and fastboot drivers should be installed for fastboot mode to work.
I have attached all the files.
Goodluck.
blankflash_oreo.zip:
Opening device: \\.\COM42
Detecting device
...cpu.id = 2375 (0x947)
...cpu.sn = 4266641337 (0xfe4fc7b9)
Opening singleimage
Loading package
Failed identify board. Wrong package?
ERROR: error loading package
Check qboot_log.txt for more details
Total time: 0.009s
_flash_singleimage()->error loading package
it is not for moto z
Use the first one blankflash_NCLS26.118-23-13-6-5_15.zip. that's the one I used
---------- Post added at 07:24 AM ---------- Previous post was at 07:22 AM ----------
p.m.6 said:
blankflash_oreo.zip:
Opening device: \\.\COM42
Detecting device
...cpu.id = 2375 (0x947)
...cpu.sn = 4266641337 (0xfe4fc7b9)
Opening singleimage
Loading package
Failed identify board. Wrong package?
ERROR: error loading package
Check qboot_log.txt for more details
Total time: 0.009s
_flash_singleimage()->error loading package
it is not for moto z
Click to expand...
Click to collapse
Use the other one. That's the one I used
THIS IS THE ERROR OF THE FIRST FILE:
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM42
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 2375 (0x947)
[ 0.006] ...cpu.sn = 4266641337 (0xfe4fc7b9)
[ 0.006] Opening singleimage
[ 0.074] Loading package
[ 0.089] ...filename = singleimage.pkg.xml
[ 0.095] Loading programmer
[ 0.138] ...filename = programmer.elf
[ 0.139] Sending programmer
[ 0.215] Handling things over to programmer
[ 0.216] Identifying storage type
[ 0.223] Waiting for firehose to get ready
[ 3.254] ...UFS
[ 3.254] Identifying CPU version
[ 3.261] ...MSM8996 3.1
[ 3.262] Determining target secure state
[ 3.265] ...secure = yes
[ 3.318] Configuring device...
[ 3.337] Skipping UFS provsioning as target is secure
[ 3.337] Configuring device...
[ 3.350] Skipping 'setbootablestoragedrive' as target is secure
[ 3.350] Flashing GPT...
[ 3.374] Flashing partition:0 with gpt_main0.bin
[ 3.375] Initializing storage
[ 3.504] Target NAK!
[ 3.504] ...ERROR: Failed to initialize (open whole lun) UFS Device slot 0 part
ition 0
[ 3.505] ...ERROR: Failed to open the device 3 slot 0 partition 0
[ 3.506] ...INFO: Device type 3, slot 0, partition 0, error 0
[ 3.507] ...WARN: Get Info failed to open 3 slot 0, partition 0, error 0
[ 3.508] ...ERROR: Failed to get device info slot:0artition:0
[ 3.508] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 3.509] ...ERROR 14: Line 1284: HANDLE_STORAGE_INFO_FAILURE
[ 3.510] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage
()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 3.510] Check qboot_log.txt for more details
[ 3.511] Total time: 3.548s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash
()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
D:\blankflash\blankflash>pause
Press any key to continue . . .
p.m.6 said:
blankflash_oreo.zip:
Opening device: \\.\COM42
Detecting device
...cpu.id = 2375 (0x947)
...cpu.sn = 4266641337 (0xfe4fc7b9)
Opening singleimage
Loading package
Failed identify board. Wrong package?
ERROR: error loading package
Check qboot_log.txt for more details
Total time: 0.009s
_flash_singleimage()->error loading package
it is not for moto z
Click to expand...
Click to collapse
p.m.6 said:
THIS IS THE ERROR OF THE FIRST FILE:
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM42
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 2375 (0x947)
[ 0.006] ...cpu.sn = 4266641337 (0xfe4fc7b9)
[ 0.006] Opening singleimage
[ 0.074] Loading package
[ 0.089] ...filename = singleimage.pkg.xml
[ 0.095] Loading programmer
[ 0.138] ...filename = programmer.elf
[ 0.139] Sending programmer
[ 0.215] Handling things over to programmer
[ 0.216] Identifying storage type
[ 0.223] Waiting for firehose to get ready
[ 3.254] ...UFS
[ 3.254] Identifying CPU version
[ 3.261] ...MSM8996 3.1
[ 3.262] Determining target secure state
[ 3.265] ...secure = yes
[ 3.318] Configuring device...
[ 3.337] Skipping UFS provsioning as target is secure
[ 3.337] Configuring device...
[ 3.350] Skipping 'setbootablestoragedrive' as target is secure
[ 3.350] Flashing GPT...
[ 3.374] Flashing partition:0 with gpt_main0.bin
[ 3.375] Initializing storage
[ 3.504] Target NAK!
[ 3.504] ...ERROR: Failed to initialize (open whole lun) UFS Device slot 0 part
ition 0
[ 3.505] ...ERROR: Failed to open the device 3 slot 0 partition 0
[ 3.506] ...INFO: Device type 3, slot 0, partition 0, error 0
[ 3.507] ...WARN: Get Info failed to open 3 slot 0, partition 0, error 0
[ 3.508] ...ERROR: Failed to get device info slot:0artition:0
[ 3.508] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 3.509] ...ERROR 14: Line 1284: HANDLE_STORAGE_INFO_FAILURE
[ 3.510] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage
()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 3.510] Check qboot_log.txt for more details
[ 3.511] Total time: 3.548s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash
()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
D:\blankflash\blankflash>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Can I know how you came about the brick?
Muito obrigado!
hypafly said:
Here is the blank flash I used to solve my problem. I was on oreo but had bootloop issues, flashed gpt.bin then had the qusb issue.
Then I flashed blankflash_NCLS26.118-23-13-6-5_15.zip. This was blank flash worked for me, I hope it works for you.
Please do this at your own risk. After that, flash gpt.bin then use RSD Lite to flash full rom. Or download RSD_Lite_Motorola_XML_To_Batch_Script.zip for windows 8 and windows 10 users, to convert firmware to fastboot flashable file then run the flashfile.bat. adb and fastboot drivers should be installed for fastboot mode to work.
I have attached all the files.
Goodluck.
Click to expand...
Click to collapse
Muito obrigado! Nada havia resolvido até esse momento, apenas o seu funcionou para mim, Thk my brother.
Pode me explicar ?
rssangel said:
Muito obrigado! Nada havia resolvido até esse momento, apenas o seu funcionou para mim, Thk my brother.
Click to expand...
Click to collapse
pode me explicar por favor...
hypafly said:
Here is the blank flash I used to solve my problem. I was on oreo but had bootloop issues, flashed gpt.bin then had the qusb issue.
Then I flashed blankflash_NCLS26.118-23-13-6-5_15.zip. This was blank flash worked for me, I hope it works for you.
Please do this at your own risk. After that, flash gpt.bin then use RSD Lite to flash full rom. Or download RSD_Lite_Motorola_XML_To_Batch_Script.zip for windows 8 and windows 10 users, to convert firmware to fastboot flashable file then run the flashfile.bat. adb and fastboot drivers should be installed for fastboot mode to work.
I have attached all the files.
Goodluck.
Click to expand...
Click to collapse
Im with oem locked now.
in adb says "failed remote failure"
i try with officcial 7.11 and 8.0
any ideas? thx
kilombero said:
Im with oem locked now.
in adb says "failed remote failure"
i try with officcial 7.11 and 8.0
any ideas? thx
Click to expand...
Click to collapse
Flash the stock 8.0 Oreo ROM from here https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Use the RSD tool mentioned in the op. Or use RSD Lite. It should work.
hypafly said:
Flash the stock 8.0 Oreo ROM from here https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Use the RSD tool mentioned in the op. Or use RSD Lite. It should work.
Click to expand...
Click to collapse
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.241s
C:\Users\Rodri\Downloads\adb-fastboot-latest\adb-fastboot-latest>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7792 KB)...
OKAY [ 0.240s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name xbl
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name pmic
(bootloader) Invalid partition name hyp
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.317s
it doesnt work... FUUUUUCK! hahahaha
Hello-
I installed w 8.1 to try this... and doesnt work
when i execute the command "fastboot flash partition gpt.bin" in cmd say this:
Microsoft Windows [Versión 6.3.9600]
(c) 2013 Microsoft Corporation. Todos los derechos reservados.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
4881a40a fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (142 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.234s
FUCCCCCCKKK!!! hahahaha
im in :
BL: 91.09(*) (sha-7de07a7, 2018-02-20
Baseband:
Product/Variant: sheridan 000000000000 32gb P3B
Oem_locked
Fuccccck haa
kilombero said:
Hello-
I installed w 8.1 to try this... and doesnt work
when i execute the command "fastboot flash partition gpt.bin" in cmd say this:
Microsoft Windows [Versión 6.3.9600]
(c) 2013 Microsoft Corporation. Todos los derechos reservados.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
4881a40a fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (142 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.234s
FUCCCCCCKKK!!! hahahaha
im in :
BL: 91.09(*) (sha-7de07a7, 2018-02-20
Baseband:
Product/Variant: sheridan 000000000000 32gb P3B
Oem_locked
Fuccccck haa
Click to expand...
Click to collapse
you must have the bootloader unlocked for flash that rom
eLaDiio said:
you must have the bootloader unlocked for flash that rom
Click to expand...
Click to collapse
the bootloader before the hardbrick was unlocked. after the blankflash its blocked.
i got a new and beuty paperweight? jaja
kilombero said:
the bootloader before the hardbrick was unlocked. after the blankflash its blocked.
i got a new and beuty paperweight? jaja
Click to expand...
Click to collapse
ajhjahjahja could be, but i supposed if you have access to the fastboot commands you could unlock the bootloader, btw why not flash a 7.11 stock rom?, later reboot on bootloader and flash the oreo stock full rom or sideload the oreo update(but i think this could make other hardbrick)
kilombero said:
the bootloader before the hardbrick was unlocked. after the blankflash its blocked.
i got a new and beuty paperweight? jaja
Click to expand...
Click to collapse
good day,
I don't know about the Moto Z but the Moto G5S (I own) can be unbricked via full dump and
sdcard boot
https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150
perhaps it helps
kind regards
eLaDiio said:
ajhjahjahja could be, but i supposed if you have access to the fastboot commands you could unlock the bootloader, btw why not flash a 7.11 stock rom?, later reboot on bootloader and flash the oreo stock full rom or sideload the oreo update(but i think this could make other hardbrick)
Click to expand...
Click to collapse
when i try to unlock with commands in cmd it throws me an error. im really stuck here.
any update on the blankflash for bl 91.09? I accidentally downgraded to 7.1 and phone now hardbricked. Last BL is 91.09. Phone is still being detected in devman. Any help is appreciated. Thanks!
here is the logs when trying to use blankflash_NCLS26.118-23-13-6-5_15
**** Log buffer [000001] 2018-08-26_10:30:21 ****
[ 0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 4.012] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.012] Check qboot_log.txt for more details
[ 4.013] Total time: 4.017s
[ 4.014]
[ 4.014] qboot version 3.40
[ 4.014]
[ 4.014] DEVICE {
[ 4.014] name = "\\.\COM3",
[ 4.014] flags = "0x64",
[ 4.014] addr = "0x61FE5C",
[ 4.014] api.bnr = "0x2EB2C98",
[ 4.014] }
[ 4.014]
[ 4.014]
[ 4.014] Backup & Restore {
[ 4.014] num_entries = 0,
[ 4.014] restoring = "false",
[ 4.014] backup_error = "not started",
[ 4.014] restore_error = "not started",
[ 4.014] }
[ 4.014]