Related
The initial situation:
For OS only a dash appears.
The boot loader is unlocked hboot is 1.54.0000, S-ON device is RH
On the device ViperOne running 3.5.0 (4.3)
Now to the problem:
Flashing a recovery is performed, also displayed as OK, but it remains the old (TWRP 2.6.3.3)
Bootloader not lock possible:
(bootloader) Lock successfully ...
(boot loader) mipi display off
(boot loader) mipi_dsi_cmds_tx_ext
(boot loader) pm8921_vreg_disable function, vreg_id = 38
(boot loader) pm8921_vreg_disable function, vreg_id = 1
(boot loader) TZ_HTC_SVC_DISABLE ret = 534 642 044 (0x1FDDFD7C)
(boot loader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.139s
Flashing via sideload possible, unfortunately, according to Rome, it passes through or terminates. After the restart, but is ancient Rome it.
Getvar all the following shows:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3893mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Read access possible via fastboot, ADB, token.
What is not possible to change anything on the device.
What are my options, I can do?
If information still needed, just ask.
Thank you
Fooox1 said:
The initial situation:
For OS only a dash appears.
The boot loader is unlocked hboot is 1.54.0000, S-ON device is RH
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
Read access possible via fastboot, ADB, token.
What is not possible to change anything on the device.
What are my options, I can do?
If information still needed, just ask.
Thank you
Click to expand...
Click to collapse
So if I understand correctly, you don't like the fact that firmware version not showing up; so I guess you have a couple of options:
1- (recommended in my opinion) get s-off using rumrunner
2- download this OTA: http://www.htc1guru.com/dld/ota_m7_..._p_release_325133_signedlqk8p6c09r7kmir2-zip/
and extract the "firmware.zip" inside, then flash that in fastboot ruu mode (TWICE in a row)
(you may need to relock bootloader for that)
Thanks for the reply, but unfortunately brings me no further.
1 Runrummer not running my knowledge with 4.3. I have also tried, without success.
2 That's my problem, I can not close the boot loader.
Fooox1 said:
Thanks for the reply, but unfortunately brings me no further.
1 Runrummer not running my knowledge with 4.3. I have also tried, without success.
2 That's my problem, I can not close the boot loader.
Click to expand...
Click to collapse
rumrunner should work just fine, but you're not on 4.3 (firmware); you're hboot 1.54 would imply that you are running a 2.24 firmware, so you need a ROOTED 2.24 ROM with unsecured kernel; try this one: oops, looks like mega is down at the moment
find a 2.24 based ROM, rooted, with unsecured kernel, and rumrunner should work fine. maybe try Maximus 10 or 11: http://llabtoofer.com/category/devices/htc-one/page/2/
However, it is to 4.3 (see photo)
My problem is that the unit will not start a new Rome. Even if the flash goes through, is the old when you start it again. The same happens if I flash a different recovery. What I put on it when the one hanging on the PC is turned on, after the boot gone into recovery.
Fooox1 said:
However, it is to 4.3 (see photo)
My problem is that the unit will not start a new Rome. Even if the flash goes through, is the old when you start it again. The same happens if I flash a different recovery. What I put on it when the one hanging on the PC is turned on, after the boot gone into recovery.
Click to expand...
Click to collapse
1- I understand your current ROM is 4.3, but that has nothing to do with firmware; firmware is <empty>, but hboot is 1.54, so it implies a 2.24 ROM.
2- to get rumrunner to work, you will need a 2.24 RUM
3- can you please boot to bootloader screen and make sure it says UNLOCKED (a screenshot would be nice )
So looking out of the boot loader. The maximum has brought nothing. If flashed, but after booting remains Viper.
As written, also the boot loader can not be closed.
Fooox1 said:
So looking out of the boot loader. The maximum has brought nothing. If flashed, but after booting remains Viper.
As written, also the boot loader can not be closed.
Click to expand...
Click to collapse
keep bootloader UNLOCKED!!
download TWRP 2.6.3.0: http://techerrata.com/browse/twrp2/m7
verify MD5
go to bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, then flash one of the maximus 10 or 11 roms.
then go for rumrunner.
Result as before. I have the 2.6.3.0 flashed message Ok, fastboot erase cache, message Ok, fastboot reboot-bootloader, One reboots into Rome. When I go into recovery again, because it is the 2.6.3.3. So the one that is already on it.
I flash so not only since yesterday. I have a feeling that he executes everything speaks to fastboot / ADB commands, but it does not implement, for whatever reason.
I have also, over sideload that Guru_Reset_M7_2.24.161.1 flashed. Everything ok, abe after the start again Viper Rome.
Fooox1 said:
Result as before. I have the 2.6.3.0 flashed message Ok, fastboot erase cache, message Ok, fastboot reboot-bootloader, One reboots into Rome. When I go into recovery again, because it is the 2.6.3.3. So the one that is already on it.
I flash so not only since yesterday. I have a feeling that he executes everything speaks to fastboot / ADB commands, but it does not implement, for whatever reason.
I have also, over sideload that Guru_Reset_M7_2.24.161.1 flashed. Everything ok, abe after the start again Viper Rome.
Click to expand...
Click to collapse
sounds too much like a locked bootloader, would you mind copy/paste command prompt, for example:
Code:
C:\ADB2>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img[/COLOR][/B]
sending 'recovery' (10570 KB)...
OKAY [ 1.860s]
writing 'recovery'...
OKAY [ 0.768s]
finished. total time: 2.634s
C:\ADB2>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.058s
C:\ADB2>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\ADB2>
No problem:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C: \ Windows \ system32> cd ..
C: \ Windows> cd ..
C: \> cd fastboot
C: \ fastboot> fastboot flash recovery recovery.img
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
C: \ fastboot> fastboot erase cache
erasing 'cache' ... OKAY
C: \ fastboot> fastboot reboot-bootloader
rebooting into bootloader ... OKAY
C: \ fastboot>
Oh, do not be surprised, the recovery was only renamed, can be write faster.
Fooox1 said:
No problem:
C: \ fastboot> fastboot flash recovery recovery.img
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
C: \ fastboot> fastboot erase cache
erasing 'cache' ... OKAY
C: \ fastboot> fastboot reboot-bootloader
rebooting into bootloader ... OKAY
C: \ fastboot>
Oh, do not be surprised, the recovery was only renamed, can be write faster.
Click to expand...
Click to collapse
1- yes, i am aware that it can be renamed, though I usually just type the first letter of the filename (for example "o") and then press tab, eg:
Code:
C:\ADB2>fastboot flash recovery o
then press TAB, and:
Code:
C:\ADB2>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
2-
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
Click to expand...
Click to collapse
mine gives me a lot more info:
Code:
C:\ADB2>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (10570 KB)...
OKAY [ 1.860s]
writing 'recovery'...
OKAY [ 0.768s]
finished. total time: 2.634s
C:\ADB2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.058s
C:\ADB2>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
3- 8432KB
What do you need more accurate. Had actually written anything. The error occurred after the Falshen the Viper Rome. I can do everything in recovery, Wipen, factory reset, etc, everything is executed and confirmed. Unfortunately baer not really. For example, I format the SD, is also displayed as running. But I then go to the File Manager is all still there.
Have also made a backup is running, I want to restore it, is nothing.
Fooox1 said:
What do you need more accurate. Had actually written anything. The error occurred after the Falshen the Viper Rome. I can do everything in recovery, Wipen, factory reset, etc, everything is executed and confirmed. Unfortunately baer not really. For example, I format the SD, is also displayed as running. But I then go to the File Manager is all still there.
Have also made a backup is running, I want to restore it, is nothing.
Click to expand...
Click to collapse
thanks for your kind comments, can i ask one more thing: MD5 of your "recovery.img"
The MD 5 Total:
84F04BFE70C03825689A457009235AD4
Fooox1 said:
The MD 5 Total:
84F04BFE70C03825689A457009235AD4
Click to expand...
Click to collapse
hmm, interesting I now have two versions of 2.6.3.0, one 10570KB and one 8432KB, but both worked fine:
Code:
C:\ADB2>fastboot flash recovery "openrecovery-twrp-2.6.3.0-m7 (2).img"
sending 'recovery' (8432 KB)...
OKAY [ 1.216s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.897s
C:\ADB2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.059s
C:\ADB2>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.052s]
finished. total time: 0.054s
-> bootloader -> recovery and it's there
have you tried using the unlocktocken again? maybe the phone is "semi-locked"
Have it now unlock again with bootloader and TWRP (the 8432 KB) tried to flash :
C: \ fastboot2 > fastboot flash unlocktoken Unlock_code.bin
sending ' unlocktoken ' (0 KB) ...
OKAY [ 0.142s ]
writing ' unlocktoken ' ...
( bootloader ) unlock token check successfully
OKAY [ 0.005s ]
finished . total time: 0.149s
C: \ fastboot2 > fastboot flash recovery recovery- open TWRP - 2.6.3.0 - m7.img
sending ' recovery ' ( 8432 KB) ...
OKAY [ 1.123s ]
writing ' recovery ' ...
OKAY [ 0.777s ]
finished . total time: 1.904s
Ergbnis as before , everything ok, but nothing happens. This is the result , if I want to lock the bootloader again :
C: \ fastboot2 > fastboot oem lock
...
( bootloader ) Lock successfully ...
(boot loader ) mipi display off
(boot loader ) mipi_dsi_cmds_tx_ext
(boot loader ) pm8921_vreg_disable function , vreg_id = 38
(boot loader ) pm8921_vreg_disable function , vreg_id = 1
(boot loader ) TZ_HTC_SVC_DISABLE ret = 534 642 044 ( 0x1FDDFD7C )
(boot loader ) Use PSHOLD to reset device .
FAILED ( status read failed ( Too many links ) )
finished . total time: 1.138s
I have the internal SD card into suspicion. Is there a way to check this or format via fastboot / ADB?
Fooox1 said:
Have it now unlock again with bootloader and TWRP (the 8432 KB) tried to flash :
C: \ fastboot2 > fastboot flash unlocktoken Unlock_code.bin
sending ' unlocktoken ' (0 KB) ...
OKAY [ 0.142s ]
writing ' unlocktoken ' ...
( bootloader ) unlock token check successfully
OKAY [ 0.005s ]
finished . total time: 0.149s
C: \ fastboot2 > fastboot flash recovery recovery- open TWRP - 2.6.3.0 - m7.img
sending ' recovery ' ( 8432 KB) ...
OKAY [ 1.123s ]
writing ' recovery ' ...
OKAY [ 0.777s ]
finished . total time: 1.904s
Ergbnis as before , everything ok, but nothing happens. This is the result , if I want to lock the bootloader again :
C: \ fastboot2 > fastboot oem lock
...
( bootloader ) Lock successfully ...
(boot loader ) mipi display off
(boot loader ) mipi_dsi_cmds_tx_ext
(boot loader ) pm8921_vreg_disable function , vreg_id = 38
(boot loader ) pm8921_vreg_disable function , vreg_id = 1
(boot loader ) TZ_HTC_SVC_DISABLE ret = 534 642 044 ( 0x1FDDFD7C )
(boot loader ) Use PSHOLD to reset device .
FAILED ( status read failed ( Too many links ) )
finished . total time: 1.138s
I have the internal SD card into suspicion. Is there a way to check this or format via fastboot / ADB?
Click to expand...
Click to collapse
1- so i just tried the lock command:
Code:
C:\ADB3>[B]fastboot oem lock[/B]
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (Too many links))
finished. total time: 1.126s
--> it rebooted back to the ROM, i went back to bootloader and sure enough it said RELOCKED
2- "I have the internal SD card into suspicion", we could check the partitions, but I doubt that it has anything to do with it, otherwise you would be experiencing a lot of random reboots.
3- also, have you tried other "tools" that work in custom recovery, such as: http://forum.xda-developers.com/showthread.php?t=1646108
just to see if recovery is working
4- did you flash any "boot.img" (kernel)?
5- have you tried "fastboot oem unlock"
6- have you tried flashing firmware (extracted from signed OTA) in ruu mode as mentioned in post #2?
2 The suspicion arises for me, since deleted, can be moved, but the device is, after rebooting, does not run or crashes. I have already backup, Rom.zip placed on the SD, but after rebooting into recovery they're gone.
3 aromafm-1.91 can be flash, can work with it, but after the restart everything as it was, nothing gets deleted, etc.
4 I have already tried e.g. from Vodafone Rome. As usual, Ok, Ok, but not adopted.
5 At the command fastboot oem unlock:
C: \ fastboot> fastboot oem unlock
... INFO [ERR] Command error!
OKAY
6 I have tried (OTA_M7_UL_JB_50_Vodafone_UK_1.29.161.11-1.28.161.7_release_315813_signedoj2qp335qmm8qjso) unzipped and used the firmware.zip.
Have the One_All-in One_Kit tried using the. But yes you use Flash Factory RUU zip. In this case, however, the device can not connect. About sideload's not the point. Will be transmitted to mobile phones, but the flash stops.
I also tried to flash the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe . Device is detected and goes to the black screen (HTC ), of course aborts then , since it is not the correct CID .
Fooox1 said:
3 aromafm-1.91 can be flash, can work with it, but after the restart everything as it was, nothing gets deleted, etc.
Click to expand...
Click to collapse
It almost sounds like a secured kernel, can u post exact details of the ROM you're running, including link.
Did u ever flash a "boot.img" ?
Sent from my HTC One using Tapatalk
I was following this guide in order to update my formerly rooted bootloader unlocked Nexus 6. I've been able to follow those instructions in the past to update my phone, but something went wrong this time. I'm on the MMB29Q version, so I downloaded the MMB29Q to MMB29V update, the link to which I found on this site. I also downloaded the MMB29Q factory image from Google's list of them and extracted the system.img file. My phone has the stock recovery, and my computer is on Arch Linux with adb version 1.0.36 and fastboot version 7.1.2_r6.
I was able to erase the system image easily enough:
Code:
$ ~ adb reboot bootloader
$ ~ fastboot erase system
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.673s]
finished. total time: 0.673s
However, when I then tried to flash the system image,
Code:
$ ~ fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (518702 KB)...
OKAY [ 16.242s]
writing 'system' 1/4...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.250s
it failed on me. According to the bootloader splash screen, my "Device is UNLOCKED. Status Code: 3" (I read somewhere that the Preflash validation failed message corresponds with an unlocked bootloader).
One other thing to note is that I remember leaving the checkbox for allowing oem unlock in developer options unchecked, which I am now realizing was probably where I went wrong (I ran fastboot oem unlock as a test, and it told me to Check 'Allow OEM Unlock' in Developer Options). However, because I cleared the system image, I don't know how I can change that setting anymore. I also realize that I didn't need to do this step in the updating process because my phone was already unrooted and thus system.img should have been stock (I think, at least). I tried re-erasing the system image and reflashing it, but that unfortunately did not fix anything. Any advice would be much appreciated!
Progress! I was able to flash TWRP, back up all my data just in case, and then follow this guide, which toggles the "Allow OEM Unlock" developer settings without having a working operating system. Running fastboot oem unlock no longer gives the error about checking that box in Settings. However, I'm still getting that same error when I try to flash the system.img. After that failed, I am fresh out of ideas, given that the problem does not seem to be that option. Anyone have any ideas?
Edit: I now realize I am a moron. I found this thread on Android.SE and realized that I had in fact downloaded the Nexus 6P MMB29Q version and that is why it failed. After downloading the correct verion, rewiping the system partition, and reflashing it, my phone works again!
Hi Folks,
Need some help here. I'm new to flash and other stuff.
I tried to install Lineage 15.1. I did fastboot oem unlock which erased everything. I'm stuck in AP fastboot Flash Mode.
I tried below things.
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 18.385s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 18.400s
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash recovery twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.422s]
booting...
OKAY [ 0.031s]
finished. total time: 0.469s
[PHONE GETS TWRP RECOVERY SCREENS]
I tried adb sideload as suggested in one of the pages and got this
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload lineage-15.1-20180402-nightly-shamu-signed.zip
Total xfer: 0.01x
In Phone :
Starting ADB sideload feature ..
Installing zip file '/sideload/package.zip'
Warning: No file_contexts
Target : google/shamu/shamu:7.1.1/N6F27m/4299435:user/release-keys
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: Failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid Argument
Failed to unmount /system : No such volume
script aborted (no error message)
Updater process ended with ERROR: 7
Finally, I tried with copying installer files in OTG Drive and tried to install from there. But couldn't mount it as I can't make OTG check in Mount in TWRP.
Please help .. How can I overcome this and install OS in my phone.
Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.
mal13 said:
Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.
Click to expand...
Click to collapse
Yes, I can boot into twrp using this command...
fastboot.exe boot twrp-3.2.1-0-shamu.img
This bringstwrp in my phone. But I can't move files to the phone. Even I tried adb push which pushes the files to the phone but while installing it got failed.. I'm not sure what I'm missing..
I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Same issue with Minimal ADB. I used 1.4 ...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 15.628s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 15.644s
vigkumar said:
Same issue with Minimal ADB. I used 1.4 ...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 15.628s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 15.644s
Click to expand...
Click to collapse
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.
vigkumar said:
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.
Click to expand...
Click to collapse
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Thank you very much for your response. I tried both Fastboot and ADB. Both failed Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.
What is the right way to identify the correct radio file.
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.
Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.
finished. total time: 0.094s
ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
OKAY [ 0.038s]
finished. total time: 0.469s
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip
Total xfer: 0.01x
Even it got failed with the below error.
Installing zip file '/sideload/package.zip'
Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater Process ended with Error 7.
vigkumar said:
Thank you very much for your response. I tried both Fastboot and ADB. Both failed Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.
What is the right way to identify the correct radio file.
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.
Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.
finished. total time: 0.094s
ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
OKAY [ 0.038s]
finished. total time: 0.469s
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip
Total xfer: 0.01x
Even it got failed with the below error.
Installing zip file '/sideload/package.zip'
Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater Process ended with Error 7.
Click to expand...
Click to collapse
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.
Try fastboot flashing with the sim card removed.
The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
vigkumar said:
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip
Click to expand...
Click to collapse
That was your first error! You can't flash a nightly via fastboot.
You need to boot into recovery and select it there to install.
ktmom said:
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.
Try fastboot flashing with the sim card removed.
The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Both method failed. :crying::crying:
vigkumar said:
Both method failed. :crying::crying:
Click to expand...
Click to collapse
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?
As @Elektroschmock pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.
** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:
Code:
fastboot devices
return?
The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?
As @Elektroschmock pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.
** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:
Code:
fastboot devices
return?
The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Yes, I'm trying stock and followed links that you provided. Both installation methods failed.
Fastboot devices returns,
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot devices
ZX1G525DZX fastboot
Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".
Navigate into the extracted folder (e.g "shamu-n6f27h")
Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"
Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".
Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;
boot.img
cache.img
recovery.img
system.img
userdata.img
Navigate on the PC to the location where the fastboot binary is.
Boot the phone into fastboot by pushing and holding the volume down and power buttons
Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.
Double check that "fastboot devices" returns your device.
Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.
Code:
1) flash the boot image (also called the kernel):
fastboot flash boot boot.img
reboot:
fastboot reboot-bootloader
2) If you want, you can flash the radio:
fastboot flash radio radio.img
reboot:
fastboot reboot-bootloader
3) flash recovery:
fastboot flash recovery recovery.img
reboot:
fastboot reboot-bootloader
4) flash system partition:
fastboot flash system system.img
reboot:
fastboot reboot-bootloader
5) flash userdata (which will wipe the internal storage:
fastboot flash userdata userdata.img
reboot:
fastboot reboot-bootloader
6) flash cache:
fastboot flash cache cache.img
Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot
If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.
Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.
ktmom said:
Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".
Navigate into the extracted folder (e.g "shamu-n6f27h")
Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"
Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".
Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;
boot.img
cache.img
recovery.img
system.img
userdata.img
Navigate on the PC to the location where the fastboot binary is.
Boot the phone into fastboot by pushing and holding the volume down and power buttons
Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.
Double check that "fastboot devices" returns your device.
Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.
Code:
1) flash the boot image (also called the kernel):
fastboot flash boot boot.img
reboot:
fastboot reboot-bootloader
2) If you want, you can flash the radio:
fastboot flash radio radio.img
reboot:
fastboot reboot-bootloader
3) flash recovery:
fastboot flash recovery recovery.img
reboot:
fastboot reboot-bootloader
4) flash system partition:
fastboot flash system system.img
reboot:
fastboot reboot-bootloader
5) flash userdata (which will wipe the internal storage:
fastboot flash userdata userdata.img
reboot:
fastboot reboot-bootloader
6) flash cache:
fastboot flash cache cache.img
Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot
If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.
Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.
Click to expand...
Click to collapse
Thanks a lot for your assistance on this. I followed your exact instructions and it is given below.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>dir *.img
Volume in drive C is Windows8_OS
Volume Serial Number is 40E0-62B9
Directory of C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools
01-01-2009 00:00 8,686,822 boot.img
01-01-2009 00:00 6,398,184 cache.img
26-09-2017 16:53 118,279,680 radio.img
01-01-2009 00:00 14,206,186 recovery.img
01-01-2009 00:00 1,619,795,140 system.img
01-01-2009 00:00 142,201,816 userdata.img
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot devices
ZX1G525DZX fastboot
You're right. Initially it was DEVICE is UNLOCKED. Status Code 3.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
Once reboots, it says DEVICE IS LOCKED. Status Code 2. I had to long press the power key, which unlocks the DEVICE.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (8483 KB)...
OKAY [ 0.285s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.338s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.737s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.774s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13873 KB)...
OKAY [ 0.580s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.617s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (522524 KB)...
OKAY [ 18.848s]
writing 'system' 1/4...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.901s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash userdata userdata.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.037s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
vigkumar said:
Thanks a lot for your assistance on this. I followed your exact instructions and it is given below.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>dir *.img
Volume in drive C is Windows8_OS
Volume Serial Number is 40E0-62B9
Directory of C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools
01-01-2009 00:00 8,686,822 boot.img
01-01-2009 00:00 6,398,184 cache.img
26-09-2017 16:53 118,279,680 radio.img
01-01-2009 00:00 14,206,186 recovery.img
01-01-2009 00:00 1,619,795,140 system.img
01-01-2009 00:00 142,201,816 userdata.img
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot devices
ZX1G525DZX fastboot
You're right. Initially it was DEVICE is UNLOCKED. Status Code 3.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
Once reboots, it says DEVICE IS LOCKED. Status Code 2. I had to long press the power key, which unlocks the DEVICE.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (8483 KB)...
OKAY [ 0.285s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.338s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.737s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.774s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13873 KB)...
OKAY [ 0.580s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.617s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (522524 KB)...
OKAY [ 18.848s]
writing 'system' 1/4...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.901s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash userdata userdata.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.037s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Couple of questions.
You are working on a Nexus 6, right? Not a 6P or other device?
Did you reboot between each img flash? When you returned to the bootloader each time after rebooting, did you long press the power button because it still said "locked status 2"?
I have to say, this is the first I've ever heard of a reboot causing it to be locked then long pressing the power button to unlock. Either the bootloader is unlocked or it isn't.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
---------- Post added at 14:03 ---------- Previous post was at 14:00 ----------
Additional question, when you reboot using only the key combination, does it always show unlocked?
If yes to that, maybe it's back to my concern that the version of fastboot is not working well with the N6.
If you haven't, try with the minimal version you downloaded the other day.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I
vigkumar said:
Both method failed. :crying::crying:
Click to expand...
Click to collapse
1] If u can get to twrp, use microUSB flash drive and move ROMs over to flash via TWRP. Must mount OTG drive in TWRP after plugin to recognize flash drive
2) if u can get to fastboot mode and your PC recognizes your device via "fastboot device" command, try using WUG NRT tool kit to restore back to stock, then root @ND put TWRP on there, then flash custom Roms via TWRP
novice here. screwed up my 6p and got in a similar place as you are. i started adb side load in my phone and linux pc terminal, adb start-server, then adb sideload [add a space] then i dragged and dropped the factory firmware to terminal then enter. i had to try a couple of googles angler firmware before it found the the right format. saved my bacon.
Good point. If fails on Windows, Linux PC may work
I restored my boot.img from within Magisk because I need to OTA update. Now the phone will only boot into the bootloader with the message
AP Fastboot Flash Mode(Secure)
No Bootable A/B Slot
Failed to Boot Linux, falling back to fastboot
Nothing will work through fastboot. I've tried switching slots, re-flashing the boot.img, and re-flashing the ROM, but the flashing won't even start. Every command I try to run brings up a code on the phone that says "cmd: getvar:slot-count." My phone can be found by the fastboot devices command.Has anyone encountered and fixed this before?
doodalydoo said:
I restored my boot.img from within Magisk because I need to OTA update. Now the phone will only boot into the bootloader with the message
AP Fastboot Flash Mode(Secure)
No Bootable A/B Slot
Failed to Boot Linux, falling back to fastboot
Nothing will work through fastboot. I've tried switching slots, re-flashing the boot.img, and re-flashing the ROM, but the flashing won't even start. Every command I try to run brings up a code on the phone that says "cmd: getvar:slot-count." My phone can be found by the fastboot devices command.Has anyone encountered and fixed this before?
Click to expand...
Click to collapse
Just re-flash the system back manually from fastboot. You can find instructions all over the place.
johnjingle said:
Just re-flash the system back manually from fastboot. You can find instructions all over the place.
Click to expand...
Click to collapse
It won't work. When I input the fastboot command into cmd, it doesn't proceed and then I get a code on my phone that says "cmd: getvar:slot-count." No fastboot commands will work, even though my phone is detected as a fastboot device. I don't get it.
doodalydoo said:
It won't work. When I input the fastboot command into cmd, it doesn't proceed and then I get a code on my phone that says "cmd: getvar:slot-count." No fastboot commands will work, even though my phone is detected as a fastboot device. I don't get it.
Click to expand...
Click to collapse
That doesn't sound fun.
Have you tried:
fastboot getvar all
or
fastboot boot ****.img (TWRP image.)
just to see if fastboot can output the details about your phone?
johnjingle said:
That doesn't sound fun.
Have you tried:
fastboot getvar all
or
fastboot boot ****.img (TWRP image.)
just to see if fastboot can output the details about your phone?
Click to expand...
Click to collapse
I turned "Tools mode" on and now I actually get the progress of the fastboot command.
C:\adb>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-suffi: not found
(bootloader) slot-suffixes: not found
(bootloader) max-download-sizestem: not found
target didn't report max-download-size
sending 'system' (524284 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.016s
C:\adb>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-suffi: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'system' (524284 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.016s
C:\adb>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'system' (524284 KB)...
It freezes after this.
C:\adb>fastboot getvar all
(bootloader) allt-count: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot boot twrp-3.2.3-1-payton.img
downloading 'boot.img'...
OKAY [ 0.642s]
booting...
(bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote failure)
finished. total time: 0.658s
This is what it says when I try to run the commands you suggested.
Edit: My bootloader was unlocked before this happening, I just want to make sure it didn't relock and that's the problem. When it says "flashing_unlock" in recovery mode, that means the bootloader is unlocked right?
Ok a weird thing happened. Somehow the phone went from a soft brick to a hard brick. It didn't hard brick during the whole time I was trying to fix it. The last thing I did was put it on the charger and when I took it off the charger, it was hard bricked. This actually turned out to be exactly what I needed because it put the phone in the position where I could use the blankflash file. My phone is now working!
Ok it's back to not working again! I managed to get the phone booted, but it kept crashing so I booted into TWRP to wipe the system so I could do a clean install. Now none of the fastboot commands are working again. The recovery mode looks like it supposed to now unlike last time. I'm also able to sometimes run "fastboot getvar all" now, but it doesn't work all the time. I have no clue what is going on.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2253DPJK
I've managed to get the phone to boot up again, but the fastboot commands have also stopped working again. I don't know what to do at this point and I'm also afraid the next thing I do will just break the phone again.. If the phone is booting up properly, why aren't the fastboot commands working?
doodalydoo said:
Ok it's back to not working again! I managed to get the phone booted, but it kept crashing so I booted into TWRP to wipe the system so I could do a clean install. Now none of the fastboot commands are working again. The recovery mode looks like it supposed to now unlike last time. I'm also able to sometimes run "fastboot getvar all" now, but it doesn't work all the time. I have no clue what is going on.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2253DPJK
I've managed to get the phone to boot up again, but the fastboot commands have also stopped working again. I don't know what to do at this point and I'm also afraid the next thing I do will just break the phone again.. If the phone is booting up properly, why aren't the fastboot commands working?
Click to expand...
Click to collapse
Try downloading mfastboot, don't use a script, manually install each file and see what happens after each flash, etc.
For example:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------
doodalydoo said:
Ok it's back to not working again! I managed to get the phone booted, but it kept crashing so I booted into TWRP to wipe the system so I could do a clean install. Now none of the fastboot commands are working again. The recovery mode looks like it supposed to now unlike last time. I'm also able to sometimes run "fastboot getvar all" now, but it doesn't work all the time. I have no clue what is going on.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2253DPJK
I've managed to get the phone to boot up again, but the fastboot commands have also stopped working again. I don't know what to do at this point and I'm also afraid the next thing I do will just break the phone again.. If the phone is booting up properly, why aren't the fastboot commands working?
Click to expand...
Click to collapse
Also, did you have anything like this at the bottom of that fastboot command?
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
johnjingle said:
Try downloading mfastboot, don't use a script, manually install each file and see what happens after each flash, etc.
For example:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------
Also, did you have anything like this at the bottom of that fastboot command?
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Click to expand...
Click to collapse
The phone is working again and I think for good this time. Getting the fastboot commands to work was just a matter of luck I guess. I had no method, I was just randomly unplugging, plugging in, holding different keys, and powering on and off until I was lucky enough to get it to work. Once the fastboot started working, I just wiped the phone completely and clean flashed the newest ROM. I haven't had any problems since then. I think what caused all of this was I was dirty flashing improperly. I tried picking out the commands I thought were necessary from the ROM flashing commands, but wouldn't erase my data. I must have left out critical flash commands. Just so I'm sure and I don't have to go through this again, will running the ROM flash commands you posted except "mfastboot erase userdata" work to properly flash the ROM while leaving my data intact?
doodalydoo said:
The phone is working again and I think for good this time. Getting the fastboot commands to work was just a matter of luck I guess. I had no method, I was just randomly unplugging, plugging in, holding different keys, and powering on and off until I was lucky enough to get it to work. Once the fastboot started working, I just wiped the phone completely and clean flashed the newest ROM. I haven't had any problems since then. I think what caused all of this was I was dirty flashing improperly. I tried picking out the commands I thought were necessary from the ROM flashing commands, but wouldn't erase my data. I must have left out critical flash commands. Just so I'm sure and I don't have to go through this again, will running the ROM flash commands you posted except "mfastboot erase userdata" work to properly flash the ROM while leaving my data intact?
Click to expand...
Click to collapse
The only line I "usually" usually leave out is the erase "mfastboot user data", unless I am coming from a ROM or want a completely fresh start.
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down ___
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
CheckS86 said:
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down ___
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
Click to expand...
Click to collapse
did you get the solution ?? I'm in the same situation help
CheckS86 said:
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down ___
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
Click to expand...
Click to collapse
did u find the solution? i have the same problem with my note 20 ultra cant start the phone and the OEM is ON (L)
Wow. With a little more time another user (HTC U11+) enters the queue of the mishaps! Any Luck anyone? HTCDev also seem to have given up with no option to login to their website.