Database Develop

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu
This tool will root you nexus s/Galaxy Nexus install su or super su and ClockWorkMod recovery!!
For Nexus S:4G,I9020T,I9023,I9020A.
Galaxy Nexus:GSM/Verizon/Sprint
Disclaimer!
Your warranty is now void.
I am not responsible for bricked or damaged devices
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
DOWNLOAD
Click to expand...
Click to collapse
Current Version (Nexus S + Galaxy Nexus) 3.5: http://d-h.st/qaL
MIRROR:http://www.mediafire.com/download.php?1if2rvgpcte2rcs
Old versions:
3.0: http://d-h.st/mhO
2.0: http://dev-host.org/gcZ (nexus s only)
1.0: http://dev-host.org/bEE (nexus s only)
HOW-TO
Click to expand...
Click to collapse
just unzip the content and run the tool ! drivers are included in case you need them.
incase you had any problems try rerunning the tool,and if you got superuser/supersu app but you are unable to use root apps,update superuser/supersu from the play store then update the binary from inside the app.
CHANGELOG
Click to expand...
Click to collapse
V3.5
-added support for jelly bean
-few script optimization
-updated superuser and supersu
V3.0
-added support to galaxy nexus and all it's variants.
-added support to install super su.
-moved from *.bat to *.exe
-new icon
-su/super su, will now automatically flash no need to touch "install zip"
-skip bootloader unlock if you are already unlocked.
-update drivers
V2.0
-Removed "sticky.bat"
-modified su flashing script.
-the recovery now will stick automatically no need to flash any file after rooting or running any script.
V1.0
-initial release
ALL DATA WILL BE WIPED FROM DEVICE(only if bootloader is locked)
credits
-Chainfire for super su
-ChainsDD for superuser
-Pdanet for drivers
-Clockworkmod team for recovery
-my friend for the icon​

am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?

raducux said:
am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?
Click to expand...
Click to collapse
if your bootloader is locked then yes you will loose everything on USB storage,if the bootloader is already unlocked you will not loose any data,you don't need to flash a rom after rooting the device as it will not wipe the system.

Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?

Sticky please
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.

Romaniac said:
Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?
Click to expand...
Click to collapse
Turn off the usb storage,you just need usb debugging enabled if you turned on usb storage it will not work
stewie-droid said:
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.
Click to expand...
Click to collapse
The tool includes the latest cwm img,but if you want to replace it with another one you can do,just make sure you rename it to same name of the img in the root tool folder,but make sure that the recovery you will use is compatible with the nexus s

After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.

Ritwik7 said:
After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.
Click to expand...
Click to collapse
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.

Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.

Ritwik7 said:
Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.
Click to expand...
Click to collapse
My friend can you guide where i can find this .zip because i m facing the same problem.thank you in advance

Ok I got it to stick by using Root Explorer to mount it as read/write first then ran the sticky.bat. ICS is the rm /etc/install-recovery.sh command.

m.sabra said:
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.
Click to expand...
Click to collapse
I tried this and when I want to do the sticky.bat, when I type the "rm /etc/install-recovery.sh" it sais rm failed for /etc/.., Read-only file system

I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966

karx23 said:
I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966
Click to expand...
Click to collapse
thanks ! added the link to the OP in case anyone had problems like this.

Argh, I seem to have successfully unrooted my Nexus S 9020t and had it rebooted back in, but while it was booting up again I accidentally pressed a button and it told me "error: device not found" twice followed by "<waiting for device>".
Unfortunately my phone has already been rebooted, but it still seems to be waiting for my device. I'm not sure if I can disconnect this device from USB while this is going on, so uh, what do I do?
Edit: Disconnected and reconnected the USB cable on the phone to see what would happen, and it seems to be ok. I'm still stuck on "waiting for device" though. Should I consider restarting the process again?
Edit Edit: Decided to just try to redo the process all over again...seems to have worked!

