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
Related
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
i have a vivid with the OTA AT&T ICS update with unloacked bootloader and i flashed WCX ICS recovery....I want to flash a different recovery liek clockworkmod but i dont know how D:...can someone show me how to bceause i am still kidna new to rooting and stuff
>Download your favorite recovery .img
>Make sure bootloader is unlocked (should be already )
>Put phone into fastboot mode while connected to your computer
>Assuming you have the correct adb/device drivers/fastboot (again you should) open a command prompt in the same directory as your adb/fastboot/recovery.img
>flash your recovery.img
from the superthread read 3-4 times
3) (Optional) Flash a custom Kernel/Recovery (Three options, I suggest the FIRST)
*ATTENTION* IF FLASHING A KERNEL FOR A NEW ROM YOU WANT, YOU MUST FLASH THE ROM IMMEDIATELY AFTER FLASHING THE KERNEL WITHOUT BOOTING UP, THE KERNEL COMES FIRST. OTHERWISE, YOU MIGHT BOOT LOOP.
FIRST (AUTO) (joeykrim's FlashImageGUI method)
http://forum.xda-developers.com/show....php?t=1423151
OR
SECOND (AUTO) (xboarder56's method)
- First, turn off wifi on your phone
- If you have SetCPU installed or any other program where you have altered to overclock or underclock, DISABLE the "set on boot" option
- You will have to download Easy Kernel Flasher v03.zip which is attached below
- Next plug in your phone and make sure its getting detected
- After that extract the zip file (kernel flasher)
- Place the boot.img of the kernel you want flashed in the "Kernel-Here" folder.
- Make sure android debugging is enabled on your phone via settings
- Click Flash.bat for windows or Flash.sh for linux and wait for it to close terminal
- Wait for your phone to reboot and wait 5-10 minutes. Then reboot again and wait 5 minutes, then you're good to go!
http://forum.xda-developers.com/show....php?t=1328141
OR
THIRD (Manual) (Pirateghost's method)
- Extract the boot.img out of the kernel file you want and put it in the same directory as your fastboot.exe/fastboot executable
- Boot phone into hboot/bootloader (make sure you are in fastboot mode)
- Enter this code to flash the kernel and reboot the phone
Code:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
download the Vivid All In One Kit its noob friendly hahaha
So the xboarder56 kernel tool flashes boot.img's for you?
As far as flashing kernals I just swap boot.img's in the data folder that's in the folder with the app
Sent from my HTC PH39100 using XDA
ENvisiNKeD said:
download the Vivid All In One Kit its noob friendly hahaha
Click to expand...
Click to collapse
i would suggest not to use that program just follow the steps above. some people have been having issue with that program.
ccb101 said:
i would suggest not to use that program just follow the steps above. some people have been having issue with that program.
Click to expand...
Click to collapse
As long as u follow all the instruction, manual or using vivid tools, u can flas CWM with easy.
Sent from my HTC Raider X710e using xda premium
Thanks for the info...I have trying to figure out how to do the same thing. I have clockworkmod now and was thinking.of changing...I just don't know if there is any better as clockwork is the only one I've tried..
Sent from my HTC PH39100 using xda premium
if wanting to flash the twerp recovery,i got a report of it bricking a phone earlier today....if your wanting to flash an older version of cwm it corrupts some of the memory partitions onn the phone....end choice is yours but you have been warned
Listen, I ported a version of TWRP 2 many months ago for personal use. I also have seen the source for the standard CWM used for the Vivid.
I can tell you one thing for certain. There are issues in the (Big issues in the first few releases, but there always are in new developments), but there still are a few issues & some features that just don't work in CWM.
In TWRP, there are also issues & that is why I abandoned it & never released anything. The TWRP recovery is neat because it is fully touch capable. However, there are issues with the current version that cause boot loops & the inability to enter into bootloader, fastboot or recovery. TWRP has also been known to cause some format errors for device internal storage.
It is my learned opinion, that the best recovery for the Vivid to date is the wcxrecovery. If you were to contact AmonRa & ask him who is one of the best still making recoveries (since he has pretty much retired from the task) he would tell you that GinM is one of the best guys to build the recovery. GinM is who built the WCX recovery. It has as many or more features than any other recovery available for the Vivid & more importantly, the wcxrecovery is built from scratch using Vivid source. It is not a ported recovery, it is a true Vivid built custom recovery with many functions.
The latest CWM recovery is okay. It is a decent recovery that does the basics. TWRP is neat, but still just a novelty at this point & I can tell you first hand that it causes issues, some serious, as of version 2.1.1.
WCXRecovery works solidly, has never caused me any of the issues that the others have, it can root a rom & has many developer friendly functions.
If you care more about Bells & Whistles than performance, then you can install any recovery over wcx. The only recovery that you cannot flash over was the first CWM release.
Flashing a recovery is as easy as using fastboot & typing a few commands or using a bat script. But why you would want to sacrifice performance for one feature (Touch Screen), is a bit beyond me.
TWRP has potential. But it is just not there yet & CWM is just missing too many of the features that dev's use, not too mention the backup options available with wcxrecovery.
The reason why I'm asking is because I used the all-in-one toolkit but it didnt root my phone and I just pressed flash wildchilds recovery and now I have it. Now there is a newguide showing how to root but I'm afriad I might brick my phone since it already has this recovery. The guide basically says to flash wcx recovery which I already have. Do u guys now If I do it again it might brick it?
Sent from my HTC PH39100 using XDA
You won't brick your phone by flashing the wcxrecovery again - it's just this command:
fastboot flash recovery wcxrecovery.img
in a command window.
You must be in the folder containing the wcxrecovery.img file, and fastboot.exe should be either there in the folder or in your PATH.
But, if you already have it, why flash it again?
---------- Post added at 04:39 PM ---------- Previous post was at 04:20 PM ----------
GSLEON3 said:
<snip>
WCXRecovery works solidly, has never caused me any of the issues that the others have, it can root a rom & has many developer friendly functions.
If you care more about Bells & Whistles than performance, then you can install any recovery over wcx. The only recovery that you cannot flash over was the first CWM release.
<snip>
Click to expand...
Click to collapse
GSLEON3 makes a good technical case for using the WCX recovery - I also think it's really easy to use and well designed.
You can use the touch buttons to browse thru the menus -
Home: Up,
Menu: Down,
Back: Back, and
Search: Select/Confirm
Anytime it asks you to press Power to confirm, you can just tap the search button.
That's enough 'touch' functionality for me, and when it comes to tools like recovery's, eye-candy is pretty much irrelevent.
Attached is a flashable zip of CWM 5.0.2.0. I successfully installed the file from CWM, CWM Touch, and TWRP.
Good luck!
(All the usual warnings apply: flash at your own risk, etc., etc.)
____________________________________________________
Back Story:
Today I was flashing an alternate recovery when I got stuck at the boot logo. I (foolishly) had no other zip flashable recoveries on my phone. Since I had no PC access, I was SOL until I got home. I searched the forum and found no flashable standard CWM recovery. So, I decided to make one.
Do yourself a favor, save a copy on your sd card and hope you never need it!
I think all recoveries in THIS thread can be flashed via recovery. Just choose the zip format and colors of your choice. I've tried before flashing via TWRP. Anyway,thanks for sharing.
You are correct. And romracer's recovery is great, but I wanted CWM.
Sent from my MB860 using xda app-developers app
Question - why is it necessary to format /cache before flashing? I mean, the recovery log is in there (/cache/recovery/log).
I don't get it. A recovery that you can flash from recovery in case you can't get into recovery?
yeahmann said:
I don't get it. A recovery that you can flash from recovery in case you can't get into recovery?
Click to expand...
Click to collapse
Not exactly.. It's when we wanna change recovery to others. Like changing TWRP to any button recoveries. But,we still can access recovery. If we can't access recovery,the only way is by flashing image format via fastboot command.
Before I made this file I analyzed other zip flashable recoveries, and they wiped cache as well. I don't fully understand why myself. Maybe for the very purpose of clearing the recovery log? Maybe because we are taught to always clear the cache before flashing anything and it's just a habit?
ravilov said:
Question - why is it necessary to format /cache before flashing? I mean, the recovery log is in there (/cache/recovery/log).
Click to expand...
Click to collapse
I could access recovery. I just couldn't get past the boot logo. I did say "boot loop" instead of "boot logo" in the original post (I corrected that - my bad). Was this the source of your confusion?
yeahmann said:
I don't get it. A recovery that you can flash from recovery in case you can't get into recovery?
Click to expand...
Click to collapse
upndwn4par said:
Before I made this file I analyzed other zip flashable recoveries, and they wiped cache as well. I don't fully understand why myself. Maybe for the very purpose of clearing the recovery log? Maybe because we are taught to always clear the cache before flashing anything and it's just a habit?
Click to expand...
Click to collapse
Ah, I see.
upndwn4par said:
I could access recovery. I just couldn't get past the boot logo. I did say "boot loop" instead of "boot logo" in the original post (I corrected that - my bad). Was this the source of your confusion?
Click to expand...
Click to collapse
I think he was confused about why would you want to flash recovery if you already have a working recovery? And if you don't have a working recovery, a flashable recovery won't help. IE, he thought this is for emergency purposes, but in case your recovery is malfunctioning.
ravilov said:
Ah, I see.
I think he was confused about why would you want to flash recovery if you already have a working recovery? And if you don't have a working recovery, a flashable recovery won't help. IE, he thought this is for emergency purposes, but in case your recovery is malfunctioning.
Click to expand...
Click to collapse
Having a flashable recovery if your recovery works allows for easy switching. I'm not (yet) a touch recovery fan, but some roms require them.
I was trying to install a touch recovery when the install failed (bad download I think - I downloaded another copy and it installed fine). My phone would not boot past the logo, but I could boot to recovery. I pulled the battery and tried to reboot a few times, re-flashed the recovery, fixed permissions, etc. to no avail. I had no PC access, so I couldn't fastboot a recovery. So, I had no phone for a few hours. During that time I was wishing I had a recovery flashable recovery (if I hadn't recently deleted a copy of romracer's recovery from my phone I would have been good to go). I made one, pulled my sd card and loaded the file, replaced the sd card, booted to recovery, then flashed the recovery I made. The abridged version is the back story in the OP. Anyway, that brings us to the whole point of this thread.
Edit:
I think I set a record for most times using the word "recovery" in a single post.
Although I do appreciate your contributions... I refuse to do any flashing whatsoever unless I have PC access or it's already a dire emergency.
Nandroid -> Titanium Backup -> MyBackup -> Image SD Card (With all three backups) to desktop / laptop -> blast everything on phone to kingdom come -> begin whatever flashing that I probably shouldn't be doing...
Probably overkill, yes; but your remote flashing with no PC access? You sir, are a brave soul.
Normally I am almost as cautious as you. But I was at a really boring offsite meeting. But, I learned my lesson.
xdraconis said:
Although I do appreciate your contributions... I refuse to do any flashing whatsoever unless I have PC access or it's already a dire emergency.
Nandroid -> Titanium Backup -> MyBackup -> Image SD Card (With all three backups) to desktop / laptop -> blast everything on phone to kingdom come -> begin whatever flashing that I probably shouldn't be doing...
Probably overkill, yes; but your remote flashing with no PC access? You sir, are a brave soul.
Click to expand...
Click to collapse
Hey Everyone the folks over at TEAM WIN RECOVERY PROJECT put together an image file for TWRP recovery for the I9505G. I take NO CREDIT for this but I did convert the image into an ODIN flashable .TAR file because an ODIN tar was not available on TWRP website. I have tested and flashed this on my Locked Bootloader and Stock Google Edition Galaxy S IV running 4.2.2. Please make sure you Unlock the Bootloader if you want to Root your phone, the Root will not work if you try to install it from Recovery on reboot.
As Always I am not responsible if you brick your phone doing any modification
HOW TO INSTALL
Open up ODIN and click on PDA
Select Recovery.tar from the attachment you downloaded
Make sure ONLY "AUTO REBOOT" is checked
Click START
After you see the PASS on Odin and "Removed" Unplug
Power Off or Pull the battery
Use Volume Up and the Power till you see the SAMSUNG logo and let go of all. Wait for TWRP to boot, it took a little longer so your not stuck, just be patient.
8/30/2023 / 2.6.1.0
10/14/2013 / 2.6.3.0
07/21/2014 / 2.7.1.0
UPDATED TWRP IMAGES AND .TAR ODIN FILES http://techerrata.com/browse/twrp2/jgedlte
-----------------------------------------
KNOWN ISSUES For 2.6.0.0 & 2.6.1.0: 8/31/2023 ( post any help info on further releases ) UPDATE 7/21/2014 I have not been using the I9505G for awhile now so I am not sure of any issues or bugs on the latest releases please post them in the thread.
I have used TWRP from the Team Win site and the Odin package image I put together here and I have noticed and reported 2 bugs. The first is you can get stuck on TWRP screen booting into recovery, just pull the battery or reflash again until it boots up. The second is that when you restore sometimes you will get a FAIL immediately, don't panic, (1) reflash a ROM, and Restore or (2), pull battery and reboot back into recovery and Restore or (3) wipe and then Restore.
This build has some minor issues but if you follow this guide you will be OK.
Thanks to the Folks at TEAM WIN RECOVERY PROJECT and Chahk
MJ (attached file is for 2.6.0.0) PLEASE DO NOT USE ATTACHED RECOVERY PLEASE USE THE LINK ABOVE FOR OFFICIAL TWRP RECOVERY
MJHawaii said:
Hey Everyone the folks over at TEAM WIN RECOVERY PROJECT put together an image file for TWRP recovery for the I9505G. I take NO CREDIT for this but I did convert the image into an ODIN flashable .TAR file because an ODIN tar was not available on TWRP website. I have tested and flashed this on my Locked Bootloader and Stock Google Edition Galaxy S IV running 4.2.2. Please make sure you Unlock the Bootloader if you want to Root your phone, the Root will not work if you try to install it from Recovery on reboot.
As Always I am not responsible if you brick your phone doing any modification
HOW TO INSTALL
Open up ODIN and click on PDA
Select Recovery.tar from the attachment you downloaded
Make sure ONLY "AUTO REBOOT" is checked
Click START
After you see the PASS on Odin and "Removed" Unplug
Power Off or Pull the battery
Use Volume Up and the Power till you see the SAMSUNG logo and let go of all. Wait for TWRP to boot, it took a little longer so your not stuck, just be patient.
Thanks to the Folks at TEAM WIN RECOVERY PROJECT and Chahk
MJ
Click to expand...
Click to collapse
Thank you! Will try it out after work. Have you tried to perform a full nandroid backup?
---------- Post added at 11:48 AM ---------- Previous post was at 10:57 AM ----------
I just installed it via Goomanager app. =)
Sent from my GT-I9505G using xda premium
taney said:
Thank you! Will try it out after work. Have you tried to perform a full nandroid backup?
---------- Post added at 11:48 AM ---------- Previous post was at 10:57 AM ----------
I just installed it via Goomanager app. =)
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
I did not try to do a Nandroid this was the image from Team Wins website so I don't think you will have any backup issues like some did with the I9505 image. Goo Manager is always the best option but a .tar comes in handy at times that is the only reason I converted their image.
Sent from my GT-I9505G using Tapatalk 2
This is big news, but the lack of replies has me worried. I need more brave souls to flash before me.
BTW, did this trip your counter MJ?
Apologies if I am completely wrong - but does this mean that if I use this recovery my phone will be 100% identical to the official S4GE? I assume that would make a lot more stable and efficient than the current dumbs we have been leaked?
Thanks in advance!
ldjalal said:
Apologies if I am completely wrong - but does this mean that if I use this recovery my phone will be 100% identical to the official S4GE? I assume that would make a lot more stable and efficient than the current dumbs we have been leaked?
Thanks in advance!
Click to expand...
Click to collapse
From my understanding this is just a TWRP recovery. It's not something that will make your phone a stock S4GE because this is a custom recovery. It's a custom recovery for the S4GE GT-I9505G.
qnet said:
From my understanding this is just a TWRP recovery. It's not something that will make your phone a stock S4GE because this is a custom recovery. It's a custom recovery for the S4GE GT-I9505G.
Click to expand...
Click to collapse
Ohh OK, so this is just a TWRP recovery for an official S4GE? Thank you for clearing that up.
jpculp said:
This is big news, but the lack of replies has me worried. I need more brave souls to flash before me.
BTW, did this trip your counter MJ?
Click to expand...
Click to collapse
I put everything in the OP guys this is just recovery you can flash from Odin. I have tested and flashed this on my own I9505G this is NOT for the I9505
Sent from my GT-I9505G using Tapatalk 2
Flashing the .img with Heimdall is another option.
EDIT: http://forum.xda-developers.com/showthread.php?t=2370101
irishrally said:
Flashing the .img with Heimdall is another option.
EDIT: http://forum.xda-developers.com/showthread.php?t=2370101
Click to expand...
Click to collapse
Odin is easier for most Windows users because of its GUI, using standard USB drivers, and not having to mess around with Command Prompt.
Chahk said:
Odin is easier for most Windows users because of its GUI, using standard USB drivers, and not having to mess around with Command Prompt.
Click to expand...
Click to collapse
I agree Heimdal is great but most people prefer and use Odin
Sent from my GT-I9505G using Tapatalk 2
Can any one confirm this is working ?
Anyone can confirm this works ? (GT-I9505G)
(backup and restore works ?)
Thanks
imneo1 said:
Anyone can confirm this works ? (GT-I9505G)
(backup and restore works ?)
Thanks
Click to expand...
Click to collapse
Backups work I have not tried to restore though
MJHawaii said:
Backups work I have not tried to restore though
Click to expand...
Click to collapse
Full restore as well as partial work fine.
Chahk said:
Full restore as well as partial work fine.
Click to expand...
Click to collapse
Yep I did multiple backups, restore, and even flashing test zips upcoming ROMs for the I9505G. Make sure your following us in the GENERAL section here in Discussion I9505G there is a lot happening.
http://forum.xda-developers.com/showthread.php?t=2381339
Sent from my GT-I9505G using Tapatalk 2
Edit...done
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Edit...done
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I have used odin to flash this TAR File and it passes but when I boot into my recovery it is still the stock recovery. My bootloader in unlocked but Secure Boot is Enabled. I think the secure boot may be why it is not flashing correctly. If so how to I disable secure boot?
jedinegotiator said:
I have used odin to flash this TAR File and it passes but when I boot into my recovery it is still the stock recovery. My bootloader in unlocked but Secure Boot is Enabled. I think the secure boot may be why it is not flashing correctly. If so how to I disable secure boot?
Click to expand...
Click to collapse
This is a known issue with TWRP even if you download the image directly. Keep rebooting to recovery it will work...eventually. I already submitted this to Team Win.
Sent from my GT-I9505G using Tapatalk 2
Updated guys 2.6.1.0 is out with new IMG and .tar files hopefully this new update fixes the freezing when we boot into TWRP I will be testing it.
Please report back on your experience.
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Updated guys 2.6.1.0 is out with new IMG and .tar files hopefully this new update fixes the freezing when we boot into TWRP I will be testing it.
Please report back on your experience.
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
If there is no difference between that .img and the one downloaded from goo.manager, Its freezing under advanced settings. Cant restore defaults. It froze on me trying to do a back up. Im sure there are several other issues as I have not had a chance to review the thread in general section yet, but just a few results from my own experience.
EDIT: I stand corrected, I thought I was getting freezes, I let it sit and it finally completed.
So I just recently decided to flash the unbloated OTA offered in the download section. I was on the 12 radio before running a regular ROM with ROM Manager and everything working perfectly. I flashed everything and all went smoothly. I flashed the OTA and the other required .zip. I then tried to root with IOroot25. Well my phone is detected, but when it goes to reboot into recovery, it never really does. So I tried to adb reboot recovery and the same thing happened - not going into recovery, just kinda' sitting at a very dark, though barely lit, screen.
Everything functions fine but it appears I do not have any sort of recovery at all. How would I go about fixing this? Any help would be greatly appreciated.
What debloated ROM did you flash?
BoostinBen said:
So I just recently decided to flash the unbloated OTA offered in the download section. I was on the 12 radio before running a regular ROM with ROM Manager and everything working perfectly. I flashed everything and all went smoothly. I flashed the OTA and the other required .zip. I then tried to root with IOroot25. Well my phone is detected, but when it goes to reboot into recovery, it never really does. So I tried to adb reboot recovery and the same thing happened - not going into recovery, just kinda' sitting at a very dark, though barely lit, screen.
Everything functions fine but it appears I do not have any sort of recovery at all. How would I go about fixing this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
It got removed, you need to downgrade the aboot to install a recovery once you upgrade the firmware to 24A. 24A plugs the exploit that was being used. Easiest route is to use the AutoRec app in the LG G2 Development section.
mjones73 said:
It got removed, you need to downgrade the aboot to install a recovery once you upgrade the firmware to 24A. 24A plugs the exploit that was being used. Easiest route is to use the AutoRec app in the LG G2 Development section.
Click to expand...
Click to collapse
How can I use this program if I can't attain root? It says it requires root, which IOroot25 cannot do due to not having a recovery to boot into to apply the .zip.
I'm going to try the KDZ method here to flash the factory version in its full glory. Hopefully that will restore recovery mode and allow me to root the thing. I'll report back with my findings, and whether or not I was able to do this using the above link, IOroot, and AutoRec.
I am having the same issue. I was running CM11 on a verizon lg g2 with CWM recovery. I flashed prerooted 4.4.2 from MicroMod777 along with the KK baseband. It worked, but I lost root AND recovery. Now when I tried to use ioroot 25, my phone won't boot into recovery at all. It appears that I lost recovery. Is there a simple way to install recovery back?
holsteinmoo said:
I am having the same issue. I was running CM11 on a verizon lg g2 with CWM recovery. I flashed prerooted 4.4.2 from MicroMod777 along with the KK baseband. It worked, but I lost root AND recovery. Now when I tried to use ioroot 25, my phone won't boot into recovery at all. It appears that I lost recovery. Is there a simple way to install recovery back?
Click to expand...
Click to collapse
Return your phone to stock, let it take the OTA then rroot and install recovery.
http://forum.xda-developers.com/showthread.php?t=2448960
mjones73 said:
Return your phone to stock, let it take the OTA then rroot and install recovery.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
Yep...that did it! Thanks!
mjones73 said:
Return your phone to stock, let it take the OTA then rroot and install recovery.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
Running TWRP and am happy with that but would prefer CWM touch recovery. Have tried several methods to install from various XDA treads with no luck. Any info you know of on that?
CWM installed fine for me using their purchased app and just flashing the touch version after selecting my device model.
I have also installed it using .img files provided in the forums and using Flashify to flash them.
BoostinBen said:
CWM installed fine for me using their purchased app and just flashing the touch version after selecting my device model.
I have also installed it using .img files provided in the forums and using Flashify to flash them.
Click to expand...
Click to collapse
I was able to use .img files in the forums with 11a...I never took 12b...just stayed on 11a and ignored the update.
I returned to stock to get to 24a and was able to root but can't for the life of me get CWM recovery installed. I have tried flashify, installing zips, pushing .img with adb...no dice. I get error messages every time or the black screen you described in this thread's original post.
Just tried to load the zip from TWRP...no dice.
I purchased touch through the paid version of CWM and chose my device...nada...it's killing me!
I can live with TWRP but love CWM touch. Really at a loss.
Are you running 24a? If so, can you point me toward the forum link you used to get CWM loaded?
holsteinmoo said:
I was able to use .img files in the forums with 11a...I never took 12b...just stayed on 11a and ignored the update.
I returned to stock to get to 24a and was able to root but can't for the life of me get CWM recovery installed. I have tried flashify, installing zips, pushing .img with adb...no dice. I get error messages every time or the black screen you described in this thread's original post.
Just tried to load the zip from TWRP...no dice.
I purchased touch through the paid version of CWM and chose my device...nada...it's killing me!
I can live with TWRP but love CWM touch. Really at a loss.
Are you running 24a? If so, can you point me toward the forum link you used to get CWM loaded?
Click to expand...
Click to collapse
With 24a I pushed it with adb instead of flashing it via Flashify and it worked decently for me. Personally, though, I do like TWRP more, albeit it doesn't have that convenient application like CWM does.
holsteinmoo said:
I was able to use .img files in the forums with 11a...I never took 12b...just stayed on 11a and ignored the update.
I returned to stock to get to 24a and was able to root but can't for the life of me get CWM recovery installed. I have tried flashify, installing zips, pushing .img with adb...no dice. I get error messages every time or the black screen you described in this thread's original post.
Just tried to load the zip from TWRP...no dice.
I purchased touch through the paid version of CWM and chose my device...nada...it's killing me!
I can live with TWRP but love CWM touch. Really at a loss.
Are you running 24a? If so, can you point me toward the forum link you used to get CWM loaded?
Click to expand...
Click to collapse
So you took the OTA and you're on 24A now? If thats the case you need to push the 12B aboot first before you can flash recovery. AutoRec will do all that. And flash recovery for you. After its finished you can flash CWM touch if you want.
---------- Post added at 01:13 AM ---------- Previous post was at 01:12 AM ----------
BoostinBen said:
With 24a I pushed it with adb instead of flashing it via Flashify and it worked decently for me. Personally, though, I do like TWRP more, albeit it doesn't have that convenient application like CWM does.
Click to expand...
Click to collapse
Have you ever seen this? https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager It flashes recovery for you, you can manage backups, with a donation you can even make live backups while still booted in Android. I haven't tried it yet because I keep forgetting. Sounds so cool though.