Q: Can't get CWM recovery working. - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Hi guys, I've tried pretty much every ones method and files for getting CWM custom recovery on my VZW 10.1 original Tab. But each time when I go back into recovery it's still the basic android recovery. I also get signature errors when I try to update anything from SD card. I have even Odin'd back to GB and updated to ICS again and it still persists. Anyone know a way to get around the signature error. Or a way to get a custom recovery image to take. Thanks
Sent from my Galaxy Nexus using xda premium

MichaelMcC said:
Hi guys, I've trihttp://droidbasement.com/db-blog/ttp://droidbasement.com/db-blog/ttp://droidbasement.com/db-blog/d pretty much every ones method and files for getting CWM custom recovery on my VZW 10.1 original Tab. But each time when I go back into recovery it's still the basic android recovery. I also get signature errors when I try to update anything from SD card. I have even Odin'd back to GB and updated to ICS again and it still persists. Anyone know a way to get around the signature error. Or a way to get a custom recovery image to take. Thanks
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You can bypass error message by :
- flash last (or good) CWM
- remove lines in your rom zip installer (take a look here : http://forum.xda-developers.com/showthread.php?t=1946795)
For 10.1, download recovery 6.0.2.7 from DB (http://droidbasement.com/db-blog/)

Related

E: failed to verify whole file signature

Hallo all'
I have just bought A samsung galaxy s2. Its about 2 weeks old now. So I have recently decided to root it but I think It got wrong. It says its rooted because I can use rom manager and superuser. The problem is I just downloaded a rom and every time I get in to recovery mode iam getting the error: so when I go into recovery mode at the android screen with the triangle and exclemation mark I get the error:
Finding package:
Updating
E failed to verify whole file signature
E (another error cant remeber)
Then it goes into recovery mode but I only have.4 options
Reboot
Wipe system
Update system (when I choose update.zip doesnt work)
Wipe cache
help me please?
Sent from my GT-I9100 using XDA App
you need to download flash an insecure kernel in order to get root.
http://forum.xda-developers.com/showthread.php?t=1103399
Flash the zImage of your root kernel. You will get it by extracting the .tar root file. Copy it to your SD card and flash via CWM with the option Flash Kernel.
Sadly that should not work as at this point he is still running e3 recovery.
TrippinBawLz said:
Hallo all'
I have just bought A samsung galaxy s2. Its about 2 weeks old now. So I have recently decided to root it but I think It got wrong. It says its rooted because
http://forum.xda-developers.com/showthread.php?t=1103399
Use one with CWM 4 do not use Rom Manager .
jje
Click to expand...
Click to collapse
Had the same problem, here is the solution I used; seems to have fixed it for me:
www (dot) inspiredgeek (dot) com/2011/06/16/install-clockworkmod-4-0-0-2-cwm-recovery-for-samsung-galaxy-s2-ii-how-to/
(Sorry for fudged address, cant post links yet since I'm a new user)
Another problem
Solution of brainedbysaucepans worked, but iam having another BIG problem now. So I have installed CWM and went in to CWM with Volume up+Home+Power buttons, from there i choose for install from zip and i have installed the newest
MIUI rom. Restarted. Screen doesnt get passed the ''Samsung galaxy s2'' screen with the triangle and exclemation mark. So I went back to CWM and wiped all data. Still cant get past 1st screen. Telephone is un-usuable. A brick is more usefull then my telephone atm :<. Please help. URGENT.
Without knowing what you have done wrong my suggestion would be to wipe the phone install a stock rom and start reading the faqs and guides .
Full wipe boot to recovery .
mounts and storage format data cache system sd card .
put phone to download mode and flash a stock rom .
jje
betadan said:
Sadly that should not work as at this point he is still running e3 recovery.
Click to expand...
Click to collapse
Thank you! I know you are wise in saying this, as Recovery 3e requires signature verification for flashing external files. Tried pointing stock Recovery to .zip files on sd card (so as to toggle signature verification off), but it doesn't display those files for some reason. How do I get an alternate Recovery that will work with CWR, so that when I flash it will unpack, or how do I otherwise bypass this requirement? Samsung Galaxy SII, Sprint, rooted, but last 5 hours pretty hung up on getting full Recovery going. Obviously a bit of a noob, but would be wicked happy to get a workaround here so I can start flashing ROMs and such.
betadan said:
you need to download flash an insecure kernel in order to get root.
http://forum.xda-developers.com/showthread.php?t=1103399
Click to expand...
Click to collapse
bs, cannot find it. BUKI1 2.3.5 (gingerbread.BUKJ3) no work at all
signature not verified
trying to use bloatkill.zip on my Huawei h866c. After placing .zip folder on sd card and updating with recovery, I get signature verification failed message. Is there a work around. My phone is not rooted and cannot be rooted because of the addition of SuameKinUser.apk to my system files. I would like to remove it so I can traditionally root this device.
Thanks for the help.
I'm having the same sort of problem at the moment, did you ever resolve this?
My phone was locked to the 3 network when I got it, I rooted the phone and got it to the current set up as below;
Samsung gt-i9100
android version - 2.3.5
baseband version - I9100NEKI2
kernel version - [email protected] #2
build number - GINGERBREAD.XWKI8
I have SuperSU installed
I have recently tried to update using Cyanogenmod and Revolt files/guides here on XDA, the latest file being revolt_i9100-ALPHA-20131011.zip however i get the same message on install of;
E:failed to verify the whole-file signature
E:signature verification failed
Can anyone please point out what is going wrong or direct me to another guide that would be best suited to upgrading from my current setup?

[Q] HELP : Flashing : E verification : Please Read..Thanks.

Hey folks,
I've searched the forums, I've been doin this for about 3 hours now, I dislike the standard ATT rom. This is my first Samsung phone I never really had any issue with flashing HTC phones.
1) I have rooted my phone with SUPERUSER
2) I'm not using ROMMANAGER since i've read that this is buggy
3) I have cm-10-20121027-NIGHTLY-quincyatt (CYNOGEN) and Liquid-JB-v2.0-RC5-quincyatt-1020 installed on a SD card
4) I tried to actually hold down the volume UP and DOWN button and power button then boot up to manually flash the roms
no luck at all i keep gettin this "e verification failed" type of message.
If anybody would like to assist that would be greatly appreciated. I'm still going to keep researching while somebody can assist.
Update : I now try using ROMMANAGER, directs me to the bootloader but then says "waiting for SD card to mount" Can't get past this.
any ideas?
Did you install a recovery like CWM or TWRP?
That's prolly the problem. i have the old CWM. I did download the .img for the samsung note which is at this site :
http://www.clockworkmod.com/rommanager
version : 5.8.4.8
I did also install ROMMANAGER now and more famliar with it.
HERES THE THING : how do i install the CWM .img file to make it work with my phone?
if you can assist, i'll greatly appreciate it.
At the bottom of ROM manager is an option to update CWM
Sent from my SAMSUNG-SGH-I717 using xda premium

