Related
I have a G1 that was given to me stuck on the exclamation point screen.
I've tried various update.zip methods, When i try to update it says it can't read from the recovery. It'll install the update like normal it seems, but then when it reboots, go right back to the exclamation point screen.
It was never rooted. Not sure what version was on it when it bricked
I've searched the forum all day trying to find a thread like this.
Does anyone have any insight into how to fix this?
Thanks
PusherRobot said:
I have a G1 that was given to me stuck on the exclamation point screen.
I've tried various update.zip methods, When i try to update it says it can't read from the recovery. It'll install the update like normal it seems, but then when it reboots, go right back to the exclamation point screen.
It was never rooted. Not sure what version was on it when it bricked
I've searched the forum all day trying to find a thread like this.
Does anyone have any insight into how to fix this?
Thanks
Click to expand...
Click to collapse
Not sure what rom you tried to put on it but I would bet the camera button is stuck.
billquinn1 said:
Not sure what rom you tried to put on it but I would bet the camera button is stuck.
Click to expand...
Click to collapse
Should be the home button in this case. If it was the camera he'd see rainbows, with home it takes you to recovery (the ! screen)
exactly. thanks for the help.
I replaced the buttons and now everything works.
26th July 2012, 04:44 PM #51
Member
Thanks Meter 1
Posts: 62
Join Date: Nov 2008
Location: Jersey City
MORE INFO >
hey guys,
thanks for the post and the info. I am hoping I can get some help. I recently upgraded to a new ATT - HTC Vivid. I guess I was impatient in wanting to root and flash ROM so I used the [TOOL] HTC Vivid All-In-One Toolkit V2.2 to "un-lock bootloader" and get root. Afterwards I realized the phone had/has old software/rom (no ICS beats audio etc) - I tried updating the software manually and it would not take - kept getting error messege. Then I got notification that ATT/HTC was trying to "push" the update to my phone but when I tried to install the update it would not work. I keep getting what looks like a dead android with chest open with red exclamation point. I tried a few times and still nothing. so after some research I came across this thread. I am still a "noob" at this I guess so I could really use some help, please. I believe I have to "re-lock bootlaoder" but I am confused as to how to go about this. for example, how do you, "TRY FLASHING THE WCXRECOVERY.IMG USING FASTBOOT FIRST?" - please help! lol like I said - I'm still a noob I guess
I tried the video but it only further confused me
Today, 04:16 PM #52
Member
Thanks Meter 1
Posts: 62
Join Date: Nov 2008
Location: Jersey City
MORE INFO >
please help!!!! I really need it. I tried using your tutorial to re-lock my Vivid and update ROM to ICS. I got through the first part where I re-locked the phone ut when I got to the part to "unlock" again before flashing recovery I get the "Unlock bootloader" screen and I use volume button to select yes and hit power button but that's it - it's stuck at that scree and will not go further. now my phone won't start normally if I try etc and I even got a red exclamation etc - Please help, I dont know what I did wrong but now I have no phone!!!!!
Thanks a bunch for any and all help
This should probably be in the General forum, not development...
If you pull your battery, then put it back in, then hold VOLDOWN button and the POWER button, do you get into Bootloader mode?
If you can, choose Fastboot mode, and then connect your phone to the PC. (I'm assuming you have the right driver(s) installed so you can issue Fastboot commands to the phone?)
If you've gotten that far, and want to re-lock your bootloader using fastboot, the fastboot command is:
"fastboot oem lock"
Run that in a command prompt window. Make sure you have navigated to the folder that has fastboot.exe, of course. Are you familiar with using command prompt?
Once your bootloader is relocked, you can re-start your phone into bootloader mode, and then flash your stock carrier's RUU using your PC... I hope this helps.
LaZiODROID said:
This should probably be in the General forum, not development...
If you pull your battery, then put it back in, then hold VOLDOWN button and the POWER button, do you get into Bootloader mode?
If you can, choose Fastboot mode, and then connect your phone to the PC. (I'm assuming you have the right driver(s) installed so you can issue Fastboot commands to the phone?)
If you've gotten that far, and want to re-lock your bootloader using fastboot, the fastboot command is:
"fastboot oem lock"
Run that in a command prompt window. Make sure you have navigated to the folder that has fastboot.exe, of course. Are you familiar with using command prompt?
Once your bootloader is relocked, you can re-start your phone into bootloader mode, and then flash your stock carrier's RUU using your PC... I hope this helps.
Click to expand...
Click to collapse
thanks a bunch!!! I'm still a "noob" I guess and I will re-post in General. In the meantime, I can get into Bootloader mode but I am already "Relocked" - from what I understand at this point I was supposed to "Unlock" again and flash recovery using "unlock bin" but at the unlock bootloader screen on my phone after I select yes and press power button nothing happens. my phone freezes at that ponit. I dont know what to do now. any help is greatly appreciated.
rsuarez74 said:
thanks a bunch!!! I'm still a "noob" I guess and I will re-post in General. In the meantime, I can get into Bootloader mode but I am already "Relocked" - from what I understand at this point I was supposed to "Unlock" again and flash recovery using "unlock bin" but at the unlock bootloader screen on my phone after I select yes and press power button nothing happens. my phone freezes at that ponit. I dont know what to do now. any help is greatly appreciated.
Click to expand...
Click to collapse
I wonder (since you are already re-locked), if you should consider flashing your phones stock RUU (so the phone will be back to stock).
Then unlock your bootloader via HTCDEV again...
Then you can flash a custom recovery, then you can do a nandroid backup of your phone... then you can do your wipes and install a rom?
thanks again for responding, much appreciated. I wish I knew how to flash back to stock. I'm at a loss or stuck right now.I just found the stock RUU and I'm trying to download it but once I get it how do I flash it back to stock? That is actually what Ive been trying to do. You see I recently upgraded to the Vivid and "unlocked bootloader" and "rooted" before I realized I had old software (no ICS - beats audio etc). So after some research I read that I had to "re-lock" so that is what I was trying to do before I got stuck. what do you think I should do fromhere? I'd really like to at least get my phone working again with stock even, just working.
thanks again,
Rafael
LaZiODROID said:
I wonder (since you are already re-locked), if you should consider flashing your phones stock RUU (so the phone will be back to stock).
Then unlock your bootloader via HTCDEV again...
Then you can flash a custom recovery, then you can do a nandroid backup of your phone... then you can do your wipes and install a rom?
Click to expand...
Click to collapse
rsuarez74 said:
thanks again for responding, much appreciated. I wish I knew how to flash back to stock. I'm at a loss or stuck right now.I just found the stock RUU and I'm trying to download it but once I get it how do I flash it back to stock? That is actually what Ive been trying to do. You see I recently upgraded to the Vivid and "unlocked bootloader" and "rooted" before I realized I had old software (no ICS - beats audio etc). So after some research I read that I had to "re-lock" so that is what I was trying to do before I got stuck. what do you think I should do fromhere? I'd really like to at least get my phone working again with stock even, just working.
thanks again,
Rafael
Click to expand...
Click to collapse
OK. So since you are relocked, you should be able to flash your stock RUU.
The RUU is an EXE file. Just run it on your PC (with your phone, in fastboot mode, connected to the PC). It will detect the phone and perform the flashes and when it's finished, your phone will be like stock again.
Yeah...just use ruu like you would any other pc program...it will walk you through the steps in the program...
As for beats...I had beats audio on stock gingerbread? Confused why you don't...I only had gingerbread for a couple days before upgrading but I remember seeing the beats icon in notification...
Sent from my HTC PH39100 using Tapatalk 2
I tried what you said and I got an error message (error 104) and it would not update/flash the ROM. I am stuck.
and when my phone restarted I ended up with the red exclamation point in a triangle again. any more ideas? I hope I did not "brick" my phone.
rsuarez74 said:
I tried what you said and I got an error message (error 104) and it would not update/flash the ROM. I am stuck.
and when my phone restarted I ended up with the red exclamation point in a triangle again. any more ideas? I hope I did not "brick" my phone.
Click to expand...
Click to collapse
What is the exact file name of the RUU you are using?
Also, when your phone was working, what was the stock base that it had? Was it Gingerbread? or ICS?
From a quick google search, it seems Error 104 is "wrong hboot version". Interesting... I remember mine said that when I was trying to flash the old GB on my phone which had already been upgraded to ICS.
mg2195 said:
Yeah...just use ruu like you would any other pc program...it will walk you through the steps in the program...
As for beats...I had beats audio on stock gingerbread? Confused why you don't...I only had gingerbread for a couple days before upgrading but I remember seeing the beats icon in notification...
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I tried the old ATT RUU without ICS which is what I had originally and it did not take. I got an error message (error 104). I also did not have beats audio surprisingly enough when I first got the phone which is how I realized I did not have the new/current ATT ROM ICS.
LaZiODROID said:
What is the exact file name of the RUU you are using?
Also, when your phone was working, what was the stock base that it had? Was it Gingerbread? or ICS?
From a quick google search, it seems Error 104 is "wrong hboot version". Interesting... I remember mine said that when I was trying to flash the old GB on my phone which had already been upgraded to ICS.
Click to expand...
Click to collapse
name of RUU I tried: RUU_Holiday_Cingular_US_1.63.502.4_Radio_1.11.1020.03_30.77.551061.02L_release_221238_signed.exe
and it was originally Gingerbread
thanks guys
We really need a mod to move this to the "Q&A" section...
Anyways assuming your on completely stock gingerbread you can call this number *#*#682#*#* that will do a force update...vant be root tho, and can't have an unlocked bootloader
Edit...discard this post just read above about the red exclamation mark...can you still get to hboot? If you can...can you verify that it says "re-locked" at the top?
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
We really need a mod to move this to the "Q&A" section...
Anyways assuming your on completely stock gingerbread you can call this number *#*#682#*#* that will do a force update...vant be root tho, and can't have an unlocked bootloader
Edit...discard this post just read above about the red exclamation mark...can you still get to hboot? If you can...can you verify that it says "re-locked" at the top?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I can't even get to the dialer.
yes, I can still get to hboot, I think. or bootloader and it does say "RELOCKED" at top.
Use this ruu...http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe this should update you to stock ics assuming you can still get to hboot...and from their fastboot...
-ill be back in about an hour...gotta go to church..hopefully your problem will be solved...if not ill be here to help as soon as I get home
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Use this ruu...http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe this should update you to stock ics assuming you can still get to hboot...and from their fastboot...
-ill be back in about an hour...gotta go to church..hopefully your problem will be solved...if not ill be here to help as soon as I get home
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Do this ^^^
All that you need to do it boot n hboot then select fast boot and when you plug it in the pc it should say USB next to fast boot then just run the ruu file and it should hook you up with stock ics
mg2195 said:
Use this ruu...http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe this should update you to stock ics assuming you can still get to hboot...and from their fastboot...
-ill be back in about an hour...gotta go to church..hopefully your problem will be solved...if not ill be here to help as soon as I get home
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I tried running the RUU and it got stuck at 34% for a while. I unplugged the phone to attempt running the RUU again and now all I can get is black screen with HTC and 4 exclamation points in the corners of the screen - please help!!!
please dont tell me I "bricked" my phone.
Can you still get into hboot ? I wouldn't unplug the phone while its doing stuff I had that issue and just stopped the program and tried again , it takes some time to finish approximately 10 min so just let it do its thing . Just fyi
Bigtjmc said:
Can you still get into hboot ?
Click to expand...
Click to collapse
not anymore
I keep getting the HTC screen with exclamation points in the corners...
Pull the battery and try again . If that don't work then hopefully some of the more experienced guys can help.
---------- Post added at 07:46 PM ---------- Previous post was at 07:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1672425
That may help
The exclamation marks are a failed ruu...try running the ruu again...it should still work (I think) if not then try pulling the battery and trying again...
Yeah...next time do not pull the plug, I'm sure its still saveable tho..I've had failed ruu flashes before and it mentions something about exclamation marks in the corners, so Im pretty sure the ruu has a fix for it...if I get time ill see if I can get that info from a ruu...
Sent from my HTC PH39100 using Tapatalk 2
I was using the instructions from here to remove the yellow triangle from my Note N7000, and found that other people have had similar issues to what happened with mine (on page 34 of thread). I flashed the 1.tar and get the complete black screen as the instructions state (step 6) ... but from step 7 onwards, I have no response at all from my phone. I have 2x Jigs, and have attempted to use both to get this fixed, but I am not able to get phone to reconnect to ODIN. People have reported the same issue, but to no response.
I had a Galaxy Note N7000 on Telstra (Australia) but unlocked from network, running CM9 4.0.3 and was trying to flash to 4.0.4 when I got the yellow triangle. Can't check any other the other stats at present as obviously, my phone is a brick. Anyone got any super secret squirrel tricks that will get my phone back so I don't need to take it back to Telstra to get them to fix it.
Further to the above, answering some questions already asked in original forum, battery had a charge, but when I attempt to connect to charger to confirm, get no battery charging symbol on screen, get nothing at all.
When connecting the phone to Odin 1.85, and 1.87 for Steps 7-9 and the Jig Bought from here as well as making one myself, still no joy.
Any assistance will be appreciated, or am I going to have to revert to the devil to get a repair due to a hardware fault?
massochist said:
I was using the instructions from here to remove the yellow triangle from my Note N7000, and found that other people have had similar issues to what happened with mine (on page 34 of thread). I flashed the 1.tar and get the complete black screen as the instructions state (step 6) ... but from step 7 onwards, I have no response at all from my phone. I have 2x Jigs, and have attempted to use both to get this fixed, but I am not able to get phone to reconnect to ODIN. People have reported the same issue, but to no response.
I had a Galaxy Note N7000 on Telstra (Australia) but unlocked from network, running CM9 4.0.3 and was trying to flash to 4.0.4 when I got the yellow triangle. Can't check any other the other stats at present as obviously, my phone is a brick. Anyone got any super secret squirrel tricks that will get my phone back so I don't need to take it back to Telstra to get them to fix it.
Further to the above, answering some questions already asked in original forum, battery had a charge, but when I attempt to connect to charger to confirm, get no battery charging symbol on screen, get nothing at all.
When connecting the phone to Odin 1.85, and 1.87 for Steps 7-9 and the Jig Bought from here as well as making one myself, still no joy.
Any assistance will be appreciated, or am I going to have to revert to the devil to get a repair due to a hardware fault?
Click to expand...
Click to collapse
At points 7-10 the screen will not work!
Follow the rest of instructions and your phone will be all set..
My Point was that even after steps 7-10, nothing happens. Follow them to the t, and don't get my screen back, still just have a brick.
No feedback from device, device won't connect with Odin at step 10 (No COM:XX comes up) ... and device doesn't even register with PC as being connected. Different USB Slots used everything tried, and I have scoured every post pertaining to a yellow triangle in XDA, still without having any joy in getting this fixed. :crying:
Further to the above, it was step 5 that lead to this result. From step 5 onwards, I haven't been able to use my Note. Which makes me a sad panda.
Just trying to find a way to fix it rather than sending it back to Telstra to try and get a warranty repair ... if I can.
sahilarora2003 said:
At points 7-10 the screen will not work!
Follow the rest of instructions and your phone will be all set..
Click to expand...
Click to collapse
Just to make sure that I wasn't doing something wrong, got the stop watch on my G15 out, and timed everything to the T, making sure that the battery wasn't in for longer than expected etc, and this was after having the phone on charge since my last message. Still to no avail. Follow the prompts of taking battery out etc, boot into download mode, push volume up to accept the download mode, connect to PC with Odin Loaded, and then without Odin Loaded, and no response from PC, so Phone isn't responding to the Unbricking, or the computer isn't responding. This was tried in my 3 free USB ports tonight, with no luck.
Hey guys, quite honestly this is just a post-mortem help I felt I would want to chime in with. I just had almost a heart attack last night thinking I bricked my HTC Raider 4G / HTC Holiday / HTC Vivid / HTC Velocity 4G - Whatever you want to call it, it's the same phone. BTW, the captcha on this site and the discrimination towards new users is borderline a war crime
I want to ensure you that if you followed the whole Juopunutbear S-off bootloop / ControlBear method - your phone is NOT BRICKED. Mine wasn't, and I almost gave up on it last night. I ended up trading my HTC Raider 4G with someone for a Samsung Galaxy S III, but I wanted to touch base and just give you a heads up as to what I did (as best my memory serves me).
My situation was as follows:
1) I used the whole S-Off Toolkit By Hasoon2000 - and actually got S-Off (Security Off)
2) I followed to a tee, with all of it's "beer" references and did the whole "wire-trick" see picture below, I had to pull out my lab lamp light to see it and was getting more and more angry as the evening progressed.
3) My phone was stuck in the Juopunutbear S-Off Bootloop (or Boot Loop as some put it)
4) I could get the phone into Recovery/Fastboot (whatever you want to call it.)
Here is what I did to fix it:
1) Get yourself your OEM RUU (This is the Original Equipment Manufacturer Rom Update Utility), I hate acronyms so I will clarify as I go. You can download these at the following link (If you come back to this page a year from now and the links are broken, Google them by the exact file name, I am certain someone out there will keep backups forever. The link below surely has your carrier, e.g. Telstra etc. Follow the instructions and download your RUU for your carrier:
http://www.filefactory.com/f/002b74e0f4775869/
2) Pull the battery out of your HTC Raider / Holiday / Vivid / Velocity
3) Re-insert the battery into the phone
4) Press the volume down button + power and hold until the "Bootloader" or "Recovery" or "HBoot" or "Fastboot" screen comes up - many names for it.
5) Once the screen has come up, click on Fastboot and connect it to your computer. If it detects your computer it will say "Fastboot USB", this is good and it will look like the image at the bottom.
6) Once the phone is connected, run the specific file name for your phone based on carrier from point number 1.
7) Leave the phone plugged in and running, and it will basically flash the phone back to OEM - at least this way you can have a useable phone and will allow you to retreat/regroup and fight another day.
Fastboot USB Photo - Get your phone to look like this by going through the menus, it won't take more than 10 seconds
http://i47.tinypic.com/ru5m55.png
My Lab Setup - With The "Wire Trick" + Lamp and me getting more and more pissed off.
http://i48.tinypic.com/dyng9v.jpg
I hope this helps, I was quite honestly pulling my hair out trying to find out more information/help but it was just almost impossible to find for this phone - I think the reduced user base is partially to blame for this. My previous phone was a Samsung Galaxy S I9000 and I had absolutely no issues with support. I've learned my lesson and devices to back out, I now have a nice Samsung Galaxy S 3. If you need anything - I think you can PM me. P.S. I ran both Virtuous Inquisition ROM as well as Wajee's 1.5 and they were ok - Wajee was a bit better.
Thanks for that. S-OFF seems scary for many, and I'm sure a lot of people got stuck on the whole juopunutbear splash screen (including myself on my 1st attempt S-OFF!)
re:
hey thanks SO much i was asking a member here for help on that! the vivid has been the only phn ive had trouble with at all!!!!!!!!!! im gonna try the fix now illl post results when i can! i was stuck on the screen with the phn and the light shinning on it!
re:
xreyx said:
hey thanks SO much i was asking a member here for help on that! the vivid has been the only phn ive had trouble with at all!!!!!!!!!! im gonna try the fix now illl post results when i can! i was stuck on the screen with the phn and the light shinning on it!
Click to expand...
Click to collapse
hey Zlatko1983 idk if im missing something or what, but i have downloaded the needed ruu for the vivid (it only has cingular an i have att phn) but the ruu says that there is an error and it doesnt upgrade the rom. i get a error screen and the option to retry. any suggestions???? THANK!
What kind of an error screen? Was your phone in Fasboot USB?
Sent from my SGH-I747M using xda app-developers app
Zlatko1983 said:
What kind of an error screen? Was your phone in Fasboot USB?
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
well the htc soft ware said error, i dont recall the error code #, i did have it in fastboot usb, also after it failed, i unplugged the data cable and on the fastboot usb menu it said(i think)
security "something" fail
and
rom"something" fail (in red letters)
im super lost and im doing everything as you mentioned. also once i reboot, the phn just boots into that flash light and phn. if its ok i would like to record a shot vid of what my phn does and send it to you, because when im in the fastboot usb menu the phn starts running some cheks and stuff on its own and THEN it lets me choose what i want to do(reboot, fastboot, etc.)
thank you so much for your help!!!!!!!
Hey Guys,
After installing CM on my Xperia Z and trying to get back into recovery I noticed that I was always getting a picture of a dead green android guy with a red triangular sign with an exclamation mark on it.
I have read that there might be the possibility of having to use a certain combination to get into recovery - but I wasn't able to find it on Google.
Any experiences here? You guys know the answer?
lampen12 said:
Hey Guys,
After installing CM on my Xperia Z and trying to get back into recovery I noticed that I was always getting a picture of a dead green android guy with a red triangular sign with an exclamation mark on it.
I have read that there might be the possibility of having to use a certain combination to get into recovery - but I wasn't able to find it on Google.
Any experiences here? You guys know the answer?
Click to expand...
Click to collapse
Try to re install the recovery