Hey..thought maybe someone knows..Ok when 2.1 update came out i was easily able to change the bootscreen by replacing the bootanimation,zip file. I had a problem with battery charging so i decided to do a repair which fixed the problem but when i tryed to replace the boot screen it wont use the zip file i put in it uses a screen says android kinda greenish grey and flashing. Anyone else have this prob? Is there a way to replace the boot screen now or did they Patch it?
elvish said:
Hey..thought maybe someone knows..Ok when 2.1 update came out i was easily able to change the bootscreen by replacing the bootanimation,zip file. I had a problem with battery charging so i decided to do a repair which fixed the problem but when i tryed to replace the boot screen it wont use the zip file i put in it uses a screen says android kinda greenish grey and flashing. Anyone else have this prob? Is there a way to replace the boot screen now or did they Patch it?
Click to expand...
Click to collapse
Try one of these - http://forum.xda-developers.com/showthread.php?t=748145&page=14
Related
PLZ HELP ME !!WAT EVER I RESET OR HARD RESET THE MAIN O2 SCREEN CAN SEE AFTER THAT IT WAS WHITE COLOUR SCREEN ONLI ???
I have a similar situation here. Since Nov 18th, my Xda II refused to boot.
The display gets stuck at the boot screen, with no backlight and no radio LED on.
Today I managed to cold boot it to the "USB Serial 1.2" screen and WinXP managed to detect the USB device, thus I went on and flash the ROM via the PC. The ROM flashing process completed, but as I reset the device to continue, it was the same screen again. It won't proceed and always get stuck at the boot screen.
I wonder if this is really a hardware problem? It has barely just turned 2 years old!
I wonder if the screen's backlight & radio/charge LED are activated & controlled by the OS (WM2003SE)? And if I managed to flash the ROM, does it mean the ROM chip is still functioning? And could it be I have a faulty RAM that caused this?
The service centre wanted to slap me a bill of RM1,560 (approx US$410) to change the mainboard. Now I am in a dilemma whether to repair or to get a new device (Xda Exec, Universal or even Atom). But of course, first priority would be to try to salvage this Xda II.
my problem fix ready !!now my XDA11 is working fine !!the solution is to re-run the nbk or radio rom file !!!download the step 1 to fix yr problem !!here is the post link :
http://forum.xda-developers.com/download.php?id=2857
fuchai said:
my problem fix ready !!now my XDA11 is working fine !!the solution is to re-run the nbk or radio rom file !!!download the step 1 to fix yr problem !!here is the post link :
http://forum.xda-developers.com/download.php?id=2857
Click to expand...
Click to collapse
it means upgrade the solution for white screen, or what...
pls help
My Friend has a HTC Wildfire, he's on a tour with his friends
Problem starts now , He was talking with his friend and suddenly screen went blank. He's using VillianROM on it now when he switches on he can't see the screen at all, but phone it self works when someone calls he's still able to answers it. he cant flash new ROM Also. he can't see screen so
Any Help ? anyone had such kind of a problem with HTC ?
maheshpatel said:
He was talking with his friend and suddenly screen went blank. He's using VillianROM on it now when he switches on he can't see the screen at all, but phone it self works when someone calls he's still able to answers it.
Click to expand...
Click to collapse
This is certainly not related to VillianROM in any way.
I think it's a hardware problem - there's something wrong with display panel. If the backlight is dead you should barely see very dark image on the screen in bright lightning conditions.
Anyway, looks like there's nothing you nor your friend can do to fix it. You need to send it to service.
maheshpatel said:
he cant flash new ROM Also. he can't see screen so
Click to expand...
Click to collapse
If the phone has USB debugging enabled by accident (I guess it's hard to turn it on blindly) then you can access it using adb shell. If you have custom recovery image installed, such as Clocwork or Amon_RA, you can boot to it and fave full access to your phone through USB using adb (or fastboot) so you can flash new ROM images.
oyah said:
If you have custom recovery image installed, such as Clocwork or Amon_RA, you can boot to it and fave full access to your phone through USB using adb (or fastboot) so you can flash new ROM images.
Click to expand...
Click to collapse
Yes, what he said ^^.
I'll just add one more thing. To get to custom recovery easily, pull the battery out and put it back in again. Then perform what ever key combination to boot custom recovery.
Good luck to your friend!
You might also have more luck posting in the Wildfire sections where they me able to help. It does seem like a Hardware issue with the screen to me? Was it dropped or anything?
It seems like hardware. Probably connection between screen and PCB.
ya his phone dropped many times, ya it seems like hardware issue to me also..
hey. i went to take my evo off the charging dock and then went to wake up the screen and when i do the whole screen is in rainbow, snow pixel. like all i can see normal is the status bar. i can boot and reboot, boot into recovery ( but cant see anything except the very first line on the top of the screen) but the screen is just messed up. it looks like one of this old tv's that when they loose connection they get white and black snow except mine is colored snow.
any ideas?
thanks
Shotgun4 said:
hey. i went to take my evo off the charging dock and then went to wake up the screen and when i do the whole screen is in rainbow, snow pixel. like all i can see normal is the status bar. i can boot and reboot, boot into recovery ( but cant see anything except the very first line on the top of the screen) but the screen is just messed up. it looks like one of this old tv's that when they loose connection they get white and black snow except mine is colored snow.
any ideas?
thanks
Click to expand...
Click to collapse
I would imagine LCD failure, though I can't be quite sure. Could you include a picture of it?
Shotgun4 said:
hey. i went to take my evo off the charging dock and then went to wake up the screen and when i do the whole screen is in rainbow, snow pixel. like all i can see normal is the status bar. i can boot and reboot, boot into recovery ( but cant see anything except the very first line on the top of the screen) but the screen is just messed up. it looks like one of this old tv's that when they loose connection they get white and black snow except mine is colored snow.
any ideas?
thanks
Click to expand...
Click to collapse
The same problem with my GSM Evo 3d:/
What ROM, Radio, kernel are you using? LeeDroid V5.3 and LeeDroid V4.2.1-1.94GHz-KERNEL, radio - 10.59.9020.00_10.15.9020.06 in my case
http://img515.imageshack.us/img515/543/img20120225140835.jpg
I noticed that when I removed battery and tried to boot, in the beginning screen was black and then was LeeDroid's boot-sound and when phone is supposed to ask for my PIN code the rainbow-pixel screen appears.
Could anyone make step by step instruction how to reflash ROM? I cannot see anything so I need all information (like push vol down two times). I hope it might works
Akasa Fox said:
I would imagine LCD failure, though I can't be quite sure. Could you include a picture of it?
Click to expand...
Click to collapse
really... LCD Failure... how would i fix that... here are some pics. I am running this rom http://forum.xda-developers.com/showthread.php?t=1456793 on version 1.3.
so i will post pics, and do you think rogers would be able to fix this problem or would it cost a hell of alot of money?
I'm not convinced that it's LCD failure. LCD is working (in a strange way) and in my case touch is working as well. In my opinion it might be motherboard (or anything that controls LCD). I'm going to try changing radio, rom and kernel - maybe it will work. But I really need your help with the step by step guide I mentioned in my previous post.
ok, so what are you going to try and do, are you going to try and reflash a rom?
like i can try and give you instructions, but i need to know what you want to do.
EDIT: I have downloaded and tried to run the RUU for My rogers htc evo. it is installing the rom, stock radio, and what not. so when it is done i will update and post back if that worked or not.
UPDATE: Installing the new RUU did not work, the screen is still messed up im guessing its a hardware failure. im going to try to bring it into rogers and see if they will do anything to help me out.
Something new, now my screen is completely black (but i can hear that touchscreen and touch buttons are working).
@Shotgun4 - please let me know what you'll find out.
misiolin said:
@Shotgun4 - please let me know what you'll find out.
Click to expand...
Click to collapse
I Will do That.
Shotgun4 said:
I Will do That.
Click to expand...
Click to collapse
Thanks mate
My screen is once more pixelful
I don't want to start new topic so I'll ask here:
Could anyone please help me with going back to stock rom?
My LCD is still not functional so it'll be unusual guide.
1. I open cmd and run adb reboot bootloader command (with stock rom in PG86IMG.zip file)
2. Does phone starts in fastboot or bootloader? If fatboot I need to press power button right?
3. Now phone should check for PG86IMG.zip file, what should I press to accept flash?
4. Now few minutes for flash
5. And what button should I press to reboot?
Is there any easier way to flash stock rom without working LCD? with adb commands maybe? please help me guys
misiolin said:
I don't want to start new topic so I'll ask here:
Could anyone please help me with going back to stock rom?
My LCD is still not functional so it'll be unusual guide.
1. I open cmd and run adb reboot bootloader command (with stock rom in PG86IMG.zip file)
2. Does phone starts in fastboot or bootloader? If fatboot I need to press power button right?
3. Now phone should check for PG86IMG.zip file, what should I press to accept flash?
4. Now few minutes for flash
5. And what button should I press to reboot?
Is there any easier way to flash stock rom without working LCD? with adb commands maybe? please help me guys
Click to expand...
Click to collapse
Your in diagnostic mode. Hold down the power button for 45 seconds then press the camera button twice it should reset the phone.
Diagnostic Mode, never herd about it. I tried both with phone on and off, no luck :/. Anyone has idea what it might be? (I'll post picture once more http://img515.imageshack.us/img515/543/img20120225140835.jpg)
PS
I managed to reinstall my shipped ROM, but screen is still f*cked up ;(.
Guys I have a problem. Is there any way to switch on USB debugging without working screen? I need to s-on my phone and I cannot use adb without USB debugging. My touch screen and touch buttons are working though so maybe someone could make screenshots how to switch it on? I'm on stock ROM now.
Or maybe there is other method to use step 5 of this tutorial without USB Debugging?
And one more question, If my phone doesn't connect with computer in bootloader/fastboot, does it means that I have s-on?
I have noticed that I can no longer bill directly to my AT&T account with this phone, so I thought I'd try to modify my build.prop file to make it appear as a Galaxy Nexus and see if that would fix my issue. I copied the /system/build.prop file, edited the three lines that are the device fingerprints, pasted it back, and now my device just has a black screen with the backlight on and the soft keys are blinking. If I cold-boot it I can still get to Hboot/recovery so I know I'm not stuck. I'm just confused as why a build.prop would cause it to be stuck like that. Anyone have any ideas?
K.AuthoR said:
I have noticed that I can no longer bill directly to my AT&T account with this phone, so I thought I'd try to modify my build.prop file to make it appear as a Galaxy Nexus and see if that would fix my issue. I copied the /system/build.prop file, edited the three lines that are the device fingerprints, pasted it back, and now my device just has a black screen with the backlight on and the soft keys are blinking. If I cold-boot it I can still get to Hboot/recovery so I know I'm not stuck. I'm just confused as why a build.prop would cause it to be stuck like that. Anyone have any ideas?
Click to expand...
Click to collapse
The build prop is essential to the device's functionality. It should be well known that an improper edit could cause issues, which is why I always make a backup before editing this file.
You can use adb to pull the build.prop file and fix the issue. Or get the original build prop from your rom zip and use adb to push the file to the device.
You could also create a flashable zip that flashes a new build prop only. I'm not super familiar with adb, so this is what I'd probably do. Though, I'm sure you've figured it out by now.
K.AuthoR said:
I have noticed that I can no longer bill directly to my AT&T account with this phone, so I thought I'd try to modify my build.prop file to make it appear as a Galaxy Nexus and see if that would fix my issue. I copied the /system/build.prop file, edited the three lines that are the device fingerprints, pasted it back, and now my device just has a black screen with the backlight on and the soft keys are blinking. If I cold-boot it I can still get to Hboot/recovery so I know I'm not stuck. I'm just confused as why a build.prop would cause it to be stuck like that. Anyone have any ideas?
Click to expand...
Click to collapse
Did you make sure to set permissions back to what they're supposed to be? I edited build.prop once and didn't set permissions correctly and it failed to boot.
Also best to get a build.prop based on the AT&T version and add the lines necessary to your current build.prop rather than copy pasting a build.prop from another phone.
There's a zip file with a stock AT&T build prop in the development forum in the updated radio image thread.
http://forum.xda-developers.com/showthread.php?p=44260480
Sent from my HTC One using xda app-developers app
Simba501 said:
The build prop is essential to the device's functionality. It should be well known that an improper edit could cause issues, which is why I always make a backup before editing this file.
You can use adb to pull the build.prop file and fix the issue. Or get the original build prop from your rom zip and use adb to push the file to the device.
You could also create a flashable zip that flashes a new build prop only. I'm not super familiar with adb, so this is what I'd probably do. Though, I'm sure you've figured it out by now.
Click to expand...
Click to collapse
will this work even tho i cant boot ???
themainlad said:
will this work even tho i cant boot ???
Click to expand...
Click to collapse
Most of the time you can get into recovery, even if you can't boot into the ROM. You'll have to use the hardware shortcut to get into recovery. Long-press the power button until it stops blinking. Then, release the power button and immediately press/hold volume down. This will bring you to the bootloader; from there, you can get into recovery.
So, you have some options. Do you have a copy of the ROM zip on the device?
Sent from my Nexus 7
Simba501 said:
Most of the time you can get into recovery, even if you can't boot into the ROM. You'll have to use the hardware shortcut to get into recovery. Long-press the power button until it stops blinking. Then, release the power button and immediately press/hold volume down. This will bring you to the bootloader; from there, you can get into recovery.
So, you have some options. Do you have a copy of the ROM zip on the device?
Sent from my Nexus 7
Click to expand...
Click to collapse
what blinking ? i have no rom ! due to the lack of compatibility on sony xpira m
themainlad said:
what blinking ? i have no rom ! due to the lack of compatibility on sony xpira m
Click to expand...
Click to collapse
I assumed you were using an HTC One. I know absolutely nothing about that device; you'll have to ask in that section.
green light
Simba501 said:
Most of the time you can get into recovery, even if you can't boot into the ROM. You'll have to use the hardware shortcut to get into recovery. Long-press the power button until it stops blinking. Then, release the power button and immediately press/hold volume down. This will bring you to the bootloader; from there, you can get into recovery.
So, you have some options. Do you have a copy of the ROM zip on the device?
Sent from my Nexus 7
Click to expand...
Click to collapse
when i try to enter recovery notification light turns green but no screen
Hi all,
i tried to bypass PIE with the bypasspie.zip file i flashed it using rom installer to boot and recovery. I don't have recovery on my Sony Xperia Z2 and now the battery seems to be empty after reboot. I am currently charging and the LED shows a blinking red light. Does anybody know what i should do or should i wait till (maybe) the battery is full and was the cause of it? By the way, i am very sure that ill have to wait 3 hours like mentioned by other people who share their problem with the red light blinking, i was just going to ask because i got 3 hours to wait
Chris
automatischa said:
Hi all,
i tried to bypass PIE with the bypasspie.zip file i flashed it using rom installer to boot and recovery. I don't have recovery on my Sony Xperia Z2 and now the battery seems to be empty after reboot. I am currently charging and the LED shows a blinking red light. Does anybody know what i should do or should i wait till (maybe) the battery is full and was the cause of it? By the way, i am very sure that ill have to wait 3 hours like mentioned by other people who share their problem with the red light blinking, i was just going to ask because i got 3 hours to wait
Chris
Click to expand...
Click to collapse
Always make backup of the rom, or just backup file which will be changed after flash.
in this case linker file from /system/bin
Paget96 said:
Always make backup of the rom, or just backup file which will be changed after flash.
in this case linker file from /system/bin
Click to expand...
Click to collapse
Yes i know but i was too new to android. I am not familiar with the filesystem yet. I hope the phone will atleast boot so i can fix things if the OS is broken.
automatischa said:
Yes i know but i was too new to android. I am not familiar with the filesystem yet. I hope the phone will atleast boot so i can fix things if the OS is broken.
Click to expand...
Click to collapse
just to know bypass pie can cause bootloop and losing root
Yesss
i was able to recover android using the repair function of sony pc companion