Database Develop

[ON HOLD] Stuck in boot screen (not bootloader, rooted)

Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!

Enion said:
Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!
Click to expand...
Click to collapse
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.

kibmikey1 said:
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...

Enion said:
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...
Click to expand...
Click to collapse
Blinking is good, just hold POWER + VOLDOWN with the phone sensors under a bright light (not kidding!!), it should reboot after 30sec to 2 minute. If it doesn't reboot, let go and try again; the bright light is important!!
Once it reboots, keep holding VOLDOWN so it reboots to bootloader.

Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to
flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back

Enion said:
Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back
Click to expand...
Click to collapse
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped

nkk71 said:
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped
Click to expand...
Click to collapse
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
thanks!

Enion said:
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
thanks!
Click to expand...
Click to collapse
hey mate, edit your post and remove IMEI and s/n we don't need to see those.
can you confirm your hboot is dated before June 2013. I'll post your options after that

Hi, thanks for noticing, I removed it, please dit your post aswell
If you're talking about the date at the top of the bootloader, it says May 3

Enion said:
Hi, thanks for noticing, I removed it, please dit your post aswell
Click to expand...
Click to collapse
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
Enion said:
If you're talking about the date at the top of the bootloader, it says May 3
Click to expand...
Click to collapse
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day

nkk71 said:
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day
Click to expand...
Click to collapse
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.

Enion said:
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.
Click to expand...
Click to collapse
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )

nkk71 said:
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )
Click to expand...
Click to collapse
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward

Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
No problem mate, remember for revone to work your firmware is good ((bootloader) version-main: 1.29.161.16), but you will need a ROM based on 4.1.2 preferably (I have one - which worked for me and two others) in case you can't find one.
Also read here: http://forum.xda-developers.com/showthread.php?t=2431515
here: http://forum.xda-developers.com/showthread.php?t=2365506
and of course: http://forum.xda-developers.com/showthread.php?t=2314582
Let me know if you need any more help.
Once you are S-Off, you can easily upgrade/downgrade firmware in @vomer's guide (same as before, but down in the firmware section): http://forum.xda-developers.com/showthread.php?t=2365506

Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
Hey @Enion, you all good now?

nkk71 said:
Hey @Enion, you all good now?
Click to expand...
Click to collapse
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion

Enion said:
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion
Click to expand...
Click to collapse
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread

nkk71 said:
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread
Click to expand...
Click to collapse
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.

Enion said:
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.
Click to expand...
Click to collapse
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
nkk71 said:
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
Click to expand...
Click to collapse
Thank you sir!

i need help i think my device is bricked

okk so i was trying to flash a rom for the first time and i really went at it the wrong way. i didin't backup my original RUU and now my device is stuck on the bootloader screen and i really have no idea what to do. i just want to get an OS running on my phone right now cause im freaking out. my company carrier is rogers and this is what my phone is showing right now:
***tampered***
***relocked***
m7_ul pvt ship s-on rh
hboot-1,55,0000
radio-4a.20.3263.16
opendsp -v32,120.274.0909
os-
emmc-boot 2048mb
i try looking for another ruu to flash in my phone but i cant seem to find one that works with my phone..even when i try using the flashboot getvar command to check for the version this is all i got.. : C:\Users\david\Desktop\sdk-tools>fastboot getvar version-main
version-main:
finished. total time: 0.001s
any help at this point would be greatly appreciated i need to get my phone up working so i can receive my calls
i have managed to bring back recovery mode by re-unlocking it via htcdev..now when the phone boots it goes to the google logo and then the language selecting screen then restarts after 10 secs everytime

Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.

fenstre said:
Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.
Click to expand...
Click to collapse
this is what i got from the fastboot getvar all command :
C:\Users\david\Desktop\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA346W904162
(bootloader) imei: 354439050131335
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
cidnum says ROGER001? im i don't think ive seen cid what that number around
edit: could it be possible that this is what i need ? "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17"
since i did not make a backup is there a chance i can restore this ? ive tried the method that suggest sideloading but it didn't work or maybe i didin't do it right but it didn't wanna recognize my phone when i tried the command'
edit 2: also, im using twrp instead of cwm if that information can help in any way.

