Database Develop

"LOOK" Here First {List} Roms/Kernels/Mods/Themes/FAQ'S *Update 27/09/11*

This thread is here to make the lives of every one just that much easier. Will try to keep the first and reserved posts as up to date as humanly possible.
Please ask all questions in relation to issues you are having following the FAQ instructions to make it easier to answer your questions and easier for us to track the solutions that way the FAQ post is as up to date and accurate as possible.
As the GT10.1 landscape changes this thread will get updated. I will try and keep everything as simple and to the point as possible. Contributors will be much appreciated.
THE BASICS
BOOTLOADER MODE
Turn device off. Then hold down power + volume down button (the button closer to power button) until you see two icons appear then let go. Left icon (box) is recovery and right icon (Android robot) is Download. Use Vol. down to navigate then vol. up to select.
DOWNLOADING MODE
Just tap volume up when you have highlighted the android robot icon. You should see downloading appear under the icon.
RECOVERY MODE
Vol. up/down to navigate up or down and power button to select.
This is what you use to install ROMs/KERNELs and even themes for your specific roms when they become available. Just highlight the box icon and hit Vol. up. What we are doing now is replacing the stock recovery on your device with Clockwork Mod Recovery which allows you install unsigned ROMs/Kernels/Updates. When in recovery mode you can also back up whatever current ROM you have on your device so if you install a new ROM and something goes wrong you could always use recovery to restore. Whenever you install a new ROM it's advised to always wipe the device using cwmR to ensure a more stable install. Install new ROMS will also mean you will be losing all the apps on your device. It will look like you have a brand new device after the install unless its an update.zip for whatever rom you are currently on and the developer of that rom supports it.
Don't worry about losing your apps as you can always re-download them once you sync your device with your google account. However, the state of those apps and your settings will be lost, so I strongly suggest that you use an app like titanium back up and always make a back up of your apps before flashing any new ROMs. Check in the Recommended Apps section for a direct link to Titanium backup.
Here is the clockwork mod menu
- Reboot system now (self explanatory )
- Apply update from SDcard. (when you connect your device to your computer it will show up as tablet. The SDcard that cwm refers to is simply your device storage. Always make sure to copy install.zips to the root directory of your tablet storage.) You use this when applying an update for a specific ROM if that is what the ROM developer says.
- Wipe Data/ Factory Reset You should always do this before you install a new ROM or if you are having minor issues with your device.
- Wipe cache partition Think of this as the lite version of whats above . If you do above though it doesn't hurt to do this too.
- Install zip from SDcard Use this to install new ROMs.
- Back up and Restore
- Mounts and Storage use this to connect your device to your computer when in recovery mode. It is also possible to transfer files to your device while in this mode.
- Advanced What you are interested in here is something called dalvik cache, you want to wipe this too before installing any new ROM
- Power off
CLICK ME FOR ALL TERMINOLOGY DEFINITIONS
NVFLASH
Nvflash is a low level formatting and imaging tool. If you don't have a working recovery, or have broken the actual boot-loader on your tablet, this is the tool you will need to turn to. For those with unlocked bootloaders (and no fastboot capability), its the best way to root your device. Nvflash is pretty much NVida's version of say an ODIN program but done through cmd prompt. It can save a tablet if one is soft/semi-bricked or maybe full-bricked. To use nvFlash you must first put your tablet in APX mode (think of it as a way to allow you use commands on your computer to control your tablet).
Refer to this thread for downloads and instructions.
So off we go.
ROOTING YOUR TAB
GO TO SamsunFirmware.com AND DOWNLOAD A STOCK FIRMWARE FOR YOUR TAB VERSION> KEEP IN SAFE PLACE!!!!!!! You are already on the right page just scroll down.
Courtesy of RoboBear
GOOGLE I/O & RETAIL WIFI VERSION
[GTP7510]
DOWNLOADS compiled and hosted by tphillips
Content - GT-p7510_USB_Driver | hc-3.1_ota-full_sam_tab_10.1.zip(StockROM) | Odin3_v1.85 | recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5 | stockretail.tar.md5(recovery) | Samsung_Galaxy_Tab_10.1_root
Download FilesForDummies.zip here
Mirror 1
Mirror 2
DONT WIPE during any part of this process. Make sure to put the stock rom from the download package on your device/use CWM and do a backup of your rom before you start anything in case something goes wrong. You have been warned!!!!!
1. Install samsung USB driver or download samsung Kies and install on your computer which will in turn install the drivers for you.
2. Run Odin.exe, choose PDA and point it to recovery.md5 file.
3. Connect tab via usb to your computer while in downloading mode then hit start in Odin on computer after connection has been established. Run, wait then reboot.
4. Connect tab to computer in usb storage mode (make sure usb debugging is off in tab settings) copy root exploit (Samsung_Galaxy_Tab_10.1_root.zip) to you tablet and take note of where it is. You can skip this part i fyou downloaded this file with your tablet.. Turn off tab. Reboot into bootloader again but this time go to recovery. Select to install zip from SDcard. navigate to where the root.zip is. Install the root.zip. Reboot into android. Your tablet is rooted.
5. Done.
You can also refer to this well made Video showing the whole procedure or this other awesome video by Dansan682.
RETAIL 3G
[GTP7500]
1. Download this Root.zip file to your tablet and move it to root directory of tablet storage. (you can also download on comp. then transfer to tablet)
2. Reboot tab and go into recovery mode and apply the root.zip you just downloaded.
3. Then reboot
rooted already
For CWM
1. After rooting download and install Rom Manager from market.
2. open Rom Manager app and have it install clockwork Mod to your device, you should see your device listed within Rom manager.
3. Done.
Courtesy of Robobear
RETAIL 4G
[GTP7500] courtesy of poitee
Downloads
Kernel.zip
Recovery.zip
1. Copy Files to root of device storage.
2. Boot into Bootloader mode and navigate to and enter recovery mode.
3. Apply Kernel.zip then recovery.zip
4. reboot.....Done.
UNROOTING & RESTORING STOCK RECOVERY
1. Using CWM Flash the stock rom for your device. This unroots your device and basically makes it like a brand new tablet.
2. Use Odin to flash the stock recovery from the filesfordummies.zip.
3. Done, your device is exactly how it was when you picked it up.
FLASHING ROMS AND KERNELS
This is pretty easy as long as you have CWM on your device.
Simply boot CWM recovery, navigate to either update/instal zip from SDcard (pls adhere to ROM/kernel install instructions) and flash the .zip file of the ROM or kernel.
I will update this section with links to all the existing and stable ROMs and kernels as the become available. I will advice that you hold off on the kernels if you can as every stable kernel will eventually get cooked into a ROM unless of course you want to help test them or be on the bleeding edge .
AVAILABLE ROMS & KERNELS
LEGEND
★ - WIFI
★ - 4G
★ - 3G
★ - Custom ROM
★ - Kernel
If your Device is supported the stars will tell you all you need to know.
★[ROM]Stock US Retail WiFi in case something goes wrong
[Solution] HC 3.1 OTA Stock ODIN
★[ROM]Stock|EU|Wifi|Retail|Touchwiz
★ [ROM][STOCK][ARABIC][AUG'13]W/ Official TOUCHWIZ
★★ [ROM][CWM] 3.1|WiFi|Touchwiz UX|DEODEXED
★★ [ROM][CWM] 3.1|WiFi|Touchwiz UX [UPDATE: New WiFi Base Rom]
★★ [ROM][CWM]3.1|WiFi|Bonsai ROM|ToucWiz option|
★★ [ROM][CWM]3.1| Blazar TW Rom|OC 1.6GH Kernel|Prerooted| by Poitee
★★ [ROM] [CWM]3.1|StarBurst ROM| by PhantomHacker
★★ [ROM][CWM][EUR][3G] BroodComb G-P7500 XWKG9 [ALPHA]
★★ [ROM]Task650's KME ROM UEKME Touchwhiz
★★ [KERNEL] 3.1|WiFi|OC 1.4GHZ| by Pershoot
★★[ROM] LiquidSpeed>>> New!!!
★★[KERNEL] 3.1|WiFi|OC1.6GHZ|Voltage Control|Voodoo Sound|CIFS-NTFS| by Poitee
[TABUNTU] Galaxy Tab 10.1 NATIVE Ubuntu WIFI now with a video
IRC ONLINE CHAT
Drop in HERE if you need some Help . #gtab
ROM/KERNEL/THEMES/UPDATES BETA TESTING!!!!
Ever wanted to get whats coming before anyone else (never mind the small issue of being a guinea pig ) Well here is your chance. In this section I will put up the contact info of any dev currently looking for testers and for a limited duration, once the devs has all their testers his link will be closed. You can also think of this section as a great way to see what is coming and what stage of development its in. So stop just downloading stuff people, now you can actually really contribute to making what gets released the best it can be and as bug free as possible.
FAQ
Be sure to ask whatever questions you have in relation to anything and any problems you come across. But please start every question you have with either a
(Q) basically letting me know its a question or a
(P) letting me know its a problem
I will put up all your questions or problems on here so everyone can see them and the answers or fixes . this way people won't have to filter through tons of pages to get help.
(Q) Should I follow these instructions for an IO edition tab? Or should I just use the fastboot flash [cwm recover] and flash the zips through that?
(A) This method will work on the IO version.
(Q) kernel 2.6.36.4 is a NO-GO for the 3G version?
(A) Yes, it doesn't work on the 3G version yet.
(Q) If my tab ins locked does that mean i cant flash kernels on it?
(A) You can flash anything as long as you have a recovery that will support it. In our case CWM. Being locked and unlocked really only stops you from flashing stuff "easily" but since we can change the recovery, we can flash anything.
(Q) Does the Odin file wipe tab?
(A) No. All Odin is doing here is flashing a new recovery to your tab. Nothing more.
(P) Can't see tablet as USB storage device on Mac.
(A) Unfortunately Android and Macs don't play nice... you best bet is to use dropbox or a simple bluetooth transfer to transfer files from your mac to your tablet. Then on your Tab use a file manager app to move your files to where you want them to be. For now. Another option is to download everything that requires you using CWM with your tablet so its all already there. So in CWM all you have to do is navigate to your downloads folder. I just created a folder called mods and I have them all there.
(P) Stuck in BootLoop after Flashing ROM via Odin.
(A) You should use nvFlash to falsh CWM if you don't still have it then do a full wipe of your device including reformating all partions in mounts and storage except the boot partition then using Odin install a stock Rom on your device.
(P) I messed things up on my LTE tab and I now somehow dont have a recovery mode anymore!!!!!
(A) Go Here and scroll to post #4 and follow tijayz instructions.... make sure to thank him!!!
USER TIPS AND RECOMMENDED APPS
TIPS
1. Working Hulu
2. How to utilize the entire screen for setting widgets and icons without the 1inch gap on the sides? Use ADW launcher EX
3. Rotation Lag Fix
4. Look here for a Mod to permanently set your browser user agnet to desktop. No more mobile sites.
RECOMMENDED APPS!!!!!go on!!, find an awesome app and suggest it to be added to this list!!! Only android market or direct .apk links so isers can download and install straight from their devices
Titanium BackUp
Circle Launcher
ADW Launcher EX
Beautiful Widgets
CNN
Minimalistic Text
Thumb Keyboard
Tablet Keyboard
XBMC
PLEX
Playstation Emulator
SNES emulator
Multipicture Live wallpaper. Kiss weirdly cropped wallpapers goodbye
Wallpaper Slideshow
Dolphin Browser HD
Pulse news Reader
AutoDesk SketchBook Pro
Feedly
File Manager HD (honeycomb)
All credit goes to all the awesome devs and members of xda. I have done nothing but make this thread.

DEV CENTRE
This section will have a host of developer specific tools and even tutorials. XDA making it easier for XDA??????
Good Times....
To start things off
APK Manager: Honeycomb Edition by tphillips

Thanks so much. But the download link doesnt work. Would appreciate it if you could get it working! Looking forward to flashing roms!
EDIT:Nevermind-its working

rvrugg90 said:
Thanks so much. But the download link doesnt work. Would appreciate it if you could get it working! Looking forward to flashing roms!
EDIT:Nevermind-its working
Click to expand...
Click to collapse
Sorry, try again... its working on my end though.

Nice, should be stickied.

(Q) Should I follow these instructions for an IO edition tab? Or should I just use the fastboot flash [cwm recover] and flash the zips through that?

The so-called "Mount device as USB Mass storage" thread has nothing to do with mounting the device as Mass Storage. It only tells you how to mount as MTP, which can be done without any of the steps mentioned in the thread. Seriously, it doesn't belong on this list.
Also, you should include instructions for using nvflash to install a custom recovery. I found it much easier and safer to root through this method than through Odin.

[Q] kernel 2.6.36.4
Many thanks for preparing this post.
Just wanted to add a question here: can you confirm that kernel 2.6.36.4 is a NO-GO for the 3G version?
Or is it related with TW versus plain HC?
I'm running the stock TW rom on a rooted 3G tab. Tried to flash the above kernel with OC purposes, had to recover through a CWM backup.
Thanks for clarifying

ca110475 said:
Many thanks for preparing this post.
Just wanted to add a question here: can you confirm that kernel 2.6.36.4 is a NO-GO for the 3G version?
Or is it related with TW versus plain HC?
I'm running the stock TW rom on a rooted 3G tab. Tried to flash the above kernel with OC purposes, had to recover through a CWM backup.
Thanks for clarifying
Click to expand...
Click to collapse
the oc kernel is not supporting tw at this current time.

I'm just going to copy exactly waht I typed in the IRC -- I'm stuck without being able to reboot into recovery with an I/O tab. Also cannot get fastboot to work
- i got some help from here earlier but now i'm stuck again in rooting/flashing a custom rom on the IO edition
<slobdogg> i went through the ODIN process to revert to 3.0.1, then was able to adb reboot recovery and install the root file
<slobdogg> afterwards i installed clockwork mod using RM, and then did the update to a 3.1 OTA file on XDA
<slobdogg> now i'm supposed to reboot into recovery to reinstall root but i cannot
<slobdogg> even in ADB if i reboot recovery it just restarts the device...also, I cannot enter recovery through the Vol Down + Power method, just fastboot and odin
<slobdogg> so im right back where I was (3.1 with no root)

ralexand said:
I'm just going to copy exactly waht I typed in the IRC -- I'm stuck without being able to reboot into recovery with an I/O tab. Also cannot get fastboot to work
- i got some help from here earlier but now i'm stuck again in rooting/flashing a custom rom on the IO edition
<slobdogg> i went through the ODIN process to revert to 3.0.1, then was able to adb reboot recovery and install the root file
<slobdogg> afterwards i installed clockwork mod using RM, and then did the update to a 3.1 OTA file on XDA
<slobdogg> now i'm supposed to reboot into recovery to reinstall root but i cannot
<slobdogg> even in ADB if i reboot recovery it just restarts the device...also, I cannot enter recovery through the Vol Down + Power method, just fastboot and odin
<slobdogg> so im right back where I was (3.1 with no root)
Click to expand...
Click to collapse
in order to do adb reboot recovery you need a rooted boot.
flash the latest tools pack, and you will get root/adb root shell/busybox,dropbear,ssh,etc.,etc.
you need to get CWM or the stock IO recovery on the device, prior to being able to flash.

pershoot said:
in order to do adb reboot recovery you need a rooted boot.
flash the latest tools pack, and you will get root/adb root shell/busybox,dropbear,ssh,etc.,etc.
you need to get CWM or the stock IO recovery on the device, prior to being able to flash.
Click to expand...
Click to collapse
What tools pack are you referring to? Can't seem to find something relating to that on the forum.
I feel like an idiot because it just seems like if i restart the process, I'll lose CWM again and be back where I am right now. If I could just get fastboot to work this whole thing would be a lot easier because I could just flash CWM without root.

ralexand said:
What tools pack are you referring to? Can't seem to find something relating to that on the forum.
I feel like an idiot because it just seems like if i restart the process, I'll lose CWM again and be back where I am right now. If I could just get fastboot to work this whole thing would be a lot easier because I could just flash CWM without root.
Click to expand...
Click to collapse
http://droidbasement.com/db-blog
XDA:
[Tools] – SU/BusyBox/Misc – Galaxy Tab 10.1 (Update: 6/18/11)
this sends you to droidbasement.

pershoot said:
in order to do adb reboot recovery you need a rooted boot.
flash the latest tools pack, and you will get root/adb root shell/busybox,dropbear,ssh,etc.,etc.
you need to get CWM or the stock IO recovery on the device, prior to being able to flash.
Click to expand...
Click to collapse
As with most issues, mine turned out to be user error. I forgot to re-flash the root.zip file after flashing the 3.1 update. That prevented me from being ablet o reboot into CWM.
Started from step 1, and flashed the root file after the 3.1 update and now i'm fine.
Thanks!

ralexand said:
(Q) Should I follow these instructions for an IO edition tab? Or should I just use the fastboot flash [cwm recover] and flash the zips through that?
Click to expand...
Click to collapse
This is only really known for certain to work on a retail locked or unlocked version. Not certain about the google i/o version but will ask around for you. But nothing here says that version is supported using this method.
However, i see no reason why it won't work though, assuming you only flash the root exploit.
For instructions specific to your model though, refer to this thread

Berner said:
The so-called "Mount device as USB Mass storage" thread has nothing to do with mounting the device as Mass Storage. It only tells you how to mount as MTP, which can be done without any of the steps mentioned in the thread. Seriously, it doesn't belong on this list.
Also, you should include instructions for using nvflash to install a custom recovery. I found it much easier and safer to root through this method than through Odin.
Click to expand...
Click to collapse
Thanks, removed the usb thingy, however, it would be nice if you also contributed a link to the nvflash method so i could update the thread. its not my thread you know? it belongs to all of us. How good this thread ends up being all boils down to how helpful we all are.

ralexand said:
As with most issues, mine turned out to be user error. I forgot to re-flash the root.zip file after flashing the 3.1 update. That prevented me from being ablet o reboot into CWM.
Started from step 1, and flashed the root file after the 3.1 update and now i'm fine.
Thanks!
Click to expand...
Click to collapse
Glad to see you are sorted
Please everyone... carefully follow the instructions!!!
On another note, does this mean that this process works on a google i/o device already on android 3.1? Please let me know so i can update

however, it would be nice if you also contributed a link to the nvflash method so i could update the thread. its not my thread you know? it belongs to all of us. How good this thread ends up being all boils down to how helpful we all are.
Click to expand...
Click to collapse
Posts 1 & 2 of them most viewed thread in this forum. http://forum.xda-developers.com/showpost.php?p=14866263&postcount=2

Berner said:
Posts 1 & 2 of them most viewed thread in this forum. http://forum.xda-developers.com/showpost.php?p=14866263&postcount=2
Click to expand...
Click to collapse
Well, i put it up and took it out again, there is currently a much, much, much easier and direct method to root the device. And one that I am sure you will agree is by far more straight forward.

Lorddeff07 said:
This is only really known for certain to work on a retail locked or unlocked version. Not certain about the google i/o version but will ask around for you. But nothing here says that version is supported using this method.
However, i see no reason why it won't work though, assuming you only flash the root exploit.
For instructions specific to your model though, refer to this thread
Click to expand...
Click to collapse
I'm not sure if it's just my version of the I/O Tab, or all I/O Tabs, but one key thing is that I could NOT boot into recovery on a non-rooted 3.1 Edition.
On 3.1, adb reboot recovery would simply reboot my device. I cannot use the POW + VOL DOWN button combination because I am presented with a USB icon on the left (which takes you to fastboot - which would not work for me), and the ODIN Download Icon on the right.
So, the only changes to the instructions with regards to an IO tab is to remove any reference to "POWER + VOL DOWN" as the method of getting into recovery. IT MUST be done via a command -- either adb reboot recovery or using Rom Manager to boot into CWM.
Exact steps for me (brief):
1. ODIN to revert to 3.0.1
2. reboot the device, turn on USB Debugging
3. connect to computer and use ADB to "adb reboot recovery" then install root zip file once you get into the stock recovery
4. Reboot - install Rom Manager and Clockwork Mod.
5. Reboot into CWM
6. Install the 3.1 Update AND [before rebooting] re-install the root zip file
7. Voila!
Only thing is -- now that I am on 3.1, the only way for me to get into recovery is via Rom Manager because the 'adb reboot recovery' function only reboots the devices, and the button combination trick still does not work.
EDIT: paragraph above is not entirely true -- i can open a terminal on my Tab and type 'reboot recovery' to get back into recovery. So, it's just adb & the button combination that does not work.
I still cannot figure out why I cannot get fastboot to work. My computer even seems to recognize that I have a fastboot device connected, but I cannot send any fastboot commands; even fastboot devices returns nothing.

[TESTERS] Beta version of Flash Image GUI

Appreciate all the help testing! Will keep this thread around if more issues are encountered.
For the time being I'm going to close down this thread as I've posted a new official thread!
Thanks everybody, especially PirateGhost!
New official thread: http://forum.xda-developers.com/showthread.php?p=20926830
Goal:
Working on making kernel flashing on the HTC Vivid / Holiday a few steps easier/simpler!
Background:
The HTC unlock method has been out for the last 6 months on the HTC EVO 3D. We've developed some work around methods to make things simpler for both the developers and the users who are stuck using the HTC unlock method.
How:
Fact for EVO 3D and theory for Vivid: The HTC unlock method only allows write access to the kernel (boot partition) in either fastboot mode or the normal android mode.
This means a custom kernel can only be loaded in two modes, either through fastboot or while in the standard Android mode.
Tool:
Flash Image GUI is an application I wrote to load the kernel and modules while in standard Android mode. This eliminates the need for using fastboot which requires a computer and will eliminate the need for using the Windows dependent .bat files for automating the fastboot flashing process. This will also eliminate the need to reboot into fastboot mode.
Current Status:
An updated Flash Image GUI code to support the HTC Vivid device but need a few testers to verify it all works properly on their devices!
Testing Location:
Either post back in this thread if you're able to help or join us on IRC - irc.freenode.net #gen-dev
Testing Steps:
Would recommend joining the irc channel for more detailed assistance but if you'd prefer to test and post in this thread, here are the steps:
**Wild Child told me there is no kernel backup support yet**
Stock Kernel Signed - http://w1z4rd.net/boot.img (Thanks IanWizard)
Stock Kernel Unsigned - http://joeykrim.com/evo3d/files/boot-unsigned-holiday.img
Skip straight to Step 5. The above links can be used to restore the kernel back to 100% stock.
1) Downloading clockworkmod recovery for your device to your local desktop
2) fastboot boot c:\downloads\cwm-recovery.img
3) Make a nandroid of all partitions (will need this in case there are any issues)
4) Reboot into normal android mode
5) Install Flash Image GUI - http://joeykrim.com/evo3d/files/FlashImageGUI.apk
6) Download a kernel to flash - list provided below
7) Push kernel .zip file to /sdcard (either usb mount the device or adb push c:\downloads\kernel.zip /sdcard/kernel.zip
8) Open Flash Image GUI - make a note of the kernel version displayed at the top of the application
9) Click browse and select the kernel .zip file from the sdcard
10) Flash the Image
**11) Reboot
12) Check the kernel version to see if the process worked (Either open Flash Image GUI and kernel version information will be at the top or Menu->Setting->About Phone -> Software Version -> More.
**If you're interested in testing the flashing of a kernel and ROM combination, at step 11, reboot into the standard recovery mode, where ClockworkMod should be loaded and flash the ROM .zip file
Steps to restore previous kernel before testing
1) fastboot boot c:\downloads\cwm-recovery.img
2) Restore Nandroid created in previous section step 3
Kernels to Test Flash:
Thanks to Dodgejcr for the stock vivid kernels for testing!
Stock Kernel boot.img zip with modified kernel version to verify flash worked properly
Stock Kernel anykernel .zip with modified kernel version to verify flash worked properly
PirateGhost Telstra boot.zip - This *probably* requires the associated ROM Raider .zip to be loaded. Don't flash this kernel unless you're also flashing the ROM .zip.
Thanks for the support and willingness to test!

