Database Develop

[Q] Htc one boot loop stuck. No Recovery

Hi
I have this Htc one and its stuck on bootloop . i have tried the guide by LibertyMarine "http://forum.xda-developers.com/showthread.php?t=2632736" but i cant istall the recovery. After sending the recovery phone does not go into recovery and comes back to bootloader screen. any idea or help is appreciated thanks
Tampered
Relocked
Security Warning
M7_UL PVT SHip S-ON RH
Hboot-1.54.0000
Radio-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.161.1
eMMC-boot 2048MB
Jun 23 2013,03:49:03.0

Your device is relocked. Needs to be unlocked via HTC Dev. and then send recovery.
Post your commands and their output once you flash recovery

thanks
SaHiLzZ said:
Your device is relocked. Needs to be unlocked via HTC Dev. and then send recovery.
Post your commands and their output once you flash recovery
Click to expand...
Click to collapse
Hi this what i get thanks. Also after the unlock bootloader from HTC DEv I still get RELOCKED
C:\adb>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.159s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.173s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.060s]
finished. total time: 0.063s
C:\adb>fastboot flash recovery "C:\adb\recovery.img"
sending 'recovery' (9184 KB)...
OKAY [ 1.165s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.050s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.044s]
finished. total time: 0.047s

its done now
hi
i tried again after alittle bit more charge to the battery and this time after unlock bootloader from htc dev it worked fine and i have got "Unlocked" on bootloader and Recovery installed successfully subsequently.
Thanks for the lead mate.
C:\adb>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.161s
C:\adb>
C:\adb>fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.104s]
finished. total time: 0.105s
C:\adb>fastboot flash recovery "C:\adb\recovery.img"
sending 'recovery' (9184 KB)...
OKAY [ 1.164s]
writing 'recovery'...
OKAY [ 0.722s]
finished. total time: 1.891s
C:\adb>adb push "C:\Users\Admin\Downloads\rom.zip" /sdcard/rom.zip
2224 KB/s (1204493869 bytes in 528.674s)

delete

Wonderful

erase fail
I get message FAILED (remote: not allowed) at erasing cash

i cant lock the bootloader of my nexus 6

hello i can't lock the bootloader of my nexus 6 since i received it from the technical service of motorola. before i send it to them it was closed and when i received it it was unlock and another no padlock its apear when is booting. ive traid every thing but nothing work
i can flash factory images but i cant relock it. fastboot oem lock works on my nexus 7 but not on my nexus 6

You should use the correct command, as google documents it.
But locking your bootloader is a pretty bad idea, and will prevent you from having any ability to fix anything if it fails to boot. If you cannot boot into android, you cannot enable unlock, and will be locked out for good with no recourse other then to send it in.
See this page
https://source.android.com/security/verifiedboot/verified-boot.html
Scroll down to "changing the device state" and use the given fastboot command.

i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem

alex482 said:
i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem
Click to expand...
Click to collapse
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.

istperson said:
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.
Click to expand...
Click to collapse
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly

alex482 said:
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly
Click to expand...
Click to collapse
Do other adb/fastboot commands work?

What does
Code:
fastboot devices
say?

yes its work adb devices , adb reboot, adb reboot bootloader, fastboot flash...., fastboot devices , fastboot reboot and fastboot reboot-bootloader

istperson said:
What does
Code:
fastboot devices
say?
Click to expand...
Click to collapse
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot

C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.077s
that it what it say when i tried to lock it but i also tried to flash the factory image its work but then when i try to lock it the same massage appear again

Please paste here the output of flashing the factory image.

istperson said:
Please paste here the output of flashing the factory image.
Click to expand...
Click to collapse
yes when its finish i copy and past everything here

I'd be curious what specific error it gives with the fastboot flashing lock says, as that should be the command now assuming your on MM and using up to date SDK.

C:\Program Files (x86)\platform-tools>adb devices
List of devices attached
ZX1G423BMR device
C:\Program Files (x86)\platform-tools>adb reboot bootloader
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot
C:\Program Files (x86)\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
C:\Program Files (x86)\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\Program Files (x86)\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.617s]
finished. total time: 0.617s
C:\Program Files (x86)\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.409s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.685s]
finished. total time: 1.102s
C:\Program Files (x86)\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
C:\Program Files (x86)\platform-tools>fastboot flash radio radio-shamu-d4.01-9625-05.27+fsg-9625-02.104.img
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.283s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.522s]
finished. total time: 5.808s
C:\Program Files (x86)\platform-tools>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\platform-tools>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (517178 KB)...
OKAY [ 20.071s]
writing 'system'...
OKAY [ 6.964s]
sending sparse 'system' (515137 KB)...
OKAY [ 20.267s]
writing 'system'...
OKAY [ 7.088s]
sending sparse 'system' (518219 KB)...
OKAY [ 20.493s]
writing 'system'...
OKAY [ 7.188s]
sending sparse 'system' (492726 KB)...
OKAY [ 19.042s]
writing 'system'...
OKAY [ 6.804s]
finished. total time: 107.938s
C:\Program Files (x86)\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8197 KB)...
OKAY [ 0.316s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.431s
C:\Program Files (x86)\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8915 KB)...
OKAY [ 0.334s]
writing 'recovery'...
OKAY [ 0.126s]
finished. total time: 0.463s
C:\Program Files (x86)\platform-tools>fasboot flash cache cache.img
"fasboot" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
C:\Program Files (x86)\platform-tools>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.057s]
sending 'cache' (6248 KB)...
OKAY [ 0.237s]
writing 'cache'...
OKAY [ 0.137s]
finished. total time: 0.446s
C:\Program Files (x86)\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.349s]
finished. total time: 1.349s
C:\Program Files (x86)\platform-tools>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.165s]
sending 'userdata' (138868 KB)...
OKAY [ 5.070s]
writing 'userdata'...
OKAY [ 3.001s]
finished. total time: 9.236s
C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.070s
C:\Program Files (x86)\platform-tools>fastboot reboot
rebooting...
finished. total time: -0.000s