If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.

gffmac said:
If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.
Click to expand...
Click to collapse
well all i was trying to do was install the goole play edition rom (bigxie_m7_GPe_KRT16S_odexed-signed.zip) but after the installation it kept restarting after the language selection screen. i used twrp to flash the rom. right now all im able to do is cycle through the booloader, the recovery screen and to the language selection screen

Unless you have another rom (4.3 rom) copied onto the storage on your phone you will probably have to flash stock recovery and recover by installing a stock RUU for your carrier/CID version.
---------- Post added at 11:59 AM ---------- Previous post was at 11:54 AM ----------
Out of curiosity try going into twrp and doing a factory reset (wipe) and reboot see if you have the same issue.

is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?

deerome said:
is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?
Click to expand...
Click to collapse
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.

gffmac said:
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.
Click to expand...
Click to collapse
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.

deerome said:
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.
Click to expand...
Click to collapse
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.

gffmac said:
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.
Click to expand...
Click to collapse
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until im better at this thing.
anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:

deerome said:
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until Im better at this thing.
Anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:
Click to expand...
Click to collapse
No probs glad you got it working again.
If you really want to try a Google Edition rom you would need to s-off your phone which is trickier than what you have done so far so may want to read up some more.

I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk

deerxmoose said:
I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??

gffmac said:
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??
Click to expand...
Click to collapse
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk

deerxmoose said:
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.

gffmac said:
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.
Click to expand...
Click to collapse
Before trying that ill prefer to try Any other solutions. Anyone?
Sent from my Desire HD using Tapatalk

There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery

SaHiLzZ said:
There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery
Click to expand...
Click to collapse
Tried that over and over and it keeps saying device not found.
Sent from my Desire HD using Tapatalk

Then you should fix your computer/adb issues.

[Q] flash RUU...but no device.

Hi all,
Changed from Samsung S2 to HTC one and installed custom ROM. My kid pulled the USB cable in the middle of something and after that I was stuck in boot. Trying to flash an RUU I re-locked the phone and now I am stuck there. I really tried to find the answer in other threads and it feels I am close (to knowing either how to solve this or get to know it is impossible), but I am not quite there:
Situation:
Tampered-relocked-security warning (comes and goes strangely enough)
S-On
HBOOT 1.44
eMMC-boot
May 3, 2013
Fastboot USB
Problem: whatever I try to do, my PC says there is no device. I installed HTC sync manager but it can not find my phone. It was in USB debugging before the loop....and now I do not know what to do.
Any suggestions for not making 2014 my worst phone-starting year ever....?

cdresor said:
Hi all,
Changed from Samsung S2 to HTC one and installed custom ROM. My kid pulled the USB cable in the middle of something and after that I was stuck in boot. Trying to flash an RUU I re-locked the phone and now I am stuck there. I really tried to find the answer in other threads and it feels I am close (to knowing either how to solve this or get to know it is impossible), but I am not quite there:
Situation:
Tampered-relocked-security warning (comes and goes strangely enough)
S-On
HBOOT 1.44
eMMC-boot
May 3, 2013
Fastboot USB
Problem: whatever I try to do, my PC says there is no device. I installed HTC sync manager but it can not find my phone. It was in USB debugging before the loop....and now I do not know what to do.
Any suggestions for not making 2014 my worst phone-starting year ever....?
Click to expand...
Click to collapse
can you post results from
fastboot getvar all
minus your iemi and serial no
you run it from the bootloader screen you posted above

getvar
clsA said:
can you post results from
fastboot getvar all
minus your iemi and serial no
you run it from the bootloader screen you posted above
Click to expand...
Click to collapse
Thanks. First I got "no device", but I drained the battery (because nothing happened when plugging/unplugging the USB cable), reinstalled drivers on my PC and reconnected the HTC. I got security warning again but I guess it sees my phone, because getvar worked:
bootloader version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-clpd: None
version-microp: None
version-main: 1.29.401.16
version-misc: PUT SHIP S-ON
serialno:
imei:
meid: 000000000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC_Y13
battery-status: low
battery-voltage: 3286 mV
partition-layout: Generic
security: on
build-mode: ship
boot-mode: fastboot
getvar: all FAILED (status read failed (too many links))
finished. Total time 5.188s

