Related
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.
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?
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
xDexter said:
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
Click to expand...
Click to collapse
Ive been using ViperDNA which comes with what seems like a custom SuperUser type of all in it.
But when I origionally rooted my phone, i seem to remember having an issue with SuperSU, and the first time i rooted i said screw it and just installed Superuser without any problems. The second time i rooted, i Installed SuperSU, then had to download Superuser form the Android Market, to update the binary, which updated it for SuperSU, and that solved my problem.
When you try to open an app that needs to use root access, do you get the notification asking for permission?
perhaps the "other" superSU/busybox package that you used didn't properly do what it needed to do?
I see the link on that tutorial is broken, fortunately i have the file that i originally downloaded form that very same tutorial saved to my hard drive, and now uploaded to DropBox if you would like to download it and try flashing this zip while in recovery to see if it gives you a proper root.
I would recommend downloading the above file, and flashing that to see if it helps. I'll try to remember to check back here to see if you posted anything in reply, but let me know if it doesn't work. Ill try to help as much as I can
BigRed35m said:
I would recommend downloading the above file, and flashing that to see if it helps. I'll try to remember to check back here to see if you posted anything in reply, but let me know if it doesn't work. Ill try to help as much as I can
Click to expand...
Click to collapse
I installed your package, and get the same errors before in SuperSU. It wants to upgrade but then force restarts whilst trying.
I then tried the Superuser app by Chainsdd, and I make a little progress?
First, when I try to upgrade, it asks for root from SuperSU and Superuser. Since SuperSU came with the busybox package, I can't uninstall it.
When I first go to the updater, it shows me this: (See attachment 1, I can't do links :S)
After I upgrade it, I am left with this screen: (see attachment 2)
It looks like it reverts back to su v .98 from 1.02?
Either way, as soon as I hit lets do it again, the phone restarts. Did I screw up the unlock/root somehow? In the top left of my fastboot screen it shows ***TAMPERED*** and ***UNLOCKED***
I am using CWM 6.0.2.1
BigRed35m said:
When you try to open an app that needs to use root access, do you get the notification asking for permission?
Click to expand...
Click to collapse
If I do it right when I reboot my phone it usually asks correctly
Thanks again for the help so far!
xDexter said:
I installed your package, and get the same errors before in SuperSU. It wants to upgrade but then force restarts whilst trying.
I then tried the Superuser app by Chainsdd, and I make a little progress?
First, when I try to upgrade, it asks for root from SuperSU and Superuser. Since SuperSU came with the busybox package, I can't uninstall it.
When I first go to the updater, it shows me this: (See attachment 1, I can't do links :S)
After I upgrade it, I am left with this screen: (see attachment 2)
It looks like it reverts back to su v .98 from 1.02?
Either way, as soon as I hit lets do it again, the phone restarts. Did I screw up the unlock/root somehow? In the top left of my fastboot screen it shows ***TAMPERED*** and ***UNLOCKED***
I am using CWM 6.0.2.1
If I do it right when I reboot my phone it usually asks correctly
Thanks again for the help so far!
Click to expand...
Click to collapse
It's difficult for me to troubleshoot when i haven't had to fix this problem since december haha.
The tampered, and unlocked is standard that is what it shows for everyone who unlocked the boot-loader.
So let me get this straight,
Do me a favor, un-install Superuser, download RootChecker from the market by JoeyKrim, And run it, what does it say?
->When you run it, did it ask for permission from SuperSU?
With just the SuperSU installed, if you run a program that requires root permission (For example, RootChecker), Nothing shows up asking if you want to Allow/Deny?
->When you open SuperSU to update the binary, it fails to update and restarts the APP?
With the SuperSU/BusyBox package flashed, when you install Superuser from the android market and try to update the binary, it *appears* to revert back to an older version of the binary?
-> After updating the binary through Superuser (despite the appparent reversion), if you un-install Superuser, and try to run RootChecker, does it work?
Sorry, i know it is a lot and i'm not much help, i'm troubleshooting blindly and from a distance haha.
xDexter said:
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
Click to expand...
Click to collapse
you need to install a kernel with /system writing enabled. Such as lk's or cubed
htc has a line wrong in their code and it makes it so that /system cant be edited while booted into android, only while in recovery. Installing a kernel that fixed this bug will let you use supersu from the play store and other apps such as adfree which need to edit system files to function
Bigandrewgold said:
you need to install a kernel with /system writing enabled. Such as lk's or cubed
htc has a line wrong in their code and it makes it so that /system cant be edited while booted into android, only while in recovery. Installing a kernel that fixed this bug will let you use supersu from the play store and other apps such as adfree which need to edit system files to function
Click to expand...
Click to collapse
Yeah this is what I figured out too.
Sent from my HTC6435LVW using XDA Premium HD app
Even with a writeable kernel SuperSu gives a hiccup at first. Download SuperUser, update the binary of SuperSu, then uninstall SuperUser. SuperSu will be fine after that.
orangechoochoo said:
Even with a writeable kernel SuperSu gives a hiccup at first. Download SuperUser, update the binary of SuperSu, then uninstall SuperUser. SuperSu will be fine after that.
Click to expand...
Click to collapse
I never had an issue with supersu
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
I never had an issue with supersu
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Quite a few of us running a version of Supercharged Hatka had problems when they switched to SuperSu,but now they switched back to SuperUser and the problem hasn't reared its head.
I haven't found a way to get system root on surnia xt1526. I've searched and I've done trial and error. I've been a member for years and this is my 1st post cause I try to teach my self. But every attempt I've made at getting system root fails 1 way or another. When I use system less root, I can't interact with the system partition the way I'm used to. Something always, eventually, messes up my phone. So if someone knows where to point me, id truly appreciate it. Sorry of this seems obvious to some but I've been trying for a while.
Thanx
Have you tried system SuperSu?
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
amarc78 said:
Have you tried system SuperSu?
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Click to expand...
Click to collapse
Yes, I have tried it. It didn't work. But it's been awhile. I see that they have newer versions that I'm going to try. Thanx. I forgot about this.
neojpl said:
Yes, I have tried it. It didn't work. But it's been awhile. I see that they have newer versions that I'm going to try. Thanx. I forgot about this.
Click to expand...
Click to collapse
I just tried it yesterday and it won't boot with system root. I hadn't tried it in a while for that reason.
Sent from my LGLS755 using XDA Labs
Use Magisk13.3!! I have tried use supersu zip but that gave to me a bootloop, so i have wiped system, installed it again, flashed magiskroot and my phone boot. If u need more help just tell