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
Related
Hi. My problem is simple. I cannot pass boot screen. I have T-Mobile G2 Touch (polish version). I decided to load RUU through HBoot because my PC doesnt see pluged in phone. Only RUU version which is working on my phone is T-Mobile PL 3.35 and some other numbers further. Its, what i think the same soft as i had before (before RUU when it started to not passing boot screen) so it hasnt fixed anything. So i thought that maybe other RUU roms will be more helpful, but when Hboot is checking ROM its says that CID is incorrect and i cant install it. I have heard about Goldcard, but in this case, when i cant plug phoneto my PC, i doubt if this is a good idea. My question is- what can i do in this case? I really dont want to have bricked phone. Thanks!
Hello
I have a serious problem with my phone , started yesterday when i restarted my phone on the button in the system ( like restarting a computer). After that it has started but system booted only to htc welcome screen and no further, so rly help me
Methods i have tried:
- battery pull
- htcdev unlock bootloader ( so my bootloader is now unlocked )
nothing works ;(
SHOOTER_U VT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
What rom did you flashed, being s-on will cause issues flashing the kernel, you must have 4ext recovery with smart flash enabled
(Don't ask me for help as I couldn't care if your phone explodes, eh!
I have the exact same problem. Been using my phone issue free for a year and a half. Today I noticed the gps was on but it was not enabled in the "toggles" menu. I rebooted the phone and now it's in an ENDLESS loop that wont pass the white / green HTC logo boot screen.
I can not access recovery it just reboots.
I have tried:
1) flashing stock RUU through fasboot which did go to 100% ... phone still reboot loops
2) flashing latest stock ICS through fastboot (did not work said CID error)
3) Pulled battery and let phone sit
4) s-off with HTC dev unlocker
At this point I'm not sure what to do... I think this may be a catastrophic hardware failure.
Well I do believe my device is a lost cause.
1) I was able to flash 2.17 via RUU but it didn't change a thing.
2) Did the "Brick" method and downgrade to HBOOT 1.40 Still same behavior.
3) flashed 1.13 fully 100% via RUU.. still same thing.
No matter what I do the phone will not get past the white HTC splash screen. It stays on that screen for about 20 seconds then reboots. Also the phone feels really hot behind the cameras (not the battery) I think it's toast. Luckily I have an old HTC hero for a backup so I'm not completely FUBAR but I'll be on craigslist tomorrow looking for something new. Thinking of jumping ship to PagePlus this might be just the right time.
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.
Hello friends, master cdma evo3d, I ask you to help provide solutions for my current shooter htc bootloop, stuck at htc logo ...... initial problem when I update OTA all went well, until the requested reboot my evo , apparently after on it just stuck at htc logo and repeated, some friend give me a solution to flash the RUU file it and I did, indeed managed to install but when lit up again the results are still the same stuck on htc logo,more suggestions to install files PG86IMG zip.I doing well, but the result remains the same, namely stuck at htc logo and repeated, ..... then I try (something stupid) to lower HBOOT follow one of the tutorials in this forum with the htc conditions stuck, I was less fortunate in the "bricked device" .... now mainver I've even changed to 2.95.651.5 and I already can not install files RUU or PG86IMG again ..... what do I do now? I hope there is support from all to give you a little knowledge is still newbie to me and pardon my language is probably a mess because I asked for help uncle google to translate .......
***RELOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
RADIO-1.09.00.0100
openADSP-v02.06.0.2226.00.0217
eMMC-boot
According to the setup you have you should be able to lower the main version and run the ruu....
Sounds like you did that but it should work. Just in case here are some downloads:
https://copy.com/6l3QGAbVTC1WJim4
https://copy.com/jF1Mm
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.