Similar position, help me too please
my device HTC 802d china telecom, am based in china, running 4.2.2 upgrade 4.3 available
my phone says
TAMPERED
RELOCKED
SECURITY WARNING - this comes and goes
Phone working well, htc sync manager work well
when i go to bootloader then fastboot, it says fastboot usb but fastboot or adb says no device
pc not detect my phone from bootloader, kindly help

sureshnv said:
my device HTC 802d china telecom, am based in china, running 4.2.2 upgrade 4.3 available
my phone says
TAMPERED
RELOCKED
SECURITY WARNING - this comes and goes
Phone working well, htc sync manager work well
when i go to bootloader then fastboot, it says fastboot usb but fastboot or adb says no device
pc not detect my phone from bootloader, kindly help
Click to expand...
Click to collapse
I will get back to you if I find out what was wrong. Right now though I dare not to touch my phone until I see which help I can get from this forum. My HTC Sync manager says I have no device, most commands say no device but still I got getvar info. So I do not quite understand all of this....but hopefully I will get there. Good luck!

cdresor said:
I will get back to you if I find out what was wrong. Right now though I dare not to touch my phone until I see which help I can get from this forum. My HTC Sync manager says I have no device, most commands say no device but still I got getvar info. So I do not quite understand all of this....but hopefully I will get there. Good luck!
Click to expand...
Click to collapse
yeah we can get you their - Uninstall HTC Sync manager but leave the drivers (it will ask during uninstall)
the date in the bootloader indicates Revone should work to s-off your phone as I can see your on hboot 1.44
Try to get s-off >> http://forum.xda-developers.com/showthread.php?t=2314582
while your reading Download this
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
next step is this from @nkk71
Step 2: Flash your RUU.zip
Download your MID & CID compatible RUU.zip
Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
Click to expand...
Click to collapse

if you're having problems with revone, use the following rom: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250

clsA said:
yeah we can get you their - Uninstall HTC Sync manager but leave the drivers (it will ask during uninstall)
the date in the bootloader indicates Revone should work to s-off your phone as I can see your on hboot 1.44
Try to get s-off >> http://forum.xda-developers.com/showthread.php?t=2314582
while your reading Download this
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
next step is this from @nkk71
Click to expand...
Click to collapse
Again, thanks for replying.
I uninstalled HTC Sync manager but it never asked about the drivers (I only got install/repair/uninstall) so everything was deleted. I reinstalled.
Nevertheless, trying to push revone I simply got the message "error:device not found". I guess /data/local/tmp/ is the correct dir for my device, or can this be different on different machines somehow?
I am still downloading the ROM, hoping for help.....d/l takes a looong time so don´t hurry

cdresor said:
Again, thanks for replying.
I uninstalled HTC Sync manager but it never asked about the drivers (I only got install/repair/uninstall) so everything was deleted. I reinstalled.
Nevertheless, trying to push s-off I simply got the message "error:device not found". I guess /data/local/tmp/ is the correct dir for my device, or can this be different on different machines somehow?
I am still downloading the ROM, hoping for help.....d/l takes a looong time so don´t hurry
Click to expand...
Click to collapse
you need to be booted into custom recovery when you push with adb

cdresor said:
Again, thanks for replying.
I uninstalled HTC Sync manager but it never asked about the drivers (I only got install/repair/uninstall) so everything was deleted. I reinstalled.
Nevertheless, trying to push revone I simply got the message "error:device not found". I guess /data/local/tmp/ is the correct dir for my device, or can this be different on different machines somehow?
I am still downloading the ROM, hoping for help.....d/l takes a looong time so don´t hurry
Click to expand...
Click to collapse
strange, i always install sync manager, then go back to Control Panel -> Uninstall -> HTC Sync Manager
HTC Drivers stay just fine.
You can use those:
HTCDriver_4.8.0.002.exe 15.1 MB
https://mega.co.nz/#!TAcGAJ7L!YdWM4AIji95b1ow8kVgagggOx5Yh7csRN5G0KJaCo6w
you have to get adb working; you can check by typing "adb devices" either in custom recovery or booted-up ROM (USB debugging enabled), it should show your device serial number.

