Hi everybody. I just bought an HTC one m9 (att) sight unseen through local classified ads It will not boot into an OS. It has TWRP 2.8.6.4
When I hold down and power I get:
HTC download mode
*** UNLOCKED ***
htc_himaulatt PVT S-OnLK-1.0.0.0000
RADIO-01.01_U1440221_62.05.503206_F
OpenDSP-v20.2.6-00452-M8994-0216
OS-1.32.502.31
Mar 23 2015,02:02:54(506785)
Here are my challenges:
It does not seem to charge.
When I attempt to boot the OS I get "this build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action"
It stays on this screen until the battery dies.
I attempted, based on the readme thread, to download the corresponding Ruu and convert it to a 0PJAIMG.zip. The phone recognizes this when I boot to download mode, but my volume up button does not work.
What should I try next to go from a paperweight to a usable phone.
swing4thefence said:
Hi everybody. I just bought an HTC one m9 (att) sight unseen through local classified ads It will not boot into an OS. It has TWRP 2.8.6.4
When I hold down and power I get:
HTC download mode
*** UNLOCKED ***
htc_himaulatt PVT S-OnLK-1.0.0.0000
RADIO-01.01_U1440221_62.05.503206_F
OpenDSP-v20.2.6-00452-M8994-0216
OS-1.32.502.31
Mar 23 2015,02:02:54(506785)
Here are my challenges:
It does not seem to charge.
When I attempt to boot the OS I get "this build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action"
It stays on this screen until the battery dies.
I attempted, based on the readme thread, to download the corresponding Ruu and convert it to a 0PJAIMG.zip. The phone recognizes this when I boot to download mode, but my volume up button does not work.
What should I try next to go from a paperweight to a usable phone.
Click to expand...
Click to collapse
Update:
I updated TWRP to 3.2.3.0 and was able to flash Lineage OS 13, but now my recovery mode freezes and the rom bootloops. When recovery freezes, the screen goes crazy, kind of like it looks when the digitizer underneath is broken.
I managed to log in long enough to downgrade twrp to 3.0.0.0 but the screen problems are the same and set in even faster.
Now what?
Related
Do you know of a way to decrease the time it takes AT&T's TITAN to start-up?
When powering up, I go through three splash (a.k.a. boot) screens:
1) HTC 2) AT&T rethink possible 3)Windows Phone
I would like to speed up how long each of these screens are displayed (or eliminate one or more of them) to say time going from Off to the Lock Screen.
FYI: I'm not a developer and don't have access to Developer Tools
Thanks for Your Time!
Phone: HTC Titan PI39100
OS: Windows Phone 7.5 v. 7.10.7720.68
Firmware Revision No. 1600.2200.11004.502
Hardware Revision No. 0002
Bootloader v. 1.10.160015.3(132409)
Modifications: NONE
Unfortunately we can't do that without having an unlock (I don't know what level of unlock, but certainly higher than a developer unlock). The HTC logo can be overwritten with a flashing tool (but don't try it yet, I don't think any compatible flashing tool has been made yet).
Sit tight! If/when custom ROMs start popping up, the ability to flash over the HTC logo will soon follow.
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.
I wanted to start a thread to see if we can get some ideas going on how to fix this flicker of epic preportions some of you are having running AOSP on the 3.4 kernel.
Anyone can participate flicker or no flicker we need your help, Please list the following:
Hboot:
Hboot Engineering or normal:
Super CID / Back to normal:
which recovery are you using:
Are you S-off or S-on:
Are you Dev unlocked or not:
Do you use the SD swap hack or not:
How bad is the flicker (1 not at all / 2 some flicker/ 3 anime fight scene):
What is your base band:
(please copy the template above into your post and answer the questions)
Hboot: 1.15.1111
Hboot Engineering or normal: Engineering
Super CID / Back to normal: CID-VZW_001
which recovery are you using: TWRP 2.6
Are you S-off or S-on: S-off
Are you Dev unlocked?: No
Do you use the SD swap hack or not: No
How bad is the flicker (1 not at all / 2 some flicker/ 3 anime fight scene): 2
What is your base band: 1.53.06.0919
Hboot: 1.15.0000
Hboot Engineering or normal: (do not know what this means)
Super CID / Back to normal: CID-VZW__001
which recovery are you using: TWRP 2.5.0.0
Are you S-off or S-on: S-off
Are you Dev unlocked?: Yes
Do you use the SD swap hack or not: Yes
How bad is the flicker (1 not at all / 2 some flicker/ 3 anime fight seen): I've seen the whole spectrum, mostly 2 (some flicker), but sometimes none.
What is your base band: 1.53.06.0919
My info
Hboot: 1.15.0000
Hboot Engineering or normal: normal - used HTCDev unlock process (although had to change CID from Verizon first)
Super CID / Back to normal: should be normal - VZW_001
which recovery are you using: Clockwork 6.0.3.3
Are you S-off or S-on: S-ON
Are you Dev unlocked or not: yes
Do you use the SD swap hack or not: no
How bad is the flicker (1 not at all / 2 some flicker/ 3 anime fight scene): 3
What is your base band: 1.53.06.0919
Here's what my HBOOT screen says:
*** TAMPERED ***
*** UNLOCKED ***
FIREBALL PVT SHIP S-ON RL
HBOOT-1.15.0000
RADIO-1.53.06.0919
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 1 2012, 12:05:25
MY serial is HT26KS312867
I flashed 9/20 this morning (without even clearing anything but cache) and got the new Cyanogenmod setup screens, though I just Next'd through them. The flickering is still there, and is really bad on specifically on the color grey (or when, for instance, opening a page that's white and then dragging down from the top which shades out the white underneath) but is much, much less noticeable below 25% brightness. I'm going to run at that level of brightness for a while and just see how it works.
We need to post in the Android general section or something and ask for help. As mower said, this is a developer forum overall and I'm sure there's got to be some people out there willing to take a look into it or offer some ideas.
Hboot: 1.15.1111
Hboot Engineering or normal: Engineering
Super CID / Back to normal: CID-VZW__001
which recovery are you using: TWRP 2.6.3.0 Official & ClockworkMod Touch 6.0.3.3 Official
Are you S-off or S-on: S-OFF
Are you Dev unlocked or not: NO
Do you use the SD swap hack or not: NO
How bad is the flicker (1 not at all / 2 some flicker/ 3 anime fight scene): 1
What is your base band: 1.53.06.0919
HT26YS S/N
logcat output of bootup for my device (which flickers)
In the 10.2 thread (which I don't have authority to reply to) brianr134 asked if someone could post bootup logcat output from a device with a flickering panel. here it is! it's from the 9/20 nightly which i've been running all day. not too bad to use, although i've noticed bluetooth output has some weird knocking sounds sometimes and its a little unstable (but i did _NOT_ do a complete wipe, it was an upgrade from 10.1 simply because I wanted to quickly see how bad the flickering was, etc). I hope it helps!
"Show Surface Updates" on mdm05 vs nightly cm10.2
I just noticed that "show surface updates" has different behavior as well under these two - under mdm05 you can click "show surface updates" and not see any flashing to indicate updating. But when you do this under the cm10.2 nightlies, the status bar updates wildly in the same pattern as the flickering. I had turned this on under 10.2 briefly just to see if that had anything to do with it, and I initially thought it wasn't related. But I'm back on mdm05 now and the difference in the behavior is striking. The question is, why would it make some panels flicker and others not?
Since I have no idea how the "flicker" appears, does it come immediately at boot (visible in the CM animation) or part way through? Is it only in the gray colors?
Can someone else post another logcat?
brianr134 said:
Since I have no idea how the "flicker" appears, does it come immediately at boot (visible in the CM animation) or part way through? Is it only in the gray colors?
Can someone else post another logcat?
Click to expand...
Click to collapse
I can't get you the logcat, but I can tell you how it appears. First, mdmower discovered that if you never let the device's screen go off, the flicker will never appear. Obviously your screen has to go off at some point though. So once that happens, you will eventually start to see flicker. The best way to notice it is to turn brightness up. If you use auto brightness and you're in a dark setting you may not notice it right away. It starts as a mild flicker, mostly only noticeable on light grays. It eventually progresses worse and worse over a couple hours and you'll always see it. It's pretty much the edges of the screen flickering. If you stay on that build for a long time - maybe over night - the flickering will be super intense.
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!
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 .. :/