I made a terrible rookie mistake and foolishly updated my Google Edition HTC one to 4.4 over OTA. However, my device at the time was unlocked and rooted running TWRP and a rooted 4.3. I am beating myself because not only did I update recklessly, but I failed to make a backup before doing so. I have learned a few lessons so far from this folly and I anticipate to learn many more.
Right now when my device restarts it quickly flashes the "google" logo on black screen then transitions to a cyan screen with little green and red lines. When I boot into recovery mode and make my way to fastboot, this is what is shown:
***tampered***
***unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSP-v31.120.274.0617
0S-3.07.1700.1
I've been scouring the internet for options and have tried the following with various forms of failure. I've tried flashing various recovery files (I ultimately get "FAILED (remote: signature verify fail)"). Then I tried turning S-OFF and that wouldn't let me push the revone due to the "binary being unable to execute." I've unlocked and rooted multiple times before, but all the errors I keep getting have me stumped. I'm happy to try these and more ideas again because chances are high I missed a crucial step.
I would really appreciate if I could get some guidance on how to proceed to even get back to stock android (I'm willing to abandon any info on my SD card as I cannot seem to figure out how to save any of it at this point).
Apologies in advance for posting this in the wrong place, not providing proper information, making major noob moves, etc. Please show me pity and offer any guidance/help you may have. I will very much appreciate it.
Thank you so much!
Related
Hi all i have been following this board for a while and thanks to u guys i have leant a lot. sadly not enough :-(
I have killed my sensation :-(
I have tried every stock ruu and ics sticks at 39% most others stick at 44%
I have have black sceen with htc in middle and exlamation marks in corners.
If i pull out the usb i get:
*** unlocked ***
pyramid pvt ship s-off rl
hboot 1.20.0000
radio-11.15.3504.16_m
emmc-boot
(date)
RUU
I have used command promp and with fastboot tried flashing recovery which says its done but still nothing??
tried sending roms to system stillo nothing??
Cant access my fone through adb.
and to be honest i have no idea wot to do??
I tried fastboot erase system but came back remote not allowed.
Is it dead or can it be revived????
Thanks in advance lads.
Oh i was running miui and wen i restarted my fone oneday it just died.
This should probably be in the Sensation part of the forums for more specific help.
You said that you tried flashing recovery through fastboot and it says that it's done. Maybe you should try booting into recovery. If it really has successfully flashed a recovery then you should be able to boot into recovery. I'm not sure the button combinations you have to push for the Sensation, but I'm sure you can find it by googling it.
As for trying fastboot erase system and it coming back as remote not allowed, maybe you don't have the engineering hboot to utilize fastboot commands. I know with the mytouch 3G and mytouch 4G that in order to utilize fastboot commands you have to have the engineering hboot.
If none of this helps, maybe you can ask people on the Sensation forums for help.
You just hold down and press volume but it still does not go into recovery?? i have reposted this in the sensation section thanks for ur help i will look into the hboot thing.
Hello, well I recently got this HTC evo 3D from a friend, he bought it extemely cheap since it was not working, and he tried to fix with no success so he gave it to me to try. The thing is that I have some experience fixing samsung phones but HTC seems like a really new thing to me. Anyway the first thing I would like to ask its about the real state of the phone. The phone only turns on and shows a black screen, the htc logo in white letters at the center, and one triangle in each corner, all of the triangles have an exclamation mark.
Thats all it shows, I tried the volume down + power button to enter the recovery screen but it doesnt work. We dont really know what happened to the phone or how this device was bricked, and since I dont really know htc I cannot really guess. Not sure either if this device is either S/On or OFF, rooted or etc.
I read the HTC Unbricking Project and thought "I might as well try that", but I dont really understand what they are saying, not about using linux, its about the tools they say you need:
the appropriate package for the device
the latest RUU for your device
a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
We dont use any of this on samsung phones so I dont really understand what they mean, could anyone offer an overall advice of what should I do or where to read about this stuff.
Thanks in advance
Update: I managed to get this white screen when I unplugged the usb cable, hope it helps
Robert1989 said:
Hello, well I recently got this HTC evo 3D from a friend, he bought it extemely cheap since it was not working, and he tried to fix with no success so he gave it to me to try. The thing is that I have some experience fixing samsung phones but HTC seems like a really new thing to me. Anyway the first thing I would like to ask its about the real state of the phone. The phone only turns on and shows a black screen, the htc logo in white letters at the center, and one triangle in each corner, all of the triangles have an exclamation mark.
Thats all it shows, I tried the volume down + power button to enter the recovery screen but it doesnt work. We dont really know what happened to the phone or how this device was bricked, and since I dont really know htc I cannot really guess. Not sure either if this device is either S/On or OFF, rooted or etc.
I read the HTC Unbricking Project and thought "I might as well try that", but I dont really understand what they are saying, not about using linux, its about the tools they say you need:
the appropriate package for the device
the latest RUU for your device
a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
We dont use any of this on samsung phones so I dont really understand what they mean, could anyone offer an overall advice of what should I do or where to read about this stuff.
Thanks in advance
Update: I managed to get this white screen when I unplugged the usb cable, hope it helps
Click to expand...
Click to collapse
I can't make out what all that says on your white screen(that's bootloader by the way.) I need you to tell me a few things first.
1.Is the device s-on or s-off? To find out go to the top line and read across to see if it is s-on or s-off
2. Is the bootloader locked, relocked or unlocked? You can see the status at the very top highlighted in purple.
3. What's the hboot version
4. Also, what's the radio band number?
Now the thing is, with HTC devices there are two different s-off's
S-on bootloader unlocked and true s-off. S-on bootloader only gives you access to some of most of the name memory unlocked. You can't downgrade firmware. You can only flash your current one or upgrades. If you upgrade your firmware, your stuck. S-off gives full access to the whole nand memory. The idea is to gain s-off as it is much easier to flash things, more access to software, can upgrade or downgrade your hboot and firmware.
Edit: I got good news for you. Since your able to access your bootloader screen, your phone is not bricked. As a matter of fact, as long as it can boot up to something, its not bricked. Now keep in mind, you will need to download an ruu file and run it to restore that phone.
Robert1989 said:
Update: I managed to get this white screen when I unplugged the usb cable, hope it helps
Click to expand...
Click to collapse
I've never seen that orange "RUU" flag on the bootloader screen before. I'm not sure what it means but it may need to have the 2.89.651.2 RUU (the build it currently has) re-flashed so I would try running that version of the RUU (similar to Kies) after connecting it via USB to a Windows PC.
You can get the RUU here.
ramjet73
Your bootloader indicates you're S-ON and Re-Locked, which means that it was once HTC unlocked (The manufacturer's poor substitute for unlocking a bootloader)
The device is definitely not Bricked by any definition of the term. A true brick doesn't power on. This is just "soft bricked" meaning it's functional, but has a corrupt partition or partitions that are preventing it from reaching the android subsystem.
You need to use the RUU EXE when you're at that white screen. It should recognize it and re-flash most of the partitions on the device. You might also need to run it twice possibly.
UPDATE: I thought about deleting this but I figured I'd leave it just in case it happened to somebody else. Rebooting my laptop (yay windows) and re-running the RUU exe fixed the world. In my defense, I don't use windows very much.
My power button has come loose and Verizon was nice enough to swap out my DNA for a new one. They told me that I absolutely had to return the phone to stock or I would see a fee on my bill.
I used Moonshine on my phone so I decided to follow the instructions here to flash back to factory.
http://forum.xda-developers.com/showthread.php?t=2293919
Unfortunately something has clearly gone wrong. I couldn't get the RUU download to work in windows so I decided to try the alternate option. Now I'm stuck looking at my bootloader with the following on it.
Code:
***TAMPERED***
***LOCKED***
MONARUDO PUT SHIP S-ON
HBOOT-1.33.0001
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
eMMC-boot
My windows laptop doesn't appear to recognize the old phone at all now. fastboot devices shows nothing in the results. My Linux desktop seems to talk to the old phone just fine. The new phone is recognized just fine on both machines. I'm not really sure what this is about.
Did I miss something important when I followed the instructions? (i've got to assume yes)
Any thoughts? (other than sending cookies back with the phone as a bribe)
ok I have been reading non stop and I think this is a problem of me being very uneducated and getting in over my had in the cell phone world. I put viper rom on my phone. It installed correctly ( so it said) but it has been stuck in bootloader ever since. It just reboots and turns off over and over no matter what selection I make. I also do not have access to TWRP. Could someone please point me in the correct direction ? (in plain English) Im sure I have read the correct steps out there but I know so little I don't know where to start. it is unlocked. s-off as well. htc one M7 VZ hboot 1.57.000 os-4.10.605.3 eMMC-boot 2048MB I don't know if any of this helps.. i can not access my phone through pc at the moment......
thanks,
Howsema
Hello,
please excuse my poor english. I have a stock Evo3D which ends up in a bootloop after starting it. I have never rooted / installed a custom rom on it.
I wanted to gift my evo 3D to my little sister, after turning it on to check it i realized my batterie became too weak to start the phone so i replaced it with one i found on ebay.
Since then i coudn't boot properly.
I spend about 12 Hours to solve this problem but it just wont work regardless of what i do.
Here are some informations the bootloader shows:
***LOCKED***
SHOOTER_U PVT SHIP S-ON RL
HBOOT- 1.53.0007
RADIO- 11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
May 22 2012, 01:06:07
The first thing i tried was to reinstall a stock ROM using a RUU, this didn't work i did a couple of attempts and then realised it has a Vodafone branding, next thing was using a Vodafone RUU
it didnt work aswell, i read on another forum that it has to be a ICS RUU with Vodafone CID which appearently doesn't exist. So my next attempt was to change the CID in which i needed to unlock the bootloader.
So i went to htcdev.com and did everything step by step, i thought "man this is easy", i got to last step where i could choose if i really wanted to unlock the phone or not. I choose yes and the phone was supposed to reboot.
The problem now is it doesn't, it freezes with the red light and black screen, i cant access the bootloader unless i remove the battery and put it back in. If i do so it still is locked.
Now im out of ideas and feel bad for my sister, cause i promised to give this phone to her if she gets good grades.
If you have ANY ideas please let me know i would really appreciate it.
xbluemonkeyx said:
Hello,
please excuse my poor english. I have a stock Evo3D which ends up in a bootloop after starting it. I have never rooted / installed a custom rom on it.
I wanted to gift my evo 3D to my little sister, after turning it on to check it i realized my batterie became too weak to start the phone so i replaced it with one i found on ebay.
Since then i coudn't boot properly.
I spend about 12 Hours to solve this problem but it just wont work regardless of what i do.
Here are some informations the bootloader shows:
***LOCKED***
SHOOTER_U PVT SHIP S-ON RL
HBOOT- 1.53.0007
RADIO- 11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
May 22 2012, 01:06:07
The first thing i tried was to reinstall a stock ROM using a RUU, this didn't work i did a couple of attempts and then realised it has a Vodafone branding, next thing was using a Vodafone RUU
it didnt work aswell, i read on another forum that it has to be a ICS RUU with Vodafone CID which appearently doesn't exist. So my next attempt was to change the CID in which i needed to unlock the bootloader.
So i went to htcdev.com and did everything step by step, i thought "man this is easy", i got to last step where i could choose if i really wanted to unlock the phone or not. I choose yes and the phone was supposed to reboot.
The problem now is it doesn't, it freezes with the red light and black screen, i cant access the bootloader unless i remove the battery and put it back in. If i do so it still is locked.
Now im out of ideas and feel bad for my sister, cause i promised to give this phone to her if she gets good grades.
If you have ANY ideas please let me know i would really appreciate it.
Click to expand...
Click to collapse
Is it a sort-by-lowest-price battery? if so it could be (again) a battery problem! In my experience most used batteries for evo 3d are stock ones by htc and Anker ones
Snoob25 said:
Is it a sort-by-lowest-price battery? if so it could be (again) a battery problem! In my experience most used batteries for evo 3d are stock ones by htc and Anker ones
Click to expand...
Click to collapse
Thanks for the quick reply, it was a mid priced battery with sold by a high rated seller.
I've dealt with a similar problem. Try booting into the bootloader and leave it there until the battery dies. Pull the battery for -several minutes-, then replace and plug in. Give it a while to charge, then start again with the ruu.
Edit:
Also with a similar problem, had some luck running the ruu multiple times consecutively without letting it boot all the way / rebuild the dalvik cache between flashes.