awesome. i just went from stock rooted to my rom using this tool.
might i suggest a 'reboot to recovery for rom flashing' button? that would complete this little project, i think.

Good idea man. I'll surely add this to the superguide once a few more people test it. Less steps is always good.
Sent from my HTC PH39100 using xda premium

slapshot30 said:
Good idea man. I'll surely add this to the superguide once a few more people test it. Less steps is always good.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
i am working with him on IRC to get a one-stop-shop for rooted users to flash a new rom. no more fastboot flash boot for the noobs!
LOL

You are still gonna keep the ROMs and kernals separate for people that would rather do it from adb/recovery right? Cause I've had terrible luck trying to take shortcuts using batches, programs and the like.

travisxcore said:
You are still gonna keep the ROMs and kernals separate for people that would rather do it from adb/recovery right? Cause I've had terrible luck trying to take shortcuts using batches, programs and the like.
Click to expand...
Click to collapse
the beauty of this tool is that you dont use batches and programs on your computer
its all on the phone and will boot you to recovery to flash the rom you want (as soon as he gets all the bugs worked out. im just the guinea pig here, inputting little value)

I've have been able to flash a kernel in recovery. I was using the first compile i think. First step I did was reboot recovery from advanced then I wiped dalvik and flashed the zip containing the kernel. It seemed to work anyways.
Sent from my HTC-X710a using XDA App

