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
Related
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 just added the line for faster uploading on HSUPA like I did with GB, but now after restarting my phone only show the Samsung logo then goes black. I did get it to go into Download mode once (volume down+power) but for some reason I cant get it into there again.
Any help on getting into CWM recovery would be appreciated.
Google 'galaxy note cwm button combo' or something similar and use the button combo you get told. If you can get into download mode again I would recommend a flash through Odin. Its probably because ICS didn't suport the tweak
Sent from my GT-I5800 using XDA
Press and hold volume down while powering on
Thur u arrrrrrgh
From What I have found out by tinkering, there are certain things you could do to tweak GB that ICS just does not like. They have changed memory management features around that's for sure. I've tried several things each either had no effect, or negative effects on ICS but *knock on wood* I have yet to make my phone unable to boot yet. I don't put it past myself though. I tinker A LOT!
Smonic said:
Google 'galaxy note cwm button combo' or something similar and use the button combo you get told. If you can get into download mode again I would recommend a flash through Odin. Its probably because ICS didn't suport the tweak
Sent from my GT-I5800 using XDA
Click to expand...
Click to collapse
(CWM) I got it, On the i717 it's hold volume up + power until Samsung appears.
I was aware that down+power puts it into Download mode, but I didn't want to use Odin if I didn't have it.
I found that the international version which is N7000(I think) you hold different buttons, thats what was confusing me.
Was able to get into CWM and restored. Note do not tweak build.prop variables between 2 different Android builds
Edit: Also wanted to reiterate that you MUST keep holding the buttons until the Samsung screen shows up and don't let go even though it vibrates... keep them down until you see Samsung.
ZPaul2Fresh8 said:
I just added the line for faster uploading on HSUPA like I did with GB, but now after restarting my phone only show the Samsung logo then goes black.
Any help on getting into CWM recovery would be appreciated.
Click to expand...
Click to collapse
I had this problem after tweaking the build.prop also. After I re-flashed and was back up and running, I tried again. This time I noticed that the permissions on the build.prop were set to rw-rw-rw- After making the modifications to the build.prop and changing the permissions to rw-r--r-- it worked fine without sticking after reboot.
Hope this helps.
riprod said:
I had this problem after tweaking the build.prop also. After I re-flashed and was back up and running, I tried again. This time I noticed that the permissions on the build.prop were set to rw-rw-rw- After making the modifications to the build.prop and changing the permissions to rw-r--r-- it worked fine without sticking after reboot.
Hope this helps.
Click to expand...
Click to collapse
This was driving me nuts. Great tip. It worked for me.
Glad I could help!
Sent from my SAMSUNG-SGH-I717 using XDA
Wish I knew about those permissions earlier. I spent a few hours last night trying to do the tweaks and I kept getting stuck. What worked for me was using ROM Toolbox from the play store, then using the build.prop editor. oh well...you leave you learn
So yeah as the title states my internal screen is completely scattered, I can't use touch anymore nor see anything. But when my device is turned on and I connect it via Usb to my PC I hear the Usb connection sound. My Device is rooted and I think the debug mode is unfortunately deactivated.
Is there any way I can recover my Music and Pictures? Maybe through recovery mode? Or just a programm that bypasses the lockscreen?
I tried a lot hope someone can help me!
Thanks in advance!
-Removed for Personal Information-
Is there no way?
You should be able to use ADB to copy your stuff from your phone to your PC, and you won't need to guess what's on the phone's screen while you're doing it. Lots of tutorials on how to use it on here/elsewhere (search).
MistahBungle said:
You should be able to use ADB to copy your stuff from your phone to your PC, and you won't need to guess what's on the phone's screen while you're doing it. Lots of tutorials on how to use it on here/elsewhere (search).
Click to expand...
Click to collapse
I searched about 2 hours for solutions. The problem is usb debug mode isn't activated on my phone so ADB doesn't recognize my device..
You're pretty much boned then & you're going to have to guess where you are in recovery (if you're someone who flashes roms & messes around with your phone I can't see why you wouldn't have USB debugging on by default).
No easy fixes. Unless you want to wait until you've replaced the screen.
Edit - What buttons you need to press to get to where you need to be in recovery in order to mount the card will depend on what version of recovery you have given many kernel builders modify it. Find someone using the same kernel as you & ask them to help you navigate your way thru.
MistahBungle said:
You're pretty much boned then & you're going to have to guess where you are in recovery (if you're someone who flashes roms & messes around with your phone I can't see why you wouldn't have USB debugging on by default).
No easy fixes. Unless you want to wait until you've replaced the screen.
Edit - What buttons you need to press to get to where you need to be in recovery in order to mount the card will depend on what version of recovery you have given many kernel builders modify it. Find someone using the same kernel as you & ask them to help you navigate your way thru.
Click to expand...
Click to collapse
It was a fresh install of RR and so it wasn't activated at the night I destroyed it. Bad Luck I guess ^^ The problem is I won't replace the screen because I got a Galaxy Nexus for the same amount of money the new screen would cost..
So the buttons are not the same in every RR recovery?
Depending on which version of CWRecovery the kernel has/how (if) the kernel dev has modified it will determine how many button presses & how you have to go up/down through menus.
Post in the RR discussion thread & ask someone to walk you through as I suggested yesterday.
Yeah I understand what you mean about the cost to replace the screen Vs cost of a new phone.
Vicious_Colours said:
It was a fresh install of RR and so it wasn't activated at the night I destroyed it. Bad Luck I guess ^^ The problem is I won't replace the screen because I got a Galaxy Nexus for the same amount of money the new screen would cost..
So the buttons are not the same in every RR recovery?
Click to expand...
Click to collapse
In a little bit of a panic. I replaced the build.prop on my phone with one of the defaults I found here (for p769v20d) and now my phone won't start up. I just see the LG logo and the screen stays black. I tried doing a hard reset and the little open android shows up, but it then goes black as well. I have root but removed cwm to install the update. My bootloader is locked. Is there anyway to fix this?
applecityfoxes said:
In a little bit of a panic. I replaced the build.prop on my phone with one of the defaults I found here (for p769v20d) and now my phone won't start up. I just see the LG logo and the screen stays black. I tried doing a hard reset and the little open android shows up, but it then goes black as well. I have root but removed cwm to install the update. My bootloader is locked. Is there anyway to fix this?
Click to expand...
Click to collapse
Sounds like you'll need to do an offline flash http://forum.xda-developers.com/showthread.php?p=38677123.
applecityfoxes said:
In a little bit of a panic. I replaced the build.prop on my phone with one of the defaults I found here (for p769v20d) and now my phone won't start up. I just see the LG logo and the screen stays black. I tried doing a hard reset and the little open android shows up, but it then goes black as well. I have root but removed cwm to install the update. My bootloader is locked. Is there anyway to fix this?
Click to expand...
Click to collapse
Do you still get adb connection? How about taking your original build.prop (or from your original kdz) and:
adb push build.prop > /system
? Should work fine I guess
Sent from my LG-P760 using xda app-developers app
N00BY0815 said:
adb push build.prop > /system
Click to expand...
Click to collapse
A great option. I reflash the phone.
applecityfoxes said:
In a little bit of a panic. I replaced the build.prop on my phone with one of the defaults I found here (for p769v20d) and now my phone won't start up. I just see the LG logo and the screen stays black. I tried doing a hard reset and the little open android shows up, but it then goes black as well. I have root but removed cwm to install the update. My bootloader is locked. Is there anyway to fix this?
Click to expand...
Click to collapse
You should do a search for similar questions before making the same question thats already been answered
anyways, you should offline flash a fresh 10g kdz.. root it and then use rooted v20d cwm back up to restore u to rooted v20d.
worked perfectly for me
So, I already had some issues with this device and they've been pretty similar, in a way that the problem always starts with random reboots when the power button is pressed. About two weeks ago I took it to a technician, because all sorts of connectivity (3G/Wi-fi/Bluetooth) simply stopped working, after yet another reboot. About 3 days ago I got it back and it was working fine except for the fact that the initial boot Motorola logo (The green one before the other logo animations) wasn't showing up. He told me it was fine because it was only an aesthetic problem because he couldn't find that image for my device's resolution.
This morning when i was going to work i picked up my XT1025 Moto E to check for messages and it suddenly restarted. So when I turn it back on, not only the animations did not pop up, but after some time all i get is a black screen, no UI whatsover, all I can do is turn off/restart the phone. At random times when I turn on the screen, it's content shows up but I can't click anything, and then an error message pops up saying that ''system has stopped responding''. I've tried many things to fix it, but nothing has worked so far.
What i've tried:
-Wiping cache partition did not work
-Factory resetting did not work either
-Unlocking bootloader (but apparently it was unlocked already)
-Flashing a custom recovery did not work for some reason...
These last two were on the ''All-In-One Guide'' by neo.ank and honestly I have no idea what i should do to fix this problem - I was thinking about reinstalling the stock ROM but i'd rather ask here first for you guys suggestions... (like i said, complete newb here).
Sorry for the long post and bad english, hopefully someone can help me out on this.
Kaio Oliveira said:
So, I already had some issues with this device and they've been pretty similar, in a way that the problem always starts with random reboots when the power button is pressed. About two weeks ago I took it to a technician, because all sorts of connectivity (3G/Wi-fi/Bluetooth) simply stopped working, after yet another reboot. About 3 days ago I got it back and it was working fine except for the fact that the initial boot Motorola logo (The green one before the other logo animations) wasn't showing up. He told me it was fine because it was only an aesthetic problem because he couldn't find that image for my device's resolution.
This morning when i was going to work i picked up my XT1025 Moto E to check for messages and it suddenly restarted. So when I turn it back on, not only the animations did not pop up, but after some time all i get is a black screen, no UI whatsover, all I can do is turn off/restart the phone. At random times when I turn on the screen, it's content shows up but I can't click anything, and then an error message pops up saying that ''system has stopped responding''. I've tried many things to fix it, but nothing has worked so far.
What i've tried:
-Wiping cache partition did not work
-Factory resetting did not work either
-Unlocking bootloader (but apparently it was unlocked already)
-Flashing a custom recovery did not work for some reason...
These last two were on the ''All-In-One Guide'' by neo.ank and honestly I have no idea what i should do to fix this problem - I was thinking about reinstalling the stock ROM but i'd rather ask here first for you guys suggestions... (like i said, complete newb here).
Sorry for the long post and bad english, hopefully someone can help me out on this.
Click to expand...
Click to collapse
You Should Flash Custom Roms.....
shyvam said:
You Should Flash Custom Roms.....
Click to expand...
Click to collapse
Hey man, thanks for the reply. How would this solve the problem, exactly? (I don't want o sound like a douche , i'd just like an explanation for information purposes - i'd be very thankful for some links ).
Are U on stock rom?
GNVM said:
Are U on stock rom?
Click to expand...
Click to collapse
I think it's currently using lollipop 5.1.
If u want to get back to stock 5.1 then flash stock rom. Then download the firmware from below link .
http://www.androidfilehost.com/?fid=24052804347783250
and download the batch file
https://www.androidfilehost.com/?fid=24269982087018369
1. Boot ur phone in fastboot mode then.
2. Extract the firmware and batch file on same folder and click on the batch file.
3. Click on the Fashtool batch file.
GNVM said:
If u want to get back to stock 5.1 then flash stock rom. Then download the firmware from below link .
http://www.androidfilehost.com/?fid=24052804347783250
and download the batch file
https://www.androidfilehost.com/?fid=24269982087018369
1. Boot ur phone in fastboot mode then.
2. Extract the firmware and batch file on same folder and click on the batch file.
3. Click on the Fashtool batch file.
Click to expand...
Click to collapse
Worked like a charm. Thanks a lot, man. ^_^