nkk71 said:
if you're having problems with revone, use the following rom: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250
Click to expand...
Click to collapse
Sorry for being stupid but will the ROM make my HTC S-Off (as the heading implies) or work with the current S-ON?
I still don´t understand how I am to flash it to my device when everything I do (except getvar) says "device not found". But I will try and might get out of this mess a little bit smarter than I was before.
Thanks!

cdresor said:
Sorry for being stupid but will the ROM make my HTC S-Off (as the heading implies) or work with the current S-ON?
I still don´t understand how I am to flash it to my device when everything I do (except getvar) says "device not found". But I will try and might get out of this mess a little bit smarter than I was before.
Thanks!
Click to expand...
Click to collapse
I would flash the RUU and skip s-off for now till you get your phone working again. From what your saying you don't even have custom recovery any more ?

cdresor said:
Sorry for being stupid but will the ROM make my HTC S-Off (as the heading implies) or work with the current S-ON?
I still don´t understand how I am to flash it to my device when everything I do (except getvar) says "device not found". But I will try and might get out of this mess a little bit smarter than I was before.
Thanks!
Click to expand...
Click to collapse
1- No, the ROM will not make you S-Off, but it's proven to be very compatible with revone
2- you install that using custom recovery (CWM or TWRP)
3- you'll still have to use the revone commands as mentioned in their thread
4- adb vs fastboot:
"fastboot devices" <- works in bootloader screen ONLY (the white screen)
"adb devices" <- works in a booted up ROM (with USB debugging enabled) or in custom recovery (CWM or TWRP), it does NOT work in bootloader
---------- Post added at 04:42 PM ---------- Previous post was at 04:36 PM ----------
cdresor said:
Sorry for being stupid but will the ROM make my HTC S-Off (as the heading implies) or work with the current S-ON?
I still don´t understand how I am to flash it to my device when everything I do (except getvar) says "device not found". But I will try and might get out of this mess a little bit smarter than I was before.
Thanks!
Click to expand...
Click to collapse
clsA said:
I would flash the RUU and skip s-off for now till you get your phone working again. From what your saying you don't even have custom recovery any more ?
Click to expand...
Click to collapse
+1, disregard my previous post, and go with @clsA recommendation of flashing ruu, to get your phone back up and running.

clsA said:
I would flash the RUU and skip s-off for now till you get your phone working again. From what your saying you don't even have custom recovery any more ?
Click to expand...
Click to collapse
Unfortunately you are quite right. I guess there is something fishy with my drivers although getvar gets info from my phone. And although Windows does not show any phone, in device manager there is a "My HTC" which is said to run correctly. Sigh.
I will try to get in contact with my phone and flash a ROM.

cdresor said:
Unfortunately you are quite right. I guess there is something fishy with my drivers although getvar gets info from my phone. And although Windows does not show any phone, in device manager there is a "My HTC" which is said to run correctly. Sigh.
I will try to get in contact with my phone and flash a ROM.
Click to expand...
Click to collapse
just do the stuff in post 6 and skip s-off for now

clsA said:
just do the stuff in post 6 and skip s-off for now
Click to expand...
Click to collapse
Getting there, getting there.....
First I just got "error opening". Changed the long name to "1.zip" and it seemed to work. Finished with these lines though:
writing "zip".....
(bootloader) signature checking....
FAILED (remote: 12 signature verify fail)
And back to where I was before. Should I just retry (download again) or do you have any further advice?

cdresor said:
Getting there, getting there.....
First I just got "error opening". Changed the long name to "1.zip" and it seemed to work. Finished with these lines though:
writing "zip".....
(bootloader) signature checking....
FAILED (remote: 12 signature verify fail)
And back to where I was before. Should I just retry (download again) or do you have any further advice?
Click to expand...
Click to collapse
did you md5 check the file you already have ?