Pirateghost said:
i am working with him on IRC to get a one-stop-shop for rooted users to flash a new rom. no more fastboot flash boot for the noobs!
LOL
Click to expand...
Click to collapse
Thank God... lol
It hasn't gotten that bad yet, with not that many people needing to flash kernels, but I was waiting for the onslaught of problems involving it.

Pirateghost said:
the beauty of this tool is that you dont use batches and programs on your computer
its all on the phone and will boot you to recovery to flash the rom you want (as soon as he gets all the bugs worked out. im just the guinea pig here, inputting little value)
Click to expand...
Click to collapse
I'm still a little weary...idk I've never really liked not having control over something like this because if my phone bricks, at least I know its my fault. But I could see the benefit being out and just downloading the ROM/kernal straight to my phone and flashing it. And I definitely see the benefit for people that don't have a single clue what their doing. Would help cut down on the same 1000 help me posts...lol.

ToyGUN said:
I've have been able to flash a kernel in recovery. I was using the first compile i think. First step I did was reboot recovery from advanced then I wiped dalvik and flashed the zip containing the kernel. It seemed to work anyways.
Sent from my HTC-X710a using XDA App
Click to expand...
Click to collapse
bet it didnt flash a kernel even if it was included in the zip....

Appreciate all the help testing! Will keep this thread around if more issues are encountered.
For the time being I'm going to close down this thread as I've posted a new official thread!
Thanks everybody, especially PirateGhost!
New official thread: http://forum.xda-developers.com/showthread.php?p=20926830

