Develop Bugs

epic stuck at boot screen because of screen resolution change need help

ok guys this is my first time asking for help because i don't want to start all over again, i was on ics fb17/fb15 modem, running as my daily for about two days and i wanted to change the density like i did on gb, i don't remember what app it was because right after i changed it the phone rebooted to change it and got stuck at the galaxy s2 screen, so what im asking is if there's a way to command prompt into the phone and pull the build.prop and change the dpi back to stock and push it back so it can boot, also i suck at command prompt so if you can help, could you post exact commands for me to use, and yes Ive searched the forums and google and couldn't find anything that showed how to command prompt into it if it wasn't turned on. any help would be awsome

mypd1991 said:
ok guys this is my first time asking for help because i don't want to start all over again, i was on ics fb17/fb15 modem, running as my daily for about two days and i wanted to change the density like i did on gb, i don't remember what app it was because right after i changed it the phone rebooted to change it and got stuck at the galaxy s2 screen, so what im asking is if there's a way to command prompt into the phone and pull the build.prop and change the dpi back to stock and push it back so it can boot, also i suck at command prompt so if you can help, could you post exact commands for me to use, and yes Ive searched the forums and google and couldn't find anything that showed how to command prompt into it if it wasn't turned on. any help would be awsome
Click to expand...
Click to collapse
If you can get into recovery you can do command prompts from there. If you dont have a recovery I suggest download rogue with fB17 kernel baked in and then go to mounts and you can mount your system. I would start there first... Then we can deal with adb...
All you would have to look for is how to push a file using adb in a google search. Make sure you pull the build.prop file from your downloaded original rom/zip file to push it back to your phone
adb pull /system/build.prop
adb push build.prop /system/
Edit: You can also download adbcommander for your pc which does the same thing but through a program.

thank you so much, im just waiting on my sdk to update, kinda slow internet, and im guessing it should work, never thought about connecting it in recovery. thanks

mypd1991 said:
thank you so much, im just waiting on my sdk to update, kinda slow internet, and im guessing it should work, never thought about connecting it in recovery. thanks
Click to expand...
Click to collapse
I know this thread is a bit old, but I just found myself in the same boat... Just got my E4GT yesterday and been playing around. Decided to change DPI and after reboot i'm stuck on Samsung boot screen. I did have a recovery loaded, so I booted in pulled build.prop, changed it back and pushed back however still stuck. Did this fix your issue?

i just go into custom recovery and reflash rom without wipe n it boots back up
Sent from my SPH-D710 using XDA

elliwigy said:
i just go into custom recovery and reflash rom without wipe n it boots back up
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
This was my fix to get phone running again... But then how do we effectively update build.prop w/o causing it to stick at boot? First attempt was using ES File Explorer, enabled root and mounted system, modified only the DPI value in build.prop, saved, reboot. stuck at boot screen.
Update: Was looking at build.prop and noticed there are 2 lines containing DPI setting. I only updated the first line on my first attempt... This time I did adb pull from recovery, edited file, and adb push back. Then when i rebooted build.prop does not reflect my changes, still had default values.
Update:Tried using ES File Explorer again and made sure to update both lines, still get stuck at boot screen. Act's like phone is preventing any changes to it and locks up when it detects a change.

Ever get a fix for this??? I'm experiencing the exact same issue with my Galaxy s4 1337M on a TW lollipop Rom.

Help! Phone not bricked, but won't boot.

Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?

Try flashing the stock tar in odin if nothing else works.

DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok

I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you

Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol

fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store

DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha

[Q] Soft Brick,TWRPvsClockwork-Avoiding same mistakes

Dodged a bullet yesterday. FreeGee unlock, chose TWRP and then went to flash stock v9 odex. Wiped Cache/Dalvick and then flashed. Upon reboot I saw LG screen then black and nothing. Tried to LGPNST from download mode with LG driver and could not detect phone. After messing around in TWRP for about 2 hours where I performed about every function available (just before throwing the phone into the fireplace), I queued the z9 odex twice let TWRP flash it twice and everything worked. Here's the thing, my wife's phone is incessantly prompting to update, so I need to flash her phone. Should I use clockwork? Anyway to avoid a similar issue and near total bricking of her phone?

