I have a Sprint 7 Tab running EF17, Firmware v. 2.3.4 and Kernal 2.6.35.7.
Long ago I rooted the Tab and installed Root Explorer, Rom Manager and Titanium RootPro, all without any problems at all. When I use Rom Manager, it states I have Clockworkmod version 2.5.1.2 (which might be the problem).
I wipe Dalvik and factory reset. No matter which version I try to flash, the update process starts and sates "Verifying update package..." then I get the signature verification failed message.
I spent a couple of hours in this forum trying to find out what I was doing wrong and it seems either I have too old a version of CWM or my SDCARD is somehow corrupt.
If the problem is the version of CWM, is there a simple way to update it? I tried to use Heimdall to update the kernal. Zadig recognizes the Tab when shut off, but when I put the Tab into downloading mode and list devices, the Tab does not show up.
If the problem is the SDCARD is corrupt, what next?
The Old version CWM was the problem. For some reason my old 32 Laptop would not install Heimdall so I tried a new 64 windows machine and I installed the new kernal. The install then went fine.
Unless there is a belief that this post might help another user, please delete this post.
Related
So I have a compilation of three issues that I've found on the forums but after two days, of researching and troubleshooting, no luck so hoping someone out there has had a chance to fix this and can share their knowledge.
Here's what I've done so far:
Ran Super One Click to root and worked
Flashed bootloader 30.04
Booted to "critical error 1337 510b"
RSD flashed to VRZ_MB810_2.3.32_1FF_01.sbf (Happy_Holidays_From_TBH.zip) using RSD Lite 4.8
RSD flashed to SHADO_X6_2.3.34_SYSTEM-ONLY.sbf (SHADO_X6_2.3.34_SYSTEM-ONLY.zip)
Lost root so tried Super One Click - wouldn't work
Installed Koush Bootstrap recovery
Installed and successfully rooted with z4root
Tried installing to C_01.43.01P.zip from Peter Alfonso and fails with error in list below
So here are the three errors I'm getting now and haven't been able to find a fix to any of them. I'm thinking it's possible permission issues on my device. I ran the Fix Permissions options from ROM Manager but it didn't help.
When I reboot into recovery mode, get error: "e: can't open /cache/recovery/command"
When try to install baseband update and says"Writing RDL/BP image... E:Error in /sdcard/update.zip (Status 0) Installation Aborted"
Tried flashing a few other SBF's and about 10 seconds into each, DX shows error "critical error 1337 510b" and flash never moves ahead
Here are some of the items I've tried and none of them have helped:
Rename to update.zip
Install using built in recovery
Installed ROM Manager
Installed ClockWork
Battery pull
Wipe cache (several times)
Install package with DroidExplorer
This list could go on and on an on - I've been working on this for two days
EDIT: Realized I hadn't upgraded the kernel from TBH so I just installed it and it worked properly, but still doesn't fix above issue when trying to update my baseband.
The good news is that I took a backup using ClockWork and I've restored it a half dozen times over past few days (so that I could actually leave the house and use my phone) so my phone is working, I just can't do any more flashing
Any suggestions? Thanks in advance!
EDIT: Been a few days and no replies. Very uncommon for this forum. Did I post in the wrong area? or not follow forum rules? Or I'm just an idiot? I've tried formatting all partitions (except for sdcard) and get "Error formatting boot partition". All other partitions format correctly but still can't install the latest baseband. The only thing that still works is flashing sbf of VRZ_MB810_2.3.32_1FF_01.sbf and SHADO_X6_2.3.34_SYSTEM-ONLY.sbf to get back to stock and restore my latest backup. Please help, I would really like to get the latest baseband installed.
I've been told that C_01.43.01P is only for original Droid, not the X - which is why it wouldn't work.
Go to the Droid X Android Development subforum and look at my thread for the update zip. Its a zip you download and flash through clockwork to upgrade and /or fix issues with the latest OTA. That should fix you right.
Hi
I have recently had my HTC Wildfire rooted after the fantastic AlpharevX contribution.
I've played around with different ROMs, and since I experienced problems with GPS in CM 7.1 RC1, I decided to go for a Radio update.
I have CWM recovery 3.2.0.0, which according to this general Wildfire thread is not compatible with flashing the current radio versions.
I therefore downloaded the Radio zip-file, copied it to my SD root dir and started ROM Manager and selected update ROM from SD card.
I checked "Backup current ROM" and "Wipe Dalvik cache" and pressed OK to the different dialog boxes.
It then rebooted to a black screen with the little green Android and a warning sign with an exclamation mark in it.
It has just stayed there for more than 10 minutes now.
I read somewhere that flashing radio can be riscy, and also that one must have patience and not interrupt anything. Therefore I haven't dared touching it without seeking advice...
What should I do? Am I supposed to press anything to continue, or should I try to turn it off (either using power button or by battery removal)?
Kind regards, Martin
UPDATE: I lost patience and decided to click on the different buttons. By clicking the power button, it displayed that I had entered CWM Recovery 3.2.0.0 and the log states:
Finding update package...
Opening update package...
Verifying update package...
E: failed to seek in /cache/update.zip (Invalid argument)
E: signature verification failed
Installation aborted.
I have just rebooted for now... Is it somehow possible to have two different CWM Recovery versions installed, such that I can boot directly into 3.2.0.0 and maybe enter 2.5.x.x. from ROM Manager?
you must flash clockworkmod recovery in rom manager then click run in recovery mode (second option) in rom manager then phone will reboot and got temporary CWM 2.5.0.7 and you can flash radio in this version
ziemjak said:
you must flash clockworkmod recovery in rom manager then click run in recovery mode (second option) in rom manager then phone will reboot and got temporary CWM 2.5.0.7 and you can flash radio in this version
Click to expand...
Click to collapse
Thanks a lot...
I just updated the radio.
Now I also now how to flash Froyo custom ROMS. CWM 3.2 only allowed me to flash Gingerbread ROMs.
moderator pls close thread problem solved
Hi since we are at it, I also have a question about radios...
My Bluetooth used to work just fine on my htc stock ROM before switching to CM 7.0.3, I could both send and receive files from my mac.... well the thing is I can only receive them now, I can't get my wildfire to send anything to my mac! (already tried the app from the market, I think it's called Bluetooth File Transfer)
Anyway do you think a radio upgrade or in my case downgrade could fix this? I currently have 13.55.55.24H_3.35.20.10.
EDIT: This is not a result of ROM Manager, this is a result of installing Overstock 1.4.3 which also installs CWM recovery.
Not trying to be rude or anything, but I don't remember this ever not working.
I am having issues with 3e. No matter how carefully I follow the instructions (flash->reboot->reinstall packages always fails) when flashing recovery from current Rom Manager and Premium License, it does not work. Additionally, the premium license is persistent in my applications list and no premium ROMs ever show up in my download list. Even when I select Vibrant MTB and either 2.x or 3.x, all I get is a message that states current recovery will be used. I'm still going thru posts for a possible solution.
Try putting this in the root of your internal SD, reboot to recovery and reinstall packages twice.
Yeah, I was misinformed. This is not a result of ROM Manager, this is a result of installing Overstock 1.4.3 which also installs CWM recovery.
If anyone want to do this it is really simple with the SGS kernel flasher app. Download your overstock kernel of choice from here or your choice of kernel that includes CWM from the dev bible, unzip it, move the zimage to the internal phone memory and then choose that file as your kernel with the SGS Flasher.
Note: I have not been successful with going back to stock kernel when I tried to but that may have been because I didn't disable the lag fix.
jneal9 said:
Try putting this in the root of your internal SD, reboot to recovery and reinstall packages twice.
Click to expand...
Click to collapse
I'm 100% stock on 2.2Froyo except for root/unlock and am puzzled by this. I know it's not ROM Manager because it worked on my first SGS4G which died and totally bricked after a week (TMO exchanged it happily cause it wouldn't even go into download mode or charge).
What's in this update you linked? Cause I'm smart, but not as smart as most of the posters here and I recognize only a couple things in the file.
It installs CWM.
Are you using a Vibrant or SGS4G?
SGS 4G for TMobile.
BTW... I totally appreciate the help here. I don't know the ins-n-outs of the android phones like I do IOs, not that I'm all that up to date on that either.
Update... Still does not work. I get the failed signatures error and the update is aborted. I tried doing a factory reset and re-rooting the phone in case something didn't work correctly and get the same error. At this point, it's all gravy since the only thing I really needed was the unlock but now I'm in a "I just want to know how this works" mode.
Thanks for the help.
Ok yeah that my be the problem since that zip is for the Vibrant. So just to be straight, you are unable to get CWM on your SGS4G?
That's correct. I can't apply any update.zip nor does flashing CWM recovery work. It says it's flashing but then when I do the 3 button reboot to get to recovery, it's the 3e version still and when I go to reinstall packages, it starts but then fails as it tries to verify signatures.
Hi Folks,
I'm trying to get clockwork installed on a rooted stock firmware vibrant for a friend. Using ROM manager i've tried to install CWM and it says it is successful, however after trying to reboot into recovery and choosing re-install packages I get these errors:
E:Failed to verify Whole File Signature
E:signature verification failed
Installtion aborted
I tried flashing Vibrant (MTD) Clockwork Recover 3.x from ROM manager but it does the same thing.
Also tried the AIO tool from the sticky in the dev section and it doesn't work either. I chose the custom ROM but it doesn't push it to the phone or reboot it into recovery. (The install drivers option gave me a windows unhandled exception error)
I downloaded Heimdall but am not sure how it's used, can it flash any ROM or only specially formatted ones?
I've been searching these forums for a few days now and finding so much new and old processes to do things and I'm not very familiar with Samsung phones so any help is appreciated. Thank-you.
Re-Root it
Re-root the phone using One-click, when Baywolfs fails, one click always does it because it push's it through using ADB
CWM wont work unless the phone is proper ROOTED, youll know when its done right, cause youll see the super=user App after your done
Link: http://forum.xda-developers.com/showthread.php?t=739300
After that, un-install Rom manager, then re-install it, then while your connected to WIFI or provider, make sure you flash CWM recovery,
Re- download the ROM again, but dont open it!!
Then when you are ready to flash that ROM as a zipped file, DO NOT open it [ meaning UNZIP] or you'll continue to get the signature error.
Then either flash using reboot into recovery or install using CWM option of sd card install, either or works!! .
Are you having trouble getting past the stock 3e recovery? I've been trying to get past it for a few days but have been poking around learning the in/outs of this. I have not yet gotten Rom Manager to properly flash CWM Recovery... the stock 3e is stubborn. Once CWM recovery is done, your options open up for backups, restores and installing some custom roms.
I don't know what the solution is but I'm still looking around.
Hope this was on track...
Its stuborn in the sense its picky about free space. You'll need to free up some room in order to use CWM. Reference this thread for guidance -
http://forum.xda-developers.com/showthread.php?t=925400
I was running CyanogenMod 10.1.x versions, using ROM Manager to upgrade as new ones were available. However, when I tried to upgrade to 10.2.1 it kept rebooting every several minutes, showing the new bootup screen with the rotating arrow. I tried upgrading to version 11...M9 also with ROM Manager and now it only comes up in recovery mode (CWM v6.0.3.1). There seems to be no way to finalize the installation. I can't sideload from the PC, since, although DeviceManager shows "Google Galaxy Nexus ADB Interface," I do not see any entries in Device Management or in the Explorer, so I can't offload a full backup, nor can I use adb to sideload the new CM. I can't instal from the internal sdcard, since it starts with "...Installing /sdcard/update.zip" and then can't find it - it comes up with the "(no such file or directory)."
Since (except for Device Manager) nothing on the PC recognizes a connection with the Nexus 10, I'm pretty much out of options. I can do a complete "wipe data/factory reset" I suppose, but would like something not so drastic (given no backup). When I look at CWM's display of mounted and unmounted storage, sdcard is unmounted and won't mount. I've even done a full wipe and factory reset, with the same results.
A brand-new install of the Samsung USB Drivers 1.5.33.0 through Skip's app now results in an error message when I reattach the tablet saying the driver install failed. I still show the device in Device Manager.
I have Skip's Universal Android Toolkit v1.0.2 and it seems to recognize that a Nexus 10 is connected, but can't do anything to it (it expects you are originally booted to Android, not recovery.
This is my first Samsung device, so I'm totally unfamiliar using Odin and haven't figured out how to use it to correct the problem.
It seems that, if I can sideload a copy of CM 11, I should be okay, but all roads look closed.
Any ideas?
I'm locked in a loop.
'
Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!
Thanks - will keep trying.
demkantor said:
Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!
Click to expand...
Click to collapse
I downloaded the latest Android SDK with platform tools and put the cm zip file in the directory with adb.exe. On the tablet, in ClockworkmMod Recovery, I selected "install zip from sideload." The tablet went into sideload mode and instructed me to type "adb sideload <filename>. So I typed: "adb sideload cm-11-20140805-SNAPSHOT-M9-manta.zip" and hit the enter key. The PC reported 100% downloaded. The tablet listed:
Restarting adbd...
Finding update package...
Opening update package...
Installing update...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I'm at least communicating between the PC and tablet, but the update is still failing. Any hope of trying to flash standard ROM, re-root, and start again?
You need to update your recovery, grab the latest TWRP or CWM .img for manta and flash in via fastboot first, then boot to new recovery then flash ROM
Thanks, I grovel at your feet!
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.
Beartooth01 said:
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.
Click to expand...
Click to collapse
Great to see @demkantor help get you back up and running ..
@Beartooth01 Can you plz add "SOLVED" to the thread title
Thx Josh