Updated tool to version 2.0 ! check the changelog in OP, it should solve all sticky recovery related problems,as i removed sticky.bat and now the recovery will stick automatically without the need of running any commands or flashing any fixes.
thanks for reporting problems and feedbacks

thank you for this

Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?

Lelouche said:
Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?
Click to expand...
Click to collapse
Ok first have you unlocked your bootloader when the tool asked you to use volume buttons to chose yes and unlock ? (If you did this you should see an unlocked lock under google logo when booting the phone) if you didn't just run the script again and unlock the bootloader.
Are the drivers installed properly ? When you connect the phone to the pc check device manager to see if the PC recognizes the phone (the drivers are included in the tool in case you need them .
And last check the root tool folder on your pc it should have a file called cwm.img if it doesn't then download the tool again.

SuperUser is not visible after the process
I am on stock ICS, I had previously unlocked the bootloader, then I did the whole process mentioned in this thread. It showed me the CWM menu but when I did the reboot, I couldn't find the superuser app. Then to test whether it is rooted or not, I installed titanium backup but it says the device isnt rooted. What to do now? I tried SuperOneClick but it doesn't seem to work.
Edit: Thanks guys, sorry. It was my mistake, I didnt do the whole process in a right way. It is working as expected.

[ROOT][CWM] Root Nexus 4 & Install Official ClockworkMod Recovery

I originally posted this method at AddictiveTips. The method I posted there is targeted at everyone including the absolute beginners and I have also included instructions there for setting up the required tools, and for reverting back to the original recovery and boot image in case anything goes wrong. All external credits should be given to that guide (it does link back to this thread). Here is the link: How To Root Nexus 4 and Install ClockworkMod Recovery on it.
To my knowledge, this is the first confirmed working rooting method for Nexus 4 posted here at XDA. Though my knowledge is limited, so please correct me if I am wrong.
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
This method requires an unlocked bootloader. You can find instructions for unlocking it at XDA, or at the AddictiveTips guide linked above (the link to the bootloader unlock guide is in the requirements section there).
UPDATE 2: If your device does NOT get wiped after unlocking the bootloader, fret not. While this isn't expected behavior, several users have experienced the same on the Nexus 4. This could be due to some error at Google's end, but unlocking still works perfectly fine.
That said, let's get on with rooting and flashing CWM.
ClockworkMod Recovery Method:
Download the latest official ClockworkMod recovery from CWM website and rename it to recovery.img
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Download the recovery flashable SuperSU package with Busybox and transfer it to your phone's internal SD card.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Enter this command in a command prompt to flash the ClockworkMod recovery (making sure you are in the directory where you downloaded the recovery file):
Code:
fastboot flash recovery recovery.img
OR
If you simply want to root without flashing a custom recovery and want to stick to your stock recovery, simply boot this recovery once using this command:
Code:
fastboot boot recovery.img
If you flashed the recovery in the previous step, you can now boot into recovery by pressing volume-up or volume-down twice to select the recovery option, and then the power button to enter it. If you simply booted into the recovery file without flashing it in the previous step, you should already be in recovery now.
Once in recovery, take a backup to be on the safe side.
Flash the downloaded SuperSU and busybox package zip file from recovery.
Clear cache and dalvik cache just in case (not required but won't hurt).
Reboot the device.
ADB and Insecure Boot Image Method:
Grab the insecure boot image from this thread.
Also download these root files. This package includes the latest SuperSU 0.98, latest su binary that comes with it, and working busybox (not sure if latest).
Extract the contents of the downloaded zip file to your computer.
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Get back into bootloader mode and boot into the downloaded insecure boot image:
Code:
fastboot boot boot.img
Don't worry, this will not replace your existing boot image and will only boot from the insecure one once.
If it does NOT work for you and you get stuck in a boot loop, simply reboot your phone into bootloader and use the above command again. Some users had issues with booting from it the first time, but a second attempt worked.
Once booted into Android successfully using the insecure boot image, simply enter these commands one by one in command prompt (making sure you are in the directory where you downloaded the files):
Code:
adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
Reboot your device.
You will now have root access. Tested and confirmed working by Stryder5 and many others.
Credits:
Stryder5 for testing, confirming, tipping me about working CWM, providing the required drivers, and helping others on the thread. :highfive:
Harry GT-S5830 for the insecure boot image.
fkrone for his recovery revert disabler script and his unofficial working CWM before an official one became available.
Kstarz for posting this same recovery method with his own working CWM in this thread before an official one was out.
evaradar for informing about the release of official ClockworkMod recovery.
Koush for developing ClockworkMod recovery.
Chainfire for developing SuperSU.
Everyone else on this thread for testing, providing feedback and hitting the 'THANKS' button. =)
I have tried my best to give everyone the due credit but if I have missed out on anyone, please do remind me.

Yep, worked like a charm. Got Titanium running and restored all my apps
Btw, check your PM.

Checked...thanks. =) Added the links.

stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied

jshaw06 said:
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
Click to expand...
Click to collapse
You need to boot the unsecure boot.img first.

BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.

HQRaja said:
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
Click to expand...
Click to collapse
I'm pretty sure I used the one Harry GT-S5830 provided.

I used the one in the OP of that thread.. is there a different one I'm supposed yo use?
Sent from my SGH-T999 using Tapatalk 2
---------- Post added at 06:41 AM ---------- Previous post was at 06:23 AM ----------
It works
Sent from my SGH-T999 using Tapatalk 2

jshaw06 said:
It works
Click to expand...
Click to collapse
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.

Stryder5 said:
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Click to expand...
Click to collapse
No issues with installing the OTA after root?
Edit: Just noticed in your sig that you did not install the update.

I installed after ota
Sent from my SGH-T999 using Tapatalk 2

jshaw06 said:
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You mean you gained root after you installed the OTA?
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
apzalo said:
No issues with installing the OTA after root?
Click to expand...
Click to collapse
I gained root, but haven't installed the OTA yet.

when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?

Yes sorry gained root after OTA
Sent from my SGH-T999 using Tapatalk 2

Elemenopee said:
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Click to expand...
Click to collapse
Nope, it isn't. Try again...it's safe to try as many times as you want since we're not flashing the boot image; merely booting from it, which is temporary and doesn't last after reboot. Hope it works on the next try.

After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!

quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?

Ngo93 said:
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
Click to expand...
Click to collapse
Step 8 itself will boot up the phone normally into Android, just using that insecure boot image instead of the stock one. And yes, you then just start entering those adb commands. =)

0.0 said:
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Click to expand...
Click to collapse
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.

HQRaja said:
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
Click to expand...
Click to collapse
so i extract the "occam-jop40c-factory-cd3dc140.tgz" file, then double-click the "flash-all.bat" file?

Tried to Install TWRP, I think I deleted Android...

I was following originally this guide by a user who posted steps that would basically allow me to move all of my apps from my internal storage to external SD card. The link to the thread I had posted about this can be found here: http://forum.xda-developers.com/lg-l90/general/internal-memory-storage-help-t3171582/post62245649
I managed to root my phone using the KingRoot method, right after, I installed Flashify, flashed the TeamWin Recovery Project, and right after, it automatically rebooted me. After that, I went to the reboot section, clicked on recovery, and than, it loaded me to an icon where the Android logo is opened from its belly with a red triangle with the ! mark inside the red triangle.
I am assuming that my Android OS was deleted, as I see I now have 3 GB of free internal storage space. I originally was running everything on stock. Is there any solution here? I did manage to install CM12.1, but I forgot to flash GAPPS, thus I had to manually download the Flashify and KingRoot APK's and ended up deleted CWM12.1 as it just seemed buggy.
At this point, I want to just go back to my normal Android, I am fine with using Stock, as long as I have free storage. Though, if using another ROM would be better (where battery life improvements and overall faster performances is always acceptable). I don't want to brick my phone, as it so far seems to be working.
I currently don't have any other backup phone on me, so I would love to solve these issues ASAP as I do need my phone to make calls and answer SMS Text Messages.
Thanks!