Same thing using Clockwork on wife's phone. Now I'm trying everything to get it back. Still have recovery, but unable to complete system reboot. Black screen. Used to flash evo all the time, never an issue. Now I'm 0 for 2 with a miraculous boot and update on my phone. This one doesn't look like I'm going to get as lucky. CWM is a bigger pain too. Frustrated. Not looking forward to lgpnst (still not sure how it all works) and then trying this mess again.

I had a similar problem to yours last night to. Except I didn't really do anything to it. It was just sitting there charging and I took it off the charger and it was doing some kind of boot loop, But every so often it would just stop on a black screen. I lgnpst about six times back but after running root and freegee I would try to get into bootloader and it would do it again. Eventually I tried doing freegee with clockwork instead and it did it again, Than I forced the phone off and pluged it in to my computer to get ready to lgnpst again so I could at least use the phone. All of a sudden I look at the screen and there was a battery charging animation. And then unpluged it and for kicks turned it on and it booted up no problem. Then I tried booting into bootloader and all works now. It was really strange, I did put twrp back though. I like it better then clockwork. I think I sore you asking questions in irc while I was in there asking question to ha.
-Frank

MikeDroid said:
Same thing using Clockwork on wife's phone. Now I'm trying everything to get it back. Still have recovery, but unable to complete system reboot. Black screen. Used to flash evo all the time, never an issue. Now I'm 0 for 2 with a miraculous boot and update on my phone. This one doesn't look like I'm going to get as lucky. CWM is a bigger pain too. Frustrated. Not looking forward to lgpnst (still not sure how it all works) and then trying this mess again.
Click to expand...
Click to collapse
I had the same thing happen and couldn't figure it out so I took it back to sprint told them I did the update and it messed up so they gave me a new phone for 35 bucks and from now on im staying STOCK.........................

DId you try to lgnpst back yet? That may help you.
-Frank

Frank...yup that's how mine worked. Just not sure how to do this. I don't think my failed lgpnst attempts did anything, b/c mine took the update eventually. I'll keep trying. This phone is so temperamental. Does Shellnut have some input on this problem? I can't figure out why some phones take and others don't when doing the same thing.

Talk to Shelnut2 over pm or find him in irc. I just found out there is a special version of freegee that may fix the problem. I seem to have fixed mine but I sent him a pm asking some questions about the problem. I think you are going to need to lgnpst back. Then root and run the special version of freegee. You have to get it from him because it does some things different that may brick the phone permanently. Thats why you have to ask for it. From what I understand it fixes that kind of problem.
-Frank

I will. I'm going to see if this thing will self correct. Otherwise I will check with him on that. The LGPNST is something I'm not looking fwd to doing.

LGPNST is not detecting phone in dl mode but does detect when in recovery. This SUCKS. Frustrated and out of ideas.

When you installed lgnpst did you install the file that says auto-lgnpst? Also did you run install.bat as administrator?
-Frank

frankt2012 said:
When you installed lgnpst did you install the file that says auto-lgnpst? Also did you run install.bat as administrator?
-Frank
Click to expand...
Click to collapse
Not sure if I ran as administrator. Assumed that I did. As a casual hack, I'm in over my head.
Sent from my LG-LS970 using xda app-developers app

Ok. Ran as admin. Won't even detect device. Anyone in DFW area proficient in this stuff who I could pay to lgpnst this thing?

Bricked OG
MikeDroid said:
Ok. Ran as admin. Won't even detect device. Anyone in DFW area proficient in this stuff who I could pay to lgpnst this thing?
Click to expand...
Click to collapse
I've been working on mine for a day and a half. I can't figure out the thing with renaming the ".tot" file to ".bin" because I don't even see a .tot file. After I unzipped the big ZV7 there was only one file without an extension so I can't figure out if thats the one I'm supposed to rename. Can you point me in the right direction?:crying:
[ I figured it out, I had to go into Preferences on my file explorer and set it to show all file types...DUHHH ]

