Hi,
I have bricked my SGS II ICS 4.0.3. by changing build.prop (I've changed LCD Density) for the second time, and even though I have backup, wiping the whole phone, reflashing stock ROM, restoring it would be real pain in the ass (for the second time, again). So I was wondering, I can access to both recovery and download mode, and I also had USB Debugging on while the phone was running - ADB can't recognize my phone, though. Is there any way to access build.prop and change it back, or I have to do the stock-rom-flashing stuff all over again?
Thank you.
EDIT: Also I'm wondering if there is any way to change that annoying LCD Density without bricking my phone...again.
uN3xp3ct3d said:
Hi,
I have bricked my SGS II ICS 4.0.3. by changing build.prop (I've changed LCD Density) for the second time, and even though I have backup, wiping the whole phone, reflashing stock ROM, restoring it would be real pain in the ass (for the second time, again). So I was wondering, I can access to both recovery and download mode, and I also had USB Debugging on while the phone was running - ADB can't recognize my phone, though. Is there any way to access build.prop and change it back, or I have to do the stock-rom-flashing stuff all over again?
Thank you.
EDIT: Also I'm wondering if there is any way to change that annoying LCD Density without bricking my phone...again.
Click to expand...
Click to collapse
You should be able to start an ADB shell from recovery and edit the build.prop file. What do you mean "ADB can't recognize my phone, though"? If you plug the phone in and type "adb devices", what does it say?
ctomgee said:
You should be able to start an ADB shell from recovery and edit the build.prop file. What do you mean "ADB can't recognize my phone, though"? If you plug the phone in and type "adb devices", what does it say?
Click to expand...
Click to collapse
My fault, I tried to access it via Download mode and not recovery.
Now ADB recognizes my phone, however I'm unable to get superuser access. When I enter su, it gives me back following message: "Segmentation fault". Any ideas?
EDIT: I can't even push the original build.prop back to phone, I get Permission denied message.
uN3xp3ct3d said:
My fault, I tried to access it via Download mode and not recovery.
Now ADB recognizes my phone, however I'm unable to get superuser access. When I enter su, it gives me back following message: "Segmentation fault". Any ideas?
Click to expand...
Click to collapse
Yikes, that sounds like memory corruption somewhere in the system partition. I know you don't want to do the full wipe thing, but it is probably your best hope.
uN3xp3ct3d said:
EDIT: I can't even push the original build.prop back to phone, I get Permission denied message.
Click to expand...
Click to collapse
Right, you won't be able to without superuser access. Since you're getting a segmentation fault when attempting to run "su", you don't have the rights necessary to do so.
ctomgee said:
Yikes, that sounds like memory corruption somewhere in the system partition. I know you don't want to do the full wipe thing, but it is probably your best hope.
Click to expand...
Click to collapse
How did I manage to mess up that by just changing one variable in build.prop (ro.sf.lcd_density)? I'm really considering downgrade to Gingerbread.
uN3xp3ct3d said:
How did I manage to mess up that by just changing one variable in build.prop (ro.sf.lcd_density)?
Click to expand...
Click to collapse
Dunno, don't know what all you've done/installed/modded/etc. Maybe you yourself didn't do anything. Maybe something you installed (and you granted SU access to) did it. Too many variables.
ctomgee said:
Dunno, don't know what all you've done/installed/modded/etc. Maybe you yourself didn't do anything. Maybe something you installed (and you granted SU access to) did it. Too many variables.
Click to expand...
Click to collapse
It's kinda weird, because only Titanium backup, AdFree and nitrality had SU access. And now even formatting data isn't helping, so I'll just have to flash it again. Damn.
uN3xp3ct3d said:
It's kinda weird, because only Titanium backup, AdFree and nitrality had SU access. And now even formatting data isn't helping, so I'll just have to flash it again. Damn.
Click to expand...
Click to collapse
Hmm... actually, I guess you could try re-rooting. Have you tried that yet? Maybe the su binary itself got corrupted.
ctomgee said:
Hmm... actually, I guess you could try re-rooting. Have you tried that yet? Maybe the su binary itself got corrupted.
Click to expand...
Click to collapse
Well, I already flashed stock ICS again so now there's no point. However, next time I mess it up (and I probably will), I'll try that. By the way, do you have any idea how to change screen DPI without actually messing up my phone again? I tried nitrality, LCD Density modder, manually editing build.prop...
uN3xp3ct3d said:
Well, I already flashed stock ICS again so now there's no point. However, next time I mess it up (and I probably will), I'll try that. By the way, do you have any idea how to change screen DPI without actually messing up my phone again? I tried nitrality, LCD Density modder, manually editing build.prop...
Click to expand...
Click to collapse
I don't, sorry man. I don't change my DPI.
Related
Rooted last night, superuser was working fine but this morning I lost all superuser access. Uninstalled SU and reinstalled it. Rom manager gained access but others won't. Now even when I try to flash CWM recovery it says "an error occurred while attempting to run privileged commands!". Any ideas?
you might have to look in this thread, and get the working SU that way
http://forum.xda-developers.com/showthread.php?t=1003088
magneticzero said:
you might have to look in this thread, and get the working SU that way
http://forum.xda-developers.com/showthread.php?t=1003088
Click to expand...
Click to collapse
Thanks, I was reading over that a few minutes ago. I'll give it a try
Tried to flash that patch but I can't boot into recovery. It boots into the bootloader, I select recovery and it just goes back to the white bootloader screen. Am I missing something?
since su works with rom manager, press menu and clear cache and try to push clockwork back on your phone. also there is a option to wipe clockwork mod everytiem you update it. alot of people have success with that.
magneticzero said:
since su works with rom manager, press menu and clear cache and try to push clockwork back on your phone
Click to expand...
Click to collapse
I did that, rebooted like 10 times trying to get into recovery and for some reason I know have su permissions again.... I dunno what happened.
But how do I get into cwm to install rom's and backup/restore? I keep getting the white bootloader screen for some reason.
Sorry, double post....
ugadroid said:
I did that, rebooted like 10 times trying to get into recovery and for some reason I know have su permissions again.... I dunno what happened.
But how do I get into cwm to install rom's and backup/restore? I keep getting the white bootloader screen for some reason.
Click to expand...
Click to collapse
there is an option in rom manager to boot into clockwork recovery, but i edited my last post.. maybe you need to push clockwork again if it isnt going into recovery the manual way, might not be loading the files properly
magneticzero said:
there is an option in rom manager to boot into clockwork recovery, but i edited my last post.. maybe you need to push clockwork again if it isnt going into recovery the manual way, might not be loading the files properly
Click to expand...
Click to collapse
Seems like something might have gotten messed up. Now I lost all su permissions again. lol. I probably should unroot and do the process over again. I've tried the option in rom manager but it takes me to the bootloader screen and when I select recovery it just takes me right back.
I also had this same exact problem. The reason was I had messed something up during the root process. What happened to me is I switched the RUU's around and ended up with the wrong one. My opinion would be to re-root using the original ADB method and make sure you are using the correct RUU. If you need assistance just PM me and I will guide you step through step to re-rooting your T-Bolt.
stedrocklp said:
I also had this same exact problem. The reason was I had messed something up during the root process. What happened to me is I switched the RUU's around and ended up with the wrong one. My opinion would be to re-root using the original ADB method and make sure you are using the correct RUU. If you need assistance just PM me and I will guide you step through step to re-rooting your T-Bolt.
Click to expand...
Click to collapse
I thought for sure I used the right RUU files but it was late so I could have messed up. I would appreciate any help, I used the windows one click method. Not too familar with ADB but I have played with it a lil. PM me when ever you get a chance. Thanks bro.
Mad props to stedrocklp for all the help last night. The help that people give on this site is why it's the best.
I used the one click root on gingerbread and now I can't get the system recovery to work. Every time i try to install it it gives me an install failure message saying "/data/data/com.tenfar.a4.recovery/files/surunner.sh (Permission denied)". Ahh so frustrating can anyone help?
dust. said:
I used the one click root on gingerbread and now I can't get the system recovery to work. Every time i try to install it it gives me an install failure message saying "/data/data/com.tenfar.a4.recovery/files/surunner.sh (Permission denied)". Ahh so frustrating can anyone help?
Click to expand...
Click to collapse
Permission Denied Automatically Makes Me Think Of Root. Have You Made Sure That You Have Root?
It sounds to me that you need to allow Recovery to have SU access. If you want to test your root access download the Terminal app from the market and type in su and enter. See if it allows you. If not, then you need to try to root your device again.
Well I'm pretty sure it's rooted because Titanium Backup is letting me freeze apps and whatnot and I have System Recovery allowed on Superuser... so I don't know what is wrong
Try This, Hit Charge Mode. When You Reboot Uninstall The App Entirely. Reinstall.
MikeJ92YJ said:
Try This, Hit Charge Mode. When You Reboot Uninstall The App Entirely. Reinstall.
Click to expand...
Click to collapse
Ah yes uninstalling rebooting and reinstalling worked like a charm! I thought I had tried it before but I guess not. Thanks a lot!
dust. said:
Ah yes uninstalling rebooting and reinstalling worked like a charm! I thought I had tried it before but I guess not. Thanks a lot!
Click to expand...
Click to collapse
Lol Sweet.
Okay, just wanted to put this info here for easy reference. Feel free to correct anything I may have wrong.
*Based on my experiences performing the operation on windows 7 x64.
1. Install the LG USB driver for windows found under the software tab from their site here
2. Download and extract the English version of the root optimus g created by fiddy619 from here
3. Set USB debugging on and attach your phone to usb, then put it in MTP/Media Sync mode. Next, open a command prompt and navigate to the "stuff" sub-directory of the extracted file. Run the command "adb devices" to make sure your phone has been detected. Go back to the main directory and run the RootOptimusG.bat file.
4. When prompted on your phone choose restore data. Leave your phone plugged into USB until the program tells you it is finished! Sit back and let the magic happen. Your phone will reboot. Mine acted weird for a few seconds after it rebooted, the buttons at the bottom were going on and off and the screen was flickering. Just be patient and give it a couple minutes if needed.
5. When prompted that all is complete you can disconnect your phone from your computer and open the Play store to get the update for SuperSU
Now you are ready to unlock!
should be a sticky.
Thanks!
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
karelson said:
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
Click to expand...
Click to collapse
well if you have the supersu then it should be rooted. also if you now have it unlocked then it is rooted because i dont think you can unlock unless you root. also please search around the forums about what apps to not remove after root. a lot of people have noted issues after removing google apps.
showstopper03 said:
well if you have the supersu then it should be rooted. also if you now have it unlocked then it is rooted because i dont think you can unlock unless you root. also please search around the forums about what apps to not remove after root. a lot of people have noted issues after removing google apps.
Click to expand...
Click to collapse
Great Thank You.
karelson said:
Great Thank You.
Click to expand...
Click to collapse
actually it looks like V.05 you can uninstall any app without fear of security warnings. Please read all of this link for more info on it.
http://forum.xda-developers.com/showthread.php?t=2001655
Correct, you can just double click the bat file...my steps vary because I included a check to make sure adb is recognizing your device properly.
karelson said:
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
Click to expand...
Click to collapse
Bumping this back to the top until stickied.
Sent from my LG Optimus G using Tapatalk 2
IrateCustomer said:
Bumping this back to the top until stickied.
Sent from my LG Optimus G using Tapatalk 2
Click to expand...
Click to collapse
Mine is stuck at "Select Restore Data" from my Phone step ... not sure whats going on.
kirdroid said:
Mine is stuck at "Select Restore Data" from my Phone step ... not sure whats going on.
Click to expand...
Click to collapse
I tried unrooting and re-rooting just to test our guides here and I am stuck at this step too. Obviously I can simply flash su in CWM but I wonder why this is happening.
carrett said:
I tried unrooting and re-rooting just to test our guides here and I am stuck at this step too. Obviously I can simply flash su in CWM but I wonder why this is happening.
Click to expand...
Click to collapse
Go to general-developer options- set desktop backup password. Set the password and then use that when you run the script and restore from desktop backup screen shows up.
Sent from my LG-E970 using Tapatalk 2
kirdroid said:
Go to general-developer options- set desktop backup password. Set the password and then use that when you run the script and restore from desktop backup screen shows up.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
If that worked for you, I'm happy for you. I am at this time unable to find a way to unroot and then re-root aside from restoring a backup in CWM or flashing a superuser zip in CWM. This could be because of a "bug" in our rooting script, in SuperSU's un-rooting function, or just an incompatibility between the two. Either way, I think this rooting mechanism works for more virgin LGOGs than not.
worked for me, easy peasy.
When i run the script it gives an error saying that i'm missing backup-restore.apk and /system/bin/ric does not exist. Any ideas as to why this is?
nice. thank you.
aznracer62 said:
When i run the script it gives an error saying that i'm missing backup-restore.apk and /system/bin/ric does not exist. Any ideas as to why this is?
Click to expand...
Click to collapse
That is probably because your phone is not rooted yet. I got that too as I was rooting it. Worked great.
I'm trying to root. USB debugging is on, connected as MTP. Run ADB, run adb-devices, returns an empty screen.
Try to run the script, it tells me "please check setting again"
HALP.
bebop_ said:
I'm trying to root. USB debugging is on, connected as MTP. Run ADB, run adb-devices, returns an empty screen.
Try to run the script, it tells me "please check setting again"
HALP.
Click to expand...
Click to collapse
Also need to allow "unknown sources" in security settings.
adfurgerson said:
Also need to allow "unknown sources" in security settings.
Click to expand...
Click to collapse
I had that checked as well.
bebop_ said:
I had that checked as well.
Click to expand...
Click to collapse
Do you have lg usb drivers installed?
Hello, I've tried rooting my tablet at first with the sourceforge androidroot thing]. Afterwards I turned on the tablet and the "Android" sign at start up had changed and so did my background,Now I get a system UI error and it restarts every time. Preferabbly I would not like to do a hard reset but I would like to take guides if so, So far nothing I've found on google has helped me.
(I've tried to unroot with SuperoneClick and DoomLord
a500 tablet
DarkLoves said:
Hello, I've tried rooting my tablet at first with the sourceforge androidroot thing]. Afterwards I turned on the tablet and the "Android" sign at start up had changed and so did my background,Now I get a system UI error and it restarts every time. Preferabbly I would not like to do a hard reset but I would like to take guides if so, So far nothing I've found on google has helped me.
(I've tried to unroot with SuperoneClick and DoomLord
Click to expand...
Click to collapse
Which tablet is it? I have an a500 and may be able to help you.
dibblebill said:
Which tablet is it? I have an a500 and may be able to help you.
Click to expand...
Click to collapse
It may be an a500, My tablet is Grey and has the "Acer" on the back. I'm not too sure though. :/
DarkLoves said:
It may be an a500, My tablet is Grey and has the "Acer" on the back. I'm not too sure though. :/
Click to expand...
Click to collapse
Help...please?
Definitely an a500
-bump-
DarkLoves said:
Definitely an a500
-bump-
Click to expand...
Click to collapse
Okay. Which rooting tool did you use? Was it also supposed to install a custom recovery, ROM, etc? I know I'm not on my desktop atm, but i found one for ICS which installed a partition mounter and such.
dibblebill said:
Okay. Which rooting tool did you use? Was it also supposed to install a custom recovery, ROM, etc? I know I'm not on my desktop atm, but i found one for ICS which installed a partition mounter and such.
Click to expand...
Click to collapse
Google "source forge android root" and it should be the first thing that pops up,
I cannot post links yet ;/
DarkLoves said:
Google "source forge android root" and it should be the first thing that pops up,
I cannot post links yet ;/
Click to expand...
Click to collapse
Ah, did find it.
Didn't use that script. Once I'm at my desktop, I can tell you the script I used. Do you have a description of what your boot screen looked like? It could have been the recovery screen.
"Had to run the script manually. After the line files\adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop" and reboot the screen went black after boot android logo. Thought the tablet was bootlooping but this was not the case. Could still connect with adb and USB so after I continued to run all the script file the tablet was booting as expected with root access."
This was posted in the comments on that script. As far as hard reset, I'm not sure, beyond finding something that can push a new recovery or ROM straight to the tablet.
dibblebill said:
Ah, did find it.
Didn't use that script. Once I'm at my desktop, I can tell you the script I used. Do you have a description of what your boot screen looked like? It could have been the recovery screen.
"Had to run the script manually. After the line files\adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop" and reboot the screen went black after boot android logo. Thought the tablet was bootlooping but this was not the case. Could still connect with adb and USB so after I continued to run all the script file the tablet was booting as expected with root access."
This was posted in the comments on that script. As far as hard reset, I'm not sure, beyond finding something that can push a new recovery or ROM straight to the tablet.
Click to expand...
Click to collapse
"bootlooping"; I might have the same problem this person is having. It seems to be "bootlooping" but as this comment says it might not be the problem.a
DarkLoves said:
"bootlooping"; I might have the same problem this person is having. It seems to be "bootlooping" but as this comment says it might not be the problem.a
Click to expand...
Click to collapse
Try reconnecting it to the computer if you still have the script working, and getting back to that step. Unfortunately, I'm drawing a blank right now on doing a hard reset without OS access.
dibblebill said:
Try reconnecting it to the computer if you still have the script working, and getting back to that step. Unfortunately, I'm drawing a blank right now on doing a hard reset without OS access.
Click to expand...
Click to collapse
Well I still have the script, only thing I would be able to do is to try and re-root it or something, the only option is to press enter for it to root.
DarkLoves said:
Well I still have the script, only thing I would be able to do is to try and re-root it or something, the only option is to press enter for it to root.
Click to expand...
Click to collapse
Try that and leave it connected.
dibblebill said:
Try that and leave it connected.
Click to expand...
Click to collapse
I would have to do it while it was turned off.
DarkLoves said:
I would have to do it while it was turned off.
Click to expand...
Click to collapse
Er, well I dont have to but, I'm not sure if I should turn it on.
Should I do it while its on is the question.
DarkLoves said:
Er, well I dont have to but, I'm not sure if I should turn it on.
Should I do it while its on is the question.
Click to expand...
Click to collapse
I'd say yes. If the tablet's powered off, it can't connect at all. :S
dibblebill said:
I'd say yes. If the tablet's powered off, it can't connect at all. :S
Click to expand...
Click to collapse
Failed to copy files/su to /system/xbin/su' : Read-only file system
rm failed for /data/local.prop No such file or directory
Installing superuser....
failed to copy 'files/superuser.apk' to '/system/;app/superuser.apk' : Read-only file system
It didn't work, uh, Still same problem.
re-edit Everything is alright. Thanks sorry for the trouble.
I'm going to check if its rooted, it should be.
DarkLoves said:
Failed to copy files/su to /system/xbin/su' : Read-only file system
rm failed for /data/local.prop No such file or directory
Installing superuser....
failed to copy 'files/superuser.apk' to '/system/;app/superuser.apk' : Read-only file system
It didn't work, uh, Still same problem.
re-edit Everything is alright. Thanks sorry for the trouble.
I'm going to check if its rooted, it should be.
Click to expand...
Click to collapse
Not Rooted
DarkLoves said:
Not Rooted
Click to expand...
Click to collapse
Okay. I hate to make you wait, but I have to- when I get home today, I'll log onto my desktop PC and check all the rooting tools (I keep every tool for every phone/tablet I root). It'll be about 8-10 hours (I'm at work right now), but I'll get the names of the rooting tools I used. You're on the stock Android 4.0.3 OS, right?
DarkLoves said:
Not Rooted
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1520469
Try this thread. ITs what I used to root.
Did it work?
I was trying to disable FSYNC using the method described by poofyhairguy. I did it via terminal, in su. I mounted /system in rw mode, I copied libsqlite.so and libsqlite_jni.so into backup copies, and overwritten them with copied provided by poofyhairguy. Alas, I forgot to chmod, so they were left with whatever permission they came from. I rebooted the tablet and now it is permanently in the starting screen with big ASUS letters across. I cannot even turn it off!
Help, please, what do I do? I don't really know much about Android, so please use simple explanation.
Just to add some details. My Prime is stock, rooted but not unlocked.
I also don't seem to be able to reach it from ADB. I did install ADB and drivers on my PC a while ago, when I rooted it. I'm trying this now:
- connect Prime to PC
- reboot with volume down, select a USB symbol
- PC says "installing drivers" and "ready"
- in adb shell, when I try "adb devices" it shows an empty list
Any help?
OK, here is more information and more questions. I can start the tablet in fastboot mode (USB symbol on screen). After reinstalling ASUS suite and Google SDK I connected the tablet to my Windows 7 laptop. It searched for drivers for a while, installed and said "ready".
"adb devices" returns and empty list. "fastboot devices" returns one entry, a long hexadecimal number and the word "fastboot". Does it mean that I can see my tablet via fastboot but not adb? Does adb work when tablet is in fastboot mode at all?
Does it mean that the only option is to reflash ASUS firmware?
@Felisek Did you tried to wipe aka hard reset the device via bootloader? or you have important files which you don't want to reset? or you don't see wipe option in bootloader?
Sorry, I'm not much expert in android underhood that I can help you more but looking at your problem doesn't look like you have bricked your device so keep hopes. Someone having more knownledge might come and help you.
btw; AFAIK, adb and fastboot are different kinds. You see fastboot.exe in the sdk package? yes that links with fastboot option on the devices. But I might be wrong as well.
May be you try entering into fastboot and use fastboot.exe, then go to the path where you modified the files. Either replace them to original ones or chmod. But I don't know whether this gonna work.
CRACING said:
Did you tried to wipe aka hard reset the device via bootloader? or you have important files which you don't want to reset? or you don't see wipe option in bootloader?
Click to expand...
Click to collapse
There is a wipe option, but I don't think it is going to work. As far as a know (correct me if I'm wrong), factory wipe does not change /system folder. In particular, there are two "wrong" files in /system/lib that cause the problem, so wiping everything else is not going to help. I need to change/restore these files.
I think I can reflash the stock ROM using recovery, but I'd like to try and fix it without wiping everything first. I don't have anything unmissable on the tablet, but reinstalling everything and rooting is a bit of a hassle.
Felisek said:
There is a wipe option, but I don't think it is going to work. As far as a know (correct me if I'm wrong), factory wipe does not change /system folder. In particular, there are two "wrong" files in /system/lib that cause the problem, so wiping everything else is not going to help. I need to change/restore these files.
Click to expand...
Click to collapse
Hmm may be you are right so reflashing whole ROM is required.
Felisek said:
I think I can reflash the stock ROM using recovery, but I'd like to try and fix it without wiping everything first. I don't have anything unmissable on the tablet, but reinstalling everything and rooting is a bit of a hassle.
Click to expand...
Click to collapse
Recovery? but you said you haven't unlocked or you mean stock recovery?
Yeah, upon reflashing, you will lose root but hey, you can root again using the new method (motorola's) and its not at all risky as unlocking. :good:
May be you can wait for sometime, I hope someone comes up guiding you how to replace/modify the system files using adb or fastboot.
CRACING said:
Recovery? but you said you haven't unlocked or you mean stock recovery?
Click to expand...
Click to collapse
There is a "RCK" option on startup, I thought that was recovery. But, yes, I mean stock recovery, if this is how it is called. Download stock firmware, put it on a microSD, rename it to EP201_SDUPDATE.ZIP, reboot and apparently it installs automatically.
When I was making my guide I tried using the old ICS libsqlite.so and libsqlite_jni.so files and softbricked in the same mannor. The only way I found to fix it was to flash the stock ROM as it says to do in my guide.
Note that unless you purposefully wipe your data in the recovery your data should remain intact from my experiance with it. The way the stock Asus recovery seems to do it is to blow /system away (so yes you must re-root, etc).
Good news. I unbricked my Prime by reflashing the stock ROM, using the method described by poofyhairguy. All my apps and settings survived. I only lost root, so even rootkeeper cannot recover it. Not too bad, after all.
Sent from my Transformer Prime TF201 using Tapatalk HD