So I have a Verizon SGIII rooted with recovery. I changed my LDC Desnity to 270 with ROM Toolbox, then I installed LCD Density Modder and used that do change it back to 320 (what I thought was the default value). Now when I boot up my phone I get to the Samsung Galaxy SIII logo and then the screen just goes black. Doesn't respond to touch or anything. I'm now trying to mount my system through recovery but it won't work for some reason.
Is there some way I can fix this through recovery?? Will a cache wipe or something reset the LCD density?
Thanks
Did you make a nandroid backup before hand ? If so you could try advance restore and restoring system from a nandroid backup. Or just do a full restore.
Sent from my SGH-I747M using xda app-developers app
Unfortunately I didn't. But if I have to do a full restore I can. Is this the "Factory Reset" option?
connect your device to samsung kies maybe? you can do stuff on your phone with the pc i think theres restore as well
Sent from my SGH-T999V using xda app-developers app
If you don't wanna mess around with adb commands to pull the build.prop and fix it manually just reflash your rom.
Sent from my SPRINT GALAXY S III
Related
Hi,
My Galaxy Note start having this long boot up waiting times after reverting back from ICS update.
The phone would wait for around 5 minutes on the Samsung splashing boot up screen and then a vibration with a light would emits the lower menu buttons when the phone is about to start.
It's like the waiting time for "Android is upgrading... Scanning applications XXX - 296" on the ICS!
Any help or ideas on how to fix that? Maybe a change in the numbers of "boot up timeout" file or something, if there's any can fix it???
Thanks!
Sent from my GT-N7000 using xda premium
Have you tried clear cache n wipe data?
Yes I've done cache wipe, dalviks cache wipe, system restore before reverting back!!!!
some time post flash it needed.
you can try again still not works, Reflash stock ROM again
I really have no time of doing so, it's time consuming...! Can I do that and then apply CWM backup restore??? Or it's going to conflict?
Cwm backup will push system junk if restore completely, so restore data only
Sent from my GT-N7000 using xda premium
Or that...
Sent from my GT-N7000 using xda premium
I haven't had the need since going to the Note, but there's a neat program called alogcat which, for the boot animation, shows the logcat file scrolling by.
It might be useful to see what the Note is grinding on as it's booting up.
I used it for my mytouch 4g. Also nice to know that the boot is actually still 'booting' versus totally hung.
- Frank
How do you go over th boot menu in alogcat? You just scroll and search for boot?
Sent from my GT-N7000 using xda premium
Hey Everyone,
So I was being impatient and wanted to change the Density of my LCD on my Nexus 7. I changed it from the stock DPI to 170 using LCD Density Modder on the Market. Ever since reboot I have not been able to get past the google screen when you first turn on device. I can get into bootloader as well. My bootloader is unlocked and device is rooted if that helps.
Is there any easy way to recover the device besides a adb, or fastboot method? If not, what are the adb, fastboot commands to flash the OTA image to device from my PC?
Thanks
Download the nexus root toolkit, it can turn everything stock.
Sent from my LG-P999 using xda app-developers app
I have the nexus root toolkit, but don't you need the device powered on to put in usb debugging mode, etc? All I can do is hit google splash screen and get into bootloader, recovery.
There's buttons that say revert to stock, I believe those work in recovery.
Sent from my LG-P999 using xda app-developers app
redmonke255 said:
Download the nexus root toolkit, it can turn everything stock.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
+1 just unlock and reflash
Sent from my i777 using xda app-developers app
Whenever I try to flash stock + unroot I get error message, "Windows cannot find 'C:\\data\gnexwug_DLnX.exe'. Make sure you typed the name correctly, and then try again."
Im not trying to type in anything, all I am doing is trying to restore to stock.
did you make a nandroid backup?" i am goign through the same thing right now. I am goign to restore from backup.
To change the desinty, it must be manually done in build.prod i assume. LCD Density modder might not be compatible, yet.
edit: Crap, i cant boot to recovery for some reason :/
edit2: it seems the only way to boot into recovery now is from a ROM manager application. Ijust finished restoring using the Nexus Toolkit.
I finally figured how to get SDK going and restored via nexus root toolkit. Thanks guys!
Sent from my Nexus 7 using xda app-developers app
mheller91 said:
I finally figured how to get SDK going and restored via nexus root toolkit. Thanks guys!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I stupidly did the same thing and am now in the same situation. :crying:
Can you tell me how you finally got it sorted?
Cheers
damienleetobin1976 said:
Hi,
I stupidly did the same thing and am now in the same situation. :crying:
Can you tell me how you finally got it sorted?
Cheers
Click to expand...
Click to collapse
Personally,
i booted into fastboot (all buttons if i remember correctly), then hit up the Tool Kit, go to advanced > temporary recovery, From there, i just restored my nandroid backup, or if you have any roms on there, just flash that.
You could do that, or once in fastboot and connected, you could just unlock, which will wipe everything.
tremblingwater said:
Personally,
i booted into fastboot (all buttons if i remember correctly), then hit up the Tool Kit, go to advanced > temporary recovery, From there, i just restored my nandroid backup, or if you have any roms on there, just flash that.
You could do that, or once in fastboot and connected, you could just unlock, which will wipe everything.
Click to expand...
Click to collapse
Hi,
I tried this and went for the Unlock route but after a restart it now just seems to be stuck at the google splash screen.
Is it usual to take this long?
Cheers
So what program is everyone using to change the DPI without getting a black screen?
Sent from my Nexus 7 using xda premium
theusername said:
So what program is everyone using to change the DPI without getting a black screen?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just using a file explorer (specifically, solid explorer but root explorer should also work), navigating to /system/build.prop, and changing the number ro.sf.lcd_density.
changing that particular number's easy, and the last app I tried somehow managed to make a second build.prop inside the same file. So yeah.
Don't forget to backup your build.prop (preferably externally as well, in case you need to flash it) before trying this. And/or make a nandroid.
damienleetobin1976 said:
Hi,
I tried this and went for the Unlock route but after a restart it now just seems to be stuck at the google splash screen.
Is it usual to take this long?
Cheers
Click to expand...
Click to collapse
Im not sure, i dont want to advise something that is wrong, but, no, it doesn't take extraordinarily long. How long has it been?
I would boot into fastboot again and try the other route (provided you have a rom on the device or hopefully, better yet, a nandroid)
If you're using the cwm recovery from the toolkit you must be plugged in to usb to access cwm from the bootloader menu. From there you can reflash whatever you want to fix it.
jamesbra said:
If you're using the cwm recovery from the toolkit you must be plugged in to usb to access cwm from the bootloader menu. From there you can reflash whatever you want to fix it.
Click to expand...
Click to collapse
Yep, this is how it got it back and running last night.
I then used root explorer to edit build.prop and it worked like a charm.
Thanks all
Hi all,
I was hoping someone could shed sime light to my situation. I have a rogers S4 and I rooted it via motochopper and it worked fine. Restored all my apps from Titanium backuoband all was well.
This morning my phone then got stuck at the samsung boot screen and I had to wipe data via the stock recovery to get iy working again...
Can anyone tell me why this is happening? This is thr 3rd time this has happened
Sent from my SGH-I337M using Tapatalk 2
My guess would be the titanium backup. As it can mess things up, once in a while.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
linkin275 said:
My guess would be the titanium backup. As it can mess things up, once in a while.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I would blame TB mess ups more on old data being restored that causes problems, than TB itself.
OP... Are your app backups from a different ROM? If so, then I would try restoring without data. Or fresh app installs.
Sent from my SAMSUNG-SGH-I337 using xda premium
are you restoring system apps? or just user apps? if you are restoring system apps or something like the messaging storage, will normally cause problems in TB.
best to just connect to wifi and download all the apps again from playstore.
What I would do is odin back to stock do not restore anything for a day or 2, and monitor it. If it never does it again, then it was your backup, keep in mind some apps that worked on the G3, may not work on the G4.
Yes, this is Titanium, it happenned to me too, remember that doing that is like copying everything in the C: Program Files of a PC, formating the computer and restoring that folder, it might work, but you might end up in a lot of trouble overtime since the OS installs different part everywhere. Use Carbon aka Helium, its a much cleaner way to go
I was restoring apps (with data) and the backups were from older ROMs I used in my nexus 4. I am currently trying a non-rooted method for a few days and see if this problem reoccurs
Sent from my SGH-I337M using Tapatalk 2
UPDATE: so far so good... My setup is currently unrooted and I haven't had this issue appear. I'm gonna root in a few days and monitor it again
Sent from my SGH-I337M using Tapatalk 2
cool
So I've gotten myself into a real mess with my nook. I was playing around with it and accidentally deleted my user partition and when I was trying to repair it I ended up wiping it of everything... So as I've been trying to fix it with Nook Manager which creates a backup but I don't think its a functioning one because when I press restore backup nothing happens. I also tried doing a factory restore but it says the factory restore.zip is missing. I can't find either a backup img or a restore.zip for the NST online anywhere. Is there any hope or is this thing gone for good? I would really appreciate any help people can offer.
Can anyone please test this for me?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Sorry.
Somehow my mobile app posted that in the wrong topic
Sent from my SGH-M919 using XDA Premium 4 mobile app
You should look at this thread: http://forum.xda-developers.com/showthread.php?p=48132647#post48132647
I have a rooted Note 3, snapdragon variant. Rooted with towelroot
The main reason i rooted was to change the screen's dpi; i cant stand having everything oversized at 480dpi
I changed the dpi by editing the build.prop
My question is, what would happen if i unrooted (through SuperSU) and then did a factory reset without manually changing the dpi back to default?
Would it stay changed or would it revert to 480?
Sent from my SM-N9005 using XDA Free mobile app
It will stay. Factory Reset doesn't touch System Files, it only removes the User (Data) Files. It's not like an flash with Odin.
So all changes you're doing with your System won't revert by doing an Factory Reset.
HSD-Pilot said:
It will stay. Factory Reset doesn't touch System Files, it only removes the User (Data) Files. It's not like an flash with Odin.
So all changes you're doing with your System won't revert by doing an Factory Reset.
Click to expand...
Click to collapse
So I can have, say, 380dpi settings even if i unroot by not changing the build.prop back?
What happens if i want to change it back to the default?
I'd have to root again so that i can edit the build.prop?
Sent from my SM-N9005 using XDA Free mobile app
Exactly.
Strayckler said:
I have a rooted Note 3, snapdragon variant. Rooted with towelroot
The main reason i rooted was to change the screen's dpi; i cant stand having everything oversized at 480dpi
I changed the dpi by editing the build.prop
My question is, what would happen if i unrooted (through SuperSU) and then did a factory reset without manually changing the dpi back to default?
Would it stay changed or would it revert to 480?
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Of course it stayed at the value you have set.
Because the build.prop file is on system partition. And factory reset only affect the userdata, not system partition.
What if i update my firmware?
Sent from my SM-N9005 using XDA Free mobile app