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
Related
ok I have 2 htc one, I s-off'ed one 6 months ago and its been working fine since then.
but today I tried to s-off the other one may built having hboot 1.44
I got it s-off successfully and unlocked but there are no red warning that your htc one is a development blah blah on the welcome screen
I flashed the twrp recovery 3 times but when I enter the recovery mode first a blue screen appears and then the red triangle with exclamation mark!
note: the custome recovery flashes successfully
also I have used fastboot erase cache also
Just to clear things up: S-off was achieved back in June/early July for Hboot 1.44
Hboot 1.54 S-off was achieved two weeks ago with a different method to the first one.
Hboot 1.44 modified Hboots are available where the red warning flag has been removed, and I guess you put that one on your second One.
gunswordx said:
ok I have 2 htc one, I s-off'ed one 6 months ago and its been working fine since then.
but today I tried to s-off the other one may built having hboot 1.44
I got it s-off successfully and unlocked but there are no red warning that your htc one is a development blah blah on the welcome screen
I flashed the twrp recovery 3 times but when I enter the recovery mode first a blue screen appears and then the red triangle with exclamation mark!
note: the custome recovery flashes successfully
also I have used fastboot erase cache also
Click to expand...
Click to collapse
Bad download? Try to download Twrp again or try CWM rercovery
hardstuffmuc said:
Just to clear things up: S-off was achieved back in June/early July for Hboot 1.44
Hboot 1.54 S-off was achieved two weeks ago with a different method to the first one.
Hboot 1.44 modified Hboots are available where the red warning flag has been removed, and I guess you put that one on your second One.
Click to expand...
Click to collapse
I tried the old revone method(same file I used for the previous one)
also I checked the md5 and have download almost all the versions of twrp. to be sure I even flashed it on my previous one and was working there
I would also try the CWM recovery with
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
and make sure you use a USB 2.0 on your computer. Apparently USB 3.0 may cause problems
hardstuffmuc said:
I would also try the CWM recovery with
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
and make sure you use a USB 2.0 on your computer. Apparently USB 3.0 may cause problems
Click to expand...
Click to collapse
yes tried all the recoveries
the thing is even though fastboot says flashed successfully, the stock recovery is still there !
also i have only usb 2.0
gunswordx said:
yes tried all the recoveries
the thing is even though fastboot says flashed successfully, the stock recovery is still there !
also i have only usb 2.0
Click to expand...
Click to collapse
can you copy/paste the command prompt, including a DIR of the folder, so we can take a look?
251|[email protected]:/data/local/tmp $
c:\ADB>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful - no need to reboot.
10|[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful.
[email protected]:/data/local/tmp $ exit
exit
c:\ADB>adb reboot-bootloader
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.825s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.810s
c:\ADB>fastboot flash recovery recovery.img
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.608s]
finished. total time: 1.810s
c:\ADB>fastboot oem writecid 11111111
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.016s]
finished. total time: 0.016s
c:\ADB>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.856s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.206s]
writing 'recovery'...
OKAY [ 0.663s]
finished. total time: 1.871s
c:\ADB>fastboot flash recovery recovery-TWRP-newbl.img
sending 'recovery' (7238 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.794s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
c:\ADB>adb reboot-bootloader
c:\ADB>
gunswordx said:
251|[email protected]:/data/local/tmp $
c:\ADB>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful - no need to reboot.
10|[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful.
[email protected]:/data/local/tmp $ exit
exit
c:\ADB>adb reboot-bootloader
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.825s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.810s
c:\ADB>fastboot flash recovery recovery.img
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.608s]
finished. total time: 1.810s
c:\ADB>fastboot oem writecid 11111111
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.016s]
finished. total time: 0.016s
c:\ADB>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.856s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.206s]
writing 'recovery'...
OKAY [ 0.663s]
finished. total time: 1.871s
c:\ADB>fastboot flash recovery recovery-TWRP-newbl.img
sending 'recovery' (7238 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.794s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
c:\ADB>adb reboot-bootloader
c:\ADB>
Click to expand...
Click to collapse
why use revone again, and why so many flashes?
Just:
adb reboot bootloader (no - needed in adb)
fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader (- is needed in fastboot)
Then just select RECOVERY using VOL Up or Down, press POWER to enter into recovery.
the first time revone didn't work so I had to do it again.
got s-off and super cid
after each recovery flash I rebooted bootloader and went to recovery but same red triangle
that's why so many recovery flashes
gunswordx said:
the first time revone didn't work so I had to do it again.
got s-off and super cid
after each recovery flash I rebooted bootloader and went to recovery but same red triangle
that's why so many recovery flashes
Click to expand...
Click to collapse
OK, just reboot your phone and try the steps, I posted above.
tried but same result. I can't seem to flash the recovery even though the cmd window says successful
gunswordx said:
tried but same result. I can't seem to flash the recovery even though the cmd window says successful
Click to expand...
Click to collapse
very weird, you feel like trying one more time?
Download this:
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
Check MD5: 1c6afb14db3f305b0ad7d85d5af80bef
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot
adb reboot recovery
and post back command prompt.
nkk71 said:
very weird, you feel like trying one more time?
Download this:
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
Check MD5: 1c6afb14db3f305b0ad7d85d5af80bef
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot
adb reboot recovery
and post back command prompt.
Click to expand...
Click to collapse
ok will try
Hi All,
please help I want to fix my phone no root no custom firmware just to want device work again
i tried htcdev to unlock no luck
fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: -0.000s
**************
fastboot flash recovery recovery_cwm_hboot1.03.img
sending 'recovery' (6992 KB)...
OKAY [ 0.219s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.234s
my phone stuck in recovery mode please help HTC Desire 500
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.
Hey guys. I really need the eu firmware (germany) for my G6!!! I bricked my G6 and cant boot up.
I wanted to flash the magisk patched boot img from the forum and have unfortunately overlooked that it was for the g6 plus -.- My bootloader is unlocked, but everytime when i turn on device, i have the message: Your device has been unlocked and cant be trusted. ID: bad key... and i cant boot up! I tried to flash the g6 firmware from the forum, but without solution... The Message freeze it and the phone cant boot.
i hope anyone has the eu firmware for me or any help! ^^
Heres my log:
C:\adb>fastboot oem fb_mode_set
... OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash partition gpt.bin
sending 'partition' (45 KB)... OKAY [ 0.000s]
writing 'partition'... INFOValidating 'gpt.default.xml'
INFOCommitting 'gpt.default.xml'
INFO- flashing 'gpt_main0.bin' to 'partition:0'
INFOFlashing primary GPT image...
INFOFlashing backup GPT image...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adb>fastboot flash bootloader bootloader.img
sending 'bootloader' (7419 KB)... OKAY [ 0.234s]
writing 'bootloader'... INFOValidating 'bootloader.default.xml'
INFOSecurity version downgrade
INFOImage aboot failed validation
INFOPreflash validation failed
INFOCancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.438s
C:\adb>fastboot flash logo logo.bin
sending 'logo' (2182 KB)... OKAY [ 0.062s]
writing 'logo'... OKAY [ 0.047s]
finished. total time: 0.109s
C:\adb>fastboot flash boot boot.img
sending 'boot' (22528 KB)... OKAY [ 0.719s]
writing 'boot'... INFOImage signed with key bad key
OKAY [ 0.266s]
finished. total time: 0.984s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (22628 KB)... OKAY [ 0.734s]
writing 'recovery'... INFOImage signed with key bad key
OKAY [ 0.359s]
finished. total time: 1.094s
C:\adb>fastboot flash dsp adspso.bin
sending 'dsp' (16384 KB)... OKAY [ 0.516s]
writing 'dsp'... OKAY [ 0.156s]
finished. total time: 0.672s
C:\adb>fastboot flash oem oem.img
sending 'oem' (206464 KB)... OKAY [ 6.550s]
writing 'oem'... OKAY [ 1.456s]
finished. total time: 8.006s
C:\adb>fastboot flash system system.img_sparsechunk.0
sending 'system' (259756 KB)... OKAY [ 8.238s]
writing 'system'... OKAY [ 2.132s]
finished. total time: 10.370s
C:\adb>fastboot flash system system.img_sparsechunk.1
sending 'system' (253441 KB)... OKAY [ 8.033s]
writing 'system'... OKAY [ 1.669s]
finished. total time: 9.703s
C:\adb>fastboot flash system system.img_sparsechunk.2
sending 'system' (254074 KB)... OKAY [ 8.048s]
writing 'system'... OKAY [ 1.679s]
finished. total time: 9.727s
C:\adb>fastboot flash system system.img_sparsechunk.3
sending 'system' (260545 KB)... OKAY [ 8.251s]
writing 'system'... OKAY [ 1.711s]
finished. total time: 9.962s
C:\adb>fastboot flash system system.img_sparsechunk.4
sending 'system' (259733 KB)... OKAY [ 8.221s]
writing 'system'... OKAY [ 1.696s]
finished. total time: 9.917s
C:\adb>fastboot flash modem NON-HLOS.bin
sending 'modem' (71577 KB)... OKAY [ 2.272s]
writing 'modem'... OKAY [ 0.547s]
finished. total time: 2.819s
C:\adb>fastboot erase modemst1
erasing 'modemst1'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot erase modemst2
erasing 'modemst2'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot flash fsg fsg.mbn
sending 'fsg' (6780 KB)... OKAY [ 0.212s]
writing 'fsg'... OKAY [ 0.078s]
finished. total time: 0.290s
C:\adb>fastboot erase cache
erasing 'cache'... OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot erase userdata
erasing 'userdata'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot erase customize
erasing 'customize'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot erase clogo
erasing 'clogo'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot oem fb_mode_clear
... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot reboot
DeineMudda111 said:
Hey guys. I really need the eu firmware (germany) for my G6!!! I bricked my G6 and cant boot up.
I wanted to flash the magisk patched boot img from the forum and have unfortunately overlooked that it was for the g6 plus -.- My bootloader is unlocked, but everytime when i turn on device, i have the message: Your device has been unlocked and cant be trusted. ID: bad key... and i cant boot up! I tried to flash the g6 firmware from the forum, but without solution... The Message freeze it and the phone cant boot.
i hope anyone has the eu firmware for me or any help! ^^
Heres my log:
C:\adb>fastboot oem fb_mode_set
... OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash partition gpt.bin
sending 'partition' (45 KB)... OKAY [ 0.000s]
writing 'partition'... INFOValidating 'gpt.default.xml'
INFOCommitting 'gpt.default.xml'
INFO- flashing 'gpt_main0.bin' to 'partition:0'
INFOFlashing primary GPT image...
INFOFlashing backup GPT image...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adb>fastboot flash bootloader bootloader.img
sending 'bootloader' (7419 KB)... OKAY [ 0.234s]
writing 'bootloader'... INFOValidating 'bootloader.default.xml'
INFOSecurity version downgrade
INFOImage aboot failed validation
INFOPreflash validation failed
INFOCancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.438s
C:\adb>fastboot flash logo logo.bin
sending 'logo' (2182 KB)... OKAY [ 0.062s]
writing 'logo'... OKAY [ 0.047s]
finished. total time: 0.109s
C:\adb>fastboot flash boot boot.img
sending 'boot' (22528 KB)... OKAY [ 0.719s]
writing 'boot'... INFOImage signed with key bad key
OKAY [ 0.266s]
finished. total time: 0.984s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (22628 KB)... OKAY [ 0.734s]
writing 'recovery'... INFOImage signed with key bad key
OKAY [ 0.359s]
finished. total time: 1.094s
C:\adb>fastboot flash dsp adspso.bin
sending 'dsp' (16384 KB)... OKAY [ 0.516s]
writing 'dsp'... OKAY [ 0.156s]
finished. total time: 0.672s
C:\adb>fastboot flash oem oem.img
sending 'oem' (206464 KB)... OKAY [ 6.550s]
writing 'oem'... OKAY [ 1.456s]
finished. total time: 8.006s
C:\adb>fastboot flash system system.img_sparsechunk.0
sending 'system' (259756 KB)... OKAY [ 8.238s]
writing 'system'... OKAY [ 2.132s]
finished. total time: 10.370s
C:\adb>fastboot flash system system.img_sparsechunk.1
sending 'system' (253441 KB)... OKAY [ 8.033s]
writing 'system'... OKAY [ 1.669s]
finished. total time: 9.703s
C:\adb>fastboot flash system system.img_sparsechunk.2
sending 'system' (254074 KB)... OKAY [ 8.048s]
writing 'system'... OKAY [ 1.679s]
finished. total time: 9.727s
C:\adb>fastboot flash system system.img_sparsechunk.3
sending 'system' (260545 KB)... OKAY [ 8.251s]
writing 'system'... OKAY [ 1.711s]
finished. total time: 9.962s
C:\adb>fastboot flash system system.img_sparsechunk.4
sending 'system' (259733 KB)... OKAY [ 8.221s]
writing 'system'... OKAY [ 1.696s]
finished. total time: 9.917s
C:\adb>fastboot flash modem NON-HLOS.bin
sending 'modem' (71577 KB)... OKAY [ 2.272s]
writing 'modem'... OKAY [ 0.547s]
finished. total time: 2.819s
C:\adb>fastboot erase modemst1
erasing 'modemst1'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot erase modemst2
erasing 'modemst2'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot flash fsg fsg.mbn
sending 'fsg' (6780 KB)... OKAY [ 0.212s]
writing 'fsg'... OKAY [ 0.078s]
finished. total time: 0.290s
C:\adb>fastboot erase cache
erasing 'cache'... OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot erase userdata
erasing 'userdata'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot erase customize
erasing 'customize'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot erase clogo
erasing 'clogo'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot oem fb_mode_clear
... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot reboot
Click to expand...
Click to collapse
Hi, I am sorry to hear that. What version of firmware you had installed and what version are trying to flash? it seems that you are flashing a firmware older than firmware installed
jekyll86 said:
Hi, I am sorry to hear that. What version of firmware you had installed and what version are trying to flash? it seems that you are flashing a firmware older than firmware installed
Click to expand...
Click to collapse
I flashed that one: https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292
I cant find another new firmware for my g6, there seems to be only this version. I dont know which Version i had before, but it must have been a EU version (i'm from germany) with april update... I'm very frustrated...
DeineMudda111 said:
I flashed that one: https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292
I cant find another new firmware for my g6, there seems to be only this version. I dont know which Version i had before, but it must have been a EU version (i'm from germany) with april update... I'm very frustrated...
Click to expand...
Click to collapse
That seems March firmware, you have to wait someone that upload April firmware.
Inviato dal mio moto g(6) plus utilizzando Tapatalk
jekyll86 said:
That seems March firmware, you have to wait someone that upload April firmware.
Inviato dal mio moto g(6) plus utilizzando Tapatalk
Click to expand...
Click to collapse
I will wait... Thank you
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