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.
Related
bricked my htc one trying to flash an ruu and computer gliched. can get into fast boot and it displays *tampered* *relocked* and *security warning*.
tried to re-up the ruu and says 12 signatures failed or something. any help would be much apriciated. and i cannot connect with adb because i was trying to get rid of cm10 and for some reason i cannot connect to adb with cm10. now when i reboot phone just goes right into bootloader/fastboot. tried to flash a recovery did not work. PLEASE HELP!
thanks in advance.
bk73w said:
bricked my htc one trying to flash an ruu and computer gliched. can get into fast boot and it displays *tampered* *relocked* and *security warning*.
tried to re-up the ruu and says 12 signatures failed or something. any help would be much apriciated. and i cannot connect with adb because i was trying to get rid of cm10 and for some reason i cannot connect to adb with cm10. now when i reboot phone just goes right into bootloader/fastboot. tried to flash a recovery did not work. PLEASE HELP!
thanks in advance.
Click to expand...
Click to collapse
do you have s-off? you can only flash a RUU with s-off...
How exactly did the computer glitch? Calm down, if you can get into the bootloader which I assume you can (as you can see the tampered etc tags) then it's still salvageable. As the person above asked, do you have s-off?
postfatal said:
How exactly did the computer glitch? Calm down, if you can get into the bootloader which I assume you can (as you can see the tampered etc tags) then it's still salvageable. As the person above asked, do you have s-off?
Click to expand...
Click to collapse
nope still got it to work though. was very shocked. bootloader worked, was locked, and s-on. could not do ruu so i found a stock rom i ran it once got a security issue then manually typed it in something like fastboot flash image XXX.zip and got another thing 12 security signature or something other, ran it again imediatelly <did not close command prompt and left phone with the htc emblem on there> with the same command and surprisingly it worked!
Unlock then reflash a recovery
Sent from my HTC One using xda app-developers app
Yep, that should do it since you unlock and flash from the bootloader.
Bseagull said:
Yep, that should do it since you unlock and flash from the bootloader.
Click to expand...
Click to collapse
it's weird tho, because it was "relocked" and S-ON so I dont even know how it worked.
So I've run into a problem with my new Htc First phone, the wifi doesnt locate any access points.
Its unlocked,rooted and S-off-ed.
I can unroot and lock the bootloader but does anyone know how to S-on it?
Yea, you just have to ruu first and then follow this guide.
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Kendosis said:
Yea, you just have to ruu first and then follow this guide.
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Click to expand...
Click to collapse
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
dramon said:
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
Click to expand...
Click to collapse
You usually have to run a factory reset, cache/dalvik cache wipe before you flash roms. I get that wifi problem sometimes when trying to flash a rom before wiping.
dramon said:
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
Click to expand...
Click to collapse
DUDE QUICK THING ! you can't flash any roms in till you RELOCK THE BOOTLOADER ! I know it sounds weird but trust me you will keep the S-off status (assuming you have s-off) and everything works fine, I couldn't flash any roms in till I relocked and I heard others have this problem too.
Now the WiFi problem, if factory resetting doesn't work, try flashing the stock rooted ROM around these threads, if that doesn't work try JMZ's kernel, and if that doesn't work then you have a hardware problem, good luck.
Sent from my HTC first
If he just RUU's it he won't have to worry about relocking his boot loader, he should just use titainium backup and ruu to save time.
Kendosis said:
If he just RUU's it he won't have to worry about relocking his boot loader, he should just use titainium backup and ruu to save time.
Click to expand...
Click to collapse
Trust me I've tried RUU and even that didn't work for me, in till I relocked , it was weird but its worth a shot since relocking keeps the s-off anyways
Sent from my HTC first
SneakyGuyDavid said:
Trust me I've tried RUU and even that didn't work for me, in till I relocked , it was weird but its worth a shot since relocking keeps the s-off anyways
Sent from my HTC first
Click to expand...
Click to collapse
I've tried it many times already it works, after you ruu it you just have to turn s-on before you try to unlock the boot loader again otherwise you'll get bootloop.
Kendosis said:
I've tried it many times already it works, after you ruu it you just have to turn s-on before you try to unlock the boot loader again otherwise you'll get bootloop.
Click to expand...
Click to collapse
guys guys, you've lost me.
All I need to do is wipe away all traces of my rooting and bootloader unlocking etc as I'm returning it for warranty.
Now my First is rooted, custom recovery and s-off and unlocked .
I want it unrooted, s-on and boot loader locked.
Someone please guide me through the steps :/
btw im not a n00b, but this is my first HTC phone so I'm not too familiar with these ruu's and s-offs
dramon said:
guys guys, you've lost me.
All I need to do is wipe away all traces of my rooting and bootloader unlocking etc as I'm returning it for warranty.
Now my First is rooted, custom recovery and s-off and unlocked .
I want it unrooted, s-on and boot loader locked.
Someone please guide me through the steps :/
btw im not a n00b, but this is my first HTC phone so I'm not too familiar with these ruu's and s-offs
Click to expand...
Click to collapse
Step 1. RUU your device
Step 2. After it reboots when it's done ruu'ing just start it and go through the set up.
Step 3. Turn on USB debugging mode.
Step 4. Turn on CMD on your PC then just follow the commands below
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writecid xxxxxxxx (where xxxxxxxx is your stock CID.) Mines is CWS__001 on the HTC first I'm not sure if it's the same on all devices just check to see if yours it the same, if it is just use fastboot oem writecid CWS__001
fastboot reboot-bootloader
fastboot getvar cid (It should say CWS__001 if that is your cid.)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
And that's it, it is a extremely simple process lol, I've done it at least 20 times since I tend to ruu my device a lot off of S-OFF, when messing around with different roms.
http://forum.xda-developers.com/showthread.php?t=841890
So its okay if I flash the ruu by the second method as in this thread?
And will custom recovery be overwritten with stock recovery?
OK Update!
I was well on my way to relock,s-on my phone etc and here's what happened
@Kendosis
@SneakyGuyDavid
1) Sucessfully RUU'd
As it happened I didnt have my sim inserted and when I rebooted, the wifi was working! When I inserted the sim the wifi stopped working. I did some bit of research and it turns out it has something to do with wifi country codes. Apparently it can be fixed by this app
https://play.google.com/store/apps/details?id=com.fardjad.android.wifixmanager
2) Since the app required root, I was going to get root again.
(Flashing RUU gave me bootloader locked)
I unlocked and then flashed CWM
3) Since I had no roms on my phone storage and the CWM doesnt mount storage, I had to sideload the ROMS.
4) No matter which roms I flashed, I was stuck in a bootloop. I relocked and tried flashing again but I was again stuck in a bootloop. CWM works fine though.
Current status: Bootloader Locked, S-off.
What do I do to fix this bootloop :/
@dramon
I told you to s-on after you ruu first otherwise you get boot loop lol.
Now RUU again and right after don't install nothing just start up the phone and turn usb debugging on and follow the steps to S-ON.
Kendosis said:
@dramon
I told you to s-on after you ruu first otherwise you get boot loop lol.
Now RUU again and right after don't install nothing just start up the phone and turn usb debugging on and follow the steps to S-ON.
Click to expand...
Click to collapse
also sideload sucks ass, if you flash TWRP then you can run adb from it and use adb push, so in cmd you would run " adb push
ROMZIPNAME.ZIP /sdcard "
Thanks guys, I now have an idea of how the rooting and unlocking works for HTC (Y)
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
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
Hi, I have a thoug one, So i had an att htc one m7, i changed its os to the GPE and the hboot was 1.54, i was having problems with battery overheating and losing signal so i decided to get it back to stock, so first error: i used TWRP to flash an old nandroid of the firs OS it had, and it worked except that the touch screen didnt work, so i tried to downgrade the hboot to 1,44 and succedeed, but it didnt help to the touch problem, i tried to flash a RUU exe of att but when the RUU tries to connect to bootloader the phone disconnects, i read somewhere that if i relock the bootloader it can help but it didnt, now I am stucked I cant flash anything because of the bootloader and I cant give permission to unlock it again since the touch doesn work. Please help, im truly desperate.
ivandaterrible said:
Hi, I have a thoug one, So i had an att htc one m7, i changed its os to the GPE and the hboot was 1.54, i was having problems with battery overheating and losing signal so i decided to get it back to stock, so first error: i used TWRP to flash an old nandroid of the firs OS it had, and it worked except that the touch screen didnt work, so i tried to downgrade the hboot to 1,44 and succedeed, but it didnt help to the touch problem, i tried to flash a RUU exe of att but when the RUU tries to connect to bootloader the phone disconnects, i read somewhere that if i relock the bootloader it can help but it didnt, now I am stucked I cant flash anything because of the bootloader and I cant give permission to unlock it again since the touch doesn work. Please help, im truly desperate.
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" and don't forget that since you downgraded to hboot 1.44, only win7/Linux/Mac will detect the phone in bootloader mode (not win8 / win10).
alray said:
Post the output of "fastboot getvar all" and don't forget that since you downgraded to hboot 1.44, only win7/Linux/Mac will detect the phone in bootloader mode (not win8 / win10).
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-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 and then the fastboot was recognized by windows.