clsA said:
did you md5 check the file you already have ?
Click to expand...
Click to collapse
Hrm...I never understood how I check md5 on my computer so I figured it was faster to d/l it again. I am happy something happens between my computer and the phone though.....I see the light in the tunnel. Hopefully not the headlight on a freight train.

cdresor said:
Thanks. First I got "no device", but I drained the battery (because nothing happened when plugging/unplugging the USB cable), reinstalled drivers on my PC and reconnected the HTC. I got security warning again but I guess it sees my phone, because getvar worked:
bootloader version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-clpd: None
version-microp: None
version-main: 1.29.401.16
version-misc: PUT SHIP S-ON
serialno:
imei:
meid: 000000000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC_Y13
battery-status: low
battery-voltage: 3286 mV
partition-layout: Generic
security: on
build-mode: ship
boot-mode: fastboot
getvar: all FAILED (status read failed (too many links))
finished. Total time 5.188s
Click to expand...
Click to collapse
cdresor said:
Hrm...I never understood how I check md5 on my computer so I figured it was faster to d/l it again. I am happy something happens between my computer and the phone though.....I see the light in the tunnel. Hopefully not the headlight on a freight train.
Click to expand...
Click to collapse
1- I'm assuming you TYPED that getvar ^^ above correct!?!?! (because of the "mistyped" stuff in it)... please confirm!!!! EDIT:: even better, do a "fastboot getvar all" again, and copy/paste output, not typed
2- can you open the ruu.zip and post the contents "android-info.txt" (I could download it and check myself, but that would just take another 1 and half hours)

cdresor said:
Hrm...I never understood how I check md5 on my computer so I figured it was faster to d/l it again. I am happy something happens between my computer and the phone though.....I see the light in the tunnel. Hopefully not the headlight on a freight train.
Click to expand...
Click to collapse
md5 app
all you do is copy the long code of the md5 and the app will take it from the clipboard .. simply browse to the file your checking and it will go

Having an issue with S-Off. Help please?

I did a stupid thing: I unlocked my AT&T m7 (which I thought also made it S-OFF). I then installed a recovery and wiped the phone. After CM11 wouldn't install I realized that the phone was still S-ON. I have no OS on it to boot into. Any ideas on how I can get an HTC ROM on there so I can run the revone and grant it S-OFF? Thanks in advance!
Adam

niphoet said:
I did a stupid thing: I unlocked my AT&T m7 (which I thought also made it S-OFF). I then installed a recovery and wiped the phone. After CM11 wouldn't install I realized that the phone was still S-ON. I have no OS on it to boot into. Any ideas on how I can get an HTC ROM on there so I can run the revone and grant it S-OFF? Thanks in advance!
Adam
Click to expand...
Click to collapse
Well if you have a custom recovery, just flash any rom. Or did I misunderstand something?

aooga said:
Well if you have a custom recovery, just flash any rom. Or did I misunderstand something?
Click to expand...
Click to collapse
I can't transfer a ROM (CM11, Viper, etc) to the device. I can't get ADB sideload to work. I've installed the universal adb drivers and no dice.

niphoet said:
I can't transfer a ROM (CM11, Viper, etc) to the device. I can't get ADB sideload to work. I've installed the universal adb drivers and no dice.
Click to expand...
Click to collapse
Ah okay. When you connect your phone to your computer in recovery, what does "adb devices" give you? Nothing?

aooga said:
Ah okay. When you connect your phone to your computer in recovery, what does "adb devices" give you? Nothing?
Click to expand...
Click to collapse
Correct, I get nothing.

niphoet said:
Correct, I get nothing.
Click to expand...
Click to collapse
If even after re-flashing the TWRP.img it doesn't work, I would just do an RUU and go from there. Bad thing about not having an SD card slot

aooga said:
If even after re-flashing the TWRP.img it doesn't work, I would just do an RUU and go from there. Bad thing about not having an SD card slot
Click to expand...
Click to collapse
I've tried RUU but it keeps failing. Can you recommend a specific RUU to try?

