Related
Open Recovery
Version: 1.14
Credit for mankind (from alldroid) for the CustomUpdate, on which this recovery is based,
credit for poseidon (also from alldroid) for ADBRecovery.
Click this bar to view the full image.
Features:
- rooting the phone from menu (using ChainsDD su and SuperUser.apk)
- nandroid backup/restore from menu
- apply update *.zip files from menu (located in OpenRecovery/updates under the sdcard root folder, there is a sample one (just unpacks a file named "babble" to /system), no signatures are needed
- wipe data (factory reset)
- wipe cache
- wipe dalvik-cache
- adb in recovery, using bash shell
- run a script
- recovery options for applications
Installation:
1) You need to have the vulnerable recovery with exploit, see this thread how to flash it: http://modmymoto.com/forums/showthread.php?t=530112
2) Download and unpack the archive on the sdcard.
Usage:
1) Reboot into recovery (hold 'X' button on bootloader 90.78, on others hold camera button; until you see triangle)
2) Apply the update.zip
3) You are now in Open Recovery
this recovery for Motorola Milestone i think if we work together to customize it and let it work with Samsung Galaxy S I9000 what we need to rebuild the vulnerable recovery with exploit first then change some codes in the open recovery scripts.
so please let's work on it.
i get it from this link
http://modmymobile.com/forums/401-motorola-milestone/531599-open-recovery-v1-14-06-11-2010-a.html
Would make a HUGE step forward to have a recovery. Miss the nandroid backups
Lets hope some of the pro's can make it possible
I read that entire first post, then got to the end and saw that none of what I'd read was for the SGS at all!
Of course it'd be nice to have these things on the SGS, hopefully they'll come in time and the SGS will be getting updates at the same rate as CM for Nexus!
"For those asking, I am working on a recovery for Samsung Galaxy S phones. Give me a few days. They are nonstandard recoveries."
From:
http://twitter.com/clockworkmod
DocRambone said:
"For those asking, I am working on a recovery for Samsung Galaxy S phones. Give me a few days. They are nonstandard recoveries."
From:
http://twitter.com/clockworkmod
Click to expand...
Click to collapse
wow wow wow this is the best news we are waiting for you prof thanks...
Ok, I think I have a Samsung Galaxy S recovery ready. Someone join IRC. http://webchat.freenode.net/?channels=koush
https://twitter.com/clockworkmod/status/18810497362
Please be proficient with ADB and not **** a brick if your phone's recovery gets hosed
https://twitter.com/clockworkmod/status/18810529781
"Just got a rough recovery loaded onto the Samsung Galaxy S. Gonna need to tweak it to work on this phone. It's pretty different."
http://twitter.com/clockworkmod
Great work, be good to see something in action!
Hi, all
i am new with android OS.
i have an htc desire Z which was semi-bricked, it keeps on htc logo. then i search this forum for unbrick the device, and i found this rom, PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
i tried to update the file, and the device is ok after the update proses.
but, after i tried to open an application (i.e message), i can't go back to home. when i touch the home icon on the screen, the vibrate is on, but the screen is still.
is there something missing in the update proses?
sorry if i'm doing double post with this thread.
thank you all.
Well the problem is that you flashed a stock G2 ROM on the DZ... I think
omarsalmin said:
Well the problem is that you flashed a stock G2 ROM on the DZ... I think
Click to expand...
Click to collapse
+1
I agree
Sent from my HTC Vision using XDA App
Oh, I see..
Then i should look for DZ one. Could anyone here give me the link of stock DZ rom?
My hboot screen display:
Vision PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 2 2010
Here's what you're going to need to do. You need to download Terminal Emulator from the Android Market (the one by Palevich I think) and follow these steps:
Download the G2TempRoot.rar file I have attached. It also includes a DesireZ bootloader.
Extract the files to your desktop.
Now, you're going to ROOT your poor device. Follow these steps.
1. Make sure you have your USB debugging enabled and plug-er-in.
2. Open a command shell. Type in "cd Desktop\G2TempRoot" without the quotes of course...
3. Type in the following commands followed by enter after each one.
Code:
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
adb push busybox /data/local/tmp/busybox
adb push root /data/local/tmp/root
adb push rage /data/local/tmp/rage
adb shell chmod 0755 /data/local/tmp/*
adb push wpthis\wpthis-pre-OTA.ko /sdcard/wpthis-pre-OTA.ko
adb push wpthis\wpthis-OTA.ko /sdcard/wpthis-OTA.ko
adb push desirezboot\hboot-dzship.img /sdcard/hboot-dzship.img
--- All commands from here out are typed into the phone using Terminal Emulator, not ADB ---
4. Open up the Terminal Emulator you just installed on your phone and type the following:
Code:
/data/local/tmp/rage
Let it finish. After you see "Forked #### childs" press the Menu button on your keyboard and then tap "Reset terminal" on the screen.
5. Open the Terminal Emulator again. This time it will force close. Close it. Now, open the Terminal Emulator again, this time you should have a root shell.
6. If you did not apply the OTA update, type this into your terminal screen:
Code:
insmod /sdcard/wpthis-pre-OTA.ko
and press enter. It should say something about "function not implemented". This is normal. If it says anything else, you probably applied the OTA, and you need to reboot and start this process from step 4, replacing wpthis-pre-OTA.ko in step 6 with wpthis-OTA.ko.
7. Now, you're going to type the following commands into your shell. Make sure you double check EACH and EVERY command before you hit enter. Screwing up the first one, specifically has a nasty habit of producing bricks.
Code:
dd if=/sdcard/hboot-dzship.img of=/dev/block/mmcblk0p18
/data/local/tmp/root
sync
8. Now you should be able to reboot your phone into fastboot (trackpad button+power) and reflash using a HTC DesireZ RUU. Sorry, I have none of these in my files. Look in the wiki here, I think there are a few posted up.
9. If the RUU can't detect your phone, don't close the utility, YET. Search for rom.zip on your computer, and it'll be the one located in your temp folder. It should be ~ 260MB. Copy it to a place on your desktop, rename it PC10IMG.zip, and copy it to the root of your SD card using either an adapter and a SD reader, or a working phone that has SD storage. Then it's just a matter of booting into the bootloader with the Vol down + Power combination. It should go through the checks, and ask you to update if all worked correctly.
-- My guess is you didn't apply SuperCID to your phone before flashing G2 ROM? --
Wow, thanks for the reply. Quite confused though.
Yes, maybe i didn't apply SuperCID before flashing.
How can i make sure that USB debugging has been enabled?
Wow, well I guess this confirms it's fine to flash a stock G2 ROM to a Desire Z !
Those buttons won't be working because of the key mapping. The G2 and DZ have different hardware keyboard, so different keyboard mappings. Those capacitive buttons on the phone are effectively linked to the hardware keyboard, so just need mapping differently. It's possible to change the mapping, but probably makes more sense (no pun intended lol) just to flash a DZ ROM.
You can find the original 1.34 European RUU at http://forum.xda-developers.com/showthread.php?t=822908
There is also a newe 1.72 version, but be careful, because right now the current rooting methods don't work on that one.
To enable USB debugging you need to go into Menu->Settings->Applications->Development
Actually, the bootloader may have detected an incorrect digitizer controller. There is a difference in both the version of the bootloader and the order in which the firmwares partitions are flashed. You may want to reflash the G2 firmware again without switching out the bootloader to see if this fixes your issue. If not, the problem may actually lie in the partition 7 which was modified to unlock your phone. Try a reflash of the G2 PC10IMG.zip without switching your bootloader back if you have your heart set on stock Android. Watch the screen while it is flashing to make sure everything flashes ok. One of the TP entries should get skipped. TP stands for touch panel in this case. An incorrect driver could well explain why your icons aren't working.
For anyone interested, I flashed my G2 to DZ and back with great success, but to load the DZ rom I had to switch bootloaders and flashing it back to G2 flashed twice due to the difference in partition order to make sure everything went through OK. You may also have a corrupt .zip file. Open up your PC10IMG.zip file up in an archiver and run a test to make sure nothing fails. If the zip is corrupt its gonna load a bad digitizer driver everytime and possibly screw up the ROM.
Okay, i'll try again.
@steviewevie, Thanks for sharing.
If i use RUU_Vision_HTC_WWE....exe with a DZ that has a G2 rom inside, there will be no problem with the device?
@deliberate187, I guess there is nothing wrong with the zip file i have, coz i got it from this forum, and when i extract it with winrar, it extracts all files completely withouit fails.
deliberate187 said:
Actually, the bootloader may have detected an incorrect digitizer controller. There is a difference in both the version of the bootloader and the order in which the firmwares partitions are flashed. You may want to reflash the G2 firmware again without switching out the bootloader to see if this fixes your issue. If not, the problem may actually lie in the partition 7 which was modified to unlock your phone. Try a reflash of the G2 PC10IMG.zip without switching your bootloader back if you have your heart set on stock Android. Watch the screen while it is flashing to make sure everything flashes ok. One of the TP entries should get skipped. TP stands for touch panel in this case. An incorrect driver could well explain why your icons aren't working.
For anyone interested, I flashed my G2 to DZ and back with great success, but to load the DZ rom I had to switch bootloaders and flashing it back to G2 flashed twice due to the difference in partition order to make sure everything went through OK. You may also have a corrupt .zip file. Open up your PC10IMG.zip file up in an archiver and run a test to make sure nothing fails. If the zip is corrupt its gonna load a bad digitizer driver everytime and possibly screw up the ROM.
Click to expand...
Click to collapse
Interesting info. So those TP things in the ROM are something to do with the touch panel ?
I could be wrong, but the TP files are Atmel firmwares. If I'm not mistaken Atmel is the manufacturer of the controller chips used in the touch panels on Android phones.
Sent from my T-Mobile G2 using XDA App
Sirs,
I believe I did the same, that is flashing a G2 ROM to a Desire Z phone.
Now I followed the instructions till I reached 8 and 9, I downloaded: RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe, tried it, it gave me this error on the PC:
"Error [156]: image error
The rom update utility cannot update your android phone.
Please get the correct rom update utility and try again."
Searched for rom.zip, changed its name to PC10IMG.zip, took the sd card out, copied the file, rebooted the phone, the bootloader didn't recognize the ROM.
This what flashed so fast on the screen:
"SD Checking ...
Loading ... [PC10DIAG.zip]
No image!
Loading ... [PC10DIAG.ngh]
No image or wrong image!
Loading ... [PC10IMG.zip]
Lack of heap!
Loading ... [PC10IMG.nbh]
No image or wrong image!"
I hope these info will help:
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 2 2010, 17:59:38
The mobile works, but none of the bottom icons do: Home, Menu, Back, and Search.
The keyboard isn't matching 100% specially with the special characters.
At boot, HTC signs appear, then "T mobile G2 with Google" appears short after, then the home screen.
Settings/About phone:
Model number: T-mobile G2
Android Version
2.2
Baseband Version
12.22.60.09.bU_26.02.01.15_M2
Kernel version
2.6.32.17-g814e0a1
[email protected]#1
Build number
1.19.531.1 CL255798 release-keys
I m lost as you may see!
I don't know what else I made wrong in addition to flashing the wrong ROM.
Hey all,
Just made a splash image that I think you guys might appreciate. My friend showed me the picture and I decided to do the necessary changes to make it into a splash.
For your viewing pleasure
To flash: Download the zip then with an unlocked (S-OFF) bootloader, flash the new_splash.img file to your phone:
adb reboot bootloader
fastboot flash splash1 new_splash.img
fastboot reboot
i would rather have it as a background
my boot image shows 1 micro second. not worth even thinking about changing it.
Well the png is there too so u can use it as a background I guess
Powers88 said:
Well the png is there too so u can use it as a background I guess
Click to expand...
Click to collapse
Some kind of bloody :-D but looks great, although I'm running a MacBook bit I also love my Android mobile.
Does it work to flash this lb other Android systems like 2. 1/ 2. 2k any experiences?
Thx guys
sent from my DEFY using XDA App
This is just a splash image file so as long as your screen size is 480 x 800. You can search for how to change the splash image for your particular phone and then just use this file. I'm sure it will work on any version of android
Anyone have the adb commands handy for pulling the stock splash image just in case I want to put it back?
This is a copy of the original splash that I found in another thread.
did that last attachment post?
lets try that again. this is the default splash.
Nitemare3219 said:
Anyone have the adb commands handy for pulling the stock splash image just in case I want to put it back?
Click to expand...
Click to collapse
Even though the original splash is posted, the commands to pull the old one are to be executed from a root shell and are as follows:
Code:
dd if=/dev/block/mmcblk0p19 of=/mnt/sdcard/splash.img
You may have to do a search for it because when I pulled mine it put it into a random folder on my computer
I followed 2 guides to get my phone rooted and get my HBOOT patched to allow S-OFF - AlphaRev and Clockwork Recovery 2.5.0.1.
I want to get rid of the Joker from start up - had I would of known that I would of remained S-ON till they fixed that. That did permanently add Clockwork Recovery to the recovery area. There is a new version I downloaded and told it to install from ZIP and it reloaded and came to 2.5.0.7 but it never permanently patched it in. I am seriously considering going to AmonRA if it is available - I have done so many searches my head is spinning from lack of finds.
Am I missing something or is this something that needs to be done via ADB/Fastboot? If thats the case, I may need some help.
Permanently flashing recoveries has to be done through fastboot with a .img file, the update.zip way will never permanently flash a recovery, unfortunately. Here is a download link for the 2.5.0.7 recovery image, here's how you flash it (you must have the android sdk installed, and you have to have the fastboot.exe command in either \tools or \platform-tools):
Open up a command prompt window and type this:
fastboot flash recovery C:\location\of\recovery.img
When you reboot into recovery again via hboot, it should be 2.5.0.7.
As for the splash screen, that can be changed too (thank god, I hated the joker screen as well). Follow the instructions on this thread, there are plenty of screens to choose from, including the stock t-mobile screen.
If you need anything better explained, I can try to better explain it.
Thanks for the tips. I did find one I wanted - simple and Tmobile-ish. I do have the SDK installed with all updates from the Java Frontend that it uses BUT I still do not have fastboot.exe
I tried one from a friend but it keeps sticking at WAITING FOR DEVICE. Do I need to be in fastboot first on the phone then do this? It is detecting the phone with ADB devices command.
I'm pretty sure you need to be in fastboot to do this. Why the need for permanent recovery anyway?
I tried fastboot mode on the phone and it worked - Thanks for the tip! Flashed just fine and with help of some of the threads on the themes area i got the splash screen modified. (joker is gone - thank goodness!)
I am wanting to change the boot animation - I know how that works but I can't seem to find any for the MT3GS.
Again, I appreciate the tips. They have been helpful. ( I had to transpose what your talking about to the mac - and find fastboot for the mac - HTC had it on their site with a google search )
Yeah, for some reason google stopped compiling fastboot.exe for the sdk, it sucks. I just kept mine from older revisions of the sdk, and I copy it over whenever there's an update.
And at least for me, (@ whoever asked), permanent recoveries are significantly more convenient, and it saves time. It's nice to actually be able to use hboot recovery option, bypassing the stock recovery. It's also nice to be able to write to /system without a r/w overlay or without having to be in recovery.
MusicMan374 said:
Yeah, for some reason google stopped compiling fastboot.exe for the sdk, it sucks. I just kept mine from older revisions of the sdk, and I copy it over whenever there's an update.
And at least for me, (@ whoever asked), permanent recoveries are significantly more convenient, and it saves time. It's nice to actually be able to use hboot recovery option, bypassing the stock recovery. It's also nice to be able to write to /system without a r/w overlay or without having to be in recovery.
Click to expand...
Click to collapse
Not only that but it keeps that wonderfull 800k space free I am a space freak and like all free space and things organized. But the fact that if I screw up a flash - and for some reason I don't have a rom downloaded I can pop in my NANDROID backup card (which is stored in a safe under my foundation) and restore. That way I don't have to download update.zip anymore.
But I am seriously considering AmonRA - I just can't find a copy for my phone. Looks like it is for older phones unless I am missing something.
Does this phone support any other MicroSD cards 16GB or above?
thronka said:
Not only that but it keeps that wonderfull 800k space free I am a space freak and like all free space and things organized. But the fact that if I screw up a flash - and for some reason I don't have a rom downloaded I can pop in my NANDROID backup card (which is stored in a safe under my foundation) and restore. That way I don't have to download update.zip anymore.
But I am seriously considering AmonRA - I just can't find a copy for my phone. Looks like it is for older phones unless I am missing something.
Does this phone support any other MicroSD cards 16GB or above?
Click to expand...
Click to collapse
There is no AmonRA recovery for our phone, I don't believe. It was requested of him after we got s-off, but we don't know since he doesn't own a slide, and it's awfully hard to develop for a phone you don't have, haha
Well the easiest way to flash a recovery is to make sure you have CM7, or CM6, or separately put the files, MTD0 and Flash_Image in /Data/Local So if you have that, Here it is:
You just need to go to terminal Emulator type
Su
Flash_image recovery /sdcard/xxxx/xxxx.img
(Making sure you realize that the x's represent directories and file names)
For example I would put mine on the Root of the SD card and mine would look like this
Flash_Image recovery /sdcard/recovery.img
Sent from my T-Mobile myTouch 3G Slide using XDA App
iDaZzLeFatHoeZz said:
Well the easiest way to flash a recovery is to make sure you have CM7, or CM6, or separately put the files, MTD0 and Flash_Image in /Data/Local So if you have that, Here it is:
You just need to go to terminal Emulator type
Su
Flash_image recovery /sdcard/xxxx/xxxx.img
(Making sure you realize that the x's represent directories and file names)
For example I would put mine on the Root of the SD card and mine would look like this
Flash_Image recovery /sdcard/recovery.img
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Been flashed for a while now. I did not know this method but it is good to have and try when there is an update.
I have been tinkering with the ArayrayMod Revamped files since Arayray moved on to a MyTouch 4G. (traitor! LOL)
Looks like I may be going into the developing side of roms but I am just waiting for approval to post the rom for public viewing. a .32 kernel with Wifi calling included and thats really it - well retaining OC on that rom as well.
Much more tough than I thought doing this by hand - and I always thought my Unix Administration skills would be wasted.
[HOWTO] ClockworkMod Recovery & TWRP - Upgrade/Downgrade (Touch/Non-Touch Recovery)
IF YOU TRASH YOUR PHONE USING THIS PROCEDURE, THEN IT IS A VERY GOOD INDICATION YOU ARE AN IDIOT AND SHOULD NOT BE FLASHING ANY ROMS NOR PARTICIPATING ON THESE FORUMS. . . . JUST SAYIN'. . . .
Please be VERY careful when using this method as you can brick your phone. Make sure you triple check the file you downloaded is the right size and placed in the right area, but most importantly that the command lines you type are exactly right. If you are not comfortable using this method, then please do not and go find a flashable version of these recoveries.
I've posted a procedure to format/'flash' your recovery while on your phone in one of the threads on here and was asked by a Forum Mod to make a quickie guide to be placed as a sticky on the dev boards so others might benefit.
Anyway, here is a very quick and easy way to change your ClockworkMod recovery with a couple of command lines.
The TWRP link is in the second post.
Now for the ClockworkMod Instructions:
1. First, go here and look up your ClockworkMod recovery that pertains to your phone: http://www.clockworkmod.com/rommanager
2. Download the .img file for your phone and save it on your computer.
3. Rename the .img file to recovery.img and save it to your internal sd card of your phone. For example: recovery-clockwork-6.0.1.4-hercules.img ------> recovery.img
4. Open up Terminal Emulator on your phone and type the following 2 commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
(please note the second command is a one line command with spaces between "dd & if=" and ".img & of=")
If your Rom identifies your internal sdcard as /emmc instead of /sdcard, then make the adjustment to command line (dd if=/emmc/recovery.img) instead of what is posted above.
That simple.
You can also issue these commands from adb shell if you are connected to your computer.
If Terminal Emulator does not have Superuser or SuperSU permissions for root privileges then make sure it does. You can also go from NON Touch CWM to Touch CWM using this and vice versa. Simply make sure you have the right recovery for your phone and rename it to recovery.img.
As for explanations:
dd if= command is a common Unix program whose primary purpose is the low-level copying and conversion of raw data.
dd stands for "data description"
if stands for "input file"
of stands for "output file"
the = is the location of the data you are using. ie. /sdcard/recovery.img
the /dev/block/mmcblk0p22 is the location/partition of the recovery on your phone.
So essentially you are doing a low level rewrite of the recovery image on your phone via command lines.
***Also, the best way to remember this command line is to not to. Copy the command line and save it to your own personal contact info in Google under Notes and then you will have it with you wherever you go. You really do not want to mess with getting it wrong. You could brick your phone if you mess things up.
Anyway, I hope this helps. . . . it really is very easy to execute without fault.
Works with TWRP too.
This also works with changing to and from TWRP. Download the image (for our phones it's TWRP 2.3.1.1) rename it to recovery.img and follow the above instructions and you are good to go.
Follow this link to get the image file: http://teamw.in/project/twrp2/101
***I attached the old TWRP 2.2.2.0 is case you run into problems with the newer versions not restoring backups properly or renaming backups correctly.***
Excellent Thread, I hope Dev's requiring specific CWM versions can link to your post.
Thanks for your efforts.
Noellenchris
XDA Forum MOD
Thanks for the instructions! Thanks even more for explaining the command lines.
Just thought I'd point out a small bug with the Touch Recovery. If you flash one of the newer ICS roms like Darkside Evolution through the Touch Recovery, once booted, the ROM WILL NOT SLEEP through time out. I've confirmed this with 2 separate ICS roms. Flashing non-touch recovery through Rom Manager fixes this problem.
Wouldn't it be easier to use gscript and run the commands as you need them?
Thanks for the HOW TO I actually was looking for it.
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
dextroamphetamine said:
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
Click to expand...
Click to collapse
For some people Rom Manager doesn't work. On the T-Mobile SGH-T989 Galaxy SII, Rom Manager will only allow you to go to 5.0.2.6 not 5.0.2.7. And, I think you have to upgrade Rom Manager to go to Touch. I bought Rom Manager, and don't use Touch Recovery, so I am not sure.
I like to use the command structure verses program because I know it works, it's fast, and I can see the results if an error occurs.
Oh yeah...this was really simple...Thanks...went from Touch back to Non Touch.
Give this a try
If you want a simple way to flash the Touch Recovery then give this a try. I will be adding the Hard Recovery as well in the next release.
SGSII T989 Root Toolkit
http://forum.xda-developers.com/showthread.php?t=1650908
http://forum.xda-developers.com/showthread.php?p=26200755
I get a write error: No space left on device. 1001+0 records in 1000+0 records out 512000 bytes transferred in 0.132 secs.
I reboot into recovery and it's still on 5.0.2.6
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
albanianbrotha said:
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
Click to expand...
Click to collapse
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
hobakill said:
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
Click to expand...
Click to collapse
Haha no worries bro. I mean worries that it failed for no reason, but I already sent it in, he just got it today. Same person you linked. Definitely trying to install ics again when i get it. Plus I think the ota ics for tmo came out yesterday or something? Probably a better experience than what was already out there with the radio and stuff.
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
MustangFTW said:
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
Click to expand...
Click to collapse
No! Do NOT use this procedure with that file extension!
What recovery are you trying to install? And for what phone? I briefly ran my cursor over the various files and the download links are either .img or .zip files. I did not see .ndif file extension.
PM me if you need additional help.
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
fresherthanU said:
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
Click to expand...
Click to collapse
You're welcome, I'm glad I could help you. But, the link to the .img files is in the OP instructions. . . .
Unfortunately this method did not work for me... I have tried many ways to update my CWM and none of them worked, it is almost hopeless for me
Good news! You made front page! http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)