What is your L90 variant?
You probably messed just the system and boot, CM12.1 and other custom roms currently runs with KitKat bootstack, and you may flashed them with Lollipop bootstack. Try to boot holding PWR + VOL DOWN, wait for LG logo show up, immediately release PWR button and hold again (don't release VOL DOWN). If you aboot is fine, you'll be shown a white screen asking if you wan't to reset your phone. If you still have your stock recovery, your phone will actually be reseted to stock, if you changed the recovery to TWRP or CWM, it will boot into them.
From the recovery you can create the right .zip to flash stock system and boot images retrieved from your kdz of your phone with LG Fimrware Extract. If you are able to flash them back, you won't need Kingroot, since your bootloader is unlocked, you can root your phone straight from the recovery with SuperSU flashable zip.
If none of the two options happen, you probably messed your aboot or recovery partition.

F. Gacrux said:
What is your L90 variant?
You probably messed just the system and boot, CM12.1 and other custom roms currently runs with KitKat bootstack, and you may flashed them with Lollipop bootstack. Try to boot holding PWR + VOL DOWN, wait for LG logo show up, immediately release PWR button and hold again (don't release VOL DOWN). If you aboot is fine, you'll be shown a white screen asking if you wan't to reset your phone. If you still have your stock recovery, your phone will actually be reseted to stock, if you changed the recovery to TWRP or CWM, it will boot into them.
From the recovery you can create the right .zip to flash stock system and boot images retrieved from your kdz of your phone with LG Fimrware Extract. If you are able to flash them back, you won't need Kingroot, since your bootloader is unlocked, you can root your phone straight from the recovery with SuperSU flashable zip.
If none of the two options happen, you probably messed your aboot or recovery partition.
Click to expand...
Click to collapse
I think I did mess with my stock recovery boot, and instead TWRP is set as my boot. When I pres the VOLUME down and Power button, I get prompted to a White screen that says "Erase all user data and restore default settings?", after I select "Yes", and "Yes" again, it shows "Factory Reset Performing". Than a quick animation of the Android logo with gears running behind it, after that it looks like it reboots, but right back to Team Win Recovery Project. From there, when I select Reboot, and recovery, it just shows the Android logo with the red triangle.
What are my options from here? I should mention, when I select the option "Reboot" in TWRP and go to "Recovery", it does say "No OS Installed!" , after swiping it than says "Install SuperSU? Your device does not appear to be rooted. Install SuperSU Now?".
Is there a proper way to also root the device, since it seems to be rooted, even though I swipe to install SuperSU?
EDIT: I also have a LG L90 D415.

If TWRP is booting, you are fine. TWRP is your new recovery, takes place of the stock LG recovery.
I don't know how many variants L90 have, you are D415RD or its a different model? If it's the same D415 you said, you can flash the D415RD zip with TWRP from this topic: http://forum.xda-developers.com/lg-...flashablestock-zip-kk-l-via-recovery-t3137255 (use Lollipop if you were at LL before, use KitKat if it was KK. You cannot downgrade to KK if you were on LL before, they are different bootstacks).
I suggest before flashing, wipe > adv wipe > dalvik/system/data/internal storage (your internal sd data will be wiped)/cache - do NOT format sdcard, it's your microSD with the necessary zip files to go back to stock. Go back and format data, type yes. Go back to home menu, reboot > recovery so your data get remounted and accessible again (ignore warnings saying there is no android installed and asking to install super user). Install > select the zip and wait. You can also flash SuperSU to get root (do after flashing the rom): https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip

F. Gacrux said:
If TWRP is booting, you are fine. TWRP is your new recovery, takes place of the stock LG recovery.
I don't know how many variants L90 have, you are D415RD or its a different model? If it's the same D415 you said, you can flash the D415RD zip with TWRP from this topic: http://forum.xda-developers.com/lg-...flashablestock-zip-kk-l-via-recovery-t3137255 (use Lollipop if you were at LL before, use KitKat if it was KK. You cannot downgrade to KK if you were on LL before, they are different bootstacks).
I suggest before flashing, wipe > adv wipe > dalvik/system/data/internal storage (your internal sd data will be wiped)/cache - do NOT format sdcard, it's your microSD with the necessary zip files to go back to stock. Go back and format data, type yes. Go back to home menu, reboot > recovery so your data get remounted and accessible again (ignore warnings saying there is no android installed and asking to install super user). Install > select the zip and wait. You can also flash SuperSU to get root: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Click to expand...
Click to collapse
Ah okay, great, so I can easily fix this solution Just a question here - after performing this, when I go back to Stock, would it be recommended to just stick with it? I did some searching for fast Lollipop ROMs, and there are only a few out there from my search...
Also - Next time, is there a better way to do all of this? I was originally trying to install Xposed as a previous user had posted on these forums, that it allowed you to do a multitude of things additional to the whole Link2SD access.

Stick to the stock ROM.
TWRP is the best way of doing all of this, there nothing more easy than simply booting TWRP recovery and flash a zip file. Forget LG recovery and KDZ flash, TWRP is much better. TWRP allow to flash select partitions, thus preserving your unlocked bootloader and custom recovery.
If you are talking about all the partition format and reboot things I said, that actually is not really necessary, but since you tried to make some other changes other than simply flashing a new rom, I just wanted to make sure you were making a clean flash and first boot to avoid any obscure errors.
I don't know what is the current development status of Xposed in android LL and the recovery flasheable zip for our L90, but the last time I checked it wasn't stable and could lead to lots of FC to an unbootable system, so I just skiped any modification at this level.

F. Gacrux said:
Stick to the stock ROM.
TWRP is the best way of doing all of this, there nothing more easy than simply booting TWRP recovery and flash a zip file. Forget LG recovery and KDZ flash, TWRP is much better. TWRP allow to flash select partitions, thus preserving your unlocked bootloader and custom recovery.
If you are talking about all the partition format and reboot things I said, that actually is not really necessary, but since you tried to make some other changes other than simply flashing a new rom, I just wanted to make sure you were making a clean flash and first boot to avoid any obscure errors.
I don't know what is the current development status of Xposed in android LL and the recovery flasheable zip for our L90, but the last time I checked it wasn't stable and could lead to lots of FC to an unbootable system, so I just skiped any modification at this level.
Click to expand...
Click to collapse
YES! I was able to boot back into Stock ROM, but further more, I have root access via SuperSU! I was able to do the Link2SD method, and removed a bunch of the bloatware pre-installed on the ROM, it all works now! Thanks a lot for helping on all of this!
After spending literally my whole day trying to get my phone root acces, I think I will stick to Stock, everything works, and I don't want to kill another day trying to accomplish a miniscule achievment, since I already have Root access.
Now, one of my last questions: is there an appropriate way for me to boot into TWRP? Every time I reboot, I go straight to my ROM, not sure how to go back to TWRP (in the case I ever need to flash something again).
Otherwise, my phone works, and I was able to achieve my original goal of freeing up internal space.
Any cool tips or advice you recommend to possibly speed up or just enhance the Stock ROM now that I have root access?
Sent from my LG-D415 using XDA Free mobile app

I recommend to remove the software after flashing in TWRP, before doing the first boot, just mount /system and open ADB. If you do this after install, there is probably a lot of .dex files and app data remaining taking precious storage.
For example, if you update Youtube, Gmail and other pre-installed apps, after update they won't be removed, instead the new version will be renamed to something like com.google.youtube-2 and the previous version will remain in /system, you can notice this if you go to your app list in setting and try to uninstall, android will say that the version will be reverted to the stock one that shipped in the stock rom.
Here's a list of stuff and apps I removed before booting:
rm /system/usbautorun.iso
rm -r /system/app/Books
rm -r /system/app/ChromeWithBrowser
rm -r /system/app/Drive
rm -r /system/app/Gmail2
rm -r /system/app/GoogleTTS
rm -r /system/app/Hangouts
rm -r /system/app/LGSearchWidgetProvider
rm -r /system/app/Maps
rm -r /system/app/Music2
rm -r /system/app/Newsstand
rm -r /system/app/PlayGames
rm -r /system/app/PlusOne
rm -r /system/app/Street
rm -r /system/app/talkback
rm -r /system/app/Videos
rm -r /system/app/YouTube
rm -r /system/apps/bootup/LGBoxnet
rm -r /system/apps/bootup/LGFlashlightWidget
rm -r /system/apps/bootup/LGSmartWorld
rm -r /system/priv-app/LGBrowser
rm -r /system/priv-app/LGDictionary
rm -r /system/priv-app/LGEmail
rm -r /system/priv-app/LGFileManager
rm -r /system/priv-app/LGMemo
rm -r /system/priv-app/LGQTranslator
rm -r /system/priv-app/Velvet
rm -r /system/vendor/carrier/system/LGRemoteCall
rm -r /system/vendor/carrier/system/rspermlge
rm -r /system/vendor/overlay/com.android.browser
rm -r /system/vendor/overlay/com.lge.email
rm -r /system/vendor/overlay/com.lge.filemanager
rm -r /system/vendor/overlay/com.lge.lgworld
Of course, this is MY case, I removed applications that I thought not to be necessary to me. Apps such as Gmail, Youtube and etc I installed the most recent version from play store. Note that some apps cannot be removed or your cannot go past the setup wizard (the first screen after the first boot) e.g.: webview.
Don't try to install Xposed Framework, you will end with a lot of FC that will render the system unusable, I tried and didn't worked, but I had a TWRP backup and was just a matter of reverting everything.
Also, disable automatic system update. If you leave this checked in the settings and your phone updates, you will end in a soft brick.
To go to recovery you have 2 ways:
1 - Install Android Terminal Emulator, type su, then reboot recovery.
2 - Turn off your phone. Hold PWR + VOL DOWN, wait for LG logo show up, immediately release PWR button and hold again (don't release VOL DOWN). Don't worry, since you have TWRP recovery installed instead of LG recovery, your data won't be reseted, instead it will boot into TWRP.
I personally don't like the this second method because it's a good way to worn out your pwr and vol buttons, my previous phone was a LG Optimus 2x and the pwr/wake button became almost unusable after some time, I need to press very hard to work, use this second method only if you cannot boot into recovery from the OS.
To avoid always typing those command in Android Terminal Emulator, you can create a shortcut widget, just type reboot recovery in the argument, name the shortcut and it's done, everytime you tap the shortcut it will automatically open the terminal and reboot the phone. Don't forget to configure the app. to open always with su or the shortcut won't work (reboot command needs superuser access).

Xposed framework works in our L90 Lollipop, as long as you follow those steps I found @ reddit: https://www.reddit.com/r/LGL90/comments/3f8ycw/guide_how_to_install_xposed_framework_on_lollipop/
If you skip disabling the apps mentioned and clearing cache and dalvik, you will end in a infinite number of force closes and crashes, rendering the system unusable.
Of course, like always, do a system/boot/data backup with TWRP, if anything goes wrong, you'll be able to go back.
After the first boot a window will be shown saying that android system is updating some stuff, this will take a few minutes don't worry.
I installed LG Pie Support module to remove that annoying home google search ring when swiping from navigation buttons to screen.
Lollipop Memory Leak Fix module seems to have no effect tbh.

Cannot uninstall/install framework after backup restore

Dear community,
I installed xposed using the following adk: XposedInstaller_3.0_alpha4.apk then flash, from recovery, the framework for my Oukitel K6000 Pro (Android 6.0): xposed-v86-sdk23-arm64.zip
All worked fine until I have to restore a backup from recovery (backup taken before I flash the framework).
Now, Xposed cannot see the framework, so I tried to uninstall it using xposed-uninstaller-20150831-arm64.zip always from recovery. The uninstallation seems goes ok, so I reboot the device, enter again into recovery to flash again the xposed-v86-sdk23-arm64.zip
Unfortunately I got an error during install process:
chown: /system/bin/dex2oat.orig.gz read only file system
or
cp: can't create '/system/xposed.prop' File esists
And the installation stop there.
Could someone help me to reinstall the framework and come back to working status?
Thank you
Lucas

Lord Spectre said:
Dear community,
I installed xposed using the following adk: XposedInstaller_3.0_alpha4.apk then flash, from recovery, the framework for my Oukitel K6000 Pro (Android 6.0): xposed-v86-sdk23-arm64.zip
All worked fine until I have to restore a backup from recovery (backup taken before I flash the framework).
Now, Xposed cannot see the framework, so I tried to uninstall it using xposed-uninstaller-20150831-arm64.zip always from recovery. The uninstallation seems goes ok, so I reboot the device, enter again into recovery to flash again the xposed-v86-sdk23-arm64.zip
Unfortunately I got an error during install process:
chown: /system/bin/dex2oat.orig.gz read only file system
or
cp: can't create '/system/xposed.prop' File esists
And the installation stop there.
Could someone help me to reinstall the framework and come back to working status?
Thank you
Lucas
Click to expand...
Click to collapse
Try clearing art/dalvik and cache then reboot directly back into recovery and flash Xposed again
Sent from my SCH-R220

Thank you for reply mattzeller, unfortunately, after cleaning art/dalvik and cache and reboot directly into recovery to install sdk I got the same error:
chown: /system/bin/dex2oat.orig.gz read only file system

Lord Spectre said:
Thank you for reply mattzeller, unfortunately, after cleaning art/dalvik and cache and reboot directly into recovery to install sdk I got the same error:
chown: /system/bin/dex2oat.orig.gz read only file system
Click to expand...
Click to collapse
Try mounting system as read/write in recovery before flashing
Sent from my SCH-R220

mattzeller said:
Try mounting system as read/write in recovery before flashing
Click to expand...
Click to collapse
I believe you mean from terminal, could you please share the command to do that? Thx!
However I see from recovery log, during uninstall/install processes:
Mounting /system and /vendor read-write
So, packages already tried to mount system... Maybe fails, I don't know!!!

Lord Spectre said:
I believe you mean from terminal, could you please share the command to do that? Thx!
However I see from recovery log, during uninstall/install processes:
Mounting /system and /vendor read-write
So, packages already tried to mount system... Maybe fails, I don't know!!!
Click to expand...
Click to collapse
In recovery open terminal :
mount -o rw,remount /system
Then try to flash Xposed
Sent from my SCH-R220

DAMN!DAMN!DAMN! This is what I done on terminal:
# mount -o rw,remount /system
Try to flash xposed-v86-sdk23-arm64.zip
Got: cp: can't create '/system/xposed.prop' File esists
Then from terminal:
# rm /system/xposed.prop
rm: can't remove '/system/xposed.prop': Read-only file system
At this point I don't know how can I proceed. Maybe flashing stock rom, then install framework from recovery, and then restore backup

Just to inform that I solved reflashing stock rom, recovery TWRP and SuperSU... Then flash again the Xposed SDK. Unfortunately I cannot use the TWRP backup, and I had to configure my phone from scratch.

Lord Spectre said:
Just to inform that I solved reflashing stock rom, recovery TWRP and SuperSU... Then flash again the Xposed SDK. Unfortunately I cannot use the TWRP backup, and I had to configure my phone from scratch.
Click to expand...
Click to collapse
Sounds like something in your backup got screwed up I would suggest deleting that back up once everything is set up and redoing it
Sent from my SCH-R220

Can't flash my recovery to TWRP on LineageOS

Hello dear fellows,
since 2 days i try to fix a problem with my unlocked and rooted Sony Xperia Z C6603. Still not finding any solution via internet, i take my last chance and post it here.
I unlocked and rooted my C6603 2 days ago and installed via fastboot the actual Lineage Custom ROM lineage-14.1-20171027-nightly-yuga-signed.zip.
Everything worked fine.
Bootloader -> fastboot flash boot boot.img (from lineage-14.1-20171027-nightly-yuga-signed.zip) :good:
Restart into Android Recovery :good:
Install via ADB sideload lineage-14.1-20171027-nightly-yuga-signed.zip :good:
Install via ADB sideload LineageOS 14.1 ARM32 SU (for full root access) :good:
Boot into Lineage, activate dev options and enabled Android-Debugging + Root-Access -> Apps and ADB :good:
Now my problem:
The so called "Android Recovery" is rly bad, so i try to override this recovery with TWRP 3.0.2.0 (yuga) but everytime i get the following error:
Code:
fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10656 KB)...
OKAY [ 0.351s]
writing 'recovery'...
[B]FAILED (remote: Command not allowed)[/B]
finished. total time: 0.370s
Where is my fffffff problem^^ Yes my phone is unlocked and yes, it is rooted (checked it also via root app).
I cant install gapps (dont work with ADB sideload) and and i want a proper recovery for backups and stuff...
So, what is wrong with me? Maybe someone of you have a good idea and can help me, i would rly appreciate it!
Sry for my not so proper english, hope u understand my problem anyway
Phone information:
Sony Xperia Z C6603
Android 7.1.2
LineageOS 14.1-20171020-NIGHTLY-yuga
LineageOS API-Level Guava (7)
Kernel-Version 3.4.113-yuga-gd710842
Build-Number lineage-yuga-userbug 7.2.1 NJH47F f281cb28f4

Thanx for all the help^^
I figured it out what to do:
1. fastboot flash boot twrp(actualversion).zip NOT fastboot flash recovery twrp(actualversion).zip
2. reboot into TWRP recovery mode
3. check if u can mount your data folder
3.1 if not, go to wipe -> advanced wipe -> change file system to ext4
4. install via ADB the actual LineageOS (or put the actual LineageOS file on your Sony/SD)
4. install LineageOS 14.1 SU via ADB (or put the actual LineageOS 14.1 SU file on your Sony/SD) -> https://www.lineageosroms.org/forums/topic/how-to-root-lineage-os-13-14-1-marshmallow-nougat-rom/
6. install Open gapps -> http://opengapps.org/
7. reboot and configure LineageOS
7.1 check your developer options -> Debugging + root access for ADB and apps
8. download TWRP apk via PlayStore
8.1 give TWRP apk root access and download the actual TWRP file for yuga
9. flash this TWRP recovery via app
10. DONE
Everything works fine (for now )
Topic can be closed!

Same problem here, filesystem is ext4, TWRP app says it flashed but after a reboot its not there.
Always have to go via "fastboot flash boot twrp.img" and on the next reboot after flashing lineage its gone again.
After some research I found it it belongs into the fota partition, but I dont seem to have one.

nurps said:
Same problem here, filesystem is ext4, TWRP app says it flashed but after a reboot its not there.
Always have to go via "fastboot flash boot twrp.img" and on the next reboot after flashing lineage its gone again.
After some research I found it it belongs into the fota partition, but I dont seem to have one.
Click to expand...
Click to collapse
Did you manage to solve the issue? I have the exact problem. The TWRP says it flashed but recovery is still stock android.

I have C6602. Someone on reddit gave me the solution; (do note that I had to run
Code:
adb root
for
Code:
su
to work.
You have a Xperia device which deals with recovery kind of weird. Recovery is stored with the kernel, not in a standalone recovery partition. Because of this you need to flash it to a FOTAKernel partition and use a kernel that supports FOTAKernel (the LineageOS one does).
To flash TWRP, first move the recovery image to your device with the adb command
Code:
adb push twrp-3.0.2-0-yuga.img /sdcard
. Then run
Code:
adb shell
to get access to the shell. Then run
Code:
su
and accept any prompts to gain root access. Then to actually flash, run
Code:
dd if=/sdcard/twrp-3.0.2-0-yuga.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Click to expand...
Click to collapse