niphoet said:
I've tried RUU but it keeps failing. Can you recommend a specific RUU to try?
Click to expand...
Click to collapse
Do you have Super cid or still the att one?

aooga said:
Do you have Super cid or still the att one?
Click to expand...
Click to collapse
I've tried:
RUU_M7_UL_JB_50_Cingular.exe
---and---
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe

niphoet said:
I've tried:
RUU_M7_UL_JB_50_Cingular.exe
---and---
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
This one seems to work for everyone I give it to.
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe

aooga said:
This one seems to work for everyone I give it to.
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
Click to expand...
Click to collapse
I'll try it and report back in the morning. Thanks for all the help so far!

niphoet said:
I'll try it and report back in the morning. Thanks for all the help so far!
Click to expand...
Click to collapse
Sure.
---------- Post added at 08:57 PM ---------- Previous post was at 08:54 PM ----------
niphoet said:
I'll try it and report back in the morning. Thanks for all the help so far!
Click to expand...
Click to collapse
Just to let you know, that rom is pretty old. You'll need to do some updating. If you don't want to do that, you can also download this one :
DOWNLOAD
But it might not work. It's worth a try though.

aooga said:
Sure.
---------- Post added at 08:57 PM ---------- Previous post was at 08:54 PM ----------
Just to let you know, that rom is pretty old. You'll need to do some updating. If you don't want to do that, you can also download this one :
DOWNLOAD
But it might not work. It's worth a try though.
Click to expand...
Click to collapse
Neither of those worked. Here is the error I get: Link.
I guess my next step is to try to find my otg cable and try to load a rom from there, right?
------
EDIT:
I managed to get adb working in recovery using a 32-bit VM (I now remember the problems I've had in the past with x64 and adb). I installed Viper, used rumrunner to achieve S-OFF. I am still unable to flash cm11. PhilZ/CWM gives me Status 0 and TWRP just says failed. Any idea what my next step should be?
ANOTHER EDIT:
Okay, I'm able to install an older m7att build but i can't install any of the unified m7 roms.

Have you got fastboot working?
http://koush.com/post/universal-adb-driver
Read here...
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Post a fastboot getvar all when working
Sent from my Nexus 7 using XDA Premium 4 mobile app

niphoet said:
Neither of those worked. Here is the error I get: Link.
I guess my next step is to try to find my otg cable and try to load a rom from there, right?
------
EDIT:
I managed to get adb working in recovery using a 32-bit VM (I now remember the problems I've had in the past with x64 and adb). I installed Viper, used rumrunner to achieve S-OFF. I am still unable to flash cm11. PhilZ/CWM gives me Status 0 and TWRP just says failed. Any idea what my next step should be?
ANOTHER EDIT:
Okay, I'm able to install an older m7att build but i can't install any of the unified m7 roms.
Click to expand...
Click to collapse
You should be able to install any rom. Try flashing TWRP again? Whats the exact error in TWRP.

bored_stupid said:
Have you got fastboot working?
http://koush.com/post/universal-adb-driver
Read here...
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Post a fastboot getvar all when working
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36LW912065
(bootloader) imei: 354439051648014
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.240s
aooga said:
You should be able to install any rom. Try flashing TWRP again? Whats the exact error in TWRP.
Click to expand...
Click to collapse
I tried TWRP 2.6.3.3 and 2.7.0.0. Here is the error in TWRP: Link
EDIT: See this. Under the section "Recovery Update" I flashed the unofficial TWRP 2.7.0.8 and it flashed the latest nightly. I guess I'm good to go now. Thanks to all for all of the help!!

niphoet said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
......!!
Click to expand...
Click to collapse
Just to let you know, the error when it says "Too many links" happens when you use a USB 3 port. Android and adb don't play very nice with usb 3.

Unable to return my ONE to stock via RUU

Hey Guys,
I am pulling my hair out trying to return my HTC one M7 back to stock. Selling it to a friend that knows nothing about rooting and is not tech savy.
Anyways I cant seem to get the RUU to do. I have the correct file (I am with Rogers in Canada) that is the most up to date (see pictures).
I keep getting the Error 158 Image Error when I run the setup.
My phone is Locked as well which i know is the main cause for this error.
I am also running HD Revolution 84.0 at the moment.
I also set the CID to 11111111, hoping this might fix it but no luck
Any help is most appreciated.

FowlMouthedDuck said:
Hey Guys,
I am pulling my hair out trying to return my HTC one M7 back to stock. Selling it to a friend that knows nothing about rooting and is not tech savy.
Anyways I cant seem to get the RUU to do. I have the correct file (I am with Rogers in Canada) that is the most up to date (see pictures).
I keep getting the Error 158 Image Error when I run the setup.
My phone is Locked as well which i know is the main cause for this error.
I am also running HD Revolution 84.0 at the moment.
I also set the CID to 11111111, hoping this might fix it but no luck
Any help is most appreciated.
Click to expand...
Click to collapse
I should also note I am running TWRP v2.8.4.0

FowlMouthedDuck said:
I should also note I am running TWRP v2.8.4.0
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number please.

Seanie280672 said:
post your fastboot getvar all please without imei and serial number please.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4256mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT

FowlMouthedDuck said:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4256mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
Click to expand...
Click to collapse
Ok never mind, version main is missing, I suggest you find the firmware and flash that first then whilst still in the bootloader with fastboot USB on the screen, run the RUU

Seanie280672 said:
Ok never mind, version main is missing, I suggest you find the firmware and flash that first then whilst still in the bootloader with fastboot USB on the screen, run the RUU
Click to expand...
Click to collapse
Where is the best spot to download the firmware?

FowlMouthedDuck said:
Where is the best spot to download the firmware?
Click to expand...
Click to collapse
you should be able to pull it from the ruu, when you start the ruu and it extracts itself, make sure your computer is showing hidden files and folders then goto C:\users\(your user name)\app data\ local\(lots of strange characters and numbers folder) before closing the RUU and copy the firmware to a different location on your computer.
However, also as your s-off, you are aware you can flash any RUU like the 401 (WWE) or developer edition, its all stock.

Seanie280672 said:
you should be able to pull it from the ruu, when you start the ruu and it extracts itself, make sure your computer is showing hidden files and folders then goto C:\users\(your user name)\app data\ local\(lots of strange characters and numbers folder) before closing the RUU and copy the firmware to a different location on your computer.
However, also as your s-off, you are aware you can flash any RUU like the 401 (WWE) or developer edition, its all stock.
Click to expand...
Click to collapse
1. Is it in the Temp folder?
2. if It flash one of those RUU's, can I still update to Lollipop when it is available?

FowlMouthedDuck said:
Where is the best spot to download the firmware?
Click to expand...
Click to collapse
Your hboot 1.44 means the firmware has never been updated or did you put that their returning to stock ?
Maybe try an older RUU like >> http://forum.xda-developers.com/showthread.php?t=2529225

FowlMouthedDuck said:
1. Is it in the Temp folder?
2. if It flash one of those RUU's, can I still update to Lollipop when it is available?
Click to expand...
Click to collapse
Yup, dev edition will be the first to get it too.

Seanie280672 said:
Yup, dev edition will be the first to get it too.
Click to expand...
Click to collapse
Is it the Rom.zip file? When I tried to copy to the phone in windows 7 to the phone, it just gives me a "Cannot copy item" msg. The device has either stopped responding or has been disconnected.
I am thinking maybe the dev edition might be the best bet because my friend might be switching to another carrier instead of Rogers

FowlMouthedDuck said:
Is it the Rom.zip file? When I tried to copy to the phone in windows 7 to the phone, it just gives me a "Cannot copy item" msg. The device has either stopped responding or has been disconnected.
I am thinking maybe the dev edition might be the best bet because my friend might be switching to another carrier instead of Rogers
Click to expand...
Click to collapse
then try here >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
theirs also a RUU here 6.07.1540.2 >> http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
Also their is no Firmware.zip in a RUU their found in OTA update packages

clsA said:
then try here >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
theirs also a RUU here 6.07.1540.2 >> http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
Click to expand...
Click to collapse
Will this still allow the phone to be unlocked and switched to another carrier here in Canada? (ex. rogers to telus).

FowlMouthedDuck said:
Is it the Rom.zip file? When I tried to copy to the phone in windows 7 to the phone, it just gives me a "Cannot copy item" msg. The device has either stopped responding or has been disconnected.
I am thinking maybe the dev edition might be the best bet because my friend might be switching to another carrier instead of Rogers
Click to expand...
Click to collapse
well if you go to dev edition be sure to note clsA link incase of any problems and you have to return it to Rogers.
also need to know if you backflashed your HBOOT to 1.44 yourself ?
---------- Post added at 09:51 PM ---------- Previous post was at 09:45 PM ----------
clsA said:
then try here >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
theirs also a RUU here 6.07.1540.2 >> http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
Also their is no Firmware.zip in a RUU their found in OTA update packages
Click to expand...
Click to collapse
sorry missed this, thanks :good:

Seanie280672 said:
well if you go to dev edition be sure to note clsA link incase of any problems and you have to return it to Rogers.
also need to know if you backflashed your HBOOT to 1.44 yourself ?
---------- Post added at 09:51 PM ---------- Previous post was at 09:45 PM ----------
sorry missed this, thanks :good:
Click to expand...
Click to collapse
Can to simply take the firmware from the OTA? If so, do I install the .zip like any ROM? Because I am trying to do that and as soon as I hit install in TWRP, it just reboots the recovery.
And yes I did backflash the HBOOT. I believe i had to do it when I had the lastest Viperone rom installed.

FowlMouthedDuck said:
Can to simply take the firmware from the OTA? If so, do I install the .zip like any ROM? Because I am trying to do that and as soon as I hit install in TWRP, it just reboots the recovery.
And yes I did backflash the HBOOT. I believe i had to do it when I had the lastest Viperone rom installed.
Click to expand...
Click to collapse
Disregard my last post. I forgot you had to use fastboot to update firmware. So I used the firmware.zip from the OTA. Now after rebooting, i get no display. I still have my usb plugged in and I can hear windows connecting and disconnecting but nothing is happening when I hold down power

FowlMouthedDuck said:
Disregard my last post. I forgot you had to use fastboot to update firmware. So I used the firmware.zip from the OTA. Now after rebooting, i get no display. I still have my usb plugged in and I can hear windows connecting and disconnecting but nothing is happening when I hold down power
Click to expand...
Click to collapse
Crap .. what firmware did you flash ?? and you never answered how did you get to hboot 1.44
you have to flash those OTA firmware.zip in order 3.x to 4.x to 5.x to 6.x ... you cant just jump to the newest firmware
when you plug in your phone check device manager for QHSUSB_DLOAD

Oops I forgot to finish my post. I did downflash the hboot when I downloaded the latest viperone rom (i think it asked me to if I remember correctly).
So device manager has QHUSB_DLOAD, what should i do with it?
Sorry for all the headaches. I am still a little new to the firmware stuff and going back to stock

FowlMouthedDuck said:
Oops I forgot to finish my post. I did downflash the hboot when I downloaded the latest viperone rom (i think it asked me to if I remember correctly).
So device manager has QHUSB_DLOAD, what should i do with it?
Sorry for all the headaches. I am still a little new to the firmware stuff and going back to stock
Click to expand...
Click to collapse
Yeah that sucks .. hope you can make this work
http://forum.xda-developers.com/showthread.php?t=2770684

FowlMouthedDuck said:
So I used the firmware.zip from the OTA.
Click to expand...
Click to collapse
you should be able to pull it from the ruu
Click to expand...
Click to collapse
he said, not from an ota. Ota fimware are only patches and must be flashed incrementally like clsA said.
So device manager has QHUSB_DLOAD, what should i do with it?
Click to expand...
Click to collapse
Looks like you make the situation worse. you could have avoided that by following what they said... :angel:
Now follow this guide: http://forum.xda-developers.com/showthread.php?t=2770684