Hi All,
I've been a ClockworkMod Recovery user since I started with Android devices and never had a problem so I'm still happily using it today. The issue is that I can never seem to find a flashable version of the latest version so I'm making this post to provide that if anyone is interested. I'm using the loki-patch tool from djrbliss to patch the recovery image and then I create a flashable zip to install it. I wrote a little script that I run under Ubuntu to patch the recovery as well as create the zip package so keeping up with the latest recoveries should be simple. I've modified the way this flashes so that both the loki patch and loki flash tools are used which perform additional checks to make sure a valid bootloader base is being used. I re-used the loki-doki script from attn1 and modified it a little to do recoveries instead of bootloaders.
The flash process performs the following:
1. Extracts a boot image directly from the device, therefore much safer and more generic.
2. Using loki-patch, applies the loki patch to the CWM recovery image using the extracted boot image.
3. Using loki-flash, flashes the patched recovery image to the device. As per djrbliss, there are checks in the tool to avoid unsupported bootloaders so it's obviously much safer.
About the images:
- This is the latest touch and non-touch versions of ClockworkMod v6.0.4.7
- This is for the Samsung Galaxy S4 (Verizon) only!
- This is for bootloader version I545VRUAMDK only!
- As with any other downloads here, flash at your own risk!
Installation:
- This is meant to install via recovery so just copy to your device, boot into recovery, and install from zip.
All thanks go to:
- djrbliss for his loki tools found here: https://github.com/djrbliss/loki
- The ClockworkMod Team who provides the recoveries here: https://www.clockworkmod.com/rommanager
- attn1 for his loki-doki install script found here: http://rootzwiki.com/topic/41841-lo...tom-boot-image-on-att-and-verizon-galaxy-s-4/
.
I had been looking for the same thing for a few days. Made my own zip to get on 6.0.4.7
Thanks for doing this... Rom manager hasn't been working for me flashing, but I did just get pointed to flashify in another thread and that worked well.
Good to have options!
Sent from my SCH-I545 using xda app-developers app
Thank you for this.
Sent from my SCH-I545 using Tapatalk
brandonair95 said:
Thank you for this.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I tried 6.0.4.7 and it won't flash older update binaries... Philz version has the option to disable this issue and cwm 6.0.4.4 still works great for me...but 6.0.4.7 won't flash most of the touchwiz Roms available
Don't know why I quoted you...habit of quoted replies I guess...lol
jamesd1085 said:
I tried 6.0.4.7 and it won't flash older update binaries... Philz version has the option to disable this issue and cwm 6.0.4.4 still works great for me...but 6.0.4.7 won't flash most of the touchwiz Roms available
Don't know why I quoted you...habit of quoted replies I guess...lol
Click to expand...
Click to collapse
I'd be curious - if you install flashify and flash the latest CWM with that, see if you have the same issue?
Or let me know what binary you're trying to flash and I'll test it as well.
vanberge said:
I'd be curious - if you install flashify and flash the latest CWM with that, see if you have the same issue?
Or let me know what binary you're trying to flash and I'll test it as well.
Click to expand...
Click to collapse
Yes it would still persist...it uses only new updater scripts as tho old ones have been deemed "dangerous"
This is a good thread to have going for sure. I'm on Philz as well but this should help a lot of folks out. Good work
Sent from my SCH-I545 using Tapatalk
Related
Ok i would like to kno if there's a method on the lg p500 for updating the custom recovery clockworkmod from the phone for example passing to 5.0.2 to 5.0.2.7 without using LGMD or a software like ROM Manager...so a way through the actual recovery for updating itself or through the emulator terminal.
Hesediel said:
Ok i would like to kno if there's a method on the lg p500 for updating the custom recovery clockworkmod from the phone for example passing to 5.0.2 to 5.0.2.7 without using LGMD or a software like ROM Manager...so a way through the actual recovery for updating itself or through the emulator terminal.
Click to expand...
Click to collapse
Well, most people update their recoveries through normal flashable zips.
You just flash it using the old recovery, reboot it and you will see the new one.
There is a list of flashable recovery zips here, but it's a bit outdated:
http://forum.xda-developers.com/showthread.php?t=1065197
Here you can also find the new Amonra 3.06 (the best IMO): http://forum.xda-developers.com/showpost.php?p=19885521&postcount=292
If you want I can make you a flashable zip of the new CWM 5.0.2.7 as well. Just let me know.
Wrong section
Sent from my LG-P500 using Tapatalk
MaKTaiL said:
Well, most people update their recoveries through normal flashable zips.
You just flash it using the old recovery, reboot it and you will see the new one.
There is a list of flashable recovery zips here, but it's a bit outdated:
http://forum.xda-developers.com/showthread.php?t=1065197
Here you can also find the new Amonra 3.06 (the best IMO): http://forum.xda-developers.com/showpost.php?p=19885521&postcount=292
If you want I can make you a flashable zip of the new CWM 5.0.2.7 as well. Just let me know.
Click to expand...
Click to collapse
Well than what are u waiting for?,dying for the new recovery
Sent from my LG-P500 using Tapatalk
MaKTaiL said:
Well, most people update their recoveries through normal flashable zips.
You just flash it using the old recovery, reboot it and you will see the new one.
There is a list of flashable recovery zips here, but it's a bit outdated:
http://forum.xda-developers.com/showthread.php?t=1065197
Here you can also find the new Amonra 3.06 (the best IMO): http://forum.xda-developers.com/showpost.php?p=19885521&postcount=292
If you want I can make you a flashable zip of the new CWM 5.0.2.7 as well. Just let me know.
Click to expand...
Click to collapse
Or just flash using the Flash Image GUI App... its in my signature...
its an app that flashes kernels and recoveries without booting to the recovery... you dont even need a flashable zip... just choose your recovery.img file and select Flash... n u have a new recovery...
WRONG SECTION BTW...!
Found something ..... at download.clockworkmod.com/recoveries/ there was a cwm 5.0.2.7 zip ( for p500) downloaded it and it had META-INF so is it a flashable zip...
Sent from my LG-P500 using Tapatalk
I'm trying to get into the bootloader to flash an older version of TWRP. I'm holding various combinations of buttons down when rebooting but the phone either goes to Recovery, Odin, or normal boot. The "bootloader" boot option in TWRP doesn't work either, it just goes to normal boot. What am I missing? I know for many phones the bootloader is accessed by holding VOL Down + Power when rebooting but that's not working on the Note 2.
Thanks.
slicknick27 said:
I'm trying to get into the bootloader to flash an older version of TWRP. I'm holding various combinations of buttons down when rebooting but the phone either goes to Recovery, Odin, or normal boot. The "bootloader" boot option in TWRP doesn't work either, it just goes to normal boot. What am I missing? I know for many phones the bootloader is accessed by holding VOL Down + Power when rebooting but that's not working on the Note 2.
Thanks.
Click to expand...
Click to collapse
I believe the reason why you can't boot into bootloader is because it has something to do with the Unlock Bootloader method/exploit. I'm going to take a shot in the dark and say the exploit is not the standard unlock method so therefore you can't boot into the bootloader.
Also, you can flash a recovery a different way. Download the Goo.im Manager app in the Google Play Store and when you go in the app, you can search the recoveries and it will flash them from the app for you.
DroidOnRoids said:
I believe the reason why you can't boot into bootloader is because it has something to do with the Unlock Bootloader method/exploit. I'm going to take a shot in the dark and say the exploit is not the standard unlock method so therefore you can't boot into the bootloader.
Also, you can flash a recovery a different way. Download the Goo.im Manager app in the Google Play Store and when you go in the app, you can search the recoveries and it will flash them from the app for you.
Click to expand...
Click to collapse
Hey, thanks for shedding some light on this. And I'm going to try flashing from the Goo.im manager, that sounds easier at this point, too.
slicknick27 said:
Hey, thanks for shedding some light on this. And I'm going to try flashing from the Goo.im manager, that sounds easier at this point, too.
Click to expand...
Click to collapse
No problem, man. Just make sure you flash the right recovery file because if you are broad on your search, it will give you a list of different recoveries for different devices. Search the version of TWRP you want with 'i605'.
DroidOnRoids said:
No problem, man. Just make sure you flash the right recovery file because if you are broad on your search, it will give you a list of different recoveries for different devices. Search the version of TWRP you want with 'i605'.
Click to expand...
Click to collapse
Unfortunately there are no older versions of TWRP in the Goo.im manager app. This is off-topic from my original question but it's the reason I was trying to get into the bootloader in the first place. Do you know of any way to downgrade TWRP to a previous version on this phone other than the flashing from bootloader method?
slicknick27 said:
Unfortunately there are no older versions of TWRP in the Goo.im manager app. This is off-topic from my original question but it's the reason I was trying to get into the bootloader in the first place. Do you know of any way to downgrade TWRP to a previous version on this phone other than the flashing from bootloader method?
Click to expand...
Click to collapse
Hm, you searched with i605, right? Well, I searched and found that on Goo.im, it is actually t0ltevzw.
Here are all the TWRP builds for the VZW Note 2 from Goo.im: http://goo.im/devs/OpenRecovery/t0ltevzw/
EDIT: Here's our device page on the TWRP website: http://teamw.in/project/twrp2/133
EDIT 2: If I were you, try not to flash a recovery using Odin. I wouldn't risk screwing up the unlocked bootloader exploit. Lastly, if you didn't know, do NOT in any way flash a custom rom using Odin. It's bad news for your phone.
Edited again because I forgot fastboot requires bootloader access lol
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
DroidOnRoids said:
Hm, you searched with i605, right? Well, I searched and found that on Goo.im, it is actually t0ltevzw.
Here are all the TWRP builds for the VZW Note 2 from Goo.im: http://goo.im/devs/OpenRecovery/t0ltevzw/
EDIT: Here's our device page on the TWRP website: http://teamw.in/project/twrp2/133
EDIT 2: If I were you, try not to flash a recovery using Odin. I wouldn't risk screwing up the unlocked bootloader exploit. Lastly, if you didn't know, do NOT in any way flash a custom rom using Odin. It's bad news for your phone.
Edited again because I forgot fastboot requires bootloader access lol
Click to expand...
Click to collapse
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
slicknick27 said:
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
Click to expand...
Click to collapse
So the 2.4.0.0 is the version you want, correct? And which file of this recovery version did you download? If you tried downloading and installing using the Goo.im app, try downloading the zip file from your computer and transferring it over to your SD Card. From there you can reboot to the existing recovery, install it, and reboot the recovery.
If that doesn't work either, tell me and I can figure out a different option.
DroidOnRoids said:
So the 2.4.0.0 is the version you want, correct? And which file of this recovery version did you download? If you tried downloading and installing using the Goo.im app, try downloading the zip file from your computer and transferring it over to your SD Card. From there you can reboot to the existing recovery, install it, and reboot the recovery.
If that doesn't work either, tell me and I can figure out a different option.
Click to expand...
Click to collapse
Actually, if I can I'd like to downgrade to TWRP 2.3.3.1, which was the version I installed back when I got the phone in December.
On Goo.im web site it is:
openrecovery-twrp-2.3.3.1-t0ltevzw.zip
It is my understanding though that you can't flash TWRP from within TWRP?
slicknick27 said:
Actually, if I can I'd like to downgrade to TWRP 2.3.3.1, which was the version I installed back when I got the phone in December.
On Goo.im web site it is:
openrecovery-twrp-2.3.3.1-t0ltevzw.zip
It is my understanding though that you can't flash TWRP from within TWRP?
Click to expand...
Click to collapse
You can flash CWM in TWRP, TWRP in CWM, TWRP in TWRP, or CWM in CWM. All you need to do is flash it and then go to the recovery options and hit Reboot Recovery.
Where did you hear that you can't flash TWRP in TWRP?
DroidOnRoids said:
You can flash CWM in TWRP, TWRP in CWM, TWRP in TWRP, or CWM in CWM. All you need to do is flash it and then go to the recovery options and hit Reboot Recovery.
Where did you hear that you can't flash TWRP in TWRP?
Click to expand...
Click to collapse
OK, yeah, I was told in another thread that I couldn't flash TWRP with TWRP.
So, I just want to clarify, I can flash an older version of TWRP over an newer version of TWRP already installed -- as if I was flashing any regular .zip?
slicknick27 said:
OK, yeah, I was told in another thread that I couldn't flash TWRP with TWRP.
So, I just want to clarify, I can flash an older version of TWRP over an newer version of TWRP already installed -- as if I would flash any regular .zip?
Click to expand...
Click to collapse
Yes, you can do that because it's going to completely overwrite the other version of TWRP. It doesn't matter what version you flash because it's going to be all on its own. The previous recovery doesn't benefit from a newer version of a recovery. You're safe to do it
EDIT: When I had my Galaxy Nexus, TWRP was brand spanking new so I had to downgrade a lot because of all the bugs presented in the later releases.
DroidOnRoids said:
Yes, you can do that because it's going to completely overwrite the other version of TWRP. It doesn't matter what version you flash because it's going to be all on it's own. The previous recovery doesn't benefit from a newer version of a recovery. You're safe to do it
EDIT: When I had my Galaxy Nexus, TWRP was brand spanking new so I had to downgrade a lot because of all the bugs presented in the later releases.
Click to expand...
Click to collapse
Phew. OK. Well again I thank you for sticking with me and clearing this up. I suspected I could do that in the first place but was confused by information I was given otherwise. Off I go to recovery!
slicknick27 said:
Phew. OK. Well again I thank you for sticking with me and clearing this up. I suspected I could do that in the first place but was confused by information I was given otherwise. Off I go to recovery!
Click to expand...
Click to collapse
Good luck! Let me know when it's a success.
DroidOnRoids said:
Good luck! Let me know when it's a success.
Click to expand...
Click to collapse
Well, TWRP verified the checksum and the modem installed successfully. But apparently it turns out the problem was not as it originally seemed.
When I downloaded the older version of TWRP, I opened its .MD5 file again just to check, and I noticed that the .MD5 files for the zips on Goo.im (or at least OpenRecovery's ZIPS) omitted the asterisk that precedes the filename:
Code:
d4624c4f8c9427b6137b2b97902e76b3 openrecovery-twrp-2.4.1.0-t0ltevzw.zip
Whereas with other .MD5 files that I've created (including the .MD5 file for the modem zip that was failing verification in TWRP), I've used an asterisk before the filename:
Code:
d4624c4f8c9427b6137b2b97902e76b3 [B][COLOR="Red"]*[/COLOR][/B]openrecovery-twrp-2.4.1.0-t0ltevzw.zip
So after the modem flashed successfully on TWRP 2.3, I decided to try flashing it again (with the asterisk omitted from the MD5 file) on the latest TWRP 2.4.1.0. It flashed just fine. So the issue seems to be TWRP getting hung up on the asterisk that precedes the filename in MD5 files -- though this doesn't happen all the time because I've flashed many MD5 files with the asterisk successfully.
A bug in TWRP? Or maybe I shouldn't be using the asterisk at all. In any case, I'm back on TWRP 2.4.1.0 with the modem flashed.
EDIT: And I learned that you can flash TWRP in TWRP
slicknick27 said:
Well, TWRP verified the checksum and the modem installed successfully. But apparently it turns out the problem was not as it originally seemed.
When I downloaded the older version of TWRP, I opened its .MD5 file again just to check, and I noticed that the .MD5 files for the zips on Goo.im (or at least OpenRecovery's ZIPS) omitted the asterisk that precedes the filename:
d4624c4f8c9427b6137b2b97902e76b3 openrecovery-twrp-2.4.1.0-t0ltevzw.zip
Whereas with other .MD5 files that I've created (including the .MD5 file for the modem zip that was failing verification in TWRP), I've used an asterisk before the filename:
d4624c4f8c9427b6137b2b97902e76b3 *openrecovery-twrp-2.4.1.0-t0ltevzw.zip
So after the modem flashed successfully on TWRP 2.3, I decided to try flashing it again (with the asterisk omitted from the MD5 file) on the latest TWRP 2.4.1.0. It flashed just fine. So the issue seems to be TWRP getting hung up on the asterisk that precedes the filename in MD5 files -- though this doesn't happen all the time because I've flashed many MD5 files with the asterisk successfully.
A bug in TWRP? Or maybe I shouldn't be using the asterisk at all. In any case, I'm back on TWRP 2.4.1.0 with the modem flashed.
EDIT: And I learned that you can flash TWRP in TWRP
Click to expand...
Click to collapse
I would bring that to their attention and see why that's the case on their recovery. Anyway, glad that everything is figured out and running perfectly. :good:
DroidOnRoids said:
I would bring that to their attention and see why that's the case on their recovery. Anyway, glad that everything is figured out and running perfectly. :good:
Click to expand...
Click to collapse
Yes I'm going to report it.
Take it easy.
I followed a tutorial to successfully root my phone in the past, but I need to do it again and want to understand it a bit better this time. (I'm doing it using command-line heimdall from Ubuntu.) Doing "sudo heimdall flash --recovery recovery.img --no-reboot", the tutorial provided a recovery.img which went on to install CWM. Then from within the rooted phone I installed another custom recovery. But do I need to do this as a 2-step process like this, or can I simply for the first time on an UNrooted phone do "sudo heimdall flash --recovery SOME-OTHER-RECOVERY.img --no-reboot"?
The tutorial also provided a CWM-SuperSU-v0.87.zip. What's actually the purpose of this, and do I even need it?
It also came with an s3pit.pit, but I didn't actually do anything with this. Did the 'heimdall' command that I ran do something with this, or is it safe to do the rooting process without it?
I'm asking because I'd like to root my phone not blindly following one tutorial which provided its own files (http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-linuxubuntu/). Surprisingly there are no other decent tutorials out there on rooting this phone from Ubuntu, any ideas?
You can flash any compatible recovery in step 1. I see no reason to flash something you don't need. I recommend philz recovery (link in signature) but twrp is good. I would stay away from cwm as its not great if you want to go to 4.2 android roms
Having a recovery is one thing but actually you're still not rooted. You need recovery to flash a zip which will give you root. Unless you just want to flash a custom rom, in which case you only need the recovery and can skip flashing root stuff
Sent from my GT-I9300 using Tapatalk 2
I wasn't aware of these distinctions, thanks. What alternative zips that give me root could you recommend? I would rather use one that is on xda-developers rather than on a blog post on some random website. Does it need to be compatible with the recovery, or would any 'root zip' meant for the i9300 work?
So is it possible to root the stock default ROM by just flashing a root zip using the stock recovery? Or is a custom recovery needed for this?
Roots are in Development section as said CWM is rather out of date now .
Both TWRP and Philz work well .
jje
I think I have misunderstood. In the first response it said "You need recovery to flash a zip which will give you root", which I assumed was the "CWM-SuperSU-v0.87.zip" I mentioned in the original post. I'm wondering about alternatives for this zip, not for the recovery (for the recovery I'll use Philz or TWRP as has been suggested).
iamthemandroid said:
I think I have misunderstood. In the first response it said "You need recovery to flash a zip which will give you root", which I assumed was the "CWM-SuperSU-v0.87.zip" I mentioned in the original post. I'm wondering about alternatives for this zip, not for the recovery (for the recovery I'll use Philz or TWRP as has been suggested).
Click to expand...
Click to collapse
You don't need an alternative. It contains 2 things. The su binary (what gives you root) and the super user app (a graphical "gatekeeper" to root). If you're applying root to a handset, you'll be using these things
Sent from my GT-I9300 using Tapatalk 2
here are the latest cwm/twrp recoveries made by dhacker29 in recovery flashable format:
https://drive.google.com/folderview?id=0B-53iD-71B3iTWhzNVc0QkdJSkk&usp=sharing
they can't be flashed with stock recovery, can be flashed only with existing cwm/twrp. if you're unlocked but running stock recovery, they can be flashed with safestrap.
all thanks to dhacker29!
source: http://androidhosting.org/Devs/Dhacker29/MotoX/
So instead of using rsd to go back to stock, we can flash this as we would a custom ROM?
I can't seem to update TWRP, trying to flash using my current version of TWRP.
Sent from my XT1060 using Tapatalk
Thank you very much
Edit: I just fastbooted in TWRP 2.6.3.2 but when in TWRP it shows 2.6.3.0 still. It said it updated though through fastboot.
mroneeyedboh said:
So instead of using rsd to go back to stock, we can flash this as we would a custom ROM?
Click to expand...
Click to collapse
no, these zips update your cwm/twrp recovery to the latest version. if you want to avoid using rsd, make a nandroid of your stock unmodified system.
DonKilluminati23 said:
I can't seem to update TWRP, trying to flash using my current version of TWRP.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
what is the problem, did the flash fail? did you reboot recovery after installing?
rebretz000 said:
Thank you very much
Edit: I just fastbooted in TWRP 2.6.3.2 but when in TWRP it shows 2.6.3.0 still. It said it updated though through fastboot.
Click to expand...
Click to collapse
i have no idea what the problem could be. i flashed the new twrp with cwm, rebooted recovery, and it shows 2.6.3.2.
you did extract the recovery.img from the zip before fastbooting, correct?
you know what, i downloaded the img file from DHackers Android Hosting. Let me download the ZIP file and flash it through TWRP.
rebretz000 said:
you know what, i downloaded the img file from DHackers Android Hosting. Let me download the ZIP file and flash it through TWRP.
Click to expand...
Click to collapse
heh, well you got the image straight from the source, shouldn't have any problems with it. the ones in the zip files are unmodified except for being renamed to generic "recovery.img" (so i don't have to modify the updater-scripts for each one).
actually, just realized that twrp for the x still shows as 2.6.3.0, i was thinking of the new razr m twrp which does show 2.6.3.2. you can tell it's updated by the haptic feedback though.
Q9Nap said:
actually, just realized that twrp for the x still shows as 2.6.3.0, i was thinking of the new razr m twrp which does show 2.6.3.2. you can tell it's updated by the haptic feedback though.
Click to expand...
Click to collapse
Thank you. I figured it was updated because of the new vibration under settings.
Been driving myself nuts. I fastbooted it through fastboot, mfastboot, and mxfastboot.
Went back to hashcodes 2.6.3.1 then back.
Thank you for confirming.
Edit: DHacker just confirmed on twitter that he forgot to update a script so it will show 2.6.3 but all is well.
rebretz000 said:
Thank you. I figured it was updated because of the new vibration under settings.
Been driving myself nuts. I fastbooted it through fastboot, mfastboot, and mxfastboot.
Went back to hashcodes 2.6.3.1 then back.
Thank you for confirming.
Edit: DHacker just confirmed on twitter that he forgot to update a script so it will show 2.6.3 but all is well.
Click to expand...
Click to collapse
Ahh yes, just noticed the vibration. I suppose it worked after all! A little confusing but it seems to have worked after all
Sent from my XT1060 using Tapatalk
Q9Nap said:
here are the latest cwm/twrp recoveries made by dhacker29 in recovery flashable format:
http://batakang.com/ftp/?dir=devs/mhous33/xt1060
they can't be flashed with stock recovery, can be flashed only with existing cwm/twrp. if you're unlocked but running stock recovery, they can be flashed with safestrap.
all thanks to dhacker29!
Click to expand...
Click to collapse
Thanks for putting these packages together! Now we change recoveries on the fly:good:
So will the CWM work on a 4.4 VZW Dev Ed? If so, can I flash it with TWRP? I know theres a CWM on the forums, but someone said you should only use TWRP with 4.4.
SwiftLeeO said:
So will the CWM work on a 4.4 VZW Dev Ed? If so, can I flash it with TWRP? I know theres a CWM on the forums, but someone said you should only use TWRP with 4.4.
Click to expand...
Click to collapse
I'm pretty sure you can use this CWM. I think it was just updated this week by DHacker.
rebretz000 said:
I'm pretty sure you can use this CWM. I think it was just updated this week.
Click to expand...
Click to collapse
Ah okay. So would you know if I can flash it using TWRP? I mean it isn't an img file so I can't flash it through fastboot, so how would I flash it?
SwiftLeeO said:
Ah okay. So would you know if I can flash it using TWRP? I mean it isn't an img file so I can't flash it through fastboot, so how would I flash it?
Click to expand...
Click to collapse
These are flashable zips you flash in recovery.
Travisdroidx2 said:
These are flashable zips you flash in recovery.
Click to expand...
Click to collapse
Correct. But would you need CWM to flash CWM, or could you use TWRP to flash CWM and it would overwrite TWRP?
SwiftLeeO said:
Correct. But would you need CWM to flash CWM, or could you use TWRP to flash CWM and it would overwrite TWRP?
Click to expand...
Click to collapse
Won't matter. I used twrp to flash the new twrp. Or use twrp to flash cwm. Shouldn't matter.
SwiftLeeO said:
Ah okay. So would you know if I can flash it using TWRP? I mean it isn't an img file so I can't flash it through fastboot, so how would I flash it?
Click to expand...
Click to collapse
I've never flashed a recovery through a recovery. I've only ever used ADB. You can do two things.
1) Extract the zip file to remove the recovery img
2) If the OP doesn't mind me posting this you can go to DHacker's files and get the CWM recovery img he has there.
On the rezound I could take a .IMG recovery and rename it to PH98IMG.img, boot into bootloader, and it would auto flash the recovery... Does this method not work on the moto X?
Sent from my XT1060 using Tapatalk
porkrynd said:
On the rezound I could take a .IMG recovery and rename it to PH98IMG.img, boot into bootloader, and it would auto flash the recovery... Does this method not work on the moto X?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I'm coming from a Rezound too, pretty sure the PH98IMG thing is specific to HTC devices
I managed to get my girlfriends S4 unbricked by flashing a NC5 4.4.2 rom on her phone.
I got safestrap going, super user, etc. on her phone.
From here, how can I get a custom ROM loaded? I tried following cyanogen's steps, but the loki flash does nothing to my phone. When I try to reboot into recovery, it just boot loops till I try to start normally.
These are the steps Im talking about:
"Prepare and flash your recovery image
Download ClockworkMod Recovery:
ClockworkMod Recovery: download
Rename to: recovery.img
Download the Loki installer files (credit to djrbliss for Loki).
Extract the contents of the zip. (You might need to move the recovery image into the same directory as the zip contents, and rename it "recovery.img".)
Windows: run the install-cwm.cmd file
Reboot into recovery and proceed to next section."
http://wiki.cyanogenmod.org/w/Install_CM_for_jflte
ThoR294 said:
I managed to get my girlfriends S4 unbricked by flashing a NC5 4.4.2 rom on her phone.
I got safestrap going, super user, etc. on her phone.
From here, how can I get a custom ROM loaded? I tried following cyanogen's steps, but the loki flash does nothing to my phone. When I try to reboot into recovery, it just boot loops till I try to start normally.
These are the steps Im talking about:
"Prepare and flash your recovery image
Download ClockworkMod Recovery:
ClockworkMod Recovery: download
Rename to: recovery.img
Download the Loki installer files (credit to djrbliss for Loki).
Extract the contents of the zip. (You might need to move the recovery image into the same directory as the zip contents, and rename it "recovery.img".)
Windows: run the install-cwm.cmd file
Reboot into recovery and proceed to next section."
http://wiki.cyanogenmod.org/w/Install_CM_for_jflte
Click to expand...
Click to collapse
Safestrap is the recovery if you're not on MDK. Unfortunately, you're not on mdk. Safestrap users can only flash TW based roms and a couple of GPE roms. No CM, AOSP, nor AOKP will work. It's sad but true. There are some solid TW roms in the development section. Just make sure to follow the steps in the OP since some roms require other files to be flashed with some roms.
Hightower24 said:
Safestrap is the recovery if you're not on MDK. Unfortunately, you're not on mdk. Safestrap users can only flash TW based roms and a couple of GPE roms. No CM, AOSP, nor AOKP will work. It's sad but true. There are some solid TW roms in the development section. Just make sure to follow the steps in the OP since some roms require other files to be flashed with some roms.
Click to expand...
Click to collapse
What does MDK come from? The current build on the device?
Thanks for the post. I love CM on my OnePlus and my s3. Shame I can't put it on hers
Which one do you recommend?
ThoR294 said:
What does MDK come from? The current build on the device?
Thanks for the post. I love CM on my OnePlus and my s3. Shame I can't put it on hers
Click to expand...
Click to collapse
mdk was the last build that had the loki exploit. The OTA after that killed it and all subsequent builds.