Develop Bugs

[FIXED]bricked slcd on htc black screen - need urgent help :(

I ran a ruu update to restore my SLCD device to stock without knowing wether it is compatible or not.and hence I need to create a goldcard without knowing that too.
I just got it a few days ago with a leedroid rom. then used a cm7 rom.
everything was ok.
now after trying the ruu
I just get a white HTC logo with black backgrounf and 4 exclamation marks on every edge of the screen.
when I unplug my usb I shows the hboot screen with the ruu option only.
PLEASE I BEG YOU ANYONE?I NEED HELP
searched everywhere. everyone suggests creating a goldcard but I cant cause my phone is stuck on a black screen white a white HTC logo plus exclamation marks.
note: its a used SLCD desire I think cause it has white bleeding on the edge of the screens.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pc detects fastboot. no manual access to fast and hboot.
hboot appers when unplugging the usb
its
cm7r2 (on top)
bravo PVT3 SHIP S-OFF
HBOOT-6.93.1002
MI CROP-051d
TOUCH PANEL-SYNT0101
RADIO-4.08.00.09
Aug 10 2010, 17:52:18
ruu
ran RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed.exe
and also tried RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed and even the asian one
hope this helps
please someone pls help me asap thankyou

anyone?

The "Screen of Death" for the HTC is something rare and in most cases hard to recover, but you can still try some things:
1) Do you have guarantee for it. If you do you are cleared from the first. Go with your phone to them an tell them you tried to apply an OTA and this is the result. Since you ran the RUU you don't have ROOT or S-OFF anymore so you are clean.
2) Can you go in HBOOT. If yes follow this thread (http://forum.xda-developers.com/showthread.php?t=880268 , 2nd post) on how to get the PB99IMG from the RUU and try flashing it from SDCARD in hboot.
I will still dig on your problem, maybe find something, but I think you wrote on a bad part of the phone and it wasn't written well.
EDIT: You don't have to create the gold card in your phone, since the gold card is unique by SDCard and not by phone. So find someone with a phone and create it using their phone and then u can use it.

I see.
I still have S=off after trying the RUU and went to error at the end when I unplug my usb cable I can see hboot.
saying the info on the first post.
but it says something with partition error
edit: when the phone is off. its normal because I can charge it using a charger or via pc.
when pressing power it doesnt vibrate.
It turns on then black background with a big white HTC logo at the center.
4 traingles with exclamation marks at the four corners of the screen
edit:it completely powers on!
my only problem now is I dont have hboot screen so evrytime my phone reboots or shuts down.
I have to connect it to pc and use fastboot :/
will alpharev tool fix this?

managed to go to cwm recovery using the command fastboot oem boot
it boots but now on boot loop :/
after unplugging my battery then turning it on it goes back to black screen with the four exclamation marks on it
sigh

Well if you managed to go to hboot, does it say that it is trying to load PB99IMG.zip from card, or you don't have your sd card mounted?
You need to run the PB99 directly from hboot not from CWM.
Did you flashed another hboot for the ROM? Another Radio for the ROM?
Try to extract the PB99IMG from the latest WWE 2.29.405.5 and run it from boot, and also make a GoldCard and put it in the phone when running it.
Did you get some kind of error number?
We have to take it step by step and try everything and maybe fix it.
If you need to mound SD Card try this: http://forum.xda-developers.com/showthread.php?t=531310 , maybe it can help you.
LEDIT: To create a goldcard see this: http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
LLEDIT: Also you should read this thread's from the beginning till end. Even though they are for bricked display, you can follow them and it is all very well explained.
1)http://forum.xda-developers.com/showthread.php?t=880268
2)http://forum.xda-developers.com/showthread.php?t=831734

many Thanks man! managed to create a goldcard.
then got saw this post http://forum.xda-developers.com/showthread.php?t=768256
got almost everything sorted out but one thing isnt right
while flashing via hboot. no error numbers. hboot says partitioning error
everything says OK except for system - fail PU
but my device is still rooted,still have S-OFF still have cm7r2 hboot and has the modified 6.93 HBOOT
THANKS for helping me here bro!

gonemad02 said:
many Thanks man! managed to create a goldcard.
then got saw this post http://forum.xda-developers.com/showthread.php?t=768256
got almost everything sorted out but one thing isnt right
while flashing via hboot. no error numbers. hboot says partitioning error
everything says OK except for system - fail PU
but my device is still rooted,still have S-OFF still have cm7r2 hboot and has the modified 6.93 HBOOT
THANKS for helping me here bro!
Click to expand...
Click to collapse
Well if this is what the RUU says then I'm afraid you can't install it since you changed the partitions of the NAND with the custom HBOOT. Maybe trying to flash the stock HBOOT will get you fixed.
I'm not too sure if the custom HBOOT could stop you from installing the RUU but from what you tell this could be the only reason.
Since you still have ROOT and S-OFF you should be able to flash it either by fastboot or by CWM.
After you install the stock HBOOT try to reload the RUU from SD.
EDIT: I dig around a little more on your problem and as jordan.harris01 said you need to downgrade your hboot or to flash the stock HBOOT. The stock HBOOT can be found on AlphaRev homepage.