[DEV] ClockworkMod 5.5.0.4 [UPDATED: Can't get to CWM? Here's the fix!]

Howdy y'all!
I just compiled a proper version of ClockworkMod recovery 5.5.0.4 off of the ICS branch of CyanogenMod.
It supports backing up boot images (I have heard that the image that is being flashed now doesn't support backing that up), and in the near future will support recovery chargemode.
This repository will hopefully contain in the near future a semi-working copy of CyanogenMod 9 also, but there's no guarantees on that one
So, without further ado:
What is this?
This is ClockworkMod Recovery 5.5.0.4 and the files necessary to build it yourself.
Click to expand...
Click to collapse
How do I use it?
You must first be unlocked with HTCDev.com (there is an excellent guide over there, just click on the Unlock Bootloader button and it'll walk you through)
Once you're unlocked, download the prebuilt image below, and do the following (in the same directory you used to unlock your phone):
Code:
fastboot flash recovery <path/to/prebuilt-image-you-downloaded.img>
You need to replace the stuff in brackets with the path to the img file you downloaded from here...
Alternate Installation Method (ph39img)
Much easier installation once unlocked with HTCDev...
Simply download the ph39img.zip I have linked to in the downloads section, and put it on your external SD card.
Reboot your phone into HBOOT, and allow the update. Then you've got clockwork installed super easy, no computer needed!
Click to expand...
Click to collapse
How is this different from the ClockworkMod image that's floating around here?
Truth be told, I haven't tried the other version yet-- but I have been told that it doesn't back up boot.img, and has a few other bugs.
Also, this version has /sdcard mapped to the external SD card as opposed to the internal SD card. This is a safety feature to prevent losing backups in case your device becomes inaccessible. All backups should be to an external storage medium (even on your desktop, it's a good practice to not backup your hdd to the same device )
I'm sure mine has bugs too, but I'm posting the source so y'all can laugh at me
Click to expand...
Click to collapse
The Goods: Where do I get it? -- Downloads:
recovery-beta2.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-beta2.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG-chargemode.zip
New! PH39IMG.zip for users with ICS OTA: http://goo-inside.me/private/iomonster/htcvivid/recovery/ph39img/hboot-1.85/PH39IMG.zip
Click to expand...
Click to collapse
recovery-take1.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-take1.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG.zip
Click to expand...
Click to collapse
The GitHub source is here:
https://github.com/thecubed/android_device_htc_holiday
Click to expand...
Click to collapse
Please don't mirror the files (hotlinking is okay!), just incase I need to take them down or quickly update them. Thanks!
Click to expand...
Click to collapse
Changelog
recovery-take1 : initial release
recovery-beta2 : now supporting charge mode in all forms just like stock recovery, and a few behind-the-scenes tweaks
Click to expand...
Click to collapse
Tips and Tricks (what works, and what doesn't)
Please read the following-- the HTCDev unlock comes with it's own disadvantages and risks...
The HTCDev unlock adds the word "**UNLOCKED**" to your HBOOT screen. Even if you put your phone to stock with a RUU and re-lock the phone, your phone will show "**RELOCKED**" when booted to the bootloader.
At this time, I am unsure if AT&T will refuse warranty claims if they see that text. Just remember: if you unlock, there may not be any way back to complete stock any time soon.
Another disadvantage of the HTCDev unlock: ClockworkMod recovery CANNOT flash kernels. You must use JoeyKrim's kernel flasher ( http://forum.xda-developers.com/showthread.php?p=20926830 )or fastboot to flash kernels. This includes Nandroid backups.
If you back up your phone and apply a new ROM and kernel, you will have to fastboot flash the old boot.img back or use JoeyKrim's kernel flasher before switching ROMs.
If you flash a ROM, make sure to read the instructions with the ROM. Every ROM developer has a different method of flashing the kernel-- some come with a script to run, and others just give you the files to flash. Please read what they have to say before posting here with a complaint
Not seeing your rom .zips on your SD card, or having trouble restoring a backup?
This version of ClockworkMod has the external SD card set as primary. This is to avoid the problem of "my phone died, and I can't access my backups".
To solve this issue, simply put your ROMs or whatnot on your external SD card. In the future, I may look into how hard it is to add a internal/external SD switcher to clockwork, but for now the safest default is the external SD.
Sorry about that!
Some rom.zip's don't work...
This may be because they're using an old version of the update-binary in their .zip file. Contact your ROM maintainer and ask for an updated version
If you are a ROM developer, here's the updated "update-binary". Drop it in your META-INF/com/google/android directory in your ZIP and update your format() commands properly...
update-binary.bin (rename to update-binary) - http://legacyschool.us.to/htcvivid/update-binary.bin
Click to expand...
Click to collapse
HELP! I CANT GET INTO RECOVERY! *new!
If you find yourself unable to get into CWM (i.e. the screen flashes some text, then reboots immediately), just boot to fastboot (hboot -> fastboot), then issue "fastboot erase cache" on your PC.
Then you should be able to boot into ClockworkMod. After you're in there, make sure to format /cache to fix the problem.
This issue will be fixed soon, I'll add some intelligence to the kernel to not bother rebooting to fsck a partition if it's marked 'dirty' or unmountable. Stock recovery is supposed to fsck the partitions if they're dirty/broken, but CWM doesn't bother, and the kernel gets easily confused.
Click to expand...
Click to collapse
How can I contact (chastise, praise, call names) you?
On IRC (Freenode) you'll find me hanging out in #htc-holiday when I'm available.
Just say my name "IOMonster" (or "IOMonster_desk") and if I'm around I'll answer.
I also will sometimes respond to PM's on XDA, but XDA's forum has a bad habbit of not emailing me when I get a new PM...
Click to expand...
Click to collapse
Standard "it might not work" clause
This software hasn't been thoroughly tested, and it might not work.
It might not backup things correctly, and it might not restore them right.
Please don't trust this software with anything sensitive or life-alteringly important.
I'd hate to say "I told you so!"
That's not to say this software doesn't work, it's just the standard disclaimer.
Click to expand...
Click to collapse
Donation Information
I love to develop. I don't do this for money, I do it just for the "thanks".
Please don't feel obligated to donate, but if you feel like it, you can click the button below to donate a small amount to me. Alternatively, consider donating to a charity of your choice-- there are so many good causes out there that could use your donation.
​Thank you in advance!
Click to expand...
Click to collapse
Credits / Thank You's
IanWizard-cloud (testing, moral support )
Pirateghost (much needed debugging, testing, and flashing his phone no less than 20 times!)
joeykrim
toastcfh
fattire
BananaCakes (for getting clockwork built in the first place and enabling so many mods on day 1 of unlock!)
..and lots of others!
Click to expand...
Click to collapse
Thanks for giving this looong post a read!
Good luck!

Shoot I'll give it a shot. Flashing now. Will edit this post after its been tested.
Edit: Short glance review, I know a lot of this is already stated/known but just posting it anyways
So firstly, I'm still getting no confirmation when I flash images (whether it be recovery or kernal) but again, I think thats from me using a VM to do all the work.
Still boots into recovery when plugged in.
Maybe I'm just being an idoit, but I couldn't get out of the keytest, had to hold power button which booted the rom.
Of course the usb mount and such works.
Will try backup later when I'm not short on downtime.

already flashed... beautiful. will run through some tests tonight. and dont think you are getting rid of me on IRC now

Coming from the HTC EVO 3D land with the HTC unlock method for the last 6 months .. the following tips have been very helpful.
HTC Unlock method only allows kernel write access while in two modes, fastboot and standard android mode. HTC unlock method does NOT allow a kernel to be flashed from standard recovery mode. This includes a ROM .zip with a kernel inside. The ROM will load, but the kernel will not from standard recovery mode.
The ONLY way to flash a kernel whether by performing a full nandroid restore including the kernel or flashing a ROM with a kernel inside, is to use the following command to load the custom recovery:
fastboot boot <destination of recovery.img>
example on windows: fastboot boot c:\downloads\cwm-recovery.img
Everything else will work in the standard custom recovery mode EXCEPT the ability to flash a kernel. To flash a kernel through the custom recovery, fastboot mode must be used per HTC's unlock method.

Updated OP with simpler installation method (ph39img).
Much easier to use, and no mucking around in commandline!

well it most definetly worked. i jus downloaded the zip file and was able to back up my settings. Only problem i have is. ( which is a similiar problem i had before this. if i powered off the phone and plug it to charge it would automatically restart the phone.) When i power off now and plug it in to charge. It automatically goes to the clockworkmod set up. none the less my phone works and i have backed it up. But i still was wondering wat could cause these problems ?

Same issue here can't charge while off,
I not sure boot backups are working,
Was stock did back up, flashed RR betas and then restore to saved image, got bootloop, had flash boot thru fastboot
Sent from my HTC PH39100 using xda premium

Great start for this....from what i was told theres drivers needed in the recovery for it to charge while device is off and fastboot is unchecked...device charges while fastboot is checked and device is off....
WC

Recovery works great for me.
BTW, the offline charge issue is usually in the chargemon file.

for the new recovery, we will need to be using a new update-binary and when flashing a rom, your updater-script must contain 4 arguments in the format line, like this:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p29", "0");
inside the attached zip you will find the update-binary
if you dont know what update-binary and updater-script is, then this isnt for you and you needn't concern yourself with it.

Just put your new recovery in the superguide and gave you credit. Keep up the good work!

There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew

drewdatrip said:
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
Click to expand...
Click to collapse
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100

Pirateghost said:
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Click to expand...
Click to collapse
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew

drewdatrip said:
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
Click to expand...
Click to collapse
At that point it was too late for.the fix. It does work now though.
Sent from my HTC PH39100

Question has the flash able zip been updated so it will now work to flash rooms or is it the rom zip scripts that needed updating? Can I place this zip on my SD card and overwrite the old version ( if that's what was in fact wrong)
Sent from my HTC PH39100 using Tapatalk

I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.

hackit said:
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
Click to expand...
Click to collapse
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.

Thanks will try now.
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
---------- Post added at 09:01 PM ---------- Previous post was at 08:29 PM ----------
Worked like a charm, just finished my first nandroid backup as well.
off we go to start testing out a rom.....
wooo hoooo!
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse

ok i have a question, after using the phone for a full day know (still stock).
I have noticed I'm unable to keep my connection to rogers for data only.
I have checked and the apn is right.
I have cleared dalvic cache and fixed permissions.
Still when im away from wifi and using data, most of the time i have no connection.
Now before i updated to this version of cwm i had no issue's with my data connection.
anyone else having an issue with a raider on rogers?
Thanks

[Q] Fastboot?? Finally need to ask

I thought I knew enough not to ever post a question that might be answered already but here goes... I am an HTC Evo owner and know how to flash a rom in recovery with no problem. I boot into recovery (Amon Ra, I have cwm on my wifes phone) do a nandroid backup, wipe phone, cache, dalvik then flash zip from sd. i choose a rom and flash then reboot, everything is all good. With my Vivid, I am fearful of flashing a rom this way because of this fastboot step and what is a kernel(<------- i know it sounds newb but a for real question)? If I absolutely have to perform the fast boot step, I am 99% certain I will be able to figure it out, in fact I believe I have performed a similar task when rooting the Vivid. I may have the capability to do it but it doesn't make sense to me. I would like to understand why. Any helpful answers or tips for me?

"In computing, the kernel is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level." (This was from Wikipedia)
I would post a URL but since I'm 'new'.
Anyways, that's the gist of it.
(To my knowledge)

With most roms for example Rumraider, you need to flash the kernel (boot image) first before you flash the rom in. Cwm in order for the Rom to boot properly. It is the nearly the exact same steps as you HTC EVO. I'm coming from an HTC Aria so I'm like you and never had to this kernel flashing before. Trust yourself it is not hard. Just read the superguide. I repeat READ THE SUPERGUIDE. It explains exactly how to do it. There are a few ways to do it. I find using the command prompt the easiest but you need a pc. You can now even use a kernel flasher or a program called flash image GUI from the market. Honest its not so bad just read read read. I believe we need to flash this way until we get S-off. Hope this helps.
Sent from my HTC PH39100 using XDA App

strose09 said:
With most roms for example Rumraider, you need to flash the kernel (boot image) first before you flash the rom in. Cwm in order for the Rom to boot properly. It is the nearly the exact same steps as you HTC EVO. I'm coming from an HTC Aria so I'm like you and never had to this kernel flashing before. Trust yourself it is not hard. Just read the superguide. I repeat READ THE SUPERGUIDE. It explains exactly how to do it. There are a few ways to do it. I find using the command prompt the easiest but you need a pc. You can now even use a kernel flasher or a program called flash image GUI from the market. Honest its not so bad just read read read. I believe we need to flash this way until we get S-off. Hope this helps.
Sent from my HTC PH39100 using XDA App
Click to expand...
Click to collapse
What he said.
Sent from my Transformer TF101 using Tapatalk

Thanks to all of you!!! I use the comand window with the EVO 3d screen to boot in recovery. (1.5) I use the rootevo3dnew folder and hold down shift right click and it opens that comand window. (Just so you know what I know) But with the vivid I cant get the comand window to find the phone. I have used flash image GUI from the market (life saver) But I have found that some ROMS do not have a Kernal file in it for it to find. So it says I am missing img. So the question is how do I flash a kernal or add it to a Rom I would like to try? O and yes a noob all the way

When you use the command prompt window are you in fastboot on your phone? Make sure you install the correct drivers as well. If that doesn't work try using a program called easy kernel flasher. I think a dev on her created it.
Sent from my HTC PH39100 using XDA App

strose09 said:
When you use the command prompt window are you in fastboot on your phone? Make sure you install the correct drivers as well. If that doesn't work try using a program called easy kernel flasher. I think a dev on her created it.
Sent from my HTC PH39100 using XDA App
Click to expand...
Click to collapse
Thanks I will try that tonight The one thing I noticed is I use FlashImageGUI and it works great on HoliRaider V1 - Sense 3.5. I have tried to use it on VJRaider 0.0.3 Sense 3.5 and it will not load the kernal. why would that be?

I stole this from the superguide.
First, download FlashImageGUI from the bottom of the post. But, if you are going to use this more than once, SUPPORT THE DEV and buy the app from the market. You will also get auto updates if you buy it straight from the market
- If you downloaded the FlashImageGUI from the bottom of this post, put it on your external sd card and use a file explorer from your phone to install it
- Then download the ROM you want (this app can find the kernel image in a ROM zip) or just download the kernel by itself or the recovery img you want
- Put your desired kernel or ROM zip or recovery img on the ROOT of your SD card (not in any folders)
- Turn off wifi
- Launch the FlashImageGUI app on your phone
- Click browse and select the ROM zip or kernel or recovery img you put on the sd
- If you selected a ROM zip, the app will automatically find the kernel image
- Select "kernel image" or "recovery image"
- Select "clear dalvik" and "clear cache"
- Click "Flash Image" and let it complete
- IF THIS GAVE AN ERROR OR DIDN'T WORK CORRECTLY, ASK THE DEV OF THE ROM/KERNEL/RECOVERY TO MAKE IT COMPATIBLE WITH THIS APP
- If you were flashing a recovery, turn off the phone and try going into recovery mode (power button + vol down) and you should have the new custom CWM
- (If you were flashing a kernel, YOU NEED TO IMMEDIATELY FLASH YOUR DESIRED ROM
- Turn off your device, then boot into h-boot (hold down the power button and vol down)
- Now flash your ROM zip by following the guide below to flash the ROM, START WITH STEP 6 OF THAT GUIDE
http://forum.xda-developers.com/showthread.php?t=1416836

strose09 said:
I stole this from the superguide.
First, download FlashImageGUI from the bottom of the post. But, if you are going to use this more than once, SUPPORT THE DEV and buy the app from the market. You will also get auto updates if you buy it straight from the market
- If you downloaded the FlashImageGUI from the bottom of this post, put it on your external sd card and use a file explorer from your phone to install it
- Then download the ROM you want (this app can find the kernel image in a ROM zip) or just download the kernel by itself or the recovery img you want
- Put your desired kernel or ROM zip or recovery img on the ROOT of your SD card (not in any folders)
- Turn off wifi
- Launch the FlashImageGUI app on your phone
- Click browse and select the ROM zip or kernel or recovery img you put on the sd
- If you selected a ROM zip, the app will automatically find the kernel image
- Select "kernel image" or "recovery image"
- Select "clear dalvik" and "clear cache"
- Click "Flash Image" and let it complete
- IF THIS GAVE AN ERROR OR DIDN'T WORK CORRECTLY, ASK THE DEV OF THE ROM/KERNEL/RECOVERY TO MAKE IT COMPATIBLE WITH THIS APP
- If you were flashing a recovery, turn off the phone and try going into recovery mode (power button + vol down) and you should have the new custom CWM
- (If you were flashing a kernel, YOU NEED TO IMMEDIATELY FLASH YOUR DESIRED ROM
- Turn off your device, then boot into h-boot (hold down the power button and vol down)
- Now flash your ROM zip by following the guide below to flash the ROM, START WITH STEP 6 OF THAT GUIDE
http://forum.xda-developers.com/showthread.php?t=1416836
Click to expand...
Click to collapse
Yep I tried this like 5 times didn't work and I found out I had a bad download. So I downloaded the rom again and used this and it worked. Thanks guys
I thought I was losing my mind on this but just a bad download

ClockworkMod Recovery Images Available for Verizon LG G2

I have created Loki-enabled images for ClockworkMod Recovery and Touch Recovery.
Links to the images:
http://www.androidfilehost.com/?a=show&w=files&flid=8961
recovery-clockwork-6.0.4.4-vs980.lok
http://www.androidfilehost.com/?fid=23196940996968932
recovery-clockwork-6.0.4.4-vs980.lok.img
http://www.androidfilehost.com/?fid=23196940996968933
recovery-clockwork-touch-6.0.4.4-vs980.lok
http://www.androidfilehost.com/?fid=23196940996968931
recovery-clockwork-touch-6.0.4.4-vs980.lok.img
http://www.androidfilehost.com/?fid=23196940996968934
There is one set of images for CWM recovery and one for CWM Touch recovery. The loki images were created from the CWM images on clockworkmod.com using loki_flash.
Files ending in *.lok.img are identical (binary-same) to the corresponding *.lok files. Use these if using Flashify, since it doesn't allow flashing of files ending in *.lok. Or, just rename the *.lok files to *.img. Your choice.
These images should be flashed using the loki_flash method detailed here (use option 1):
http://forum.xda-developers.com/showthread.php?t=2449670
Just replace the name of the file specified in those instructions with the *.lok file you downloaded from the link above.
Or, as stated above, you can use Flashify.
Don't try to set up a custom CWM (or TWRP) recovery image from within CWM ROM Manager - you will end up with a non-working recovery mode. This is how I stumbled upon this issue and why I created the above loki images. If you are in a broken recovery state, just use the above images to get back to a working recovery state.
*** THESE IMAGES ARE ONLY VALID FOR THE VERIZON LG G2 VARIANT [vs980]! DON'T FLASH THEM ON ANY OTHER DEVICES ***

How is the cache wipe on this? Does it takee a long time (5-10 min) like TWRP? Thanks for the development

BriVG said:
How is the cache wipe on this? Does it takee a long time (5-10 min) like TWRP? Thanks for the development
Click to expand...
Click to collapse
There are instructions on how to make twrp do wipes faster in the 3rd post of the Cleanrom thread. It wipes everything in only a few seconds. Been using this method for a couple of weeks with no problems.

Cache wipe took 13 minutes... Just cache
Sent from my VS980 4G using Tapatalk

Originally Posted by BriVG
How is the cache wipe on this? Does it takee a long time (5-10 min) like TWRP? Thanks for the development
Click to expand...
Click to collapse
There are instructions on how to make twrp do wipes faster in the 3rd post of the Cleanrom thread. It wipes everything in only a few seconds. Been using this method for a couple of weeks with no problems.
Click to expand...
Click to collapse
Not sure this answered his question.
Thanks Devs. From my VZW G2.

trickster2369 said:
Not sure this answered his question.
Thanks Devs. From my VZW G2.
Click to expand...
Click to collapse
Just curoius is CWM has any benefits or downsides compared to TWRP?
Thank you

Evilmonstertruck said:
Just curoius is CWM has any benefits or downsides compared to TWRP?
Thank you
Click to expand...
Click to collapse
I havent run CWM yet on my g2 but thats all I ran in the past and it's really just personal preference. TWRP does have a bit more options and features and can be themed whereas CWM is pretty simple and plain. I think I like CWM a bit more though just because the layout is a bit nicer imo.

Evilmonstertruck said:
Just curoius is CWM has any benefits or downsides compared to TWRP?
Thank you
Click to expand...
Click to collapse
I've never used CWM touch, so I can't speak to that. I used CWM on my Incredible and Rezound, and they do the same things. The first time I used TWRP was on my Nexus 10, because CWM wasn't available as an option. Probably the biggest difference is the UI. TWRP can be themed also. Kind of like getting a new pair of shoes. The old ones are worn in and comfortable, and your used to them. The new ones look nice and clean, and work pretty much the same, but eventually grow on you. That's where I am with TWRP.
Thanks Devs. From my VZW G2.

I was curious about the wipe because I've heard that the - rm option was not wiping sufficiently for some people...

Just installed it and ran a backup. Seems to backup quicker than TWRP.
:good:

Because i'm not lazy
Here's the TWRP tip for faster wipes.
The Fix

locoface said:
Because i'm not lazy
Here's the TWRP tip for faster wipes.
The Fix
Click to expand...
Click to collapse
Yeah it's very fast but I've read in other posts of different forums that some people reported that this method left artifacts that possibly messed with subsequent flashes

any direct instructions for us noobs to adb on how to do this from just root with stock recovery?

HOWTO:install custom recovery with root and stock recovery
1) Download and install LG G2 Windows USB Driver, if you haven't already.
2) Download and install Flashify from the Google Play Store.
3) Download CWM Recovery or CWM Touch Recovery image file (*.img, not *.lok files). Either one - your choice.
4) Connect your phone to your PC via USB using Media sync (MTP) option.
5) Copy the appropriate *.img file, downloaded in step 3, to a location on your phone's SD card
6) Using Flashify, select Flash -> Recovery Image, and browse to the location on your phone's SD card where you copied the *.img file in step 5.
7) Select the file, and choose "Yup!"
Enjoy CWM Recovery goodness.
Viper76269 said:
any direct instructions for us noobs to adb on how to do this from just root with stock recovery?
Click to expand...
Click to collapse

