Tampered - Locked - S-On - Need to exchange - HTC Droid DNA

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)

Related

[q] my htc evo 3d won't pass htc welcome screen!?

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.

[Q]bricked phone, help please, need some advice

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.

Help needed if possible, VM phone stuck in Bootloader, RUU Error 170

If anyone could spare a moment that would be most appreciated. I have searched for hours and my laptop is crying under the "weight of a thousand tabs" at the moment and have finally decided that my problem is not going to be solved by more forum browsing. Luckily I have all the links to tutorials I was following so I can pinpoint exactly where things went wrong.
The carrier: Virgin Mobile
The problem: Stuck in bootloader, no options working. Recovery and factory reset both yield nothing. RUU fails with error 170.
The History: I decided I was going to try and root my phone today. That actually worked via stock. Followed a guide that showed me how to unlock the phone (using HTCDEV) and pushed TWRP as my recovery.img. I flashed the stock ROM and had root access. Then I was following another guide to obtain S-OFF. It said that I should flash SetMainVersionLow via my recovery and the next step was to run "fastboot oem lock" which worked. Then it told me to run the RUU.exe which simply gives me error 170 "USB Connection Error". I was running adb and fastboot commands early from this same machine, and nothing changed from the point of "fastboot oem lock" and running the RUU, though now my device won't even show up in fastboot or adb.
Any help would be most appreciated. I'm 12 hours in surfing on the web for solutions and have got nothing. I have learned that this site rocks (just looking through posts and the general responses people get) and you can bet and help some stranger will give me on the internet will be paid forward five times over. I'm a computer major in school so I am well versed with technology but as you can tell my rooting experience is non-existent. Thanks all.
More info:
Windows 8 64-Bit
Bootloader displays the following:
*** RELOCKED ***
*** Security Warning ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
RADIO-1.09.00.0108
OpenADSP-v2.6.0.226.00.0217
eMMC-boot
May 17 2012,15:06:44
EDIT: I have, through restarting both laptop and phone a few times, obtained fastboot. My RUU now proceeds past where I would encounter error 170, but still fails. When I unplug the USB it says HBoot older. Anyone have a "newer" RUU?
fastboot getvar cid = SPCS_002
fastboot getvar mainver = 1.00.000.0
I was trying to use:
RUU_Shooter_ICS_35_S_Sprint_WWE_VM_1.13.652.2_Radio_1.06.00.0426_NV_1.53_144_release_262287_signed.exe
I also tried:
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
'
which gave me the error "CID incorrect"

[Q] [DEAD?] HTC EVO 3D pro help required

So the story is I got this phone from a friend for free and it's not working. Next is some info I have found.
First is the forever bootscreen.
*** LOCKED ***
*** SECURITY WARNING ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011, 15:03:01
....................
Some phone info.
HTC 3D EVO FCC ID: NM8PG86300
Model: PG86300
IMEI: 35871044661787
S/N: HT1CYV211753
P/N: 99HNJ004-00
a token example from fastboot, at htcdev returns error 150 - doesn't allow me to proceed with unlock of the bootloader.
<<<< Identifier Token Start >>>>
47B3145FF96274E03070C998F66FF7BD
C7245D1F8DF602901AAD442C71F4EB5C
B9B4081EA26F6A82B3EABDC8544686F1
1AC27EA1394FF8AEDA634395FA0A8FBE
6288792606968C46841EE9B7670F20C9
5D1B1C1295D3882C81BCA01AE0E3A179
11673423F363A34C1797CDA128371DAE
9DB4C0B7500FE097C43CCBFB50377180
F56738F0C03BA925749693A2FCEF1E9A
AAAEFE9EFDD676CB56E9787B9D42F3BA
D87FBEAD3B4F8D0A283D2C2E376A1779
36C5EA4FF479C7B811BB3B273E4DEF8A
066110BCDEB9AF842DC2588DAB982383
73A0E6825419B45B5CF37CA6A011DBF0
CDCFF3D8EE40F36DE4223A70272CE7E4
4D16C6CB24E5CD3FC0D03BFDACBC7F4F
<<<<< Identifier Token End >>>>>
I hope that's enough data.
To sum up it is locked with S-ON. Selecting recovery/factory reset reboots it in 1 sec to bootloader. Phone does respond to some fastboot commands, most useful was fastboot oem rebootRUU that takes me to a black screen with an HTC logo and if I disconnect a usb cable I'm stack in bootloader like menu with the only choice 'RUU' that is not click able at all. I have tried enormous number of .img files through fastboot flash (loads, throws: remote: signature verify fail) and using an sd card(loads, verifies, goes back to main menu). I'm in process of trying out RUU exe files from website url androidruu with provider shooter (I can't post urls) First run I thought was going to be a success, it found the phone said that the current version is something like &20, started doing something - restarted the phone and phone got stuck at black screen when the program exited with code 155, while waiting for the phone to get to bootloader I assume. Please your suggestions, maybe deeper knowledge of fastboot protocols would help. Device is not showing up under adb. I was trying all of that using windowsXP/ubuntu computer. please help reinstalling, reviving, flashing this half alive HTC EVO 3D. I believe it is called roger as well. And I assume the previous owner is an idiot.
Some more to say
Ive spent 24 hours with google, HTC EVO 3D (GSM i believe), usb cable and an SD card, i'm lost and despair.
first of all make sure your bootloader is locked .you can lock it via fastboot : Type the following in the command prompt window:
fastboot devices
This is to ensure that your device is detected, if nothing appears on screen with this command, then it means you don’t have the proper drivers installed on your PC. And if that’s the case you should download and install/re-install the HTC Sync software given in Step 1.1Now type the following command to re-lock your HTC bootloader
fastboot oem lock then download and run this and follow the instructions http://www.androidruu.com/getdownlo...00U_11.25.3504.06_M_release_262714_signed.exe
Sent from my Panasonic printer Buy me a beer cause i'm alcoholic and i need more and more https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=HN6YQLDZT76EE
Hi i have a same problem,,,after install the RUU its says everithing is ok and fine your phone is now reboot,,,and after reboot it stuck at the white screen with a HTC logo,,,i dont know what can i do,,,can you help me please ? my bootloader is locked and i think i dont do anything wrong,,,,and my second problem is i cant go into recovery mod,,,if i press the power button to open the recovery mode in bootloader the phone will reboot as normall and stuck at the white screen with a HTC logo,,, :/ i looking for a soution 3 days,,, but noting happened,,, i really dont know what can i do ,,, any ideas ? plss.. :/
Informations :
Shooter_U (ics) S-on
Radio : 11.25.3504.06_m
and the Ruu what i used is ( RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed .exe)... im very depressed about it... (( please help me to get back to life my evo... :/,,and sorry for my bad english :/
first of all you cant get to recovery cauese the ruu erased your custom recovery.if the ruu was succesful and you can not boot your phone it can be a hardware damage...
edit: what is the result after running ruu? its succesful or what?
Sent from my Panasonic printer Buy me a beer cause i'm alcoholic and i need more and more https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=HN6YQLDZT76EE
yes,,,its says succesful,,,you are succesfuli installed the stock rom now your android phone will reboot and ready to use.. ,,or something like that,,,but after reboot its stuck on white screeen...
Any solution? plss help me .. :/

Bootloop problem

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.

Categories

Resources