Database Develop

M7 Cant get into RUU mode

I have a verizon htc one m7 that will boot to the verizon logo then restart. i can access the bootload/fastboot and recovery. when i issue the fastboot command of fastboot oem rebootRUU the command completes and phone goes black then the green htc logo appears and continues to try and boot normally. does anybody have any suggestions on how to get to the RUU mode? bootloader is locked and s-on is active. this is a completly stock phone.

I think you need unlocked bootloader (but I'm not sure). So try unlocking it (keep in mind that you'll loose the guarantee)

suchauser said:
I think you need unlocked bootloader (but I'm not sure). So try unlocking it (keep in mind that you'll loose the guarantee)
Click to expand...
Click to collapse
1- no need for an unlocked bootloader
2- he's on Verizon so he can't use HTCdev to unlock, and sunshine won't work without a booted phone
idragoncell said:
I have a verizon htc one m7 that will boot to the verizon logo then restart. i can access the bootload/fastboot and recovery. when i issue the fastboot command of fastboot oem rebootRUU the command completes and phone goes black then the green htc logo appears and continues to try and boot normally. does anybody have any suggestions on how to get to the RUU mode? bootloader is locked and s-on is active. this is a completly stock phone.
Click to expand...
Click to collapse
how about some background info, how you ended in this situation... if it's a complete stock phone (so you weren't messing around with flashing things), then it could very well be a hardware problem... but the above info isnt enough, you need to provide more details of how this came to be
it's also good practice to copy/paste the entire command prompt output, so we can take a look of what was typed and what the output generated

Customer bought the phone too me in a boot loop state.. he claims he was using it and it just went black then came back on but never fully booted kept restarting at the verizon logo. htc told him to try and factory reset the phone but that was a no go as well. i have tried a RUU utility and when the program says rebooting to bootloader it doesnt go into bootloader just trys to boot up normally. the same thing happens when i attempt to put it in RUU mode it just reboots and trys to boot normally.

idragoncell said:
Customer bought the phone too me in a boot loop state.. he claims he was using it and it just went black then came back on but never fully booted kept restarting at the verizon logo. htc told him to try and factory reset the phone but that was a no go as well. i have tried a RUU utility and when the program says rebooting to bootloader it doesnt go into bootloader just trys to boot up normally. the same thing happens when i attempt to put it in RUU mode it just reboots and trys to boot normally.
Click to expand...
Click to collapse
sorry, dont get me wrong, but since i've been back (for a few hours), people are ... let's just say, not very forthcoming
what would help:
a screenshot of bootloader
a "fastboot getvar all" (excluding the last 6 digits of IMEI, MEID, and serial number... those need not be shared)
possibly a fastboot oem last_dmesg
though if the phone is completely stock, never been tampered with, then you have a high chance it's a hardware problem

http://imgur.com/73JGfka
https://goo.gl/photos/hkdxnmNtB7ctd2XA9
http://imgur.com/El0SNkj

idragoncell said:
http://imgur.com/73JGfka
https://goo.gl/photos/hkdxnmNtB7ctd2XA9
http://imgur.com/El0SNkj
Click to expand...
Click to collapse
thanks for the details, nothing "looks" wrong from those, but the "fastboot oem last_dmesg" has to be done after attempting to flash something, after a (non flashing reboot) it will just be empty.
couldn't find much, but have you tried this RUU:
http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
EDIT:
1- RUU.EXE will leave a log (before you close the .exe), in c:\ruu_log\.......txt
2- command prompt copy/paste is preferred to a screenshot, since it's much easier to read
good luck

HTC Desire 510 can't do anything with it. Stuck

So here's the story... this is an HTC Desire 510 purchased from Telus here in Canada. I've been messing around with different kernels, ROMs, etc. None of them really worked well for me, so I decided to go back to stock, unlock and try to sell it. Now I'm stuck at the bootloader and I can't figure out what to do. I tried to re-lock the bootloader so I could flash the stock ROM (those were the instructions I read)...
Whenever it boots, it gets to the recovery screen. ("Fastboot USB" / HBOOT) it says *Tampered* and *Relocked* at the top.
Then, when I try to unlock it with Unlock_code.bin (I have tried every method available), and say "Yes", I get the Fastboot USB screen with an overlay that says - at the top: Entering Recovery...
at the bottom it says: This build is for development purposes only, etc.
Then it just stays there until I remove the USB cable and the battery.
I reboot and I get the same thing every time.
Is there any way to fix this? I've tried many an adb command with no avail. I'm ready to throw this thing into the river.