kaczmar2 said:
1) Download and install LG G2 Windows USB Driver, if you haven't already.
2) Download and install Flashify from the Google Play Store.
3) Download CWM Recovery or CWM Touch Recovery image file (*.img, not *.lok files). Either one - your choice.
4) Connect your phone to your PC via USB using Media sync (MTP) option.
5) Copy the appropriate *.img file, downloaded in step 3, to a location on your phone's SD card
6) Using Flashify, select Flash -> Recovery Image, and browse to the location on your phone's SD card where you copied the *.img file in step 5.
7) Select the file, and choose "Yup!"
Enjoy CWM Recovery goodness.
Click to expand...
Click to collapse
Can't we just install CWM from Rom manager?

Unless the image available from within ROM manager has been updated, NO. You will end up with a broken recovery image. That is why I made the images above. I did this exact thing myself and that is how I found the issue and made these images.
The images on clockworkmod.com and in ROM manager didn't work for me until I created Loki versions.
However, you are welcome to try to see what results you get. If you boot into recovery and get an error, you can just flashify the images above to get back a working recovery.
Sent from my VS980 4G using Tapatalk

kaczmar2 said:
Unless the image available from within ROM manager has been updated, NO. You will end up with a broken recovery image. That is why I made the images above. I did this exact thing myself and that is how I found the issue and made these images.
The images on clockworkmod.com and in ROM manager didn't work for me until I created Loki versions.
However, you are welcome to try to see what results you get. If you boot into recovery and get an error, you can just flashify the images above to get back a working recovery.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Oh ok, i went ahead and did yours instead of Rom Manger before your reply anyway lol, works great. One big question though. what the heck is Loki in the phone world? I spent 2 years with galaxy nexus, rooting, zipping etc etc and never stumbled upon Loki stuff.