All of the r2 Hboots prevent the RUU from over-writing it! You need to download the "downgrader" hboot, flash that Hboot and then you'll be able to flash your RUU without problem.

managed to fix my problem thanks guys!
both of you really helped
thanks jordan harris
and to you especially UsManyDead

gonemad02 said:
managed to fix my problem thanks guys!
both of you really helped
thanks jordan harris
and to you especially UsManyDead
Click to expand...
Click to collapse
i have exactly the same problem!
that is: i can see the same information when i unplug my phone, bootloops and exclamation marks.
do you still remember how you fixed this?

ruudislang said:
i have exactly the same problem!
that is: i can see the same information when i unplug my phone, bootloops and exclamation marks.
do you still remember how you fixed this?
Click to expand...
Click to collapse
bortak's troubleshooting guide in my sig
Sent from my HTC Desire

[Q] Crashing on Bootloader / Display Tear

OK so I've looked through the forum (admittedly the Galaxy Nexus specific one only) and tried some searches but may not be able to articulate this problem in clear way. Basically, I'm continuously crashing - started with a stock, but unlocked/rooted install. Now it won't boot and crashes in the boot loader as well after a few seconds (thus not allowing any non-trivial actions to actually complete.)
The first crash was after enabling face unlock for the first time. When I hit the power button to shut things off, the display "tore" and then went totally dark. Phone was completely unresponsive till I pulled the battery for a few minutes (found that one from search.) Couldn't complete a boot sequence though - would go to the animation, then display would go wonky and then shut down. Would usually have to pull battery again to get any response from that.
Went to recovery mode and wiped data - which completed - same problem on boot. Only thing I'd done was unlock and root (for eventual root apps, none of which had been run) so decided to undo that (using "Galaxy Nexus Root Toolkit 1.3.") On the factory restore there are several steps (boot loader, radio, etc.) and I haven't been able to complete that process.
I suspect it might even be bad hardware at this point, but can't go back to VZW with the phone still showing unlocked. Phone is a recent eBay purchase to replace a lost device but seemed fine for the 2-3 days I used before this all started.
Anyone seen something like this before?

So your able to get into recovery still? If it doesn't boot into the os it's probably a compatibility error between the kernel and rom your using (Just clearning data in recovery won't fix this).
So what rom/kernel combination were you using at the time?
Also have you tried flashing a completely different custom rom to the one your having issues with.
And any nandroid backups you have made in the past?

What's weird is that I was in stock kernel / rom at the time. (At least I'm nearly sure - it did come from eBay after all...)
I'll also try changing the ROM, that could be it. The big question is if that can complete before the thing melts. If I boot to recovery and wait, doing nothing, the system crashes in a minute or two.
My current thinking is that I might have a bad recovery / clockwork mod install.

can you still get to the bootloader and is it stable to sit on the bootloader?

I can get to the boot loader but it is not stable there (I think I was conflating the two.)

does your bootloader look like this? i want to make sure you and i are talking about the same thing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yep, that's the one (before it crashes. I have a pic of the amusing video display when it does that I'll put up when I hit the magic 8 posts...)

try using ODIN to restore your phone. instructions are found here: http://forum.xda-developers.com/showthread.php?t=1394051
also, how long can you sit on the bootloader before it crashes?

I'll try that as tonight - thanks!
Varies on time to crash, but no less than 30 seconds and no more than 5 minutes so far. Requires a battery pull and wait to come back after that.

i would like to see the picture of the crash you are talking about.
also, you can relock the bootloader real fast before you take it to VZW. only takes 1 command once you get to the bootloader
fastboot oem lock

Wow, same crash while in download mode. That can't be good...

yeah thats not good at all. i'd lock the bootloader and return it

http://dulinor.smugmug.com/photos/i-XkKWCrg/0/S/i-XkKWCrg-S.jpg
This is the crash I'm seeing

Yeah return to the store and show them this, the board is probably bad.

thats rough, but since you got it on ebay returning it may be a hassle and if the phone is not a north american model samsung might not even accept it for warranty.
did you try to flash the stock google image using fastboot instead of using the toolkit? it will only take a few mins. when you display crash like that does it still take commands from fastboot? you can test it when the display crash like that type in fastboot devices and see if you get the id number in command prompt. if your build was yakju then you can get the factory images from here http://code.google.com/android/nexus/images.html

Just got back from the store - they issued a replacement, none on hand so one should ship out today. (Thanks for the tip on re-locking it - not sure if they checked, but was happier having that.)
So of course, it actually completed booting (for the first time) but crashed during activation. Once they saw it crash on the Odin screen, they were happy to do the swap.
I had been trying to re-flash OEM Google - which it should have been all along.
Thanks everybody for your help.

What is this screen, and how do I stop this from happening?

