Database Develop

Stuck in fastboot, LG L90 D405N

Hello,
I made a mistake of using a .bat file created by someone to unlock my bootloader. After going through the .bat file, I see that it nulled my boot.img file on the phone, so now I'm stuck in fastboot mode (previously nulled LAF to get access). The irony here is that I do have a backup of the boot.img file on both my PC and on the phone's internal memory, but there's no way (atleast I haven't found one) to actually flash it back so it would work. So my question here would be - do you guys have any ideas how should I proceed? I tried using fastboot flash, but all I get in turn is an error:
"FAILED (remote: unknown command)"
Device is not unlocked (as I was trying to get it unlocked). I have no access to anything else other than fastboot.
getvar all outputs this:
(bootloader) display-panel:
(bootloader) charger-screen-enabled: 0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x38400000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0xfbd80000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x80000000
(bootloader) unlocked: no
(bootloader) secure-boot: no
(bootloader) version-hardware: rev_10
(bootloader) variant: w7n_global_com Samsung 8GB
(bootloader) serialno: LGD405aa16eaa7
(bootloader) kernel: lk
(bootloader) product: W7N_GLOBAL_COM
all:
finished. total time: 0.041s
Any input to this thread is appreciated!

How reliable Bootloader Unlock Check in hidden menu is?