litobirdy said:
Oh ok, i went ahead and did yours instead of Rom Manger before your reply anyway lol, works great. One big question though. what the heck is Loki in the phone world? I spent 2 years with galaxy nexus, rooting, zipping etc etc and never stumbled upon Loki stuff.
Click to expand...
Click to collapse
same here, but to my understanding, Loki is a way to bypass the bootloader, or tricking the phone to thinking the bootloader is unlocked.
---------- Post added at 11:10 PM ---------- Previous post was at 10:42 PM ----------
i was looking for my buddy's phone on AT&T, and it says you have to be on TWRP in order to install there. is that the same for this? or can i use flashify and flash CWM while i have a stock recovery?

The LG G2 (and other devices, like the Samsung Galaxy S4) on Verizon and AT&T used locked bootloaders. These same devices on other carriers (T-Mobile, etc.) include an unlocked bootloader, which allows users to flash custom kernels and make other modifications to the software on their own devices, AT&T and Verizon branded devices ship with a locked bootloader that prevents these types of modifications.
Loki is effectively an exploit that fools the locked bootloader into loading an unsigned, modified (loki-fied) image. You can read more about how it works here and here, if you wish.
You can use Flashify and and flash CWM while you have a stock recovery if you use the images I posted and follow the instructions in a post above. My understanding is that the AT&T variant of the G2 has a locked bootloader, so these same instructions would apply to that device, I would assume. If you want to use TWRP instead of CWM, there is a Loki-enabled image of that floating around the XDA forums; you can use Flashify and flash TWRP if you wish.
Viper76269 said:
same here, but to my understanding, Loki is a way to bypass the bootloader, or tricking the phone to thinking the bootloader is unlocked.
---------- Post added at 11:10 PM ---------- Previous post was at 10:42 PM ----------
i was looking for my buddy's phone on AT&T, and it says you have to be on TWRP in order to install there. is that the same for this? or can i use flashify and flash CWM while i have a stock recovery?
Click to expand...
Click to collapse

anyone get a white screen asking you for a code to put in after hitting reboot system from CWM recovery? i just shut the phone off and back on and it was ok, but i'm just wondering if it was a fluke