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
Related
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
SAFESTRAP 1.09 for Droid 4 (2nd-System Bootstrap / Recovery)
[ After installation boot into recovery and make a FULL backup while in Non-Safe mode to have a full 1st and 2nd system backup for disaster recovery. ]
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. WE DO NOT HAVE A FASTBOOT FOR THE DROID 4 YET. PLEASE USE CAUTION. **
[ Make sure you get the DROID 4 VERSION ]
Download Here
Instructions for Use
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.
SPECIAL THANKS TO:
Koush who develops such a GREAT recovery system and the makes the source available for others to use.
The Atrix dev team who I pulled the internal/external SD card support from
The Defy dev team that originally developed the Bootmenu source which I stripped down and used for the Splashscreen.
As always, let me know what you think!
Reserved for future use
Literally just turned on another phone after brickin my first one....flashing now
reigndropz said:
Literally just turned on another phone after brickin my first one....flashing now
Click to expand...
Click to collapse
Please be careful! I will be posting a Droid 4 ROM created from our current MotoBlur .215 system. This can be flashed as the Safe ROM in Safestrap for those who like to "play" with their phones / settings / bloatware. That way if you mess something up you'll be able to get into Recovery and restore a backup /system.
Hashcode said:
Please be careful! I will be posting a Droid 4 ROM created from our current MotoBlur .215 system. This can be flashed as the Safe ROM in Safestrap for those who like to "play" with their phones / settings / bloatware. That way if you mess something up you'll be able to get into Recovery and restore a backup /system.
Click to expand...
Click to collapse
Will do, can't wait for that! Hey quick question....let's say I wanted to flash a zip for a mod in Safestrap. I cant flash it when SS is disabled so I have to enable it but that restores the old system. Is this where I want to toggle , install the zip and then toggle back afterwards?
reigndropz said:
Will do, can't wait for that! Hey quick question....let's say I wanted to flash a zip for a mod in Safestrap. I cant flash it when SS is disabled so I have to enable it but that restores the old system. Is this where I want to toggle , install the zip and then toggle back afterwards?
Click to expand...
Click to collapse
There's no flashing zips to the "Non-Safe" ROM in Safestrap. You can only flash zips to the Safe ROM (with Safe Mode enabled).
You only run your original ROM when Safe Mode is disabled.
Hashcode said:
There's no flashing zips to the "Non-Safe" ROM in Safestrap. You can only flash zips to the Safe ROM (with Safe Mode enabled).
You only run your original ROM when Safe Mode is disabled.
Click to expand...
Click to collapse
The problem I'm having is When Safe Mode is enabled , I cant start any ROM. I enabled Safe Mode and then restored a nandroid backup but it wont load. It hangs after the Moto boot screen. The only way it seems to work is if I disable Safe Mode which in turn loads the previous ROM, so I'm always at square one. I'm sure I am doing this wrong, just not sure what exactly it is.
Anytime i flash something in safestrap i get a bootloop. I tried atric rom and the stock rooted rom. Same results. I would log cat but usb debugging isnt enabled
Sent from my DROID4 using Tapatalk
papi92 said:
Anytime i flash something in safestrap i get a bootloop. I tried atric rom and the stock rooted rom. Same results. I would log cat but usb debugging isnt enabled
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I'll download arctic and see what's happening with it. Should be able to flash that one. But the stock rooted /system dump needs some files tweaked I think.
reigndropz said:
The problem I'm having is When Safe Mode is enabled , I cant start any ROM. I enabled Safe Mode and then restored a nandroid backup but it wont load. It hangs after the Moto boot screen. The only way it seems to work is if I disable Safe Mode which in turn loads the previous ROM, so I'm always at square one. I'm sure I am doing this wrong, just not sure what exactly it is.
Click to expand...
Click to collapse
I'm not sure restoring a nandroid backup works that way. I'll get a MotoBlur .215 for use w/ Safestrap available for download here in a bit.
papi92 said:
Anytime i flash something in safestrap i get a bootloop. I tried atric rom and the stock rooted rom. Same results. I would log cat but usb debugging isnt enabled
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Looks like someone over at rootzwiki figured something out on this. According to the post, when in the bootloop, if you go back into recovery for a second time, and boot again, supposedly it lets you into the second ROM.
Here's the official post on it:
http://rootzwiki.com/topic/19673-ics-on-droid-4/
This guy loaded ICS from the Droid Kang version of RAZR and claims it's working....I was going to give it a try in a bit, and see if it works.
garlick2 said:
Looks like someone over at rootzwiki figured something out on this. According to the post, when in the bootloop, if you go back into recovery for a second time, and boot again, supposedly it lets you into the second ROM.
Here's the official post on it:
http://rootzwiki.com/topic/19673-ics-on-droid-4/
This guy loaded ICS from the Droid Kang version of RAZR and claims it's working....I was going to give it a try in a bit, and see if it works.
Click to expand...
Click to collapse
I've loaded it as well last week and it does work but there are too many issues. Besides the one he mentioned, when you turn the screen, it gets stuck in the horizontal view and wont revert back. Also, the above method doesnt work, at least not for me. Flashing a ROM does work though without going through those steps, I am just not having luck with flashing zip's of other kinds.
Cool. Jeff8732 didn't have a lot to say about it besides the keyboard didn't light up.
I also am a bit more interested in a CM9 based ROM, my understanding that's the one that Hashcode is working on....so I'll just hang tight and wait for that.
The links here are down. Anyone have working links? Thanks.
mystik1 said:
The links here are down. Anyone have working links? Thanks.
Click to expand...
Click to collapse
http://blog.hash-of-codes.com/how-to-safestrap/
There is the link that I used.
Delete files
I was wondering if i could delete any of the safestrap backups from my SD card. It's using well over 3GB. Right now I have the following files in the backup folder:
Nonesafe:
cahce.ext3.tar
data.ext3.tar
nandroid.md5
osh.ext3.tar
system.ext3.tar
systemorig.ext3.tar
Orig:
data.ext3.tar
Safe:
data.ext3.tar
I was wondering, would it be safe to delete any of those?
Links fixed.
Two requests:
Add a shell option to the recovery menu. I really miss that feature (from AmonRa recovery on my G1).
Integrate kexec. We ought to be able to intercept the boot process and load any kernel we want, safely. On the XDAndroid builds we replace /init with a shell script that does a bunch of manipulation before exec'ing the real Android init. For a kexec boot you add a kernel argument to flag that it was kexec'd. If the shell script sees that argument, it knows kexec was already done and just passes the boot on thru. If it doesn't see the argument, it kexecs the kernel you want.
Follow this thread for more details. I also added a kexec option to our Powerdown menu (in addition to Shutdown and regular Reboot) to allow fast swapping between kernels.
http://lists.xdandroid.com/pipermail/xdandroid-dev/2011-May/000327.html
Come to think of it - can we partition the internal SD card? If so, we could create a new root partition as well. Could just use the external SD too if all else fails.
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.
I inadvertently formatted my Sprint HTC One (ver. 1.29.651.6) with TRWP, now the phone is useless. There is no RUU for this version yet, please tell me there is something I can do restore the factory ROM or at least be able to copy my TWRP backup files to the now inaccessible internal storage.
Try sideloading a rom via twrp
Sent from my HTCONE using xda app-developers app
benmac33 said:
I inadvertently formatted my Sprint HTC One (ver. 1.29.651.6) with TRWP, now the phone is useless. There is no RUU for this version yet, please tell me there is something I can do restore the factory ROM or at least be able to copy my TWRP backup files to the now inaccessible internal storage.
Click to expand...
Click to collapse
Same here, I am usually good at doing these procedures... but last night, after loading the recovery (and followed directions from XDA and youtube video exactly), the internal storage was inaccessible from twrp, even though I saved the superuser zip in the download area, it could not be reached by the twrp file browser. In my desperate attempt to fix this, I followed another members poor advice and ended up essentially wiping the phone....
Now, I can boot into fastboot and twrp.... but it does not get past the white HTC start up screen and is stuck there.
If anyone can share a link to the best method to fix this issues, I appreciate it! Whether sideloading a rom, or restoring factory stock, please help!. Thank you.
The following does not work?
It seems that you have to fastboot oem lock first.
http://forum.xda-developers.com/showthread.php?t=2250904
Sprint_HTC_One_m7wls_1.29.651.7_RUU.zip
http://www.youtube.com/watch?v=0WWNZpaQBh8&hd=1
bwlinux said:
The following does not work?
It seems that you have to fastboot oem lock first.
http://forum.xda-developers.com/showthread.php?t=2250904
Sprint_HTC_One_m7wls_1.29.651.7_RUU.zip
http://www.youtube.com/watch?v=0WWNZpaQBh8&hd=1
Click to expand...
Click to collapse
Thank you sir! I will try this and report back on results. As much as I disliked stock and wanted to flash CM10.1 rom... at this point, I guess I will be glad to have things back to stock .... :good:
Good lookin out on that link, that's what I was looking for. Much appreciated.
u could use adb and transfer a rom to the sdcard
ggoomani said:
Thank you sir! I will try this and report back on results. As much as I disliked stock and wanted to flash CM10.1 rom... at this point, I guess I will be glad to have things back to stock .... :good:
Click to expand...
Click to collapse
Feeling very happy with my phone now that it has been fixed.. much thanks to your advice, I was able to look at the posts and video and recovered my device to re-lock, loaded stock RUU, then went right back to unlocking, installing recovery and rom (CM 10.1). 2nd time around worked as predicted.
It took a few nervous moments, but was well worth the effort now that the phone is essentially a nexus 5 like device for me. I will not miss Sense or blinkfeed at all. Never really used Zoe and camera software features.. Could those be installed separately as an additional camera app besides the standard CM supplied version?
ticklemepinks said:
u could use adb and transfer a rom to the sdcard
Click to expand...
Click to collapse
I also wiped everything on my phone and formatted the internal sd card with TWRP. I wanted a fresh start and thought I could just mount the internal sd card thru recovery and transfer my rom.zip off my laptop. Very BIG mistake, as I was unaware that TWRP does not mount/format properly! The above quote by Ms. Pinks was the first method that I tried, but did not work because TWRP rendered my internal memory useless.......phone would no longer recognize it. After several hours of failed attempts I just gave up for the night. In the morning, I did some reading on Clockwork Mod Recovery on other forums and it got alot of positive reviews........mounts/formats/wipes partitions properly! It just does'nt have some of the bells and whistles that TWRP does. I proceeded to flash it thru fastboot using the fastboot flash recovery cwm.image command. Once flashed, I was able to boot into recovery and reformat my internal sd card properly! After that, I used adb to push my rom.zip to the card and flashed away! I have tried all the functions in CWM and it works beautifully! (I love TWRP, but there are to many bugs in it's current state.....for this phone at least) Gonna be using CWM from now on. Hope my experience can help some other user's who screwed up too.
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