I am having trouble with this.
CMD - window only says waiting for device.
Device says FASTBOOT USB.
And I wrote fastboot oem lock.
Does anyone know what the **** is the problem ?
BOOTLOADER says ***TAMPERED*** ***UNLOCKED***
S-ON
HBOOT 1.54
I have managed before to relock it . Why not now ?
I have stock ROM installed now.
Is it missing drivers in the computer or ?
Did it say success after doing the command? If so, did you then reboot the bootloader to check if it's been done?
EddyOS said:
Did it say success after doing the command? If so, did you then reboot the bootloader to check if it's been done?
Click to expand...
Click to collapse
The Command window says : Waiting for device.
Drivers aren't installed, hence why it's not worked. What Windows version are you using?
Related
This is what my recovery screen says at the top:
*** UNLOCKED ***
Holiday PVT SHIP S-ON RL
HBOOT-1.85.0025
Click to expand...
Click to collapse
Currently im running Holics ROM 0.8.
I want to get back to stock rom without bricking my phone.
I need noob instructions, i dont know anything ...
Thanks,
Dom
No one can help me and teach me how to restore the Vivid?
You need to lock the bootloader and run the phones RUU.
Do you want the ICS or GB stock?
Sent from my HTC PH39100 using XDA
Chavisca1 said:
You need to lock the bootloader and run the phones RUU.
Do you want the ICS or GB stock?
Click to expand...
Click to collapse
Well I'd rather have ICS lol
But whichever works
Go here:
http://forum.xda-developers.com/showthread.php?t=1564776
This is the phones RUU.
Click the link in the post and it will download automatically.
Then once that's downloaded, Boot into H-Boot and go into fastboot usb.
(Assuming you have android-sdk installed)
Go to where you have the fastboot.exe installed. Should be with the adb and all in platform-tools.
And hold shift and right click and click open command window here.
The type "fastboot oem lock"
Run the RUU.exe you downloaded.
Chavisca1 said:
Go here:
http://forum.xda-developers.com/showthread.php?t=1564776
This is the phones RUU.
Click the link in the post and it will download automatically.
Then once that's downloaded, Boot into H-Boot and go into fastboot usb.
(Assuming you have android-sdk installed)
Go to where you have the fastboot.exe installed. Should be with the adb and all in platform-tools.
And hold shift and right click and click open command window here.
The type "fastboot oem lock"
Run the RUU.exe you downloaded.
Click to expand...
Click to collapse
Yeah i tried this method dozens of times, the command prompt just sits there and says "waiting for device"
or something similar
Do you have the drivers for the phone?
http://forum.xda-developers.com/showthread.php?t=1450105
The drivers for Windows 7 and XP Are in the download links of this forum.
Drivers as in the HTC Drivers installed on my PC?
Yeah
Can you type in "fastboot devices" when you're in fastboot and it give you the serial number for your phone? Or does it just show nothing?
shows nothing
You need drivers. Try re installing. I posted a link above.
Hi all, i need as soon as possible your help. I need to go back to stock ROM, since i have to send my phone in warranty beacouse the display is broken. I need to know every step i have to do. Your help will be really appreciate.
ParadiseCity said:
Hi all, i need as soon as possible your help. I need to go back to stock ROM, since i have to send my phone in warranty beacouse the display is broken. I need to know every step i have to do. Your help will be really appreciate.
Click to expand...
Click to collapse
Download correct ruu, in fastboot mode type fastboot oem lock in cmd and flash ruu when phone is fully rebooted.
For locking bootloader, step 6: http://forum.xda-developers.com/showthread.php?t=1578546
and for ruu chapter 4: http://forum.xda-developers.com/showthread.php?t=1693896
AlluXX said:
Download correct ruu, in fastboot mode type fastboot oem lock in cmd and flash ruu when phone is fully rebooted.
For locking bootloader, step 6: http://forum.xda-developers.com/showthread.php?t=1578546
and for ruu chapter 4: http://forum.xda-developers.com/showthread.php?t=1693896
Click to expand...
Click to collapse
6.open the terminal in your computer and type in 'adb devices', you probably will see an empty list, no devices. Just follow step 7
7. type in 'fastboot oem lock' without quotes and your device is locked again, you will see relocked - you might see a warning under it but that's nothing, after rebooting the warning will go away.
I haven't understand these lines. Can u explain me, what does mean "adb devices"?
Sv: [Q] Help for stock ROM
ParadiseCity said:
6.open the terminal in your computer and type in 'adb devices', you probably will see an empty list, no devices. Just follow step 7
7. type in 'fastboot oem lock' without quotes and your device is locked again, you will see relocked - you might see a warning under it but that's nothing, after rebooting the warning will go away.
I haven't understand these lines. Can u explain me, what does mean "adb devices"?
Click to expand...
Click to collapse
Most easy way to flash stock ROM is when device is unlocked , s-off it and run the ruu. If you relock the device you can't flash a GB ROM if you had used stock ICS.
Sent from my Sensation XL using xda app-developers app
anders3408 said:
Most easy way to flash stock ROM is when device is unlocked , s-off it and run the ruu. If you relock the device you can't flash a GB ROM if you had used stock ICS.
Sent from my Sensation XL using xda app-developers app
Click to expand...
Click to collapse
I have installed SDK Android tools, but when i write on CMD "fastboot oem lock" it says "this command is unknown". Why?
ParadiseCity said:
I have installed SDK Android tools, but when i write on CMD "fastboot oem lock" it says "this command is unknown". Why?
Click to expand...
Click to collapse
1- download rom ship
2- relock loader
+ into flash mode
+ Run command in "platform-tools" Folder: "fastboot oem lock"
+ run rom ship RUU - - -ok
R: [Q] Help for stock ROM
chikaro24 said:
1- download rom ship
2- relock loader
+ into flash mode
+ Run command in "platform-tools" Folder: "fastboot oem lock"
+ run rom ship RUU - - -ok
Click to expand...
Click to collapse
How can i flash ruu? Will i have access to recovery?
Inviato dal mio HTC Sensation XL with Beats Audio X315e con Tapatalk 2
Flashing an ruu is done via computer with a windows os
Hey,
I just S-OFF'ed my phone with Firewater (http://forum.xda-developers.com/showthread.php?t=2632351)
Anyyone got a link for me with how i can remove the red text?
I've HBOOT 1.54.0000
killerbie said:
Hey,
I just S-OFF'ed my phone with Firewater (http://forum.xda-developers.com/showthread.php?t=2632351)
Anyyone got a link for me with how i can remove the red text?
I've HBOOT 1.54.0000
Click to expand...
Click to collapse
flash custom firmware (without red text)
kamilmirza said:
flash custom firmware (without red text)
Click to expand...
Click to collapse
Where can I find that, please?
thx
ps: so I falsh custom firmware, then recovery again, than my rom again. Or am i wrong?
killerbie said:
Where can I find that, please?
thx
ps: so I falsh custom firmware, then recovery again, than my rom again. Or am i wrong?
Click to expand...
Click to collapse
please use search before posting
check THIS or THIS or THIS(dark bootloader)
no need to flash recovery or ROM after updating firmware
Got another problem.
When the phone is on, I can give commands via the command prompt (reboot etc works)
When in bootloader it always says 'waiting for device"
I've already relocked the bootloader to install the firmware
killerbie said:
Got another problem.
When the phone is on, I can give commands via the command prompt (reboot etc works)
When in bootloader it always says 'waiting for device"
I've already relocked the bootloader to install the firmware
Click to expand...
Click to collapse
uninstall HTC Sync with drivers, restart PC
download and install these DRIVERS
try again
kamilmirza said:
uninstall HTC Sync with drivers, restart PC
download and install these DRIVERS
try again
Click to expand...
Click to collapse
I get this in command prompt:
c:\adb>adb devices
List of devices attached
FA35MW903859 device
c:\adb>adb reboot bootloader
c:\adb>fastboot reboot-bootloader
< waiting for device >
-> after reboot I do get a windows message saying devices not recognised, wierd. when the phone is on i can get an adb connection, but not in bootloader
EDIT: when the phone is in bootloader I find an unknown usb device in device manager, i'm going to install those drivers manully there.
(this ones http://www.sendspace.com/file/j26i6g)
killerbie said:
I get this in command prompt:
c:\adb>adb devices
List of devices attached
FA35MW903859 device
c:\adb>adb reboot bootloader
c:\adb>fastboot reboot-bootloader
< waiting for device >
-> after reboot I do get a windows message saying devices not recognised, wierd. when the phone is on i can get an adb connection, but not in bootloader
EDIT: when the phone is in bootloader I find an unknown usb device in device manager, i'm going to install those drivers manully there.
(this ones http://www.sendspace.com/file/j26i6g)
Click to expand...
Click to collapse
boot into bootloader 1st
choose fastboot in the bootloader
then use all the fastboot comands in command prompt - it should work
eg. c:\adb\fastboot devices
BIGMOH said:
boot into bootloader 1st
choose fastboot in the bootloader
then use all the fastboot comands in command prompt - it should work
eg. c:\adb\fastboot devices
Click to expand...
Click to collapse
Still doesnt' work. My pc revognises the phone only when its IN android I think :/
Is it possible to flash the firmware.zip via adb sideload? or recovery? or just when android is on? in those cases adb works
killerbie said:
Still doesnt' work. My pc revognises the phone only when its IN android I think :/
Is it possible to flash the firmware.zip via adb sideload? or recovery? or just when android is on? in those cases adb works
Click to expand...
Click to collapse
By any chance are you using Windows 8.1?
killerbie said:
I get this in command prompt:
c:\adb>adb devices
List of devices attached
FA35MW903859 device
c:\adb>adb reboot bootloader
c:\adb>fastboot reboot-bootloader
< waiting for device >
-> after reboot I do get a windows message saying devices not recognised, wierd. when the phone is on i can get an adb connection, but not in bootloader
EDIT: when the phone is in bootloader I find an unknown usb device in device manager, i'm going to install those drivers manully there.
(this ones http://www.sendspace.com/file/j26i6g)
Click to expand...
Click to collapse
BIGMOH said:
By any chance are you using Windows 8.1?
Click to expand...
Click to collapse
seems like Windows 8.1
Sent from my One using Tapatalk
kamilmirza said:
seems like Windows 8.1
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Yep, Windows 8.1. I'm going to try get my hands on a windows 7 machine this evening
Hello,
this morning I was looking for a stock rom for my HTC one mini 2 and I used "fastboot oem lock" since then my phone is blocked in fastboot mode: i've access to hboot too, but can't access to Recovery mode. If I reboot the phone, it came back to fastboot mode.
On my screen I've the following:
*** TAMPERED ***
***RELOCKED***
*** Security Warning ***
I've tried to unlock the bootlader through HTCDev procedure, but when I've to flash the Unlock_code.bin the terminal send back: error: cannot load 'Unlock_code.bin'
Anyone have an idea about what I can do?
First: You do NOT need to relock bootloader to install stock ROM.
Relocking bootloader mey cause troubles like this.
Have you tried to overwrite recovery?
tarx1000 said:
First: You do NOT need to relock bootloader to install stock ROM.
Relocking bootloader mey cause troubles like this.
Have you tried to overwrite recovery?
Click to expand...
Click to collapse
Hello!
I've tired to flash a recovery. I've got the same response when I try to flash any kind of file:
error: cannot load 'memul-stock-recovery-2.16.401.1.img
deleric said:
Hello,
this morning I was looking for a stock rom for my HTC one mini 2 and I used "fastboot oem lock" since then my phone is blocked in fastboot mode: i've access to hboot too, but can't access to Recovery mode. If I reboot the phone, it came back to fastboot mode.
On my screen I've the following:
*** TAMPERED ***
***RELOCKED***
*** Security Warning ***
I've tried to unlock the bootlader through HTCDev procedure, but when I've to flash the Unlock_code.bin the terminal send back: error: cannot load 'Unlock_code.bin'
Anyone have an idea about what I can do?
Click to expand...
Click to collapse
Are you using an Original HTC cable???
kativiti said:
Are you using an Original HTC cable???
Click to expand...
Click to collapse
yep!
deleric said:
I've tried to unlock the bootlader through HTCDev procedure, but when I've to flash the Unlock_code.bin the terminal send back: error: cannot load 'Unlock_code.bin'
Click to expand...
Click to collapse
Is the unlock_code.bin file in the same directory as all the other unlock files?
press shift and right click top of folder and option to open cmd shows.
hello. it worked. thx
Hi Guys/Girls,
So today a friend gave me a HTC m7 to try and fix........From what i can gather something went wrong when they tried to encrypt the phone. Now when turn it on it asks for a password, when you get it wrong it wants to reset the phone, but this achieves nothing and you end up back at the encryption page. Neither Recovery Or Factory Reset work it comes up with: E:failed to mount /data. Also says some stuff before that about E:missing bitmap oem_unlock_bg, which im guessing is why i cant unlock the bootloader? i can get fastboot to work but as soon as i ask for the token it just sits and does nothing. adb does not seem to work.
As a side note i have 2 other htc m7's with broken screens, so if this is something that needs a hardware change that may be possible id assume?. I'm just unsure where to go from here, if i cant unlock the bootloader then what can you do???
I've rooted a few phones but your talking to abit of a beginner here guys.
Anyway TIA!
RUU (Rom update utility)
Sent from my SM-N930F using Tapatalk
clsA said:
RUU (Rom update utility)
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
Sorry if this seems nooby, but can you use a RUU with a locked boot loader and s-on? i cant even get the phone to respond to "fastboot oem get_identifier_token". I've been all over htc1guru but its abit beyond me, does fastboot flash work on a locked bootloader?
This seems to be a pretty bad catch 22, i cant fix the issue, because the issue stops me from doing anything. Any alternate ways around this guys???
Happyhog11 said:
Sorry if this seems nooby, but can you use a RUU with a locked boot loader and s-on? i cant even get the phone to respond to "fastboot oem get_identifier_token". I've been all over htc1guru but its abit beyond me, does fastboot flash work on a locked bootloader?
Click to expand...
Click to collapse
When S-ON, a ruu must be flashed with a locked bootloader, thats the only way Only S-OFF phones can flash a ruu with an unlocked bootloader.
Happyhog11 said:
This seems to be a pretty bad catch 22, i cant fix the issue, because the issue stops me from doing anything. Any alternate ways around this guys???
Click to expand...
Click to collapse
Can your phone at least reboot in RUU mode (Black screen with silver HTC logo)?
Code:
fastboot oem rebootRUU
Can you post the outputs of
Code:
fastboot oem last_dmesg
and
Code:
fastboot oem dmesg
alray said:
When S-ON, a ruu must be flashed with a locked bootloader, thats the only way Only S-OFF phones can flash a ruu with an unlocked bootloader.
Can your phone at least reboot in RUU mode (Black screen with silver HTC logo)?
Code:
fastboot oem rebootRUU
Can you post the outputs of
Code:
fastboot oem last_dmesg
and
Code:
fastboot oem dmesg
Click to expand...
Click to collapse
None of those commands work all i get is "< waiting for devices >". It is connecting to my pc i hear the noise of a device connecting plus "fastboot version" comes up with "htc_fastboot version 2.0.1", seems to be any oem commands wont work???
Also i was just playing around with the encryption page and can get access to the phones settings so i turned on usb debugging, some of the stuff in settings does not seem to work correctly and it crashes occasional but i thought this info might be useful....?
Happyhog11 said:
None of those commands work all i get is "< waiting for devices >"
Click to expand...
Click to collapse
Is your phone booted in bootloader mode with "fastboot usb" highlighted in red?
alray said:
Is your phone booted in bootloader mode with "fastboot usb" highlighted in red?
Click to expand...
Click to collapse
yep, some commands it just seems to hang on, comes up with ***Locked*** in purple, then a heap of info in green then below that FASTBOOT USB in red............