Database Develop

my phone is bricked...

hi all i have unfortunatly bricked my phone so i have locked the bootloader and want to get the stock RUU back on my phone but i'm having issues getting 1 that works, i include the screen shot og my getvar all screen....
can anyone post a download link for the right ruu that will get me back to stock please??

nottys4 said:
hi all i have unfortunatly bricked my phone so i have locked the bootloader and want to get the stock RUU back on my phone but i'm having issues getting 1 that works, i include the screen shot og my getvar all screen....
can anyone post a download link for the right ruu that will get me back to stock please??
Click to expand...
Click to collapse
ok. A bricked phone is one that is bricked. Yours is "softbricked".
It seems like you have S-OFF. FYI you should never ever just lock bootloader after having bricked something. And if you put it S-ON again ... this makes things even harder. But luckily you are S-OFF.
Going back S ON with a altered bootloader is inevitably going to lead into a hard bricked device ! -> so don't go s-on!
Now here is the RUU you need:
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
DON'T INSTALL IT USING WINDOWS 8 OR ABOVE!
You need to use win7!
Why?
Q: What do I have to pay attention to using Windows 8.1 ?
A: Actually, there are no more driver issues with Windows 8 or Windows 8.1. But if your HTC One is on hboot 1.44 or even below hboot 1.44 you can't get a fastboot connection to your HTC One. This means if you're using one of the older RUU's that downgrade to hboot 1.44 you'll be stuck after the first hboot preupdate:
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
And you won't be able to reflash the RUU to complete the RUU process.. This means that you have to find a Windows 7 Computer to complete the RUU process. What does this exactly mean?
Never flash a 1.44 firmeware or RUU package to your device using Windows 8+ or you'll be stuck!
Click to expand...
Click to collapse
If you wanna go 100% stock so that nobody sees that your phone was ever rooted: head over here: http://forum.xda-developers.com/showthread.php?t=2541082
If you just want stock software, maybe root again, go there: http://forum.xda-developers.com/showthread.php?t=2632736
Remember to mention or quote me if you have any further questions and if I helped you I'd really appreciate a thanks

[Q] HTC One stuck in bootloader with relocked bootloader, s-on and custom recovery

​my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh. I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
​my Hboot is version 1.57 and my OS is 6. 10.531.9
​I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
​if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.

kage_outram said:
​my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh.
I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
​my Hboot is version 1.57 and my OS is 6. 10.531.9
​I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
​if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.
Click to expand...
Click to collapse
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.

majmoz said:
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.
Click to expand...
Click to collapse
What commands do I put in to add the RUU

kage_outram said:
What commands do I put in to add the RUU
Click to expand...
Click to collapse
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer

majmoz said:
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer
Click to expand...
Click to collapse
what should happen next

[Q] Hard bricked VZM HTC M7

Hey guys, so I tried to unlock my phone to switch over to T-mobile and in the process, I believe I bricked my phone. I followed some very misleading guide, and due to this, my phone is stuck on the RUU screen with the four triangles. To make things worse, my computer (running win 8.1) stopped being able to recognize my phone, so adb and fastboot won't recognize it either (I feel like this happened due to me trying to flash a RUU). I tried several times to re-install drivers to no avail. I don't think I can get to the recovery screen either. Is there any hope in saving this or is it a goner? Thanks.
What I've done so far before this state:
S-OFF
Rooted
changed the CID and MID to T-mobile relevant IDs