I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jmattp said:
I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
Click to expand...
Click to collapse
Its the stock Recovery screen. I would just do a fresh install using Odin
Sent from my Galaxy Nexus using XDA

That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.

jmattp said:
That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.
Click to expand...
Click to collapse
If you can get into fastboot and recovery then you don't have any serious problems.
Sent from my Galaxy Nexus using XDA

Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)

jmattp said:
Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)
Click to expand...
Click to collapse
It must've been something else, I've had the battery die a few times, its booted up fine. Glad you fixed it.
Sent from my Galaxy Nexus using XDA

Oh dear..we have a brick.

So my S3 is stuck in a loop where it wont get past the samsung logo. I can still access safe mode and dl mode fine. Odin still sees my phone and I've been trying to flash it back to stock with no luck. Odin keep getting stuck at 2/5 of the progress bar on <ID:0/004> system.img.ext4. I've also tried my sd card but it can't seem to mount it.
So what are my options ? Can someone please help me out.
EDIT: I can mount my SD card now, put two zips on it tried one so far but it still seems to be unable to boot off of it. I'll wait a few minutes to see what happens.

Change wire. Same thing happen to me before. I change my wire for odin and it worked.

Are you 100% sure thats the problem ? It could make sense since I don't have the factory stock one anymore. But its a good quality cable.

Yep. Some wires do not have data or charging capabilities. Best to use stock cable or even go to a TMo store and get one of their Universal Cables (I've heard good things about those tbh).
Also try plugging into a USB port closest to the motherboard. Ones that are further away from the power source sometimes don't work as well.
One last thing, the system.img generally takes a fair amount of time to run. I've had the whole stock Odin flash take up to 10 minutes before. So you might think that it is getting stuck but it may still be writing to the partitions.

I still haven't been able to fix it because I haven't gotten a hold of a stock cable yet but I was wondering. If I could transfer music, flash a rom, etc. Doesnt that mean my cable is fine ? I just have a hard time believing it would be the cable.
My phone is still able to boot up with CWM or stock safe mode and I can still access dl mode. I might have to go exchange my phone but I'll have to get lucky for the person not to check the flash count. Not only that but I really don't feel like buying another one.
If someone can link me to the stock rom for the 999v(videotron) it'd help out quite a lot. SO far I've tried two stock ones and it always hangs whenn odin reaches <ID:0/004> system.img.ext4...

You're probably just flashing the wrong firmware in Odin. Here is a link for the Videotron firmware. After you download, extract the .zip and put the .tar file in the PDA field in Odin.
http://www.hotfile.com/dl/184265810/b6b383c/T999VVLDLL1_T999VYVLDLL1_VTR.zip.html

Alright I just started DL it. I'm pretty sure I already tried a file named exactly like this though. It's going to take 50 minutes to download but once it's done and I've tried it with odin I'll post the results. Just to be 100% sure, I just check the F. reset time and auto reboot boxes right ?
Edit: I'm installing it right now, it seems to get stuck at the same place as usual.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Perhaps this link will help move you along.
http://forum.xda-developers.com/showpost.php?p=30386309&postcount=1
Remember, as the author says don't use the provided link files if your phone is not a Verizon galaxy s3. Find your phone model's needed files.
Sent from my SGH-T999 using Tapatalk 2

THANK YOU! I think this should do the trick. I will come back to you guys with the results!
edit: When I try to flash it, it says :secure check fail: aboot If it isn't the right version, than where can I get the files for mine. It's pretty hard to find the right files for me.

So does anyone know why it would hang like this ?

How long have you waited?

Check the box : Nand erase all. Might help to clean install that tar file.

after you have installed the stock rom and also make sure you root it then just wipe factory reset and also cache it should be fine.

Can't enter bootloader

Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.

Ok so basically what he is saying is that his phone does NOT even have recovery mode. Where we get the dead android guy he gets this and is thus unable to flash his phone with new recovery or system.
That happened to a friend of mine a long time ago but he threw away his phone ( sold it for cheap ) without trying much.
Are there any ACTUAL solutions ?
Again Power + vol up keys DO NOT bring up recovery mode/fastboot or however you want to call it.

Anyone ?

yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there

debully said:
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
Click to expand...
Click to collapse
"moorefied" ?? Can you explain ?

xRanker said:
"moorefied" ?? Can you explain ?
Click to expand...
Click to collapse
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.

debully said:
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
Click to expand...
Click to collapse
That is mostly because people touch where they are not supposed to ^^
But um thanks for reply.

With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.

debully said:
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
Click to expand...
Click to collapse
Not so sure of that, I really think its more user error than anything else, especially when it comes to fastboot. Copy and paste isn't your friend and it seems most people overwrite their boot or fastboot partitions with system files because they use the same command but change the img file name.
Have never had an unrecoverable brick, and those soft bricks I've had were my fault by not reading properly or skipping through steps quickly.

XepouH said:
Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Click to expand...
Click to collapse
Find your answer here