In Windows, go to control panel, file settings, show file extensions. Something like that.
Sent from my LG-LS970 using xda premium

Finally got bit working. No more issues. Non of this stuff is very intuitive when your in panic mode. All is good now though.
Sent from my LG-LS970 using xda app-developers app

Apps
MikeDroid said:
Dodged a bullet yesterday. FreeGee unlock, chose TWRP and then went to flash stock v9 odex. Wiped Cache/Dalvick and then flashed. Upon reboot I saw LG screen then black and nothing. Tried to LGPNST from download mode with LG driver and could not detect phone. After messing around in TWRP for about 2 hours where I performed about every function available (just before throwing the phone into the fireplace), I queued the z9 odex twice let TWRP flash it twice and everything worked. Here's the thing, my wife's phone is incessantly prompting to update, so I need to flash her phone. Should I use clockwork? Anyway to avoid a similar issue and near total bricking of her phone?
Click to expand...
Click to collapse
Always backup your phone before tinkering with system files, and experimenting with launchers, kernals etc.
Titanium backup in WORTH the investment to upgrade to PRO.
Rom manager is a good one to boot directly into recovery without fiddling in the fastboot menu. And for backing up settings and roms.
Always KNOW what your doing. lol. sometimes even the big guys forget this. RESEARCH!

Deleted.

Deleted.

Have you tried going into download mode and flashing stock mg2? I dont know how to fix your no network issue but its worth a try to see if phone boots again. Or try 3 parted gb stock. Search
Sent from my GT-I8160 using Tapatalk

teddytsen said:
Have you tried going into download mode and flashing stock mg2? I dont know how to fix your no network issue but its worth a try to see if phone boots again. Or try 3 parted gb stock. Search
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
I tried it and it seems it will work but I don't know why but phone shut downs after a few seconds while flashing the rom again. And also I heard very silent sound from phone and after sound reach a a little bit high level phone shut itself down. I thought it is because of the battery. Battery might finish. Plugged battery out and tried again to go download mode with usb connected, it doesn't go download mode. I need to charge battery I think but since the system is fully down it doesn't charge :S

And currently! I successfully flashed the stock Jellybean Kernel! Phone is now on and I will root it. How can I change imei? With many researches I learnt that I need to back up EFS and then edit it with hex editor and restore it to phone again. But none of the programs or apps don't work with Ace 2. I need to change its IMEI please any ideas?

Since the phone's imei was cloned i dont know how to receive the original one..
Sent from my GT-I8160 using Tapatalk

teddytsen said:
Since the phone's imei was cloned i dont know how to receive the original one..
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Can you have a look at here http://forum.xda-developers.com/showpost.php?p=49016501&postcount=6957

Problem enabling Trace Input with ZVC update

I don't know if anyone else is having this issue, but I have tried enabling Trace Input by editing the Build Prompt using Root Browser four times now, and all four times have resulted in the following two error pop-ups:
Unfortunately, com.android.systemui has stopped working. OK
Unfortunately, Home has stopped working. OK
Pressing OK gets me nowhere. It only brings back the same two messages instantly, making it impossible for me to do ANYTHING. It's a stock rooted OTA ZVC, so there's no custom recovery nor ROMs to flash even if I had a custom recovery. Two out of the four times, I had to use the LG Flash Tool and flash the ZV7 and 8 tot files and kept installing the OTAs until I was back to ZVC. The other two times, I flashed the ZVC files. Of course, regardless of what you flash, you're losing EVERYTHING on your phone — music, movies, pics, texts, call logs, apps, etc. Reinstalling tons of apps and using the USB to transfer tons of pics, movies, and music takes FOREVER to do, so I was wondering if any of you were having this same issue. If so, how do I resolve it?
P.S. I usually tether my data to my computer, but right now I'm using my little sister's wifi hotspot. Sprint is upgrading the towers on my area, so not only is there no LTE available right now, but the download speeds are terribly slow. I'm downloading the ZVC tot now, and it's 0.6/2.1 GB with 10 hours left to complete. I'm hoping someone can/will provide me with a fix before then to save me the trouble of starting fresh all over again.
Sent from my iPad using Tapatalk