kiweewee said:
Hey guys, so I tried to unlock my phone to switch over to T-mobile and in the process, I believe I bricked my phone. I followed some very misleading guide, and due to this, my phone is stuck on the RUU screen with the four triangles. To make things worse, my computer (running win 8.1) stopped being able to recognize my phone, so adb and fastboot won't recognize it either (I feel like this happened due to me trying to flash a RUU). I tried several times to re-install drivers to no avail. I don't think I can get to the recovery screen either. Is there any hope in saving this or is it a goner? Thanks.
What I've done so far before this state:
S-OFF
Rooted
changed the CID and MID to T-mobile relevant IDs
Click to expand...
Click to collapse
if you have used a 1.xx.xxx.x RUU with windows 8.1, thats the problem. When flashing a 1.xx.xxx.x ruu, your bootloader will downgrade to version 1.44. This bootloader version isn't compatible with windows 8.1 (fastboot won't work).
The ruu screen with 4 triangles = incomplete ruu flash. Most likely caused by the computer not being able to flash the entire RUU after hboot 1.44 was flashed.
If using a ruu.exe, you'll need to find a winXP or 7 pc. If using a ruu.zip, you can either use winXP, win7, Linux (recommand ubuntu 12.04 32 bits version) or MacOS.
Btw why did you flashed a ruu to unlock your phone? You know that sim-unlock can be done simply by using a paid code? Or if you have s-off you can sim-unlock for free using the sieempi method.
can you post all the information you can see on the bootloader screen here?

Uh I don't think I can get to the bootloader screen as it is stuck on the RUU screen. Would connecting my phone on linux get some response?

kiweewee said:
Uh I don't think I can get to the bootloader screen as it is stuck on the RUU screen. Would connecting my phone on linux get some response?
Click to expand...
Click to collapse
hold volume down and power until the phone reboot in bootloader mode. can you confirm the ruu version used?

I've done that and the screen just turns off and on with the RUU screen with the four triangles still there.
I've also tried connecting my phone on linux, after installing adb and fastboot, but it has given me a "HTC unknown usb device( device failed enumeration) " warning.

I used this ruu after hearing my phone should be using this ruu, I changed the cid to 11111111 and mid to tmobile on the android.info file so it would work
RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted
After flashing this once it gave me the hboot error thing to boot again, but that is when my phone stopped responding to fastboot.

kiweewee said:
I used this ruu after hearing my phone should be using this ruu, I changed the cid to 11111111 and mid to tmobile on the android.info file so it would work
RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted
After flashing this once it gave me the hboot error thing to boot again, but that is when my phone stopped responding to fastboot.
Click to expand...
Click to collapse
I'm pretty sure your totally wasting your time you can't turn a CDMA Verizon phone into a GSM t-mobile phone by flashing a RUU
your going to end up with a bunch of screwed up partitions
this is how you get fastboot working on windows 8.1 hboot 1.44
http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337

[Q] Tried Returning to Stock, now stuck in bootloader

So about 6 months ago a friend wanted to root his sprint m8, i had a tmobile one at the time and rooted it and s-off'd it successfully so i did his phone for him, however firewater didn't work for s-off and he didn't want to pay the 25 for sunshine. fast forward to yesterday and he wanted to go back to stock to turn in his phone for an upgrade, so i tried to restore his stock nandroid, but he deleted it. so then i attempted to relock the bootloader and flash the ruu. The ruu failed, and now im stuck in fastboot, twrp is gone, so i can't get a backup restored. I'm hoping their is some other way i can can return his phone to stock. I feel stuck and out of my depth, so i'm hoping someone can help, thanks.

jwalters1123 said:
So about 6 months ago a friend wanted to root his sprint m8, i had a tmobile one at the time and rooted it and s-off'd it successfully so i did his phone for him, however firewater didn't work for s-off and he didn't want to pay the 25 for sunshine. fast forward to yesterday and he wanted to go back to stock to turn in his phone for an upgrade, so i tried to restore his stock nandroid, but he deleted it. so then i attempted to relock the bootloader and flash the ruu. The ruu failed, and now im stuck in fastboot, twrp is gone, so i can't get a backup restored. I'm hoping their is some other way i can can return his phone to stock. I feel stuck and out of my depth, so i'm hoping someone can help, thanks.
Click to expand...
Click to collapse
You say the RUU failed...
Any error message?
As much info as you can give would be better.

