Database Develop

I NEED to get Clockworkmod Recovery on my phone, but I can't seem to get it to work

I got my phone back just 3 days ago and figured i'd finally customize it. I FINALLY figured out a safe and full-proof way of rooting my samsung galaxy s i9000M. I FINALLY figured out that I need to switch the <3e> recovery to <2e> recovery so that I'm able to flash custom ROMs.
Here's the annoying part...
I STILL can't set up Clockworkmod recovery instead of the stock recovery menu. The tutorial I'm following specifies that I need this recovery in order to get everything workin.
I have the phone rooted and I have ROM manager installed too.
Won't someone tell me how to install it on my phone?
I've tried this website:
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-3-using-rom-manager/
didn't work many times
thanks in advance!

stacyluo said:
Hi, I'm new to this forum.
Click to expand...
Click to collapse
gotta start somewhere

I should point out, it keeps saying "can't open /sdcard/update.zip"
(no such file or directory) if that helps

You mean you don't have recovery yet or you can't install any zip files?
Sent from my GT-I9000 using XDA Premium App

You'll probably need to do it via Odin.
If you look at the guides here on XDA you'll see easily how to do this.
There are probably easier ways to do by now, but you can follow the more traditional method without much difficulty and not really with that many screw up chances.
Just grab a custom Kernel, like SpeedMod or so, for Odin installation.
Follow the steps that you'll see on the Odin guide to install just the Kernel. Once that is done the Recovery mode will be altered and you can start using CWM normally from there on (or until you install some other full ROM that replaces the kernel and recovers the official recovery mode).

[Q] CWM not flashing on my phone...PLEASE HELP!

