My cousin asked me to replace his Aria's cracked digitizer and I did. When I tried turning it on to see if it worked, the screen had backlight but it was black and the orange led light kept flashing. It didn't move from there. I took off the battery and tried it again and it went to what looked like S-On HBOOT FASTBOOT screen. It wont respond to the volume keys to go down or up on the selection menu and the power button won't select anything. I tried plugging it to the computer but it only does the same thing and sometimes the orange led light doesn't flash it'll just be orange.
This is exactly what it says
LIBERTY PVT SHIP S-ON
HBOOT-0.57.0000
MICROP-031b
TOUCH PANEL-STN21_00
RADIO-7.08.35.06
May 8 2010,03:56:58
HBOOT (this part is highlighted in blue and when i connect the usb to the pc it'll say HBOOT USB PLUG)
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT(This is highlighted in blue)
RECOVERY (not highlighted but is green colored)
CLEAR STORAGE
SIMLOCK(not highlighted but colored blue)
then it has three android bots on skateboards at the bottom
I tried putting the Original shipped file as a zip in the sd card but when it checks to see if there's any to flash it doesn't recognize i guess because it doesn't tell to me to continue with the installation or anything.
IDK what to do ?
Please help ! Thanks in advance!
Is it possible you have the wrong digitizer? I noticed this line:
TOUCH PANEL-STN21_00
Click to expand...
Click to collapse
Mine says TOUCH PANEL-STN21_03, and any other images I can find on Google are the same
I know there are two types for Liberty, Synaptics & Atmel.. I'm not sure if the hardware detects which one is installed and switches over, but if it doesn't you may have an Atmel one and the phone came with Synaptics.
It might be something for a different phone too
(Libertys with Atmel are something like "TOUCH PANEL-ATMEL224_16ab")
Does it work and boot with the old one put back in? (if that's possible.. I haven't had to replace any digitizers, so don't really know what happens)
WinSuk said:
Is it possible you have the wrong digitizer? I noticed this line:
Mine says TOUCH PANEL-STN21_03, and any other images I can find on Google are the same
I know there are two types for Liberty, Synaptics & Atmel.. I'm not sure if the hardware detects which one is installed and switches over, but if it doesn't you may have an Atmel one and the phone came with Synaptics.
It might be something for a different phone too
(Libertys with Atmel are something like "TOUCH PANEL-ATMEL224_16ab")
Does it work and boot with the old one put back in? (if that's possible.. I haven't had to replace any digitizers, so don't really know what happens)
Click to expand...
Click to collapse
But my little aria is
LIBERTY PVT SHIP S-OFF
HBOOT-6.02.1002
MICROP-031b
TOUCH PANEL-STN21_00
RADIO-7.13.35.13
Nov 4 2010,23:12:58
and I am used Revolutionary to let it S-OFF
By the way,my aria is made in Taiwan and bought it in Taiwan,too
ishow0806 said:
But my little aria is
LIBERTY PVT SHIP S-OFF
HBOOT-6.02.1002
MICROP-031b
TOUCH PANEL-STN21_00
RADIO-7.13.35.13
Nov 4 2010,23:12:58
and I am used Revolutionary to let it S-OFF
By the way,my aria is made in Taiwan and bought it in Taiwan,too
Click to expand...
Click to collapse
Hmm I guess that doesn't matter then
It could still be wrong and the boot loader doesn't change though
Related
Hi. You might think. it's another lazy ass*ole, who is to lazy to read. But i red basicly all posts about bricked Hero. I have GSM Hero 2.1. Tried to update to 2.3, with RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDrive. And in the middle of process it bricked.
I get with white screen with writings:
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
TOUCH PANEL-SYN0104
RADIO-6.35.15.14
Aug 4 2009,19:43:30
And a picture of over crossed chip at the bottom. Tried to post a picture, but site wont let me. Will upload after a while.
Tried all possible key combinations - nothing. Can't get it to recovery mode. Tried same updating software, but the same. Tried to do the same on other PC - same.
Is there anything possible to do? 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.
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)
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.