Yeah it boots into the black screen with silver htc logo and it starts to run and then the error pops up and says "Error 1555 unknown error the rom update utility cannot update your android phone. please get the correct rom update utility and try again."

jwalters1123 said:
Yeah it boots into the black screen with silver htc logo and it starts to run and then the error pops up and says "Error 1555 unknown error the rom update utility cannot update your android phone. please get the correct rom update utility and try again."
Click to expand...
Click to collapse
Sounds like you are trying to use an older RUU.
The latest can be found here.
http://forum.xda-developers.com/showthread.php?t=2729173

BD619 said:
Sounds like you are trying to use an older RUU.
The latest can be found here.
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
No, that's where I initially got the first RUU, when it failed i tried to use an older one and the same thing happened. I used this one. http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe Which was the very top one for sprint, non hk. and I locked the bootloader again so it would work.

jwalters1123 said:
No, that's where I initially got the first RUU, when it failed i tried to use an older one and the same thing happened. I used this one. http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe Which was the very top one for sprint, non hk. and I locked the bootloader again so it would work.
Click to expand...
Click to collapse
If the phone is s-on you cannot flash an older RUU.
Make sure you drivers are installed correctly.
Make sure you are using a USB2 port.
Post the info from bootloader please...really just the hboot version.
Post a copy of getvar all also please.

BD619 said:
If the phone is s-on you cannot flash an older RUU.
Make sure you drivers are installed correctly.
Make sure you are using a USB2 port.
Post the info from bootloader please...really just the hboot version.
Post a copy of getvar all also please.
Click to expand...
Click to collapse
ok so hboot version says 3.19.0.0000, i am on a usb 2.0 port, i am not sure how to paste my copied text from the cmd prompt into this box so i just pasted it to a .txt file and attached that and it has all the getvar all info. thanks for the help.

Everything is current according to the getvar...go ahead and remove it as it contains the imei #
The latest RUU should work.
Maybe try downloading Sync Manager to update the drivers or try a different PC/usb port.

Low and behold i was in a 3.0 port lmao... smh... so you just saved me beating my head against the wall for god knows how much longer, thanks for the help, the ruu is working fine now:fingers-crossed:

Unbrick M7 no root no recovery no unloked bootloader no touch screen

So I bricked my M7 pretty bad, at this point I dont have root acces, the usb disconnects from pc when trying to acces bootloader (adb works), the bootloader is relocked. This is what I did: I
used TWRP to flash and old stock nandroid, it worked but the touchscreen didnt, so I cant do anything.
I tought the problem was the hboot so i downgraded from 1.54 to 1.44
I tried to run a ruu.exe but it gave a 155 error, i read somewhere that the problem might be the unlocked bootloader so I relocked.
Since then whenever I try to acces the bootloader thru ADB it disconnects.
Thats it, I cant do anything else. I need HELP.

ivandaterrible said:
So I bricked my M7 pretty bad, at this point I dont have root acces, the usb disconnects from pc when trying to acces bootloader (adb works), the bootloader is relocked. This is what I did: I
used TWRP to flash and old stock nandroid, it worked but the touchscreen didnt, so I cant do anything.
I tought the problem was the hboot so i downgraded from 1.54 to 1.44
I tried to run a ruu.exe but it gave a 155 error, i read somewhere that the problem might be the unlocked bootloader so I relocked.
Since then whenever I try to acces the bootloader thru ADB it disconnects.
Thats it, I cant do anything else. I need HELP.
Click to expand...
Click to collapse
Can you post a picture of your bootloader screen so we know what firmware and CID you have?

donkeykong1 said:
Can you post a picture of your bootloader screen so we know what firmware and CID you have?
Click to expand...
Click to collapse
Hi thanks for the reply, but I already solved it, it turns out I didnt knew obout the driver and Im running w10 so that was the problem, anyway I deactivated the windows signature enforment drivers function and get registry archive from this thread http://forum.xda-developers.com/htc-...s-8-1-t2858337 and then the fastboot was recognized by windows.