Hi Everybody,
So it goes like this. I rooted my phone for the first time and I backed up using Titanium Backup. then i downloaded rom manager. Within rom manager i flashed CWM. When i get to recovery mode and i try to reinstall packages it starts a download and a quarter of the way it gives me an error like "Failed to verify whole file signature"...and installation was aborted. After trying other varius methods posted like uninstall rom manager and rebot your phone and try again. I still had no success. So in recovery mode i thought maybe if i delete my internal storage and user data with cache data it might work (not knowing what deleting user data did). after my process of getting the phone on track i checked to see if my phone was still rooted. In my applications folder i had superuser permissions so i assumed it was still rooted. I went straight to market and downloaded Rom Manager, and tried again to flash CWM. Went into recovery and i had no success, it still gave me the same error message. I downloaded Titanium Backup to restore my files (i copied my internal storage device so i have titanium backup's files that i backed up) and when it loaded up the application said that the phone is not rooted.
So to get to the point. HOw can i get CWM on my phone? and Why was titanium backup saying my phone is not rooted when i have superuser permissions and rom manager was also using it?
Thank you.

Is your stock recovery 3e?....

That is what it is, you need to look in the development section for the modded 3e recovery thread, and follow those directions!
Sent from my SAMSUNG-SGH-I897 using xda premium

It's in the sticky roll up on to if the general section...

b-eock said:
That is what it is, you need to look in the development section for the modded 3e recovery thread, and follow those directions!
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Can you please post a link to the thread.

xhambone786x said:
Can you please post a link to the thread.
Click to expand...
Click to collapse
Yahh just. Sec!
http://forum.xda-developers.com/showthread.php?t=909213
Sent from my SAMSUNG-SGH-I897 using xda premium

Its a sticky. Look in the "Read BEFORE flashing!!" thread and "The Captivate Directory |Guides|ROMs|Themes|Etc.| READ BEFORE POSTING(Updated 9/7/11)" thread.... use the search as well....

Question about Bootstrapper and Clockwork Mod

I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.

Lyxdeslic said:
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Click to expand...
Click to collapse
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App

erismaster said:
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?

I think he's saying to not use rom manager at all. You can flash roms from cwm recovery.
Edit: just to clarify I mean by booting into recovery using the bootstrapper and flashing a rom from there to avoid any issues caused from the rom manager
Sent from my rooted xt860

Lyxdeslic said:
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
Click to expand...
Click to collapse
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App

erismaster said:
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.

Lyxdeslic said:
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Click to expand...
Click to collapse
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App

erismaster said:
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info man.

[How to] Stock to Stock/CM9 Dual Boot

I've been struggling installing custom roms on my phone so I figured I'd document the process to help out anyone else starting out. I'd like to thank everyone for helping me figure this out and for the hard work of the community for making this possible.
Edit: My goal was to come up with a way to install CM9 while leaving the original system it came with and all my settings and apps. I understand how to do TitaniumBackup and how to save specific apps/files to but I wanted an exact backup of my original system alongside any custom rom so I just wrote down the steps I used to make it happen.
Root the system
1.First apply one click root using this tool
Further instructions here: http://forum.xda-developers.com/showthread.php?t=1319653
http://dl.xda-developers.com/attach.../7/6/DooMLoRD_v4_ROOT-zergRush-busybox-su.zip
Droid 3 CWM (ClockWorkMod)
2. Install this apk onto the phone and click the first button then the second button
http://forum.xda-developers.com/attachment.php?attachmentid=882933&d=1328117678
3. Boot into recovery and make a backup of your system
4.Apply Fastboot package for UMTS XT860 Iusacell Mexico using RSD Lite 5.5
Further instructions here:
http://rootzwiki.com/topic/4370-sbf...959-and-56890/page__view__findpost__p__100987
XT860 Iusacell: http://www.fileserve.com/file/cgdZ2..._SLU-57M-111107-release-keys-Latam-01.xml.zip
RSD Lite: http://www.multiupload.com/T6NOEBKKLO
5. Reroot using 2.3.6 Zerg tool
Basically after flashing with RSD Lite then re-root using this tool:
http://dl.xda-developers.com/attach.../7/6/DooMLoRD_v4_ROOT-zergRush-busybox-su.zip
6.Re-install CWM (Droid 3 Bootstrapper from step 2) and then apply the Bell rar file as a nandroid restore.
Further instructions here: http://forum.xda-developers.com/showpost.php?p=21446640&postcount=112
https://rapidshare.com/files/1705579381/ClockworkMod_v.5.0.2.6_Bell_2.3.6.rar
7. Reboot into the system and let the OS load again then re-install cwm (no need to reroot) and reboot back into recovery.
the trick to booting into recovery the second time is to turn the phone off, hold the m key while pressing the power button, plug in the phone to usb, choose bp tools
source: http://forum.xda-developers.com/showpost.php?p=21474818&postcount=120
restore your original backup from step 3 using advanced restore and restore the Data only and then wipe cache and dalvik cache
8. Remove CWM and install safestrap instead it involves using adb shell and removing certain files instructions found here:
http://www.droidforums.net/forum/dr...d-help-removing-clockworkmod.html#post1801072
9. Install SafeStrap once CWM is removed just install it, reboot and press the menu key while booting
http://dl.xda-developers.com/attach...5/7/9/2/5/Droid3_Safestrap_Tweaked_v1.08d.apk
10. ICS Install, at this point you have prepped your system so you can install CM9 otherwise it won't boot on the stock Bell 2.3.4
Instructions here: http://forum.xda-developers.com/showpost.php?p=22254669&postcount=61 (start at step 8 or 9 in those instructions)
-Apply CM9 Alpha 6 Zip
http://www.hash-of-codes.com/files/cm9-droid3-20120130-1730.zip
-Apply XT860 Sub-Patch (by Rick#2) for ICS Zip
http://bit.ly/Ah5b6d
Further instructions here: http://hash-of-codes.blogspot.com/p/how-to-safestrap.html

Great tutorial
As a note, in step 6, you could flash any custom rom to /system. You might not be able to restore /data though. Can try and if no go do a data wipe. If you backup apps with titanium backup and call logs/sms/mms with mybackroot its not such a big deal. Just redownload those 2 apps and restore everything(honestly I rarely nandroid, only if im doing something im confident will end in a fastboot flash, I just use those 2 apps). Im running liberty in /systemorig and eclipse in /system
Sent from my XT860 using xda premium

Also zergrush should root anything I believe 2.2.x and up. You could save the hassle of getting one click. AFAIK anyways. When I first rooted I used the one click as well(way back when it first came out)but I know it roots 2.3.5 and 2.3.6 and works on other models as well. Originally for one of the Sony experia phone
Sent from my XT860 using xda premium

Endoroid said:
Also zergrush should root anything I believe 2.2.x and up. You could save the hassle of getting one click. AFAIK anyways. When I first rooted I used the one click as well(way back when it first came out)but I know it roots 2.3.5 and 2.3.6 and works on other models as well. Originally for one of the Sony experia phone
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Thanks for the tip I wouldn't have been able to get this far without your help Endoroid. I'll edit the How-To to use the same root twice, I wish mods would sticky more useful posts like zerg's root instead of pete's root and How-To such as this one.

Thanks for the detailed tutorial. I'm on Bell 2.3.6, rooted. Step 2 did not work for me. I could install the program (droid3 CW bootstrap) and click the first button (with "success" popup), but reboot into recovery would not work. It would simply boot up normally. If I held "m" down then I could get to the blackscreen menu, scroll down and select BP tools, but still, a normal bootup would follow.
I used root explorer to check for what the bootstrap program did. In /system/bin/ directory was the "hijack" file as well as a modified "logwrapper" and the original "logwrapper" which was renamed to "logwrapper.bin". Uninstalling the bootstrap did not remove these. To manually uninstall, I removed hijack, logwrapper and renamed logwrapper.bin to logwrapper.
I also tried Koush's Rom Manager from the Market and selected "Droid 3" as the device, but it also would not achieve a boot into CWM Recovery menu.
I tried the two programs separately and then together, but it made no difference.
My next step was to try Safestrap Recovery v1.08 from hash-of-codes. This installed and has allowed me to boot into the green recovery menu after powering down fully, holding "m" and pressing the power button. On the next black screen, scrolled down to "bp tools" with volume down button and then pressed volume up to select it. I went into "backup and restore" and created a nandroid backup of my current 2.3.6 Bell system. (volume up/down to scroll, power button to select).
Sorry if I'm being verbose with the button presses but thought it might help for future reference and maybe for others as well.
Question now is which step to go to now... do I try using RSDLite to flash the fastboot package for Iusacell Mexico file? If I understand correctly, this will change the radio and also there is no going back at this point to stock Bell.
I'm concerned about warranty service if something goes wrong and there's no still no Bell SBF to flash back to stock. Would it be that noticeable? If I restored my nandroid backup, would I still be on the upgrade path with Bell? If I restored the backup and deleted safestrap recovery, would it show?

ncho2233 said:
Thanks for the detailed tutorial. I'm on Bell 2.3.6, rooted. Step 2 did not work for me. I could install the program (droid3 CW bootstrap) and click the first button (with "success" popup), but reboot into recovery would not work. It would simply boot up normally. If I held "m" down then I could get to the blackscreen menu, scroll down and select BP tools, but still, a normal bootup would follow.
I used root explorer to check for what the bootstrap program did. In /system/bin/ directory was the "hijack" file as well as a modified "logwrapper" and the original "logwrapper" which was renamed to "logwrapper.bin". Uninstalling the bootstrap did not remove these. To manually uninstall, I removed hijack, logwrapper and renamed logwrapper.bin to logwrapper.
I also tried Koush's Rom Manager from the Market and selected "Droid 3" as the device, but it also would not achieve a boot into CWM Recovery menu.
I tried the two programs separately and then together, but it made no difference.
My next step was to try Safestrap Recovery v1.08 from hash-of-codes. This installed and has allowed me to boot into the green recovery menu after powering down fully, holding "m" and pressing the power button. On the next black screen, scrolled down to "bp tools" with volume down button and then pressed volume up to select it. I went into "backup and restore" and created a nandroid backup of my current 2.3.6 Bell system. (volume up/down to scroll, power button to select).
Sorry if I'm being verbose with the button presses but thought it might help for future reference and maybe for others as well.
Question now is which step to go to now... do I try using RSDLite to flash the fastboot package for Iusacell Mexico file? If I understand correctly, this will change the radio and also there is no going back at this point to stock Bell.
I'm concerned about warranty service if something goes wrong and there's no still no Bell SBF to flash back to stock. Would it be that noticeable? If I restored my nandroid backup, would I still be on the upgrade path with Bell? If I restored the backup and deleted safestrap recovery, would it show?
Click to expand...
Click to collapse
First, you may wish to just go with safestrap and try flashing g rom in safe mode. If it bootloops no harm done because your bell /system is intact
If that fails you can try using motofastboot instead of rsdlite to just flash /system. You can restore your /system with your nandroid.
As far as I know roms should work with bell 2.3.6.
If you do end up flashing the whole fastboot package with rsdlite you can make your phone appear to be bell stock. You can restore your nandroid and then mod the build.prop so about phone shows bell info. The warranty guys would have to look deep to see its been changed.
Its up to you ultimately but as I said I don't think you would have to flash the fastboot. Safestrap should work as is on bell 2.3.6. As long as you don't mess with /systemorig (nonsafe mode) its easy to remove the evidence. Uninstall safestrap recovery and remove su/superuser
If I recall correctly dasilva had his issue due to being on 2.3.4 and unable to update.
Sent from my XT860 using xda premium

Thanks Endoroid. I went ahead and tried installing Rick#2's latest patched version of CM9 and to my great surprise it worked and the phone has booted up running ICS. I'm pretty happy since I didn't think this was possible without losing the ability to get back to Bell stock and right now, I think it's still possible since I didn't flash any other country's fastboot files. Is this right?

ncho2233 said:
Thanks Endoroid. I went ahead and tried installing Rick#2's latest patched version of CM9 and to my great surprise it worked and the phone has booted up running ICS. I'm pretty happy since I didn't think this was possible without losing the ability to get back to Bell stock and right now, I think it's still possible since I didn't flash any other country's fastboot files. Is this right?
Click to expand...
Click to collapse
Correct
Safestrap was built with the idea of keeping your phone intact. You can still easily receive OTA updates and can return your phone to stock if you need to get warranty repair done
Sent from my XT860 using xda premium

dasilva333 said:
XT860 Iusacell: http://www.fileserve.com/file/cgdZ2..._SLU-57M-111107-release-keys-Latam-01.xml.zip
Click to expand...
Click to collapse
This file is necessary, but alas fileserve is gone... All the links on the web point to just that one location.
Does someone have it? Can someone upload it?

白い熊 said:
This file is necessary, but alas fileserve is gone... All the links on the web point to just that one location.
Does someone have it? Can someone upload it?
Click to expand...
Click to collapse
+1

1of16 said:
+1
Click to expand...
Click to collapse
Personally, I like the Bell version the most, it has the least amount of Blur. You can find an entire SBF database here:
http://sbf.droid-developers.org/
Sent from my XT860 running ICS

danifunker said:
Personally, I like the Bell version the most, it has the least amount of Blur. You can find an entire SBF database here:
http://sbf.droid-developers.org/
Sent from my XT860 running ICS
Click to expand...
Click to collapse
Thanks, and I can use it on my XT862 too?
is it possible to install the latest OTA (5.7.906), which I want to use as stock rom?

[Video Guide] Installing TWRP Custom Recovery (D415)

Hey, my friends of the L90 Discussion Forums.
I know there was already a previously made text guide for this, but since some people like visuals, I made a quick video tutorial for it.
All the instructions and download links are in the description of the video. I'll paste them here just if you are too lazy to get the YouTube video open from the YouTube site.
Here's the video:
(Sorry for any wording mess-ups I made. I'm a better script/speech writer than I am a presenter.)
https://www.youtube.com/watch?v=vaGM-TtlRbM
__
I did not originally come up with how to get the bootloader. Credit to Quarx from XDA and his friends at 4pda.ru.
Ok, So, here are the instructions if you did not find it clear enough from the video, and got your **** stuck in a ceiling fan:
Requirements:
1. Root (Use Towelroot)
2. Terminal app (I used an app called Android Tuner Pro. Remember to enable SU when installing Recovery and rebooting or it may not work)
3. twrp.img - http://bit.ly/1IZ2BRn - download from google drive
Instructions:
1. Ensure that your phone is rooted.
2. Download and move twrp.img to internal sdcard (/sdcard)
3. Open up terminal app, ENSURE THAT YOU HAVE SU ENABLED, and type in this command:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17
3.5. If the command works, it should take a few seconds and it will say "11 MB has been transferred in so and so seconds"
4. After that, type in:
reboot recovery
It should then reboot into the newly installed TWRP recovery. Wait now, Why isn't anything working when I touch it? Well, TWRP has a small error that doesn't recognize touches the first time around, so wait till the screen times out after 60 seconds, turn the screen back on, and unlock. Then it should be usable. Remember to change the screen timeout to 15 if you don't want to wait.
There you go, that should be about it.
Enjoy!
Disclaimer: I do not take responsibility for damage done to your phone. You do this at your own risk.
See original instructions here: (go down to quarx's post) http://forum.xda-developers.com/showthread.php?t=2770938&page=31
__

That's a good video. Thanks for taking the time out to make it. Do you know where I can find towelroot? I tried www.towelroot.com, but it said that there were problems with the security certificate. I can't find it in the play store either.

EpicSaga said:
That's a good video. Thanks for taking the time out to make it. Do you know where I can find towelroot? I tried www.towelroot.com, but it said that there were problems with the security certificate. I can't find it in the play store either.
Click to expand...
Click to collapse
APK Attached.

I just installed TWRP on my LG D415, thank you.

EpicSaga said:
I just installed TWRP on my LG D415, thank you.
Click to expand...
Click to collapse
Oh, you're welcome! Hope you enjoy it!

Can I flash CM11 using TWRP after installing TWRP using this method, ? Is there a way to access TWRP Recovery by pressing a combination of buttons when the phone is rebooting? I tried to load TWRP Recovery by turning off the phone then pressing the volume down button and the power button, but I got the factory hard reset instead. I didn't do the factory data reset.

EpicSaga said:
Can I flash CM11 using TWRP after installing TWRP using this method, ? Is there a way to access TWRP Recovery by pressing a combination of buttons when the phone is rebooting? I tried to load TWRP Recovery by turning off the phone then pressing the volume down button and the power button, but I got the factory hard reset instead. I didn't do the factory data reset.
Click to expand...
Click to collapse
I have not tried flashing any ROMs or anything yet on it.
Also, I found a key combination, which is exactly the one you said. Problem is, the guide I read it from said you need to go through with the Erase Phone and whatever, and then it will load your recovery, but I'm not risking what I've done so far just to try to get into Recovery.
Instead, I made a small app that uses the Shell and Root to simply perform a reboot into Recovery by the press of a button.
Attached.
(916 KB compressed, 3.01 MB when installed)
WARNING: 4.0.3+ (API 15+)

Sadcamp said:
I have not tried flashing any ROMs or anything yet on it.
Also, I found a key combination, which is exactly the one you said. Problem is, the guide I read it from said you need to go through with the Erase Phone and whatever, and then it will load your recovery, but I'm not risking what I've done so far just to try to get into Recovery.
Instead, I made a small app that uses the Shell and Root to simply perform a reboot into Recovery by the press of a button.
Attached.
(916 KB compressed, 3.01 MB when installed)
WARNING: 4.0.3+ (API 15+)
Click to expand...
Click to collapse
I followed a video on youtube on how to flash recovery for the LG 3. I did the combination of volume down and power button and selected the factory data reset and it loaded TWRP. It looked like the stock factory data reset prompts until it loaded TWRP. It didn't erase anything. What does the .apk do that you posted?

EpicSaga said:
I followed a video on youtube on how to flash recovery for the LG 3. I did the combination of volume down and power button and selected the factory data reset and it loaded TWRP. It looked like the stock factory data reset prompts until it loaded TWRP. It didn't erase anything. What does the .apk do that you posted?
Click to expand...
Click to collapse
There's just a button in the middle of the screen that says "Boot into Recovery".
It requests Superuser so that it can run the shell command "reboot recovery".
Screenshots attached. (Also, uploaded it to the Play Store, will be up in a few hours)

Sadcamp said:
There's just a button in the middle of the screen that says "Boot into Recovery".
It requests Superuser so that it can run the shell command "reboot recovery".
Screenshots attached. (Also, uploaded it to the Play Store, will be up in a few hours)
Click to expand...
Click to collapse
Which Superuser app is the best? I am using is from ChainsDD, it might be outdated though. Are you using chainfire's Superuser App? After looking at the screenshots that you posted, and I looked on the playstore and that was the only one that looked similar. Merry Christmas

EpicSaga said:
Which Superuser app is the best? I am using is from ChainsDD, it might be outdated though. Are you using chainfire's Superuser App? After looking at the screenshots that you posted, and I looked on the playstore and that was the only one that looked similar. Merry Christmas
Click to expand...
Click to collapse
I believe I am using Chainfire's.
Merry Christmas to you too.

Sadcamp said:
I believe I am using Chainfire's.
Merry Christmas to you too.
Click to expand...
Click to collapse
Is it possible to switch to another Superuser app? I don't think I saw any support for this Superuser app from ChainsDD when I installed it. The only thing that interests me is that it has OTA Survival. I guess that means it will survive an OTA update.

EpicSaga said:
Is it possible to switch to another Superuser app? I don't think I saw any support for this Superuser app from ChainsDD when I installed it. The only thing that interests me is that it has OTA Survival. I guess that means it will survive an OTA update.
Click to expand...
Click to collapse
Yeah, I do believe there should be, mostly, ability to switch root apps.

Is it safe to flash CM11 once you have recovery? Would that take erase towel root and root access somehow and then TWRP along with it? Or would TWRP recovery survive?

I am unsure. I am the kind of guy that enjoys Stock so I've never bothered to flash anything. Best off asking someone who is a heavy flasher and active user.
Sent from my LG-P769 using XDA Free mobile app

EpicSaga said:
Is it safe to flash CM11 once you have recovery? Would that take erase towel root and root access somehow and then TWRP along with it? Or would TWRP recovery survive?
Click to expand...
Click to collapse
Towel root is only used for the rooting process, it can be deleted once you install supersu and busybox, or like you want flash a custom rom, any thing is safe oto do once you have a custom recovery as long as you follow op's directions on flashing their rom. Always read directions and as much info as can first. Recovery will always be safe unless you flash a kdz with lg flash tool which is used to completely return to stock, recovery, system and all. Also always back up while in recovery before flashing. Its always good to have back up stock rom, or any roms you like in case you decide to switch back or between them.
Sent from my LG-D415 using XDA Free mobile app

aerdely said:
Towel root is only used for the rooting process, it can be deleted once you install supersu and busybox, or like you want flash a custom rom, any thing is safe oto do once you have a custom recovery as long as you follow op's directions on flashing their rom. Always read directions and as much info as can first. Recovery will always be safe unless you flash a kdz with lg flash tool which is used to completely return to stock, recovery, system and all. Also always back up while in recovery before flashing. Its always good to have back up stock rom, or any roms you like in case you decide to switch back or between them.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
What does busybox do? I installed it and every time I open the app it says "Smart Install is loading ...You may go ahead and install Busybox or wait for Smart Install to finish loading". There are boxes to tick under "Smart Install" that can only be used in the PRO edition. The boxes are: "Enable Smart Install", "Replace All (Symlinks all)", and "Clean Mode". I don't know what these options do, but from the reviews I've read the PRO edition can break WIFI and even break the phone. If I do buy the PRO edition, and I flash CM11, it would wipe out the app. Would I have to buy it all over again from the play store?

EpicSaga said:
What does busybox do? I installed it and every time I open the app it says "Smart Install is loading ...You may go ahead and install Busybox or wait for Smart Install to finish loading". There are boxes to tick under "Smart Install" that can only be used in the PRO edition. The boxes are: "Enable Smart Install", "Replace All (Symlinks all)", and "Clean Mode". I don't know what these options do, but from the reviews I've read the PRO edition can break WIFI and even break the phone.
Click to expand...
Click to collapse
Just open the app and click install once rooted and supersu binarys are install. Rooted apps use the commands and things busy box installs to run. Never had an issue with it, like said just hit install and leave the app on the phone for updates. When you install a custom rom they're s already built in, really only use for rooting the stock rom.
Sent from my LG-D415 using XDA Free mobile app

aerdely said:
Just open the app and click install once rooted and supersu binarys are install. Rooted apps use the commands and things busy box installs to run. Never had an issue with it, like said just hit install and leave the app on the phone for updates. When you install a custom rom they're s already built in, really only use for rooting the stock rom.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
What is the Applet Manager?

EpicSaga said:
What is the Applet Manager?
Click to expand...
Click to collapse
Never used it, also to tell you the truth im not rooted st the moment, i went to stock to tske the 10e update and there no method as of now to root it, i could go back to 10c but i found that the update was improved on handling ram, that was the only reason i used a custom rom for a while. Once thetes a root method i may go back.
Sent from my LG-D415 using XDA Free mobile app