Hello. I have been trying for many many hours to boot into CWM 4.0.0.2 but everytime I reboot to recovery, it boots to the stock recovery mode and not CWM. I have the zip file installed on my phone and I flashed CWM to my phone and click reboot into recovery to no avail. I am really getting frustrated with this, so any help is gravely appreciated! Thanks!!
Cwm is wrong
You have to download the cwm from these fourms not rom manager
This phone needs a custom 3.x cwm
Sent from my SGH-T839 using xda app-developers app
---------- Post added at 08:33 PM ---------- Previous post was at 08:24 PM ----------
Check the sticky in android development the ref reupload
Sent from my SGH-T839 using xda app-developers app
immorality said:
Cwm is wrong
You have to download the cwm from these fourms not rom manager
This phone needs a custom 3.x cwm
Sent from my SGH-T839 using xda app-developers app
---------- Post added at 08:33 PM ---------- Previous post was at 08:24 PM ----------
Check the sticky in android development the ref reupload
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
I didn't use rom manager. I manually extracted recovery.zip and update.zip and rebooted, but still no ClockWorkMod. I also tried your method and still the same result. Won't load CWM.
Well, I put recovery file and update.zip into parent folder, rebooted and booted into recovery mode, and clicked reinstall packages (I only get 4 options on my recovery mode window, which are reboot system now, reinstall packages, delete all user data, and delete cache data), but it gives me the error "E:signature verification failed
installation aborted."
It won't let me boot into clockworkmod recovery; just the stock recovery. Atleast it doesn't give an update.zip error.
http://forum.xda-developers.com/showthread.php?p=40198560
See page 3, like the 36th post or so, this method has worked for me dozens of times, never an issue
Sent from my Nexus 4 using xda premium
demkantor said:
http://forum.xda-developers.com/showthread.php?p=40198560
See page 3, like the 36th post or so, this method has worked for me dozens of times, never an issue
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I rebooted into recovery and tried to install the rom, but it still didn't work.
OK, then you will need to go through the guide from the start, skip only the hiemdall stuff that is in red but do all the rest, if you follow these direction you can't go wrong
Sent from my Nexus 7 using xda premium
demkantor said:
OK, then you will need to go through the guide from the start, skip only the hiemdall stuff that is in red but do all the rest, if you follow these direction you can't go wrong
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Are you talking about the stickied noob guide?
Nope, the one I linked you too... In my aroma thread...page three, forget the post number but you can't miss it
Sent from my Nexus 7 using xda premium
demkantor said:
Nope, the one I linked you too... In my aroma thread...page three, forget the post number but you can't miss it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I see it. Currently doing it and reached the part where it is in download mode. It says Downloading... Do not turn off Target!!! However, I don't see t839-Sidekick4G-UVKG2-One-Click. Do I download it?
This was the part in red that I said to skip, this part is only if you soft bricked your phone, if you want go back to start and root from the beginning (ie follow guide from start to finish) you can and its good practice. but really if you have su and busybox installed then you just need to replace the recovery binary and follow the guide from there.
Sent from my Nexus 7 using xda premium
demkantor said:
This was the part in red that I said to skip, this part is only if you soft bricked your phone, if you want go back to start and root from the beginning (ie follow guide from start to finish) you can and its good practice. but really if you have su and busybox installed then you just need to replace the recovery binary and follow the guide from there.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have been following your guide and I feel optimistic. I didn't see anything in red, so I didn't notice. I will try out the best and post back. If I get stuck, can I PM you?
Sure, if your on a mobile app it may not show in red. But I'll be heading off took bed shortly, really if you are stuck just download all I linked and start from scratch and don't skip anything, can't mess up this way and only takes 10min tops from start to end (maybe 15 if you never done it before)
Sent from my Nexus 7 using xda premium
demkantor said:
Sure, if your on a mobile app it may not show in red. But I'll be heading off took bed shortly, really if you are stuck just download all I linked and start from scratch and don't skip anything, can't mess up this way and only takes 10min tops from start to end (maybe 15 if you never done it before)
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks man. I will let you know by tomorrow if this worked for me.
azeem40 said:
Thanks man. I will let you know by tomorrow if this worked for me.
Click to expand...
Click to collapse
Nope, I still get the error:
Even after copying the recovery file over the original, it gives:
E:can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
I don't know what I am doing wrong. Any more help is greatly appreciated!
azeem40 said:
Nope, I still get the error:
Even after copying the recovery file over the original, it gives:
E:can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
I don't know what I am doing wrong. Any more help is greatly appreciated!
Click to expand...
Click to collapse
Faulty root
A) re root
B) odin then re root
Sent from my SGH-T839 using xda app-developers app
immorality said:
Faulty root
A) re root
B) odin then re root
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
I used SuperOneClick. Even while using it, the root can still end up being bad? I have su permissions and it says my phone is rooted.
azeem40 said:
I used SuperOneClick. Even while using it, the root can still end up being bad? I have su permissions and it says my phone is rooted.
Click to expand...
Click to collapse
Yes it happens very rarly but has happen to me
An glad you sloved this issues will move to the next thread
Sent from my SGH-T839 using xda app-developers app
Related
Hey guys I'm having a cwm issue I followed the instructions from a previous post pushed recovery to s.bin r/w rebooted then into recovery and reinstall packages but kept giving me installation aborted message? Now can't find recovery file I pushed please xda help! Thanks in advanced
Sent from my SGH-T959V using XDA Premium App
yosif yackson said:
Hey guys I'm having a cwm issue I followed the instructions from a previous post pushed recovery to s.bin r/w rebooted then into recovery and reinstall packages but kept giving me installation aborted message? Now can't find recovery file I pushed please xda help! Thanks in advanced
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Try flashing this with Odin, you'll have CWM without pushing the custom recovery file to /bin
http://forum.xda-developers.com/showthread.php?t=1195860
Thank you! I'll have to wait to get to a computer
Sent from my SGH-T959V using XDA Premium App
I had the same problem getting this to work. I tried a lot of times before I finally got it to work.
The only thing I did differently to finally get this to work was to download the files to my computer first and then transfer them to my phone. When I downloaded directly to the phone the file had a .bin extension added to it. Just deleting the .bin extension didn't work for me.
FBis251 said:
Try flashing this with Odin, you'll have CWM without pushing the custom recovery file to /bin
http://forum.xda-developers.com/showthread.php?t=1195860
Click to expand...
Click to collapse
worked for me and it was after whole morning,
wish i had come to this section first.
Thanks a ton.
you need the recovery file in system/bin AND the update.zip on your sd card root for cwm to work
Just rooted my phone now I'm wondering I install the rom manager I tried to run back up current rom when rebooted it froze has to pull battery. Then when. Rebooted tried to reboot into recovery and again froze what should i do.
Sent from my Nexus S using xda premium
Are you able to boot into recovery with Power + Vol Up?
Dont use rom manager just use cwm.
Sent from my Nexus S using xda premium
mixtapes08 said:
Dont use rom manager just use cwm.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I guess the next question would be...
Smok3thekid: do you have Clockwork Mod recovery on your phone?
No I can not boot into. Recovery from power+up
Sent from my Nexus S using xda premium
kto_matchu said:
I guess the next question would be...
Smok3thekid: do you have Clockwork Mod recovery on your phone?
Click to expand...
Click to collapse
To be honest I'm not 100 % sure I followed the steps of the nexus hacks on how to root and now trying to backup stock.img and I can't boot into recovery.
OK so I'm pretty sure I do I did it in rom manger
Sent from my Nexus S using xda premium
So I finally got my phone to do a backup on my stock rom then I tried to reboot into recovery just to check it out and to see if it would work and it still frozen or gave me error it was (!) And had to pull battery
Sent from my Nexus S using xda premium
smok3thekid said:
To be honest I'm not 100 % sure I followed the steps of the nexus hacks on how to root and now trying to backup stock.img and I can't boot into recovery.
OK so I'm pretty sure I do I did it in rom manger
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
You should go back and follow the instructions, then!
http://forum.xda-developers.com/showthread.php?t=895545
I got clockwork mod recovery 3101 that's what I flashed when I rooted
Sent from my Nexus S using xda premium
That's what I get when I boot Into recovery
Sent from my Nexus S using xda premium
kto_matchu said:
You should go back and follow the instructions, then!
http://forum.xda-developers.com/showthread.php?t=895545
Click to expand...
Click to collapse
Follow these instructions to the letter and you'll be fine....
Greetz
smok3thekid said:
That's what I get when I boot Into recovery
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Looks like you're having issues getting into the recovery. That screen isn't the recovery, and I've had it before.
A lot of times, when you root on a stock rom, the phone deletes clockwork and restores the old recovery. That might be why you're having issues with it.
http://forum.xda-developers.com/showthread.php?t=895545
The second post on this thread describes how to make clockwork stick. You might need to make use of some adb commands OR get an app like Root Explorer.
1. Flash the recovery
2. Follow the instructions in the second post before rebooting your phone.
That should do it.
kto_matchu said:
That screen isn't the recovery, and I've had it before.
Click to expand...
Click to collapse
Actually it is. That's the stock recovery, but it's options are too limited which is why we use CWM.
Rest of your instructions should help the OP out though, good on that.
Greetz
Just flash clockwork again and flash a non stock rom, or remove the file as described if u wanna stay stock.
Ya I think it was just freezing up got into recovery and installed new rom
I do thank everyone help
Sent from my Google Nexus S using xda premium
frutelaken said:
Actually it is. That's the stock recovery, but it's options are too limited which is why we use CWM.
Rest of your instructions should help the OP out though, good on that.
Greetz
Click to expand...
Click to collapse
True-say! Thanks for the correction
My cwm cannot find my sd card so that means I can't flash zip files. Can anyone help me get cwm 4.0.0.9? Currently I have cwm 5.0.2.7
Sent from my myTouch 4G Slide using xda premium
What's the error? Is it that weird Lum thing?
Sent from my Bulletproof_Doubleshot using xda app-developers app
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Also the one your on is the most stable, have you tried messing with your SD? This happens to me every once in a while. I just reboot.
Sent from my Bulletproof_Doubleshot using xda app-developers app
AgentCherryColla said:
What's the error? Is it that weird Lum thing?
Sent from my Bulletproof_Doubleshot using xda app-developers app
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Also the one your on is the most stable, have you tried messing with your SD? This happens to me every once in a while. I just reboot.
Sent from my Bulletproof_Doubleshot using xda app-developers app
Click to expand...
Click to collapse
I think its the lum thing when using terminal emulator but some told me to flash 5.0.2.7 and I did and it's messed up
Sent from my myTouch 4G Slide using xda premium
Is there a problem with the true official CWM release or are you just wanting to change? And at this point, unless you are trying to apply an "update.zip" file you don't need access to your external card.....unless I am just misunderstanding your issue. ADB will flash your new recovery directly to the correct partition on your internal system memory. Won't it??
BTW Agent.....what is that weird "Lum" thing? I've not run across that term.
its the error with opening sdcards on cwm 6.x
xmc wildchild22 said:
its the error with opening sdcards on cwm 6.x
Click to expand...
Click to collapse
Thank you XMC....I'm always anxious to learn. :good:
Do you have any idea why that type of error would pop up out of the clear blue like that?
WeekendsR2Short said:
Is there a problem with the true official CWM release or are you just wanting to change? And at this point, unless you are trying to apply an "update.zip" file you don't need access to your external card.....unless I am just misunderstanding your issue. ADB will flash your new recovery directly to the correct partition on your internal system memory. Won't it??
BTW Agent.....what is that weird "Lum" thing? I've not run across that term.
Click to expand...
Click to collapse
Can you help me with this step by step
Sent from my myTouch 4G Slide using xda premium
K7Cobb said:
Can you help me with this step by step
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
You really won't have any problems. I promise. It flashes just like any other version of CWM thru adb. Just download it from my "Tools" thread, place it where you normally flash a file from, rename the file to boot.img. Then from your command window on your computer you just do the following string of commands:
reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Remember? :good:
flash boot?
WeekendsR2Short said:
You really won't have any problems. I promise. It flashes just like any other version of CWM thru adb. Just download it from my "Tools" thread, place it where you normally flash a file from, rename the file to boot.img. Then from your command window on your computer you just do the following string of commands:
reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Remember? :good:
Click to expand...
Click to collapse
Hang on, isn't he trying to flash his recovery? I've never done it through fastboot, but I can't help but think that flashing a recovery image to the boot partition won't turn out well... There is an option in fastboot to flash recovery, but again, I've never used it.
The way I've always flash recovery images is (in terminal emulator or ADB)
flash_image recovery /sdcard/name-of-recovery.img
As I was looking up this command, I saw someone (well, not just anyone, kornyone) suggest using ROM Manager... Although you would, of course, have to flash an older version of CWM.
My guess could be stupid but try redownloading cwm and reflash cwm recovery ...
Sent from my myTouch_4G_Slide using xda app-developers app
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
K7Cobb said:
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
Click to expand...
Click to collapse
It's an Android command, you need to either run it through ADB Shell or through the Terminal Emulator (You ran it directly in the Windows command line)
Do you have ADB and fastboot setup? If not, go download Android SDK from Google and get it installed. (Be sure to install Platform Tools as well as Tools)
If you haven't setup the Android SDK before, you'll need to install the Java SDK too.
The second two commands he provided are not ADB commands, they should be run directly from the directory where fastboot is installed, which is the Android SDK Install location\platform-tools.
The default Android SDK install location (as of the new version I downloaded yesterday) is C:\Users\(Your Name)\AppData\Local\Android\android-sdk . The old default location was C:\Program Files (x86)\Android\android-sdk . I like that one better. You can use whichever you wish, just be sure you remember where it is.
I can't post links, otherwise I'd link you to a guide. Sorry :/
Nvm thank you all
Sent from my myTouch 4G Slide using xda premium
Sompom said:
Hang on, isn't he trying to flash his recovery? I've never done it through fastboot, but I can't help but think that flashing a recovery image to the boot partition won't turn out well... There is an option in fastboot to flash recovery, but again, I've never used it.
The way I've always flash recovery images is (in terminal emulator or ADB)
flash_image recovery /sdcard/name-of-recovery.img
As I was looking up this command, I saw someone (well, not just anyone, kornyone) suggest using ROM Manager... Although you would, of course, have to flash an older version of CWM.
Click to expand...
Click to collapse
Your way will work but I promise the ADB fastboot flash sequence will too. It's the only way I've ever flashed my recoveries. Always more than one way to skin a cat.
---------- Post added at 10:49 PM ---------- Previous post was at 10:37 PM ----------
K7Cobb said:
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
Click to expand...
Click to collapse
Sorry......I just kinda took something for granted. (as usual)
Before you can run that string I told you about you have to tell your system it is an ADB command. ACTUALLY it's like this:
ADB reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Sorry for my oversight. I hope it didn't cause you much grief.
I do the stuff correct. But when I go to clock work it still says 5027
Sent from my myTouch 4G Slide using xda premium
So when you enter the command it tells you "sending image" and then the time?
After that it tells you "writing image" then the time and then something to the effect of "transfer complete"? If it does then somehow you've gotten the images confused and renamed the 5.0.2.7 image and put that one in your flashing folder and not the 4.0.0.9 image.
It's always your choice what you run on your phone but I still don't understand your opposition to the official CWM release. ANYway....Good Luck in your attempt.
WeekendsR2Short said:
So when you enter the command it tells you "sending image" and then the time?
After that it tells you "writing image" then the time and then something to the effect of "transfer complete"? If it does then somehow you've gotten the images confused and renamed the 5.0.2.7 image and put that one in your flashing folder and not the 4.0.0.9 image.
It's always your choice what you run on your phone but I still don't understand your opposition to the official CWM release. ANYway....Good Luck in your attempt.
Click to expand...
Click to collapse
Omg it does not work Clearly if I'm having problems. Not meant to be taken in a mean way but I keep telling people the same thing
Sent from my myTouch 4G Slide using xda premium
Omg. What is wrong with this???!?!?!?!?!? I need MAJOR HELP!!!
Sent from my myTouch 4G Slide using xda premium
What I'm trying to find out is how in the crap you got 5.0.2.7 on your phone to start with. If you flashed it thru terminal emulator you can put 4.0.0.9 on there the very same way. If you flashed it thru ADB you can put 4.0.0.9 on there the very same way. See what I'm saying? Have you ever flashed anything or did you get it on there thru maybe Rom Manager. I'm just looking for a clue. SEE? I know you're having a problem but we need to more than "it's not working".
K7Cobb said:
I do the stuff correct. But when I go to clock work it still says 5027
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I am running 5.5.0.4 and ROM manager reports the version as 5.0.2.7. Seems to work fine here.
Hastily spouted for your befuddlement
I must be making a big mistake along the process, because I am fairly new to this. I flashed a couple ROMs on my Droid X in the past, but my S3 is just not working for me...
I have followed the stickied guide to flash the stock ROM, install TWRP, then root and unlock bootloader. When I attempt to follow the instructions to install the ROM I have chosen, it fails every time. It fails just after attempting to open the .zip, so it is very quickly. I have Odin flashed back to stock 3 times and tried 2 different ROMs, both fail the same way.
Is there any more information I should provide?
What error message you get? Whether you are seeing TWRP recovery or Stock recovery?
Sent from my SCH-I535 using xda premium
ramdesai said:
What error message you get? Whether you are seeing TWRP recovery or Stock recovery?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
"Unable to open .zip," or something similar.
So have you tried just rooting the phone first with bootloader unlocked. Once you make sure you have the phone rooted then go back into recovery to flash.
Also there are so many steps you could have messed up on a little bit more detail on what it does when you go into recovery to flash or if you can't even get there.
Sent from my SCH-I535 using xda premium
honestcrook said:
"Unable to open .zip," or something similar.
Click to expand...
Click to collapse
You getting this from twrp or cwm
Sent from my SCH-I535 using xda premium
bbqsfire said:
So have you tried just rooting the phone first with bootloader unlocked. Once you make sure you have the phone rooted then go back into recovery to flash.
Also there are so many steps you could have messed up on a little bit more detail on what it does when you go into recovery to flash or if you can't even get there.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Good point. Be sure your bootloader is unlocked - most roms now will not flash with a locked bootloader. Also did you verify the md5 matches? You flashed on the dx so I'm sure you did - just trying to cover all the bases.
Sent from my SCH-I535 using xda premium
bbqsfire said:
You getting this from twrp or cwm
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Getting the same error in both. Tried CWM first, because that is what I was familiar with from the past, but I reflashed and tried TWRP. They are not both installed at the same time, if that would be an issue.
I have only verified that my bootloader is unlocked by the split second flash of SAMSUNG during boot. I also do not have a "custom" message at the bottom. I'm not familiar with any other way to verify.
After trying a few different things with no success, I have looked into the error a little further.
Opening update package...
minzip: Missed a local deader sig (at 10)
E:Can;t open /blah.zip
(bad)
Installation aborted.
I:Can't partition non-vfat: datamedia
I:Can't format unknown volume: /emmc
Click to expand...
Click to collapse
Anyone want to lend a hand?
Hey guys,
I had an older version of ParanoidAndroid on my Tab2 and I wanted to install something else. So I found a ROM here and tried to install it from CWM. I (think I) made the dumb mistake of formatting everything before installing, and during installation it just... failed. I googled since and found that the current version of CWM might be incompatible with 4.4 (that the ROM was running). Whatever the case, it's now stuck in a boot loop and I don't know what to do. Any suggestions?
When you formatted everything, did you mean /system to?
Sent from my One X using xda app-developers app
Nope. Sorry for the bad wording, I meant that from CWM I did a "wipe data/factory reset", wiped cached partition, dalvik cache.
First is there a way you can update your CWM recovery? Also, can you still enter download mode to flash?
Sent from my One X using xda app-developers app
TheDougTechCrew said:
First is there a way you can update your CWM recovery? Also, can you still enter download mode to flash?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
First, I don't know how to update the CWM recovery. I found updates on the CWM website (can't link to it due to low post count here) but it only has .img files, which Odin doesn't support. I don't know any other method of installing this other than Odin, at this point.
And yes, I can still enter download mode, and CWM. I just don't know what to do with them.
andreiknox said:
First, I don't know how to update the CWM recovery. I found updates on the CWM website (can't link to it due to low post count here) but it only has .img files, which Odin doesn't support. I don't know any other method of installing this other than Odin, at this point.
And yes, I can still enter download mode, and CWM. I just don't know what to do with them.
Click to expand...
Click to collapse
Tell me what is the model number of your Galaxy Tab and I will find some recovery image and ROM you can flash and provide instructions.
It's the P3110.
Look for @Android-Andi s thread on latest recovery
Sent from my GT-P3110 using xda app-developers app
SiqrCarnbon said:
Look for @Android-Andi s thread on latest recovery
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Again, I can't link due to the low post count, but I found this thread started by him: /showthread.php?t=2535083 . However, I see it's only for P5XXX devices...
...up?
This is for the 7in. Found it in Development section:
http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Many thanks, flashing this worked!