cjmitchell said:
So here's the story... this is an HTC Desire 510 purchased from Telus here in Canada. I've been messing around with different kernels, ROMs, etc. None of them really worked well for me, so I decided to go back to stock, unlock and try to sell it. Now I'm stuck at the bootloader and I can't figure out what to do. I tried to re-lock the bootloader so I could flash the stock ROM (those were the instructions I read)...
Whenever it boots, it gets to the recovery screen. ("Fastboot USB" / HBOOT) it says *Tampered* and *Relocked* at the top.
Then, when I try to unlock it with Unlock_code.bin (I have tried every method available), and say "Yes", I get the Fastboot USB screen with an overlay that says - at the top: Entering Recovery...
at the bottom it says: This build is for development purposes only, etc.
Then it just stays there until I remove the USB cable and the battery.
I reboot and I get the same thing every time.
Is there any way to fix this? I've tried many an adb command with no avail. I'm ready to throw this thing into the river.
Click to expand...
Click to collapse
Is it 64 bit or 32 bit? And what type of recovery did you have on it before?

MrMike2182 said:
Is it 64 bit or 32 bit? And what type of recovery did you have on it before?
Click to expand...
Click to collapse
It's 32 bit and it had TWRP.

cjmitchell said:
It's 32 bit and it had TWRP.
Click to expand...
Click to collapse
What you need to do first of all is find an RUU for your device and then find the original recovery, not the twrp recovery but the actual recovery that was on the phone when you first got it. If you don't flash the original recovery then the RUU will refuse to continue and that's basically HTC's way of trying to prevent us from breaking the phone.. The unlock code you got from HTC you should have kept and whenever you sell the phone pass it along to the new owner.. So to help you understand everything I said first unlock your bootloader again and then flash the original recovery and then lock the bootloader again then run the RUU on the PC.. Some times you have to run the RUU a few times to finally get it to finish completely cause some times it'll hang and just sit there so just end the process and restart it but before ending it be sure you gave it enough time to try before thinking it's stuck because it may not be... After the RUU finishes, the phone will totally be stock again the same way it was the day you bought it..