[Q] Android System Recovery 3e

Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.

[Q] Samsung Galaxy Tab GT-P1000 weird recovery problems

Hi guys! I have been reading through the post and searching for possible solution to my Galaxy Tab GT-P1000 problem but I cant find any solutions. Here is the story:
I have flashed the GT-P1000 tab with clockworkmod version 6 (i am not sure the exact version) using Odin.
Now after flashing the recovery, I have successfully installed Cyanogenmod 11 (nightly build) and everything was successful and everything is great.
A friend of mine borrowed the tab and he put a pattern to lock the phone, instead of asking him what is the pattern I just decided to wipe the tab again to make a clean install. So what I did was I went to recovery and selected "format /system" which I shouldn't have, then after rebooting it is not booting up to Cyanogen anymore, so what i did was I just wiped everything (format /data, cache and factory reset)
Now this is the weird part, the devices has kept on booting up to clockwork recovery and it says the device is not yet rooted, it is asking me if it is ok to root it, I always selected yes
After another boot up, the clockwork recovery is now version 3.0.0.5??? it is really weird? I never installed any clockwork mod with a lower version... How did that happen?
Now whenever I try to install from sd card or restore it or mount it nothing happens, it just says:
E:Can't mount
E:unknown volume
E:unable process volume! skipping
I tried to flash the recovery again using Odin many times but still the clockwork mod is stuck in version 3.0.0.5.
Right now, I am not sure if my understanding of the entire system is correct:
1. Should I install a new recovery, if yes, how and why is it whenever I am installing it again it is not being installed, it gets stuck to version 3.0.0.5?
2. Are there any other recovery I should use and how should I install it? is it the same as using the Odin?
3. Is there a way to install the original recovery of this tab and then from there I will start over again.
@Battousai1
1. & 2. Find an Odin flashable recovery for p1000... Go to download mode and flash it with Odin...
After doing that you shouldn't have the problem anymore...
3. To install the original recovery find the stock rom which is again Odin flashable ... Flash it and you'll have the stock recovery...
Sent from my GT-P3100 using Tapatalk
zeetherocker said:
@Battousai1
1. & 2. Find an Odin flashable recovery for p1000... Go to download mode and flash it with Odin...
After doing that you shouldn't have the problem anymore...
3. To install the original recovery find the stock rom which is again Odin flashable ... Flash it and you'll have the stock recovery...
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
@zeetherocker, thanks! I am currently downloading the overcome recovery, hopefully this will solve the problem.
@Battousai1
Good luck... [emoji106]
Battousai1 said:
@zeetherocker, thanks! I am currently downloading the overcome recovery, hopefully this will solve the problem.
Click to expand...
Click to collapse
Hi guys, just an update, I have finally managed to restore my device's software back to its original version. Thanks to Overcome. Here's the thread for those who still have this device and have some similar problems: http://forum.xda-developers.com/showthread.php?t=1881981