yes im on 6.0 marshmallow and the sdk with the latest update

Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?

istperson said:
Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?
Click to expand...
Click to collapse
yes its all turn on i send to it to change the rear camera because it was factory failure

Then it too must be a hardware problem.

do you think so?

alex482 said:
do you think so?
Click to expand...
Click to collapse
It seems, you did everything right. The line "(bootloader) Please flash valid signed images firstly!" is returned by the bootloader, and the bootloader is, opposite to adb and fastboot, closed source. So no help from the source.
I googled it, and it appeared on the Moto G 2014 device.

Can I still battery charging after a Fullwipe?

Hello, I was on Android Marshmellow 6.0.1 + SU and I made with TWRP a full backup (+TA.img). I wiped:
+Dalwik
+Cache
+Data
+System
+Internal Storage
-Micro SDcard
Then booting into the TRWP 3.1.0.1 revovery did not work anymore (only Sony logo) and I thought I have to flash TWRP again. I used cmd administrator with this commands:
C:\adb>fastboot.exe -i 0x0fce oem unlock 0xxxx640DA639C0xxx
...
OKAY [ 3.281s]
finished. total time: 3.281s
C:\adb>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (13092 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.875s]
finished. total time: 1.422s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.000s
I hold the volume down button and i was able to come into TWRP menu. Problem: I forgot to save my Lineage files on Micro SDcard, so flashing was not possible for me and I made it off (Volup + Power) After copieng with the pc the needed flash files to micro sdcard I tried again booting to TWRP recovery but does still not work. Then I tried some more commands:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.063s]
finished. total time: 0.484s
C:\adb>fastboot reboot
< waiting for any device >
rebooting...
finished. total time: -0.000s
C:\adb>adb ls -h
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
C:\adb>adb shell
error: no devices/emulators found
C:\adb>adb devices
List of devices attached
C:\adb>fastboot devices
YT9119CPJT fastboot
C:\adb>
I´m still in a bootloop and i can not see that my smartphone is charging the battery. At last it saw only 50% in TRWP
and I don´t realy know what I have to do now. Need HELP :crying:
P.S.: I am on Windows 10 home (64 bit) and flashtool-0.9.25.0 told me all drivers was succefuly installed (with Win10 Disable Driver Signature Enforcement) and I used twrp-3.0.2-1-z3c.img
Edit: After some research, I read the battery can not charging, because it's in bootloader mode and i have to flash the stock rom back. I did it succesfully with flashtool

fastboot boot recovery.img FAILED(remote: unknown command)

Hey guys,
I have ZTE Red Magic with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP. So I booted into the bootloader, entered "fastboot boot recovery.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.582s
The installation of recovery was successful as I typed the command "fastboot flash recovery recovery.img"
target reported max download size of 536870912 bytes
sending 'recovery' (26721 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.001s]
finished. total time: 0.583s
I have absolutely no idea what I'm doing wrong. pls help

boyDbest said:
Hey guys,
I have ZTE Red Magic with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP. So I booted into the bootloader, entered "fastboot boot recovery.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.582s
The installation of recovery was successful as I typed the command "fastboot flash recovery recovery.img"
target reported max download size of 536870912 bytes
sending 'recovery' (26721 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.001s]
finished. total time: 0.583s
I have absolutely no idea what I'm doing wrong. pls help
Click to expand...
Click to collapse
Did you unlocked bootloader?

methuselah said:
Did you unlocked bootloader?
Click to expand...
Click to collapse
Yes brother i did

Unable to unlock/flash recovery

I am trying to unlock the bootloader and flash TWRP for the first time. I followed the steps from here: https://wiki.lineageos.org/devices/s2/install
I turned on the unlock option in settings and unlocked via fastboot, rebooted it manually (it didn't reboot), and then tried to flash:
Code:
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
$ ./adb reboot bootloader
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.779s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.836s]
Writing 'recovery' OKAY [ 0.231s]
Finished. Total time: 1.071s
$ ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
However, I got into the stock recovery page instead of TWRP. You can see above that the flash failed before I rebooted, but succeeded after that. Interesting observations:
- The above webpage indicates that the device should reset when I reboot, but it didn't, which means the unlock didn't work.
- When I went back to bootloader, the first attempt to flash failed, but when I ran another unlock it worked though apparently it did nothing.
Am I missing a step? I am using fastboot version 29.0.6-6198805 on Mac OS Mojave 10.14.6.

Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.

kalehrl said:
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
Click to expand...
Click to collapse
Thank you! That got me into TWRP with a dialog titled "Unmodified System Partition" with a slider to allow modifications. I am googling to see what this dialogue is about and how to get TWRP to permanently get installed.

That's normal. Just enable modifications and that's it.

kalehrl said:
That's normal. Just enable modifications and that's it.
Click to expand...
Click to collapse
OK, I don't remember seeing it before (I haven't flashed in at least a couple of years). I ran `adb reboot recovery` and it did go back into TWRP, so I am assuming that it did get persisted. For some reason "Never show this screen..." option didn't work, which is fine, but does it indicate that something is still readonly?

I don't think so.
You're good to proceed.

I was able to sideload the ROM and opengapps nano and it is booting up for the first time. I skipped the optional step to install root (AddonSU), I guess I can do it later too if I feel the need to get root. Thanks a lot for your quick help.

No problem.
If you want to root it, do it with Magisk.
Nowadays, LineageOS team recommend it.