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
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.
Hello my hope :3
actually i cannot access my recovery or the os, if i start the device, its just a bootloop.
Fastboot is possible, but bootloader is locked and im not able to tick something in the develeloper settings because there is no os anymore.
C:\adb>fastboot flash recovery recovery_OBT7.img
target reported max download size of 442499072 bytes
sending 'recovery' (22237 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.529s
Click to expand...
Click to collapse
i tried the Snapdragon tool(MsmDownloadTool) also but only get this error: FirehoseWriteData Failed, do you have any suggestions? :c
im stuck with this piece of sh*t phone and "waiting for any device". I flashed TWRP 142314 times on my phone, and today this bloody problem comes out and i cant f*king solve it. My drivers and everything is up to date, expect something named "S1 Boot Fastboot" (warning sing near that in device manager). I have no idea what the hell is that and i cant flash twrp and install custom rom. Any ideas, excpet that one about uninstalling win10 )))
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
nevenx said:
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
Click to expand...
Click to collapse
You can't flash TWRP to the recovery partition on the Xperia Z. It doesn't use the recovery partition; instead, it uses the FOTAKernel partition, which is inaccessible by Fastboot. If you want to destroy your old stock firmware and install custom ROM, flash TWRP to boot partition. The phone should not boot to the firmware and boots straight to TWRP.
I am leaving house for 2 weeks in 7 hours i realluy need help in flashing my phone I cant flash Vendor in fastboot
and i think it doesnt boot becxause of error flashing and erasing vendor
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot flash recovery twrp-3.1.1-2-v1-prague.img
target reported max download size of 471859200 bytes
sending 'recovery' (24468 KB)...
OKAY [ 0.855s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 2.042s
C:\Users\Matas Niewulis\Desktop\Pulpit>
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot flash erase vendor
error: cannot load 'vendor'
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot reboot
rebooting...
finished. total time: 0.341s
C:\Users\Matas Niewulis\Desktop\Pulpit>
please help me fix my device.. sorry for a mess in this post, im in a hurry
ooooh **** i restored my device to working oreder by doing fix vendor partition in twrp..
but i still have the problem with fingerprint, security, dev options etc
Vendor you can flash only by twrp/ restoring.
Which firmware do you have?