can't install custom recovery??

about a month ago I tried to change to a new ROM on my sgh-i717R model note which was already rooted running TWRP and a custom ROM that I had installed quite awhile ago. I did not realize that TWRP had to be updated to a newer version to use the 4.4 ROMS and the update failed and bricked my phone. I managed to fix it and put back a stock Rogers 2.3.6 ROM and it put back the original samsung recovery. The problem now besides being on an old ROM there is a lot of input lag using on screen keyboard, so I want to try a new custom ROM to see if it fixes things, but when I try to flash a new recovery with Odin (TWRP 2.8.0.0), Odin tells me that everything is good and it passes, but when I then reboot my device and go into recovery mode afterwards, it is the same samsung recovery mode with only the custom binary download counter incremented, but TWRP is nowhere to be found... I have tried with several versions of TWRP and it is the same thing.
qazplokm said:
about a month ago I tried to change to a new ROM on my sgh-i717R model note which was already rooted running TWRP and a custom ROM that I had installed quite awhile ago. I did not realize that TWRP had to be updated to a newer version to use the 4.4 ROMS and the update failed and bricked my phone. I managed to fix it and put back a stock Rogers 2.3.6 ROM and it put back the original samsung recovery. The problem now besides being on an old ROM there is a lot of input lag using on screen keyboard, so I want to try a new custom ROM to see if it fixes things, but when I try to flash a new recovery with Odin (TWRP 2.8.0.0), Odin tells me that everything is good and it passes, but when I then reboot my device and go into recovery mode afterwards, it is the same samsung recovery mode with only the custom binary download counter incremented, but TWRP is nowhere to be found... I have tried with several versions of TWRP and it is the same thing.
Click to expand...
Click to collapse
You may have lost root when you went back to GB
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
You may have lost root when you went back to GB
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
yeah it was unrooted, but you cannot root without putting the custom recovery first.. Anyways I solved the problem, for some reason TWRP does not work (even though I tried all the versions specified for quincyatt and sgh-i717) but I was able to put on CWM no problems and re-root with superuser from there.
qazplokm said:
yeah it was unrooted, but you cannot root without putting the custom recovery first.. Anyways I solved the problem, for some reason TWRP does not work (even though I tried all the versions specified for quincyatt and sgh-i717) but I was able to put on CWM no problems and re-root with superuser from there.
Click to expand...
Click to collapse
I know this thread is a couple weeks old but I thought I'd add something that I have found that might help if someone else has this problem.
The only way I was able to install the new version of TWRP was to install the old one first while rooting the phone then download the new versions .zip and update it via TWRP. I was able to get the new version working that way and now I am able to flash any rom I want with no issues.
Hope this helps others.

Categories

Resources