andriodee said:
I don't know if anyone else is having this issue, but I have tried enabling Trace Input by editing the Build Prompt using Root Browser four times now, and all four times have resulted in the following two error pop-ups:
Unfortunately, com.android.systemui has stopped working. OK
Unfortunately, Home has stopped working. OK
Pressing OK gets me nowhere. It only brings back the same two messages instantly, making it impossible for me to do ANYTHING. It's a stock rooted OTA ZVC, so there's no custom recovery nor ROMs to flash even if I had a custom recovery. Two out of the four times, I had to use the LG Flash Tool and flash the ZV7 and 8 tot files and kept installing the OTAs until I was back to ZVC. The other two times, I flashed the ZVC files. Of course, regardless of what you flash, you're losing EVERYTHING on your phone — music, movies, pics, texts, call logs, apps, etc. Reinstalling tons of apps and using the USB to transfer tons of pics, movies, and music takes FOREVER to do, so I was wondering if any of you were having this same issue. If so, how do I resolve it?
P.S. I usually tether my data to my computer, but right now I'm using my little sister's wifi hotspot. Sprint is upgrading the towers on my area, so not only is there no LTE available right now, but the download speeds are terribly slow. I'm downloading the ZVC tot now, and it's 0.6/2.1 GB with 10 hours left to complete. I'm hoping someone can/will provide me with a fix before then to save me the trouble of starting fresh all over again.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I'm sorry, with those 2 errors kind of hard to do anything on the phone. I would say I could send you a build prop, but without getting into a recovery or without the errors won't do any good.
If you can use
http://forum.xda-developers.com/showthread.php?t=2715496
The auto-rec program. It keeps download, down grades aboot, gives you recovery.
I do apologize if I don't remember but if you are one of the few unlucky with white line syndrome on the phone after a recovery is installed.
Cloudyfa has the fix linked on the first page also.
Which will make it like you didn't just try to put recovery on.
Sent from my Nexus 7 using Tapatalk

The app you used to edit may have truncated the build.prop, I know rootexplorer says its too big and truncates in a warning message, do it on computer and overwrite or use a separate build.prop editor. Check permissions on modified build.prop which should be rw-r-r. I have done this on both my G2s with no problems.

Abhinav.tella nailed it. I use Rom Toolbox lite, just as I show in my thread. Works like a charm on ZVC. Also, you can just flash a ZVC TOT if you had to. You don't need to flash all the way back using an old TOT file and work your way to current.
Sent from my iPad using Tapatalk

abhinav.tella said:
The app you used to edit may have truncated the build.prop, I know rootexplorer says its too big and truncates in a warning message, do it on computer and overwrite or use a separate build.prop editor. Check permissions on modified build.prop which should be rw-r-r. I have done this on both my G2s with no problems.
Click to expand...
Click to collapse
I guess I can try that. My only gripe is that if it doesn't work, I'll have to tot back and have no files or anything on my phone again. That is a hassle and it really sucks having to reroot and install all my apps and stuff again.
Sent from my iPad using Tapatalk

andriodee said:
I guess I can try that. My only gripe is that if it doesn't work, I'll have to tot back and have no files or anything on my phone again. That is a hassle and it really sucks having to reroot and install all my apps and stuff again.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I did it on my computer.

abhinav.tella said:
I did it on my computer.
Click to expand...
Click to collapse
How?
Sent from my iPad using Tapatalk

Also clear data on keyboard before rebooting! Nobody seems to mention that.
Sent from my LG-LS980

joshuajones said:
Also clear data on keyboard before rebooting! Nobody seems to mention that.
Sent from my LG-LS980
Click to expand...
Click to collapse
Dont have to....