MrMike2182 said:
What you need to do first of all is find an RUU for your device and then find the original recovery, not the twrp recovery but the actual recovery that was on the phone when you first got it. If you don't flash the original recovery then the RUU will refuse to continue and that's basically HTC's way of trying to prevent us from breaking the phone.. The unlock code you got from HTC you should have kept and whenever you sell the phone pass it along to the new owner.. So to help you understand everything I said first unlock your bootloader again and then flash the original recovery and then lock the bootloader again then run the RUU on the PC.. Some times you have to run the RUU a few times to finally get it to finish completely cause some times it'll hang and just sit there so just end the process and restart it but before ending it be sure you gave it enough time to try before thinking it's stuck because it may not be... After the RUU finishes, the phone will totally be stock again the same way it was the day you bought it..
Click to expand...
Click to collapse
HTC or Telus don't provide a RUU for the Telus version of the phone so I've been trying the Cricket version, doesn't work. It gives me the message: ERROR [131]: CUSTOMER ID ERROR.
There is some russian website that seems to have it for Telus, but you have to pay to access it, and I don't even know if it's what I need. ir-file.com (I can't post links)
So I'm not going down that rabbit hole.
I can't flash any recovery I find...
"fastboot getvar platform" gives me hTCBmsm2886
"fastboot flash recovery (*.img)" gives me a message saying FAILED (remote: signature verify fail) for every single recovery image I can find. Nothing works.

cjmitchell said:
HTC or Telus don't provide a RUU for the Telus version of the phone so I've been trying the Cricket version, doesn't work. It gives me the message: ERROR [131]: CUSTOMER ID ERROR.
There is some russian website that seems to have it for Telus, but you have to pay to access it, and I don't even know if it's what I need. ir-file.com (I can't post links)
So I'm not going down that rabbit hole.
I can't flash any recovery I find...
"fastboot getvar platform" gives me hTCBmsm2886
"fastboot flash recovery (*.img)" gives me a message saying FAILED (remote: signature verify fail) for every single recovery image I can find. Nothing works.
Click to expand...
Click to collapse
Did you try to reflash twrp? If I was in your predicament I'd flash twrp and then there is a rom that I configured to work great on the 32 bit phones it's the Modded CM11 and I'm pretty sure it'll work on yours albeit the cameras aren't working yet at least it's a start and you can find the CM11 I configured here ----> Modded CM11

MrMike2182 said:
Did you try to reflash twrp? If I was in your predicament I'd flash twrp and then there is a rom that I configured to work great on the 32 bit phones it's the Modded CM11 and I'm pretty sure it'll work on yours albeit the cameras aren't working yet at least it's a start and you can find the CM11 I configured here ----> Modded CM11
Click to expand...
Click to collapse
Yeah, I tried to reflash TWRP, I get that message "FAILED: (remote: signature verify fail)"
That is after I type in the C:\adb\ folder "fastboot flash recovery twrp-2.8.7.0-a11.img"
and every other recovery image I can find, including older versions of TWRP.
This is why I'm frustrated, nothing works. If I could flash a ROM that'd be cool, but I can't get out of the bootloader, I can't even get into recovery.

cjmitchell said:
Yeah, I tried to reflash TWRP, I get that message "FAILED: (remote: signature verify fail)"
That is after I type in the C:\adb\ folder "fastboot flash recovery twrp-2.8.7.0-a11.img"
and every other recovery image I can find, including older versions of TWRP.
This is why I'm frustrated, nothing works. If I could flash a ROM that'd be cool, but I can't get out of the bootloader, I can't even get into recovery.
Click to expand...
Click to collapse
I need you to type everything you see on your HBoot screen when you pull the battery and put it back in and then hold the volume down button and then press the power button at the same time and when the screen comes up type everything you see in here so I can see it... I think the reason you're getting the remote signature failure is because the bootloader is still locked and you have to make sure it really is unlocked.. Try that then get back to me.

Yeah, the bootloader is still locked. here's what it says:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 19 2015,21:13:29.0
Then the regular menu.
I can't seem to unlock the bootloader.

cjmitchell said:
Yeah, the bootloader is still locked. here's what it says:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 19 2015,21:13:29.0
Then the regular menu.
I can't seem to unlock the bootloader.
Click to expand...
Click to collapse
Well if you had the boot unlocked before, why can't you send the unlock_code.bin to it and have it unlock again? Or did you lose the key? Because you're supposed to keep that key.. Did you use some sort of program to try and root the phone? Like them 1 click root apps...
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Go download this to a computer/laptop whatever and connect the phone to it and try to run this RUU on the PC while the phone is connected to it and turned on in HBoot/fastboot... Do this before trying to unlock the boot again and if it hangs try it again because some times it can take 3 or 4 tries to get it to work... Download Cricket RUU - http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Edit: I know you said your carrier is Telus and I know that's a Cricket RUU that I listed, but they are both the same so run it!!
Edit again: Never mind don't bother running the RUU because you're not s-off and you can't change your CID so I suggest you find a way to unlock your bootloader again somehow and then flash the CM11 to test out.

MrMike2182 said:
Well if you had the boot unlocked before, why can't you send the unlock_code.bin to it and have it unlock again? Or did you lose the key? Because you're supposed to keep that key.. Did you use some sort of program to try and root the phone? Like them 1 click root apps...
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Go download this to a computer/laptop whatever and connect the phone to it and try to run this RUU on the PC while the phone is connected to it and turned on in HBoot/fastboot... Do this before trying to unlock the boot again and if it hangs try it again because some times it can take 3 or 4 tries to get it to work... Download Cricket RUU - http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Edit: I know you said your carrier is Telus and I know that's a Cricket RUU that I listed, but they are both the same so run it!!
Edit again: Never mind don't bother running the RUU because you're not s-off and you can't change your CID so I suggest you find a way to unlock your bootloader again somehow and then flash the CM11 to test out.
Click to expand...
Click to collapse
I have the unlock_code.bin, I've been trying to send it to the phone but it doesn't work. I've tried the WinDroid app and the command line "fastboot flash unlocktoken unlock_code.bin" and I get to the screen that asks if I want to unlock the bootloader, but when I select "Yes" it hangs and sticks on that screen, but at the top it says: "Entering Recovery..." and at the bottom it says "This build is for development purposes only", etc.
If I can't flash anything then I'm guessing it's perma-bricked... :/

cjmitchell said:
I have the unlock_code.bin, I've been trying to send it to the phone but it doesn't work. I've tried the WinDroid app and the command line "fastboot flash unlocktoken unlock_code.bin" and I get to the screen that asks if I want to unlock the bootloader, but when I select "Yes" it hangs and sticks on that screen, but at the top it says: "Entering Recovery..." and at the bottom it says "This build is for development purposes only", etc.
If I can't flash anything then I'm guessing it's perma-bricked... :/
Click to expand...
Click to collapse
Right it hung there because there was no recovery flashed so right after you unlock that no matter what just flash twrp to it the second after you tap yes to unlock the bootloader send the recovery to it.

MrMike2182 said:
Right it hung there because there was no recovery flashed so right after you unlock that no matter what just flash twrp to it the second after you tap yes to unlock the bootloader send the recovery to it.
Click to expand...
Click to collapse
as soon as I hit the "Yes" option on the "Unlock bootloader?" screen, it tries to go into recovery. And it's instant. There is no window where I can flash the recovery - I've tried it multiple times.
So I can't unlock it and I can't flash a recovery.
I'm afraid this thing is done for...

cjmitchell said:
as soon as I hit the "Yes" option on the "Unlock bootloader?" screen, it tries to go into recovery. And it's instant. There is no window where I can flash the recovery - I've tried it multiple times.
So I can't unlock it and I can't flash a recovery.
I'm afraid this thing is done for...
Click to expand...
Click to collapse
You are supposed to be unlocking it from a PC and flashing the recovery from the PC also not trying to flash the recovery from the phone you cant do that unless the phones working.. Don't you have minimal ADB and Fastboot installed on a Windows PC?

Bad Encryption Gone Wrong

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............

Can't access full fastboot commands

Hi all, I was wondering if you know, after bootloader unlocking, why I can't access full fastboot commands as the one to remotely boot a recovery. "fastboot boot recovery.img" says "Failed: Command not allowed" and also does "fastboot oem ?" to list oem commands. OEM unlocking is permanently On , on the Dev Options and as I said before, bootloader is unlocked. But, I still can, I guess, flash boot, recovery etc. but I don't want to do it right now. I can tell it because so happened on my previous Huawei Phone and what's happening now on my P10 is the same thing. Thanks in advance.

Up, my ROM is VTR-L09C55B130 stock and I'm on Android 7.0

phone corrupt and cant be trusted

i tried rooting my device but something went wrong after flashing the boot.img
now the device is stuck and i can only access fastboot.
i tried accessing the recovery but i get the same error msg.
i tried flashing every recovery img that exist for the red magic 3 but with no success

Flashing Unlock
Hey, make sure that you have first unlocked the bootloader with the fastboot command: "fastboot flashing unlock". Try it. It will erase all your data and do a reset factory and then you should be able to reboot your device normally. Also, it will let you flash the boot.img for root your device.

Perseo99 said:
Hey, make sure that you have first unlocked the bootloader with the fastboot command: "fastboot flashing unlock". Try it. It will erase all your data and do a reset factory and then you should be able to reboot your device normally. Also, it will let you flash the boot.img for root your device.
Click to expand...
Click to collapse
when i type "fastboot flashing unlock" in cmd it shows nothing .. just showing what commands i can do with fastboot

mashkalny said:
when i type "fastboot flashing unlock" in cmd it shows nothing .. just showing what commands i can do with fastboot
Click to expand...
Click to collapse
Did you let unlock bootloader and permitted the USB debbugin on the developers option before flash the boot.img?
Make sure you are using a USB 2.0 to connect your device to the PC. See if you PC recognizes the device into the fastboot menu with "fastboot devices", if doesn't, try reboot another phone with "adb rebbot bootloader", then enter "fastboot devices", your device should be listed into de the devices attached. Then try again entering "fastboot flashing unlock".

Perseo99 said:
Did you let unlock bootloader and permitted the USB debbugin on the developers option before flash the boot.img?
Make sure you are using a USB 2.0 to connect your device to the PC. See if you PC recognizes the device into the fastboot menu with "fastboot devices", if doesn't, try reboot another phone with "adb rebbot bootloader", then enter "fastboot devices", your device should be listed into de the devices attached. Then try again entering "fastboot flashing unlock".
Click to expand...
Click to collapse
i believe i forgot to unlock the bootloader when i tried to root. now i cant access anything in the fastboot mode.

mashkalny said:
i believe i forgot to unlock the bootloader when i tried to root. now i cant access anything in the fastboot mode.
Click to expand...
Click to collapse
Oh, that could be a problem. Try to use this tool. I hope you can get your phone working again. If this doesn't works, try to flash the original boot.img of your firmware version.
https://forum.xda-developers.com/re.../tool-nubia-red-magic-3-unbirck-tool-t3965044