Hi,
I have recently rolled back to stock firmware (4.1.2). As usual, I wanted to unlock it again but "Bootloader Unlock Check" in hidden menu says "unlock",
dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock
And the following is the output of "fastboot getvar all"
$ fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: ????????????
(bootloader) mid: 001
(bootloader) product: X3
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000600000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system:
(bootloader) partition-type:system:
(bootloader) partition-size:cache: 0x0000000018000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata:
(bootloader) partition-type:userdata:
Definitely it is still locked because, look at below
$ fastboot flash recovery twrp-2.8.7.0-p880.img
sending 'recovery' (8182 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.140s
So, my question is
How reliable Bootloader Unlock Check in hidden menu is? or what is wrong?

HTC One M7 - Bricked?

Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ҟÀü«/륑-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!

Have you tried to flash stock recovery or RUU?

JB_ said:
Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ҟÀü«/륑-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!
Click to expand...
Click to collapse
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.

alray said:
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.
Click to expand...
Click to collapse
Well as I want to remember it I don't think I have flashed a rom yet, I never got that far I just tried to flash twrp 2.8.4.0.
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.

JIMSHERIKO said:
Have you tried to flash stock recovery or RUU?
Click to expand...
Click to collapse
Well if I understand it right when I try to flash a RUU it just says unknown modelid and I think because it's corrupted or something. :/

JB_ said:
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.
Click to expand...
Click to collapse
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.

alray said:
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.
Click to expand...
Click to collapse
Ah so i need to get TWRP up and running for adb to work then.
Well looks like i got my awnser then. Thank you for your time!

i need help R1 HD

I have R1 HD R0030UU
its friends phone he get OTA when installed OTA the phone get bootloop and can get recovery and fastboot but I can't use SPFT to flash the phone its restart before when the red line finish on SPFT I tryed to unlock bootloader with fastboot OEM unlock but its failed is there any way to get back with the stock recovery or fastboot command
I have all drive NEEDS on my PC if there any way to use SDCARD to flash
Thanks all

This is photo of recovery may help you to help me get it back

KARIM9377 said:
I have R1 HD R0030UU
its friends phone he get OTA when installed OTA the phone get bootloop and can get recovery and fastboot but I can't use SPFT to flash the phone its restart before when the red line finish on SPFT I tryed to unlock bootloader with fastboot OEM unlock but its failed is there any way to get back with the stock recovery or fastboot command
I have all drive NEEDS on my PC if there any way to use SDCARD to flash
Thanks all
Click to expand...
Click to collapse
only thing you can do with stock recovery is factory reset.
Was phone bootloader unlocked before the ota.
If so bootloop is normal after OTA, except usually it will not open recovery only fastboot.
did you try "fastboot OEM unlock" like you put above or
"fastboot oem unlock" like it supposed to be?

mrmazak said:
only thing you can do with stock recovery is factory reset.
Was phone bootloader unlocked before the ota.
If so bootloop is normal after OTA, except usually it will not open recovery only fastboot.
did you try "fastboot OEM unlock" like you put above or
"fastboot oem unlock" like it supposed to be?
Click to expand...
Click to collapse
Thanks for reply no I think it was not unlocked bootloader before OTA
I try factory reset from stock recovery but not fix bootloop
"Fastboot OEM unlock" not working when pres V up to confirm unlock on phone its say fail back to fastboot 3se
I think if I can get full OTA update zip file for R0030UU can I update with stock recovery
When use flash tool I get this error
S_BROM_DOWNLOAD_DA_FAIL (0x7D4)

KARIM9377 said:
Thanks for reply no I think it was not unlocked bootloader before OTA
I try factory reset from stock recovery but not fix bootloop
"Fastboot OEM unlock" not working when pres V up to confirm unlock on phone its say fail back to fastboot 3se
I think if I can get full OTA update zip file for R0030UU can I update with stock recovery
Click to expand...
Click to collapse
the updates are incremental, and it checks md5sum of every file on /system before doing the install, so if ota was stopped halfway you might be "borked"
also will need to know the version it was on , in order to get correct update.
here is link for the v17 to v21 update
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip

mrmazak said:
the updates are incremental, and it checks md5sum of every file on /system before doing the install, so if ota was stopped halfway you might be "borked"
also will need to know the version it was on , in order to get correct update.
Here is link for the v17 to v21 update
http://hwfotadown.mayitek.com/ota/r...ric_6.0_20170505-17451495815395129/update.zip
Click to expand...
Click to collapse
r0011uu is it working on r0030uu ?

KARIM9377 said:
r0011uu is it working on r0030uu ?
Click to expand...
Click to collapse
not sure. All my links are for either r0011uu or r0010uu.
r0011uu= non prime 16gb version
and
r0010uu= prime 16 gb version
Be AWRAE all the updates flash a new preloader that intentionaly blocks spft. and gives the error you have
so any update takes flash tool away

still no fix
mrmazak said:
not sure. All my links are for either r0011uu or r0010uu.
r0011uu= non prime 16gb version
and
r0010uu= prime 16 gb version
Be AWRAE all the updates flash a new preloader that intentionaly blocks spft. and gives the error you have
so any update takes flash tool away
Click to expand...
Click to collapse
still no fix try with all OTA file but not work and i cant find OTA or firmware for R0030UU 16GB 2G RAM I think i have v6.6 on it because not accept flash with SPFT
THIS is my getvar all
C:\adb>fastboot getvar all
(bootloader) max-download-size: 0x800000
(bootloader) partition-size:flashinfo: 1
(bootloader) partition-type:flashinfo: r
(bootloader) partition-size:userdata: 32
(bootloader) partition-type:userdata: ex
(bootloader) partition-size:cache: 19000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a700
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 25
(bootloader) partition-type:metadata: ra
(bootloader) partition-size:nvdata: 2000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw dat
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw da
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw da
(bootloader) partition-size:keystore: 80
(bootloader) partition-type:keystore: ra
(bootloader) partition-size:secro: 60000
(bootloader) partition-type:secro: raw d
(bootloader) partition-sizeemkeystore:
(bootloader) partition-typeemkeystore:
(bootloader) partition-size:seccfg: 8000
(bootloader) partition-type:seccfg: raw
(bootloader) partition-size:expdb: a0000
(bootloader) partition-type:expdb: raw d
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw da
(bootloader) partition-size:recovery: 10
(bootloader) partition-type:recovery: ra
(bootloader) partition-size:boot: 100000
(bootloader) partition-type:boot: raw da
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw da
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a0
(bootloader) partition-typerotect2: ex
(bootloader) partition-sizerotect1: a0
(bootloader) partition-typerotect1: ex
(bootloader) partition-size:nvram: 50000
(bootloader) partition-type:nvram: raw d
(bootloader) partition-sizeroinfo: 300
(bootloader) partition-typeroinfo: raw
(bootloader) partition-sizereloader: 4
(bootloader) partition-typereloader: r
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.078s

KARIM9377 said:
still no fix try with all OTA file but not work and i cant find OTA or firmware for R0030UU 16GB 2G RAM I think i have v6.6 on it because not accept flash with SPFT
THIS is my getvar all
C:\adb>fastboot getvar all
(bootloader) max-download-size: 0x800000
(bootloader) partition-size:flashinfo: 1
(bootloader) partition-type:flashinfo: r
(bootloader) partition-size:userdata: 32
(bootloader) partition-type:userdata: ex
(bootloader) partition-size:cache: 19000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a700
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 25
(bootloader) partition-type:metadata: ra
(bootloader) partition-size:nvdata: 2000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw dat
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw da
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw da
(bootloader) partition-size:keystore: 80
(bootloader) partition-type:keystore: ra
(bootloader) partition-size:secro: 60000
(bootloader) partition-type:secro: raw d
(bootloader) partition-sizeemkeystore:
(bootloader) partition-typeemkeystore:
(bootloader) partition-size:seccfg: 8000
(bootloader) partition-type:seccfg: raw
(bootloader) partition-size:expdb: a0000
(bootloader) partition-type:expdb: raw d
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw da
(bootloader) partition-size:recovery: 10
(bootloader) partition-type:recovery: ra
(bootloader) partition-size:boot: 100000
(bootloader) partition-type:boot: raw da
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw da
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a0
(bootloader) partition-typerotect2: ex
(bootloader) partition-sizerotect1: a0
(bootloader) partition-typerotect1: ex
(bootloader) partition-size:nvram: 50000
(bootloader) partition-type:nvram: raw d
(bootloader) partition-sizeroinfo: 300
(bootloader) partition-typeroinfo: raw
(bootloader) partition-sizereloader: 4
(bootloader) partition-typereloader: r
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.078s
Click to expand...
Click to collapse
dont think there is anything you can do.
Contact "Blu" customer service, maybe they will send you a repair file or let you send it in for repair. The phones have 1 year warrenty

BLU R1 HD won't turn on
KARIM9377 said:
I have R1 HD R0030UU
its friends phone he get OTA when installed OTA the phone get bootloop and can get recovery and fastboot but I can't use SPFT to flash the phone its restart before when the red line finish on SPFT I tryed to unlock bootloader with fastboot OEM unlock but its failed is there any way to get back with the stock recovery or fastboot command
I have all drive NEEDS on my PC if there any way to use SDCARD to flash
Thanks all
Click to expand...
Click to collapse
Hey guys, my BLU HD has stopped working and it is just stuck whit white screen blu logo, I tried hard reset from recovery mode and unlock bootloader with fastboot but nothing has changed. Can somebody help me, please?

Need help with boot loop: Stock/OEM ROM (last security update), unlocked bootloader

Hello! After going through all the Q&A/Help threads regarding "boot loops", I was not able to find a solution that worked for my situation. I'm hoping to to get some advice for how to fix the following issue:
Issue: Nexus 6 (XT1103, 64GB, unlocked boot loader, no root, stock recovery, ROM = last OTA security update) was found boot-looping when I pulled it out of my pocket one afternoon. I can get to boot loader menu (Power + Volume DN), but I cannot enter recovery mode. Choosing any option from the main boot loader menu restarts the boot-loop.
Knowns: Battery was nearly dead, so I originally thought this was the cause. Ordered new battery and installed on Thursday. Still boot-looping after trying to boot to OS.
Things I've already tried:
Battery replacement (OEM EZ30)
Cleared cache from recovery (I was able to get recovery running one time, cleared cache, boot-loop restarted on reboot)
Can access with fastboot from boot loader menu (serial number is correct)
Cannot access with adb due to inability to start recovery (obviously)
Tried flashing TWRP using fastboot and then rebooting to recovery --> boot-loop starts again
Tried flashing 10/2017 factory image using one-by-one method --> boot-loop starts again
"Safe" (?) boot from boot-loader menu by pressing/holding power button when "BOOTLOADER LOGS" is selected --> boot-loop starts again
Tried loading TWRP from laptop using fastboot ("fastboot boot C:\Android\TWRP.img") --> screen changes momentarily, then boot-loop starts again
Erased and flashed cache and userdata using fastboot --> boot-loop starts again after reboot
Probably forgot some of the steps along the way....
Results from "fastboot getvar all" (not sure how to remove auto-smileys):
PS C:\Android> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-72.04
(bootloader) product: shamu
(bootloader) board: shamu
(bootloader) secure: yes
(bootloader) hwrev: 0x83A0
(bootloader) radio: 0x6
(bootloader) emmc: 64GB Hynix REV=07 PRV=03 TYPE=57
(bootloader) ram: 3072MB Hynix S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: ZX1G323VQT
(bootloader) cid: 0x00DE
(bootloader) channelid: 0x00
(bootloader) uid: 64EB4F0111000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jan 14 23:25:58 UTC 2015"
(bootloader) ro.build.fingerprint: none
(bootloader) ro.build.version.full: none
(bootloader) ro.build.version.qcom: none
(bootloader) version-baseband: D4.01-9625-05.45+FSG-9625-02.117
(bootloader) kernel.version: none
(bootloader) sdi.git: git=MBM-NG-V72.04-0-gf291c61
(bootloader) sbl1.git: git=MBM-NG-V72.04-0-g60ea7e6
(bootloader) rpm.git: git=MBM-NG-V72.04-0-g18b261e
(bootloader) tz.git: git=MBM-NG-V72.04-0-g921699c
(bootloader) aboot.git: git=MBM-NG-V72.04-0-gb11eacf
(bootloader) partition-type:modem: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:sdi: raw
(bootloader) partition-type:sec: raw
(bootloader) partition-type:ddr: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:sbl1bak: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:versions: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:mdm1m9kefs1: raw
(bootloader) partition-type:mdm1m9kefs2: raw
(bootloader) partition-type:mdm1m9kefs3: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:mdm1hob: raw
(bootloader) partition-type:mdm1dhob: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadD: raw
(bootloader) partition-type:mdm1m9kefsc: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:cache: ext4
(bootloader) partition-typeem: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:modem: 0x0000000007000000
(bootloader) partition-size:metadata: 0x0000000001000000
(bootloader) partition-size:sbl1: 0x0000000000060000
(bootloader) partition-size:sdi: 0x000000000000e000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:ddr: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x0000000000040000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-sizeadA: 0x000000000040f000
(bootloader) partition-size:sbl1bak: 0x0000000000060000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x0000000000040000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:versions: 0x0000000000001000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:mdm1m9kefs1: 0x0000000000100000
(bootloader) partition-size:mdm1m9kefs2: 0x0000000000100000
(bootloader) partition-size:mdm1m9kefs3: 0x0000000000100000
(bootloader) partition-sizeadB: 0x0000000000100000
(bootloader) partition-size:sp: 0x0000000001000000
(bootloader) partition-size:keystore: 0x0000000001000000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-sizeersist: 0x0000000002000000
(bootloader) partition-size:mdm1hob: 0x0000000000040000
(bootloader) partition-size:mdm1dhob: 0x0000000000008000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:logo: 0x0000000000800000
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-sizeadD: 0x0000000000278000
(bootloader) partition-size:mdm1m9kefsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:recovery: 0x0000000001004000
(bootloader) partition-size:kpan: 0x00000000008e0000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-sizeem: 0x0000000004000000
(bootloader) partition-sizeadC: 0x0000000000100000
(bootloader) partition-size:system: 0x0000000080000000
(bootloader) partition-size:userdata: 0x0000000de97e0000
(bootloader) qe:
(bootloader) ro.carrier: unknown
(bootloader) dm-verity-state: Not Supported
all: listed above
Finished. Total time: 0.472s
PS C:\Android>
So far, nothing has worked. Originally, I was hoping to recover my user data as my last backup was a little too long ago (she's been very reliable for the last 3.5 years). At this point, I would be happy to just recover the OS and get the device working again with my brand-new battery.
Does anyone have some good advice for how to troubleshoot and fix this boot-loop issue?
Thanks!

I'm assuming you have Android SDK installed on your PC and you know how to use it. While your N6 is in fastboot mode, does your PC recognize it and if it does open a cmd prompt and type fastboot devices. Is your N6 listed?

Yup (see #3). Serial number is returned correctly from "fastboot devices".
Guapo613 said:
I'm assuming you have Android SDK installed on your PC and you know how to use it. While your N6 is in fastboot mode, does your PC recognize it and if it does open a cmd prompt and type fastboot devices. Is your N6 listed?
Click to expand...
Click to collapse

May I suggest downloading Wugfresh's Nexus Root Toolkit.
Study the Options available on this Toolkit. From the 1st Screen select Launch.
If anything can help you with your extremely frustrating issues, it's this one. None better for your worthy Nexus 6.

Similar Boot Loop Issue
PreachJohn said:
May I suggest downloading Wugfresh's Nexus Root Toolkit.
Study the Options available on this Toolkit. From the 1st Screen select Launch.
If anything can help you with your extremely frustrating issues, it's this one. None better for your worthy Nexus 6.
Click to expand...
Click to collapse
I have been having the same issue as the original poster. I can hold POWER + VOL DOWN to gain access to that menu but every other option leads me back to a boot loop. I've done the following:
- Downloaded and installed the Android SDK
- used the Fastboot command to erase cache, userdata, bootloader, dalvic-cache, system
- Flashed the newest image (7.1.1 [NGI77B] Which is what I had prior to the boot loop issues) downloaded from developers.google.com
- Downloaded the NRT from Wugfresh and flashed all (at least 4 times now)
The boot loop continues but my PC does recognize the phone and I can tell when I flash the images that it takes because the font for "Google" changes based on the image version (sans serif for the newer ones).
Also, I have never installed a 3rd party image
I have never hard dropped the device or exposed it to water.
All other hardware has worked fine, including the battery.
Note: I had this phone boot loop over a year ago (and has never been fixed since then). When I was researching it back then, I cam across some people discussing the possibility of one of the processor cores possibly being faulty due to some problem at the factory at the time of manufacturing...some cold solder joint that eventually fails or something. I just recently tried to get this phone working again but haven't seen anything mentioning the processor issue at all so I'm wondering if that was just speculation.
I can gladly post any logs or anything that will help to troubleshoot.
Thanks in advance for any and all assistance!

Update: Processes performed
Since it has been over a year since I used this phone, I am not 100% certain on what options were enabled/disabled so I so suppose I need to determine that first.
I am fairly certain (though not 100%) that I had USB debugging enabled prior to breaking.
I do NOT remember ever rooting my N6.
Again, the above mentioned are assumptions.
Update to processes performed:
Downloaded TWRP
​-Moved file to Dir where fastboot.exe located
​-renamed file to twrp.img (ensured extension was visible so I could verify it wasn't still an .apk file)
​-Plugged in phone and booted using POW + VOL DN
​-ran fastboot devices and verified SN matched my phone
​-flashed (or attempted to flash) TWRP image:
C:\Users\djfon\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (2703 KB) OKAY [ 0.170s]
Writing 'recovery' (bootloader) Invalid boot image
FAILED (remote: '')
fastboot: error: Command failed
Rebooting at this point continues the boot loop when I choosing Recovery, Factory, QCOM or BP Tools.
Selecting Restart Bootloader returns me to the fastboot screen.

fonem said:
Since it has been over a year since I used this phone, I am not 100% certain on what options were enabled/disabled so I so suppose I need to determine that first.
I am fairly certain (though not 100%) that I had USB debugging enabled prior to breaking.
I do NOT remember ever rooting my N6.
Again, the above mentioned are assumptions.
Update to processes performed:
Downloaded TWRP
​-Moved file to Dir where fastboot.exe located
​-renamed file to twrp.img (ensured extension was visible so I could verify it wasn't still an .apk file)
​-Plugged in phone and booted using POW + VOL DN
​-ran fastboot devices and verified SN matched my phone
​-flashed (or attempted to flash) TWRP image:
C:\Users\djfon\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (2703 KB) OKAY [ 0.170s]
Writing 'recovery' (bootloader) Invalid boot image
FAILED (remote: '')
fastboot: error: Command failed
Rebooting at this point continues the boot loop when I choosing Recovery, Factory, QCOM or BP Tools.
Selecting Restart Bootloader returns me to the fastboot screen.
Click to expand...
Click to collapse
Try using an older minimal Fastboot from this thread. Try 1.2 -1.3 releases.

@fonem
You say that you renamed the TWRP image file. Did it have extension .img before rename? If not, it is the wrong file.

ktmom said:
Try using an older minimal Fastboot from this thread. Try 1.2 -1.3 releases.
Click to expand...
Click to collapse
I've downloaded both versions, 1.2 ans 1.3. I will install them and give them both a try and post my findings.
---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------
runekock said:
@fonem
You say that you renamed the TWRP image file. Did it have extension .img before rename? If not, it is the wrong file.
Click to expand...
Click to collapse
I'm on a different PC right now but the one I was using when trying to flash my phone was an .apk file. I'll look for a different version of TWRP and verify it is an .img file.
*EDIT*
Using both Minimal ADB & Fastboot versions, I flashed TWRP several times.
- Downloaded TWRP image files from https://dl.twrp.me/shamu/
- Flashed the following TWRP versions:
- twrp-2.8.2.0-shamu.img
- twrp-3.0.0-0-shamu.img
- twrp-3.1.0-0-shamu.img
- twrp-3.2.1-0-shamu.img
- twrp-3.3.1-0-shamu.img
Sample command prompt log:
c:\Program Files (x86)\Minimal ADB 1.3>fastboot flash recovery twrp-3.2.1-0-shamu.img
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.385s]
writing 'recovery'...
OKAY [ 0.185s]
finished. total time: 0.570s
After every successful install, I restarted the phone in fastboot mode and then selected the Recovery option. Still getting the Google logo boot loop.

fonem said:
I've downloaded both versions, 1.2 ans 1.3. I will install them and give them both a try and post my findings.
---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------
I'm on a different PC right now but the one I was using when trying to flash my phone was an .apk file. I'll look for a different version of TWRP and verify it is an .img file.
Click to expand...
Click to collapse
Sounds like you downloaded the TWRP app, which, if you're rooted, should be able to install the recovery image.
But, that's not what you want for Fastboot flashing. Go to TWRP website and on the page I linked, scroll past the app methods of installing and look for the "Download Links:" section.

@fonem
Unfortunately, your phone sounds unfixable to me.

fonem said:
I've downloaded both versions, 1.2 ans 1.3. I will install them and give them both a try and post my findings.
---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------
I'm on a different PC right now but the one I was using when trying to flash my phone was an .apk file. I'll look for a different version of TWRP and verify it is an .img file.
*EDIT*
Using both Minimal ADB & Fastboot versions, I flashed TWRP several times.
- Downloaded TWRP image files from https://dl.twrp.me/shamu/
- Flashed the following TWRP versions:
- twrp-2.8.2.0-shamu.img
- twrp-3.0.0-0-shamu.img
- twrp-3.1.0-0-shamu.img
- twrp-3.2.1-0-shamu.img
- twrp-3.3.1-0-shamu.img
Sample command prompt log:
c:\Program Files (x86)\Minimal ADB 1.3>fastboot flash recovery twrp-3.2.1-0-shamu.img
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.385s]
writing 'recovery'...
OKAY [ 0.185s]
finished. total time: 0.570s
After every successful install, I restarted the phone in fastboot mode and then selected the Recovery option. Still getting the Google logo boot loop.
Click to expand...
Click to collapse
Before giving up on this, download the last Factory image. Use the flash-all script which will completely update the phone.
Continue to use the older minimal Fastboot that you downloaded. The newer Fastboot are not backwards compatible with Shamu.
Booting to recovery relies on the the android kernel. Reinstalling the factory image many get things back on track. After a successful Fastboot flash, try booting before doing anything else.
BTW, just use the last release of what ever your installing. That includes using TWRP twrp-3.3.1-0-shamu.img.

Okay, I will attempt to flash the latest factory image using Minimal 1.2 and see if it takes.
One thing I remember the day that my N6 began to loop is that I was visiting family and my phone was in my back pocket. I started to feel hot and when I pulled my phone out, it was looping and hotter than I've ever felt I before. I'm wondering if there was a hardware failure such as the CPU core solder problem I read about.
I've read about apps that can manipulate the cores to OC them or shut them off completely but they all seem to be done from within a working phone OS. And I'm not sure it would even be worth it at this point. I guess I'm more upset that the N6 was such a great phone for me. Oh well. I'll give this last attempt a try before adding it to my box of old phones.
Thanks everyone for your help!